Author: tille
Date: 2010-09-04 20:24:30 +0200 (Sat, 04 Sep 2010)
New Revision: 5212
Modified:
trunk/community/website/docs/policy.xml
Log:
Fixed ddtp location and typo
Modified: trunk/community/website/docs/policy.xml
===================================================================
--- trunk/community/website/docs/policy.xml 2010-09-04 14:28:45 UTC (rev
5211)
+++ trunk/community/website/docs/policy.xml 2010-09-04 18:24:30 UTC (rev
5212)
@@ -71,7 +71,7 @@
interested in joining us.</para>
<para>If you speak a language other than English, you can
contribute
rightaway with translations of package descriptions at
- <ulink
url="http://ddtp.debian.org";>ddtp.debian.org</ulink>.</para>
+ <ulink
url="http://ddtp.debian.net";>ddtp.debian.net</ulink>.</para>
<para>When working on these, you will find immediate targets
for improvements
of the original English versions, too. For these, though, you
need access
to Debian Med's source code repository. Very welcome are
tutorials that
@@ -91,7 +91,7 @@
<title id="readings">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/";>Developpers
Reference</ulink>: details best packaging practices.</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>
</itemizedlist>
@@ -118,7 +118,7 @@
To check sources out from our repostitories,
please do:
<itemizedlist>
<listitem>
- <para>If you are a member of
Debian Med or a Debian developper, you have write permission:</para>
+ <para>If you are a member of
Debian Med or a Debian developer, you have write permission:</para>
<blockquote>
<para><userinput>
<command>svn
co</command> <filename
class="directory">svn+ssh://[email protected]/svn/debian-med/trunk/...</filename>
@@ -183,7 +183,7 @@
</para>
<note><para>We are currently considering an alternative
layout in which all
the <filename>trunk</filename>,
<filename>tags</filename> and
- <filename>branches</filename> directories are grouped
together, so that developpers can checkout trunks without tags.</para></note>
+ <filename>branches</filename> directories are grouped
together, so that developers can checkout trunks without tags.</para></note>
<para>The Git repository is not structured: each
package is in its own Git repository.
But all of them are under the same
<filename>debian-med</filename> directory.</para>
</sect2>
@@ -325,7 +325,7 @@
<sect2>
<title>CDBS</title>
- <para>The use of CDBS is welcome as it helps us to
factorise our code. Nevertheless, please do not use complex CDBS for
non-trivial packages, so that other developpers can quickly understand the
package when doing QA work.</para>
+ <para>The use of CDBS is welcome as it helps us to
factorise our code. Nevertheless, please do not use complex CDBS for
non-trivial packages, so that other developers can quickly understand the
package when doing QA work.</para>
<para>It is technically possible to build CDBS packages
using Debhelper without the <filename>debian/compat</filename> file. Please do
not, and always include such a file according to the above guidelines.</para>
</sect2>
_______________________________________________
debian-med-commit mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/debian-med-commit
