RE: [PROPOSAL] Committer access and responsibilities...

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > If you are a commiter - you have the same rights with all > other commiters. > If you don't want to exercise some rights - it's your choice. But it's not just about exercising rights, it's also about granting rights. At the moment, you can

Re: [PROPOSAL] Committer access and responsibilities...

On Sat, 25 May 2002, Pier Fumagalli wrote: > > If you are a commiter - you have the same rights with all other commiters. > > If you don't want to exercise some rights - it's your choice. > > Hola, you tend to forget a part I'm stressing out quite hardly... It's not > only "rights"... It's also

welcoming and nurturing volunteers

http://www.libertyforall.net/2002/archive/do-ocracy.html - Sam Ruby -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: [PROPOSAL] Committer access and responsibilities...

[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I do agree ( and I advocated for this a lot ) on lowering ( or > eliminating) the walls between projects, so jakarta commiters can commit > code in any jakarta project ( subject to the normal project rules ). > Some people didn't agree with that even

Re: [PROPOSAL] Committer access and responsibilities...

Henri Yandell <[EMAIL PROTECTED]> wrote: > > +1. > > Another example if I could. The job role of 'Java admin' is growing more > and more at companies. Developers shouldn't be adminning things, but would > you have your unix or oracle admin be the admin of the Java side with zero > Java knowledge

Re: [PROPOSAL] Committer access and responsibilities...

-1 If someone doesn't want to be involved in the voting - he can do exaclty that, abstain. If someone doesn't want to support a particular release - he can abstain from the release vote( or vote +-0 ). If you spend time and write code for a project and are willing to maintain/support - and if t

Re: [PROPOSAL] Committer access and responsibilities...

-1, its not broken, it worked. I see little reason to fix it. On Fri, 2002-05-24 at 21:11, Henri Yandell wrote: > > +1. > > Another example if I could. The job role of 'Java admin' is growing more > and more at companies. Developers shouldn't be adminning things, but would > you have your unix

Re: [PROPOSAL] Committer access and responsibilities...

+1. Another example if I could. The job role of 'Java admin' is growing more and more at companies. Developers shouldn't be adminning things, but would you have your unix or oracle admin be the admin of the Java side with zero Java knowledge? Jakarta houses the 'Java' community at Apache but th

Re: Criteria for commit access

In truthit doesn't. On Fri, 2002-05-24 at 20:18, John McNally wrote: > > > On Fri, 2002-05-24 at 17:06, John McNally wrote: > > The site docs say it can happen after 6 months of inactivity. Though I > > can't seem to find the location atm. > > http://jakarta.apache.org/site/roles.html >

Re: Criteria for commit access

On Fri, 2002-05-24 at 17:06, John McNally wrote: > The site docs say it can happen after 6 months of inactivity. Though I > can't seem to find the location atm. http://jakarta.apache.org/site/roles.html My question is how does it happen? > > john mcnally > -- To unsubscribe, e-mail:

Re: Criteria for commit access

The site docs say it can happen after 6 months of inactivity. Though I can't seem to find the location atm. My question is how does it happen? john mcnally On Fri, 2002-05-24 at 16:39, Pier Fumagalli wrote: > Andrew C. Oliver <[EMAIL PROTECTED]> wrote: > > >> > >> * Perhaps a more fruitful

Re: Criteria for commit access

Andrew C. Oliver <[EMAIL PROTECTED]> wrote: >> >> * Perhaps a more fruitful topic for us to explore is when to retire >> committer status due to inactivity. Pier is one of the few to do this >> explicitly. I have done it a bit more implicitly - including submitting >> patches to projects that

Re: Criteria for commit access

Sam Ruby <[EMAIL PROTECTED]> wrote: > Overall, my feelings on the subject are: > > * Deciding when to convert a developer into a commiter is a balance that > each project/subproject will need to determine for itself. My feeling as well... The subject of my discussion was to get somewhere else

Re: Criteria for commit access

At 18:31 24.05.2002 -0400, Sam Ruby wrote: >* Perhaps a more fruitful topic for us to explore is when to retire >committer status due to inactivity. Pier is one of the few to do this >explicitly. I have done it a bit more implicitly - including submitting >patches to projects that I am official

FW: http://jakarta.apache.org/site/cvsindex.html

FYI! :) Pier -- Forwarded Message From: Cliff Woolley <[EMAIL PROTECTED]> Date: Fri, 24 May 2002 18:33:54 -0400 (EDT) To: [EMAIL PROTECTED] Subject: http://jakarta.apache.org/site/cvsindex.html Don't know which list to send this to, but I figured you guys were probably as appropriate a

