<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. 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. :).
+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. :).
<p>The packages should be lintian clean and tested in pbuilder or
similar, to make sure the dependencies are correct and obvious
debian/main, so if the package isn't acceptable for main, there is
normally no need to approach me.
+<p>I find it best to hear directly from the person planning on
+maintaining the package, to be able to ask how much time the
+prospective maintainer plan to spend on the package, as well as work
+out issues with the package directly.
+
+<p>When I sponsor packages, I add a line 'Upload sponsored by Petter
+Reinholdtsen' to the debian changelog to document the fact to the next
+sponsor of the package.
+
+<h2>Related documents</h2>
+
+<ul>
+
+<li><a href="http://wiki.debian.org/SponsorChecklist">Debian sponsor
+ check list</a><li>
+
+<li><a href="http://people.debian.org/~mpalmer/sponsorship.html">Matthew
+ Palmer's guidelines for sponsoring people</a></li>
+
+<li><a href="http://www.debian.org/doc/debian-policy/">Debian Policy</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>
+
+</ul>
+
</body>
</html>
projects / homepage.git / blobdiff