Thanks for the feedback from Fluo! I didn't think about the impediments access-wise. Also there could be difficulties if the project has more than one git repository.
I guess the double-email problem is also why you moved notifications to the separate https://lists.apache.org/list.html?notificati...@fluo.apache.org I think for Apache Example (tm) (incubating) we should then use regular Jira (works out of the box) - but I guess we could mention the GH-issues alternative as well. I think for many things we will need a kind of "meta" link. Say for instance let's say example.incubator.apache.org gets a "contributing" page that says you can raise GitHub pull requests such and such. The "meta" page for this should say how this can be requested from INFRA and what kind of email notifications would happen. On 5 October 2016 at 00:51, Keith Turner <ke...@deenlo.com> wrote: > On Tue, Oct 4, 2016 at 6:43 PM, Christopher <ctubb...@apache.org> wrote: >> On Tue, Oct 4, 2016 at 6:25 PM Josh Elser <els...@apache.org> wrote: >> >>> >>> >>> Stian Soiland-Reyes wrote: >>> > On 3 October 2016 at 06:30, Luciano Resende<luckbr1...@gmail.com> >>> wrote: >>> >> +1, >>> >> >>> >> I had started something similar, at least on the website side, with best >>> >> practices and required branding items. >>> >> >>> >> Please consider adding it to the "example" project : >>> >> >>> >> https://github.com/apache/apache-website-template >>> > >>> > Brilliant - yes, that's exactly the kind of thing I mean! You've >>> > already got a great Community page there: >>> > >>> https://github.com/apache/apache-website-template/blob/master/site/community.md >>> > >>> > >>> > So - how do we proceed? I suggest to use the [EXAMPLE] tag on this >>> > list as there could be a couple of things we need to agree (not >>> > discuss!) what best practice actually is. >>> > >>> > Do we need an IPMC vote? >>> > >>> > We need to request from infra something like: >>> > >>> > git repository incubator-example >>> > - w/ pull request sync to general@incubator ? >>> > >>> > Jira (or brave: GH issues? Fluo can inform us) >>> >>> As far as I know, after we got everything set up (which, admittedly, I >>> think was more tricky because pre-ASF "fluo" was already on Github, code >>> and issues), GH issues have been smooth-sailing. As long as you're OK >>> with closing issues via git commit message, anyways :) >>> >>> >> Closing issues with FF merge or git commit message isn't a big deal, but >> the biggest issue with using GH issues at ASF is the lack of ability to use >> labels/milestones for issue-tracking/planning. Some of that can be done > > Nothing new to add, just want to reinforce how much of an impediment > this is. Not being able to utilize GH labels and milestones is really > suboptimal for coordination and planning purposes. Can't mark issue > as bug or feature, can't set its projected fix version, can't easily > see what issues were fixed in a version, etc. > >> manually with Wiki/mailing list, but it's kind of a pain. There can also be >> a lot of duplicate spam to users if they subscribe to GH issues, and then >> also subscribe to the mailing lists for activity notifications. >> >> >>> > git repository incubator-example-site >>> > (alternatives: apache/apache-website-template as-is; site/ folder in >>> > incubator-example repo) >>> > >>> > http://example.incubator.apache.org/ >>> > - and corresponding git2pub >>> > >>> > >>> > I am not sure about separate mailing list (who would sign up?) >>> > although we can fake that on its mailing list page. >>> > >>> > >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- Stian Soiland-Reyes http://orcid.org/0000-0001-9842-9718 --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
