Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 54502BC80 for ; Tue, 10 Jan 2012 11:08:55 +0000 (UTC) Received: (qmail 41263 invoked by uid 500); 10 Jan 2012 11:00:57 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 36991 invoked by uid 500); 10 Jan 2012 11:00:34 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 36290 invoked by uid 99); 10 Jan 2012 11:00:21 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jan 2012 11:00:21 +0000 Received: from localhost (HELO mail-ee0-f47.google.com) (127.0.0.1) (smtp-auth username bdelacretaz, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jan 2012 11:00:20 +0000 Received: by eekb47 with SMTP id b47so139502eek.6 for ; Tue, 10 Jan 2012 03:00:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.14.15.214 with SMTP id f62mr7629311eef.123.1326193219176; Tue, 10 Jan 2012 03:00:19 -0800 (PST) Received: by 10.213.29.133 with HTTP; Tue, 10 Jan 2012 03:00:19 -0800 (PST) In-Reply-To: References: <20120109172226.26971i7pcqj1wwbm@www.teotigraphix.com> <20120109173928.361437o9c58j3qn4@www.teotigraphix.com> Date: Tue, 10 Jan 2012 12:00:19 +0100 Message-ID: Subject: Re: whiteboard From: Bertrand Delacretaz To: flex-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 On Tue, Jan 10, 2012 at 11:10 AM, Peter Elst wrote: >> In general I'd say everyone's welcome to touch any code as long as >> they know what they are doing - and that might include asking >> whoever's currently working on the module in question if that's ok. >> > > Maybe I'm overthinking this, but how would the original committer need to > be contacted? Does that type of thing also happen on the list to have it on > the record or do you reach out to the committer directly?.. On list - not necessarily to have it on the record, but everything happens on list ;-) > > I like the idea of everyone being allowed to touch anything, but can > imagine different people might have different goals and get in each others > way... In my Apache book the default is that I'm allowed to touch anything if I know what I'm doing and if I can reasonably expect that I'm not getting in the way of the work being done on that code. But I'm also ready to back out if someone asks me to - svn makes it easy to revert any unwanted changes, so if asked I will revert. Of course, sometimes someone will ask for a code freeze on some part of the code, or tell others that they're doing major changes somewhere and expect to be left alone for a bit, that's fine. Or we kick them out to their own branch if that gets in the way of the overall progress. I'd try to keep it simple, and address issues if/as they come up. -Bertrand