[pkg-go] Fwd: Updating the pkg-go Team Maintenance policy

[Alexandre Viau]

Hello,

On 19/01/16 03:50 PM, Michael Stapelberg wrote:
> aviau, in which way would you want people to express their preferences?

See the patch:

> - putting the team in the Maintainers field 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.
>
> - 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.

> Could we re-use the LowNMU mechanism that Debian has,

By putting the team in uploaders or in maintainers, you indicate your
preference. There is no need to maintain a LowThresholdNmu page or
equivalent.

> see https://wiki.debian.org/LowThresholdNmu? Or is LowNMU different than
> what your proposal wants to accomplish? If yes, can you outline the
> differences that are important to you please?

I don't consider a team upload the same as an NMU, as we are a team and
we work together. A team policy would be addressed to members of the
teams and not all DDs. However, it is true that the spirit of it is the
same.

Team uploads can be different as they would require the use of our git
repositories.

Also, it looks like the NMU policy does not apply when you are in the
uploaders, which is the case for us. For example, you subscribe to
LowThresholdNmu and it does not appear in the tracker page for
golang-golang-x-sys, which you maintain:
 - https://tracker.debian.org/pkg/golang-golang-x-sys

-- 
Alexandre Viau
aviau at debian.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-go-maintainers/attachments/20160119/6f11ef4a/attachment.sig>