[Python-modules-commits] r34167 - in www (python-modules-policy.html python-modules-policy.rst)
foka at users.alioth.debian.org
foka at users.alioth.debian.org
Sun Sep 6 04:23:19 UTC 2015
Date: Sunday, September 6, 2015 @ 04:23:17
Author: foka
Revision: 34167
Make minor revisions to python-modules-policy.rst
* Change ``text`` to :code:`text` to keep the same highlighting
when built with rst2html from Docutils 0.12 vs Docutils 0.4.1
* Change http://svn.debian.org/ http://anonscm.debian.org/
* Add commas where necessary
Modified:
www/python-modules-policy.html
www/python-modules-policy.rst
Modified: www/python-modules-policy.html
===================================================================
--- www/python-modules-policy.html 2015-09-06 01:15:16 UTC (rev 34166)
+++ www/python-modules-policy.html 2015-09-06 04:23:17 UTC (rev 34167)
@@ -3,16 +3,14 @@
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-<meta name="generator" content="Docutils 0.4.1: http://docutils.sourceforge.net/" />
+<meta name="generator" content="Docutils 0.12: http://docutils.sourceforge.net/" />
<title>Python Modules Packaging Team - Policy</title>
<meta name="author" content="Gustavo Franco <stratus@debian.org>, Raphaël Hertzog <hertzog@debian.org>" />
<style type="text/css">
/*
-:Author: David Goodger
-:Contact: goodger at users.sourceforge.net
-:Date: $Date: 2005-12-18 01:56:14 +0100 (Sun, 18 Dec 2005) $
-:Revision: $Revision: 4224 $
+:Author: David Goodger (goodger at python.org)
+:Id: $Id: html4css1.css 7614 2013-02-21 15:55:51Z milde $
:Copyright: This stylesheet has been placed in the public domain.
Default cascading style sheet for the HTML output of Docutils.
@@ -50,6 +48,10 @@
dl.docutils dd {
margin-bottom: 0.5em }
+object[type="image/svg+xml"], object[type="application/x-shockwave-flash"] {
+ overflow: hidden;
+}
+
/* Uncomment (and remove this text!) to get bold-faced definition list terms
dl.docutils dt {
font-weight: bold }
@@ -76,7 +78,7 @@
div.attention p.admonition-title, div.caution p.admonition-title,
div.danger p.admonition-title, div.error p.admonition-title,
-div.warning p.admonition-title {
+div.warning p.admonition-title, .code .error {
color: red ;
font-weight: bold ;
font-family: sans-serif }
@@ -118,7 +120,7 @@
margin-left: 1.5em }
div.sidebar {
- margin-left: 1em ;
+ margin: 0 0 0.5em 1em ;
border: medium outset ;
padding: 1em ;
background-color: #ffffee ;
@@ -160,12 +162,39 @@
hr.docutils {
width: 75% }
-img.align-left {
- clear: left }
+img.align-left, .figure.align-left, object.align-left {
+ clear: left ;
+ float: left ;
+ margin-right: 1em }
-img.align-right {
- clear: right }
+img.align-right, .figure.align-right, object.align-right {
+ clear: right ;
+ float: right ;
+ margin-left: 1em }
+img.align-center, .figure.align-center, object.align-center {
+ display: block;
+ margin-left: auto;
+ margin-right: auto;
+}
+
+.align-left {
+ text-align: left }
+
+.align-center {
+ clear: both ;
+ text-align: center }
+
+.align-right {
+ text-align: right }
+
+/* reset inner alignment in figures */
+div.align-right {
+ text-align: inherit }
+
+/* div.align-center * { */
+/* text-align: left } */
+
ol.simple, ul.simple {
margin-bottom: 1em }
@@ -219,14 +248,21 @@
pre.address {
margin-bottom: 0 ;
margin-top: 0 ;
- font-family: serif ;
- font-size: 100% }
+ font: inherit }
-pre.literal-block, pre.doctest-block {
+pre.literal-block, pre.doctest-block, pre.math, pre.code {
margin-left: 2em ;
- margin-right: 2em ;
- background-color: #eeeeee }
+ margin-right: 2em }
+pre.code .ln { color: grey; } /* line numbers */
+pre.code, code { background-color: #eeeeee }
+pre.code .comment, code .comment { color: #5C6576 }
+pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold }
+pre.code .literal.string, code .literal.string { color: #0C5404 }
+pre.code .name.builtin, code .name.builtin { color: #352B84 }
+pre.code .deleted, code .deleted { background-color: #DEB0A1}
+pre.code .inserted, code .inserted { background-color: #A3D289}
+
span.classifier {
font-family: sans-serif ;
font-style: oblique }
@@ -278,13 +314,25 @@
white-space: nowrap ;
padding-left: 0 }
+/* "booktabs" style (no vertical lines) */
+table.docutils.booktabs {
+ border: 0px;
+ border-top: 2px solid;
+ border-bottom: 2px solid;
+ border-collapse: collapse;
+}
+table.docutils.booktabs * {
+ border: 0px;
+}
+table.docutils.booktabs th {
+ border-bottom: thin solid;
+ text-align: left;
+}
+
h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
font-size: 100% }
-tt.docutils {
- background-color: #eeeeee }
-
ul.auto-toc {
list-style-type: none }
@@ -298,7 +346,7 @@
<col class="docinfo-content" />
<tbody valign="top">
<tr><th class="docinfo-name">Author:</th>
-<td>Gustavo Franco <<a class="reference" href="mailto:stratus@debian.org">stratus@debian.org</a>>, Raphaël Hertzog <<a class="reference" href="mailto:hertzog@debian.org">hertzog@debian.org</a>></td></tr>
+<td>Gustavo Franco <<a class="reference external" href="mailto:stratus@debian.org">stratus@debian.org</a>>, Raphaël Hertzog <<a class="reference external" href="mailto:hertzog@debian.org">hertzog@debian.org</a>></td></tr>
<tr class="field"><th class="docinfo-name">License:</th><td class="field-body">GNU GPL v2 or later</td>
</tr>
<tr class="field"><th class="docinfo-name">Introduction:</th><td class="field-body"><p class="first">Python Modules Packaging Team aims to improve the python modules situation
@@ -309,48 +357,48 @@
GForge installation. We currently have a SVN repository and a mailing list
whose email address can be used in the Maintainer field on co-maintained
packages.</p>
-<p class="last">For more information send a message to: <a class="reference" href="mailto:debian-python@lists.debian.org">debian-python@lists.debian.org</a></p>
+<p class="last">For more information send a message to: <a class="reference external" href="mailto:debian-python@lists.debian.org">debian-python@lists.debian.org</a></p>
</td>
</tr>
</tbody>
</table>
-<div class="contents topic">
-<p class="topic-title first"><a id="contents" name="contents">Contents</a></p>
+<div class="contents topic" id="contents">
+<p class="topic-title first">Contents</p>
<ul class="simple">
-<li><a class="reference" href="#joining-the-team" id="id1" name="id1">Joining the team</a></li>
-<li><a class="reference" href="#maintainership" id="id2" name="id2">Maintainership</a></li>
-<li><a class="reference" href="#subversion-procedures" id="id3" name="id3">Subversion Procedures</a><ul>
-<li><a class="reference" href="#hints" id="id4" name="id4">Hints:</a></li>
+<li><a class="reference internal" href="#joining-the-team" id="id1">Joining the team</a></li>
+<li><a class="reference internal" href="#maintainership" id="id2">Maintainership</a></li>
+<li><a class="reference internal" href="#subversion-procedures" id="id3">Subversion Procedures</a><ul>
+<li><a class="reference internal" href="#hints" id="id4">Hints:</a></li>
</ul>
</li>
-<li><a class="reference" href="#quality-assurance" id="id5" name="id5">Quality Assurance</a></li>
-<li><a class="reference" href="#license" id="id6" name="id6">License</a></li>
+<li><a class="reference internal" href="#quality-assurance" id="id5">Quality Assurance</a></li>
+<li><a class="reference internal" href="#license" id="id6">License</a></li>
</ul>
</div>
-<div class="section">
-<h1><a class="toc-backref" href="#id1" id="joining-the-team" name="joining-the-team">Joining the team</a></h1>
+<div class="section" id="joining-the-team">
+<h1><a class="toc-backref" href="#id1">Joining the team</a></h1>
<p>The team is open to any python-related package maintainer. To be added on
-the team, please send your request on <a class="reference" href="mailto:debian-python@lists.debian.org">debian-python@lists.debian.org</a>
+the team, please send your request on <a class="reference external" href="mailto:debian-python@lists.debian.org">debian-python@lists.debian.org</a>
indicate why you want to join the team: maintain your current packages
within the team, help maintain some specific packages, etc.
Don't forget to indicate your Alioth login !</p>
<p>Any Debian developer who wishes to integrate his packages in the team can do so
without requesting access (as the repository is writable by all DD). If one
-wants to be more involved in the team, we still recommend <a class="reference" href="https://alioth.debian.org/project/request.php?group_id=30714">requesting</a> access
+wants to be more involved in the team, we still recommend <a class="reference external" href="https://alioth.debian.org/project/request.php?group_id=30714">requesting</a> access
so that he appears in the public member list displayed on Alioth's project page.</p>
<p>The team accepts all contributors and is not restricted to Debian developers.
Several Debian developers of the team will gladly sponsor packages of non-DD
who are part of the team. Sponsorship requests can be sent on the main
discussion list or on #debian-python IRC channel (OFTC network).</p>
<p>All team members should of course follow the main discussion list:
-<a class="reference" href="mailto:debian-python@lists.debian.org">debian-python@lists.debian.org</a></p>
+<a class="reference external" href="mailto:debian-python@lists.debian.org">debian-python@lists.debian.org</a></p>
</div>
-<div class="section">
-<h1><a class="toc-backref" href="#id2" id="maintainership" name="maintainership">Maintainership</a></h1>
+<div class="section" id="maintainership">
+<h1><a class="toc-backref" href="#id2">Maintainership</a></h1>
<p>A package maintained within the team should have the name of the team either
in the Maintainer field or in the Uploaders field.</p>
-<p>Maintainer: Debian Python Modules Team <<a class="reference" href="mailto:python-modules-team@lists.alioth.debian.org">python-modules-team@lists.alioth.debian.org</a>></p>
-<p>This enables the team to have an overview of its packages on the <a class="reference" href="http://qa.debian.org/developer.php?login=python-modules-team@lists.alioth.debian.org">DDPO_website</a>.</p>
+<p>Maintainer: Debian Python Modules Team <<a class="reference external" href="mailto:python-modules-team@lists.alioth.debian.org">python-modules-team@lists.alioth.debian.org</a>></p>
+<p>This enables the team to have an overview of its packages on the <a class="reference external" href="http://qa.debian.org/developer.php?login=python-modules-team@lists.alioth.debian.org">DDPO_website</a>.</p>
<p>Thus if you bring some packages into the team, you can keep your name in
the Maintainer field. You will receive bug reports and handle your package
as usual except that other team members may help from time to time and/or
@@ -359,12 +407,12 @@
completely by the team and every member is invited to work on any
outstanding issue.</p>
<p>Team members who have broad interest should subscribe to the mailing list
-<a class="reference" href="mailto:python-modules-team@lists.alioth.debian.org">python-modules-team@lists.alioth.debian.org</a> whereas members who are only
+<a class="reference external" href="mailto:python-modules-team@lists.alioth.debian.org">python-modules-team@lists.alioth.debian.org</a> whereas members who are only
interested in some packages should use the Package Tracking System to
follow the packages.</p>
</div>
-<div class="section">
-<h1><a class="toc-backref" href="#id3" id="subversion-procedures" name="subversion-procedures">Subversion Procedures</a></h1>
+<div class="section" id="subversion-procedures">
+<h1><a class="toc-backref" href="#id3">Subversion Procedures</a></h1>
<p>We're using a Subversion repository to maintain all the packages, then if you're not
already using it you will need to install svn-buildpackage.</p>
<p><em>The repository layout:</em></p>
@@ -389,37 +437,37 @@
<dt>www/</dt>
<dd>Documents and stuff that will be or are being published online in our website.</dd>
</dl>
-<div class="section">
-<h2><a class="toc-backref" href="#id4" id="hints" name="hints">Hints:</a></h2>
+<div class="section" id="hints">
+<h2><a class="toc-backref" href="#id4">Hints:</a></h2>
<ul class="simple">
-<li>To keep your package tree clean as pointed out above, always <tt class="docutils literal"><span class="pre">svn-inject</span></tt> your packages using -o argument.</li>
-<li>If you svn-inject'ed a package without -o you should remove upstream sources and run <tt class="docutils literal"><span class="pre">svn</span> <span class="pre">propset</span> <span class="pre">mergeWithUpstream</span> <span class="pre">1</span> <span class="pre">debian/</span></tt>.</li>
-<li>Since you are keeping only debian/ directory in the svn tree you need to put the 'package-foo'_'version'.orig.tar.gz in tarballs/ a directory above the package and svn-buildpackage will do the merge for you. More information about this in the svn-buildpackage howto at /usr/share/doc/svn-buildpackage/.</li>
-<li>After upload, tag the latest revision running <tt class="docutils literal"><span class="pre">svn-buildpackage</span> <span class="pre">--svn-tag-only</span></tt> into 'package-foo' directory.</li>
-<li>You can revert the changelog changes after tagging, running <tt class="docutils literal"><span class="pre">svn</span> <span class="pre">revert</span> <span class="pre">debian/changelog</span></tt>.</li>
-<li>If you're a pbuilder user, you can invoke it using <tt class="docutils literal"><span class="pre">svn-buildpackage</span> <span class="pre">--svn-builder</span> <span class="pre">pdebuild</span> <span class="pre"><args></span></tt>.</li>
+<li>To keep your package tree clean as pointed out above, always <code>svn-inject</code> your packages using <code>-o</code> argument.</li>
+<li>If you svn-inject'ed a package without <code>-o</code>, you should remove upstream sources and run <code>svn propset mergeWithUpstream 1 debian/</code>.</li>
+<li>Since you are keeping only debian/ directory in the svn tree, you need to put the 'package-foo'_'version'.orig.tar.gz in tarballs/ a directory above the package, and svn-buildpackage will do the merge for you. More information about this in the svn-buildpackage howto at /usr/share/doc/svn-buildpackage/.</li>
+<li>After upload, tag the latest revision running <code>svn-buildpackage --svn-tag-only</code> into 'package-foo' directory.</li>
+<li>You can revert the changelog changes after tagging, running <code>svn revert debian/changelog</code>.</li>
+<li>If you're a pbuilder user, you can invoke it using <code>svn-buildpackage --svn-builder pdebuild <args></code>.</li>
</ul>
<p>For more information on how to maintain packages within the repository with svn-buildpackage:
-<a class="reference" href="https://web.archive.org/web/20141027193341/http://pkg-perl.alioth.debian.org/subversion.html">http://pkg-perl.alioth.debian.org/subversion.html</a></p>
+<a class="reference external" href="https://web.archive.org/web/20141027193341/http://pkg-perl.alioth.debian.org/subversion.html">http://pkg-perl.alioth.debian.org/subversion.html</a></p>
<p>Please note that python-modules URLs are different than pkg-perl ones:</p>
<ul class="simple">
<li>svn+ssh://login@svn.debian.org/svn/python-modules/packages/</li>
<li>svn://svn.debian.org/python-modules/packages/</li>
-<li><a class="reference" href="http://svn.debian.org/wsvn/python-modules/">http://svn.debian.org/wsvn/python-modules/</a></li>
+<li><a class="reference external" href="http://anonscm.debian.org/viewvc/python-modules/">http://anonscm.debian.org/viewvc/python-modules/</a></li>
</ul>
-<p>Moreover, python-modules still use the default layout: don't pass <tt class="docutils literal"><span class="pre">-l</span> <span class="pre">2</span></tt> to <tt class="docutils literal"><span class="pre">svn-inject</span></tt>.</p>
+<p>Moreover, python-modules still use the default layout: don't pass <code>-l 2</code> to <code>svn-inject</code>.</p>
</div>
</div>
-<div class="section">
-<h1><a class="toc-backref" href="#id5" id="quality-assurance" name="quality-assurance">Quality Assurance</a></h1>
+<div class="section" id="quality-assurance">
+<h1><a class="toc-backref" href="#id5">Quality Assurance</a></h1>
<p>The goal of the team is to maintain all packages as best as possible.
Thus every member is encouraged to do general QA work on all the
packages: fix bugs, test packages, improve them to use the latest python
packaging tools, etc.</p>
</div>
-<div class="section">
-<h1><a class="toc-backref" href="#id6" id="license" name="license">License</a></h1>
-<p>Copyright (c) 2005-2007 Python Modules Packaging Team. All rights reserved.
+<div class="section" id="license">
+<h1><a class="toc-backref" href="#id6">License</a></h1>
+<p>Copyright (c) 2005-2015 Python Modules Packaging Team. All rights reserved.
This document is free software; you may redistribute it and/or modify
it under the same terms as GNU GPL v2 or later.</p>
</div>
Modified: www/python-modules-policy.rst
===================================================================
--- www/python-modules-policy.rst 2015-09-06 01:15:16 UTC (rev 34166)
+++ www/python-modules-policy.rst 2015-09-06 04:23:17 UTC (rev 34167)
@@ -97,12 +97,12 @@
Hints:
======
-* To keep your package tree clean as pointed out above, always ``svn-inject`` your packages using -o argument.
-* If you svn-inject'ed a package without -o you should remove upstream sources and run ``svn propset mergeWithUpstream 1 debian/``.
-* Since you are keeping only debian/ directory in the svn tree you need to put the 'package-foo'_'version'.orig.tar.gz in tarballs/ a directory above the package and svn-buildpackage will do the merge for you. More information about this in the svn-buildpackage howto at /usr/share/doc/svn-buildpackage/.
-* After upload, tag the latest revision running ``svn-buildpackage --svn-tag-only`` into 'package-foo' directory.
-* You can revert the changelog changes after tagging, running ``svn revert debian/changelog``.
-* If you're a pbuilder user, you can invoke it using ``svn-buildpackage --svn-builder pdebuild <args>``.
+* To keep your package tree clean as pointed out above, always :code:`svn-inject` your packages using :code:`-o` argument.
+* If you svn-inject'ed a package without :code:`-o`, you should remove upstream sources and run :code:`svn propset mergeWithUpstream 1 debian/`.
+* Since you are keeping only debian/ directory in the svn tree, you need to put the 'package-foo'_'version'.orig.tar.gz in tarballs/ a directory above the package, and svn-buildpackage will do the merge for you. More information about this in the svn-buildpackage howto at /usr/share/doc/svn-buildpackage/.
+* After upload, tag the latest revision running :code:`svn-buildpackage --svn-tag-only` into 'package-foo' directory.
+* You can revert the changelog changes after tagging, running :code:`svn revert debian/changelog`.
+* If you're a pbuilder user, you can invoke it using :code:`svn-buildpackage --svn-builder pdebuild <args>`.
For more information on how to maintain packages within the repository with svn-buildpackage:
`http://pkg-perl.alioth.debian.org/subversion.html <https://web.archive.org/web/20141027193341/http://pkg-perl.alioth.debian.org/subversion.html>`_
@@ -111,9 +111,9 @@
* svn+ssh://login@svn.debian.org/svn/python-modules/packages/
* svn://svn.debian.org/python-modules/packages/
-* http://svn.debian.org/wsvn/python-modules/
+* http://anonscm.debian.org/viewvc/python-modules/
-Moreover, python-modules still use the default layout: don't pass ``-l 2`` to ``svn-inject``.
+Moreover, python-modules still use the default layout: don't pass :code:`-l 2` to :code:`svn-inject`.
-----------------
Quality Assurance
@@ -128,7 +128,7 @@
License
-------
-Copyright (c) 2005-2007 Python Modules Packaging Team. All rights reserved.
+Copyright (c) 2005-2015 Python Modules Packaging Team. All rights reserved.
This document is free software; you may redistribute it and/or modify
it under the same terms as GNU GPL v2 or later.
More information about the Python-modules-commits
mailing list