On Tue, Jan 10, 2012 at 11:10 AM, Peter Elst <peter.e...@gmail.com> 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
