17 Oct
2005
17 Oct
'05
1:24 p.m.
From: Royce Mitchell III
Here's a combination of various suggestions to hopefully
begin to close this matter:
3) TC has power to block CF, subject to be overruled by a
vote should a majority feel it is not critical enough.
Sorry, I still think this is fundamentally wrong. It's the developers as a
collective which run this project. It's the developers as a collective (and
this includes the TC with his vote) which should make this decision. If
you're going to give final decision making capability to the devs anyway,
why put the TC in the middle? If the devs are going to overrule him anyway,
there's a big chance that the vote would piss off the TC (especially if it
happens a few times in a row). I know I would find it much easier to accept
a collective decision, rather than a collective decision explicitly
overriding a decision I made earlier.
To get this moving forward, perhaps 2 proposals should be voted on: proposal
A which gives TC blocking power (overrulable by a vote) and proposal B which
does note give the TC that power. Instead of a yes/no vote on a single
proposal we can then vote either A or B.
Andrew, would you still be willing to run for TC and
continue
the absolutely fantastic work you've done there given these,
assuming everybody would agree to them?
In the scenario above (A/B vote) Andrew could wait for the outcome of the
vote and then decide whether he wants to fulfill the TC role. I hope he
will, but I understand he would want to know exactly what he signs up for
before committing himself.
Gé van Geldorp.