Re: moving to codeberg?

Simon Josefsson via Bug reports for the GNU Internet utilities <[email protected]> Wed, 02 Jul 2025 09:57:56 +0200
Newsgroups	gmane.comp.gnu.inetutils.bugs
Message-ID	<[email protected]>
"Alfred M. Szmidt" <[email protected]> writes:

> What would people say about moving things over to codeberg? Savannah
> is entierly unusable, and the FSF admins are not interesting in doing
> anything.

I consider codeberg for some projects.  I have many projects that are
dual savannah + gitlab (to get to functionality that doesn't really work
on savannah).  It is a really time consuming task to switch or maintain
both systems, so I sometimes wish I didn't do it, but the end results
are rewarding.  It is also not crystal clear exactly which features to
use from which site, and for different projects (libidn, libidn2,
oath-toolkit, gsasl etc) I ended up with different trade-offs.

I dislike the confrontational approach to MOVE things from savannah, but
I see no problem having additional "inetutils" projects on any other
site if there is anyone using that site who is interested in helping
inetutils, and if there are any useful result for the inetutils from
being on that site.  This can be gitlab (like we use for CI/CD which to
me is critical to have any confidence of the release tarballs),
codeberg, github or whatever.

Maybe we can experiment with a codeberg git repo for inetutils, and see
if any useful contributions come that way, and could be merged back to
savannah manually?  I started the project below and pushed savannah's
master branch both as 'main' (which I reckon is the codeberg-preferred
branch name) and 'master':

https://codeberg.org/inetutils/inetutils

I started a separate git repo to experiment with Codeberg Forgejo CI/CD
rules for InetUtils.  Let's see if we can keep CI/CD rules outside of
the core InetUtils project until we get some experience with it:

https://codeberg.org/inetutils/cicd

Compare the gitlab CI/CD inetutils project
https://gitlab.com/gsasl/inetutils/-/pipelines which uses this CI/CD
rule file:
https://gitlab.com/gnulib/pipeline/-/blob/main/gnu/inetutils.yml?ref_type=heads

Or the github inetutils CI/CD project, which I've sadly not had any time
at all to look into: https://github.com/gnu-inetutils/ci-check

If anyone wants to propose a 'Pull Request' on codeberg for this
inetutils repo, we could experiment with this workflow a bit.

I wouldn't consider this any official action, and I don't speak for the
InetUtils project, this is just a toy experiment to learn.

/Simon
signature.asc (application/pgp-signature, 1.2 KB)