[gnutls-help] [PATCH 0/2] Add support for Guile 3.0
ludo at gnu.org
Thu Jun 6 10:19:42 CEST 2019
Nikos Mavrogiannopoulos <nmav at gnutls.org> skribis:
> On Wed, Jun 5, 2019 at 12:07 PM Ludovic Courtès <ludo at gnu.org> wrote:
>> I meant ignore the issues with these ToS, such as the “Indemnification”
>> section at <https://about.gitlab.com/terms/>; fundamentally, I want to
>> contribute to GnuTLS, I don’t want to have to deal with GitLab B.V., but
>> I think we already discussed it before. I also find it sad that a
>> distributed VCS led to more centralization than we had before…
> That's true, though gitlab gives us the option to move data (issue
> tracker etc) elsewhere. The good thing is that there are options also,
> not only gitlab.com, but also gitlab.gnome.org
> (https://wiki.gnome.org/GitLab/IncubatorReqs ), and few other
I don’t mind having an account on gitlab.gnome.org or savannah.gnu.org:
these are run by non-profit organizations with clear commitments.
To contribute to GnuTLS, in practice I have to sign up to gitlab.com and
agree their terms of service; I have to trust GitLab B.V. to be “kind”
to me and to GnuTLS in the future. It doesn’t really help that
theoretically data from the issue tracker can be moved elsewhere.
> The main benefit I see of gitlab.com is the CI, and the
> workflow improvements saving time in all involved parties.
Sure, I understand, even though it’s a workflow that doesn’t work well
>> The convention in GnuTLS is to add ’Signed-off-by’ by the author?
> Yes, there are few contribution guidelines that were changed over the
> years, one was this one. The full list is at:
> The request for changes in the guidelines are usually tagged with the
> process tag in gitlab:
Oh, I see, thanks for the pointers.
Back to the original patches, should I push a new branch to add the
More information about the Gnutls-help