
On Tue, 05 May 2009 00:22:36 -0500, Rajko M. wrote:
On Tuesday 05 May 2009 12:02:56 am Jim Henderson wrote:
A plan is formed by the project leaders and IMHO is accepted or not by the community. If the project leaders want the project to grow, the perspectives of all members of the community are considered and weighed. As you and I both said, opinions have to be heard and taken into account. Then the views are incorporated or not into the overall plan.
Just to underscore, accepted by majority of community members, which doesn't mean every single person, nor vocal minorities, unless they give sound arguments to their stand.
Concur, though arguably it's not necessarily a majority of community members, but of the project team, who decides this based on the discussion within the community. At least that's how I see it. You often cannot have a community this size work towards a majority vote on anything (certainly not the entire community), that's why the project leaders represent the community in making these decisions. But a key part of the process (as I see it) is that community feedback has to be listened to and those opinions weighed as part of the equation. Ask, listen for feedback, and then decide based on the feedback plus the leadership's own opinions. Having been through product and program discussions myself where names were selected, released, and then had to be changed because of a lack of imagination, creativity, or deviousness/dirty mindedness on the part of those deciding on the name, I can tell you that replacing a name after the fact is much more difficult than making a release with a name that isn't going to lead to people asking "what WERE they thinking when they chose this name". I've had the opportunity to speak out on bad product/program names before and sometimes the name goes forward as originally decided, and other times the name was changed before it ever hit the public (and in one case, that was a REALLY good thing).
So I reiterate: the day the project stops listening to multiple points of view from the community is the day the project stops being a community- driven project.
and ends.
That is simple fact. No one is forced to accept anything, so project ends when it doesn't have followers.
Yup. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org