You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Bruno P. Kinoshita" <ki...@apache.org> on 2021/04/25 22:14:30 UTC
[IMAGING] Adding .asf.yaml
Hi all,
I've created a PR to add .asf.yaml to Commons Imaging. The PR includes only basic GitHub project information such as description (from pom.xml), URL to Commons Imagnig component page, and these labels: [java, image, imaging, image-processing]
The .asf.yaml docs [2] state
>When using a feature in .asf.yaml, make sure that you have discussed what you propose with the entire project first, and have understood what the configuration changes will do to your (and the team's) workflow and project resources.
I think features such as changing how notifications work, branch locking, enabling GH pages/wiki/issues/etc. deserve a longer discussion here first (if anyone wants to use these features, of course). But I'm assuming adding only description/URL/labels to GitHub as I've done in that PR should be OK?
I'll leave the PR open until Friday NZ time anyway in case anyone disagrees with the PR. I'm adding it so users looking for things like "image-processing" labels in GitHub find the project. (I thought about it after looking at Python's pillow, clicking on image-processing, filtering by Java, and realizing commons-imaging wouldn't show in that list…)
Cheers
Bruno
[1] https://github.com/apache/commons-imaging/pull/141
[2] https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-BranchProtection
Re: [IMAGING] Adding .asf.yaml
Posted by sebb <se...@gmail.com>.
On Sun, 25 Apr 2021 at 23:14, Bruno P. Kinoshita <ki...@apache.org> wrote:
>
> Hi all,
>
> I've created a PR to add .asf.yaml to Commons Imaging. The PR includes only basic GitHub project information such as description (from pom.xml), URL to Commons Imagnig component page, and these labels: [java, image, imaging, image-processing]
>
> The .asf.yaml docs [2] state
>
> >When using a feature in .asf.yaml, make sure that you have discussed what you propose with the entire project first, and have understood what the configuration changes will do to your (and the team's) workflow and project resources.
>
>
> I think features such as changing how notifications work, branch locking, enabling GH pages/wiki/issues/etc. deserve a longer discussion here first (if anyone wants to use these features, of course). But I'm assuming adding only description/URL/labels to GitHub as I've done in that PR should be OK?
Proposed changes look OK to me.
I agree that any other changes require prior discussion.
> I'll leave the PR open until Friday NZ time anyway in case anyone disagrees with the PR. I'm adding it so users looking for things like "image-processing" labels in GitHub find the project. (I thought about it after looking at Python's pillow, clicking on image-processing, filtering by Java, and realizing commons-imaging wouldn't show in that list…)
>
>
> Cheers
> Bruno
>
>
> [1] https://github.com/apache/commons-imaging/pull/141
> [2] https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-BranchProtection
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org