Debian Developers - Re: Development standards for unstable

This is Interesting: Free IT Magazines  
Home > Archive > Debian Developers > January 2006 > Re: Development standards for unstable





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: Development standards for unstable
Andreas Tille

2006-01-13, 10:44 pm

On Thu, 12 Jan 2006, Petter Reinholdtsen wrote:

> [Florian Weimer]
>
> Why is specifying the consequences of doing a bad job with maintaining
> ones debian packages threatening?


IMHO it isn't at all.

> Personally I believe it is time we made clear and written down
> explanations on what will happen to badly maintained packages, and
> then implement it, to make sure the quality of the packages still in
> Debian when this policy is implement is higher than the current level.


In addition to the list of Anthony I might add:
Require kind of a monthly status report of the maintainer. There must be a
reason if an RC bug is open longer than a month. The maintainer should
give reasons like "Need help", "Discussing with upstream", ...
If the RC bug is two month old: "Sorry, got no help", "Upstream is ignorant",
....
If a maintainer would not manage to respond to an RC bug for three months
the package is obviousely not maintained and should be taken over by
somebody else, IMHO.

Kind regards

Andreas.

--
http://fam-tille.de


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com