[gnutls-help] Guile-Gnutls bindings to separate git repo?

[Simon Josefsson]

Ludovic Courtès <ludo at gnu.org> writes:

> Hi Simon,
>
> Simon Josefsson <simon at josefsson.org> skribis:
>
>> The GnuTLS developers talked about separating the Guile bindings for
>> GnuTLS into a separate git repository,
>
> Heh, good to know.

Hi.  Sorry, I should have qualified that as _some_ GnuTLS developers,
thus not speaking for everyone.

>> with the advantages being 1) simplify core GnuTLS maintenance and
>> reduce complexity, 2) allow a separate release schedule for
>> guile-gnutls.  What do you think?  Is there any disadvantage with
>> this?  I'm happy to (co-?)create a guile-gnutls repository and do a
>> first release of it to get the ball rolling.
>
> I think the repository layout has to mirror the social construct.
> Having the bindings within GnuTLS was IMO a strength at a time when
> there was cohesion.  Nowadays, it seems like it’s become a hindrance to
> everyone involved so separating the bindings sounds like a reasonable
> choice.

Right, I sadly agree with this, wishing some things were different.

> I’ll happily take your offer to create the initial repo if it still
> holds.  :-)

Certainly.  Is gitlab.com/gnutls a suitable place for this (do you have
a gitlab.com username?), or should we try to move it to savannah or some
other place?  Do you know if someone other than you are likely to work
on guile-gnutls soon?  The guile/ contributors list is short:

Author: Alon Bar-Lev <alon.barlev at gmail.com>
Author: Daiki Ueno <ueno at gnu.org>
Author: Leonardo Bras <leobras.c at gmail.com>
Author: Ludovic Courtès <ludo at gnu.org>
Author: Marcin Cieślak <saper at saper.info>
Author: Nikos Mavrogiannopoulos <nmav at gnutls.org>
Author: Simon Josefsson <jas at josefsson.org>
Author: Simon South <simon at simonsouth.net>
Author: Tim Rühsen <tim.ruehsen at gmx.de>

> The Guile-Gcrypt bindings have been maintained separately since their
> inception and it’s worked rather well.

Right, and my experience with supporting language bindings in libidn is
that they are better done externally than internally in the upstream
library project.  The language-specific expertise required seldom exists
in the upstream project, and whatever project-specific expertise is
needed tend to be less important and can be solved through normal
documentation requests within the core project.

/Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 255 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnutls-help/attachments/20221005/a7a28bbc/attachment-0001.sig>