On Tue, Jun 23, 2026 at 4:54 AM Steve George <[email protected]> wrote: > > Hi, > > Ludo authored a blog post covering our transition to Codeberg: > > https://guix.gnu.org/en/blog/2026/one-year-with-codeberg/ > > It's a big change, I wondered how we felt about it as a group? > > - Has it worked, or not, for you as a developer?
It is working greatly. Now that I learned about `agitjo`, I have that feeling of "nothing is on my way". (I say this as someone still using a web browser to run most interactions.) Not related but I feel a bit sad about the new disk quotas on Codeberg, since it does not allow to fork Guix or Gentoo. > - What's been better? I started contributing as soon as the repo was set to Codeberg. I had no experience about the mail-based workflow, but I feel it was too complicated to set up. > - What could be improved? As a matter of independence, a self-hosted instance. > > For me personally I think the Git repo and PRs have been a win: I spend less > time trying to figure out how to pull down a contribution. > > The automation around CI/builds has been a loss. Thanks to everyone who > worked on the PR builder, that's great and it's really clear when you see > that a PR has been built. Branch co-ordination and the Info service is what I > miss. > > The other one is that Issues are a lot worse than Debbugs. For users > generally Issues are great and it's a lot more accessible. But, it doesnn't > compare to a proper bug tracker, with a real database and interaction (here I > miss email) if you're handling a lot of bugs. Of course, Debbugs looked > awful, was difficult to use and was pretty inaccessible/annoying - but it > also had a lot of power which "as a developer" we have lost. > > Steve / Futurile >
