Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of eric@tibco.com designates
 63.100.100.143 as permitted sender)
Message-ID: <51D45677.7040900@tibco.com>
Date: Wed, 3 Jul 2013 09:51:03 -0700
From: Eric Johnson <eric@tibco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: <general@incubator.apache.org>
Subject: Re: Creating announce@ lists by default
References: 
 <CAPaJBx4cf-r1Dk0n1xn+f+9L8LH37Ky49DEyroe2wt1-o_+Fxg@mail.gmail.com>
 <CAGU5spc8Vsj6kBkqesD_ZuySUSd0TeN=1JyqmLDhdMObyneveQ@mail.gmail.com>
 <CAPaJBx6gNN0vCnEDh1vxp4J0nu8AaCS+kKKo3fKTYqt_75b4KA@mail.gmail.com>
 <CAOGo0VaporqEE6-6hCkSEn_pKVX=tDxcBVkO_fYMbJQZH3E3YQ@mail.gmail.com>
 <CAPaJBx5BQyS3bEqPu8AzksWzA5Fw3z0xh_uc=LTmVQj+mWLNEA@mail.gmail.com>
 <CAGU5spdEj4Lxc3eHyvFs-h-0y73DtOwThjZZ6ACZGDB6pZL=Gw@mail.gmail.com>
 <CAGU5spd1eNYTqLUWLE2C1=tnz8EJ-C_yqCCNQ1M-V7cAJ_wG3Q@mail.gmail.com>
 <1364409433.69713.YahooMailNeo@web28903.mail.ir2.yahoo.com>
 <CAPaJBx4AObG3wmQzQxDKT9k029BjBvmrcMTJR04CHuSnNfNPkQ@mail.gmail.com>
 <CABD8fLW3Sb9tTU=0OFfmZsPSgTwbT=sUK-e1FYRVqU06W+LnpA@mail.gmail.com>
 <CAPaJBx5R_Pq31Yf2UrZQCxJviUV-iL9+0j2joSdMhajm_fs=iw@mail.gmail.com>
 <CAAS6=7hftBpDu9cCp8vuSWz2O_bpfqfRimH-O1ND2V4UprcFCQ@mail.gmail.com>
 <CAPaJBx6nbQTcUW31aSLq2wwqYioOZ6vH-naTaEtCdX=c-StG7w@mail.gmail.com>
 <CAAS6=7gGmdSASmLrOJwuS-t13gEw1JCpwrpha9eGCCqAhmo50w@mail.gmail.com>
In-Reply-To: 
 <CAAS6=7gGmdSASmLrOJwuS-t13gEw1JCpwrpha9eGCCqAhmo50w@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

My one suggestion would be to group all the historical 
patterns/commentary at the end of the document. That way, people looking 
for specific information about current practices will not have to wade 
through historical information.

Eric

On 7/2/13 6:59 PM, Marvin Humphrey wrote:
> On Thu, May 9, 2013 at 7:29 PM, Noah Slater <nslater@apache.org> wrote:
>> Hey Marvin,
>>
>> Did you get anywhere with this?
> Finally, yes.  I've written up the subject on the Incubator wiki and linked to
> it from the proposal guide.
>
>    https://wiki.apache.org/incubator/MailingListOptions
>    http://incubator.apache.org/guides/proposal.html#template-mailing-lists
>
> I'm having second thoughts about where it should live permanently, though.
> The Incubator's documentation could withstand some reorganization and I'm
> contemplating some proposals which I'll put forth in a little while.
>
> Marvin Humphrey
>
>> On 30 March 2013 15:39, Marvin Humphrey <marvin@rectangular.com> wrote:
>>
>>> On Sat, Mar 30, 2013 at 8:06 AM, Noah Slater <nslater@apache.org> wrote:
>>>> Thanks Greg. Sane advice. I'll add this to my todo list and see if I can
>>>> come up with a patch for the docs.
>>> The obvious place to patch is the descriptive paragraph here:
>>>
>>>    http://incubator.apache.org/guides/proposal.html#template-mailing-lists
>>>
>>> However, I question whether decisions about mailing lists should be made by
>>> the small group that typically works up a proposal.  Why not start off with
>>> just a dev list and have the entire community participate in discussions
>>> about what additional mailing lists to add?
>>>
>>> *   Do we need a user@ list yet?
>>> *   Where should commit notifications be sent?
>>> *   Where should issue tracker notifications be sent?
>>> *   Should we add an announce@ list?
>>>
>>> These questions all have interesting implications with regard to community
>>> dynamics, and I think it would benefit podlings to be considering them
>>> early on.
>>>
>>> So, I'd like to propose a page describing the various mailing list choices
>>> that top-level Apache projects have made and the tradeoffs, which I
>>> volunteer to write and which I think ought to live on community.a.o rather
>>> than incubator.a.o.
>>>
>>> Once that page is live, I propose that we modify the proposal template so
>>> that the default is only a dev list.  Mailing list expansion then becomes
>>> part of the incubation curriculum, along with code import, header change,
>>> preparation of a release management procedure, making a release, recruiting
>>> new contributors/committers/PMC-members, and so on.
>>>
>>> Marvin Humphrey
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>> --
>> NS
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org