Re: Sponsorship: news and questions about the maintainer field
- To: Josip Rodin <firstname.lastname@example.org>
- Cc: Raphael Hertzog <email@example.com>, firstname.lastname@example.org, email@example.com, Stéphane Bortzmeyer <firstname.lastname@example.org>, Antti-Juhani Kaijanaho <email@example.com>, "Justin N . Penney" <firstname.lastname@example.org>, Decklin Foster <email@example.com>, Aldenor Falcao <firstname.lastname@example.org>, Ben Hendrickson <email@example.com>, Alexander Koch <firstname.lastname@example.org>
- Subject: Re: Sponsorship: news and questions about the maintainer field
- From: Hirling Endre <email@example.com>
- Date: Tue, 27 Jul 1999 14:35:22 +0200 (CEST)
- Message-id: <Pine.LNX.3.96.990727142920.8027Gfirstname.lastname@example.org>
- In-reply-to: <19990727140652.A9870@cibalia.gkvk.hr>
On Tue, 27 Jul 1999, Josip Rodin wrote:
> On Tue, Jul 27, 1999 at 01:31:59PM +0200, Raphael Hertzog wrote:
> > But I wonder what I can put in the Maintainer field ... would it be a
> > problem to leave the name of the real maintainer that is not yet a Debian
> > developer ? I don't like it too much ... that's why I suggested to use
> > Debian QA Group <email@example.com>. That does make sense for
> > oprhaned packages that are adopted but does not make any sense for new
> > packages ... any idea ?
> AFAIK dpkg-buildpackage and dinstall don't look at the Maintainer: field,
> they authenticate just the one who uploads (the changelog entry). BTS does
> look at that entry, but that is fine with us (the bug reports should go
> to the prospective maintainer, not the one who uploaded).
> But, the Maintainers file is problematic. Can it contain entries that
> aren't in the keyring?
What about putting the sponsor's email in the Maintainer field, so
when the maintainer's application is accepted, he can promptly take
over the package communicating only with the sponsor, who - I think -
has much less CPU load than the Debian QA group :)
ps: a little correction: Alexander Koch is already a maintainer, and
thus I asked him to sponsor my zebra packages that he agreed to do.
..all in all it's just another rule in the firewall.