I'm not opposed to the idea, but we do A LOT of communication via JIRA and Review Board, and my fear is that relegating these automatically generated emails to a separate list will cause people to miss the *actual*conversation that's going on. I don't like the idea of having the conversation in too many places, e.g., on the mailing list, and on Review Board, and on JIRA!
Given that we are keen to take advantage of tools like JIRA and Review Board my intuition is that any truly active contributor/committer will want to be reading both of these streams as though they are one stream. This has at least been my take on why we haven't separated JIRA and Review Board emails out before. Of course, it's very easy for me (and others) to subscribe to multiple lists. But it's also easy for people to filter emails that contain "Review Request:" or "[jira]". So I think the question comes down to what do we want to optimize for? Would we prefer to have some documentation someplace that explains to new developers that they need to sign up for these extra mailing lists (which they'll possibly miss if they just join mesos-dev@) or do we want to expose the use of these tools as a first class part of our development? On the flip side, it would be great to encourage more communication on mesos-user@. On Thu, Feb 28, 2013 at 10:14 AM, Vinod Kone <[email protected]> wrote: > I like this idea. Though I'm not sure what is the Apache way. > > > @vinodkone > > > On Thu, Feb 28, 2013 at 10:07 AM, Adam Monsen <[email protected]> wrote: > > > Currently mesos-dev is a mix of hand-typed emails and automated emails > > (from Review Board, Jenkins, and JIRA). > > > > I propose redirecting all automated ("this happened in tool x") emails > > to a separate mailing list, perhaps "mesos-auto" or "mesos-notification". > > > > This would make it easier to follow hand-typed email discussions > > directly between humans, while retaining the ability to follow all > > automated emails by subscribing to the other mailing list. > > > > Thoughts? > > > > >
