More links.

[homepage.git] / debian-sponsoring.html

diff --git a/debian-sponsoring.html b/debian-sponsoring.html
index 14c458f33cbef7630ae828cbc9d8c276a7c0bbef..8df927d6b42b22c55791d9606a40d99266d229d1 100644 (file)
--- a/debian-sponsoring.html
+++ b/debian-sponsoring.html
@@ -17,9 +17,10 @@ would do a bad job if I tried to maintain more packages.
 <p>When sponsoring, I prefer being approached by the package
 maintainer on IRC (pere on irc.debian.org and irc.oftc.net) with the
 URL to where the package can be downloaded.  I prefer an URL to a .dsc
 <p>When sponsoring, I prefer being approached by the package
 maintainer on IRC (pere on irc.debian.org and irc.oftc.net) with the
 URL to where the package can be downloaded.  I prefer an URL to a .dsc

-file to pass to dget.  This is a low-overhead solution to me, and I do
-not accumulate a large backlog of request for sponsoring (as would
-happen if I tried to gather sponsor request using email. :).
+file on <a href="http://mentors.debian.net/">mentors.debian.net</a> to
+pass to dget.  This is a low-overhead solution to me, and I do not
+accumulate a large backlog of request for sponsoring (as would happen
+if I tried to gather sponsor request using email. :).

 
 <p>The packages should be lintian clean and tested in pbuilder or
 similar, to make sure the dependencies are correct and obvious
 
 <p>The packages should be lintian clean and tested in pbuilder or
 similar, to make sure the dependencies are correct and obvious


@@ -51,8 +52,8 @@ sponsor of the package.
 <li><a href="http://www.debian.org/doc/developers-reference/">The Developers'
   Reference</a></li>
 
 <li><a href="http://www.debian.org/doc/developers-reference/">The Developers'
   Reference</a></li>
 

-<li><a href="http://revu.tauware.de/">REVU - Ubuntu package review
-framework</a></li>
+<li><a href="https://wiki.ubuntu.com/MOTU/Packages/REVU">REVU - Ubuntu
+  package review framework</a></li>

 
 </ul>
 
 
 </ul>