Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From: Piotr =?utf-8?Q?O=C5=BCarowski?= <piotr@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: Python Policy
Date: Mon, 19 Oct 2015 23:30:02 +0200
Message-ID: <qlqae-8it-37@gated-at.bofh.it>
References: <qlmzE-2TP-23@gated-at.bofh.it>
Old-Return-Path: <ozarow@gmail.com>
Sender: robomod@news.nic.it
Mail-Followup-To: Barry Warsaw <barry@debian.org>, debian-python <debian-python@lists.debian.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="s5/bjXLgkIwAv6Hi"
Content-Disposition: inline
User-Agent: Mutt/1.5.24 (2015-08-30)
Approved: robomod@news.nic.it
Lines: 274
Organization: linux.* mail to news gateway
Xref: csiph.com linux.debian.maint.python:7697


--s5/bjXLgkIwAv6Hi
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

| diff --git a/policy.rst b/policy.rst
| index c09f03a..9a9abb4 100644
| --- a/policy.rst
| +++ b/policy.rst
| @@ -1,20 +1,19 @@
| -=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
| - Python Modules Packaging Team - Policy
| -=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
| +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
| + Debian Python Modules Team - Policy
| +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
| =20
| -:Author: Gustavo Franco <stratus@debian.org>, Rapha=C3=ABl Hertzog <hert=
zog@debian.org>
| +:Author: Gustavo Franco <stratus@debian.org>, Rapha=C3=ABl Hertzog <hert=
zog@debian.org>, Barry Warsaw <barry@debian.org>
|  :License: GNU GPL v2 or later
| =20
|  :Introduction:
| -  Python Modules Packaging Team aims to improve the python modules situa=
tion
| -  in Debian, by packaging available modules that may be useful and provi=
ding
| -  a central location for packages maintained by a team, hence improving
| -  responsiveness, integration and standardization.
| +  The Debian Python Modules Team (DPMT) aims to improve the Python modul=
es
| +  situation in Debian, by packaging available modules that may be useful=
 and
| +  providing a central location for packages maintained by a team, hence
| +  improving responsiveness, integration, and standardization.
| =20
| -  PMPT or just python-modules is hosted at alioth.debian.org, the Debian
| -  GForge installation. We currently have a SVN repository and a mailing =
list
| -  whose email address can be used in the Maintainer field on co-maintain=
ed
| -  packages.
| +  The DPMT is hosted at alioth.debian.org, the Debian GForge installatio=
n. We
| +  currently have a git repository and a mailing list whose email address=
 can

+1 to all above

| +  be used in the ``Maintainer`` field on co-maintained packages.

I suggest:

s/``Maintainer`` field/``Maintainer`` or ``Uploaders`` fields/

| =20
|    For more information send a message to: debian-python@lists.debian.org
| =20
| @@ -24,16 +23,17 @@
|  Joining the team
|  ----------------
| =20
| -The team is open to any python-related package maintainer. To be added on
| +The team is open to any Python-related package maintainer. To be added on
|  the team, please send your request on debian-python@lists.debian.org
|  indicate why you want to join the team: maintain your current packages
|  within the team, help maintain some specific packages, etc.

how about adding (taken from the wiki :) this:

  In your email please state that you have read
  https://python-modules.alioth.debian.org/policy.html and
  that you accept it.

| -Don't forget to indicate your Alioth login !
| +Don't forget to indicate your Alioth login!
| =20
| -Any Debian developer who wishes to integrate his packages in the team ca=
n do so
| -without requesting access (as the repository is writable by all DD). If =
one
| +Any Debian developer who wishes to integrate his packages in the team ca=
n 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 requesting_ ac=
cess
| -so that he appears in the public member list displayed on Alioth's proje=
ct page.
| +so that they appear in the public member list displayed on Alioth's proj=
ect
| +page.
| =20
|  The team accepts all contributors and is not restricted to Debian develo=
pers.
|  Several Debian developers of the team will gladly sponsor packages of no=
n-DD
| @@ -48,71 +48,35 @@ Maintainership
|  --------------
| =20
|  A package maintained within the team should have the name of the team ei=
ther
| -in the Maintainer field or in the Uploaders field.
| +in the ``Maintainer`` field or in the ``Uploaders`` field.
| =20
|  Maintainer: Debian Python Modules Team <python-modules-team@lists.alioth=
=2Edebian.org>
| =20
|  This enables the team to have an overview of its packages on the DDPO_we=
bsite_.
| =20
| -* Team in Maintainers is a strong statement that fully collaborative
| -  maintenance is preferred. Anyone can commit to the vcs and upload as
| -  needed. A courtesy email to Uploaders can be nice but not required.
| +* Team in ``Maintainers`` is a strong statement that fully collaborative
| +  maintenance is preferred. Anyone can commit to the git repository and =
upload
| +  as needed. A courtesy email to ``Uploaders`` can be nice but not requi=
red.
| =20
| -* Team in Uploaders is a weak statement of collaboration. Help in mainta=
ining
| -  the package is appreciated, commits to vcs are freely welcomed, but be=
fore
| -  uploading, please contact the Maintainer for the green light.
| +* Team in ``Uploaders`` is a weak statement of collaboration. Help in
| +  maintaining the package is appreciated, commits to the git repository =
are
| +  freely welcomed, but before uploading, please contact the ``Maintainer=
`` for
| +  the green light.
| =20
|  Team members who have broad interest should subscribe to the mailing list
|  python-modules-team@lists.alioth.debian.org whereas members who are only
|  interested in some packages should use the Package Tracking System to
|  follow the packages.
| =20
| ----------------------
| -Subversion Procedures
| ----------------------
| -
| -We're using a Subversion repository to maintain all the packages, then i=
f you're not
| -already using it you will need to install svn-buildpackage.
| -
| -*The repository layout:*
| -
| -metainfo/
| -  Ignore this directory (reserved for future usage).
| -
| -packages/
| -  The source packages are here.
| -
| -  package-foo
| -      branches
| -         If you or someone wants to play with a package possible breakin=
g the trunk, give it a name and do it here.
| -      tags
| -         For each release, a tag. More information below.
| -      trunk
| -         That's where the main development happens, it should contain on=
ly the debian/ subdirectory part of a package.
| -
| -www/
| -  Documents and stuff that will be or are being published online in our =
website.
| -
| -
| -Hints:
| -=3D=3D=3D=3D=3D=3D
| -* To keep your package tree clean as pointed out above, always :code:`sv=
n-inject` your packages using :code:`-o` argument.
| -* If you svn-inject'ed a package without :code:`-o`, you should remove u=
pstream 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 ab=
ove the package, and svn-buildpackage will do the merge for you. More infor=
mation about this in the svn-buildpackage howto at /usr/share/doc/svn-build=
package/.
| -* 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-buildpac=
kage --svn-builder pdebuild <args>`.
| -
| -For more information on how to maintain packages within the repository w=
ith svn-buildpackage:
| -`http://pkg-perl.alioth.debian.org/subversion.html <https://web.archive.=
org/web/20141027193341/http://pkg-perl.alioth.debian.org/subversion.html>`_
| -
| -Please note that python-modules URLs are different than pkg-perl ones:
| -
| -* svn+ssh://login@svn.debian.org/svn/python-modules/packages/
| -* svn://svn.debian.org/python-modules/packages/
| -* http://anonscm.debian.org/viewvc/python-modules

