Hello, we've done a bit of template cleanup, removing some obvious questions, merging some similar questions, that sort of things.
You may want to update your template checkout to get the newer version.
I'm posting the diff, for your convenience.
Diffstats with more deletions than insertions are always a good thing:
3 files changed, 26 insertions(+), 56 deletions(-)
Ciao,
Enrico
diff --git a/nm-templates/nm_pp2.txt b/nm-templates/nm_pp2.txt
index b871f28..723d6f6 100644
--- a/nm-templates/nm_pp2.txt
+++ b/nm-templates/nm_pp2.txt
@@ -13,9 +13,6 @@ mailing lists you might want to subscribe to.
Bug Tracking System
-------------------
-BT1. Please tell me 2 different methods to close a bug in the BTS, the
- difference between them, and when to use which method.
-
BT2. You have a package (current version 1.3), with a set of open bugs:
#123: eats lots of memory (fixed in 1.2)
@@ -28,14 +25,9 @@ BT2. You have a package (current version 1.3), with a set of
open bugs:
1.4 of the package. What do you do with the bugs not mentioned
in the changelog?
-BT3. Each bug report has a severity and optionally one or more tags. What's
- the difference between severity and tags? How do you set
- them? How do they affect the release status of a debian package?
- Are there restrictions who can/should set some tags?
-
-BT4. Someone files a bug against a package that you maintain. However, the
- problem in the bug report does not come from a bug in your package, but
- rather a bug in another maintainer's package. What do you do?
+BT3. How (and when) does a package get from its first upload to a stable
+ release? Can bug tags affect the release status of a debian package? Are
+ there restrictions on who can/should set some tags?
BT5. What would you do if a bug was reported against your package and
you are not able to fix it yourself?
@@ -53,20 +45,30 @@ BT8. Please explain what a usertag is and why they're
useful.
Procedures
----------
-PR1. Although English is doubtless the "lingua franca" nowadays, which means
- that it is understood nearly everywhere, there are users who do not
- understand it. How does the Debian project help these people?
-
-PR2. Please list some tasks that form part of the duties of the Debian
- Quality Assurance group.
+PR1. Is there any of these bits of Debian that you haven't heard of, or
+ of which you would like to know more?
+ - The Debian QA team
+ - The Debian l10n team
+ - Bug Squashing Parties
+ - Debtags
+ - The Debian Wiki
+ - Comaintenance
+ - Maintaining packages in version control systems
+ - Alioth
+ - UDD
+ - backports.org
+ - debian-volatile
+ - Anything else?
+ Note that I only want to show that they exist and to offer pointers or
+ tips if you are interested.
+
+PR2. You've just heard about this great program and would like to package
+ it, what are your next steps?
PR3. What should you do when a security bug is discovered in one of your
packages? What steps do you need to fix a problem in one of your
packages in the stable release?
-PR4. At regular intervals, we arrange the so called "Bug Squashing Parties".
- What are they good for and what happens during such a BSP?
-
PR5. What are Non-Maintainer Uploads (NMUs) and when would you do an NMU?
Please list the usual procedure for an NMU.
@@ -74,9 +76,6 @@ PR5a. What is a binNMU and what are they useful for? Where
and how do
you request to schedule binNMUs? Which precautions do you have to
take to make your packages binNMU safe?
-PR6. You've just heard about this great program and would like to package
- it, what are your next steps?
-
PR7. You can't/won't maintain a package properly any more because
you have a lack of time/don't use it anymore. What are your
options to handle this situation?
@@ -92,8 +91,6 @@ PRa. Do you know how to create a revocation certificate for
your OpenPGP key?
PRb. What would you do if you wanted to retire from the project?
-PRc. Please explain what debian-volatile and backports.org are. Do you
- find them useful? Are non-DDs allowed to upload packages there?
That's the second part of P&P. When we are done with this, we will
continue with T&S, the Tasks and Skills.
diff --git a/nm-templates/nm_ts1.txt b/nm-templates/nm_ts1.txt
index 976c12c..d62a2e2 100644
--- a/nm-templates/nm_ts1.txt
+++ b/nm-templates/nm_ts1.txt
@@ -49,16 +49,8 @@ PF2. What does the version string in the Standards-Version
field of a
PF3. What is the difference between native packages and non-native
packages?
-PF4. There are many Debian suites, like "stable", "unstable", "testing",
- "experimental", "lenny", "squeeze" and "sid". Can you explain why
- there are so many and what the differences are? How (and when)
- does a package get from one to the other?
-
PF5. How do you choose the "urgency" field in the changelog?
-PF6. What are required, important, standard, optional and extra? Why are
- they useful?
-
PF7. What is Essential: yes? Why isn't libc essential and why can't it
be? Why does it not need to be essential? Why isn't the kernel
essential?
@@ -66,9 +58,6 @@ PF7. What is Essential: yes? Why isn't libc essential and why
can't it
PF8. Explain the difference between Depends, Recommends, Suggests and
Enhances.
-PF8a. What should you keep in mind regarding the Recommends field while doing
- backports or updates for Etch or older releases?
-
PF9. What is Pre-depends for? Why should you avoid it?
PFa. Please explain what a virtual package is. Where can you find a
@@ -83,7 +72,7 @@ PFc. What is your experience with maintainer scripts? Do you
know where
Marga's quick reference can be found here:
http://wiki.debian.org/MaintainerScripts
-PFd. If you had a file in your package which usually gets changed by a
+PFd. If you had a file in your package which usually gets changed by an
administrator for local settings, how do you make sure your next version
of the package doesn't overwrite it?
@@ -99,9 +88,6 @@ PFf. Write a small shell script which does the following two
things:
You may use tar, ar, grep, etc., but not any middle or high-level
dpkg tools.
-PFg. Please describe what debtags is, and how you can contribute to
- it.
-
Practical packaging
-------------------
@@ -116,10 +102,6 @@ PP1. Imagine you maintain a package which depends very
closely on some
PP2. How can you ensure your package's description is in a good state and
in a valid format?
-PP3. You have a new package, and you find that it will be in contrib.
- Why would it be there? What could you do (in theory at least) to
- get it into main?
-
PP4. If one of your packages had serious problems like either
a) the current version in the archive is not "mature" enough
to be in a Debian release but it is developing and you still
@@ -128,16 +110,9 @@ PP4. If one of your packages had serious problems like
either
other reasons and you consider it not worth including in Debian.
How would you proceed in these cases?
-PP5. There is a rather annoying bug in your package, fixed in upstream's
- CVS/development branch, but upstream is not planning a new release
- anytime soon. What do you do with it?
-
-PP6. What do you do if upstream releases a tarball once every year and
- then distributes minor revisions only in the form of patches? How do
- you manage your package then?
-
-PP6a. Which tools are available in Debian to help you with the handling
- of patches?
+PP5. How do you patch upstream sources in a package? What are the advantages
+ and disadvantages of doing it? How can you keep the number of patches
+ down?
PP7. Please list some good reasons for a package split.
diff --git a/nm-templates/nm_ts2.txt b/nm-templates/nm_ts2.txt
index cafcb82..d91d242 100644
--- a/nm-templates/nm_ts2.txt
+++ b/nm-templates/nm_ts2.txt
@@ -44,8 +44,6 @@ AL2. What is an autobuilder? Where can you find information
about your
package's build status on different architectures? What can you do
if you think there is a problem with the autobuilder?
-AL3. How does a porter handle a rebuild?
-
AL4. Tell me the differences between /usr/share and /usr/lib.
What would you do if you had a package which includes a mix of
architecture-dependent and architecture-independent files?
Ciao,
Enrico
--
GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enr...@enricozini.org>
signature.asc
Description: Digital signature
