[pkg-gnupg-maint] moving repos from alioth to salsa.debian.org

[Daniel Kahn Gillmor]

hey GnuPG debian folks--

With the impending demise of Alioth, and the offering of the gitlab
instance at https://salsa.debian.org/, we need to move the git
repositories and the mailing list, and perhaps we need to consider how
to identify the team on new package releases.

Git Repositories
----------------

I'm proposing to create the git repositories within the salsa "Debian"
group.

This means i plan to move the following git repositories:

 * gpgme
 * gnupg2
 * gnupg1
 * libassuan
 * libgpg-error
 * gpa
 * pinentry

All existing debian developers will have read/write access to these
repos.  (and everyone in the world will have read access of course) If
you're working on debian packaging for any of these projects, and you
want read/write access, please let me or any other pkg-gnupg-maint DD
know, and we'll make sure you get it.

note that this means dropping the old/unmaintained gnupg-doc.git
repository, as well as the no-longer relevant dirmngr.git repo (dirmngr
was merged into gnupg before the current stable release was published).

Mailing Lists
-------------

I remain unsure what to do about this, because we don't seem to have a
clear option supported by Debian for an ongoing mailing list for
discussion :(

In previous discussion, Werner expressed a desire to not use upstream's
gnupg-devel at gnupg.org mailing list for debian-specific packaging
discussion.

Werner, perhaps you'd be willing to add a new debian at gnupg.org mailman
instance for this work?  I'd be willing to manage that mailing list, if
you could set it up.

That would give us a place to have this discussion, a permanent archive,
and it would help answer the final question:


Identifying team-maintained packages
------------------------------------

What e-mail address should we use to identify the packages as
team-maintained?  Currently, all the packages show:

    Maintainer: Debian GnuPG-Maintainers <pkg-gnupg-maint at lists.alioth.debian.org>

If we switch to a new mailing list, we can replace the e-mail address
with that one.  If the new mailing list isn't an option, i'm sort of at
a loss for what we should put here as a team.

Suggestions?

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