[Nm-templates-discuss] templates dak.txt,1.1,1.2 nm_advocate.txt,1.1,1.2 nm_assigned.txt,1.21,1.22 nm_pp1.txt,1.2,1.3 nm_pp2.txt,1.4,1.5
joerg@haydn.debian.org
joerg@haydn.debian.org
Update of /cvsroot/nm-templates/templates
In directory haydn:/tmp/cvs-serv21028
Modified Files:
dak.txt nm_advocate.txt nm_assigned.txt nm_pp1.txt nm_pp2.txt
Log Message:
A patch from Christoph Berg
Index: dak.txt
===================================================================
RCS file: /cvsroot/nm-templates/templates/dak.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- dak.txt 19 Dec 2004 20:32:52 -0000 1.1
+++ dak.txt 15 Feb 2005 20:11:32 -0000 1.2
@@ -1,4 +1,4 @@
-I have changed my ways to check packages from my Applicants a bit.
+I have changed my ways to check packages from my applicants a bit.
I now require every applicant to upload their package(s) to the
archive at dak.ganneff.de.
@@ -6,23 +6,22 @@
the tools and procedures used by Debian. So, you really should do it for
your own benefit, beside of that it makes life easier for me.
-You will get a mail from that archive, telling you your account-name and
+You will get a mail from that archive, telling you your account name and
password there. Only after you got this mail your uploads will be
-accepted, everything else will be rejected, so please wait until you got
+accepted, everything else will be rejected, so please wait until you get
it.
You can use this login to look how the archive works. For example you
can run "madison PACKAGENAME", replace PACKAGENAME with a package that
-exists there, to see some information about it.
-Or helena, to see if there are packages in NEW.
-Please do not use this machine for anything else!
+exists there, to see some information about it. Or helena, to see if
+there are packages in NEW. Please do not use this machine for anything
+else!
-It is running the same software that the Debian Archive is using.
-This way you can now play with the tools and learn, without a risk of
-damaging something in the official archive.
-For now it means a bit more work, but in the end you are not left
-without any knowledge on how to upload packages after you maybe get
-approved.
+It is running the same software that the Debian Archive is using. This
+way you can now play with the tools and learn, without a risk of
+damaging something in the official archive. For now it means a bit more
+work, but in the end you are not left without any knowledge on how to
+upload packages after you (hopefully) get approved.
You need either dupload or dput, whatever you like more. The following
are the config snippets you have to put in your configuration for the
@@ -43,7 +42,7 @@
$cfg{ganneff_app} = {
fqdn => "dak.ganneff.de",
incoming => "./",
- login => "dak",
+ login => "dak",
dinstall_runs => 1,
};
@@ -53,7 +52,7 @@
dput ganneff_app changesfile
or
dupload -t ganneff_app changesfile
-.
+
Hints:
It works exactly as the Debian Archive, with all its checks,
@@ -72,7 +71,6 @@
- If it is already known, it is installed into the pool.
- If it was NEW and it gets accepted, it gets installed into the pool.
-
- You get mails from the archive system, telling you what is going on
with the package. Read them and maybe correct your actions, or ask for
help if you are lost.
@@ -87,7 +85,6 @@
your uploads and to polish your package(s).
If you want you can subscribe to the mailinglists dak-bcc and dak-nm at
-http://lists.jj21.de/mailman/listinfo
-The dak-bcc list gets every mail the Archive sents out as a Bcc, the
-dak-nm list is similar to the debian-devel-changes@lists.debian.org
-list.
+http://lists.jj21.de/mailman/listinfo . The dak-bcc list gets every mail
+the Archive sents out as a Bcc, the dak-nm list is similar to the
+debian-devel-changes@lists.debian.org list.
Index: nm_advocate.txt
===================================================================
RCS file: /cvsroot/nm-templates/templates/nm_advocate.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- nm_advocate.txt 6 Jan 2005 22:16:06 -0000 1.1
+++ nm_advocate.txt 15 Feb 2005 20:11:32 -0000 1.2
@@ -9,8 +9,8 @@
2) How he handles his tasks
3) How he handles problems
4) His social skills (How does he treat users? Other developers?)
- 4) Whether he is reliable or not
+ 5) Whether he is reliable or not
-(Your reply will probably get included verbatim in the final report)
+(Your reply will probably get included verbatim in the final report.)
-I thank you in advance for your answers.
+I thank you in advance for your answer.
Index: nm_assigned.txt
===================================================================
RCS file: /cvsroot/nm-templates/templates/nm_assigned.txt,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- nm_assigned.txt 25 Jan 2005 20:39:00 -0000 1.21
+++ nm_assigned.txt 15 Feb 2005 20:11:32 -0000 1.22
@@ -21,6 +21,7 @@
Application Manager (AM) assigned. You have completed the first step.
Now it's time to check your identity.
+
1. Please send me the keyid of your GPG public key so I can fetch it
from a keyserver. If your GPG key is not on a public keyserver, please
upload it to subkeys.pgp.net. If your GPG key is signed by a Debian
@@ -44,24 +45,25 @@
you that would agree to meet you and sign your key.
Although it is sufficient that you have just one signature from an
-existing Debian developer, it is strongly advised to get multiple
-signatures on your key so that your key becomes "strongly connected."
-You may check the status of your key at:
+existing Debian developer, it is strongly advised to get more
+signatures on your key so that your key becomes better connected to
+the web of trust. You may check the status of your key at
http://www.cs.uu.nl/people/henkp/henkp/pgp/pathfinder/
by entering your key ID in the statistic box. If it complains it can't
find your key, and you are sure you have entered the correct key ID, it
-means that you are not in the strong set of keys.
+means that you are not in the strong connected set of keys.
Please sign all mail to me. It's not that I'm paranoid about security,
it's just a good habit to get in to, and it shows me that you know
how.
+
2. The DAM needs some data to create your account, so please tell me
- - the preferred account name for the Debian machines
+ - the preferred account name for the Debian machines, and
- the email address to which Debian mail should be forwarded.
-Please make sure that the account name is still free -- visit
+Please make sure that the account name is still free -- visit
http://db.debian.org/ to find out if this is the case. After your
account was created, you can use the CGIs available there to
change the data that is kept about you in the Debian LDAP.
@@ -75,6 +77,7 @@
mailing list so other developers can get to know you. Please indicate
which parts I may publish and which not.
+
If you have packaged an application for Debian already, please take
another deep look into it, eliminating any error you may find. When we
start with the "Tasks and Skills" checks, you will get more information
@@ -97,6 +100,7 @@
and Procedures" -- I will ask you a few questions by e-mail which you
will need to answer. This will inevitably lead to a discussion about
Debian's goals and core beliefs as well as the way we do things.
+
Finally, thanks for volunteering! Debian is a volunteer effort and
you can make a difference!
Index: nm_pp1.txt
===================================================================
RCS file: /cvsroot/nm-templates/templates/nm_pp1.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- nm_pp1.txt 15 Jan 2005 16:16:19 -0000 1.2
+++ nm_pp1.txt 15 Feb 2005 20:11:32 -0000 1.3
@@ -2,24 +2,24 @@
$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],
+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].
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 to go on), so the more you can tell
+communications (no packages or keys involved), so the more you can tell
me (which means the less prodding replies), the better. :)
First, please explain the key points of the Social Contract and the
-DFSG _in your own words_. Also, describe what you personally think
+DFSG _in your own words_. Also, describe what you personally think
about these documents.
Secondly, a few questions, based on them:
- 0. What is Debian's approach to non-free software? Why? Is non-free
+ 0. What is Debian's approach to non-free software? Why? Is non-free
part of the Debian System?
1. Suppose that Debian were offered a Debian-specific license to
@@ -27,20 +27,20 @@
2. Donald Knuth, author of TeX, insists that no-one has the right to
modify the source code of TeX, and that any changes must be made using
- "change files" (a sort of patch file). Is this allowed for a program
+ "change files" (a sort of patch file). Is this allowed for a program
for the main section of Debian?
3. Do you know (and can you explain) the difference between free speech
- and free beer? Is Debian mainly about free speech or free beer?
+ and free beer? Is Debian mainly about free speech or free beer?
4. What are the sections of Debian software and the differences between
- them? How would you decide where to put a new package?
+ them? How would you decide where to put a new package?
5. At http://people.debian.org/~joerg/bad.licenses.tar.bz2 you can
find a tarball of bad licenses. Please compare the graphviz and three
other (your choice) licenses with the first nine points of the DFSG
and show what changes would be needed to make them DFSG-free.
- There's no need to compare word for word (which would be impossible
+ There's no need to compare word for word (which would be impossible
for some licenses anyway), but you should spot the biggest mistakes.
5a. The GNU Free Documentation License (FDL) has been heavily discussed
@@ -50,27 +50,27 @@
licensed under the FDL in main and what the consequences of this
position might be for Debian.
-5b. How do *you* check if a license is DFSG-compatible?
+5b. How do *you* check if a license is DFSG-compatible?
-5c. There are a few "tests" for this purpose, they are based on [not
- really] common situations. Do you know one (or more) of these?
- Explain it/them to me and point out which common problems can be
- discovered by it/them.
+5c. There are a few "tests" for this purpose, based on (not really) common
+ situations. Do you know one (or more) of these? Explain it/them to me
+ and point out which common problems can be discovered by it/them.
6. Are there any sections of the DFSG or Social Contract that you
might like to see changed? If so, which ones, and why?
+
Do you agree to uphold the Social Contract and the DFSG in your Debian
work?
If you are accepted as a Debian developer, you will get accounts
-on the Debian machines. Have you read the Debian Machine Usage
-Policies (DMUP) at http://www.debian.org/devel/dmup ? Do you
+on the Debian machines. Have you read the Debian Machine Usage
+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
-GPG, please don't forget this), I will go over your answers. If all is
-satisfactory, I will give you phase II of the P&P test.
+GPG, 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.
URLs:
Index: nm_pp2.txt
===================================================================
RCS file: /cvsroot/nm-templates/templates/nm_pp2.txt,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- nm_pp2.txt 14 Jan 2005 23:05:18 -0000 1.4
+++ nm_pp2.txt 15 Feb 2005 20:11:32 -0000 1.5
@@ -1,13 +1,13 @@
$Id$
$Revision$
-So now we are done with the first half of P&P lets go on to the second
+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.
-I'm sure you have read the Documents I mentioned in the first half of
-P&P. They should help you to answer these questions, but you may also
+I'm sure you have read the documents I mentioned in the first half of
+P&P. They should help you to answer these questions, but you may also
look at the bottom of this mail, where I list a few other URLs to help
you.
@@ -23,9 +23,10 @@
them?
4. How do tags and severities affect the release status of a debian package?
+ Please also give a short explanation about the other tags.
5. Where can you find the list of defined BTS pseudo packages?
- Explain to me what a Pseudo Package is.
+ Explain to me what a pseudo package is.
6. You just discovered a bug in many packages. What are your next
steps?
@@ -39,7 +40,7 @@
9. How do you check a package before you upload? Please explain to me
why and how you perform the checks.
-10. What does version 2:3.4-2.1 mean? What Debian control file would you
+10. What does version 2:3.4-2.1 mean? What Debian control file would you
put this in?
11. You have a new package, and you finally find that it will be in
@@ -50,21 +51,22 @@
administrator for local settings, how do you make sure your next version
of the package doesn't overwrite it?
-13. What is an autobuilder? Where can you find information about your
+13. 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?
14. There are many Debian suites, like "stable", "unstable", "testing",
- "woody", "sarge" and "sid". Can you explain why there are so many
- and what the differences are? How does a package get from one to
- the other?
+ "woody", "sarge" 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?
15. How can you ensure your package's description is in a good state and
in a valid format?
-16. What should you do if a security bug is discovered in one of your packages?
+16. What should you do when a security bug is discovered in one of your
+ packages?
-17. Imagine you maintain a package which depends very closely to some
+17. Imagine you maintain a package which depends very closely on some
other package. How would you keep track of the development of other
packages, even if you are not the maintainer?
@@ -96,18 +98,18 @@
25. At regular intervals, we arrange the so called "Bug Squashing Parties".
What are they good for and what happens during such a BSP?
-26. Although english is doubtless the "lingua franca" nowadays, which means
- that it is nearly everywhere understood, there are still some users who
- can't understand it properly. Which efforts does the Debian project make
+26. Although English is doubtless the "lingua franca" nowadays, which means
+ that it is understood nearly everywhere, there are users who do not
+ understand it properly. Which efforts does the Debian project make
to help these people?
27. Please list some tasks that belong to the scope of duties of the Debian
Quality Assurance group.
28. What does the version string in the Standards-Version field of a
- package's control file represent? Why is it useful?
+ package's control file represent? Why is it useful?
-29a. If one of your packages had serious problems like that either
+29. If one of your packages had serious problems like that 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
want maintain it
@@ -116,9 +118,9 @@
to be included in Debian.
How would you proceed in this cases?
-29b. You can't/wont maintain a package properly anymore because
- you have a lack of time/don't use it anymore. What are your
- options to handle this situation?
+30. You can't/wont maintain a package properly anymore because
+ you have a lack of time/don't use it anymore. What are your
+ options to handle this situation?
A word on mailing lists: there are quite a lot of Debian mailing lists
now as well as packaging-related packages, and I'd just like to check with
@@ -130,26 +132,26 @@
These two lists are must-subscribes. Everything else is optional. I
abbreviate 'debian-' to '-' from now on.
--security-announce:
- security updates to stable
+-security-announce: security updates to stable
-private: you'll be subscribed automatically when your new-maintainer
application is accepted (but you can unsubscribe if you wish);
the list is used for sensitive discussions, etc.
-devel: general mailing list for developer issues
-policy: where possible changes to debian-policy are discussed
--mentors: helping newbie Developers.
+-mentors: helping newbie Developers and maintainers.
-project: project related discussions
There are many others; check the mailing list page on the web site
for details.
-Now lets take a look at some important packages for a (upcoming) Debian
+
+Now lets take a look at some important packages for a upcoming Debian
Developer. There are many of them, I will try to list the more important
ones.
build-essential
A package that depends on all the packages in the build
- essential list. It's useful to make sure everything in the list
+ essential list. It's useful to make sure everything in the list
is installed on the system when building and testing your own
packages.
dpkg-dev All of the primary tools needed to put a Debian package
@@ -159,10 +161,10 @@
But you should be able to build a package without it.
debian-policy
Describes the policy relating to packages and details of
- the packaging mechanism. Covers everything from
+ the packaging mechanism. Covers everything from
required gcc options to the way the maintainer scripts
(postinst etc.) work, package sections and priorities,
- etc. An absolute must-read. Also useful is the file
+ etc. An absolute must-read. Also useful is the file
/usr/share/doc/debian-policy/upgrading-checklist.txt.gz,
which lists changes between versions of policy.
You must read and understand it.
@@ -196,20 +198,20 @@
Finally, some important web links:
http://www.debian.org/devel/
- The Developer's Corner. Contains links and on-line versions
+ The Developer's Corner. Contains links and on-line versions
of the stuff I mentioned before.
http://db.debian.org/
Queries about developers and machines
http://www.debian.org/devel/wnpp/
- The Work Needing and Prospective Packages list. Sort of a
+ The Work Needing and Prospective Packages list. Sort of a
big TODO list for Debian packaging stuff: what's orphaned,
what needs new maintainers, what's being adopted, what's
being packaged and what would be nice to have packaged.
http://qa.debian.org/
- The Debian Quality Assurance headquarters. Help is appreciated!
+ The Debian Quality Assurance headquarters. Help is appreciated!
http://bugs.debian.org/
Bug related info