[DRE-maint] Moving away from uploaders.mk
Lucas Nussbaum
lucas at lucas-nussbaum.net
Fri Feb 2 22:18:54 CET 2007
Hi,
I think that we should move away from the Uploaders rule. As discussed
in this thread in debian-devel[0], it is clearly not the best
organization. This scheme matches our organization the best:
Maintainer: the main person responsible for the package
Uploaders: team address + other members willing to help with this
package
I think that a good test for the inclusion in Uploaders could be:
Already appears in debian/changelog
AND
willing to participate in the maintenance
This would also allow to see which packages are de-facto unmaintained.
We don't really need to remove the uploaders.mk file: actually, it's still
necessary to build old packages with a newer ruby-pkg-tools.
I propose the following procedure to change this:
1/ Every package is modified in svn, to:
* no longer include uploaders.mk
* no longer use control.in
* modify Uploaders to only include the team address
2/ Before a deadline (2 weeks ?) every member of the team add himself to
the Uploaders field of every package he cares about.
3/ All packages are uploaded again, if another version is not going to
be uploaded very soon.
4/ Eventually, we will remove uploaders.mk.
I don't think that we need to wait for etch to release for this: even if
one of our packages requires an update after that, this is very unlikely
to cause problems.
[0] http://lists.debian.org/debian-devel/2007/01/msg00275.html
--
| Lucas Nussbaum
| lucas at lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lucas at nussbaum.fr GPG: 1024D/023B3F4F |
More information about the Pkg-ruby-extras-maintainers
mailing list