arrow-julia
arrow-julia copied to clipboard
Configure repository metadata
We can configure this repository's metadata by .asf.yaml
. See also: https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features
We should change at least notification configurations. All issue changes will be notified to [email protected] with the default configuration.
We want to send only "issue create" notifications to [email protected]
.
The current configuration sends all issue related notifications to [email protected]
.
Can I request we turn on the "Discussions" feature for the repo? I've found that very helpful recently in other repositories and I think it's really useful alongside "Issues" when there's something to discuss that's not really an issue/bug and not concrete enough for a PR.
Sure! But... I thought that we can do this by .asf.yaml
but we can't. .asf.yaml
doesn't have the feature:
- https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Repositoryfeatures
- https://github.com/apache/infrastructure-p6/blob/production/modules/gitbox/files/asfgit/package/asfyaml.py#L276-L279
(It seems that GitHub's REST API doesn't have a feature to enable/disable "Discussions": https://docs.github.com/en/rest/reference/repos#update-a-repository )
It seems that we need to discuss this on [email protected]
mailing list and vote this on the mailing list:
https://issues.apache.org/jira/browse/INFRA-20772
Please provide a link to your email list consensus about enabling github discussions. Note that github discussion are NOT to be used for anything other than user help. As is the policy of the Foundation, all code-related discussions and project management activities MUST be reflected to an ASF mailing list. Please be sure your consensus discussion includes the above caveats.
Could you send an email to [email protected]
? I can start a vote after we get consensus of the discussion on [email protected]
.