path: root/greek/devel/wnpp/index.wml

#use wml::debian::template title="Work-Needing and Prospective Packages"
#use wml::debian::toc
#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data"
#use wml::debian::translation-check translation="ff76decf22b833c8b721fc40392935030d5f2a2b" maintainer="galaxico"

<define-tag toc-title-formatting endtag=required><h3>%body</h3></define-tag>

<p>Work-Needing and Prospective Packages, WNPP for short, is a list 
of packages in need of new maintainers and prospective packages in Debian.
In order to closely track the real status of such things, WNPP is currently
operated as a pseudo-package in the <a href="https://bugs.debian.org/">Debian
Bug Tracking System (BTS)</a>.</p>

<hrline />

<p><a href="work_needing">Packages in need of a new maintainer</a>:
</p>
<ul>
  <li>
      <a href="rfa_bypackage"><rfa_number> packages up for adoption</a>,
      organized <a href="rfa_bymaint">by maintainer</a>
      or <a href="rfa_byage">by age</a>
  </li>
  <li>
      <a href="orphaned"><orphaned_number> orphaned packages</a>,
      organized <a href="orphaned_byage">by age</a>
  </li>
  <li>
      <a href="being_adopted"><adopted_number> packages currently being adopted</a>,
      organized <a href="being_adopted_byage">by age</a>
      or <a href="being_adopted_byactivity">by activity</a>
  </li>
</ul>

<p>
<a href="help_requested"><help_number> packages in need of help</a>,
organized <a href="help_requested_byage">by age</a>
or <a href="help_requested_bypop">by popularity</a>
</p>

<p><a href="prospective">Prospective packages</a>:</p>
<ul>
  <li>
      <a href="being_packaged"><packaged_number> packages being worked on</a>,
      organized <a href="being_packaged_byage">by age</a>
      or <a href="being_packaged_byactivity">by activity</a>
  </li>
  <li>
      <a href="requested"><requested_number> requested packages</a>,
      organized <a href="requested_byage">by age</a>
  </li>
</ul>


<p>Note: these lists are updated six times a day; for more up-to-date information
please check the <a href="https://bugs.debian.org/wnpp">wnpp pseudo package</a>
entry in the BTS.</p>

<p>You can search the above information by package, description or type
on the <a href="https://wnpp.debian.net">WNPP search</a> website.</p>

<p>You can browse the above information broken down into various categories
(based on <a href="https://debtags.debian.org/">debtags</a>) on the 
<a href="https://wnpp-by-tags.debian.net">WNPP-by-tags</a> website.</p>

<hrline />

<h2>Using WNPP</h2>

<toc-display />

<p>Since it uses the BTS, every developer is already familiar with the
technical details, such as submission of new information, modification of
information or closing of pending requests. On the other hand, in order to
achieve the highest level of automatization, some procedures have to be
observed.</p>

<p>In order to submit new information, a bug has to be filed against the
<a href="https://bugs.debian.org/wnpp">wnpp pseudo package</a> for each
(prospective) package that is affected.  Please note that you should
only submit one bug per source package rather than one bug for each
binary package built from a source package.</p>


<toc-add-entry>Adding new entries with <q>reportbug</q></toc-add-entry>

<p>You can use <a href="https://packages.debian.org/reportbug">reportbug</a>
(<kbd>apt-get install reportbug</kbd>):</p>

<samp>
  $ reportbug --email <var>username@domain.tld</var> wnpp<br />
  Using '<var>Your Name &lt;username@domain.tld&gt;</var>' as your from address.<br />
  Getting status for wnpp...<br />
  Querying Debian bug tracking system for reports on wnpp<br />
  (Use ? for help at prompts.)<br />
  ...<br />
</samp>

<p>You will see a list of reported bugs against WNPP which you
should read to prevent a second report for the same package.</p>
<p>After the buglist you are asked for the request type:</p>
 
<samp>
What sort of request is this?<br />
<br />
1 ITP  This is an <q>Intent To Package</q>. Please submit a package description<br />
       along with copyright and URL in such a report.<br />
<br />
2 O    The package has been <q>Orphaned</q>. It needs a new maintainer as soon<br />
       as possible.<br />
<br />
3 RFA  This is a <q>Request for Adoption</q>. Due to lack of time, resources,<br />
       interest or something similar, the current maintainer is asking for<br />
       someone else to maintain this package. They will maintain it in<br />
       the meantime, but perhaps not in the best possible way. In short:<br />
       the package needs a new maintainer.<br />
<br />
4 RFH  This is a <q>Request For Help</q>. The current maintainer wants to continue<br />
       to maintain this package, but he/she needs some help to do this, because<br />
       his/her time is limited or the package is quite big and needs several<br />
       maintainers.<br />
