or directly follow this <ulinkurl="https://alioth.debian.org/project/request.php?group_id=30063">link</ulink>.
Remember that you must have an Alioth account before requesting
membership (see <ulinkurl="http://alioth.debian.org/account/register.php">here</ulink>
membership (see <ulinkurl="https://alioth.debian.org/account/register.php">here</ulink>
to request an Alioth account).</para>
</sect2>
<sect2id="readings">
<title>Essential readings</title>
<itemizedlist>
<listitem><para>The <ulinkurl="http://www.debian.org/doc/debian-policy/">Debian Policy</ulink>: packages must conform to it.</para></listitem>
<listitem><para>The <ulinkurl="http://www.debian.org/doc/developers-reference/">Developers Reference</ulink>: details best packaging practices.</para></listitem>
<listitem><para>The <ulinkurl="http://www.debian.org/doc/maint-guide/">New Maintainer's Guide</ulink>: puts a bit of the two above in practice.</para></listitem>
<listitem><para>The <ulinkurl="http://debian-med.alioth.debian.org/docs/policy.html">Debian Med Policy</ulink> (this document): explains how the work is organised in our team.</para></listitem>
<listitem><para>The <ulinkurl="https://www.debian.org/doc/debian-policy/">Debian Policy</ulink>: packages must conform to it.</para></listitem>
<listitem><para>The <ulinkurl="https://www.debian.org/doc/developers-reference/">Developers Reference</ulink>: details best packaging practices.</para></listitem>
<listitem><para>The <ulinkurl="https://www.debian.org/doc/maint-guide/">New Maintainer's Guide</ulink>: puts a bit of the two above in practice.</para></listitem>
<listitem><para>The <ulinkurl="https://debian-med.alioth.debian.org/docs/policy.html">Debian Med Policy</ulink> (this document): explains how the work is organised in our team.</para></listitem>
For most direct operations on the repositories in Alioth, an <command>umask</command> of <literal>002</literal> is necessary to avoid problems of missing write permission to the other team members.
@@ -130,7 +130,7 @@
To check the sources of a package (referred as
<emphasis><package></emphasis> below) in our repositories, use the
Debian Med operates a <ulinkurl="https://launchpad.net/~debian-med/+archive/ppa">Personal Package Archive</ulink> (PPA) on Launchpad, where packages are backported for Ubuntu. There is currently no team policy on what to build.
</para>
<para>
Please keep in mind issues like the possibility to upgrade to the next Ubuntu stable release. Packages that are backports can be made <ulinkurl="http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version">inferior in version by using a tilde</ulink>. If the package contains additional development, a version number without the tilde will make it higher, but not as high as the next Debian revision. For example: <code>2.12.0-1~natty1</code> (backport in PPA) <<code>2.12.0-1</code> (from Debian in Ubuntu) <<code>2.12.0-1natty1</code> (in PPA, containing additions) <<code>2.12.0-2</code> (from Debian in Ubuntu).
Please keep in mind issues like the possibility to upgrade to the next Ubuntu stable release. Packages that are backports can be made <ulinkurl="https://www.debian.org/doc/debian-policy/#version">inferior in version by using a tilde</ulink>. If the package contains additional development, a version number without the tilde will make it higher, but not as high as the next Debian revision. For example: <code>2.12.0-1~natty1</code> (backport in PPA) <<code>2.12.0-1</code> (from Debian in Ubuntu) <<code>2.12.0-1natty1</code> (in PPA, containing additions) <<code>2.12.0-2</code> (from Debian in Ubuntu).
</para>
<para>
Packages sent to this PPA may be kept as branches in our repositories.
<title>Derivatives working together with Debian Med</title>
<para>
Debian Med is proud that derivatives (like for instance <ulinkurl="http://nebc.nerc.ac.uk/tools/bio-linux">BioLinux</ulink>) are profiting from our work inside Debian and we try to establish strong connections to these derivatives. With BioLinux the connection is as strong that a common workflow was created where BioLinux developers are injecting their packaging straight into the Debian Med version control system. To make sure that there will be no conflicts with the Debian revisions some attention should be payed to the revision numbering. If the derivative is creating a new package (either from scratch or an upgraded version) it should get the version <code><upstreamversion>-0<derivativename><derivativerevision></code> (which is the versioning scheme usually used by Ubuntu).
Debian Med is proud that derivatives (like for instance <ulinkurl="http://environmentalomics.org/bio-linux/">BioLinux</ulink>) are profiting from our work inside Debian and we try to establish strong connections to these derivatives. With BioLinux the connection is as strong that a common workflow was created where BioLinux developers are injecting their packaging straight into the Debian Med version control system. To make sure that there will be no conflicts with the Debian revisions some attention should be payed to the revision numbering. If the derivative is creating a new package (either from scratch or an upgraded version) it should get the version <code><upstreamversion>-0<derivativename><derivativerevision></code> (which is the versioning scheme usually used by Ubuntu).
</para>
</sect2>
<sect2id="r-packages">
<title>R packages</title>
<para>
<ulinkurl="http://packages.debian.org/r-base-core">GNU R</ulink> sometimes introduces backward incompatibilities, so the current practice is to make packages depend on versions equal or higher to the one against which they were built. When using <code>r-base-dev</code>, this can be acheived by adding the substitution variable <code>${R:Depends}</code> in the <emphasis>Depends</emphasis> field of the binary package.
<ulinkurl="https://packages.debian.org/r-base-core">GNU R</ulink> sometimes introduces backward incompatibilities, so the current practice is to make packages depend on versions equal or higher to the one against which they were built. When using <code>r-base-dev</code>, this can be acheived by adding the substitution variable <code>${R:Depends}</code> in the <emphasis>Depends</emphasis> field of the binary package.
<para>Should be <quote>optional</quote> unless forbidden by the Debian policy (<ulinkurl="http://www.debian.org/doc/debian-policy/ch-archive.html#s-priorities">see §2.5</ulink>). Packages of priority <quote>extra</quote> are excluded from some QA tests.</para>
<para>Should be <quote>optional</quote> unless forbidden by the Debian policy (<ulinkurl="https://www.debian.org/doc/debian-policy/#priorities">see §2.5</ulink>). Packages of priority <quote>extra</quote> are excluded from some QA tests.</para>
</formalpara>
</listitem>
<listitem>
<formalpara>
<title>Maintainer</title>
<para>Maintainer should be <code>Debian Med Packaging Team <email>debian-med-packaging@lists.alioth.debian.org</email></code>. Please subscribe to this list if you list yourself in the <code>Uploaders:</code> field of one of Debian Med's packages. You can refer to the <ulinkurl="http://qa.debian.org/developer.php?login=debian-med-packaging@lists.alioth.debian.org">QA page</ulink> corresponding to this email to gather information about the packages.</para>
<para>Maintainer should be <code>Debian Med Packaging Team <email>debian-med-packaging@lists.alioth.debian.org</email></code>. Please subscribe to this list if you list yourself in the <code>Uploaders:</code> field of one of Debian Med's packages. You can refer to the <ulinkurl="https://qa.debian.org/developer.php?login=debian-med-packaging@lists.alioth.debian.org">QA page</ulink> corresponding to this email to gather information about the packages.</para>
</formalpara>
</listitem>
<listitem>
<formalpara>
<title>Uploaders</title>
<para>Please add yourself as an uploader when you have a significant interest in a package. Being Uploader means that you are expected to answer to the bug reports. For more occasional works, you can do a <ulinkurl="http://www.debian.org/doc/developers-reference/pkgs#nmu-team-upload">team upload</ulink>.
<para>Please add yourself as an uploader when you have a significant interest in a package. Being Uploader means that you are expected to answer to the bug reports. For more occasional works, you can do a <ulinkurl="https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-team-upload">team upload</ulink>.
We use the <ulinkurl="http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/">machine-readable format</ulink> for the <filename>debian/copyright</filename> file. The <computeroutput>Source</computeroutput> field does not need to contain the full URL to the particular version that is being packaged, since this can be determined by the <command>uscan</command> program with the <filename>debian/watch</filename> file (but note that some packagers use it as a bookmark to record when was the last copyright check). Please list yourself in the <computeroutput>Files: debian/*</computeroutput> section if you think that your contributions are not trivial and therefore subjected to copyright. Please chose a license that is compatible with the program you package. You can also use <quote>same as if it were in the public domain</quote> or <quote>same as the packaged program itself</quote>.
We use the <ulinkurl="https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/">machine-readable format</ulink> for the <filename>debian/copyright</filename> file. The <computeroutput>Source</computeroutput> field does not need to contain the full URL to the particular version that is being packaged, since this can be determined by the <command>uscan</command> program with the <filename>debian/watch</filename> file (but note that some packagers use it as a bookmark to record when was the last copyright check). Please list yourself in the <computeroutput>Files: debian/*</computeroutput> section if you think that your contributions are not trivial and therefore subjected to copyright. Please chose a license that is compatible with the program you package. You can also use <quote>same as if it were in the public domain</quote> or <quote>same as the packaged program itself</quote>.
</para>
You can create a <filename>debian/copyright</filename> file from scratch using
<para>This file is recommended by the Policy (<ulinkurl="http://www.debian.org/doc/debian-policy/ch-source.html#s-readmesource">§ 4.14</ulink>) from version 3.8.0 for documenting source package handling. Please follow the recommendation. For instance, this file is needed when we use a patch system, when the upstream sources are in another format than gzipped tar archive, when we repack the sources,…</para>
<para>This file is recommended by the Policy (<ulinkurl="https://www.debian.org/doc/debian-policy/#source-package-handling-debian-readme-source">§ 4.14</ulink>) from version 3.8.0 for documenting source package handling. Please follow the recommendation. For instance, this file is needed when we use a patch system, when the upstream sources are in another format than gzipped tar archive, when we repack the sources,…</para>
<para>This file was (<ulinkurl="http://lists.debian.org/debian-devel-announce/2011/01/msg00006.html">recommended by the Security team</ulink>) for describing to others than the regular maintainer how the package's functionality can properly be tested.</para>
<para>This file was (<ulinkurl="https://lists.debian.org/debian-devel-announce/2011/01/msg00006.html">recommended by the Security team</ulink>) for describing to others than the regular maintainer how the package's functionality can properly be tested.</para>
