Re: Node.js and it's future in debian
Carsten Hey <firstname.lastname@example.org> writes:
> The origin of what the policy suggests to do if there is no consensus is
> a mail from Guy Maor <email@example.com>, in
> which he writes:
> | That's basically a stick to force developers to reach a consensus.
> Christian Schwarz uploaded this change later in this month.
> I don't think that there ever will be a consensus in all those
> discussions without discussing in a reasonable way (which failed in the
> past multiple times). Previously to this, asking the VP of Engineering
> for a decision was suggested in this thread.
I have to admit that I'm tempted to change Policy from "if there's no
consensus, rename both of them" to "if there's no consensus, try harder to
reach a consensus, and the technical committee decides in last resort."
Most of the time, renaming both of them isn't the right answer.
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>