From: Cayetano Santos via Guix-Science <guix-science@gnu.org>
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: Wed, 04 Sep 2024 20:55:14 +0200 [thread overview]
Message-ID: <878qw7s0z1.fsf@inventati.org> (raw)
In-Reply-To: <87zfoqjhpg.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 02 Sep 2024 15:41:47 +0200")
>lun. 02 sept. 2024 at 15:41, Ludovic Courtès <ludovic.courtes@inria.fr> wrote:
> 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?
Regarding sr.ht, let me point out that sourcehut includes support for
builds. Among others, there is a guix system build image.
https://man.sr.ht/builds.sr.ht/compatibility.md#guix-system
Not that this is a valid option to replace GitWhatever / Codeberg (as it
departs significantly from its phylosophy), but a mirror is something to
be considered as a mid/long term alternative.
Same as emacs, by the way ;-)
https://git.sr.ht/~emacs/emacs
Best,
C.
prev parent reply other threads:[~2024-09-04 18:55 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
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 [this message]
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=878qw7s0z1.fsf@inventati.org \
--to=guix-science@gnu.org \
--cc=csantosb@inventati.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.