X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=web%2Findex.html;h=32f2f82feb9aa0ef533e65a51389ad2cf7fa17a4;hb=fffe7d0517f4d1ab8a15b9e444bcb2fb92b2bd46;hp=db540dcb7b20e1ff109c0a625650526426b2143d;hpb=3148198fab7186b34d4b0d4c2eed088d46e43271;p=dak.git

diff --git a/web/index.html b/web/index.html
index db540dcb..32f2f82f 100644
--- a/web/index.html
+++ b/web/index.html
@@ -35,17 +35,20 @@
         <div id="leftcol">
 		  <ul>
 			<li><a href="#intro">Introduction</a></li>
-			<li><a href="#archivekey">Archive Signing Key</a></li>
+			<li><a href="/keys.html">Archive Signing Key</a></li>
 			<li><a href="#ftpteam">FTP Team</a></li>
 			<li><a href="#dak">dak</a></li>
 			<li><a href="#new">NEW</a></li>
 			<li><a href="#pending">Pending removals</a></li>
 			<li><a href="#removed">Removed packages</a></li>
+			<li><a href="#cruft">Cruft Report</a></li>
 			<li><a href="#testing">Testing</a></li>
 			<li><a href="#stable">Stable</a></li>
 			<li><a href="#rejections">Rejections</a></li>
+			<li><a href="#lintianrejects">Lintian Autorejects</a></li>
 <!--			<li><a href="#dependencies">Unmet Dependencies</a></li>-->
 			<li><a href="#archivecriteria">Archive Criteria</a></li>
+			<li><a href="#talks">Talks</a></li>
 		  </ul>
 		</div>
 
@@ -58,60 +61,62 @@
         <div id="archivekey">
             <h1>Archive signing key</h1>
 
-            <p>The release files are signed by an automatic archive signing key. The
-            2007/etch key can be <a href="archive-key-4.0.asc">downloaded here</a></p>
-
-            <p>The release files are signed by an automatic archive signing key. The
-            new key, to be used after the 4.0 key expires *or* right
-		  after Lenny r1 came out, can be  <a href="archive-key-5.0.asc">downloaded here</a></p>
-		</div>
+            <p>Information on the archive signing keys is available <a
+            href="/keys.html">here</a></p>
+            </div>
 
 		<div id="ftpteam">
             <h1>The ftpmaster team</h1>
 
-            <p>The members of ftpmaster currently are divided into two groups, FTP Master and FTP Assistants.</p>
+	    <p>The members of ftpmaster currently are divided into three groups, FTP Master,FTP Assistants and FTP Trainee.</p>
             <p>Members of FTP Master are:</p>
             <ul>
-                <li>Ryan Murray</li>
                 <li>Joerg Jaspert</li>
+                <li>Mark Hymers</li>
             </ul>
             <p>The FTP Assistants are:</p>
             <ul>
-                <li>Mark Hymers</li>
-                <li>Kalle Kivimaa</li>
 				<li>Frank Lichtenheld</li>
 				<li>Mike O'Connor</li>
+				<li>Alexander Reichle-Schmehl</li>
+				<li>Chris Lamb</li>
+				<li>Barry deFreese</li>
+				<li>Torsten Werner</li>
             </ul>
-            
+
             <p>This information (and more like it) is available from
             <a href="http://www.debian.org/intro/organization">Debian's Organizational Structure</a>.</p>
+
+	    <p>The FTP Master role, unix group <tt>debadmin</tt>, is responsible for:</p>
+	    <ul>
+		    <li>Keep the archive running</li>
+		    <li>Keep the archive legal</li>
+		    <li>Support the teams that depend on it (Release, Security, soon backports/volatile)</li>
+		    <li>Keep the archive uptodate with the requirements of the project</li>
+	    </ul>
+
+	    <p>The FTP Assistent role, unix group <tt>ftpteam</tt>, created in 2005,
+	    allows the addition of people to the FTP Team without having to hand out
+	    full FTP Master rights. It allows</p>
+	    <ul>
+		    <li>to process NEW,</li>
+		    <li>to handle overrides,</li>
+		    <li>to remove packages.</li>
+	    </ul>
+
+	    <p>The FTP Trainee role, group <tt>ftptrainee</tt>, was created in 2008 to allow easy training and testing of future team members.</p>
+            <p>Trainees can look at NEW and do the usual package checks, but they can not actually accept or reject a package. Instead they leave a note, which an Assistant or Master reads and acts on.</p>
         </div>
 
         <div id="dak">
-            <h1>'dak'</h1> 
+            <h1>'dak'</h1>
             <p>dak (Debian Archive Kit) is the collection of scripts that have replaced dinstall and friends.</p>
