Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
References: <48215E29-858C-43CB-9EF2-D599959541EE@apache.org>
 <552EE12E.90702@posteo.de>
 <CAPaJBx5WLdr8TWUbuJhQ7F=-po8vJ68Hsz5AZXF1jbgcfroAgw@mail.gmail.com>
In-Reply-To: 
 <CAPaJBx5WLdr8TWUbuJhQ7F=-po8vJ68Hsz5AZXF1jbgcfroAgw@mail.gmail.com>
From: Noah Slater <nslater@apache.org>
Date: Thu, 16 Apr 2015 11:42:32 +0000
Message-ID: 
 <CAPaJBx4fXD00PBidUFa-MYpwDqpfwSNUDwd=aW46q7UjTnTqOA@mail.gmail.com>
Subject: Re: [DISCUSSION] Move Fauxton to its own mailing list?
To: Noah Slater <nslater@apache.org>, dev@couchdb.apache.org
Content-Type: multipart/alternative; boundary=001a113cfeb09847350513d5f52f

--001a113cfeb09847350513d5f52f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I also think we need to start thinking carefully about the overhead we're
adding with all these mailing lists.

I think it's good that we've been in an expansionist phase. But there are
several downsides:

- Splitting mailing list traffic splits discussion and splits the
community, in a very real sense. Conversations become balkanised. This can
be good, but it also has the potential to be bad. We need to keep both
aspects in mind.

- Mailing lists are already pretty weird, and many people don't like them.
In that sense, adding mailing lists increases the barrier to entry for
participation in our project. And that's a very important issue we need to
consider.

On Thu, 16 Apr 2015 at 13:40 Noah Slater <nslater@apache.org> wrote:

> 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, somethin=
g
> 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_trainer@posteo.de>
> wrote:
>
>> +1
>>
>>
>> On 02/18/2015 02:34 PM, Jan Lehnardt wrote:
>> > Hey all,
>> >
>> > I=E2=80=99m wondering how you would feel to give the Fauxton team thei=
r own
>> mailing list for discussions and GitHub notifications?
>> >
>> > In my view, the Fauxton project is generating enough traffic to warran=
t
>> it=E2=80=99s own space :)
>> >
>> > I=E2=80=99d propose fauxton-dev@couchdb.apache.org
>> >
>> > Best
>> > Jan
>> > --
>> >
>>
>

--001a113cfeb09847350513d5f52f--