Sponsoring checklist
====================

This is based on a checklist of Matthew Palmer <mplamer@debian.org>,
see [1] for details.

For new and adopted packages:
 ( ) Is there a WNPP bug properly filed in the BTS?
 ( ) Does the package changelog close the bug?
 ( ) Is it properly created and maintained?
 ( ) Did the applicant receive the package?

Informational:
 ( ) Did the applicant provide a link to the upstream sources?
 ( ) Has the applicant a GPG-key? Is it signed by anyone?
 ( ) Does the applicant intend to join the NM process?

Packaging checks:
 ( ) debian/copyright: see [2]
 ( ) .orig.tar.gz matches with upstream, or has minor, reasonable changes.
 ( ) .diff.gz contains nothing which concerns me (e.g. potential trojans etc.)
 ( ) debian/rules:
     No dh_* commands left commented (either use them or lose them)
 ( ) debian/control: 
     package description and synopsis are reasonable (see [3] and [4])
 ( ) debian/control: build-depends look ok
 ( ) debian/changelog: Entries well formed and appropriate closes
 ( ) source and binary packages are lintian- and linda-clean
 ( ) check linitan -I for infos
 ( ) builds cleanly in pbuilder
 ( ) binary package dependencies are ok
 ( ) *.changes: bugs said to be closed in debian/changelog are actually closed
 ( ) package installs cleanly
 ( ) programs run as intended

References:
[1] http://people.debian.org/~mpalmer/sponsorship_checklist.html
[2] http://lists.debian.org/debian-legal/2003/12/msg00194.html
[3] http://people.debian.org/~walters/descriptions.html
[4] http://www.debian.org/doc/developers-reference/ch-best-pkging-practices.en.html#s-bpp-debian-control

 -- Philipp Kern <pkern@debian.org>  Wed, 08 Apr 2005 18:00:00 +0200