How I sponsor packages

This page expresses my (personal) guidelines regarding sponsorship of a debian package into the archive. If you’re interested in having me sponsor some of your work, be sure to please look this short page over, and ensure you don’t miss anything.

Thank you for your willingness to contribute! It means a lot to me, personally.

Process

• Ask me over IRC, Email or in person if I’m interested in sponsoring your work. Please use my Debian email address.
• Be sure to let me know if you’re interested in long-term or one-time sponsorship.

Going back-and-forth

• Please don’t increment the debian version when you update the package. Only increment if the package has been uploaded to the actual Debian archive.
• Send me either a dget-able URL, or a pointer to salsa.

Basic Guidelines

• If you’re using VCS, please use salsa.
• Ensure the package is lintian clean, both source and binary. If not, you should be able to explain why the error(s) are false positives and not worth overriding.
  • Conversely, there are a bunch of tags not worth overriding. If you have any questions, ask! As a project, we rely on good human judgement for this.
• Please ship manpages for user-facing binaries.
• Is there a team you should co-maintain this with? If there is, why are you not working with them to sponsor this package?
• Are there warnings in the build process? If so, are the warnings safe to ignore?
• Does it install, upgrade and uninstall correctly? You can use piuparts to check.
• Did you install all documentation worth shipping to end-users?
• Did you run the test-suite? Does it obey nocheck?

License Issues

• Are all the licenses DFSG free? Have you applied the relevant debian-legal tests on all the licenses? Are any licenses in this package not currently in Debian main?
• For our first review, please attach a list of all the licenses in the source tree.
• Are all the licenses in the debian/copyright?