<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
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.<br>
<br>
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.<br>
<br>
Teus.<br>
<br>
On 11/23/2011 08:50 AM, Dmitrijs Ledkovs wrote:
<blockquote
cite="mid:CAHfE3=OhWn8CBbLtPvaNwv_Y5iUfXqyzs8A+Zob5BE-h-AZOYw@mail.gmail.com"
type="cite">Heya<br>
<br>
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.<br>
<br>
Regards.<br>
<br>
On Tuesday, 22 November 2011, Teus Benschop <<a
moz-do-not-send="true" href="mailto:teusjannette@gmail.com">teusjannette@gmail.com</a>>
wrote:<br>
> Hi friends,<br>
><br>
> There is a resolution online that describes the situation of
Debian<br>
> Maintainers.<br>
><br>
> <a moz-do-not-send="true"
href="http://www.debian.org/vote/2007/vote_003">http://www.debian.org/vote/2007/vote_003</a><br>
><br>
> After reading it I realized that the current maintainer field
of<br>
> packages bibledit-gtk, bibledit-xiphos, bibledit-bibletime
and<br>
> gobiblecreator would not allow me to become a Debian
Maintainer, since<br>
> the field needs to be set to the one who is going to upload
these<br>
> packages in the future - the very thing I am after. So I made
the<br>
> appropriate changes in this field, and added the
DM-Upload-Allowed field<br>
> as well.<br>
><br>
> To be more precise, it is this bit that drew my attention:<br>
><br>
> -----<br>
> The initial policy for the use of the Debian Maintainer
keyring with the<br>
> Debian archive will be to accept uploads signed by a key in
that keyring<br>
> provided:<br>
><br>
> * none of the uploaded packages are NEW<br>
> * the Maintainer: field of the uploaded .changes file
corresponds with<br>
> the owner of the key used (ie, non-developer maintainers
may not<br>
> sponsor uploads)<br>
> * none of the packages are being taken over from other
source packages<br>
> * the most recent version of the package uploaded to
unstable or<br>
> experimental includes the field "DM-Upload-Allowed: yes"
in the<br>
> source section of its control file<br>
> * the most recent version of the package uploaded to
unstable or<br>
> experimental lists the uploader in the Maintainer: or
Uploaders:<br>
> fields (ie, non-developer maintainers cannot NMU or hijack
packages)<br>
> * the usual checks applied to uploads from Debian developers
pass<br>
><br>
> ----<br>
><br>
> Teus.<br>
><br>
><br>
> _______________________________________________<br>
> Pkg-crosswire-devel mailing list<br>
> <a moz-do-not-send="true"
href="mailto:Pkg-crosswire-devel@lists.alioth.debian.org">Pkg-crosswire-devel@lists.alioth.debian.org</a><br>
> <a moz-do-not-send="true"
href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel</a><br>
>
</blockquote>
<br>
</body>
</html>