El lun, 30-01-2006 a las 21:46 +0100, Michael Wechner escribió: 
> Thorsten Scherler wrote:
... 
> >>>Please, we really need to do the releases. 
> >>>
> >>>Somebody want to do this (we all will help)?
... 
> >>>
> >>what about that every two months somebody else will be doing this.
> >>(which we can write into the plan --> Wiki)?
> >>
> >>resp. that each committer will do it once
> >>
> >>I would volunteer to be the first ... ;-) but only if everyone will help
> >>to pull the wagon, whereas Gregor and Rolf could be postponed after 
> >>everyone else
> >>will have made a release, because they already did so.
> >>
> >>If committers don't want to, then I think they should retire ...
> >>
> >>WDYT?
> >>    
> >>
> >
> >Please, never forget we are working here in an open source project. 
> >
> >One has to *volunteer* for being RM not because it is your turn.
> >
> >I think we cannot expect that somebody *has* to do anything in this
> >project! 
> >  
> >
> 
> I am not forcing anyone ;-)

You wrote: "If committers don't want to, then I think they should
retire ..."

Like you said in the former thread: 'perception is often 
the "truth".'

> 
> >We all are volunteers, doing what we can and want, not because we were
> >told to. Further if you volunteer then you cannot attach restrictions on
> >it (that contradict the word "volunteer").
> >  
> >
> 
> why not? It doesn't contradict anything.
> 
> >Asking somebody to do something or otherwise "they should retire" is not
> >how volunteers like to be treated. That is not how an open source
> >project works. Worst case is that all committer will retire. 
> >  
> >
> 
> not if one is active. 

One can be active in many areas of lenya *without* doing a release. 

http://forrest.apache.org/committed.html#copdoc 
"The foundation of a project and how the community contributes to it is
known by the acronym CoPDoC: 
      * (Co)mmunity - one must interact with others, and share vision
        and knowledge 
      * (P)roject - a clear vision and consensus are needed 
      * (Do)cumentation - without it, the stuff remains only in the
        minds of the authors 
      * (C)ode - discussion goes nowhere without code"

http://forrest.apache.org/committed.html#becoming
"There is nothing at The Apache Software Foundation that says you must
write code in order to be a committer. Anyone who is supportive of the
community and works in any of the CoPDoC areas is a likely candidate for
committership.

Apache is a meritocracy. That is, once someone has contributed
sufficiently to any area of CoPDoC they can be voted in as a committer.
Being a committer does not mean you commit code, it means you are
committed to the project.

One of the key contributions people can make to the community is through
the support of a wide user base by assisting users on the user list,
writing user oriented docs and ensuring the user viewpoint is understood
by all developers. A main idea behind being a committer is the ability
to be a mentor and to work cooperatively with your peers."

> I think it's only fair to show who
> is active and who isn't, 

Firstly this can be seen on the mailing lists (user, dev and commits).
CoPDoC starts with (Co)mmunity.  Stefano Mazzocchi has developed a
pretty nice tool for analyzing this
http://people.apache.org/~stefano/agora/. ATM the demo seems to be kind
of broken since lenya does not show up anymore.

Further on our website we have a pretty nice (and still equally big) ;-)
change.log (rss + pdf) http://lenya.apache.org/changes.html, where one
can easily see who is active and what she has done regarding code
changes. 

This change.log is even updated every hour on our zone in the staging
docu. http://lenya.zones.apache.org/docu/changes.html

> otherwise it can be very misleading.

Actually I could not find nowhere that releasing is *the* *ultimate*
measurement for activity.

> >That is why the sentence "if it is your itch, scratch it" is standing
> >for open source.
> >  
> >
> 
> does it itch you?

Seriously, would I have started *this* thread 

"[IMPORTANT] We need a new RM (was Re: White paper on OS CMS)"

if not?

> 
> >-1 for your proposal
> >
> >salu2
> >  
> >
> obviously nobody wants to commit him/herself to being the RM.

Why is this obvious? 

Hubertus offered e.g. help with testing the releases and we have given
our committers a very short period of time to think about it, since I
started this thread. 

Maybe some people might actually like to step up as RM and just want to
give other committers a fair chance to apply for it as well. 

> Do you know the "grimm story" the devil and three golden hairs?

you mean http://www.familymanagement.com/literacy/grimms/grimms22.html

> So why not call up for sharing the load? 

Sharing the load is perfectly alright, but RM should not be seen "...as
a punishment for his sins....". ;-)

> What is wrong with that?

Like said I am all for sharing but releasing should not be made to the
only measurement for activity. Everyone who is trying to do her job in
the CoPDoC areas from lenya is an active committer, some more active
then others, but even the smallest thing is helping the lenya project.

salu2
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to