4 ms·
What's wrong with self-hosted gitlab?
by malermeister 4y ago
What's wrong with self-hosted gitlab?
- codetrotter 4y agoIf you self-host GitLab and I come across your repo, and I want to submit an issue I’ve found with your code. I then have to go through the trouble of making a new account for me on your instance, assuming that your instance even allows me to create an account. Don’t get me wrong, self-hosted GitLab is very useful too. But it is different from the goal of replacing GitHub with a decentralised alternative. The decentralised alternative to GitHub should work such that there is no one party that decides over accounts. You should be able to float freely around the network of instances. You should be able to follow other people and star their repositories. People, and code, should exist independently of the individual instances in the network. Any instance could ban you, and any instance could ban some of the people you follow or repositories you are following. But the network as a whole can still allow you to continue to follow others and others to follow you. Your identity is not tied to the instance. Your repositories are not tied to the instance. If one instance bans you, you can access the same network with the same identity from another instance. And others can still find you with that same identity over the network.
- zmnd 4y agoHow much time account creation realistically takes? How does that compare to the actual PR creation time? You will need to spend significantly more time on writing code, debugging, testing, creating PR that follows all the guidelines, potentially signing legal docs etc. If you can’t spend 15s on creating a new account I’m not sure I would be interested in accepting such PR.
- mhluongo 4y agoIf hosted Gitlab is so easy for contribution, why is the larger social graph on GitHub?