> People work on what they feel like, when they feel like it
> and as soon you begin trying to stop them from doing this
> they will either stop doing the work or fork. Either way
> can be a loss for the project.
While those may be accurate statements, if the individual wants to work
within a Community, they have to live by social rules, not just individual
desires. In the specific case of an Apache project, there are a couple of
issues:
- you must be willing to support the communal code.
- you must accede to the community rules that
govern what goes into the code, e.g., another
developer can veto a change for technical
reasons if they feel that the proposed change
is wrong.
> My belief is that the developers and the managers should be one and the
same.
> The people who make the decisions should be the ones who are actually
willing
> to implement, maintain and support the decisions.
The people with voting rights are Committers. Those are the developers, and
your peers.
> "To be honest all I want is for the people who are actually contributing
and
> maintaining Phoenix to be the ones that get to make decisions about its
> future. Whether that decision is to kill it off, put it in sleep mode or
> whatever it should be up to the people who do the work. As long as it is
> actively maintained there should be no interference for purely political
> reasons. How this is achieved is just an implementation detail."
If you were to define Phoenix as an Avalon subproject, what would be in it?
> I actually consider "empowering the developers" and "empowering the
community"
> as synonymous.
Do you consider the community to consist of people other than the
developers? Do you feel that developers develop code for themselves, and
secondarily for others to use? Considering that there are more developers
relying upon Avalon code that working on it, I would disagree. There have
been changes to the public API that were detrimental to the people using the
code. The ASF, which provides the infrastructure for the project, has a
vested interest in the quality of the project. Fortunately, the ASF's
interest is in the health of the project. The PMC Chairman, and the PMC,
have a responsibility to the ASF.
> The partioning of privledges to those involved with development of
codebases
> is done throughout Apache.
What partitioning would you like to see?
> In Avalon we used to partition by respect but that repect
> evaporated long ago.
Statements like this do not help your case. Most people within the
community evidence respect towards one another. There are some notable
exceptions. The PMC feels that while technical disagreements are expected
and healthy, expressing a lack of respect towards your peers is not
acceptable.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
