Folks are going to have to relearn the importance of good infrastructure management and backups after #GitHub
Especially the backups
Also, there are other open source alternatives besides GitLab
Gogs comes to mind. There’s also Gitea, which is a fork of Gogs
The background behind the fork is worth reading even if you’re not technical:
https://blog.gitea.io/2016/12/welcome-to-gitea/
A lot of it is applicable to other online communities and human interaction in general. Some of that is relatable to Mastodon
And if you’ve been tired of Git for a while and want to try a different source control, there’s the highly reliable and well-maintained Fossil:
https://fossil-scm.org/index.html/doc/trunk/www/index.wiki
It was created and is currently used by the SQLite team and there’s a comparison of the differences between Fossil and Git:
https://fossil-scm.org/index.html/doc/trunk/www/fossil-v-git.wiki
The point is, if you really do feel motivated to move to something different and explore other options, please do explore them
The dev world is bigger than Git
Don’t just stick to what you know and are comfortable with as you won’t get to grow as a creator (be it in code, ink, or musical notes) unless you expand your horizons
@cypnk Is there a 'FossilHub'?
@faissaloo These came up after a search:
Free:
http://fossilrepos.sourceforge.net
http://chiselapp.com
Paid:
https://www.a2hosting.com/fossil-hosting
There’s also a GUI tool for Fossil
https://fuel-scm.org/fossil/index
To clarify:
Cheering for a fork or moving to #GitLab is fine, but you’re moving to yet another silo unless you host yourself. But that’s not something everyone is capable of doing well without significant practice, especially if the entity you’re a part of needs reliability
An army marches on its stomach
An company survives on its uptime