Re: Conflicts between developers and policy
Manoj Srivastava <srivasta@datasync.com> wrote:
> Why should you make your package conform?
Because it's the right thing to do.
> There is nothing that says you have to follow policy. Can the Tech
> committee make me do whatever they darned well please?
Well, they certainly can't make you read the constitution drafts...
> Since the policy document have no more standing than, say, "The flight
> of the Bumble Bee", all this means is that the tech committee pointed
> to a set of rules somewhere, entirely at theur whim, and said "YOU!
> MORTAL! Follow THAT!"
Since when is "The flight of the Bumble Bee" the right thing to do?
I think now you're objecting to Ian's recursive explanation of what
policy is. For a better explanation, consult a good dictionary.
> That has been my point. If the Policy documents have no standing,
> especially in the defining document that awards authority, then the
> technical committee can bring in any reference they choose fit, not
> just the policy documents. (Like the MS OS manuals ;-)
You mean like their entire background of technical expertise? Oh, the
horror!
People who aren't competent to distinguish between worthwhile references
and garbage aren't going to be good tech committee members just because
you've reclassified policy as some kind of law.
> This is too much power in the hands of too few. Especially since the
> developers have no say in who constitutes the board. How answerable
> are they to the rest of the developers anyway?
I missed this one myself, when I was reading over the draft constitution:
If the Technical Committee and the Project Leader agree they may
remove or replace an existing member of the Technical Committee.
Of course, the developers can provide override decisions for both
the tech committee and for the leader...
But the real thing that will keep us honest is the outside world.
> I would rather be able to point to the policy documents as a kind
> of limit to the powers of the technical committee. And have the
> developers have some say in the shaping of the policy documents.
Huh? Are we even talking about the same document here?
The developers have some say. Furthermore, if they're particularly
displeased with the quick resolution they can override any decision
of the Technical Committee (or of the Leader, for that matter).
Here's a couple other statements which somewhat limit the powers
of the tech committee:
Then Technical Committee does not engage in design of new
proposals and policies. Such design work should be carried
out by individuals privately or together and discussed in
ordinary technical policy and design forums.
The Technical Committee restricts itself to choosing from or
adopting compromises between solutions and decisions which
have been proposed and reasonably thoroughly discussed
elsewhere.
What are you thinking?
--
Raul
--
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: