This chapter describes procedures that existing Debian developers should follow when it comes to dealing with wannabe developers.
Sponsoring a package means uploading a package for a maintainer who is not able to do it on their own, a new maintainer applicant. Sponsoring a package also means accepting responsibility for it.
New maintainers usually have certain difficulties creating Debian packages — this is quite understandable. That is why the sponsor is there, to check the package and verify that it is good enough for inclusion in Debian. (Note that if the sponsored package is new, the FTP admins will also have to inspect it before letting it in.)
Sponsoring merely by signing the upload or just recompiling is definitely not recommended. You need to build the source package just like you would build a package of your own. Remember that it doesn't matter that you left the prospective developer's name both in the changelog and the control file, the upload can still be traced to you.
If you are an application manager for a prospective developer, you can also be their sponsor. That way you can also verify the how the applicant is handling the `Tasks and Skills' part of their application.
See the page about advocating a prospective
developer
at the Debian web site.
Please see Checklist for
Application Managers
at the Debian web site.
Debian Developer's Reference
ver. 2.11, 08 April, 2002aph@debian.org
schwarz@debian.org
ijackson@gnu.ai.mit.edu