From f5218b14a966d95ca086fbf566e9c9769afd4df6 Mon Sep 17 00:00:00 2001 From: kov Date: Wed, 20 Feb 2002 22:53:20 +0000 Subject: [PATCH] added a section on how to deal with unreachable (maybe-MIA) maintainers git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@1418 313b444b-1b9f-4f58-a734-7bb04f332e8d --- developers-reference.sgml | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/developers-reference.sgml b/developers-reference.sgml index 8ff600e..fe45226 100644 --- a/developers-reference.sgml +++ b/developers-reference.sgml @@ -5,7 +5,7 @@ %commondata; - + @@ -368,6 +368,22 @@ id="orphaning">). Alternatively, you may ask the help of other people in order to catch up the backlog of bugs that you have (you can ask for help on &email-debian-qa; or &email-debian-devel;). + Dealing with unreachable maintainers +

+If you notice that a package is lacking maintenance, you should +make sure the maintainer is active and will continue to work on +their packages. Try contacting them yourself. +

+If you do not get a reply after a few weeks you should collect all +useful information about this maintainer. Start by logging in to +the +and doing a full search to check whether the maintainer is on vacation +and when they were last seen. Collect any important package names +they maintain and any Release Critical bugs filled against them. +

+Send all this information to &email-debian-qa, in order to let the +QA people do whatever is needed. + Retiring Gracefully

If you choose to leave the Debian project, you should make sure you do -- 2.30.2