incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marvin Humphrey <>
Subject Re: Creating announce@ lists by default
Date Wed, 03 Jul 2013 01:59:23 GMT
On Thu, May 9, 2013 at 7:29 PM, Noah Slater <> 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.

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 <> wrote:
>> On Sat, Mar 30, 2013 at 8:06 AM, Noah Slater <> 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:
>> 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:
>> For additional commands, e-mail:
> --
> NS

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message