Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAJNb-9qPM+4W6vjs7Cwv0+jms=srk57psQ-_8DkdQ1U5x_sOjQ@mail.gmail.com>
References: 
 <CAPaJBx4iUwTOBUjpVyBs+q8TO=c+__D5ui3n1UZmC-G4Sga47A@mail.gmail.com>
	<731E2379-0031-4137-ABB4-78914713EF8C@apache.org>
	<CAJ_m3YDp36_058qcMQ42mf6VStS6v+1gSUDeB+jHGo4fB2Tv8A@mail.gmail.com>
	<65A80E2D-0742-4C12-9671-2BA4B8ED477E@apache.org>
	<CAJNb-9rW=e6M6C5rFwd5ESsWFEXDQVzoE_9OBpAXTkEQ+BPQKg@mail.gmail.com>
	<CAPaJBx7V6F2dg+Fc5xJfdEV0b1k=bRx3oAxkw8cZE=5imoFW_A@mail.gmail.com>
	<CAJNb-9ptArN77D9Aq70B-shh8upC+d3MmAKNn4x1oDO_tP4z=w@mail.gmail.com>
	<CAPaJBx547=-FTF1bzF_yoQDUbKtdhzVRbC3Z5+c1UVsgeyjPeQ@mail.gmail.com>
	<CAJNb-9qgiMdXeQ4EK07nDcz=5qTXEbLQSaRbWMjjv5x5fj8PjQ@mail.gmail.com>
	<04890552-61B6-468B-B5F4-73B024604DFB@apache.org>
	<CAGg-Cd6cKvcrad9sOrgpbL_x_O=Y3YkM2sqRzTgeVGX8gMKZGQ@mail.gmail.com>
	<CAAL6JQh9Ckv=TkJ4VuD4ZA8eB-8FRMidfVOb6_4PqxRSBv2piQ@mail.gmail.com>
	<763501E5-437F-4580-A6F7-31C07A33E529@apache.org>
	<CAJNb-9o1iF-EiEPxCSBEp2KaYy56fxuaoJKk6PXwEMPkn3AhZg@mail.gmail.com>
	<33F5D5E8-1913-495F-9442-AEF0BA2A6A84@apache.org>
	<CAJNb-9qPM+4W6vjs7Cwv0+jms=srk57psQ-_8DkdQ1U5x_sOjQ@mail.gmail.com>
Date: Sun, 17 Mar 2013 13:19:45 +0000
Message-ID: 
 <CAPaJBx5eW=-2NkXKxM9YOqMReoFAuxyQ6JeKvcFWukhbT_G3_A@mail.gmail.com>
Subject: Re: [DISCUSS] Send Github new comment notifications to the dev list
From: Noah Slater <nslater@apache.org>
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=bcaec5171b6de3aaca04d81eb906

--bcaec5171b6de3aaca04d81eb906
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Benoit, you have previously voted +0 on this. Are you changing your
position?

Jan has repeatedly stated that he will personally take care of taking
comments made on the mailing list to the Github thread, until an technical
system is in place to automate that.


On 17 March 2013 13:12, Benoit Chesneau <bchesneau@gmail.com> wrote:

> On Sun, Mar 17, 2013 at 5:50 AM, Jan Lehnardt <jan@apache.org> wrote:
>
> >
> > My proposal includes that nobody is forced to use GitHub. All discussio=
ns
> > can happen without ever touching GitHub now and in the future. My
> proposal
> > was designed to take this into account. Please stop bringing this up as
> > an argument against the proposal to send GitHub comments to dev@.
>
> Is this thread read-only too ?
>
> This is were is the issue in the proposition, it doesn't solve the
> problem of the pr. We need to make sure that the ml is the main hub.
> We can't just put out a partial solution because the balance will be
> in disfavour of the apache ml:
>
> subscribed to apache
> 1. can read the comments
> 2. can't write to github
>
> subscribed to github & apache
> 1. can read
> 2. can answer to github
>
> And we all know (because of the "social" nature of github) that the
> moment we do that some will use more and more github and at the end
> won't use anymore the means inside the apache foundation. and until
> wee find a solution for the other way some people won't be able to
> interact any more.  We aren't here to favourite one kind of users.
> What do we do for others, do we also add their systems? What do we do
> for companies that can't for any reasons use github?
>
> So my point is that if we go for this solution (and if it's legally
> acceptable) we must go with the complete solution, not a partial. Ie
> we should have r/w the moment we start it. Not *eventually* later.
>
> - beno=EEt
>


--=20
NS

--bcaec5171b6de3aaca04d81eb906--