[pkg-gnupg-maint] project membership, permissions, and change review.

[Daniel Kahn Gillmor]

hey pkg-gnupg folks--

I've just looked at the alioth project membership for pkg-gnupg-maint.

we've got several different roles, including both Junior Developer and
Senior developer, which were no different from one another.

I think Junior Developer was intended to be read-only access to the git
repositories, while commit access is limited to admins and senior devs.

This should reduce the likelihood of pushing a bad commit to the shared
repositories.  If you're currently marked as "junior dev" and you've
been submitting patches and want direct commit access, please holler and
we'll switch the status.

I encourage everyone (regardless of status) to post potentially-risky
changesets for public review before pushing them to the main repository
anyway.

You can post the entire patches to the mailing list here, or to a
feature branch (either in the canonical pkg-gnupg-maint git repo, into
an alioth personal repo, or elsewhere) and then send mail to the list
here asking for discussion.

The goal here is not to keep anyone from contributing.  We want anyone
to be able to clone and to publish changesets for review.

We do want the pkg-gnupg packaging repositories to remain a stable
place, though, and we want them to match the packages that are uploaded
within debian so people can retrieve them and work with them reliably.
Limiting write access to the canonical repositories helps make sure they
match the actual uploads to the archive.

         --dkg
         
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 948 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20150512/ab85526c/attachment.sig>