Stefano Zacchiroli writes:
> On Sat, Mar 17, 2012 at 04:19:46PM -0700, Russ Allbery wrote:
>> I'm sure that's a large part of it, but I think people also avoid doing
>> this because it means not making decision by consensus. When some
>> central body hands down a decision, it almost guarantees t
On Sat, Mar 17, 2012 at 04:19:46PM -0700, Russ Allbery wrote:
> Stefano Zacchiroli writes:
> > But in our practices, we tend to rely on the Technical Committee
> > only for issues that fall in the broad category of "conflicts"
> > (ยง6.1.2 "Decide [...] where Developers' jurisdictions overlap").
>
On Tue, Mar 20, 2012 at 07:55:56AM +0100, Wouter Verhelst wrote:
> However, the problem with detailed job descriptions, as it were, is that
> you run the risk of having people argue over whether or not something is
> their responsibility. This would introduce a conflict.
>
> In the absense of such
Dear candidates,
this is the echo of a question asked two years ago in the 2010 campaign.
http://lists.debian.org/debian-vote/2010/03/msg00057.html
In addition, do you see major changes happening in the recent or next years,
and how do you think Debian should react to them ?
Have a nice day,
4 matches
Mail list logo