<br />
5 RFP  This is a <q>Request For Package</q>. You have found an interesting piece<br />
       of software and would like someone else to maintain it for Debian.<br />
       Please submit a package description along with copyright and URL in<br />
       such a report.<br />
<br />
Choose the request type: <br />
</samp>

<p>After your selection you will be asked for the package name:</p>

<samp>
Choose the request type: <var>x</var><br />
Please enter the proposed package name: <var>PACKAGENAME</var><br />
Checking status database...<br />
</samp>

<ul>
<li><p>If your request type is ITP (1) or RFP (5) you are asked for a short
   description and then for some information about the package:</p>

<samp>
Please briefly describe this package; this should be an appropriate short
description for the eventual package:<br />
&gt; <var>A DESCRIPTION</var><br />
<br />
Subject: ITP: <var>PACKAGENAME -- A DESCRIPTION</var><br />
Package: wnpp<br />
Version: N/A; reported 2002-01-30<br />
Severity: wishlist<br />
<br />
* Package name    : <var>PACKAGENAME</var><br />
  Version         : <var>x.y.z</var><br />
  Upstream Author : <var>Name &lt;somebody@some.org&gt;</var><br />
* URL             : <var>http://www.some.org/</var><br />
* License         : <var>(GPL, LGPL, BSD, MIT/X, etc.)</var><br />
  Description     : <var>A DESCRIPTION</var><br />
<br />
<br />
-- System Information<br />
...<br />
</samp>

<p>Below the <q>Description</q> line you should give more information
about the package.</p></li>

<li><p>If your request type is O (2) or RFA (3) you have to enter the name
of the package.</p>

<samp>
Choose the request type: <var>x</var><br />
Please enter the name of the package: <var>PACKAGENAME</var><br />
Checking status database...<br />
<br />
Subject: O: <var>PACKAGENAME -- SHORT DESCRIPTION</var><br />
Package: wnpp<br />
Version: N/A; reported 2002-01-30<br />
Severity: normal<br />
<br />
<br />
<br />
-- System Information<br />
...<br />
</samp>

<p>You should add some information about maintaining the package, the upstream
situation and maybe a reason why you want to give the package away.</p></li>

</ul>

<p>Then you are asked if you want to send your request:</p>

<samp>
Report will be sent to Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;<br />
Submit this bug report (e to edit) [Y|n|i|e|?]? <br />
</samp>


<toc-add-entry>Adding new entries via email</toc-add-entry>

<p>It is also possible to report reports/bugs against the WNPP via email.
The format of the submission should be like this:</p>

<samp>
  To: submit@bugs.debian.org<br />
  Subject: <var>TAG</var>: <var>package name</var> -- <var>short package description</var><br />
  <br />
  Package: wnpp<br />
  Severity: <var>see below</var><br />
  <br />
  <var>Some information about the package.</var>  (If this is an ITP or RFP a URL
  where the package (either the .deb or the original source) can be downloaded
  from is required, as well as
  information concerning its license.)
</samp>

<p>The tags to be used and their corresponding severities are:</p>

<table>
<colgroup span="3">
<col width="10%">
<col width="10%">
<col width="80%">
</colgroup>
<tr>
  <th valign="top"><a name="tag-o">O</a></th>
  <td valign="top"><em>normal</em></td>
  <td>The package has been <q>Orphaned</q>. It needs a new maintainer
      as soon as possible. If the package has a Priority higher or equal to
      standard, the severity should be set to important.
  </td>
</tr>
<tr>
  <th valign="top"><a name="tag-rfa">RFA</a></th>
  <td valign="top"><em>normal</em></td>
  <td>This is a <q>Request for Adoption</q>. Due to lack of time,
      resources, interest or something similar, the current maintainer is
      asking for someone else to maintain this package. They will maintain
      it in the meantime, but perhaps not in the best possible way.
      In short: the package needs a new maintainer.
  </td>
</tr>
<tr>
  <th valign="top"><a name="tag-rfh">RFH</a></th>
  <td valign="top"><em>normal</em></td>
  <td>This is a <q>Request For Help</q>. The
      current maintainer wants to continue to maintain this package,
      but they need some help to do this, because their time is limited
      or the package is quite big and needs several maintainers.
  </td>
</tr>
<tr>
  <th valign="top"><a name="tag-itp">ITP</a></th>
  <td valign="top"><em>wishlist</em></td>
  <td>This is an <q>Intent To Package</q>. Please submit a package
      description along with copyright and URL in such a report.
  </td>
