From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: guix-science@gnu.org, Romain GARBAGE <romain.garbage@inria.fr>,
Ricardo Wurmus <rekado@elephly.net>,
Lars-Dominik Braun <lars@6xq.net>
Subject: Re: Moving guix-science from GitHub?
Date: Mon, 2 Sep 2024 17:07:53 +0200 [thread overview]
Message-ID: <CAJ3okZ1mySMqRnvLy+83X82bJwVkJZLLZBavjawuWj+SwyT8tA@mail.gmail.com> (raw)
In-Reply-To: <87zfoqjhpg.fsf@gnu.org>
Hi,
On Mon, 2 Sept 2024 at 15:42, Ludovic Courtès <ludovic.courtes@inria.fr> wrote:
> Thanks to Romain, Cuirass recently gained support for GitLab
> integration
Oh cool! Thank you Romain.
> so it would be tempting to move to a public GitLab instance
> such as gitlab.com
[...]
> But if we are to migrate, we might just as well migrate to a
> not-for-profit instance such as codeberg.org?
Is Cuirass also integrated with codeberg.org? Maybe I have missed
something, from my understanding, codeberg.org depends forgejo which is
not related to Gitlab.
Well, if the motivation is to move from GitHub because of missing CI,
then the new forge must have integrated CI. ;-)
Otherwise, I do not have any opinion where the guix-science channel shoudl live.
Cheers,
simon
next prev parent reply other threads:[~2024-09-02 15:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 13:41 Moving guix-science from GitHub? Ludovic Courtès
2024-09-02 15:07 ` Simon Tournier [this message]
2024-09-03 6:12 ` Konrad Hinsen
2024-09-03 8:01 ` Ludovic Courtès
2024-09-03 8:04 ` Ludovic Courtès
2024-09-03 7:52 ` Ludovic Courtès
2024-09-02 15:28 ` Ricardo Wurmus
2024-09-03 7:50 ` Ludovic Courtès
2024-09-03 13:19 ` Simon Tournier
2024-09-05 7:41 ` Ludovic Courtès
2024-09-04 16:26 ` Lars-Dominik Braun
2024-09-04 16:33 ` Philippe SWARTVAGHER
2024-09-10 13:39 ` Ludovic Courtès
2024-09-04 18:55 ` Cayetano Santos via Guix-Science
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ1mySMqRnvLy+83X82bJwVkJZLLZBavjawuWj+SwyT8tA@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-science@gnu.org \
--cc=lars@6xq.net \
--cc=ludovic.courtes@inria.fr \
--cc=rekado@elephly.net \
--cc=romain.garbage@inria.fr \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.