From: Bernhard Voelker <mail@bernhard-voelker.de>
To: Simon Josefsson <simon@josefsson.org>, Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: replacement for 'join'?
Date: Fri, 14 May 2021 21:04:25 +0200 [thread overview]
Message-ID: <a2f268e5-5364-9888-17ae-a9ce204b4750@bernhard-voelker.de> (raw)
In-Reply-To: <87k0o1w6t9.fsf@latte.josefsson.org>
On 5/14/21 7:42 PM, Simon Josefsson via Gnulib discussion list wrote:
> Certainly! Was anyone working on setting up CI/CD for gnulib on GitLab?
> I recall there was a private project for it, but I don't have access.
> Any reason for this? I have become rather aquinted with GitLab CI/CD
> lately so it would be easy for me to setup something from scratch. Of
> course, given all the freedom concerns people may have with using a SaaS
> like GitLab, I think it is important that we don't let what features
> exists there influence any decisions made in gnulib. Let's use it as a
> way to improve our software, to promote more users of GNU software, just
> the way we used proprietary platforms like Solaris or IRIX in the old
> days.
IMO that's something for the gnu-prod-discuss mailing list.
We shouldn't blindly use CI/CD platforms which are potentially problematic
or even contradicting or violating the GNU freedoms, just merely because
many people use it.
(I'm no lawyer, so I can't 100% tell for Gitlab, though.)
Isn't there already GNU way for CI/CD?
I know there is hydra.nixos.org, but that looks a bit fallen asleep.
Anything else?
Have a nice day,
Berny
next prev parent reply other threads:[~2021-05-14 19:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 23:06 replacement for 'join'? Bruno Haible
2021-04-05 22:48 ` Bernhard Voelker
2021-04-06 1:01 ` Bruno Haible
2021-04-06 2:24 ` Paul Eggert
2021-04-06 9:40 ` Bernhard Voelker
2021-04-06 18:47 ` Paul Eggert
2021-04-06 20:45 ` Bruno Haible
2021-04-07 12:04 ` Bernhard Voelker
2021-04-07 12:42 ` Bruno Haible
2021-05-12 10:01 ` Simon Josefsson via Gnulib discussion list
2021-05-12 10:39 ` Bruno Haible
2021-05-12 17:58 ` Simon Josefsson via Gnulib discussion list
2021-05-14 13:17 ` Bernhard Voelker
2021-05-14 13:42 ` Bruno Haible
2021-05-14 13:48 ` Simon Josefsson via Gnulib discussion list
2021-05-14 16:19 ` Bruno Haible
2021-05-14 17:15 ` Bernhard Voelker
2021-05-14 17:42 ` Simon Josefsson via Gnulib discussion list
2021-05-14 19:04 ` Bernhard Voelker [this message]
2021-05-14 20:22 ` gnulib-ci project Bruno Haible
2021-05-14 20:36 ` Simon Josefsson via Gnulib discussion list
2021-05-14 21:38 ` Bruno Haible
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a2f268e5-5364-9888-17ae-a9ce204b4750@bernhard-voelker.de \
--to=mail@bernhard-voelker.de \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=simon@josefsson.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).