You should consider the approach Hadoop has taken where JIRA creates and resolves go to the dev list, but comments go to some other list (not sure which one). This makes it easy for people to see what is changing, and if they are interested in a particular JIRA when it is created, they can watch it and keep up to date. Just moving all JIRA traffic to commits will hide much of the work of the community from many potential contributors.
Alan. On Sep 9, 2011, at 4:20 PM, Konstantin Boudnik wrote: > Someone with JIRA admin karma should be able to do the switch in no time. I > think we have plenty of guys like that among the mentors of the project. > > Owen, could you redirect BigTop JIRA notification traffic from bigtop-dev@ to > bigtop-commits@ ? Or do we need to go through the official INFRA process for > that? > > Thanks, > Cos > > On Fri, Sep 09, 2011 at 04:04PM, Roman Shaposhnik wrote: >> On Fri, Sep 9, 2011 at 2:22 PM, Konstantin Boudnik <[email protected]> wrote: >>> The problem with current setup is that most ppl are likely to filter out >>> JIRA >>> traffic to somewhere (like /dev/null), but all these messages will sit in >>> the >>> archive and will simply create difficulties if someone needs to find stuff >>> later on. >> >> A strong +1. Do you know what needs to be done in order to make it happen? >> I expect it to be an INFRA JIRA but would be nice to know for sure. >> >> Thanks, >> Roman.
