Ted Husted wrote:
>
> "Geir Magnusson Jr." wrote:
> > Isn't that one of the basic principles of this whole thing, letting
> > small components be managed as standalone project entities under the
> > umbrella of a Jakarta library project? Isn't that why getting the
> > committer model right has been such an issue? It certainly has been what
> > I have been trying to say now for weeks.
>
> This would be a good time to submit a patch to the draft proposal, to
> give us something to vote on.
A patch? Ya, sure. I have been iterating on these points for two weeks
and it's a patch, like this is something new or that we forgot?
I'll be happy to offer a patch :)
> In general, we've proposed the taglibs model, extended to include an
> active committer roster in each package's status file, and a combined
> user/dev list for each package.
>
> In the draft proposal,
>
> < http://husted.com/about/jakarta/lib005.htm >
Could you start making new versions of this document whenever you add
anything new? I keep thinking it's a specific version, but as I read
below, I think there are new points that have been added since the last
time I tried to bring up the committer model as an issue. (Thursday?)
> the committer model is expessed at
>
> 4.3 Each package must maintain a list of its active committers in its
> status file.
I am not sure if it was labeled 4.3 last time, but I keep bringing this
up as pointless except for giving credit where credit is due - otherwise
CVS can certainly tell you who committed what to where.
I guess I should give up.
> 14. Volunteers become committers to this subproject in the same way they
> are entered to any Jakarta subproject. Being a committer in another
> Jakarta subproject is not a prerequisite.
>
> 15. Each committer has karma to all the library packages, but committers
> are required to add their name to a package's status file before their
> first commit to that package.
See above.
> 16. The library committers shall elect a committee of three committers
> to provide general oversight, in the style of the Jakarta PMC.
>
> 17. New packages may be proposed to the library general list, and voted
> on by all subproject committers. To be accepted, a package proposal must
> receive a positive super-majority vote of the library
> committers. Proposals are to identify the rationale for the package, its
> scope, its interaction with other packages and products, the Commons
> resources, if any, to be created, the initial source from which the
> package is to be created, and the initial set of committers.
You still keep talking about packages. This appears to be no more than
'cvs add <dirname>; cvs commit' whereas I keep thinking of the granular
bits as being more than that.
> 17.1 The whole number of +1 votes needed for a super majority is
> calculated by dividing the total number of active subproject committers
> by four, multiplying by three, and rounding to the nearest whole number
> (>= .5 rounds up).
>
> 19. Anyone may propose a new package to the library, and list themselves
> as the initial committers for the package. The vote on the proposal is
> then also a vote to enter new committers to the subproject as needed.
>
> -Ted.
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
