all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@cnrs.fr>
To: "Simon Tournier" <zimon.toutoune@gmail.com>,
	"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: Tue, 03 Sep 2024 08:12:43 +0200	[thread overview]
Message-ID: <m1seuh465g.fsf@fastmail.net> (raw)
In-Reply-To: <CAJ3okZ1mySMqRnvLy+83X82bJwVkJZLLZBavjawuWj+SwyT8tA@mail.gmail.com>

Hi everyone,

Simon Tournier <zimon.toutoune@gmail.com> writes:

>> 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.

Indeed. It does have CI:

   https://docs.codeberg.org/ci/

but it's probably not Gitlab-compatible.

But then, given that moving has a high cost (for the reasons pointed out
by Ricardo), we should take a long-term perspective. I expect forĝejo to
be a more interesting platform in the long run, both technically
(Fediverse) and socially (not for profit).

Questions:

 1. How much effort would it be to implement forĝejo support in Cuirass?

 2. In view of federated forges, which facilitate some aspects of moving
    between forges, maintaining mirrors, etc., could we come up with
    a way to make Guix channels easier to relocate, and/or have multiple
    URLs?

Cheers,
  Konrad.
-- 
---------------------------------------------------------------------
Konrad Hinsen
Centre de Biophysique Moléculaire, CNRS Orléans
Synchrotron Soleil - Division Expériences
Saint Aubin - BP 48
91192 Gif sur Yvette Cedex, France
Tel. +33-1 69 35 97 15
E-Mail: konrad DOT hinsen AT cnrs DOT fr
http://dirac.cnrs-orleans.fr/~hinsen/
ORCID: https://orcid.org/0000-0003-0330-9428
Mastodon: @khinsen@scholar.social
---------------------------------------------------------------------


  reply	other threads:[~2024-09-03  6:13 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 [this message]
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-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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1seuh465g.fsf@fastmail.net \
    --to=konrad.hinsen@cnrs.fr \
    --cc=guix-science@gnu.org \
    --cc=lars@6xq.net \
    --cc=ludovic.courtes@inria.fr \
    --cc=rekado@elephly.net \
    --cc=romain.garbage@inria.fr \
    --cc=zimon.toutoune@gmail.com \
    /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.