- 
+
             <p>The source is managed in git and is available
             from: <a href="http://ftp-master.debian.org/git/">http://ftp-master.debian.org/git/</a></p>
-
-		    <p>The old bzr tree is obsolete and no longer available. All
-		  information in it is now in git</p>
-		  
-            <p>The old CVS tree is obsolete but still available for historical purposes.
-            It's at <strong>:pserver:anonymous@cvs.debian.org:/cvs/dak</strong>;
-            the module is 'dak' and the login password is blank.
-            The old CVS repository can be <a href="http://cvs.debian.org/?cvsroot=dak">browsed</a>
-            courtesy of viewcvs.</p>
-
-            <p>You can also install the <a href="http://packages.debian.org/unstable/devel/dak">dak Package</a>
-            if you want to look at it and maybe run your own copy.</p>
-
-            <p>The <strong>really</strong> old dinstall scripts are still available
-            from <strong>:pserver:anonymous@cvs.debian.org:/cvs/ftp-maint</strong>;
-            the modules are 'dinstall' and 'masterfiles'.</p>
         </div>
 
-		<div id="new"> 
+		<div id="new">
             <h1>New Packages</h1>
             <p>New Packages uploaded to the archive, but not yet accepted,
             can be <a href="http://ftp-master.debian.org/new.html">seen here</a>.
@@ -120,6 +125,10 @@
             until the daily cron run moves them into the pool.</p>
         </div>
 
+		<div id="deferred">
+            <h1>Deferred Packages</h1>
+            <p>Deferred Packages which were uploaded to a DELAYED queue and have not reached their specified delay can be <a href="http://ftp-master.debian.org/deferred.html">seen here</a>.</p>        </div>
+
         <div id="pending">
             <h1>Pending removals</h1>
             <p>Packages which are scheduled to be removed from Debian
@@ -158,9 +167,15 @@
 		</p>
         </div>
 
+        <div id="cruft">
+            <h1>Cruft Report</h1>
+	    <p>Some packages which needs to be removed manually are found in
+	    <a href="cruft-report-daily.txt">the cruft-report</a>.</p>
+        </div>
+
         <div id="testing">
             <h1>Testing</h1>
-            <p>Lenny is testing, sid is unstable. For more details please look
+            <p>Squeeze is testing, sid is unstable. For more details please look
             at the <a href="http://www.debian.org/devel/testing">testing</a> pages.</p>
         </div>
 
@@ -180,10 +195,40 @@
             <a href="http://ftp-master.debian.org/REJECT-FAQ.html">the REJECT-FAQ</a>.</p>
         </div>
 
+		<div id="lintianrejects">
+		  <h1>Lintian Autorejects</h1>
+		  <p>Packages failing a defined set of lintian tags will no
+		  longer be accepted into the archive, but get rejected immediately.</p>
+
+		  <p>Those automated rejects will only be done on sourceful uploads to
+		  unstable and experimental.</p>
+
+		  <p>As there are certain lintian tags that should only appear in very rare
+		  cases we have created two categories:
+		  <dl>
+			<dt>warning</dt>
+			<dd>Tags listed here *can* be overriden by the maintainer using the normal
+			  lintian override mechanism. Of course this should only be done if you
+			  have a technically sound reason why your package needs to break in such a
+			  way.
+			</dd>
+			<dt>error</dt>
+            <dd>Tags listed here can not be overridden. Those are tags
+               corresponding to packaging errors serious enough to mark a
+               package unfit for the archive and should never happen. In
+               fact, most of the tags listed do not appear in our archive
+               currently, the few packages listed below should be easily
+               fixable with their next upload.
+            </dd>
+          </dl>
+          </p>
+          <p>The current list of tags can be <a href="static/lintian.tags">found here</a>.
+        </div>
+
 <!--         <div id="dependencies"> -->
 <!--             <h1>Unmet/Illegal dependencies</h1> -->
 
-<!-- 		    <p> -->
+<!--             <p> -->
 <!--             <a href="/unmet-deps/">Reports</a> of unmet and/or illegal dependencies -->
 <!--             for most architectures in testing+unstable used to be generated daily.</p> -->
 <!--             <p>If your package(s) are listed, you're likely to be violating policy... -->
@@ -197,6 +242,12 @@
             <a href="/archive-criteria.html">Criteria</a> for inclusion in the archive
             of new architectures.
         </div>
+        <div id="talks">
+            <h1>Talks</h1>
+
+            <a href="ftpmaster.pdf">DebConf 2009</a>, Cáceres, Spain.
+        </div>
+
         </div>
         </div>
         </div>