Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of randall.leeds@gmail.com
 designates 209.85.219.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <7F425845-5281-4C69-8AE9-DA76014E618D@apache.org>
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>
	<7F425845-5281-4C69-8AE9-DA76014E618D@apache.org>
Date: Sun, 17 Mar 2013 20:28:50 -0700
Message-ID: 
 <CAAL6JQi_QC0o70rs6JE602vmieyhnfkJA4W=5qDsPW9a=6S9FA@mail.gmail.com>
Subject: Re: [DISCUSS] Send Github new comment notifications to the dev list
From: Randall Leeds <randall.leeds@gmail.com>
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Content-Type: text/plain; charset=UTF-8

On Sun, Mar 17, 2013 at 6:34 AM, Jan Lehnardt <jan@apache.org> wrote:
>
> I consider this an edge case that I, again, am happy to find a technical
> solution for. Until then, I do it by hand. Making automatic two-way-sync
> a blocker seems overly zealous to me, when the whole idea is to get info
> to dev@ that is currently not on dev@ and clearly harms the visibility
> of the dev efforts of the project today (and as Noah points out for the
> past 24 or so months).

Automating this would be great and I would use it elsewhere. I wish
github had this built in.

> And now that we are bringing this up we get all sorts of FUD how this
> is bad and I fail to understand why getting relevant data to dev@ is
> in anyway bad and should not be implemented because there is some more
> automation to be done.

I agree that it's not a blocker to have only one way.

Plenty of projects use Github to coordinate development and still have
need for a mailing list. GIthub will not come to dominate dev@. As
long as we, eventually, deliver 2-way sync, we ensure that no one is
barred from contributing to the bulk of conversation.

This is a fun problem, but arguing about it isn't.

+1 on PRs to dev@
+1 on Jan taking point to deliver 2-way
-0 on him doing it manually for any period of time. Don't do this
unless you want to :).