/[ddp]/manuals/trunk/developers-reference/developer-duties.dbk
ViewVC logotype

Diff of /manuals/trunk/developers-reference/developer-duties.dbk

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 4909 by debacle, Tue Jun 26 17:46:56 2007 UTC revision 4910 by debacle, Sat Jun 30 13:21:18 2007 UTC
# Line 1  Line 1 
1  <?xml version="1.0" encoding="utf-8"?>  <?xml version="1.0" encoding="utf-8"?>
2  <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"  <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
3      "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">      "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
4      <!ENTITY % commondata  SYSTEM "common.ent" > %commondata;
5    ]>
6  <chapter id="developer-duties">  <chapter id="developer-duties">
7  <title>Debian Developer's Duties</title>  <title>Debian Developer's Duties</title>
8  <section id="user-maint">  <section id="user-maint">
9  <title>Maintaining your Debian information</title>  <title>Maintaining your Debian information</title>
10  <para>  <para>
11  There's a LDAP database containing information about Debian developers at  There's a LDAP database containing information about Debian developers at
12  <ulink url="https://db.debian.org/"></ulink>.  You should enter your  <ulink url="&url-debian-db;"></ulink>.  You should enter your
13  information there and update it as it changes.  Most notably, make sure that  information there and update it as it changes.  Most notably, make sure that
14  the address where your debian.org email gets forwarded to is always up to date,  the address where your debian.org email gets forwarded to is always up to date,
15  as well as the address where you get your debian-private subscription if you  as well as the address where you get your debian-private subscription if you
# Line 37  lost. Line 39  lost.
39  <para>  <para>
40  If you add signatures to your public key, or add user identities, you can  If you add signatures to your public key, or add user identities, you can
41  update the Debian key ring by sending your key to the key server at  update the Debian key ring by sending your key to the key server at
42  <literal>keyring.debian.org</literal>.  <literal>&keyserver-host;</literal>.
43  </para>  </para>
44  <para>  <para>
45  If you need to add a completely new key or remove an old key, you need to get  If you need to add a completely new key or remove an old key, you need to get
# Line 45  the new key signed by another developer. Line 47  the new key signed by another developer.
47  invalid, you also have to add the revocation certificate.  If there is no real  invalid, you also have to add the revocation certificate.  If there is no real
48  reason for a new key, the Keyring Maintainers might reject the new key.  reason for a new key, the Keyring Maintainers might reject the new key.
49  Details can be found at <ulink  Details can be found at <ulink
50  url="http://keyring.debian.org/replacing_keys.html"></ulink>.  url="http://&keyserver-host;/replacing_keys.html"></ulink>.
51  </para>  </para>
52  <para>  <para>
53  The same key extraction routines discussed in <xref linkend="registering"/>  The same key extraction routines discussed in <xref linkend="registering"/>
# Line 63  package. Line 65  package.
65  <para>  <para>
66  Even though Debian isn't really a democracy, we use a democratic process to  Even though Debian isn't really a democracy, we use a democratic process to
67  elect our leaders and to approve general resolutions.  These procedures are  elect our leaders and to approve general resolutions.  These procedures are
68  defined by the <ulink url="http://www.debian.org/devel/constitution">Debian  defined by the <ulink url="&url-constitution;">Debian
69  Constitution</ulink>.  Constitution</ulink>.
70  </para>  </para>
71  <para>  <para>
72  Other than the yearly leader election, votes are not routinely held, and they  Other than the yearly leader election, votes are not routinely held, and they
73  are not undertaken lightly.  Each proposal is first discussed on the  are not undertaken lightly.  Each proposal is first discussed on the
74  <email>debian-vote@lists.debian.org</email> mailing list and it requires  <email>debian-vote@&lists-host;</email> mailing list and it requires
75  several endorsements before the project secretary starts the voting procedure.  several endorsements before the project secretary starts the voting procedure.
76  </para>  </para>
77  <para>  <para>
78  You don't have to track the pre-vote discussions, as the secretary will issue  You don't have to track the pre-vote discussions, as the secretary will issue
79  several calls for votes on  several calls for votes on
80  <email>debian-devel-announce@lists.debian.org</email> (and all developers are  <email>debian-devel-announce@&lists-host;</email> (and all developers are
81  expected to be subscribed to that list).  Democracy doesn't work well if people  expected to be subscribed to that list).  Democracy doesn't work well if people
82  don't take part in the vote, which is why we encourage all developers to vote.  don't take part in the vote, which is why we encourage all developers to vote.
83  Voting is conducted via GPG-signed/encrypted email messages.  Voting is conducted via GPG-signed/encrypted email messages.
84  </para>  </para>
85  <para>  <para>
86  The list of all proposals (past and current) is available on the <ulink  The list of all proposals (past and current) is available on the <ulink
87  url="http://www.debian.org/vote/">Debian Voting Information</ulink> page, along  url="&url-vote;">Debian Voting Information</ulink> page, along
88  with information on how to make, second and vote on proposals.  with information on how to make, second and vote on proposals.
89  </para>  </para>
90  </section>  </section>
# Line 105  unavailable. Line 107  unavailable.
107  </para>  </para>
108  <para>  <para>
109  In order to inform the other developers, there are two things that you should  In order to inform the other developers, there are two things that you should
110  do.  First send a mail to <email>debian-private@lists.debian.org</email> with  do.  First send a mail to <email>debian-private@&lists-host;</email> with
111  [VAC] prepended to the subject of your message<footnote><para> This is so that  [VAC] prepended to the subject of your message<footnote><para> This is so that
112  the message can be easily filtered by people who don't want to read vacation  the message can be easily filtered by people who don't want to read vacation
113  notices.  </para> </footnote> and state the period of time when you will be on  notices.  </para> </footnote> and state the period of time when you will be on
# Line 120  the on vacation flag when you come back! Line 122  the on vacation flag when you come back!
122  </para>  </para>
123  <para>  <para>
124  Ideally, you should sign up at the <ulink  Ideally, you should sign up at the <ulink
125  url="http://nm.debian.org/gpg.php">GPG coordination site</ulink> when booking a  url="&url-newmaint-db;gpg.php">GPG coordination site</ulink> when booking a
126  holiday and check if anyone there is looking for signing.  This is especially  holiday and check if anyone there is looking for signing.  This is especially
127  important when people go to exotic places where we don't have any developers  important when people go to exotic places where we don't have any developers
128  yet but where there are people who are interested in applying.  yet but where there are people who are interested in applying.
# Line 166  the removal of a package at freeze time. Line 168  the removal of a package at freeze time.
168  corrected as quickly as possible.  corrected as quickly as possible.
169  </para>  </para>
170  <para>  <para>
171  Developers who are part of the <ulink url="http://qa.debian.org/">Quality  Developers who are part of the <ulink url="&url-debian-qa;">Quality
172  Assurance</ulink> group are following all such bugs, and trying to help  Assurance</ulink> group are following all such bugs, and trying to help
173  whenever possible.  If, for any reason, you aren't able fix an RC bug in a  whenever possible.  If, for any reason, you aren't able fix an RC bug in a
174  package of yours within 2 weeks, you should either ask for help by sending a  package of yours within 2 weeks, you should either ask for help by sending a
175  mail to the Quality Assurance (QA) group  mail to the Quality Assurance (QA) group
176  <email>debian-qa@lists.debian.org</email>, or explain your difficulties and  <email>debian-qa@&lists-host;</email>, or explain your difficulties and
177  present a plan to fix them by sending a mail to the bug report.  Otherwise,  present a plan to fix them by sending a mail to the bug report.  Otherwise,
178  people from the QA group may want to do a Non-Maintainer Upload (see <xref  people from the QA group may want to do a Non-Maintainer Upload (see <xref
179  linkend="nmu"/> ) after trying to contact you (they might not wait as long as  linkend="nmu"/> ) after trying to contact you (they might not wait as long as
# Line 195  Orphan all your packages, as described i Line 197  Orphan all your packages, as described i
197  <listitem>  <listitem>
198  <para>  <para>
199  Send an gpg-signed email about why you are leaving the project to  Send an gpg-signed email about why you are leaving the project to
200  <email>debian-private@lists.debian.org</email>.  <email>debian-private@&lists-host;</email>.
201  </para>  </para>
202  </listitem>  </listitem>
203  <listitem>  <listitem>
Legend:
Removed from v.4909  
changed lines
  Added in v.4910
  ViewVC Help
Powered by ViewVC 1.1.5