('NMUs','nmu','Your package is a <a href="http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu">NMU</a>'),
('NMUs','nmu','Your package is a <a href="http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu">NMU</a>'),
('QA uploads','qa','Your package is a <a href="http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-qa-upload">QA upload</a>'),
('QA uploads','qa','Your package is a <a href="http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-qa-upload">QA upload</a>'),
('Backports','backports','Your package is a <a href="http://backports-master.debian.org/">backported package</a>'),
('Backports','backports','Your package is a <a href="http://backports-master.debian.org/">backported package</a>'),
('Modified tarballs (but good reasons)','modified-tarballs','Your package modified the original source tarball somehow in a way, it does not match the original checksum anymore, but you have a <a href="http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-origtargz">good reason</a> to do so'),
('Modified tarballs (but good reasons)','modified-tarballs','Your package modified the original source tarball somehow in a way. It does not match the original checksum anymore but you have a <a href="http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-origtargz">good reason</a> to do so'),
('Library package','library-package','You are packaging a <a href="http://www.debian.org/doc/debian-policy/ch-sharedlibs.html">policy compliant library</a>'),
('Library package','library-package','You are packaging a <a href="http://www.debian.org/doc/debian-policy/ch-sharedlibs.html">policy compliant library</a>'),
('VCS snapshot tarballs','vcs-tarball','Your package is not based on a original source tarball at all, but is based on a VCS snapshot',),
('VCS snapshot tarballs','vcs-tarball','Your package is not based on a original source tarball at all but is based on a VCS snapshot',),
('contrib/non-free packages','non-free-package','Your package it targetting the <tt>contrib</tt> or <tt>non-free</tt> branches (<a href="http://www.debian.org/doc/debian-policy/ch-archive.html#s-sections">Information</a>)'),
('contrib/non-free packages','non-free-package','Your package it targetting the <tt>contrib</tt> or <tt>non-free</tt> branches (<a href="http://www.debian.org/doc/debian-policy/ch-archive.html#s-sections">Information</a>)'),
('1.0 format packages','1.0-format','Your package is using the 1.0 format (the traditional source format that is).'),
('1.0 format packages','1.0-format','Your package is using the 1.0 format (the traditional source format that is)'),
('3.0 format packages','3.0-format','Your package is using the <a href="http://wiki.debian.org/Projects/DebSrc3.0">3.0/quilt</a> format.'),
('3.0 format packages','3.0-format','Your package is using the <a href="http://wiki.debian.org/Projects/DebSrc3.0">3.0/quilt</a> format'),
('Embedded code copies','embedded-code-copies','Your package <a href="http://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles">makes use of embedded code copies in a reasonable way</a>.'),
('Embedded code copies','embedded-code-copies','Your package <a href="http://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles">makes use of embedded code copies in a reasonable way</a>'),
('DEP-5 copyright','dep5','Your package does make use of <a href="http://dep.debian.net/deps/dep5/">DEP-5</a> copyright files.'),
('DEP-5 copyright','dep5','Your package does make use of <a href="http://dep.debian.net/deps/dep5/">DEP-5</a> copyright files'),
('No Lintian cleanliness (but good reasons)','not-lintian-clean','Your package is not <a href="http://lintian.debian.org/">Lintian clean</a> down to the informational level, but you have a good reason why not.'),
('No Lintian cleanliness (but good reasons)','not-lintian-clean','Your package is not <a href="http://lintian.debian.org/">Lintian clean</a> down to the informational level but you have a good reason why not'),
('Prospective DM/DD','prospective-dm-dd','You are willing to become a <a href="http://wiki.debian.org/DebianMaintainer">Debian Maintainer</a>/<a href="http://wiki.debian.org/DebianDeveloper">Debian Developer</a> some day.'),
('Prospective DM/DD','prospective-dm-dd','You are willing to become a <a href="http://wiki.debian.org/DebianMaintainer">Debian Maintainer</a>/<a href="http://wiki.debian.org/DebianDeveloper">Debian Developer</a> some day'),
('(Willing to be) DM','applicant-is-dm','You are a <a href="http://wiki.debian.org/DebianMaintainer">Debian Maintainer</a> already, or you plan to become one soon.'),
('(Willing to be) DM','applicant-is-dm','You are a <a href="http://wiki.debian.org/DebianMaintainer">Debian Maintainer</a> already, or you plan to become one soon'),
('(Willing to enter) NM','applicant-is-nm','You are in the <a href="https://nm.debian.org/">New Maintainer</a> process to become a developer already, or you plan to apply soon.'),
('(Willing to enter) NM','applicant-is-nm','You are in the <a href="https://nm.debian.org/">New Maintainer</a> process to become a developer or you plan to apply soon'),
('Signed GPG key','signed-gpg-key','Your GPG matches the <a href="http://lists.debian.org/debian-devel-announce/2010/09/msg00003.html">guidelines of the Debian keyring maintainers</a> and/or is signed by any Debian developer.'),
('Signed GPG key','signed-gpg-key','Your GPG matches the <a href="http://lists.debian.org/debian-devel-announce/2010/09/msg00003.html">guidelines of the Debian keyring maintainers</a> and/or is signed by any Debian developer'),
('One time uploads','no-one-time-upload','Your package is a single shot upload.'),
('One time uploads','no-one-time-upload','Your package is a single shot upload'),
('Sharing a time zone','sharing-time-zone','You share a time zone with your sponsors. This can be useful to get together more easily.'),
('Sharing a time zone','sharing-time-zone','You share a time zone with your sponsors. This can be useful to get together more easily'),
('Possibility to meet-up','possibility-to-meetup','You are living close to your sponsor and you are willing to meet him eventually'),
('Possibility to meet-up','possibility-to-meetup','You are living close to your sponsor and you are willing to meet him eventually'),
('Having already packages in Debian','maintainer-already','You are living close to your sponsor and you are willing to meet him eventually'),
('Having already packages in Debian','maintainer-already','You do already have one or more packages in Debian'),
('Maintainer is not upstream','maintainer-is-not-upstream','You are not upstream of the package you are proposing to Debian'),
('Maintainer is not upstream','maintainer-is-not-upstream','You are not upstream of the package you are proposing to Debian'),
('Notable user base','notable-user-base','You can prove people are already using your program and consider it useful'),
('Notable user base','notable-user-base','You can show us that people are already using your program and consider it useful'),
('Minimizing differences to derivatives','package-in-a-derivative','Your package feeds changes introduced by any derivative back to Debian to minimize differences'),
('Minimizing differences to derivatives','package-in-a-derivative','Your package feeds changes introduced by any derivative back to Debian to minimize differences'),
To get your package into Debian, please do as follows:
<p>See ${ h.tags.link_to("our introductory page", h.url('intro-maintainers')) } for maintainers and learn how to use ${ c.config['debexpo.sitename'] } and get your packages into Debian. Furthermore see our ${ h.tags.link_to("our introductory page for sponsors", h.url('sponsors')) } to learn how to get in touch with a sponsor.</p>
<ol>
<li>Make a Debian package and upload it to ${ c.config['debexpo.sitetitle'] }. See ${ h.tags.link_to("our introductory page", h.url('intro-maintainers')) } for maintainers and learn how to use ${ c.config['debexpo.sitename'] }.</li>
<li>Once you filed a request-for-sponsorship (<em>RFS</em>) you will hopefully get positive feedback for your package. See ${ h.tags.link_to("our page dedicated to reviewers", h.url('intro-reviewers')) } to learn more about package reviews.</li>
<li>Ultimately a Debian Developer needs to upload it to Debian. Learn on ${ h.tags.link_to("our introductory page for sponsors", h.url('sponsors')) } how to get in touch with a sponsor.</li>
</ol>
<p>If you are curious about <em>Debexpo</em>, the software which is running this site, you can <a href="http://wiki.debian.org/Debexpo">read more about Debexpo on the Debian Wiki</a>.</p>
<p>If you are curious about <em>Debexpo</em>, the software which is running this site, you can <a href="http://wiki.debian.org/Debexpo">read more about Debexpo on the Debian Wiki</a>.</p>
<p>Debian is a distribution, not a general purpose repository. Many of us do not believe <em>every</em> piece of free software necessarily belongs to Debian. Please do not treat Debian as platform to advertise your own software, unless there is some <em>real</em> request for it. That said, there is no one who ultimately judges about that. Eventually you may get some feedback on that discussion after filing your WNPP bug (see below), however you are free to interpret that as suggestion, not as final vote. After all, you need to find a sponsor believing in the benefit of having your package in Debian, though. Please have a look to our ${ h.tags.link_to("sponsors page", h.url(controller='sponsor', action='index')) } to learn about personal interests of sponors.
<p>Debian is a distribution, not a general purpose repository. Many of us do not believe <em>every</em> piece of free software necessarily belongs to Debian. Please do not treat Debian as a platform to advertise your own software, unless there is some <em>real</em> request for it. That said, there is no one who ultimately judges about that. Eventually you may get some feedback on that discussion after filing your WNPP bug (see below) however you are free to interpret that as a suggestion, not as a final vote. After all, you need to find a sponsor believing in the benefit of having your package in Debian. Please have a look at our ${ h.tags.link_to("sponsors page", h.url(controller='sponsor', action='index')) } to learn about personal interests of sponsors.
<p>If you want to contribute to Debian, but you do not know which package Debian misses yet, have a look to "Request for package" (<em>RFP</em>) bugs. See WNPP below.</p>
<p>If you want to contribute to Debian, but you do not know which package Debian misses yet, take a look at "Request for package" (<em>RFP</em>) bugs. See WNPP below.</p>
<h2>2. File a WNPP bug</h2>
<h2>2. File a WNPP bug</h2>
<p><a href="http://www.debian.org/devel/wnpp/">Work-Needing and Prospective Packages</a> <em>WNPP</em> is our system of announcing your intent to markup packages being worked on. In particular its a bug against the <a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=wnpp">WNPP pseudo package</a> (<a href="http://wnpp.debian.net/">or use a nice frontend</a> to browse WNPP bugs). If you want to package something for Debian, the very first step should be to file an "Intent to package" (<em>ITP</em>) bug against <em>WNPP</em>. You may want to use the <tt><a href="http://packages.debian.org/squeeze/reportbug">reportbug</a></tt> tool to achieve that, by selecting "<em>wnpp</em>" as package to report a bug to.</p>
<p><a href="http://www.debian.org/devel/wnpp/">Work-Needing and Prospective Packages</a> <em>WNPP</em> is our system of announcing your intent to markup packages being worked on. In particular it is a bug against the <a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=wnpp">WNPP pseudo package</a> (<a href="http://wnpp.debian.net/">or use a nice frontend</a> to browse WNPP bugs). If you want to package something for Debian, the very first step should be to file an "Intent to package" (<em>ITP</em>) bug against <em>WNPP</em>. You may want to use the <tt><a href="http://packages.debian.org/squeeze/reportbug">reportbug</a></tt> tool to achieve that by selecting "<em>wnpp</em>" as package to report a bug to.</p>
<h2>3. Make the package</h2>
<h2>3. Make the package</h2>
<p>Debian packages must comply to several normative requirements and guidelines. We can't give you exhaustive instructions how to build packages here. In short, we expect you to provide a <em>source package</em> complying to the Debian policy at least (see below). Please have a look to those excellent resources:</p>
<p>Debian packages must comply to several normative requirements and guidelines. We can't give you exhaustive instructions on how to build packages here. In short, we expect you to provide a <em>source package</em> complying to the Debian policy at least (see below). Please take a look at those excellent resources:</p>
<li><strong>${ h.tags.link_to("Sign up for an account", h.url(controller='register', action='register')) }</strong>. Getting an account on this server is an automatic process and will just take a moment. We require registration so we have a valid email address where sponsors can reach you.</li>
<li><strong>${ h.tags.link_to("Sign up for an account", h.url(controller='register', action='register')) }</strong>. Getting an account on this server is an automatic process and will just take a moment. We require registration so we have a valid email address where sponsors can reach you.</li>
<li><strong>Upload your package</strong> to <tt>mentors.debian.net</tt>. You do not need to put your packages into any other web space on the Internet. Everybody will be able to download your package using either the web browser, the '<tt>dget</tt>' tools or even through a simple run of <tt>apt-get source ....</tt></li>
<li><strong>Upload your package</strong> to <tt>${ config['debexpo.sitename'] }</tt>. You do not need to put your packages into any other web space on the Internet. Everybody will be able to download your package using either the web browser, the '<tt>dget</tt>' tools or even through a simple run of <tt>apt-get source ....</tt></li>
<li>Have a look to your ${ h.tags.link_to("personal package page", h.url(controller='package', action='my')) }. Your uploaded package should <strong>show up there</strong>. From there you can toggle several settings and retrieve the RFS (request-for-sponsorship) template</li>
<li>Have a look at your ${ h.tags.link_to("personal package page", h.url(controller='package', action='my')) }. Your uploaded package should <strong>show up there</strong>. From there you can toggle several settings and retrieve the RFS (request-for-sponsorship) template</li>
<li>Your package is on display on the main page of ${ c.config['debexpo.sitetitle'] }, if you enable the "<i>Needs a Sponsor</i>" button, so interested sponsors will see it and hopefully check it out.</li>
<li>Your package is on display on the main page of ${ c.config['debexpo.sitetitle'] } (if you enable the "<i>Needs a Sponsor</i>" button) so interested sponsors will see it and hopefully check it out.</li>
<li>You will be shown a <strong>RFS (request-for-sponsorship) template</strong> that you should send to the debian-mentors mailing list to draw attention to your package.</li>
<li>You will be shown a <strong>RFS (request-for-sponsorship) template</strong> that you should send to the debian-mentors mailing list to draw attention to your package.</li>
</ul>
</ul>
...
@@ -104,33 +104,34 @@ allow_unsigned_uploads = 0
...
@@ -104,33 +104,34 @@ allow_unsigned_uploads = 0
$ dput mentors your_sourcepackage_1.0.changes
$ dput mentors your_sourcepackage_1.0.changes
</pre>
</pre>
If you did everything right, you will get a confirmation mail from our site, and you can start seeking a sponsor for your package.
If you did everything right, you will get a confirmation mail from our site and you can start seeking a sponsor for your package.
<h2>5. Find a sponsor</h2>
<h2>5. Find a sponsor</h2>
<p>Once your package is publicly available on any resource, including but not limited to ${ c.config['debexpo.sitetitle'] } you may start searching a sponsor for your package. If you uploaded packages to Debian already, you should ask your former sponsor. A sponsor is any <a href="http://wiki.debian.org/DebianDeveloper">Debian Developer</a> willing to upload your package to Debian on your behalf. Have a look to our ${ h.tags.link_to("sponsor's page", h.url(controller='sponsor', action='index')) } to learn more on sponsors and how you find one.</p>
<p>Once your package is publicly available on any resource, including but not limited to ${ c.config['debexpo.sitetitle'] } you may start searching a sponsor for your package. If you have already uploaded packages to Debian, you should ask your former sponsor. A sponsor is any <a href="http://wiki.debian.org/DebianDeveloper">Debian Developer</a> willing to upload your package to Debian on your behalf. Have a look to our ${ h.tags.link_to("sponsor's page", h.url(controller='sponsor', action='index')) } to learn more on sponsors and how to find one.</p>
<p>The main point of the sponsor process is to review your package to make sure it meets our technical requirements. Everyone can and should review other people's packages. Also, a clean package will increase your likelihood to find a sponsor. Please have a look to our page ${ h.tags.link_to("telling more about reviews", h.url('intro-reviewers')) }.</p>
<p>The main point of the sponsoring process is to review your package to make sure it meets our technical requirements. Everyone can and should review other people's packages. Also, a clean package will increase your likelihood to find a sponsor. Please take a look at our page ${ h.tags.link_to("telling more about reviews", h.url('intro-reviewers')) }.</p>
<h3>The relation between you and your sponsor</h3>
<h3>The relation between you and your sponsor</h3>
<p>A sponsor is not technically responsible for your package. <strong>You</strong> will be listed as official maintainer of the package in Debian. You will even get the bug reports if people discover problems in your package. Besides from not being able to upload the package directly into Debian you are treated as a full member of the community. The Debian project appreciates the work you do.</p>
<p>A sponsor is not technically responsible for your package. <strong>You</strong> will be listed as the official maintainer of the package in Debian. You will even get the bug reports if people discover problems in your package. Apart from not being able to upload the package directly into Debian you are treated as a full member of the community. The Debian project appreciates the work you do.</p>
<h3>What can I do if I don't find a sponsor?</h3>
<h3>What can I do if I don't find a sponsor?</h3>
<p>Don't become desperate. Sponsoring can take a while. Nonetheless, here are a few hints:</p>
<p>Don't become desperate. Sponsoring can take a while. Nonetheless, here are a few hints:</p>
<ul>
<ul>
<li>Ask again on the debian-mentors mailing list. Its common practice to ask again after a few weeks.</li>
<li>Ask again on the debian-mentors mailing list. It is common practice to ask again after a few weeks.</li>
<li>Offer your package directly to developers. We made a ${ h.tags.link_to("a list of sponsors", h.url(controller='sponsor', action='index')) }, eventually willing to upload packages for you. <em>Please don't contact every sponsor listed there. Instead, read their individual requirements and choose the sponsor which matches you and your package best</em>.
<li>Offer your package directly to developers. We made a ${ h.tags.link_to("a list of sponsors", h.url(controller='sponsor', action='index')) }, eventually willing to upload packages for you. <em>Please don't contact every sponsor listed there. Instead, read their individual requirements and choose the sponsor which matches you and your package best</em>.
</ul>
</ul>
<h2>6. Getting an upload to Debian</h2>
<h2>6. Getting an upload to Debian</h2>
<p>Once you found a sponsor interested in your package, he will <em>sponsor</em> it, that means build it and successively upload it to Debian. You will get notified by <em>dak</em> - the software used by Debian to manage its repositories - by the upload. Please note, if your package was not at all in Debian before, it needs manual approval by <a href="http://ftp-master.debian.org/">ftpmasters</a> to clear the <a href="http://ftp-master.debian.org/new.html">NEW queue</a>. They will do consistency checks, and check your <tt>debian/copyright</tt> file whether your package matches the <a href="http://www.debian.org/social_contract#guidelines">Debian Free Software Guidelines</a>. ftpmaster's opinion is binding here for both of you, you and your sponsor.</p>
<p>Once you find a sponsor interested in your package, he will <em>sponsor</em> it. That means building it and successively uploading it to Debian. You will get notified by <em>dak</em> - the software used by Debian to manage its repositories - about the upload. Please note, if your package was not at all in Debian before, it needs manual approval by <a href="http://ftp-master.debian.org/">ftpmasters</a> to clear the <a href="http://ftp-master.debian.org/new.html">NEW queue</a>. They will do consistency checks, and review your <tt>debian/copyright</tt> file whether your package matches the <a href="http://www.debian.org/social_contract#guidelines">Debian Free Software Guidelines</a>. ftpmaster's opinion is binding here for both your sponsor and you.</p>
<h2>7. Maintaining your package in Debian</h2>
<h2>7. Maintaining your package in Debian</h2>
<p>Please see the corresponding chapter in the <a href="http://www.debian.org/doc/manuals/maint-guide/update.en.html">New Maintainer's Guide</a> to get the idea. Whenever you feel like, you should update your package in Debian. The general procedure isn't different to your fist upload. Please upload your updated package to ${ config['debexpo.sitename'] } and poke your former sponsor about your change. Alternatively, follow ${ h.tags.link_to("the usual procedures", h.url(controller='sponsor', action='index')) }.</p>
<p>Please see the corresponding chapter in the <a href="http://www.debian.org/doc/manuals/maint-guide/update.en.html">New Maintainer's Guide</a> to get the idea. Whenever you feel like, you should update your package in Debian. The general procedure isn't different form your fist upload. Please upload your updated package to ${ config['debexpo.sitename'] } and poke your former sponsor about your change. Alternatively, follow ${ h.tags.link_to("the usual procedures", h.url(controller='sponsor', action='index')) }.</p>
<p>If your package passes through the sponsoring process for <em>a few</em> successive uploads without any notable correction by your sponsor, you can become a <a href="http://wiki.debian.org/DebianMaintainer">Debian Maintainer</a> which grants you limited upload rights to Debian directly. Get in touch with your sponsor to discuss your chances here. You can also <a href="http://www.debian.org/devel/join/">become a Debian Developer</a> giving you all necessary upload rights.</p>
<p>If your package passes through the sponsoring process for <em>a few</em> packages without any notable correction by your sponsor, you can become a <a href="http://wiki.debian.org/DebianMaintainer">Debian Maintainer</a> which grants you limited upload rights to Debian directly. Get in touch with your sponsor to discuss your chances here. You can also <a href="http://www.debian.org/devel/join/">become a Debian Developer</a> giving you all necessary upload rights.</p>
<p>As sponsored maintainer you don't have upload permissions to the Debian repository. Therefore you have three possibilities to get your package into Debian:</p>
<p>As sponsored maintainer you do not have upload permissions to the Debian repository. Therefore you have three possibilities to get your package into Debian:</p>
<ul>
<ul>
<li>Join a packaging team</li>
<li>Join a packaging team</li>
...
@@ -12,33 +12,33 @@ ${ c.custom_html }
...
@@ -12,33 +12,33 @@ ${ c.custom_html }
<li>Talk directly to people willing to sponsor your package</li>
<li>Talk directly to people willing to sponsor your package</li>
</ul>
</ul>
<p>They will ${ h.tags.link_to("review", h.url('intro-reviewers')) } your package. Everyone is invited to review packages, including you for other people in your situation.</p>
<p>A sponsor, regardless of how you found one will ${ h.tags.link_to("review", h.url('intro-reviewers')) } your package. Yet everyone is invited to review packages, including yourself. We encourage you to review other people's packages - both of you will benefit.</p>
<h2>Join a packaging team</h2>
<h2>Join a packaging team</h2>
<p>There are teams in Debian who maintain packages collaboratively. If your package deals with libraries for programming langauges, or is about an ecosystem of associated packages, think of KDE or Gnome packages for example, you may want to join that team. Have a look to <a href="http://wiki.debian.org/Teams/#Packaging_teams">list of packaging teams</a> in Debian.</p>
<p>There are teams in Debian who maintain packages collaboratively. If your package deals with libraries for programming languages or is about an ecosystem of associated packages, think of KDE or Gnome packages for example, you may want to join the respective team. Have a look at the <a href="http://wiki.debian.org/Teams/#Packaging_teams">(incomplete) list of packaging teams</a> in Debian.</p>
<p>Please note, each of those teams may have their own workflows and policies. Contact their respective mailing lists to learn more.</p>
<p>Please note, each of those teams may have their own workflows and policies covering how to deal with package uploads. Contact their respective mailing lists and home pages to learn more.</p>
<h2>Ask the <tt>debian-mentors</tt> mailing list</h2>
<h2>Ask the <tt>debian-mentors</tt> mailing list</h2>
<p>If your package does not match the interests of any team, or you are not sure whether a team could be interested in your package, please write to the <tt><a href="http://lists.debian.org/debian-mentors/">debian-mentors</a></tt> mailing list to draw attention to your package. Your request should be formatted according to our RFS ("<em>request for sponsorship</em>") template. If you uploaded your package to ${ config['debexpo.sitename'] }, a RFS template can be shown on your package page.</p>
<p>If your package does not match the interests of any team or you are not sure whether a team could be interested in your package, please write to the <tt><a href="http://lists.debian.org/debian-mentors/">debian-mentors</a></tt> mailing list to draw attention to your package. Your request should be formatted according to our RFS ("<em>request for sponsorship</em>") template. If you uploaded your package to ${ config['debexpo.sitename'] }, a RFS template can be shown on your package page.</p>
<p><em>If in doubt, choose this alternative.</em></p>
<p><em>If you are unsure or in doubt, choose this alternative</em>.</p>
<p>Don't worry if you get no answer: It does not mean your package is bad. Ask again after a few weeks if you did not find a sponsor by other means yet. </p>
<p>Typically you will reach the greatest audience by writing to our public mailing list. Eventually also some non-uploading reviewer may have a look at your package. Please do not worry if you get no answer: It happens from time to time that all interested people might be distracted or busy. It does not mean your package is bad. Feel free to ask again after a few weeks or try any of the alternative methods to find a sponsor. </p>
<h2>Finding a sponsor</h2>
<h2>Finding a sponsor</h2>
<p>If you want, you can write sponsors willing to upload packages to other maintainers directly. <strong>Don't contact them blindly!</strong> Instead watch out for their requirements and guidelines. Contact them only if your package is compatible to their individual requirements and matches their area of interest. To tell apart sponsors who are interested in your package and who are not, they can formulate their own sponsor metrics.</p>
<p>If you want, you can write sponsors willing to upload packages to other maintainers directly. <em>Please do not send out mass emails!</em> Instead watch out for their individual requirements and guidelines. Contact individuals only if your package is compatible to their respective requirements and matches their area of interest. To tell apart sponsors who are interested in your package and those who are not, we asked developers to formulate their own sponsor traits. Please read them carefully and compare your package with their expectations.</p>
<h2>Sponsor metrics</h2>
<h2>Sponsor metrics</h2>
To help you finding a sponsor interested in your package, they can formulate sponsor metrics:
To help you find a sponsor interested in your package, they can formulate sponsor traits for either social or technical aspects. Additionally a sponsor may not usually be interested in every package but only in a certain category.
<h3>Sponsor's personal interests</h3>
<h3>Sponsor's personal interests</h3>
<p>Sponsors typically are not interested to upload any package for you. They could, however, be interested if your package matches their area of interest. Please compare those package types with your package. Such categories eventually are certain programming languages your program is written in, a field of endeavour, or software fulfilling a certain task. </p>
<p>Typically, sponsors are not interested in uploading any package for you. However, they could be interested if your package matched their area of interest. Please compare those package types with your package. Such categories eventually are certain programming languages your program is written in, a field of endeavour or software fulfilling a certain task. </p>
<%def name="tag_helper(requirement)">
<%def name="tag_helper(requirement)">
% if not c.sponsor_filter:
% if not c.sponsor_filter:
...
@@ -59,10 +59,10 @@ To help you finding a sponsor interested in your package, they can formulate spo
...
@@ -59,10 +59,10 @@ To help you finding a sponsor interested in your package, they can formulate spo
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Debian allows several workflows and best practices to co-exist with each other. All packages <strong>must comply the <a href="http://www.debian.org/doc/debian-policy/">Debian policy</a></strong> as bare essential minimum, but some workflows and best practices beyond that are optional, but nonetheless mandatory <em>for you</em> asking that person to sponsor your upload.
Debian allows several workflows and best practices to co-exist with each other. All packages <strong>must comply to the <a href="http://www.debian.org/doc/debian-policy/">Debian policy</a></strong> as a bare essential minimum and although some workflows and best practices beyond that are optional it is nonetheless mandatory <em>for you</em> to ask someone to sponsor your upload.
</td>
</td>
<td>
<td>
Some sponsors prefer to upload only packages from people, that fulfill certain social criterias. Please don't ask an uploader to sponsor your request if you don't match them.
Some sponsors prefer to only upload packages from people who fulfill certain social criteria. Please don't ask an uploader to sponsor your request if you don't match them.
