"GitLab plans to automatically delete projects if they've been inactive for a year and are owned by users of its free tier." says The Register.
"GitLab is aware of the potential for angry opposition to the plan, and will therefore give users weeks or months of warning before deleting their work. A single comment, commit, or new issue posted to a project during a 12-month period will be sufficient to keep the project alive."
(This is not the place to vent your feelings pro or con about this policy. I'm sure gitlab has official forums or whatever for that)
"GitLab U-turns on deleting dormant projects after backlash - Now makes vague pledge to shove inactive repos into slow object storage"
"our sources told us this afternoon that it was online pressure, led by The Register's reporting, that forced a dramatic rethink at the GitHub rival. "
(this remains an inappropriate thread to discuss your feelings or thoughts about this policy or its change.)
@malerbabomba @jens @sungo self-host a #Gitea instance - the same framework that also powers #Codeberg. I have recently migrated git.platypuhs.tech from self-hosted #Gitlab to self-hosted Gitea: https://social.platypush.tech/@blacklight/108596969230176183.
Codeberg is amazing, but I've learned by experience that hosting my stuff on somebody else's computer is always a bad idea, no matter how good those people claim to be. Gitea is much lighter than Gitlab and it can even run on a Raspberry Pi, so no excuses.
The only downside is about CI/CD integrations (Gitlab is quite hard to beat on that), but I've managed to replace them with webhooks.
@sungo looks like they made a U-turn and are now gonna move inactive projects to slower storage, but still accessible
This is a single-user instance, namely for @sungo