I thought we'd already discussed moving this stuff to another list. See "[PROPOSAL] Move transactional email out of dev@" sent around this time last month.
The last email on that thread was me suggesting we kick off a DISCUSS thread. My proposal was: > I am +1 for GitHub PRs moving to something like reviews@ Joan added that she wants to have a monthly reminder sent to dev@ about where this traffic is going. Other people then suggested this ML handle JIRA traffic too. Your proposal in this thread is to move JIRA *and* GitHub to code@, which echos that. Though I think if we're sending all this stuff here, something like automated@ is more accurate. It's not clear to me that we have consensus on bunching up all automated emails and moving them to a new list. As I see it, that is one option. Another option is to split it by source, so one for GitHub, one for JIRA, etc. Any others? On Thu, 16 Apr 2015 at 00:08 Klaus Trainer <klaus_trai...@posteo.de> wrote: > +1 > > > On 02/18/2015 02:34 PM, Jan Lehnardt wrote: > > Hey all, > > > > I’m wondering how you would feel to give the Fauxton team their own > mailing list for discussions and GitHub notifications? > > > > In my view, the Fauxton project is generating enough traffic to warrant > it’s own space :) > > > > I’d propose fauxton-...@couchdb.apache.org > > > > Best > > Jan > > -- > > >
