On Sun, Jan 08, 2006 at 02:40:47PM +0100, Carsten Lohrke wrote:
> On Sunday 08 January 2006 01:35, Stuart Herbert wrote:
> > I agree that some cleaning is needed (and some of my packages are
> > desperate for it!), but I'm totally opposed to this idea.  I think the
> > idea of shutting up shop for three months (presumably with a "closed
> > for refurbishment" sign on the door) would let down our users who rely
> > on us for regular package updates, and would be a massive PR disaster.
> >  Cleaning is something that has to happen all the time; it needs to be
> > a natural and sustainable part of what we do every day.
> 
> As Donnie already pointed out, I did not mean version bumps, but only new 
> packages. 

> How about this idea: Everyone who adds a new package, has to check 
> and fix an unmaintained package before.

Guessing you missed the previous flame war about how trying to force 
people to do something doesn't actually work?


> This should be a non-issue for 
> seasoned developers, 

You're assuming seasoned devs don't occasionally go MIA on 
QA/maintenance?  It's not the case...


> but would slowdown those who continually add new 
> packages [ snip vitriolic opinions ]

If you've got an issue with devs adding stuff and abandoning/not 
supporting their stuff, hey that's fine, bitch at QA.

Don't go freezing the whole tree just because you're after slapping at 
a couple of devs over perceived wrongs.


> Don't you think that it is pretty much barefaced to let a small group do the 
> dirty, boring and annoying work, while those who don't care a bit can 
> continue to do so?!

If you've got an issue with certain devs (seems to be the case from 
your statement), take it up with QA/ombudsman, not the loop 
around attempt you're doing here.

If you're after trying to decrease the unmaintained packages, like I 
said, generate a list _from the tree_, compare it to bugs, etc.  Do 
the legwork, kick off the effort to cover the gap.

Basically, you want to decrease bugs for unmaintained, decrease the 
gap of maintained vs unmaintained, work on _that_ rather then trying 
to force everyone to drop what they're doing and fix an issue they're 
already working on at their own pace.

Folks *are* handling retirement of unmaintained packages, and taking 
on maintainance of packages already- just watch -dev for the 
occasional announcements if you think otherwise.

~harring

Attachment: pgpDAMqm725Du.pgp
Description: PGP signature

Reply via email to