Ted Husted wrote:
>
> "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 ;-).
Hm. Ok. I'll take a look. I didn't get that as the consensus at all (as
I saw a pretty much even split between library-as-mini-jakarta and
library-as-community-oriented-sourceforge, with the taglibs model there
as well a little. I will review the results so far...
> 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.
I am not sure adding to a file does much.
> 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.
Heh. Shouldn't we try to get *that* fixed?
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
