[Pkg-crosswire-devel] debian/control Maintainer field

[Teus Benschop]

Thanks, Dmitrijs, for the response. I've indeed double checked the
matter, and saw no other option to do as you say, that is, to put my
email address in the maintainer tag, and all the other email addresses
to the uploaders field.

Hope you manage to become a Debian Developer soon. I may assist to
become a Debian Maintainer first. If I can do anything for your
application, let me know.

Teus.

On 11/23/2011 08:50 AM, Dmitrijs Ledkovs wrote:
> Heya
>
> Please double check. Quite a few people have DM upload tag in control,
> yet they maintain packages part of the Debian python modules team. If
> there are changes required to allow you become DM, I'm all for it.
> E.g. Move you to maintainer and stick the team into uploaders field.
> Or something like that. I'm still in progress to become DD. I didn't
> apply for DM.
>
> Regards.
>
> On Tuesday, 22 November 2011, Teus Benschop <teusjannette at gmail.com
> <mailto:teusjannette at gmail.com>> wrote:
> > Hi friends,
> >
> > There is a resolution online that describes the situation of Debian
> > Maintainers.
> >
> > http://www.debian.org/vote/2007/vote_003
> >
> > After reading it I realized that the current maintainer field of
> > packages bibledit-gtk, bibledit-xiphos, bibledit-bibletime and
> > gobiblecreator would not allow me to become a Debian Maintainer, since
> > the field needs to be set to the one who is going to upload these
> > packages in the future - the very thing I am after. So I made the
> > appropriate changes in this field, and added the DM-Upload-Allowed field
> > as well.
> >
> > To be more precise, it is this bit that drew my attention:
> >
> > -----
> > The initial policy for the use of the Debian Maintainer keyring with the
> > Debian archive will be to accept uploads signed by a key in that keyring
> > provided:
> >
> >  * none of the uploaded packages are NEW
> >  * the Maintainer: field of the uploaded .changes file corresponds with
> >    the owner of the key used (ie, non-developer maintainers may not
> >    sponsor uploads)
> >  * none of the packages are being taken over from other source packages
> >  * the most recent version of the package uploaded to unstable or
> >    experimental includes the field "DM-Upload-Allowed: yes" in the
> >    source section of its control file
> >  * the most recent version of the package uploaded to unstable or
> >    experimental lists the uploader in the Maintainer: or Uploaders:
> >    fields (ie, non-developer maintainers cannot NMU or hijack packages)
> >  * the usual checks applied to uploads from Debian developers pass
> >
> > ----
> >
> > Teus.
> >
> >
> > _______________________________________________
> > Pkg-crosswire-devel mailing list
> > Pkg-crosswire-devel at lists.alioth.debian.org
> <mailto:Pkg-crosswire-devel at lists.alioth.debian.org>
> >
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel
> > 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-crosswire-devel/attachments/20111123/fe20354c/attachment.html>