Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

2012-10-24 Thread Didier 'OdyX' Raboud
Le mardi, 23 octobre 2012 19.19:37, Sune Vuorela a écrit : > 1) report a bug 'should this package be orphaned?' against the package > with a more or less defalut templated text and a serious severity Make it 'affects qa.debian.org', with an eventual usertag, eventually X- Debbugs-CC debian-qa@ldo,

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

2012-10-24 Thread Gergely Nagy
Steve Langasek writes: > On Tue, Oct 23, 2012 at 02:40:39PM +0200, Stefano Zacchiroli wrote: >> > 4. When/if consensus has been reached, the package can be orphaned by >> >retitling and reassigning the ITO bug accordingly. > >> I fear a bit the situation "nobody care enough to comment", being

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

2012-10-24 Thread Scott Kitterman
Andreas Tille wrote: >On Tue, Oct 23, 2012 at 05:32:25PM -0400, Scott Kitterman wrote: >> I don't object to ACKs, but the requirement to get a certain ACK/NACK >ratio. I see risk of this devolving into a popularity contest. >> >> I think it should either be unanimous or there is a dispute t

Bug#691349: ITP: libopencm3 -- firmware library for ARM Cortex-M3 and similar microcontrollers

2012-10-24 Thread chrysn
Package: wnpp Severity: wishlist Owner: chrysn * Package name: libopencm3 Version : not released yet Upstream Author : Uwe Hermann , Piotr Esden-Tempski and others * URL : http://libopencm3.org/ * License : LGPL-3+ Programming Lang: C Description : fi

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

2012-10-24 Thread Steve Langasek
On Wed, Oct 24, 2012 at 02:59:09PM +0800, Thomas Goirand wrote: > On 10/24/2012 11:55 AM, Bart Martens wrote: > >On Tue, Oct 23, 2012 at 01:40:16PM -0700, Steve Langasek wrote: > >>>I fear a bit the situation "nobody care enough to comment", being > >>>interpreted as lack of consensus. But I do thi

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

2012-10-24 Thread Bart Martens
On Wed, Oct 24, 2012 at 02:59:09PM +0800, Thomas Goirand wrote: > On 10/24/2012 11:55 AM, Bart Martens wrote: > >On Tue, Oct 23, 2012 at 01:40:16PM -0700, Steve Langasek wrote: > >>>I fear a bit the situation "nobody care enough to comment", being > >>>interpreted as lack of consensus. But I do thi

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

2012-10-24 Thread Steve Langasek
On Wed, Oct 24, 2012 at 01:58:16PM +0200, Gergely Nagy wrote: > > I disagree on this point. If you can't get anyone to ack that you should go > > ahead with the orphaning, then the system is not working as designed and > > consensus has not been achieved. It's then incumbent on the person looking

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

2012-10-24 Thread Bart Martens
On Wed, Oct 24, 2012 at 01:58:16PM +0200, Gergely Nagy wrote: > Steve Langasek writes: > > > On Tue, Oct 23, 2012 at 02:40:39PM +0200, Stefano Zacchiroli wrote: > >> > 4. When/if consensus has been reached, the package can be orphaned by > >> >retitling and reassigning the ITO bug accordingly

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

2012-10-24 Thread Thomas Goirand
On 10/25/2012 12:11 AM, Steve Langasek wrote: And I don't think this is a realistic scenario. Why can't you find N other DDs who agree with you that the package should be taken over? Hum ... and what makes you think that it will always be easy to find people to ACK? Making sure that a package i

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

2012-10-24 Thread Thomas Goirand
On 10/25/2012 12:15 AM, Steve Langasek wrote: No, it makes the process based on *consensus*, which is a minimum requirement. How many people should send ACKs in this system? - If it's a lot of people, then it's hard to hunt for so many. - If it's not a lot of people, then it hardly can be cal

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

2012-10-24 Thread Guillem Jover
On Wed, 2012-10-24 at 14:59:09 +0800, Thomas Goirand wrote: > So, what will you do if: > - previous maintainer goes MIA > - Somebody wants to hija^W salvage the package and starts the procedure > - Nobody votes for this to happen... They should use the already existing MIA process instead... rega

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

2012-10-24 Thread Steve Langasek
On Thu, Oct 25, 2012 at 01:57:12AM +0800, Thomas Goirand wrote: > I remember when I started a thread about 6 months ago, > willing to take over maintainership of a clearly unmaintained > package (since then, all other packages of this maintainer > have been orphaned...). It (unwillingly) created a

Second BSP in Dublin + Ireland DUG announcement

2012-10-24 Thread Martín Ferrari
Bug Squashing Party in Dublin = http://wiki.debian.org/BSP/2012/11/ie/Dublin Come and help get Wheezy released, a second time! After the success of the first Irish Debian BSP, we're holding a second one in November. We will gather to collectively fix bugs and help each

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

2012-10-24 Thread Clint Adams
On Wed, Oct 24, 2012 at 11:48:12AM -0700, Steve Langasek wrote: > Silence is not assent. That thread blew up because you proposed a *broken* No, silence is an indication that you don't deserve any decision-making power. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a s

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

2012-10-24 Thread Charles Plessy
Le Wed, Oct 24, 2012 at 09:46:08PM +, Clint Adams a écrit : > On Wed, Oct 24, 2012 at 11:48:12AM -0700, Steve Langasek wrote: > > Silence is not assent. That thread blew up because you proposed a *broken* > > No, silence is an indication that you don't deserve any decision-making > power. Hi

Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages

2012-10-24 Thread Steve Langasek
On Thu, Oct 25, 2012 at 08:38:19AM +0900, Charles Plessy wrote: > Le Wed, Oct 24, 2012 at 09:46:08PM +, Clint Adams a écrit : > > On Wed, Oct 24, 2012 at 11:48:12AM -0700, Steve Langasek wrote: > > > Silence is not assent. That thread blew up because you proposed a > > > *broken* > > No, sil