Hi folks,
Amazing word soup, guys! :-)
Michael Wechner wrote:
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
Thorsten is right. Project founders have more impact in the people
perception. On the other side, Michael already stated this is only his
POV. As he stated it is not an "official Lenya PMC position". :-)
.... <a_big_fat_highly_spicy_word_soup> .....
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
- ...
Until here, I think everybody more or less agree..... every committer
has a vote and his vote depends on his commitment level [1], but I am
not going to go deeper....
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".
OK. Again this is only your opinion. Thanks for sharing it! :-)
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?!?!
What I saw in few years working in open source projects:
Release manager is very important. The RMs get fast and high people
recognition. Users often note the name of the person releasing the code.
They are often looking for the person, who sent the release note. Hence,
the users think the release manager is one of the most important
committers in a project. That means recognition and the recognition is
often the incentive. He becomes a hot spot. He get visibility and thanks
to the current Open Source boom, the money can follow this recognition. ;-)
Just a random tought.
Best Regards,
Antonio Gallardo.
[1] http://www.apache.org/foundation/voting.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
