Proposal for change to repository governance

[Colin Clark]

Hey,

On 15-Jun-09, at 12:32 PM, Anastasia Cheetham wrote:

>> 2. A space for incubated projects. This is a place for growing code  
>> that we expect to some day include in our releases. Anyone can ask  
>> for commit access to this space, and will be paired with a current  
>> committer as a mentor. Code reviews will be a requisite part of  
>> the  incubation process, and we'll expect a growing standard of  
>> quality over time.
>
> As the standard of quality grows in this space, what happens to  
> commit access? Do we at some point switch over to the "fully  
> governed by all the familiar coding and commit standards used so  
> far" approach? Or so we move the code out of the "incubation" space  
> into the "current, shipping" space? And how do we decide when this  
> should happen?


Good question. It's expected that code in the incubation space will be  
moved into the main repository when it's reached a level of maturity.  
Along with this, our governance of the incubation space is  
specifically intended to nurture new contributors into full-fledged  
committers. I imagine that in many cases, the contributor will be  
nominated for commit access when their code is promoted.

But these two issues don't have to be tied together: if necessary,  
code may be promoted without giving the contributor commit access, or  
vice versa. It'll depend on the situation.

Does that seem reasonable?

Colin

---
Colin Clark
Technical Lead, Fluid Project
Adaptive Technology Resource Centre, University of Toronto
http://fluidproject.org