[Nm-templates-discuss] templates nm_pp1.txt, 1.10, 1.11 nm_pp2.txt,
1.14, 1.15 nm_ts1.txt, 1.6, 1.7 nm_ts2.txt, 1.9, 1.10
myon at alioth.debian.org
myon at alioth.debian.org
Mon Jan 1 17:08:13 CET 2007
Update of /cvsroot/nm-templates/templates
In directory alioth:/tmp/cvs-serv18332
Modified Files:
nm_pp1.txt nm_pp2.txt nm_ts1.txt nm_ts2.txt
Log Message:
update introductions and some misc fixes
Index: nm_pp1.txt
===================================================================
RCS file: /cvsroot/nm-templates/templates/nm_pp1.txt,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- nm_pp1.txt 30 Dec 2006 16:27:30 -0000 1.10
+++ nm_pp1.txt 1 Jan 2007 16:08:11 -0000 1.11
@@ -1,12 +1,13 @@
$Id$
-$Revision$
-OK, here we go with P&P, checking your knowledge of Debian policies and
-procedures. In preparation, you should read the Debian constitution[1],
-Social Contract[2] and the Free Software Guidelines, and finally the
-developer's reference[3] and the current version of Debian policy[4].
-If any questions arise, you should have a look at the draft for a DFSG
-FAQ [5].
+Here comes the first part of P&P, Philosophy and Procedures. The first
+part is about philosophy - what makes free software and Debian free.
+
+In preparation, you should read the Debian Constitution [1], the Social
+Contract and the Free Software Guidelines [2], the Developer's Reference
+[3], and finally the Debian Policy [4]. If any questions arise, you
+should have a look at the DFSG FAQ draft [5]. (If you read any of these
+locally, be sure to fetch the package from unstable!)
[1] http://www.debian.org/devel/constitution
[2] http://www.debian.org/social_contract.en.html
@@ -14,16 +15,26 @@
[4] http://www.debian.org/doc/debian-policy/
[5] http://people.debian.org/~bap/dfsg-faq.html
-After you have done this, please answer the following set of questions
-and try to be quite verbose in your answers. This, and the next half of
-P&P are the main areas that we can only check via your written
-communications (no packages or keys involved), so the more you can tell
-me (which means the less prodding replies), the better. :)
+As we will exchange a lot of mails (usually several dozens!), here are
+some notes to make things easier for us:
-A request: There will usually be several replies and followups to every
-question. If you remove any quoted part, please do not remove the
-numbers of the questions, so we can more easily see what we are talking
-about.
+* Please be verbose in your answers. If in doubt, write one sentence
+ more. Especially in this first part, your written answers are the only
+ way we can check your knowledge (no packages involved). It will save
+ you some prodding replies from me. :)
+* You can reply with URLs, but I would prefer if you could summarize the
+ content in a few words.
+* While we are discussing a question, please do not remove the number of
+ the item from the quoted part so we can more easily see what we are
+ talking about.
+* If you like, reply in several mails. Postponing a message just because
+ you have not yet had time to work on the other half of questions helps
+ neither you nor me.
+* Again, if you have questions: please ask them! I am glad to help you,
+ and sometimes I can even learn something myself.
+
+I'm not going to bore you with the introduction any longer, here's the
+first set of questions:
Philosophy
@@ -84,9 +95,11 @@
Policies (DMUP) at http://www.debian.org/devel/dmup ? Do you
accept them?
-After you have mailed this back to me (you need to sign this mail with
-your OpenPGP key, please don't forget this), I will go over your answers. If
-all is satisfactory, I will send you phase II of the P&P test.
+
+After you have mailed this back to me, I will go over your answers. If
+all is satisfactory, I will send you part 2 of the P&P test. Note that
+the reply to the last two questions here MUST be signed with your
+OpenPGP key as we want your signature on the SC and DMUP.
Interesting URLs
Index: nm_pp2.txt
===================================================================
RCS file: /cvsroot/nm-templates/templates/nm_pp2.txt,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -d -r1.14 -r1.15
--- nm_pp2.txt 30 Dec 2006 16:27:30 -0000 1.14
+++ nm_pp2.txt 1 Jan 2007 16:08:11 -0000 1.15
@@ -1,15 +1,13 @@
$Id$
-$Revision$
-So now we are done with the first half of P&P, lets go on to the second
-half. The next phase of the Policy and Procedures test examines your
-understanding of basic Debian rules and the proper method of interacting
-with Debian resources.
+Lets go on to the second half of the Policy and Procedures test. It
+examines your understanding of basic Debian rules and the proper method
+of interacting with Debian resources.
I assume you have read the documents I had mentioned in the first half
of P&P, they should help you answer the following questions. At the
bottom of this mail I also list some interesting packages and point to
-mailing lists you might want to subscribe to.
+mailing lists you might want to subscribe to.
Bug Tracking System
@@ -63,7 +61,7 @@
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?
+ 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?
Index: nm_ts1.txt
===================================================================
RCS file: /cvsroot/nm-templates/templates/nm_ts1.txt,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- nm_ts1.txt 27 Dec 2006 21:38:55 -0000 1.6
+++ nm_ts1.txt 1 Jan 2007 16:08:11 -0000 1.7
@@ -1,30 +1,32 @@
$Id$
-$Revision$
-Lets go to the next big part of your application - the check of Tasks &
-Skills. Similar to the P&P we just finished it is also splitted, this
-time in 3 steps. These steps are 2 parts of questions together with a
-severe check of your package(s).
+Lets go to the next big part of your application - the check of Tasks
+and Skills. Similar to P&P it is also split, this time in three steps.
+These steps are 2 sets of questions and finally a thorough check of your
+packages.
-There is a place where you can go and upload your package for testing. The
-archive at that site works exactly the same as the Debian archive, as
-it uses the same software behind the scene. You can take this as
-the opportunity to get used to uploads and the stuff that happens with
-your packages, so you are not just left alone after your NM without any
-knowledge what exactly you need to do to get a package into the
-archive.
+There is a place where you can go and upload your package for testing.
+The archive at that site works exactly the same as the Debian archive,
+as it uses the same software behind the scene. You can take this as the
+opportunity to get used to uploads and the stuff that happens with your
+packages, so you are not just left alone after your NM without any
+knowledge what exactly you need to do to get a package into the archive.
For more information please read http://dak.ganneff.de/dak.txt and also
the email you should get in a short timeframe from that archive. It will
tell you your accountname there, and a few other details you may want to
know.
-After we finished the two steps with the questions, I will get the
-package(s) you uploaded to that archive and check that. So please use the
-time until then to prepare the best package(s) you can do. :)
+When we have finished the two steps with the questions, I will have a
+look at your packages. So please use the time until then to prepare the
+best packages you can. :) By the way, I will sponsor uploads for you if
+you like. This of course helps the package check, but will also allow
+me to see how you handle the things we are talking about here in
+practice.
Finally, the first half of the questions:
+
RC Bug Fixing
-------------
@@ -43,7 +45,7 @@
you've found out about the bug in the BTS.
Then prepare, if possible, a NMU and send me a pointer to your NMU patch.
- Do the same thing again for 2 other bugs with severity Important
+ Do the same thing again for 2 other bugs with severity important
or higher. If you couldn't fix a bug, you should send me
the bug numbers of the bugs you tried to fix.
@@ -70,9 +72,9 @@
PF6. What are base, 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?
+PF7. What is Essential: yes? Why isn't libc6 essential and why can't it
+ be? Why does it not need to be essential? Why isn't the kernel
+ essential?
PF8. Explain the difference between Depends, Recommends and Suggests.
Index: nm_ts2.txt
===================================================================
RCS file: /cvsroot/nm-templates/templates/nm_ts2.txt,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- nm_ts2.txt 26 Dec 2006 23:04:33 -0000 1.9
+++ nm_ts2.txt 1 Jan 2007 16:08:11 -0000 1.10
@@ -1,9 +1,7 @@
$Id$
-$Revision$
-Nice, we are finished with the first half of the T&S Question set. Let's go
-on with the second half, which contains additional stuff I want to know
-from you.
+Nice, we are approaching the end! Here's the second half of the T&S
+question set which contains additional stuff I want to know from you.
Package Building and Uploading
@@ -17,13 +15,13 @@
everything required to build your package?
BU4. How do you check a package before you upload? How do you check that
- your package can install, upgrade and remove itself cleanly? Please
- explain to me why and how you perform the checks.
+ your package can install, upgrade and remove itself cleanly? Please
+ explain to me why and how you perform the checks.
BU5. If you want to sponsor a package upload, what do you need to do?
- Please take a random package out of the archive and send me the
- .changes file as it would look if you're sponsoring the upload
- of this package.
+ Please take a random package from the archive and send me the
+ .changes file as it would look if you're sponsoring the upload of
+ this package.
Architectures and Libraries
@@ -80,18 +78,17 @@
Bonus Section
-------------
-ALB1. What is a symbol-versioned library? Why are libdb2, libdb3 and libc6
- compiled using symbol versioning? What problems does symbol-versioning
- solve?
-
-ALB2. What is the -Bsymbolic ld flag, exactly what does it do, and how
- does that differ from library symbol versioning? Which problem does
- -Bsymbolic linking solve? Why is libc6 not compiled with -Bsymbolic?
+ALB1. What is a symbol-versioned library? Why are libdb2, libdb3 and
+ libc6 compiled using symbol versioning? What problems does
+ symbol-versioning solve?
-
+ALB2. What is the -Bsymbolic ld flag, exactly what does it do, and how
+ does that differ from library symbol versioning? Which problem
+ does -Bsymbolic linking solve? Why is libc6 not compiled with
+ -Bsymbolic?
-You are finished with the questions. As I already announced with my
-first T&S mail, I will check your package(s) after you've answered the
-questions above. So please upload the latest and greatest version to the
-archive at dak.ganneff.de and tell me the name of your package(s).
+Whee! That's the end of the questions. As I already announced with my
+first T&S mail, I will check your packages when we are finished here. So
+please upload the latest and greatest packages to the archive or tell me
+where I can find them.
More information about the Nm-templates-discuss
mailing list