couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Shorin <kxe...@gmail.com>
Subject Re: [PROPOSAL] Move transactional email out of dev@
Date Mon, 16 Mar 2015 13:20:51 GMT
On Mon, Mar 16, 2015 at 4:08 PM, Jan Lehnardt <jan@apache.org> wrote:
>> On 16 Mar 2015, at 14:00, Alexander Shorin <kxepal@gmail.com> wrote:
>>
>> +1 for JIRA
>> -1 for GitHub
>> I think we need another ML for PRs and related conversation there OR
>> somehow automagically add all the committers to watchers list on
>> GitHub of our projects to let them receive notification by using
>> GitHub system. People how don't want to follow all the projects may
>> unwatch those manually. But commits@ isn't the place where you should
>> go for the PRs without MUA filters while PRs isn't a thing to receive
>> lack of attention.
>
> Can you make a concrete proposal e.g. “emails so and so should go to foo@c.a.o”?

I'm not sure that they should since I have multiple views on this:

1. GitHub notification remains on dev@.
Pros:
- Everyone reads the dev@;
- You can participant in GH discussion by replying on related the email;
- Nothing need to do;
Cons:
- It's automatically generated email;
- Not at all people are interested in all our subprojects (fauxtoners
may'd like to receive www- related mails, but www- folks unlikely
would be interested in fabric changes etc.);

2. Move GitHub notifications to gh@ ML.
Pros:
- Less noise on dev@;
Cons:
- If you're not subscribed on gh@ and doesn't watch project on GitHub,
you could easily miss the notification about pull request;

3. Disable GitHub emails at all on ASF MLs, add all the folks as
watchers of all our subprojects and let them unscribe from those they
don't like to follow.
Pros:
- Everyone follows things they likes;
- No Pull Requests lacks of attention (theoretically);
- No automatically generated emails;
Cons:
- All the related conversation happens not on ASF baseground, but GitHub one;
- Daniel will be sad;

Not sure which one is the best since it's very depends on overall
people workflow and ASF rules.

--
,,,^..^,,,

Mime
View raw message