responsibility for libgcrypt and libksba

[Daniel Kahn Gillmor]

Hi Andreas--

Thanks for the response!

On Thu 2015-04-16 13:25:44 -0400, Andreas Metzler wrote:
> iirc libksba has never been used by gnutls as long as I have been
> maintaining it, it was just part of the crypto package bundle Matthias
> Urlichs used to maintain. It is very low-maintainance, though.
>
> not mind taling care of it.
>
> I have not got ay hard numbers, but I think that curently almost all
> commits to the GnuTLS git repos have my name on it. BTS work is
> different, apart from me especialy Simon Josefsson and you seem to be
> quite active. I am sorry if I have forgot anyone, this is just from
> the top of my head.

This is useful history to be aware of, thanks.

> I have not got shiny new ideas on how to improve collaboration, just
> the obvious stuff:
> - If you want to, you  would be very welcome to GIT commit rights and to
>   adding yourself as uploader.
> - I do not currently mind maintaining libksba and/or libgcrypt but you
>   are also welcome to take them over if it improves things.

OK, these both seem like reasonable options.

I think that moving libksba to pkg-gnupg at least would make sense given
its rdeps.  I'm slightly more leery about moving libgcrypt at the moment
because it touches so many other parts of the OS, though i'm happy to
try to help with its packaging in its current state at least.

> - The packages could also be moved over to the gnupg repo and the
>   pkg-gnupg-maint@ group with me continueing to have upload/commit
>   rights. - If I did the bulk of the work I would strongly prefer to
>   continue using the current debian/-only GIT layout, though.

hm, i have a reasonably strong preference for keeping everything in git,
including upstream code and pristine-tar deltas, for two reasons:

 * it's easier to collaborate directly with upstream, because we can
   keep debian/patches in a patch queue that could be applied to upsteam
   directly.

 * it's simpler for anyone who wants to work on the package to get
   everything they need (including for multiple branches) in one spot.

This is facilitated by git-buildpackage (and i've recently started using
gbp-pq for the patch queues, which is quite nice)

But a lot of this might just be comfort/familiarity with certain
workflow and tools, and i don't want to get in the way of workflow/tools
you find useful either -- can you explain what you prefer about the
debian/-only git layout and give pointers to what tools you use to
manage it?

Regards,

    --dkg