Antonio Gallardo wrote:
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! :-)
what is your opinion?
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. ;-)
yeah, right ... just like the american dream
http://en.wikipedia.org/wiki/American_Dream
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]
