Split the Developer's Duties chapter in two

One part on the technical work and one part on the administrative side.

Put the technical work first because that's the most interesting part
for the reader.

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@8577 313b444b-1b9f-4f58-a734-7bb04f332e8d

diff --git a/developer-duties.dbk b/developer-duties.dbk
index f09e3cf09ab1002607f9813a2cd312c55a79f16d..a8eb5b1d4572af81d4032326937d7ad2f96b64bd 100644 (file)
--- a/developer-duties.dbk
+++ b/developer-duties.dbk
@@ -5,6 +5,22 @@
 ]>
 <chapter id="developer-duties">
 <title>Debian Developer's Duties</title>
+
+<section id="package-maintainer-duties">
+<title>Package Maintainer's Duties</title>
+<para>As a package maintainer, you're supposed to provide
+high-quality packages that are well integrated
+in the system and that adhere to the Debian Policy.</para>
+
+
+</section>
+
+<section id="administrative-duties">
+<title>Administrative Duties</title>
+<para>A project of the size of Debian relies on some administrative
+infrastructure to keep track of everything. As a project member, you
+have some duties to ensure everything keeps running smoothly.</para>
+
 <section id="user-maint">
 <title>Maintaining your Debian information</title>
 <para>
@@ -214,6 +230,7 @@ RT' somewhere in the subject line (case doesn't matter).
 </listitem>
 </orderedlist>
 </section>
+</section>
 
 </chapter>