[PROPOSAL] Committer access and responsibilities...

Chatted with a lot of people, seen many, different development models, went around, asked, talked, and I believe I have a pretty decent picture, and maybe even a solution... So the major topic of discussion is that I perceive a substantial difference between being able to commit code to a CVS rep

Re: Criteria for commit access

BTW, one idea ( not mine ) would be to have a separate and private list for each project with _only_ the comitters. The proposals for new commiters should be done on that list, not on the public list. I don't know what Dan feels about this whole topic, but I wouldn't take it very well. Cos

Re: Criteria for commit access

On Fri, 24 May 2002, Sam Ruby wrote: > You hadn't qualified your statement to Tomcat, and I was just teasing about > your use of past tense. ;-) All those foreigners who can't learn the proper English grammar and spelling :-) > * Deciding when to convert a developer into a commiter is a balan

Re: Criteria for commit access

> > * Perhaps a more fruitful topic for us to explore is when to retire > committer status due to inactivity. Pier is one of the few to do this > explicitly. I have done it a bit more implicitly - including submitting > patches to projects that I am officially a committer to. > yes. I recomm

Re: Criteria for commit access

Costin Manolache wrote: > >>> If one quarter of the new commiters make 1/2 the contributions that people >>> like Sam Ruby did - I'm quite happy. >> >> As Mark Twain once said "The rumors of my demise have been greatly >> exaggerated." > > Sorry for picking your name as an example tomcat commiter

Re: Criteria for commit access

On Fri, 24 May 2002, Sam Ruby wrote: > Costin Manolache wrote: > > > > If one quarter of the new commiters make 1/2 the contributions that > people > > like Sam Ruby did - I'm quite happy. > > As Mark Twain once said "The rumors of my demise have been greatly > exaggerated." Sorry for picking y

Re: Criteria for commit access

On 5/24/02 5:28 PM, "Sam Ruby" <[EMAIL PROTECTED]> wrote: > Costin Manolache wrote: >> >> If one quarter of the new commiters make 1/2 the contributions that > people >> like Sam Ruby did - I'm quite happy. > > As Mark Twain once said "The rumors of my demise have been greatly > exaggerated."

Re: Criteria for commit access

Costin Manolache wrote: > > If one quarter of the new commiters make 1/2 the contributions that people > like Sam Ruby did - I'm quite happy. As Mark Twain once said "The rumors of my demise have been greatly exaggerated." - Sam Ruby -- To unsubscribe, e-mail: For

Re: Criteria for commit access

On Fri, 24 May 2002, Pier Fumagalli wrote: > > Right but it should be up to ya'll tomcatters to work out your standards > > amonst yerselves. Thats my only issue. > > Nope, because if I vote a committer in, I give him access to the Tomcat CVS > repo, but I also entitle him to vote for the frigg

Re: Criteria for commit access

"Andrew C. Oliver" <[EMAIL PROTECTED]> wrote: >> Andy, not everyone grew up in Texas! :) I don't eat beef anymore (you know >> mad-cow disease and smallpox in the UK) >> > Dern Europeans ain' speaking proper 'merican. Anyhow, just wait around > and you'll catch me speaking Spanish too. No esta

Re: Criteria for commit access

> > >Andy, not everyone grew up in Texas! :) I don't eat beef anymore (you know >mad-cow disease and smallpox in the UK) > > Dern Europeans ain' speaking proper 'merican. Anyhow, just wait around and you'll catch me speaking Spanish too. >>> >>> >>I do not think the PMC should intervene

Re: Criteria for commit access

> Just one question, have you ever voted -1 on a committer? (and not just to > you, but to every committer on this list). I've abstained, informally (off-list, that is) from voting, once. The guy in question had been active in a part of our project but I hadn't been following on that at all, so I

Re: Criteria for commit access

"Andrew C. Oliver" <[EMAIL PROTECTED]> wrote: >> That's what I did... I posted my -1 over there, detailed why, and I'm >> waiting for someone to write me back something about it... So far, nothing >> worth making me change my vote (meaning, nothing more than what was already >> there). > > So th

Re: Criteria for commit access

> > >That's what I did... I posted my -1 over there, detailed why, and I'm >waiting for someone to write me back something about it... So far, nothing >worth making me change my vote (meaning, nothing more than what was already >there). > So that means its vetoed...what's your beef? >No, my vote

Re: Criteria for commit access

"Andrew C. Oliver" <[EMAIL PROTECTED]> wrote: >> >> What I said was "but I believe that this group (as noted on the members >> meeting this Tuesday) is giving away committer privileges a little bit too >> easily"... I don't think that sound like "this is a resolution passed by >> members" or "thi

Re: [VOTE] New Committer Dan Sandberg

On Fri, 24 May 2002, Andrew C. Oliver wrote: > >And at large, it entitles you to have an @apache.org email address, to have > >access to our live servers, entitles you to be a part of the whole Apache > >family... > > > you're point being? I think that the point is that when you gain an @apache

RE: [VOTE] New Committer Dan Sandberg

> I'm sorry, but I believe that any time a new committer is made, > we _need_ to > put some thought in what we're "giving away", we're not just letting a guy > commit to our CVS server... +1 -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: Criteria for commit access

> > > Having said this, there is nothing wrong with discussing criteria for > proposing committers. In a conversation I had with Stefano Mazzocchi a > long time ago, he outlined the reasons for his liberal policy (for > granting commit access). I tend to oscillate between a liberal policy > and a

Re: [VOTE] New Committer Dan Sandberg

> > >What I said was "but I believe that this group (as noted on the members >meeting this Tuesday) is giving away committer privileges a little bit too >easily"... I don't think that sound like "this is a resolution passed by >members" or "this is a guideline given at that meeting"... > >To me it

Re: [VOTE] New Committer Dan Sandberg

"Leo Simons" <[EMAIL PROTECTED]> wrote: >>> I believe we deserve some explanation from the 'members', I'm >>> quite unhappy about this whole issue. If there are some new >>> quantitative standards for becoming a commiter ( or a member ) >>> we should know about. >> >> The ASF members didn't impo

Re: Criteria for commit access; was: [VOTE] New Committer Dan Sandberg

At 10:07 24.05.2002 -0700, [EMAIL PROTECTED] wrote: >On Fri, 24 May 2002, Andrew C. Oliver wrote: > > > Personally, I feel this discussion belongs solely on the tomcat list and > > is up to the committers of Tomcat to resolve. If the Tomcat community > > feels the bar should be raised, let them r

Re: [VOTE] New Committer Dan Sandberg

On Fri, 24 May 2002, Pier Fumagalli wrote: > It is of general interest (IMO) because becoming a committer entitles you > not only to a little peaceful heaven in your own little project, but > entitles you (and, frankly, obliges you) to be a part of the Jakarta > Community at large. You will be giv

Re: [VOTE] New Committer Dan Sandberg

"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > On Fri, 24 May 2002, Andrew C. Oliver wrote: > >> Personally, I feel this discussion belongs solely on the tomcat list and >> is up to the committers of Tomcat to resolve. If the Tomcat community >> feels the bar should be raised, let them raise

Re: EJB = bad = MS.net

Subject: Re: EJB = bad = MS.net From: Vic C <[EMAIL PROTECTED]> === http://www.softwarereality.com/programming/ejb/EJB_101Damnations.pdf Daniel Rall wrote: > "Aaron Smuts" <[EMAIL PROTECTED]> writes: > > >>So, I'm driven to a bit of exaggeration and overstatement at times >>especially when cri

Re: [VOTE] New Committer Dan Sandberg

On Fri, 24 May 2002, Andrew C. Oliver wrote: > Personally, I feel this discussion belongs solely on the tomcat list and > is up to the committers of Tomcat to resolve. If the Tomcat community > feels the bar should be raised, let them raise it. If they do not, then > it shall not be raised.

Re: [VOTE] New Committer Dan Sandberg

Personally, I feel this discussion belongs solely on the tomcat list and is up to the committers of Tomcat to resolve. If the Tomcat community feels the bar should be raised, let them raise it. If they do not, then it shall not be raised. I don't feel it should be up to anyone else. -Andy

Re: [VOTE] New Committer Dan Sandberg

> > I believe we deserve some explanation from the 'members', I'm > > quite unhappy about this whole issue. If there are some new > > quantitative standards for becoming a commiter ( or a member ) > > we should know about. > > The ASF members didn't impose any standard. Read my mail on _why_ I CC

Re: [VOTE] New Committer Dan Sandberg

"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > That leaves me perplexed for several reasons... > > First, it's the first time I see a commiter rejected - without any > reference to the quality and importance of his contribution, but some > new "member's" standard we don't know about. Dan put t

Re: [VOTE] New Committer Dan Sandberg

That leaves me perplexed for several reasons... First, it's the first time I see a commiter rejected - without any reference to the quality and importance of his contribution, but some new "member's" standard we don't know about. Dan put the SSI system in a decent shape, that's similar with the