Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages - delay for maintainer to react
On Mon, 29 Oct 2012 00:21:41 Thomas Goirand wrote: > On 10/27/2012 04:47 AM, Dmitry Smirnov wrote: > > For example if package is not maintained for years we can certainly wait > > for a month or two before orphaning even though there may be no need to > > wait that long. > > This unfortunately cannot be set as a rule. That's fine, recommendation would be good enough. On Mon, 29 Oct 2012 00:21:41 Thomas Goirand wrote: > Sometimes, a package that was > left unmaintained for a long time becomes a piece of something else, > maybe because it's a dependency of a new package, and needs to be > taken care of, and that's exactly when you will want to have a quick > adoption of the package, in order to not waste some maintainer / DD > time and/or delaying the achievement/upload of a project/package. Of course, but it looks like we've lost a bit of context. I was talking about orphaning-only while what you're saying is about adoption/salvaging/co-maintainership. On Mon, 29 Oct 2012 00:21:41 Thomas Goirand wrote: > I also think it would be a good thing if there was some kind of work > showing the intent of the adopter, on top of the ACK. This could be > in the form of a patch sent to the BTS, or some NMU. But I don't > think this should be a hard requirement. I agree with others saying > that we should trust that DDs will do the right thing. Indeed it don't have to be just NMU -- any form of contribution will do. Regards, Dmitry. -- 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/201210290904.04784.only...@member.fsf.org
Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages - delay for maintainer to react
On 10/27/2012 04:47 AM, Dmitry Smirnov wrote: For example if package is not maintained for years we can certainly wait for a month or two before orphaning even though there may be no need to wait that long. This unfortunately cannot be set as a rule. Sometimes, a package that was left unmaintained for a long time becomes a piece of something else, maybe because it's a dependency of a new package, and needs to be taken care of, and that's exactly when you will want to have a quick adoption of the package, in order to not waste some maintainer / DD time and/or delaying the achievement/upload of a project/package. On 10/27/2012 04:47 AM, Dmitry Smirnov wrote: Michael Gilbert's proposal to start salvaging with NMUs makes more sense as it allows to proceed gently and demonstrate motivation and willingness to work on the package. From non-DD prospective couple of successful NMUs will confirm salvaging intent and capacity better than random ACKs. I also think it would be a good thing if there was some kind of work showing the intent of the adopter, on top of the ACK. This could be in the form of a patch sent to the BTS, or some NMU. But I don't think this should be a hard requirement. I agree with others saying that we should trust that DDs will do the right thing. Cheers, Thomas -- 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/508d3165.5020...@debian.org
Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages - delay for maintainer to react
On Fri, 26 Oct 2012 16:56:02 Bart Martens wrote: > On Fri, Oct 26, 2012 at 08:06:57AM +1100, Dmitry Smirnov wrote: > > If bug was unanswered for let's say two months the package is free to > > orphan > > Some prefer no delay, some prefer one month, some prefer two months. I > originally wanted one month, but I got convinced by others to drop the > delay. For merely orphaning minimising delay is not too important because if there is an active maintainer ready to adopt the package it is a "salvaging" procedure. For example if package is not maintained for years we can certainly wait for a month or two before orphaning even though there may be no need to wait that long. > Now my opinion is that I trust the DDs reviewing the ITO to judge > the package's situation before sending an ACK or NACK. One possible > judgement on an ITO can be "NACK until 2 months have passed or the > maintainer has agreed to orphan the package". Another possible judgement > on an ITO can be "ACK because this package has clearly not been maintained > for years, so please proceed without further delay". I'm convinced that acknowledging is ambiguous and unnecessary. First, what do you expect DDs to acknowledge -- the fact that package needs attention (this should be obvious already) or their approval of salvager? Assuming they're not familiar with salvager's work getting and acknowledgement might be as hard as finding a sponsor. Also this will rely on developers constantly reviewing ITA requests in other people's packages. Most certainly this will increase delay and the complexity of the procedure which might work only for popular packages with high visibility. I think in usual case we can expect no response for salvaging requests. Also without timed delay acknowledgements may be very unfair if few DDs voted for salvaging and therefore salvager got a green light without waiting for possible objections. Michael Gilbert's proposal to start salvaging with NMUs makes more sense as it allows to proceed gently and demonstrate motivation and willingness to work on the package. From non-DD prospective couple of successful NMUs will confirm salvaging intent and capacity better than random ACKs. Regards, Dmitry. -- 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/201210270747.48293.only...@member.fsf.org
Re: [SUMMARY/PROPOSAL] Orphaning another maintainer's packages - delay for maintainer to react
On Fri, Oct 26, 2012 at 08:06:57AM +1100, Dmitry Smirnov wrote: > If bug was unanswered for let's say two months the package is free to orphan Some prefer no delay, some prefer one month, some prefer two months. I originally wanted one month, but I got convinced by others to drop the delay. Now my opinion is that I trust the DDs reviewing the ITO to judge the package's situation before sending an ACK or NACK. One possible judgement on an ITO can be "NACK until 2 months have passed or the maintainer has agreed to orphan the package". Another possible judgement on an ITO can be "ACK because this package has clearly not been maintained for years, so please proceed without further delay". > Another (second) situation: > > * Maintainer is not active and somebody intended to take over the package. This situation can be broken down in the "two activities" as explained here: http://lists.debian.org/debian-devel/2012/10/msg00261.html Regards, Bart Martens -- 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/20121026055602.ge10...@master.debian.org
