/[python-modules]/www/python-modules-policy.html
ViewVC logotype

Contents of /www/python-modules-policy.html

Parent Directory Parent Directory | Revision Log Revision Log


Revision 4278 - (hide annotations) (download) (as text)
Fri Jan 4 20:27:51 2008 UTC (5 years, 4 months ago) by bernat-guest
File MIME type: text/html
File size: 15381 byte(s)
Add a note about NOT using "-l 2" with svn-inject (while pkg-perl
mentions it in their documentation).
1 hertzog 239 <?xml version="1.0" encoding="utf-8" ?>
2     <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3     <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
4     <head>
5     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
6 piotr 2990 <meta name="generator" content="Docutils 0.4.1: http://docutils.sourceforge.net/" />
7 hertzog 239 <title>Python Modules Packaging Team - Policy</title>
8     <meta name="author" content="Gustavo Franco &lt;stratus&#64;debian.org&gt;, RaphaĆ«l Hertzog &lt;hertzog&#64;debian.org&gt;" />
9     <style type="text/css">
10    
11     /*
12     :Author: David Goodger
13     :Contact: goodger@users.sourceforge.net
14 piotr 2990 :Date: $Date: 2005-12-18 01:56:14 +0100 (Sun, 18 Dec 2005) $
15     :Revision: $Revision: 4224 $
16 hertzog 239 :Copyright: This stylesheet has been placed in the public domain.
17    
18     Default cascading style sheet for the HTML output of Docutils.
19    
20     See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to
21     customize this style sheet.
22     */
23    
24     /* used to remove borders from tables and images */
25     .borderless, table.borderless td, table.borderless th {
26     border: 0 }
27    
28     table.borderless td, table.borderless th {
29     /* Override padding for "table.docutils td" with "! important".
30     The right padding separates the table cells. */
31     padding: 0 0.5em 0 0 ! important }
32    
33     .first {
34     /* Override more specific margin styles with "! important". */
35     margin-top: 0 ! important }
36    
37     .last, .with-subtitle {
38     margin-bottom: 0 ! important }
39    
40     .hidden {
41     display: none }
42    
43     a.toc-backref {
44     text-decoration: none ;
45     color: black }
46    
47     blockquote.epigraph {
48     margin: 2em 5em ; }
49    
50     dl.docutils dd {
51     margin-bottom: 0.5em }
52    
53     /* Uncomment (and remove this text!) to get bold-faced definition list terms
54     dl.docutils dt {
55     font-weight: bold }
56     */
57    
58     div.abstract {
59     margin: 2em 5em }
60    
61     div.abstract p.topic-title {
62     font-weight: bold ;
63     text-align: center }
64    
65     div.admonition, div.attention, div.caution, div.danger, div.error,
66     div.hint, div.important, div.note, div.tip, div.warning {
67     margin: 2em ;
68     border: medium outset ;
69     padding: 1em }
70    
71     div.admonition p.admonition-title, div.hint p.admonition-title,
72     div.important p.admonition-title, div.note p.admonition-title,
73     div.tip p.admonition-title {
74     font-weight: bold ;
75     font-family: sans-serif }
76    
77     div.attention p.admonition-title, div.caution p.admonition-title,
78     div.danger p.admonition-title, div.error p.admonition-title,
79     div.warning p.admonition-title {
80     color: red ;
81     font-weight: bold ;
82     font-family: sans-serif }
83    
84     /* Uncomment (and remove this text!) to get reduced vertical space in
85     compound paragraphs.
86     div.compound .compound-first, div.compound .compound-middle {
87     margin-bottom: 0.5em }
88    
89     div.compound .compound-last, div.compound .compound-middle {
90     margin-top: 0.5em }
91     */
92    
93     div.dedication {
94     margin: 2em 5em ;
95     text-align: center ;
96     font-style: italic }
97    
98     div.dedication p.topic-title {
99     font-weight: bold ;
100     font-style: normal }
101    
102     div.figure {
103     margin-left: 2em ;
104     margin-right: 2em }
105    
106     div.footer, div.header {
107     clear: both;
108     font-size: smaller }
109    
110     div.line-block {
111     display: block ;
112     margin-top: 1em ;
113     margin-bottom: 1em }
114    
115     div.line-block div.line-block {
116     margin-top: 0 ;
117     margin-bottom: 0 ;
118     margin-left: 1.5em }
119    
120     div.sidebar {
121     margin-left: 1em ;
122     border: medium outset ;
123     padding: 1em ;
124     background-color: #ffffee ;
125     width: 40% ;
126     float: right ;
127     clear: right }
128    
129     div.sidebar p.rubric {
130     font-family: sans-serif ;
131     font-size: medium }
132    
133     div.system-messages {
134     margin: 5em }
135    
136     div.system-messages h1 {
137     color: red }
138    
139     div.system-message {
140     border: medium outset ;
141     padding: 1em }
142    
143     div.system-message p.system-message-title {
144     color: red ;
145     font-weight: bold }
146    
147     div.topic {
148     margin: 2em }
149    
150     h1.section-subtitle, h2.section-subtitle, h3.section-subtitle,
151     h4.section-subtitle, h5.section-subtitle, h6.section-subtitle {
152     margin-top: 0.4em }
153    
154     h1.title {
155     text-align: center }
156    
157     h2.subtitle {
158     text-align: center }
159    
160     hr.docutils {
161     width: 75% }
162    
163     img.align-left {
164     clear: left }
165    
166     img.align-right {
167     clear: right }
168    
169     ol.simple, ul.simple {
170     margin-bottom: 1em }
171    
172     ol.arabic {
173     list-style: decimal }
174    
175     ol.loweralpha {
176     list-style: lower-alpha }
177    
178     ol.upperalpha {
179     list-style: upper-alpha }
180    
181     ol.lowerroman {
182     list-style: lower-roman }
183    
184     ol.upperroman {
185     list-style: upper-roman }
186    
187     p.attribution {
188     text-align: right ;
189     margin-left: 50% }
190    
191     p.caption {
192     font-style: italic }
193    
194     p.credits {
195     font-style: italic ;
196     font-size: smaller }
197    
198     p.label {
199     white-space: nowrap }
200    
201     p.rubric {
202     font-weight: bold ;
203     font-size: larger ;
204     color: maroon ;
205     text-align: center }
206    
207     p.sidebar-title {
208     font-family: sans-serif ;
209     font-weight: bold ;
210     font-size: larger }
211    
212     p.sidebar-subtitle {
213     font-family: sans-serif ;
214     font-weight: bold }
215    
216     p.topic-title {
217     font-weight: bold }
218    
219     pre.address {
220     margin-bottom: 0 ;
221     margin-top: 0 ;
222     font-family: serif ;
223     font-size: 100% }
224    
225     pre.literal-block, pre.doctest-block {
226     margin-left: 2em ;
227     margin-right: 2em ;
228     background-color: #eeeeee }
229    
230     span.classifier {
231     font-family: sans-serif ;
232     font-style: oblique }
233    
234     span.classifier-delimiter {
235     font-family: sans-serif ;
236     font-weight: bold }
237    
238     span.interpreted {
239     font-family: sans-serif }
240    
241     span.option {
242     white-space: nowrap }
243    
244     span.pre {
245     white-space: pre }
246    
247     span.problematic {
248     color: red }
249    
250     span.section-subtitle {
251     /* font-size relative to parent (h1..h6 element) */
252     font-size: 80% }
253    
254     table.citation {
255     border-left: solid 1px gray;
256     margin-left: 1px }
257    
258     table.docinfo {
259     margin: 2em 4em }
260    
261     table.docutils {
262     margin-top: 0.5em ;
263     margin-bottom: 0.5em }
264    
265     table.footnote {
266     border-left: solid 1px black;
267     margin-left: 1px }
268    
269     table.docutils td, table.docutils th,
270     table.docinfo td, table.docinfo th {
271     padding-left: 0.5em ;
272     padding-right: 0.5em ;
273     vertical-align: top }
274    
275     table.docutils th.field-name, table.docinfo th.docinfo-name {
276     font-weight: bold ;
277     text-align: left ;
278     white-space: nowrap ;
279     padding-left: 0 }
280    
281     h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
282     h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
283     font-size: 100% }
284    
285     tt.docutils {
286     background-color: #eeeeee }
287    
288     ul.auto-toc {
289     list-style-type: none }
290    
291     </style>
292     </head>
293     <body>
294     <div class="document" id="python-modules-packaging-team-policy">
295     <h1 class="title">Python Modules Packaging Team - Policy</h1>
296     <table class="docinfo" frame="void" rules="none">
297     <col class="docinfo-name" />
298     <col class="docinfo-content" />
299     <tbody valign="top">
300     <tr><th class="docinfo-name">Author:</th>
301     <td>Gustavo Franco &lt;<a class="reference" href="mailto:stratus&#64;debian.org">stratus&#64;debian.org</a>&gt;, RaphaĆ«l Hertzog &lt;<a class="reference" href="mailto:hertzog&#64;debian.org">hertzog&#64;debian.org</a>&gt;</td></tr>
302     <tr class="field"><th class="docinfo-name">License:</th><td class="field-body">GNU GPL v2 or later</td>
303     </tr>
304     <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
305     in Debian, by packaging available modules that may be useful and providing
306     a central location for packages maintained by a team, hence improving
307     responsiveness, integration and standardization.</p>
308     <p>PMPT or just python-modules is hosted at alioth.debian.org, the Debian
309     GForge installation. We currently have a SVN repository and a mailing list
310     whose email address can be used in the Maintainer field on co-maintained
311     packages.</p>
312     <p class="last">For more information send a message to: <a class="reference" href="mailto:debian-python&#64;lists.debian.org">debian-python&#64;lists.debian.org</a></p>
313     </td>
314     </tr>
315     </tbody>
316     </table>
317     <div class="contents topic">
318     <p class="topic-title first"><a id="contents" name="contents">Contents</a></p>
319     <ul class="simple">
320     <li><a class="reference" href="#joining-the-team" id="id1" name="id1">Joining the team</a></li>
321     <li><a class="reference" href="#maintainership" id="id2" name="id2">Maintainership</a></li>
322 piotr 2990 <li><a class="reference" href="#subversion-procedures" id="id3" name="id3">Subversion Procedures</a><ul>
323     <li><a class="reference" href="#hints" id="id4" name="id4">Hints:</a></li>
324 hertzog 239 </ul>
325 piotr 2990 </li>
326     <li><a class="reference" href="#quality-assurance" id="id5" name="id5">Quality Assurance</a></li>
327     <li><a class="reference" href="#license" id="id6" name="id6">License</a></li>
328     </ul>
329 hertzog 239 </div>
330     <div class="section">
331     <h1><a class="toc-backref" href="#id1" id="joining-the-team" name="joining-the-team">Joining the team</a></h1>
332     <p>The team is open to any python-related package maintainer. To be added on
333     the team, please send your request on <a class="reference" href="mailto:debian-python&#64;lists.debian.org">debian-python&#64;lists.debian.org</a>
334     indicate why you want to join the team: maintain your current packages
335     within the team, help maintain some specific packages, etc.
336     Don't forget to indicate your Alioth login !</p>
337 hertzog 2991 <p>Any Debian developer who wishes to integrate his packages in the team can do so
338     without requesting access (as the repository is writable by all DD). If one
339     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
340     so that he appears in the public member list displayed on Alioth's project page.</p>
341 piotr 2990 <p>The team accepts all contributors and is not restricted to Debian developers.
342     Several Debian developers of the team will gladly sponsor packages of non-DD
343     who are part of the team. Sponsorship requests can be sent on the main
344 pcc-guest 3598 discussion list or on #debian-python IRC channel (OFTC network).</p>
345 hertzog 239 <p>All team members should of course follow the main discussion list:
346     <a class="reference" href="mailto:debian-python&#64;lists.debian.org">debian-python&#64;lists.debian.org</a></p>
347     </div>
348     <div class="section">
349     <h1><a class="toc-backref" href="#id2" id="maintainership" name="maintainership">Maintainership</a></h1>
350     <p>A package maintained within the team should have the name of the team either
351     in the Maintainer field or in the Uploaders field.</p>
352     <p>Maintainer: Debian Python Modules Team &lt;<a class="reference" href="mailto:python-modules-team&#64;lists.alioth.debian.org">python-modules-team&#64;lists.alioth.debian.org</a>&gt;</p>
353 piotr 2990 <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&#64;lists.alioth.debian.org">DDPO_website</a>.</p>
354 hertzog 239 <p>Thus if you bring some packages into the team, you can keep your name in
355     the Maintainer field. You will receive bug reports and handle your package
356     as usual except that other team members may help from time to time and/or
357     take over when you're too busy.</p>
358     <p>If you put the team in the Maintainer field, the package will be handled
359     completely by the team and every member is invited to work on any
360     outstanding issue.</p>
361     <p>Team members who have broad interest should subscribe to the mailing list
362     <a class="reference" href="mailto:python-modules-team&#64;lists.alioth.debian.org">python-modules-team&#64;lists.alioth.debian.org</a> whereas members who are only
363     interested in some packages should use the Package Tracking System to
364     follow the packages.</p>
365     </div>
366     <div class="section">
367     <h1><a class="toc-backref" href="#id3" id="subversion-procedures" name="subversion-procedures">Subversion Procedures</a></h1>
368     <p>We're using a Subversion repository to maintain all the packages, then if you're not
369     already using it you will need to install svn-buildpackage.</p>
370     <p><em>The repository layout:</em></p>
371     <dl class="docutils">
372     <dt>metainfo/</dt>
373     <dd>Ignore this directory (reserved for future usage).</dd>
374     <dt>packages/</dt>
375     <dd><p class="first">The source packages are here.</p>
376     <dl class="last docutils">
377     <dt>package-foo</dt>
378     <dd><dl class="first last docutils">
379     <dt>branches</dt>
380     <dd>If you or someone wants to play with a package possible breaking the trunk, give it a name and do it here.</dd>
381     <dt>tags</dt>
382     <dd>For each release, a tag. More information below.</dd>
383     <dt>trunk</dt>
384     <dd>That's where the main development happens, it should contain only the debian/ subdirectory part of a package.</dd>
385     </dl>
386     </dd>
387     </dl>
388     </dd>
389     <dt>www/</dt>
390     <dd>Documents and stuff that will be or are being published online in our website.</dd>
391     </dl>
392 piotr 2990 <div class="section">
393     <h2><a class="toc-backref" href="#id4" id="hints" name="hints">Hints:</a></h2>
394 hertzog 239 <ul class="simple">
395     <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>
396     <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>
397     <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>
398     <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>
399     <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>
400     <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">&lt;args&gt;</span></tt>.</li>
401     </ul>
402     <p>For more information on how to maintain packages within the repository with svn-buildpackage:
403     <a class="reference" href="http://pkg-perl.alioth.debian.org/subversion.html">http://pkg-perl.alioth.debian.org/subversion.html</a></p>
404     <p>Please note that python-modules URLs are different than pkg-perl ones:</p>
405     <ul class="simple">
406     <li>svn+ssh://login&#64;svn.debian.org/svn/python-modules/packages/</li>
407     <li>svn://svn.debian.org/python-modules/packages/</li>
408     <li><a class="reference" href="http://svn.debian.org/wsvn/python-modules/">http://svn.debian.org/wsvn/python-modules/</a></li>
409     </ul>
410 bernat-guest 4278 <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>
411 hertzog 239 </div>
412 piotr 2990 </div>
413 hertzog 239 <div class="section">
414 piotr 2990 <h1><a class="toc-backref" href="#id5" id="quality-assurance" name="quality-assurance">Quality Assurance</a></h1>
415 hertzog 239 <p>The goal of the team is to maintain all packages as best as possible.
416     Thus every member is encouraged to do general QA work on all the
417     packages: fix bugs, test packages, improve them to use the latest python
418     packaging tools, etc.</p>
419     </div>
420     <div class="section">
421 piotr 2990 <h1><a class="toc-backref" href="#id6" id="license" name="license">License</a></h1>
422     <p>Copyright (c) 2005-2007 Python Modules Packaging Team. All rights reserved.
423 hertzog 239 This document is free software; you may redistribute it and/or modify
424     it under the same terms as GNU GPL v2 or later.</p>
425     </div>
426     </div>
427     </body>
428     </html>

  ViewVC Help
Powered by ViewVC 1.1.5