Antonio Gallardo wrote:
Michael Wechner wrote:
Antonio Gallardo wrote:
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".
and my personal opinion is that collaborating on release management
OK. Again this is only your opinion. Thanks for sharing it! :-)
what is your opinion?
My opinion is that an Open Source project is not a company, where the
boss says: "Do or retire".
did I say that? Please don't make it sound as if
I have said something like that, because I clearly didn't!
Here, people are supposed to help when they can and want. It must be fun.
not everything is fun within an Open Source project.
I think one needs to tell people that there are responsibilities and
duties connected with roles within an Open Source project.
Saying something different than that would be very misleading.
It is not a full time job for many of us. The PMC chair is a different
story, he has some responsabilities to do when he accepts the chair,
it is part of his duties. Every PMC chair knows that. As we know,
there is a lot of more tasks to do in an Open Source project. I think
Thorsten already pointed to them, so I will not repeat it again. :-)
In short, every committer is free to decide where they want to help.
No, that's not necessarily true. This depends on the rules the community
decides on, just as the members of the ASF decided that a PMC chair
has duties.
There are different roles:
user
contributor
committer
PMC member (PMC chair)
ASF member (ASF board member)
As soon as you will "enter" the community at the level of a
committer you will have to follow certain rules and one will
have responsibilities and duties attached with it. These
rules of course are set by the community itself, but as long
as the community doesn't change them one needs to stick to
it otherwise the community will quickly go down the toilet.
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
lol. I showed a "dream" because you told money might be an incentive.
I just pointed out how is posible to reach this incentive. Is this a
dream or not?
I think it's very important to understand this.
I really don't care. ;-)
why don't you care?
In my few years in FOSS I learned that not all of us are here for a
money hunt. I will said, some yes, but not all. Some of us is here
just for the fun of programming, for personal recognition or for the
fun of helping other people between other incentives. Am I naive? Maybe.
I don't think you are naive at all, but I think the stuff you are
saying is very misleading. For instance I would claim that
most people are working on resp. contributing this project (and not just
Lenya) because it's related to their daily work and in most cases it means
money. I can't tell for people outside of Wyona, but I can clearly tell for
people who work and worked for Wyona, because in the case of
Wyona I can excatly show you the correlation between project activity
and work within the company.
I don't think that's bad at all, but it shows me the reality and
not something which I might like it to be.
(and I would claim that in most other projects it's just the same)
But often nothing is more gratificant than receiving a mail with a
"thank you" inside. I think all of us feel a good sensation when this
happens.
sure
And this is why we often found our selfs fixing bugs or adding a new
feature in places that we never used before nor plan to use.
I don't think that's the reason in most cases
Please note, I am not telling Lenya does not need to have a RM. I am
just telling nobody can be forced to be one. ;-)
I am not forcing anyone. Again, please don't give people the perception
that I said something like that. I didn't!
Michi
Best Regards,
Antonio Gallardo.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
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]
