"Geir Magnusson Jr." wrote:
> Why?  Why not let packages be the 'project' and let them run themselves?

Looking over the responses to the round 1, 

< http://husted.com/about/jakarta/lib002.htm >

it was my feeling that the consensus leaned toward the "Taglibs" model.
Committers have access in fact, but practice discourages people form
running in and hacking a codebase you haven't worked on. And, after all,
we do have the CVS to help protect us from ourselves ;-).

We are modifying the Tabligs model slightly, in that we are asking the
active committers to a package list themselves in the status file.
Again, reinforcing that working on a package is a commitment, and not a
casual hack, and that each package is an entity unto itself.

This also eliminates the overhead of a person with sufficient clearance
(like Brian B) being bothered every time we need to upgrade someone's
access.

-Ted.

Reply via email to