[Nm-templates-discuss] templates nm_ts1.txt, 1.2, 1.3 nm_ts2.txt,
1.2, 1.3 nm_ts.doc.txt, 1.15, 1.16
he at haydn.debian.org
he at haydn.debian.org
Wed Aug 17 19:57:43 UTC 2005
Update of /cvsroot/nm-templates/templates
In directory haydn:/tmp/cvs-serv9670
Modified Files:
nm_ts1.txt nm_ts2.txt nm_ts.doc.txt
Log Message:
Commit changes done by Myon, mostly whitespace, punctuation and ortography
fixes. No changes to the actual content were done.
Index: nm_ts1.txt
===================================================================
RCS file: /cvsroot/nm-templates/templates/nm_ts1.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- nm_ts1.txt 19 Jul 2005 21:39:06 -0000 1.2
+++ nm_ts1.txt 17 Aug 2005 19:57:40 -0000 1.3
@@ -3,24 +3,26 @@
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
+time in 3 steps. These steps are 2 parts of questions together with a
severe check of your package(s).
-There is also a place where you can go and upload your package. The
-archive at that site works exactly the same as the Debian archive, in
-fact it uses the same software behind the scene. So you can take this as
+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. So you can take this as
the opportunity to get used to uploads and the stuff that happens with
-your packages, you are not just left alone after your NM without any
+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 you uploaded to that archive and check that. So please take the
-time until then and prepare the best package out of it. :)
+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. :)
+
Finally, the first half of the questions:
@@ -33,19 +35,19 @@
1. Please explain me what a virtual package is. Where can you find a
list of defined virtual packages?
- 2. What does it mean for a package to have a line like
+ 2. What does it mean for a package to have a line like
"Architecture: i386 alpha powerpc" in the control file?
Do you have to provide binary packages for all these
- architectures if you upload your package?
+ architectures when you upload your package?
What is the difference between "Architecture: all" and
"Architecture: any"?
3. How do you manage new upstream releases?
- 4. There is a bug in your package, fixed in Upstream CVS/development
+ 4. There is a bug in your package, fixed in upstream's CVS/development
branch. What do you do with it?
- 5. What do you do if Upstream releases a tarball once every year and
+ 5. 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?
@@ -56,25 +58,24 @@
8. Explain the difference between Depends, Recommends and Suggests.
- 9. How does Debian handle run levels?
- What runlevels are related? How does this interact with users' local
- modifications?
- What should packages which require starting up and shutting down
- (like daemons do) do?
+ 9. How does Debian handle run levels? What runlevels are related? How does
+ this interact with the user's local modifications? What should packages
+ which require starting up and shutting down (like daemons do) do?
A. Tell me the differences between /usr/share and /usr/lib.
B. Please list some good reasons for a package split.
C. What would you need to do if upstream changed the name of the
- application? What would you do to assure smooth upgrades?
+ application? What would you do to assure smooth upgrades?
D. What is Pre-depends for? Why should you avoid it?
- E. a. Have you ever written a man page? If so, please tell me which. If not,
+ E. a. Have you ever written a manpage? If so, please tell me which. If not,
please take a look at http://qa.debian.org/man-pages.html and
choose a package listed there. Then please write a man page for it,
submit it to the BTS and tell me the bug number for it please.
+
b. Please look at http://bugs.debian.org/release-critical/debian/all.html,
choose a bug listed there (please try to find one older than a few
days), try to create a patch to fix it and submit this patch to
Index: nm_ts2.txt
===================================================================
RCS file: /cvsroot/nm-templates/templates/nm_ts2.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- nm_ts2.txt 2 Feb 2005 11:45:46 -0000 1.2
+++ nm_ts2.txt 17 Aug 2005 19:57:40 -0000 1.3
@@ -1,7 +1,7 @@
$Id$
$Revision$
-Nice, we finished with the first half of the T&S Question set. Let's go
+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.
@@ -20,18 +20,20 @@
6. What would you do if your package contains an Emacs major mode?
If you don't use/know Emacs then this: What would you do if your
- package contains a perl module? Or if it is python?
- No Emacs, no Perl, no Python? Go away. Or tell me what to do if you package
- something Java related. :)
+ package contains a perl module? Or if it is python? No Emacs, no Perl,
+ no Python? Go away. Or tell me what to do if you package something Java
+ related. :) Where would you look for more information on that?
- 7. How does Debian maintain consistency between different Windowmanager menus?
+ 7. How does Debian maintain consistency between different window manager
+ menus?
8. a. What are base, standard, optional and extra? Why are they useful?
+
b. What is Essential: yes? Why isn't libc Essential? Why isn't the
- kernel? Why can't libc be essential? Why does libc not need to be
+ kernel? Why can't libc be essential? Why does libc not need to be
essential?
- 9. What does the "urgency" field in changelog affect? When would you use
+ 9. What does the "urgency" field in changelog affect? When would you use
which urgency?
A. What are maintainer scripts? What arguments does each get?
@@ -41,14 +43,15 @@
B. How does a porter handle a rebuild?
C. a. If you want to sponsor a package upload, what do you need to do?
+
b. 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
+ .changes file as it would look if you're sponsoring the upload
of this package.
D. What is the difference between experimental and unstable?
E. What would you do if you had a package which includes a mix of
- Architecture-dependent and architecture-independent files?
+ architecture-dependent and architecture-independent files?
F. Dpkg does not support versioned provides.
Explain what that means, and list common workarounds.
@@ -57,29 +60,29 @@
on. Tell me which and why.
H. What build target would you use in debian/rules to build a package
- which includes only Non-architecture-dependent files? What is the
+ which includes only non-architecture-dependent files? What is the
"Architecture:" section for this package?
I. Fundamental runtime linker knowledge:
- I0. What are library sonames, and what are they used for? What is the
+ I0. What are library sonames, and what are they used for? What is the
"ELF" format?
- I1. How does the utility "fakeroot" work? How is that tied to
+ I1. How does the utility "fakeroot" work? How is that tied to
LD_PRELOAD, and the runtime linker?
-
- I2. What is a symbol-versioned library? Why are libdb2, libdb3 and libc6
- compiled using symbol versioning? What problems does symbol-versioning
+
+ I2. What is a symbol-versioned library? Why are libdb2, libdb3 and libc6
+ compiled using symbol versioning? What problems does symbol-versioning
solve?
- I3. What is the -Bsymbolic ld flag, exactly what does it do, and how
- that differs from library symbol versioning? What problems do
- -Bsymbolic linking solve? Why is libc6 not compiled with
- -Bsymbolic?
+ I3. What is the -Bsymbolic ld flag, exactly what does it do, and how
+ that differs from library symbol versioning? What problems do
+ -Bsymbolic linking solve? Why is libc6 not compiled with -Bsymbolic?
J. What is endianess and why does it matter when supporting multiple
architectures?
+
You are finished with the questions. As I already announced with my
-first T&S mail, I will check your package after you answered the
+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 names of your packages.
+archive at dak.ganneff.de and tell me the name of your package(s).
Index: nm_ts.doc.txt
===================================================================
RCS file: /cvsroot/nm-templates/templates/nm_ts.doc.txt,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- nm_ts.doc.txt 20 Sep 2002 23:40:55 -0000 1.15
+++ nm_ts.doc.txt 17 Aug 2005 19:57:40 -0000 1.16
@@ -3,19 +3,20 @@
Next I have some Questions and Tasks for you. This will form one part of
your T&S Check. The other check is a summary, which I will request from the
people who are working with you. If you haven't already, then please
-tell me their Names and Email Addresses. (This means people working
-with you on Debian and Documentation related stuff, not people at your
+tell me their names and email addresses. (This means people working
+with you on Debian and documentation related stuff, not people at your
paid job).
+
First we have to check that you already doing work as a documentation
maintainer. There are different ways to show me this:
a. Tell me your cvs account name you have for the web and DDP
work. Then I can check your work there.
- b. If you dont have a cvs account at cvs.debian.org then please point
+ b. If you don't have a cvs account at cvs.debian.org then please point
me to the messages in the mailinglist archive with your patches to
- the Documentation/Webstuff.
- c. At a last point you can point me to bugreports where you send
+ the documentation/web stuff.
+ c. At a last point you can point me to bugreports where you sent
documentation related patches to different packages.
If you are not able to answer at least one point of this then I will
@@ -23,10 +24,11 @@
things before we go on with your application, because there is already
a good framework for non-DD to work on documentation related things.
-Also, if you have filed bugreports (with patches) to the BTS with
+Also, if you have filed bug reports (with patches) to the BTS with
respect to documentation, please tell me the bug numbers, so I can
check them.
+
And now, some quick questions:
0. What is the best way to check that your Build-Depends Line contains
@@ -58,27 +60,28 @@
10. What is the difference between experimental and unstable?
11. What would you do if you had a package which includes a mix of
- Architecture-dependant and Non-architecture-dependant files?
+ architecture-dependant and non-architecture-dependant files?
12. There is a minimal set of packages you never need to Build-Depend
on. Tell me which and why.
13. What build target would you use in debian/rules to build a package
- which includes only Non-architecture-dependant files? What is the
+ which includes only non-architecture-dependant files? What is the
"Architecture:" section for this package?
14. Explain within 5 lines what "locale" technology means to you and
point us to the best documentation on the subject for Debian.
-
+
15. What default locale do you set before building a documentation
package?
16. Does ASCII code include so called high-bit characters?
- 17. What is ISO-8859-15? UTF8? Unicode?
+ 17. What is ISO-8859-15? UTF-8? Unicode?
-After these basic packaging related Questions comes some documentation
-related stuff. (The above are true basics, so you should be aware of this.)
+
+After these basic packaging related questions comes some documentation
+related stuff. (The above are true basics, so you should really know this.)
Here we check your knowledge in SGML and all related
tools/concepts. This includes pure SGML, but also DocBook, Stylesheets,
@@ -88,19 +91,19 @@
- Please choose one Debian subsystem, and document it throughoutly.
# Please document the Debian subsystem XY throughoutly. #
You can choose one of three target audiences for your work: novice
- user, advanced user, or Debian developer. Be warned that the
- documentation for novice users must actually teach them the chosen
+ user, advanced user, or Debian developer. Be warned that the
+ documentation for novice users must actually teach them the chosen
topic _in depth_.
- The document should be written using the SGML or XML DocBook DTD. It
+ The document should be written using the SGML or XML DocBook DTD. It
should be transformed (using the toolset of your choice among those in
Debian stable) into: high quality PDF, high quality PostScript,
W3C-compliant HTML document (in two variants: as a single large file,
and as smaller hyperlinked files), and properly formatted plain text.
-
+
The document must include at least one table, at least one image or
diagram, a TOC, an index, and one item of out-of-band information
- (footnote or margin note). You are expected to make proper use of
+ (footnote or margin note). You are expected to make proper use of
these: they must fit well within the whole document.
You should use the DDP for this work, so I can check your skills in
@@ -108,6 +111,7 @@
need to get your working directory from the CVS on my system. (Using
CVS over SSH of course).
+
Now we have checked that you are able to write good documentation. But
that's not all, we have to check if you are able to summarize technical
documents, so you will have to write two manual pages.
@@ -120,40 +124,41 @@
The second manpage should be for a binary without a manpage in the
Debian System. You can freely choose which tool you want to
- document. If the manpage is rather short, you should write manpages
+ document. If the manpage is rather short, you should write manpages
for two or more utilities. For a list of binaries without manpages
- you can look at the lintian site.[1]
+ you can look at the lintian site [1].
This manpage(s) then should be submitted to the maintainer of the
- package using the BTS, with a proper filed bug-report.
-
+ package using the BTS, with a properly filed bug report.
+
You can use any of the available toolsets (bonus points if you can do
it in SGML and generate a HTML version of the manpage as well) in
Debian stable.
After all this, we still have something to check. First there is the
-usage of Gnupg. As I request that all of your e-mail messages to me
-be signed with Gnupg, you must have at least a basic knowledge of Gnupg
+usage of GnuPG. As I request that all of your e-mail messages to me
+be signed with GnuPG, you must have at least a basic knowledge of GnuPG
(or a good mailreader where it works out of the box). To show me a bit
more of your knowledge I ask you to do the following things:
g1. Take a (small) binary file and create a gpg signature for it.
Send me both.
- g2. Do the same thing, this time for an Ascii File, clearsigned.
+ g2. Do the same thing, this time for an ASCII file, clearsigned.
- g3. Encrypt the Ascii File to my personal Key.
+ g3. Encrypt the ASCII file to my personal key.
g4. I will send you an encrypted file with a short message in. Please
decrypt that and send me the message (signed and encrypted mail).
-Next check is about SSH. There is no way to live without it today, So
+
+The next check is about SSH. There is no way to live without it today, so
you really should read the documentation that comes with it if you are
not familiar with SSH. Here are some questions for you to answer about
SSH.
- s1. Discuss the advantages and disadvantages of SSH Public Key
- Authentication compared with the "traditional" password
+ s1. Discuss the advantages and disadvantages of SSH public key
+ authentication compared with the "traditional" password
authentication.
s2. What are some advantages of SSH, compared to other remote login
@@ -166,7 +171,8 @@
I will send you a hostname then. You have to connect there and
create a few files.
- s5. Should you use things like GnuPG over a SSH Connection? Why?
+ s5. Should you use things like GnuPG over a SSH connection? Why?
+
The last (for now) check is about the BTS. You have to know how to use it.
This is easy for you: If you submitted the manpages correctly using the
@@ -174,5 +180,6 @@
done with this. If not, be prepared for some more questions in one of my
next mails.
-[List of URLS]
+
+[List of URLs]
[1] http://lintian.debian.org/reports/Tbinary-without-manpage.html
More information about the Nm-templates-discuss
mailing list