From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: guix-science@gnu.org, Romain GARBAGE <romain.garbage@inria.fr>,
Lars-Dominik Braun <lars@6xq.net>
Subject: Re: Moving guix-science from GitHub?
Date: Mon, 02 Sep 2024 17:28:26 +0200 [thread overview]
Message-ID: <87tteyhy79.fsf@elephly.net> (raw)
In-Reply-To: <87zfoqjhpg.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 02 Sep 2024 15:41:47 +0200")
Hi,
Ludovic Courtès <ludovic.courtes@inria.fr> writes:
> Currently Guix-Science{,-nonfree} are on GitHub, which is not great for
> obvious reasons, and also because there’s no CI integration.
>
> Thanks to Romain, Cuirass recently gained support for GitLab
> integration,
Superb!
> so it would be tempting to move to a public GitLab instance
> such as gitlab.com. One could also implement GitHub support without too
> much hassle (maybe?), but is it worth it?
>
> But if we are to migrate, we might just as well migrate to a
> not-for-profit instance such as codeberg.org? (I believe a prerequisite
> for the intended audience is to have something that looks similar to
> Git{Hub,Lab}, which is why I’m not suggesting the use of sr.ht.)
>
> Thoughts?
I have two worries about migrating to another location:
- publications referencing a channel with URL
https://github.com/guix-science/guix-science might break if we don't
manage to set up a permanent redirect.
- I don't know if migration would be seamless for all users of the
channel. Obviously, we'd also have to update any channel that
references guix-science (such as guix-science-nonfree).
We may also want to move guix-science-nonfree, guix-cran, and guix-bioc
while we're at it.
--
Ricardo
next prev parent reply other threads:[~2024-09-02 15:29 UTC|newest]
Thread overview: 33+ 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
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 [this message]
2024-09-03 7:50 ` Ludovic Courtès
2024-09-03 13:19 ` Simon Tournier
2024-09-05 7:41 ` Ludovic Courtès
2024-10-10 15:18 ` Moving guix-science from GitHub to Codeberg Ludovic Courtès
2024-10-10 21:49 ` Ricardo Wurmus
2024-10-11 6:53 ` Konrad Hinsen
2024-10-11 5:44 ` Lars-Dominik Braun
2024-10-11 7:20 ` Simon Tournier
2024-10-11 9:51 ` Ludovic Courtès
2024-10-11 10:07 ` Lars-Dominik Braun
2024-10-14 7:28 ` Ludovic Courtès
2024-10-15 8:46 ` Roel Janssen
2024-10-17 13:27 ` Guix-Science channels moved " Ludovic Courtès
2024-10-18 12:45 ` Ludovic Courtès
2024-10-18 13:01 ` Konrad Hinsen
2024-10-22 15:54 ` Guix-Past " Ludovic Courtès
2024-10-25 12:34 ` Guix-Jupyter " Ludovic Courtès
2024-11-04 14:26 ` Guix-Past " Ricardo Wurmus
2024-11-07 15:25 ` Simon Tournier
2024-11-07 23:15 ` Ludovic Courtès
2024-10-18 13:48 ` Guix-Science channels " Cayetano Santos
2024-10-19 19:32 ` Ludovic Courtès
2024-09-04 16:26 ` Moving guix-science from GitHub? 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tteyhy79.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-science@gnu.org \
--cc=lars@6xq.net \
--cc=ludovic.courtes@inria.fr \
--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.
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).