too would really like to be able to see the charter and bylaws in writing before effectively
"signing" them.
There are several members of the Avalon community who are quite upset with the speed
at which the vote was announces and concluded. We all have to step back and remember
that we are all only here because we choose to be. Having several of our ranks feel that
they were forced into a situation is not a good thing.
Hell guys, this isn't Florida. Legally the vote over the weekend may have been ok. But if
half the membership is left angered by the process than as a community we have all failed
miserably.
There is some personal animosity between two of us in particular. And I feel that it is
very important that we work out something that will try to make the best of that situation
as well. This has been escalating now for several months and it has come to a point
where being a part of Avalon is really not all that fun any more. I know that this is
supposedly a separate issue from voting on the PMC, but it has gotten us all into a foul
mistrusting mood which is affecting the decisions on the PMC as well.
Since the vote, I have come to understand what the PMC will entail. But the information
is still scattered across several posts over the last week. I agree with Berin that it would
be wise to get this all written down in one place. It can then be modified in line. CVS is
great for this. That way, we all know what we are voting on.
I want nothing more than to get through this so that we can all get back to the real reason
why we are all here. But lets please take the time to do it right. If even one of us is left
feeling that they were forced into something and ends up leaving, that would be a loss for
Avalon as a whole.
Cheers,
Leif
Berin Loritsch wrote:
The marathon voting that happened while I could not be there is not good
for Avalon, nor is it good for the community. It forced Peter to play a
hand he did not really want to play. I gave me the feeling that noone
really
knows what was really voted for. There are some "understandings" but
nothing written to substantiate them. If things don't go according to those
understandings, there will be many angry people with nothing they can
do except fork the community and code.
I want to call a revote, but split it into three separate votes/issues. By
separating the issues, we can have a better and clearer understanding
of what we are voting for. We voted for personalities, wording, and wether
we were for PMC or not. I want to separate the issues to make it very
clear:
1) PMC, yes or no? I have a feeling this will be a yes around the board.
2) PMC charter and bylaws. We need to start with a standard Apache
cookie cutter PMC charter, and edit it to say what we understand. Things
like rotating chair positions and conflict resolution MUST BE IN WRITING
before any sane person can agree to it. I *never* ever sign a contract
I don't agree to, or don't understand my responsibilities.
3) With a full understanding of the PMC charter, who should be the first
chair. Who does the comunity feel that will support the charter, and
has a PROVEN track record for Avalon as a whole.
It needs to be said that not one of us has been innocent of being in
disagreement. What needs to happen is that the long time committers
need to get out of the "I just don't care for being polite anymore"
mentality, which I did catch myself getting into in the last months.
Peter, Stephen, Nicola, Leos, Paul, and myself have all been involved
in heated discussions and have all said things we probably regret
saying. Nevertheless, we need clear direction and I don't think we
have it.
By taking the time to do this vote correctly, and patiently, I think we
can get to a place where we are all relatively happy.
I think that we need one full week for each voting stage (1,2,3) as
outlined above. Before we can vote on 2, we need a document that
is maintained in CVS, so that our vote is on a specific revision of
that document. Once the charter is written and voted for, it can only
be changed by the concerted effort of the PMC.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
