Re: Creating announce@ lists by default
Nice. Thanks Marvin! On 3 July 2013 06:00, Craig L Russell craig.russ...@oracle.com wrote: Marvin, Nice work. +1 Craig On Jul 2, 2013, at 6:59 PM, Marvin Humphrey wrote: On Thu, May 9, 2013 at 7:29 PM, Noah Slater nsla...@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 mar...@rectangular.com wrote: On Sat, Mar 30, 2013 at 8:06 AM, Noah Slater nsla...@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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- NS - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- NS
Re: Creating announce@ lists by default
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 nsla...@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 mar...@rectangular.com wrote: On Sat, Mar 30, 2013 at 8:06 AM, Noah Slater nsla...@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-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- NS - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Creating announce@ lists by default
Wade might be a little OTT. ;) I think the doc is too terse, if anything. (But actually, I think it strikes the balance very well.) On 3 July 2013 17:51, Eric Johnson e...@tibco.com wrote: 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 nsla...@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/MailingListOptionshttps://wiki.apache.org/incubator/MailingListOptions http://incubator.apache.org/**guides/proposal.html#template-** mailing-listshttp://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 mar...@rectangular.com wrote: On Sat, Mar 30, 2013 at 8:06 AM, Noah Slater nsla...@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-listshttp://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.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- NS --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- NS
community graduation vote at jspwiki-dev
Hi all, a quick email to inform that we've just started the community graduation vote at jspwiki-dev :-) br, juan pablo
Permission to edit Incubator wiki?
Please allow my account AndrewPhillips to edit the incubator wiki, specifically the project reports page. Thanks! ap -- Andrew Phillips Apache jclouds - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Permission to edit Incubator wiki?
On Wed, Jul 3, 2013 at 10:18 AM, Andrew Phillips andr...@apache.org wrote: Please allow my account AndrewPhillips to edit the incubator wiki, specifically the project reports page. Done. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherd assignments July 2013
On Tue, Jul 2, 2013 at 7:23 AM, Marvin Humphrey mar...@rectangular.com wrote: Benson Marguilies Chukwa Benson Marguilies Kafka Benson Marguilies MetaModel Benson will have one fewer podlings to shepherd this month. Kafka graduated last October, but hadn't followed through on removing themselves from podlings.xml per http://incubator.apache.org/guides/graduation.html#unincubate. They were also in the wiki report template generated by clutch2report.py, but I've now removed them. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
