On Wednesday 30 January 2008 15:24, Mark Slee wrote: > What we'd really > like to set up here is a system where there are different people with > committer priveleges to different parts of the project.
Hmmm... I would oppose this for two reasons; 1. Creating boundaries within a project, yet collaborate on the PMC level seems odd to me. Either people are entrusted within the project (committer rights) or they are not (no committer rights). If you think that a Thrift Java programmer will mess up the Ruby Thrift code, then you have bigger problems to deal with, IMHO. 2. Some people will eventually become fluent in more than one of these. Are you now going to start a VOTE on granting access to such member to another part of the project? Who is to decide that? The people involved in that language only or the whole PMC (ignoring for a fact that ASF has rules for this)? I can't see it work in practice. So if you drop that idea, I can vote in favour of incubating this project. Cheers -- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