</tr>
<tr>
  <th valign="top"><a name="tag-rfp">RFP</a></th>
  <td valign="top"><em>wishlist</em></td>
  <td>This is a <q>Request For Package</q>. Someone has found an
      interesting piece of software and would like someone else to maintain
      it for Debian. Please submit a package description along with
      copyright and URL in such a report.
  </td>
</tr>
</table>


<toc-add-entry>Removing entries</toc-add-entry>

<p>The procedures for closing these bugs are as follows:
</p>

<table>
<colgroup span="2">
<col width="10%">
<col width="90%">
</colgroup>
<tr>
  <th valign="top"><a name="howto-o">O</a></th>
  <td>If you are going to adopt a package, retitle its bug
      to replace <q>O</q> with <q>ITA</q>, in order for other people to know the
      package is being adopted and to prevent its automatic removal from the
      archive, and set yourself as the owner of the bug.
      To actually adopt the package, upload it with your name in
      its Maintainer: field, and put something like
      <code>
      * New maintainer (Closes: #<var>bugnumber</var>)
      </code>
      in the changelog of the package in order to automatically close this
      bug once the package has been installed; where <var>bugnumber</var>
      has to be replaced with the corresponding bugreport number.
      Furthermore, before you
      actually upload a new package with you as the maintainer, you should
      check if there is a new upstream release and you should try to fix the
      outstanding bugs.
  </td>
</tr>
<tr>
  <th valign="top"><a name="howto-rfa">RFA</a></th>
  <td><p>If you are going to adopt a package, retitle its bug
      to replace <q>RFA</q> with <q>ITA</q>, in order for other people to know the
      package is being adopted and to prevent its automatic removal from the
      archive, and set yourself as the owner of the bug.
      To actually adopt the package, upload it with your name in
      its Maintainer: field, and close this bug once the package has been
      installed.
      </p>

      <p>If you as the package maintainer decide to orphan the package you
      marked with <q>RFA</q>, please retitle the bug report and replace <q>RFA</q>
      with <q>O</q>. If you withdraw your request, please close the bug.</p>
  </td>
</tr>
<tr>
  <th valign="top"><a name="howto-rfh">RFH</a></th>
  <td><p>Normally this bug should only closed by the
      submitter, i.e. the package maintainer, if they consider it
      obsolete, either because one or more people have offered
      (and provided) their support or because they now think that
      they can handle the package for themself.
      </p>

      <p>If you as the package maintainer decides to change the RFH to
      a request for adoption (<q>RFA</q>) or if you want to
      orphan the package (<q>O</q>), please retitle the bug
      instead of closing it and filing a new one.</p>
  </td>
</tr>
<tr>
  <th valign="top"><a name="howto-itp">ITP</a></th>
  <td><p>package the software, upload it and close this bug once
      the package has been installed.
      </p>

      <p>If you change your mind, and no longer want to package this, either
      close the bug or retitle and reclassify it as RFP, as you see fit.</p>

	  <p>If you encounter problems with packaging the program (for example it
	  depends on another, not-yet-packaged program which you don't have
	  time to package), you might want to record these problems
      as additional information in the ITP, so that it is clear what's going on with
	  your packaging efforts.</p>
  </td>
</tr>
<tr>
  <th valign="top"><a name="howto-rfp">RFP</a></th>
  <td>If you are going to package this, retitle the bug report
      to replace <q>RFP</q> with <q>ITP</q>, in order for other people to know the
      program is already being packaged, and set yourself as the owner of
      the bug. Then package the software, upload it and close this bug once
      the package has been installed.
  </td>
</tr>
</table>

<p>If you feel that the developers' mailing list should know about your ITP,
RFA or anything else, add the header</p>
<pre>X-Debbugs-CC: debian-devel@lists.debian.org</pre>
<p>to the message.</p>

<p>Of course, the easiest way of closing these bugs is to include an entry
in the package changelog saying what you've done and append
<tt>(closes:&nbsp;bug#nnnnn)</tt> to it. This way the bug will be closed
automatically after the new package gets installed into the archive.</p>

<p>
<strong>Attention:</strong> if you need to reassign, retitle, or set the
owner of bug reports, you must do so by emailing the BTS control bot
<a href="$(HOME)/Bugs/server-control">directly</a> or by emailing the report
number @bugs.debian.org and using
<a href="$(HOME)/Bugs/Reporting#control">Control pseudo-headers</a>,
but <strong>not</strong> by filing new reports.
</p>

<p>Note: if a package remains orphaned for a very long time, we will examine
the situation to determine if the package is needed anymore &mdash; if not,
the FTP maintainers will be asked to remove the package from unstable.</p>

<p>If for some reason you need to contact the WNPP maintainers, they can be
reached at <email wnpp@debian.org>.</p>