+1 for all above changes

| +--------------
| +Git Procedures
| +--------------
| =20
| -Moreover, python-modules still use the default layout: don't pass :code:=
`-l 2` to :code:`svn-inject`.
| +As of October 9, 2015, the DPMT uses git as the version control system f=
or all
| +packages, and git-dpm as the patch management regime.  Details of the
| +procedures, standards for branches and tags, and common workflows are
| +maintained on the `Debian wiki <https://wiki.debian.org/Python/GitPackag=
ing>`_
| +page.

I'm against this change. If we want all team packages to follow some
rules, these rules need to be in policy document, not on the wiki page.
I don't want this page to be removed, policy can even point to it, but I
want it to be crystal clear that the binding document is the policy, not
any other document in the internet (even if it's very helpful).

What am I missing here is a set of branch/tag names and procedures
(f.e. I didn't know that git pull is not enough and I should gbp pull or
update pristine-tar branch by hand) and debian/patches related set of rules
(do we require git-dpm or can one use plain quilt of some other rules
are followed?)

| =20
|  -----------------
|  Quality Assurance
| @@ -127,7 +91,7 @@ packaging tools, etc.
|  License
|  -------
| =20
| -Copyright (c) 2005-2015 Python Modules Packaging Team. All rights reserv=
ed.
| +Copyright (c) 2005-2015 Debian Python Modules 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.
| =20
|=20

+1
--=20
Piotr O=C5=BCarowski                         Debian GNU/Linux Developer
www.ozarowski.pl          www.griffith.cc           www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

--s5/bjXLgkIwAv6Hi
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJWJWAPAAoJEK728aKnRXZFvyQQANaCOdHeUqxpg3skoSNQLP7Y
YyofC8T2sISOEks/EA2Y+mJkOE/pg/6eivzZPs6hpxssPPLH9WpK8xfC4nEAWtc1
dWteqVTUYOQ9Y0ZZ7/Hb0bpWKRWe+G0WM6DHPS8FGMbHuZ62BciJ2RghnnlopbO8
7/6OoSNNe9dH5Ir9awNfD2XY3uxJaYe0yiCqX8pDYZm7WK+lBSMBqH3JSoYTA+G+
JWUZHsophsF+RZbT9/lUs2NVb82vfSZyj/dZejMScf6o4d+ayABkeYm5c6LSeXLb
4FmscyNkP6gmXaEZ1sWHwztPdmbyWjEGwj+6OmhuQBPqrKFTSdPuo3/XdC4ZkDOG
QN1WpaWxXuo4T/qFa3dpxkVSS2ejTWTwA8UX1M5H5bJWaMG0nwXaQ7hWUGj3q2gQ
qBnV9sESfeTtey930p25hWX/2O3rk9fzxDpluu1TluSttHqDYVYE8r3aWz/Mi4zo
4aID1GoiK0OvNqnNcDPGJYNWTpqRAqeMzsAF0S/YUO8fF8bVDBrXjchkELQ+YcLr
+H25vKnJ8UaDC+d3JgGzQMogrn0gcBGUW+swttm+2j6Omuk4KRsxIGGXy1vScmHa
1QLdWmaAjSRkkoCMnzXtyRKGJN5KN/ilou1vkm+kAFq2IyvxrIWkCbdgmnpN+H07
DAPDy4UroNQ4jk3WDddy
=8D8L
-----END PGP SIGNATURE-----

--s5/bjXLgkIwAv6Hi--