Nice feedback all around. Here is a version that includes some of these thoughts: --
Dear fellow committers, The Apache Commons Team is pleased to announce that write access to the Apache Commons Subversion and Git repositories has been granted to all ASF committers. Apache Commons is an Apache project focused on all aspects of reusable Java components. As such, the components maintained by the Apache Commons project may be of interest to a variety of other Apache projects. The Apache Commons community would like to invite you to share and maintain useful code. While Apache Commons is a Commit-Then-Review community, we would consider it polite and helpful for contributors to announce their intentions and plans on the dev mailing list before committing code. Have fun, The Apache Commons Community. -- Gary On Sun, Dec 14, 2014 at 3:13 PM, Gilles <gil...@harfang.homelinux.org> wrote: > > On Sun, 14 Dec 2014 12:57:02 -0700, Phil Steitz wrote: > >> On 12/14/14 12:49 PM, Gilles wrote: >> >>> On Sun, 14 Dec 2014 20:28:37 +0100, Benedikt Ritter wrote: >>> >>>> Hi all, >>>> >>>> here is my draft for the announcement to committers@ >>>> >>>> Regards, >>>> Benedikt >>>> >>>> ------ >>>> >>>> Dear fellow committers, >>>> >>>> the Apache Commons Team is pleased to announce that write access >>>> to the >>>> Apache Commons SVN and git repositories has been granted to all ASF >>>> committers. >>>> >>>> Apache Commons is an Apache project focused on all aspects of >>>> reusable Java >>>> components. As such the components maintained by the Apache >>>> Commons project >>>> may be of interest for a variety of other Apache projects. >>>> >>>> The Apache Commons community would like to invite you to share >>>> useful code >>>> which may be useful for other projects as well. >>>> Please let us know before you start working on the code, by >>>> writing a short >>>> mail to the dev mailing list [1]. >>>> >>> >>> I'd be more careful (better safe than sorry) and add something like: >>> >>> [...] before committing code, consensus about the modifications >>> should be >>> reached on the dev ML. >>> >> >> We are CTR so that is not necessary. We might just want to refer to >> and update [1]. >> > > IMHO, it is more efficient to discuss first (with the assumption that > no objection amounts to green light). > > The upshot there is that before starting to commit >> to a component, it is polite to announce intention to start working >> on it and let people know what you have in mind. >> > > In the same vein, it is more polite to ask first whether there is an > objection). > It is also nicer, for all parties, to not have to veto a commit. > > > Gilles > > > > Phil >> >> [1] http://wiki.apache.org/commons/CommonsEtiquette >> >>> >>> >>> Thanks, >>> Gilles >>> >>> >>>> Benedikt Ritter, >>>> on behalf of the Apache Commons community >>>> >>>> [1] http://commons.apache.org/mail-lists.html >>>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
