X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=developer-duties.dbk;h=f09e3cf09ab1002607f9813a2cd312c55a79f16d;hp=5a444e76a034e9fc0898f94fb958b7421ca3b710;hb=22cf909af0f96e48102f528c16fc5107ccde8287;hpb=c81927355fe51c8a09827d098d0caad05a052d67 diff --git a/developer-duties.dbk b/developer-duties.dbk index 5a444e7..f09e3cf 100644 --- a/developer-duties.dbk +++ b/developer-duties.dbk @@ -1,7 +1,7 @@ %commondata; + %commondata; ]> Debian Developer's Duties @@ -16,8 +16,7 @@ as well as the address where you get your debian-private subscription if you choose to subscribe there. -For more information about the database, please see -. +For more information about the database, please see . @@ -26,9 +25,9 @@ For more information about the database, please see Be very careful with your private keys. Do not place them on any public servers or multiuser machines, such as the Debian servers (see ). Back your keys up; keep a copy offline. Read +linkend="server-machines"/>). Back your keys up; keep a copy offline. Read the documentation that comes with your software; read the PGP FAQ. +url="&url-pgp-faq;">PGP FAQ. You need to ensure not only that your key is secure against being stolen, but @@ -71,16 +70,16 @@ Constitution. Other than the yearly leader election, votes are not routinely held, and they are not undertaken lightly. Each proposal is first discussed on the -debian-vote@&lists-host; mailing list and it requires -several endorsements before the project secretary starts the voting procedure. +&email-debian-vote; mailing list and it requires several +endorsements before the project secretary starts the voting procedure. You don't have to track the pre-vote discussions, as the secretary will issue -several calls for votes on -debian-devel-announce@&lists-host; (and all developers are -expected to be subscribed to that list). Democracy doesn't work well if people -don't take part in the vote, which is why we encourage all developers to vote. -Voting is conducted via GPG-signed/encrypted email messages. +several calls for votes on &email-debian-devel-announce; (and +all developers are expected to be subscribed to that list). Democracy doesn't +work well if people don't take part in the vote, which is why we encourage all +developers to vote. Voting is conducted via GPG-signed/encrypted email +messages. The list of all proposals (past and current) is available on the Usually this means that other developers are allowed to NMU (see ) your package if a big problem (release critical bug, security +linkend="nmu"/>) your package if a big problem (release critical bug, security update, etc.) occurs while you're on vacation. Sometimes it's nothing as critical as that, but it's still appropriate to let others know that you're unavailable. @@ -122,7 +121,7 @@ the on vacation flag when you come back! Ideally, you should sign up at the GPG coordination site when booking a +url="&url-gpg-coord;">GPG coordination pages when booking a holiday and check if anyone there is looking for signing. This is especially important when people go to exotic places where we don't have any developers yet but where there are people who are interested in applying. @@ -152,16 +151,22 @@ can be included there, so that you won't have to modify the sources of the next upstream version. Whatever changes you need, always try not to fork from the upstream sources. + +If you find that the upstream developers are or become hostile towards Debian +or the free software community, you may want to re-consider the need to +include the software in Debian. Sometimes the social cost to the +Debian community is not worth the benefits the software may bring. +
Managing release-critical bugs Generally you should deal with bug reports on your packages as described in - . However, there's a special category of bugs +. However, there's a special category of bugs that you need to take care of — the so-called release-critical bugs (RC -bugs). All bug reports that have severity critical, -grave or serious are considered to +bugs). All bug reports that have severity critical, +grave or serious are considered to have an impact on whether the package can be released in the next stable release of Debian. These bugs can delay the Debian release and/or can justify the removal of a package at freeze time. That's why these bugs need to be @@ -176,7 +181,7 @@ mail to the Quality Assurance (QA) group debian-qa@&lists-host;, or explain your difficulties and present a plan to fix them by sending a mail to the bug report. Otherwise, people from the QA group may want to do a Non-Maintainer Upload (see ) 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 usual before they do their NMU if they have seen no recent activity from you in the BTS). @@ -191,7 +196,7 @@ following steps: -Orphan all your packages, as described in . +Orphan all your packages, as described in . @@ -203,7 +208,7 @@ Send an gpg-signed email about why you are leaving the project to Notify the Debian key ring maintainers that you are leaving by opening a ticket -in Debian RT by sending a mail to keyring@rt.debian.org with the words 'Debian +in Debian RT by sending a mail to &email-keyring; with the words 'Debian RT' somewhere in the subject line (case doesn't matter).