Andreas Tille pushed to branch master at Debian Med / community / policy
Commits: 73cd01df by Andreas Tille at 2018-05-15T15:07:12+02:00 Base URL pointing to gitlab pages (not working yet), Maintainer address should be [email protected]. - - - - - 2 changed files: - policy.html - policy.xml Changes: ===================================== policy.html ===================================== --- a/policy.html +++ b/policy.html @@ -34,7 +34,7 @@ or directly follow this <a class="ulink" href="https://salsa.debian.org/groups/med-team/-/group_members/request_access"; target="_top">link</a>. Remember that you must have an account on Salsa.debian.org before requesting membership (see <a class="ulink" href="https://salsa.debian.org/users/sign_in"; target="_top">here</a> - to request an account on Salsa.debian.org).</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a id="readings"></a>Essential readings</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>The <a class="ulink" href="https://www.debian.org/doc/debian-policy/"; target="_top">Debian Policy</a>: packages must conform to it.</p></li><li class="listitem"><p>The <a class="ulink" href="https://www.debian.org/doc/developers-reference/"; target="_top">Developers Reference</a>: details best packaging practices.</p></li><li class="listitem"><p>The <a class="ulink" href="https://www.debian.org/doc/maint-guide/"; target="_top">New Maintainer's Guide</a>: puts a bit of the two above in practice.</p></li><li class="listitem"><p>The <a class="ulink" href="https://debian-med.alioth.debian.org/docs/policy.html"; target="_top">Debian Med Policy</a> (this document): explains how the work is organised in our team.</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a id="meta"></a>Contributing to this Policy</h3></div></div></div><p> + to request an account on Salsa.debian.org).</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a id="readings"></a>Essential readings</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>The <a class="ulink" href="https://www.debian.org/doc/debian-policy/"; target="_top">Debian Policy</a>: packages must conform to it.</p></li><li class="listitem"><p>The <a class="ulink" href="https://www.debian.org/doc/developers-reference/"; target="_top">Developers Reference</a>: details best packaging practices.</p></li><li class="listitem"><p>The <a class="ulink" href="https://www.debian.org/doc/maint-guide/"; target="_top">New Maintainer's Guide</a>: puts a bit of the two above in practice.</p></li><li class="listitem"><p>The <a class="ulink" href="https://med-team.pages.debian.net/policy.html"; target="_top">Debian Med Policy</a> (this document): explains how the work is organised in our team.</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a id="meta"></a>Contributing to this Policy</h3></div></div></div><p> This policy is itself maintained in Git and all team members have write access to its repository. </p><pre class="programlisting"> @@ -273,7 +273,7 @@ rm ../*_source.changes</pre><p> Debian R packages should be maintained within the <a class="ulink" href="https://wiki.debian.org/Teams/r-pkg-team"; target="_top">Debian R Packages Team</a>. </p><p> <a class="ulink" href="https://packages.debian.org/r-base-core"; target="_top">GNU R</a> 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 class="code">r-base-dev</code>, this can be acheived by adding the substitution variable <code class="code">${R:Depends}</code> in the <span class="emphasis"><em>Depends</em></span> field of the binary package. - </p></div></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tasks"></a>Tasks</h2></div></div></div><p>The Debian Med <a class="ulink" href="https://blends.debian.org/blends"; target="_top">Debian Pure Blend</a> is organised by <a class="ulink" href="https://blends.debian.org/med/tasks"; target="_top">tasks</a>, that group packages around broad themes such as <a class="ulink" href="https://blends.debian.org/med/tasks/imaging"; target="_top">medical imaging</a> for instance. The tasks list programs that are already packaged in Debian as well as packages in preparation.</p><p>The tasks files are not hosted in the Debian Med repositories, but in the Debian Blends repository. Nevertheless, all members of the Debian Med project on Salsa have write access to the Blends Git repository. You can easily check out its sources with the command <span class="command"><strong>debcheckout -a debian-med</strong></span>.</p><p>The syntax of the tasks files is very similar to Debian control files, and described in the <a class="ulink" href="https://blends.debian.org/blends/ch08.html#edittasksfiles"; target="_top">Debian Blends website</a>.</p></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="policy"></a>Policy</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a id="debian-control"></a><code class="filename">debian/control</code></h3></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p><strong>Section. </strong>Should be <span class="quote">“<span class="quote">science</span>”</span> for the source package.</p></li><li class="listitem"><p><strong>Priority. </strong>Should be <span class="quote">“<span class="quote">optional</span>”</span> unless forbidden by the Debian policy (<a class="ulink" href="https://www.debian.org/doc/debian-policy/#priorities"; target="_top">see §2.5</a>). Packages of priority <span class="quote">“<span class="quote">extra</span>”</span> are excluded from some QA tests.</p></li><li class="listitem"><p><strong>Maintainer. </strong>Maintainer should be <code class="code">Debian Med Packaging Team <code class="email"><<a class="email" href="mailto:[email protected]";>[email protected]</a>></code></code>. Please subscribe to this list if you list yourself in the <code class="code">Uploaders:</code> field of one of Debian Med's packages. You can refer to the <a class="ulink" href="https://qa.debian.org/[email protected]"; target="_top">QA page</a> corresponding to this email to gather information about the packages.</p></li><li class="listitem"><p><strong>Uploaders. </strong>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 <a class="ulink" href="https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-team-upload"; target="_top">team upload</a>. + </p></div></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="tasks"></a>Tasks</h2></div></div></div><p>The Debian Med <a class="ulink" href="https://blends.debian.org/blends"; target="_top">Debian Pure Blend</a> is organised by <a class="ulink" href="https://blends.debian.org/med/tasks"; target="_top">tasks</a>, that group packages around broad themes such as <a class="ulink" href="https://blends.debian.org/med/tasks/imaging"; target="_top">medical imaging</a> for instance. The tasks list programs that are already packaged in Debian as well as packages in preparation.</p><p>The tasks files are not hosted in the Debian Med repositories, but in the Debian Blends repository. Nevertheless, all members of the Debian Med project on Salsa have write access to the Blends Git repository. You can easily check out its sources with the command <span class="command"><strong>debcheckout -a debian-med</strong></span>.</p><p>The syntax of the tasks files is very similar to Debian control files, and described in the <a class="ulink" href="https://blends.debian.org/blends/ch08.html#edittasksfiles"; target="_top">Debian Blends website</a>.</p></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="policy"></a>Policy</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a id="debian-control"></a><code class="filename">debian/control</code></h3></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p><strong>Section. </strong>Should be <span class="quote">“<span class="quote">science</span>”</span> for the source package.</p></li><li class="listitem"><p><strong>Priority. </strong>Should be <span class="quote">“<span class="quote">optional</span>”</span> unless forbidden by the Debian policy (<a class="ulink" href="https://www.debian.org/doc/debian-policy/#priorities"; target="_top">see §2.5</a>). Packages of priority <span class="quote">“<span class="quote">extra</span>”</span> are excluded from some QA tests.</p></li><li class="listitem"><p><strong>Maintainer. </strong>Maintainer should be <code class="code">Debian Med Packaging Team <code class="email"><<a class="email" href="mailto:[email protected]";>[email protected]</a>></code></code>. Please subscribe to this list if you list yourself in the <code class="code">Uploaders:</code> field of one of Debian Med's packages. You can refer to the <a class="ulink" href="https://qa.debian.org/[email protected]"; target="_top">QA page</a> corresponding to this email to gather information about the packages.</p></li><li class="listitem"><p><strong>Uploaders. </strong>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 <a class="ulink" href="https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-team-upload"; target="_top">team upload</a>. </p></li><li class="listitem"><p><strong>Standards-Version. </strong>Please always use the latest unless there are concerns for backporting. If no changes are needed, please indicate this fact in the changelog, and increment the value of the field.</p></li><li class="listitem"><p><strong>Homepage. </strong>should be documented whenever possible</p></li><li class="listitem"><p><a id="vcs-url"></a><strong>Vcs-Git: and Vcs-Browser: </strong>Please use the following templates, and refer to the Debian Policy <a class="ulink" href="https://www.debian.org/doc/debian-policy/#version-control-system-vcs-fields"; target="_top">§ 5.6.26</a> for details:</p><pre class="programlisting"> ===================================== policy.xml ===================================== --- a/policy.xml +++ b/policy.xml @@ -3,7 +3,7 @@ href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl";?> <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd";> -<article xml:base="http://debian-med.alioth.debian.org/";> +<article xml:base="http://med-team.pages.debian.net/";> <title>Debian Med Group Policy</title> <articleinfo> <authorgroup> @@ -96,7 +96,7 @@ <listitem><para>The <ulink url="https://www.debian.org/doc/debian-policy/";>Debian Policy</ulink>: packages must conform to it.</para></listitem> <listitem><para>The <ulink url="https://www.debian.org/doc/developers-reference/";>Developers Reference</ulink>: details best packaging practices.</para></listitem> <listitem><para>The <ulink url="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 <ulink url="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> + <listitem><para>The <ulink url="https://med-team.pages.debian.net/policy.html";>Debian Med Policy</ulink> (this document): explains how the work is organised in our team.</para></listitem> </itemizedlist> </sect2> <sect2 id="meta"> @@ -516,7 +516,7 @@ rm ../*_source.changes</programlisting> <listitem> <formalpara> <title>Maintainer</title> - <para>Maintainer should be <code>Debian Med Packaging Team <email>[email protected]</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 <ulink url="https://qa.debian.org/[email protected]";>QA page</ulink> corresponding to this email to gather information about the packages.</para> + <para>Maintainer should be <code>Debian Med Packaging Team <email>[email protected]</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 <ulink url="https://qa.debian.org/[email protected]";>QA page</ulink> corresponding to this email to gather information about the packages.</para> </formalpara> </listitem> View it on GitLab: https://salsa.debian.org/med-team/community/policy/commit/73cd01df2bcc496aca8ccac682509dab3ad413e6 --- View it on GitLab: https://salsa.debian.org/med-team/community/policy/commit/73cd01df2bcc496aca8ccac682509dab3ad413e6 You're receiving this email because of your account on salsa.debian.org.
_______________________________________________ debian-med-commit mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-commit
