On 13/02/16 10:34 PM, Martín Ferrari wrote: > On 09/02/16 01:44, Alexandre Viau wrote: >> Hello, >> >> On 08/02/16 12:49 AM, Martín Ferrari wrote: >>> Although I presume this change might not be acceptable for some people, >>> I think the notes about changelog handling would be a good addition. >> >> +1, I agree with this change. >> >> Maybe we should apply the first patch right now and wait one more week >> for this one. > > Nobody else replied, but I am in favor of this idea.
Two weeks have passed, it looks like everyone is also in favor of this patch. Michael, can we go ahead and apply Martin's patch? I have attached it to this mail. Thanks, -- Alexandre Viau [email protected]
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
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-go-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
