will delete repositories on free accounts that haven't recorded any activities for a year.

I still sporadically receive emails and support requests for SnortAI_Preproc, a machine learning pre-processor for Snort that I built more than 12 years ago for my M.Sc thesis. Even though the repo itself hasn't seen any activities for >10 years, it keeps getting stars and followers. Under Gitlab's new policy, I would have had to push a stupid commit every year for the past 10 years just to keep it alive.

And my project isn't even an outlier. These patterns are especially common in academic software, where a researcher or a graduate student may bump into your projects months or years after its latest commit.

And this is not to mention preservation: some software may have been actively developed and used in the past, lost momentum at some point for any variety of reasons, and deleting would prevent any later developer from resurrecting it, or from preserving it for historical purposes.

Being a large host of open-source software and planning to delete software that hasn't been updated in a while is like being in charge of a museum and destroying the items that visitors haven't shown interest in the past few months.

If Gitlab has decided to prioritize profit margins over their responsibility to reliably host our free contributions to the world, then they no longer deserve to host anything.

I'm very happy I successfully completed my migration to a self-hosted instance just a few weeks ago, and I don't have to cope anymore with shitty companies that still think that other people's open-source software must be something to exploit for their own profit.


The migration of git.platypush.tech from to is almost complete.

CI/CD pipelines aren't operative yet, but everything else should be working. And we've also got a "sign in with " button that uses my instance - how cool is that?

Gitlab used to take about 5 GB of RAM and a lot of CPU to run just the basics. Gitea takes barely 100 MB of RAM and it's so light on the CPU that it could even run on a Raspberry Pi. Thanks to this migration alone I've managed to downgrade my 16 GB VPS to 8 GB and save about $60/month, while having basically the same features (except for integrated CI/CD) and a much faster response time. I should have probably done this earlier.

There's only one heads up: in the process of migrating the users I couldn't (obviously) decrypt the hashed passwords, so users are required to use the "forgotten password" link to reset it, or use one of the available SSO methods. I'll probably send a communication soon to all registered users.

I'm in the process of moving my repos from to (both self-hosted).

Gitlab sucks up about 3 GB of RAM on a server with low traffic, and after they decided to break git twice (first by pushing people to use their own git binary instead of the vanilla one, then with the "commit-graph requires overflow generation data but has none" doom bug that can randomly break your repos forever), I've decided that they are not a reliable partner for my code hosting needs anymore.

I'm in the process of looking for a Gitea alternative for CI/CD. Sure, I can get back to webhooks and scripts as a workaround, but I'd like something more natively integrated. Drone CI is an alternative apparently, but it doesn't seem that well natively integrated with Gitea either. Any thoughts?


A platform about automation, open-source, software development, data science, science and tech.