I don't think we need GRs to decide development procedures like this.
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/
On Fri, Oct 26, 2012 at 7:46 AM, Arno Töll wrote:
> *) we have consensus that we are in need of such a rule set - which ever
> it may be
>
> *) we have three orthogonally different ideas:
>a) Bart's approach which was reformulated and proposed by Lucas in
> this thread [1]
>b) Mine - which
On 26.10.2012 13:54, Stefano Zacchiroli wrote:
> But I urge you to reconsider proposing a GR. It is a heavy
> weight tool, that should be used as a last resort.
So far I agree. I didn't say I'll propose on - JFTR. I said I'll
consider that and asked for opinions - like yours :)
--
with kind re
On Fri, Oct 26, 2012 at 01:54:19PM +0200, Stefano Zacchiroli wrote:
> I don't think we're nowhere near the need of it in this specific case.
s/don't//
obviously :)
--
Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack
On Fri, Oct 26, 2012 at 01:46:41PM +0200, Arno Töll wrote:
> What do you think? Does this sound like a fair compromise everyone
> could live with?
Voting is almost never a way to reach consensus. Rather, it acknowledges
that consensus has not been reached and side-steps further constructive
attemp
5 matches
Mail list logo
