Christopher Howard <christopher.how...@frigidcode.com> writes: > For most of my software, I roll my own debs and make them publicly > available, including all the debian source files.
Thank you for making your work available for others. I assume this is free software <URL:http://www.debian.org/intro/free> under clear license terms, such as the GNU GPL? > I try to follow my maintainer's guide and debian policy closely while > making them, and they are usually lintian approved (except for the > occasional wish list item). That is very good practice, and puts you ahead of many who seek to have their work in Debian. > My question is: after doing all that work, how much further is it for > me to actually get the packages into Debian? What is left in the > process? See <URL:http://mentors.debian.net/intro-maintainers>. The question of “how much work” depends in part on the particulars of the packages themselves, of course. The part which may be surprising is step 5., “Find a sponsor”. (You need to do all the steps before that, of course.) Each package uploaded to Debian must be done by an existing Debian Developer (defined essentially as someone with that authority). So you need to attract the interest of someone who thinks the package is worthwhile in Debian and who is willing to vouch for the quality of your packaging of that software. Often this same person will collaborate with you to help you get the package in shape for Debian before they upload it. You will, therefore, want to think about where the intersection might be of the community of prospective users of the package and the community of Debian developers, and seek an interested person there. Is there perhaps one or more Debian Developers already using the packages downloaded from you? -- \ “Anyone can do any amount of work provided it isn't the work he | `\ is supposed to be doing at the moment.” —Robert Benchley | _o__) | Ben Finney
pgp1BDDUWrWTF.pgp
Description: PGP signature
