[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

General reminder, Re: RFS: Orphaned Packages ladder.app, lapispuzzle.app, quake2-data, scottfree


 I removed the In-Reply-To header on intention and broke threading
through it, please read below why I've chosen to do so.

* Gerfried Fuchs <rhonda@deb.at> [2008-01-17 21:37:45 CET]:
>  Done the following (or rather, somme still in the queue), please don't
> forget to tag them properly:
> > http://mentors.debian.net/debian/pool/main/m/mines.app/mines.app_0.1.0-5.dsc
> > http://mentors.debian.net/debian/pool/main/3/3dchess/3dchess_0.8.1-14.dsc
> > http://mentors.debian.net/debian/pool/main/s/stepbill.app/stepbill.app_2.4-5.dsc

 Those were really done and uploaded.

> > http://mentors.debian.net/debian/pool/main/l/ladder.app/ladder.app_1.0-5.dsc
> > http://mentors.debian.net/debian/pool/main/l/lapispuzzle.app/lapispuzzle.app_1.0-5.dsc

 Those not. Ladder doesn't have anything useful in the about menu (just
empty entries), it looks a bit fishy to me. I spoke with Barry about it
and we might reconsider addiing this to our team pool.

 LapisPuzzle doesn't seem to be controlable at all currently, I objected
to add such a thing to our pool. Either this will get fixed (maybe with
upstream's help) or there is no real place for it in our pool).

 More generally spoken (and this is by far not limited to Barry, not at
all): Please don't add things to the pool if you aren't personally
interested in the things. Having packages in the games team doesn't
automatically mean that someone will take a look at it. If you add
something it is up to you to see that it is getting the required
attention, at least for a fair bit of time. It is quite possible that
others might jump on board and get interested too, but you shouldn't
depend on others to jump in to help you out.

 If you don't have the time for looking at a package properly then
adding it into our pool and letting it rot there isn't really helping
the users. I know that it's always a tough decision to have something
removed, but some times this is the better idea than to leave users in
the impression that something still gets its proper attention it

 Maybe some sort of rule of thumb: If you don't even remotely think
about using the package at least once a month, just don't put it in. We
currently have 239 outstanding bug reports, only a small spot of them
are forwarded or pending, though a lot of them are minor and wishlist
items, but nevertheless they should get addressed, too.

 So long,

Reply to: