On 18/08/2005 2:45 AM, Geir Magnusson Jr. wrote:
For a codebase or module that will be part of Geronimo as a
subproject, we will :
1) Setup a parallel SVN tree for it, say geronimo/$foo/
2) It would have it's own released artifacts and independent release
cycle.
3) It would be wholly under the control and oversight of the Geronimo
PMC
4) It would have it's own webpage on the site (I imagine left nav
entry for it under a Subprojects heading)
5) All geronimo committers would have commit access to the subproject
[X ] I like this and do not wish to see a separate ACL
for new people working on the subproject, but rather
rely on trust and expect new people to work on what
they know, and engage with the rest of the codebase
though conversation and interaction with other committers,
and propose code via patches which an existing committer
can allow to be committed by the new person. Through
this mechanism of engagement and participation, a new
person would be granted permission to extend
scope of activity in the codebase.
Gianny
