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
It is not "to the exclusion" of active committers. Http-client is part of jakarta-commons - and acording to the charter any jakarta-commons committer ( which is close to all jakarta ) can vote. As you probably know - only those who are really interested do that. I agree that we're not yet ready to have PMC votes on releases - we need to expand the PMC and include more people. Even when this will happen, I think the committer votes should be counted as well. At least for jakarta-commons - the difference will be insignifiant. > The new group of committers has really risen up out of the ashes of the > old HttpClient which became quite idle over the first half of last year. > These new committers are what makes HttpClient move forward, and I > cringe at the thought of taking some, any, responsibility away from > them, away from us. Think of this in terms of a larger "us". By beeing part of jakarta-commons, http client is already a part of a very large "us", almost as wide as jakarta. In all cases - the responsibilty stays with the people who chose to be involved. That can include jakarta PMC ( most of the pmc is already committer on jakarta-commons anyway - so that means absolutely no change). As active http client committers join the PMC - they'll be able to assume more responsibility. Costin > > 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. > > There have been transitional pains, and growing pains, but all in all, I > would say that HttpClient is a very healthy project. > > 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. > > 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. > > 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? > > Jeff (Jandalf) Dever. > HttpClient 2.0 release prime. > > > Conor MacNeill wrote: > >> Stephen Colebourne wrote: >> >>> Unless I am mistaken, being a PMC member implies an overseing role >>> for the >>> whole of jakarta, >> >> >> No, not quite, IMHO. The PMC as a *whole* has an oversight role for >> the whole of Jakarta but individual PMC members do not need to oversee >> all of Jakarta. In fact this is the nub of the reorg issues which have >> been floating around. AIUI, the 7 member PMC approach was felt not to >> be able to adequately cover all of Jakarta and the PMC must grow to >> adequately provide oversight. Eventually most consistently active >> committers will join the PMC. This is the httpd model, for example. >> Sam is moving from where we have been to that point in a series of steps. >> >>> a requirement to follow PMC issues and votes and to be a >>> manager. Whilst the concept of being able to push forward jakarta, JSRs, >>> make decisions etc is appealing, I do not believe that I have the time >>> available to do the job. Hell, I already lack the time to fully >>> oversee the >>> commons-lang, commons-collections and commons-clazz projects that I am >>> involved with as I would like :-) >> >> >> If you are providing oversight of these projects, even to the extent >> you have time available, you are already filling one of the roles of a >> PMC member. If you have acted as a release manager, then you have >> performed a purely PMC role. All releases of Jakarta sub-projects must >> be approved by the PMC. This isn't something that has been done in >> Jakarta to date, really, but will be increasingly the case as the PMC >> expands. To quote Sam >> >> "Longer term, the plan is to move the subprojects that chose to remain in >> Jakarta towards becoming a single community - in particular release >> votes will become a responsibility of the PMC. That does not mean that >> all PMC members will vote on all releases, but that it will be from this >> pool of members that release votes will be cast. Clearly there will >> need to be a number waves of additions like the one above to the PMC >> before we get to this point." >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
