Thorsten Scherler wrote
People often see you as a mentor in this project and what you say is
important to them. If you suggest (like yourself admitted) that people
should retire if they not doing a release then this can be
misinterpreted as an official statement.
it's my personal opinion
You are lucky and should be happy that people are pointing out that is
not the official standpoint of the lenya PMC and trying to help to
clarify the situation.
Was it unclear to you? Was is unclear to others? If so,
then people should speak up ...
Instead of defending your position IMO it would make more sense just to
say:
"Sorry if the above said may have been misinterpreted, this was not my
intention. This is not the official opinion of the lenya PMC and
project."!
...but that would have been too simple I guess. ;-)
I am not here to defend myself. Why should I apologize
for my personal opinion?!
...
Like said I am all for sharing but releasing should not be made to the
only measurement for activity.
did I say that? Definitely not!
c'mon, what about the line above
">You wrote: "If committers don't want to, then I think they should
retire ..."
what exactly does that sentence say?! Does
it say that people's activity will be measured only
on if they do a release?! Certainly NOT. It's not
about measuring, but trying to be a group of people
living together.
>
it's a clear suggestion!"
So, you have been suggesting it!!!
sure, I did and I still mean it.
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.
agreed, but that was never the issue here.
Actually it is, due to your suggestion. I feel impelled to point this
out!
I think you see ghosts where there are none.
Let me explain, why I think people should retire if
they don't want to accept rules and keep up with certain duties:
We are a group of people (having goals) living in a house.
In order to be able to live together we decide on some rules
(with reasons behind, whereas the reasons are more important than
the rules themselves) and normally some duties attached.
In the case of the ASF or the Apache Lenya community most of these rules
are not written down, but they do exist, e.g.
- Write reports for the board
- Backwards compatibility for certain branches
- ...
and my personal opinion is that collaborating on release management
should be a rule as well. The reason for this rule is that regular
releases are important such that people can base their stuff on
something "static". But doing the releases is not a lot of fun
and won't give a lot of recognition/appreciation or whatsoever,
so it's not such a big incentive for the individual doing such
a release, but it's important for the community at large.
(everyone wants to cook and eat, but nobody wants to do the dishes).
Money might be an incentive, but we don't have money. So what can we
do?!?!
The only good way I see (except finding someone who thinks doing
releases are fun ...) is sharing the load.
Michi
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
