NM process reference in NM guide
Hi,
After reading bug report (#331176), I realized NM guide had a tone of
old days when becoming DD was much simpler.
I hereby propose patch to maint-guide (NM guide) as attached along what
was reported by #331176.( http://bugs.debian.org/331176 )
This also fixes few points on debmake removal and new debhelper behavior.
(I will separate URL to default.ent but I left them in test for easy
review.)
I think we can improve situation a bit more if mpalmer includes
<list>...</list> part into his FAQ page as something like executive
summary and I removing it from this text since having too many URL
references in this kind of document are usually cause of broken links.
I want to keep this document as stable as possible.
Mathew, what do you think?
Osamu
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
Osamu Aoki <osamu@debian.org> Yokohama Japan, GPG-key: A8061F32
.''`. Debian Reference: post-installation user's guide for non-developers
: :' : http://qref.sf.net and http://people.debian.org/~osamu
`. `' "Our Priorities are Our Users and Free Software" --- Social Contract
Index: maint-guide.sgml
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/maint-guide/maint-guide.sgml,v
retrieving revision 1.98
retrieving revision 1.99
diff -u -r1.98 -r1.99
--- maint-guide.sgml 24 Sep 2005 15:27:55 -0000 1.98
+++ maint-guide.sgml 7 Jan 2006 14:37:11 -0000 1.99
@@ -5,7 +5,7 @@
<!ENTITY % default SYSTEM "default.ent"> %default;
]>
-<!-- CVS revision of this document "$Revision: 1.98 $" -->
+<!-- CVS revision of this document "$Revision: 1.99 $" -->
<!-- CVS revision of original english document "*.**" -->
<debiandoc>
@@ -211,9 +211,76 @@
<p>Note: <package/debmake/ is a package that contains some programs that
function similar to dh-make, but its specific use is <strong>not</strong>
- covered in this document, because it is <em>deprecated</em>. Please refer
- to <url name="the Debmake manual" id="http://www.debian.org/~jaldhar/";>
- for more information.
+ covered in this document, because it is <em>deprecated</em>.
+
+ <sect id="debiandeveloper">Official Debian Developer
+
+ <p>After you build your package (or while doing that), you may want to
+ become an official Debian Developer to get your new package into the
+ next distribution (if the program is useful, why not?).
+ <p>
+ You can not become an official Debian Developer over night because it
+ takes more than technical skill. Please do not be discouraged by this,
+ you can still upload your package, if useful to others, now through
+ a sponsor who is an official Debian Developer while applying yourself
+ to <url name="the Debian New Maintainer process" id="http://nm.debian.org/";>.
+ <p>
+ Here is an outline for how to become an official Debian maintainer
+ by packaging a new package.
+ <list>
+
+ <item>Discover that it isn't packaged and available in the Debian archive.
+
+ <item>Check <url name="Work-Needing and Prospective Packages" id="http://www.debian.org/devel/wnpp/";>
+ if it can be packaged and if it is already being packaged.
+
+ <item>Decide if you still want to package and maintain it.
+ A good way to decide this is to check if upstream development is active,
+ to do a licensing review and review the code to make sure you can fix it.
+ <footnote>
+ If you don't want to package it, file an RFP (request for packaging) bug
+ using the reportbug utility against the wnpp package.
+ If you don't want to maintain it, find someone who does. Unmaintained
+ packages are very annoying for the Debian Quality-Assurance and Release
+ Management groups and for Debian's users.
+ </footnote>
+
+ <item>File an ITP (intent to package) bug using the reportbug utility against
+ the wnpp package. This is done in order to prevent duplication of effort
+ (an essential step).
+
+ <item>Create the package using the rest of this document as a guide.
+ If it does not cover the kind of software, documentation or data you
+ are packaging, use a similar package as an example and or read the
+ <url name="developers reference" id="http://www.debian.org/doc/developers-reference/";>
+ and other developer documentations.
+
+ <item>Install and test your package thoroughly. Ask someone on the
+ <url name="debian-mentors" id="http://lists.debian.org/debian-mentors/";>
+ list to check your packaging for errors and common problems.
+
+ <item>Upload your package somewhere. One recommended site is
+ <url name="mentors.debian.net" id="http://mentors.debian.net";>.
+
+ <item>Register your need for a sponsor on
+ <url name="sponsors.debian.net" id="http://sponsors.debian.net";>
+
+ <item>
+ <url name="Search for a sponsor" id="http://people.debian.org/~mpalmer/debian-mentors_FAQ.html#sponsored_packages";>
+ to upload it to the Debian archive for you.
+
+ <item>After keeping your package bug-free and up-to-date in Debian for a
+ while, you may want to
+ <url name="apply to become a Debian Developer" id="http://www.debian.org/devel/join/";>.
+
+ </list>
+
+ <p>More details of this procedure are explained in the
+ <url id="http://people.debian.org/~mpalmer/debian-mentors_FAQ.html"; name="debian-mentors FAQ">.
+
+ <p>Please note that you do not need to create any new package to
+ become an official Debian Developer. Contributing to the existing packages
+ can provide a path to become an official Debian Developer too.
<sect id="otherinfo">Other information
@@ -231,10 +298,6 @@
If you made a program, and want it to get in Debian, feel free to submit
your application to become a maintainer.
- <p>After you build your package (or while doing that), you will have
- to become an official Debian maintainer if you wish your program to get
- into the next distribution (if the program is useful, why not?).
- That process is explained in Developer's Reference. Please read it.
<chapt id="first">First steps
@@ -481,7 +544,7 @@
<p>This temporary directory is usually created under your debian/
directory in the unpacked source tree. It is usually called
- <file>debian/tmp</file> or <file>debian/packagename</file>.
+ <file>debian/packagename</file>.
<p>Bear in mind that even though you need to make the program install in
debian/packagename, it still needs to behave correctly when placed in the
Reply to: