Hi Michael,
On 07/02/16 21:50, Michael Stapelberg wrote:
> tincho, I think you are in agreement with the policy change that aviau
> suggested. Have you read the patch (which you can find
> at
> https://lists.alioth.debian.org/pipermail/pkg-go-maintainers/Week-of-Mon-20160118/003015.html)
> or were you referring to the discussion as a whole?
I am sorry, I was not clear there (it was pretty late after all).
I agree with the direction of the policy change, although I think it
falls a bit short of would I would like to happen.
And I was worried in general with the discussion, because I had the
impression, from Dmitry's comments, that the changes were going to more
towards individual ownership.
> If your comment was in fact related to the patch, could you outline the
> specific differences to the pkg-perl status quo that you dislike?
Sadly, this status quo is not written in any document to show. If you
read their policy, being in Uploaders only shows you have devoted some
significant work to that package, or you feel some responsibility for it.
Mostly, what I don't like is that ownership of packages seems somehow
still encouraged. Or at the same level as total team maintenance.
Also, I think it lacks some notes on how to communicate with other
people when working on a package.
To make it clearer and to the point, I made an ammendment myself
addressing these points, attached below.
Although I presume this change might not be acceptable for some people,
I think the notes about changelog handling would be a good addition.
--
Martín Ferrari (Tincho)
diff --git a/packaging.asciidoc b/packaging.asciidoc
index 4b402f0..e473079 100644
--- a/packaging.asciidoc
+++ b/packaging.asciidoc
@@ -11,16 +11,25 @@ All Go packages are team-maintained in the pkg-go team. This has multiple advant
. There are no single points of failure, if one maintainer cannot continue
maintaining a package, another maintainer can easily help out or take over.
- . While it is strongly recommended to ask maintainers for permission before
- touching their package in any significant way, cleanup changes can very
- easily be applied to all packages.
. All packages can share the same technical standards and workflows.
. When working within a team anyway, it is much easier to get help on any
technical issue.
-On the technical side, put `Debian Go Packaging Team
-<[email protected]>` into the Maintainer field in
-`debian/control` and add yourself as Uploader.
+A package maintained within the team should have the name of the team either in
+the `Maintainer` field or in the `Uploaders` field. We spell the team like this:
+`Debian Go Packaging Team <[email protected]>`. This
+enables the team to have an overview of its packages on the DDPO website.
+
+Putting the 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
+required.
+
+If for some reason, a package needs tighter control by its original
+maintainers, putting the 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.
//////////////////////////////////////////////////////////////////////////
// TODO: add an example link
@@ -55,15 +64,24 @@ git, hg, svn. Afterwards, a date follows in the format YYYYMMDD. The last part
after the dash is the Debian version number.
In case you make more than one snapshot per day, you can append a snapshot
-number after the date, e.g. 0.0_git201306062-1. This should rarely be
+number after the date, e.g. 0.0_git20130606*2*-1. This should rarely be
necessary.
=== changelog: UNRELEASED
During the time when you still work on a package, i.e. before it is ready to
-upload, please put âUNRELEASEDâ into the distribution field in
-debian/changelog. When the package is ready for uploading, change it to
-âunstableâ.
+upload, please put `UNRELEASED` into the distribution field in
+`debian/changelog` (`dch -v <debian_version>` will do it automatically). When
+the package is ready for uploading, change it to `unstable` (`dch -r`).
+
+If you change something that has to be noted in debian/changelog, just add a
+line to the current entry (dch -a). The [firstname lastname] markers added by
+dch are okay to give credit to non-upload-permitted contributors (also for the
+initial changelog entry).
+
+Important NOTES to other group members may be placed at the top of the current
+changelog entry of packages that are not yet ready for upload (e.g. why a
+package is still `UNRELEASED`, etc.).
== Binary-only packages
_______________________________________________
Pkg-go-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
