I believe you're using technology to mean a concept (such as the git version control system). Which is valid, but I'm using the other meaning, an implementation or solution of the concept, which can certainly differ.
The two solutions have similar functionalities (git remote storage, action runners, issue tracking,etc), but for this use case (a hosting service) it is important that forgejo is copyleft while gitlab uses the MIT (an as-is) license.
If they used gitlab they could not stop gitlab from antagonistic development and this business could not provide as much trust to their users of continued improvements from the underlying git technology they are hosting.
-1
Codefloe Is a Professionally Hosted Public Git Forge | Spyke
6 replies
It’s trivially easy to stand up GitLab in a docker container. Sure it’s in the EU, but it’s the same problems in a new package.
Well the licensing is different
Of course it’s assumed that one could and should use any locally stood up system to best fit their needs.
Please do keep up the rigorous and dedicated work of nuanced and deeply thought out commentary.
You talked about a completely different technology than what the article is about.
I tied your comment to the topic graciously. Sorry.
Git is git is git my dude, it’s all just git under the hood. How is that a different technology?
I believe you're using technology to mean a concept (such as the git version control system). Which is valid, but I'm using the other meaning, an implementation or solution of the concept, which can certainly differ.
The two solutions have similar functionalities (git remote storage, action runners, issue tracking,etc), but for this use case (a hosting service) it is important that forgejo is copyleft while gitlab uses the MIT (an as-is) license.
If they used gitlab they could not stop gitlab from antagonistic development and this business could not provide as much trust to their users of continued improvements from the underlying git technology they are hosting.