Jeffrey Dever wrote:
I am not excited by the idea of only PMC members voting on releases to
the exclusion of active committers. I'm the release prime for Commons
HttpClient where all committers vote on all issues all the time,
including releases. HttpClient is somewhat unusual in commons as it is
rather a large project with a dedicated mailing list and a rich family
where many, such as myself, are primarily focused on just one project,
HttpClient.
The goal is to make all active committers PMC members.
I am quite happy with how things are going right now. Our contributor
base continues to grow and we are back to doing releases (hurray). We
are using maven to build, have factored out some services into the Codec
subproject and are looking to factor out URI into a new subproject. We
have over 250 Junit tests, are using commons-logging and have reached
critical mass to support our own votes according to Jakarta guidelines.
Some complain at our isolation, but I see this as desirable given the
size of the codebase and the volume of email traffic (approx 400/month).
Of course we have an open door policy and have good connections to those
projects that are connected to HttpClient, such as Slide, Cactus and
othes both inside and ourside of Apache.
This works well when things go well. When things go wrong, who is
accountable?
To quote the quote of Sam, "Jakarta ... becoming a single community". I
like the sound of this, but please consider that communities are
composed of families that a) are all members of the community, b)
interact more frequently with their own family members than others in
the community, c) may or may not share culture and d) a single family
has differing relationships between families.
Different families should become different projects. Ant, Avalon,
Cocoon, James, WebServices, DB, ... are all examples of this happening.
HttpClient has all the characteristics of a family in a community. I
don't want to see this relationship disrupted by taking voting power
away from the family representitives, the committers.
Semantics. The PMC for a project is the ones that make release
decisions. Either make HttpClient a project, or have the active
committers for the project join the PMC.
I have not shown interest in the PMC up untill now, but it sounds like
my family is at risk, and I'm concerned. In general, I just want to
write code and progress HttpClient (of which I don't really have time
for even this, but I like it so much I make time). I don't appear to
have been nominated (or have just shown up on the list like Stephen) but
I am eligible (committer, release prime and active for 10 months).
Should I be seeking a seat on the PMC?
Yes.
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
