Fwd: Hayes

[Andreas Pour]

Hi,

Harri, sorry to say, I disagree very much that the release coordinator should
have final say in this.  As I think everyone knows, I have zero confidence in
the current release maintainer.  If any issue of mine were left to be resolved
by him, it would be not resolved, b/c I have no confidence in his actions, and
no respect for him as a person.

The only way any group is going to function is if the institutions have
legitimacy.  When Dirk has so abused his position, then it is incumbent to
strongly rebuke him or to remove him from office.  If this does not happen, the
position loses its legitimacy.  In my opinion the position has lost its
legitimacy, so long as Dirk is in it.

Ciao,

Dre

Harri Porten wrote:
> 
> On Mon, 27 Jan 2003, Rob Kaper wrote:
> 
> [skipped technical details and history not relevant to this list]
> 
> > I'm asking this as to see how to resolve this kind of issue, who should
> > resolve it,
> 
> Ideally the both of you together, of course. Even under the assumption
> that you already tried (and failed) I still maintain my point of view that
> nobody else should look at technical arguments and judge upon them. The
> involved authors are still the experts.
> 
> > and what a policy/guideline should be for such a situation.
> 
> The only possible policy having an affect I see here is to put a decision
> power ladder going from
> 
>  1) app/lib author/maintainer
>  2) module maintainer
>  3) release coordinator
> 
> With conflict resolution sought at the lowest level first. I have to
> stress that I don't think that any low level technical guidelines should
> be put in place. Rather the duty of persons in level 2) and 3) to "force"
> an agreement between conflicting parties in 1).
> 
> Harri.