r254 - /web/deps/dep2.mdwn

[hertzog at users.alioth.debian.org]

Author: hertzog
Date: Wed Feb  1 18:18:28 2012
New Revision: 254

URL: http://svn.debian.org/wsvn/dep/?sc=1&rev=254
Log:
DEP-2: Update on the information flow

Note to re-ask ourselves the question whether we can get a consensus on
having to modify all Debian services to directly send the mail to the
DPMH and only there (i.e. no longer to the Maintainer field).

Clarify that if the Maintainer field is replaced, its former value is
moved to Uploaders.

Modified:
    web/deps/dep2.mdwn

Modified: web/deps/dep2.mdwn
URL: http://svn.debian.org/wsvn/dep/web/deps/dep2.mdwn?rev=254&op=diff
==============================================================================
--- web/deps/dep2.mdwn (original)
+++ web/deps/dep2.mdwn Wed Feb  1 18:18:28 2012
@@ -169,6 +169,7 @@
 rid of the hacks made everywhere to send a copy of the mails to the PTS,
 packages would be (progressively) modified to indicate
 “Maintainer: <source>@pkgmaint.debian.org” in their control file.
+The current content of the field would be moved to the “Uploaders” field.
 
 Until all packages have been converted, the PTS would forward copies of
 the mails to ensure that the new infrastucture can still be used for all
@@ -177,6 +178,15 @@
 Using this intermediary address also solves the problem of maintainers who
 orphan their packages and are still listed as maintainers in many released
 packages.
+
+QUESTION: It would be cleaner if DAK, the BTS, and all relevant services,
+could stop sending mails to the Maintainer field, and would instead always
+send the mail to the new infrastructure. That way we wouldn't need to
+change the Maintainer field and there would be no transition period.
+
+The new infrastructure would then be configured with initial subscriptions
+for emails listed in Maintainer fields (except for mailing lists, since
+the infrastructure aims to replace them).
 
 ### Leveraging UDD