[med-svn] [Git][med-team/community/policy][master] Fix some links and add httpS
Dylan Aïssi
gitlab at salsa.debian.org
Mon Feb 12 22:47:09 UTC 2018
Dylan Aïssi pushed to branch master at Debian Med / community / policy
Commits:
aa577ddb by Dylan Aïssi at 2018-02-12T23:46:51+01:00
Fix some links and add httpS
- - - - -
1 changed file:
- policy.xml
Changes:
=====================================
policy.xml
=====================================
--- a/policy.xml
+++ b/policy.xml
@@ -43,7 +43,7 @@
</mediaobject>
<sect1 id="introduction">
<title>Introduction</title>
- <para>Debian Med is a <quote><ulink url="http://blends.alioth.debian.org/blends">Debian Pure Blend</ulink></quote>
+ <para>Debian Med is a <quote><ulink url="https://blends.alioth.debian.org/blends">Debian Pure Blend</ulink></quote>
with the aim to develop Debian into an operating system that is particularly
well tailored for the requirements for medical practice and research.</para>
<para>The Debian Med project presents packages that are associated
@@ -66,7 +66,7 @@
are fixed, if possible in collaboration with the upstream maintainer(s).
All this work would not be very useful if it remains confidential.</para>
<para>We also dedicate some time to advertise it to the world via
- <ulink url="http://www.debian.org">www.debian.org</ulink>
+ <ulink url="https://www.debian.org">www.debian.org</ulink>
and to ease the integration of new members.</para>
<para>Please contact us on <ulink url="mailto:debian-med at lists.debian.org">debian-med at lists.debian.org</ulink>
if you want to help to make medical and biological software available
@@ -84,19 +84,19 @@
<sect2 id="membership">
<title>Membership</title>
<para>To request membership to this group, please go on our
- <ulink url="http://alioth.debian.org/projects/debian-med">Alioth page</ulink>,
- or directly follow this <ulink url="http://alioth.debian.org/project/request.php?group_id=30063">link</ulink>.
+ <ulink url="https://alioth.debian.org/projects/debian-med">Alioth page</ulink>,
+ or directly follow this <ulink url="https://alioth.debian.org/project/request.php?group_id=30063">link</ulink>.
Remember that you must have an Alioth account before requesting
- membership (see <ulink url="http://alioth.debian.org/account/register.php">here</ulink>
+ membership (see <ulink url="https://alioth.debian.org/account/register.php">here</ulink>
to request an Alioth account).</para>
</sect2>
<sect2 id="readings">
<title>Essential readings</title>
<itemizedlist>
- <listitem><para>The <ulink url="http://www.debian.org/doc/debian-policy/">Debian Policy</ulink>: packages must conform to it.</para></listitem>
- <listitem><para>The <ulink url="http://www.debian.org/doc/developers-reference/">Developers Reference</ulink>: details best packaging practices.</para></listitem>
- <listitem><para>The <ulink url="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 <ulink url="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 <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>
</itemizedlist>
</sect2>
<sect2 id="meta">
@@ -118,7 +118,7 @@
<para>We use Git repositories, hosted
by Debian. You can have a look at
each repository through Alioth's web interfaces:
- <ulink url="http://anonscm.debian.org/cgit/debian-med">cgit</ulink>.</para>
+ <ulink url="https://anonscm.debian.org/cgit/debian-med">cgit</ulink>.</para>
<warning id="umask">
<para>
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
<command>debcheckout</command> command, from the
- <ulink url="http://packages.debian.org/devscripts">devscripts</ulink>
+ <ulink url="https://packages.debian.org/devscripts">devscripts</ulink>
package.
<itemizedlist>
<listitem>
@@ -187,7 +187,7 @@ Host *.debian.org
</para>
<para id="wiki-alioth">
In case of trouble getting SSH working it is a good idea to read
- <ulink url="http://wiki.debian.org/Alioth/SSH">this wiki article</ulink>.
+ <ulink url="https://wiki.debian.org/Alioth/SSH">this wiki article</ulink>.
</para>
</sect2>
<sect2 id="git-repository-structures">
@@ -219,8 +219,8 @@ Host *.debian.org
<title>Social Git</title>
<para>
For some projects, like the ones hosted on <ulink
- url="http://www.github.com">GitHub</ulink> or <ulink
- url="http://www.gitlab.com">Gitlab</ulink>, it may be easier to
+ url="https://www.github.com">GitHub</ulink> or <ulink
+ url="https://www.gitlab.com">GitLab</ulink>, it may be easier to
forward changes made in the Debian package if this one is itself
mirrored on the same platform, as a clone. In that case, the layouts
may vary from package to packages, and the branch that contains the
@@ -266,7 +266,7 @@ Host *.debian.org
<sect3 id="new-repository-with-gbp">
<title>To create a new local git repository</title>
<para>Before you create a new git repository you probably want to check whether your target project just exists.
- <ulink url="http://anonscm.debian.org/gitweb/?pf=debian-med">Here</ulink> is an overview about all projects
+ <ulink url="https://anonscm.debian.org/cgit/debian-med">Here</ulink> is an overview about all projects
packaged in Git by the Debian Med team.
</para>
<para>When the upstream sources are distributed as compressed <command>tar</command> archives (<literal>tar.gz</literal>, …):<programlisting>
@@ -435,7 +435,7 @@ rm ../*_source.changes</programlisting>
<para>Some newcomers tend to go the create DEBIAN dir, move files around and `dpkg-deb -b` way to create
Debian packages. Short answer: Forget about this. The only way to the official Debian mirror leads
via proper source packages. The right way to build Debian packages is described in
- <ulink url="http://www.debian.org/doc/manuals/maint-guide/">Debian New Maintainers' Guide</ulink>.
+ <ulink url="https://www.debian.org/doc/manuals/maint-guide/">Debian New Maintainers' Guide</ulink>.
</para>
<para>See also the <ulink url="http://anonscm.debian.org/viewvc/debian-med/trunk/package_template/">package
template</ulink> in our Subversion repository.
@@ -447,10 +447,10 @@ rm ../*_source.changes</programlisting>
<sect2 id="itp">
<title>Announcing intent to package</title>
<para>If you intent to work on a Debian package you should follow
- the <ulink url="http://www.debian.org/devel/wnpp/#l1">normal Debian rules</ulink> and file a <acronym>WNPP</acronym> bug report.</para>
+ the <ulink url="https://www.debian.org/devel/wnpp/#l1">normal Debian rules</ulink> and file a <acronym>WNPP</acronym> bug report.</para>
<para>It is a good idea to keep the Debian Med mailing list
<ulink url="mailto:debian-med at lists.debian.org">debian-med at lists.debian.org</ulink>
- <ulink url="http://www.debian.org/Bugs/Reporting#xcc"> in CC</ulink> and to set it
+ <ulink url="https://www.debian.org/Bugs/Reporting#xcc"> in CC</ulink> and to set it
as the owner of the ITP to keep your co-workers informed. This will ensure that we notice
if for some reason the package has not been uploaded.</para>
<para>In addition, please add the package to the <quote>task</quote> file where it fits
@@ -459,7 +459,7 @@ rm ../*_source.changes</programlisting>
<sect2 id="backports">
<title>Backports</title>
<para>
- Debian offers <ulink url="http://backports.debian.org">backports</ulink> to provide
+ Debian offers <ulink url="https://backports.debian.org">backports</ulink> to provide
up-to-date software for users of the official stable releases. Backports of Debian Med packages
should be kept as branches in our <link linkend="git-repository-structures">Git</link> repositories.
The branch should be named using the release code names. As an example, the backports branch for Debian 9 ("stretch")
@@ -476,7 +476,7 @@ rm ../*_source.changes</programlisting>
</programlisting>
And then building the package using a Stable chroot after making any necessary adjustments to the packaging. See the
<ulink url="https://wiki.debian.org/BuildingFormalBackports">wiki on backports</ulink> and
- the <ulink url="http://backports.debian.org">main backports website</ulink> for more detailed instructions.
+ the <ulink url="https://backports.debian.org">main backports website</ulink> for more detailed instructions.
</para>
<para>
When preparing subsequent versions of a backport, the changelog should
@@ -498,7 +498,7 @@ rm ../*_source.changes</programlisting>
Debian Med operates a <ulink url="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 <ulink url="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 <ulink url="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.
@@ -517,13 +517,13 @@ rm ../*_source.changes</programlisting>
<sect2 id="derivatives">
<title>Derivatives working together with Debian Med</title>
<para>
- Debian Med is proud that derivatives (like for instance <ulink url="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 <ulink url="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>
<sect2 id="r-packages">
<title>R packages</title>
<para>
- <ulink url="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.
+ <ulink url="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>
</sect2>
</sect1>
@@ -548,21 +548,21 @@ rm ../*_source.changes</programlisting>
<listitem>
<formalpara>
<title>Priority</title>
- <para>Should be <quote>optional</quote> unless forbidden by the Debian policy (<ulink url="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 (<ulink url="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 at 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 <ulink url="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 at 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 <ulink url="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 <ulink url="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 <ulink url="https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-team-upload">team upload</ulink>.
</para>
</formalpara>
</listitem>
@@ -585,7 +585,7 @@ rm ../*_source.changes</programlisting>
<formalpara id="vcs-url">
<title>Vcs-Git: and Vcs-Browser:</title>
<para>Please use the following templates, and refer to the Debian Policy
- <ulink url="http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-VCS-fields">§ 5.6.26</ulink>
+ <ulink url="https://www.debian.org/doc/debian-policy/#version-control-system-vcs-fields">§ 5.6.26</ulink>
for details:<programlisting>
Vcs-Browser: http://anonscm.debian.org/cgit/debian-med/<package>.git
Vcs-Git: git://anonscm.debian.org/debian-med/<package>.git</programlisting>
@@ -634,7 +634,7 @@ Vcs-Git: git://anonscm.debian.org/debian-med/<package>.git</programlisting
<sect2 id="debian-copyright">
<title><filename>debian/copyright</filename></title>
<para>
- We use the <ulink url="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 <ulink url="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
<formalpara>
@@ -660,7 +660,7 @@ Vcs-Git: git://anonscm.debian.org/debian-med/<package>.git</programlisting
<sect2 id="debian-upstream">
<title><filename>debian/upstream</filename></title>
<para>
- We use the <ulink url="http://wiki.debian.org/UpstreamMetadata#Fields">bibliographic information</ulink>
+ We use the <ulink url="https://wiki.debian.org/UpstreamMetadata#Fields">bibliographic information</ulink>
which should be stored in the file <filename>debian/upstream</filename>. The purpose of specifying this
is to enhance the contact to upstream which thus gets an extra reward of their work if their citations
show up on pages inside the Debian domain and if users more popularly are asked to cite upstream when
@@ -695,12 +695,12 @@ pristine-tar = True</programlisting>
<sect2 id="debian-readme-source">
<title><filename>debian/README.source</filename></title>
- <para>This file is recommended by the Policy (<ulink url="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 (<ulink url="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>
</sect2>
<sect2 id="debian-readme-test">
<title><filename>debian/README.test</filename></title>
- <para>This file was (<ulink url="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 (<ulink url="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>
</sect2>
<sect2 id="debian-source-format">
@@ -831,7 +831,7 @@ QUILT_PATCHES="debian/patches"</programlisting>
</blockquote>
<para>
After this, you're ready to start working with quilt. See also the
- instructions in the <ulink url="http://www.debian.org/doc/manuals/maint-guide/modify#quiltrc">New
+ instructions in the <ulink url="https://www.debian.org/doc/manuals/maint-guide/modify.en.html#quiltrc">New
Maintainer's Guide</ulink>.
</para>
<sect4 id="quilt-create">
View it on GitLab: https://salsa.debian.org/med-team/community/policy/commit/aa577ddbc50c052a9251574a841365d23ad04add
---
View it on GitLab: https://salsa.debian.org/med-team/community/policy/commit/aa577ddbc50c052a9251574a841365d23ad04add
You're receiving this email because of your account on salsa.debian.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/debian-med-commit/attachments/20180212/18a35f4e/attachment-0001.html>
More information about the debian-med-commit
mailing list