You may sense a certain aggression/frustration here. That is brought about by the inability of this community to deal with the problems back in July/August - it was complicated by the inability of the Jakarta PMC to address the issue. Even the board didn't address the issue on the table at the time. Nobody took a position - not structure in the entire Apache organization was willing to step in with a closure. Yes - Pete got kicked - but that wasn't the subject of the Jakarta/Board discussion before - that was probably more of a surprise to me than to any of you. What I do know is that those types issues MUST be address by the Avalon PMC. If you continue along the lines your describing - your just creating the comfortable environment where you simply isolate yourself away from the potential of having to take a difficult decision.The aggression is not helpful, our wider community shrinks by a percentage again.
As a PMC member - I REFUSE to let a similar situation arise for other members of the community. I will do everything I can to ensure that the PMC is an instrument that has balls and ability. And I'm confident that providing those attributes are held up with respect - that we will never need to use them. Today the PMC has balls - please don't try to take that away. Its abilities will evolve through attention and consideration to the charter and procedures, and progressively, through respect from a united community.
For the record, I was like it or not, mediating on the 'dispute' on August. Significant gains were made. I did not publish my results to the board. I'm sure if I had done, the board would not have felt the need to act on advise since then, in the way they did.
-ph
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
