Conversation
Notices
-
@arunisaac Not sure if Gogs supports OpenID, but that would be a solution: one login, many instances, no single point of failure like with Github.
- lnxw48 (Linux Walt) likes this.
-
!selfhosting !decentralife With #github, you just have a single account and you can contribute to a lot of projects.
With something like #gogs, you need a separate account for every gogs instance whose projects you want to work on. That could be very many accounts, and a lot of fragmented identities. Is there any #git hosting system, or bug tracking system, that can #federate between instances?
A simple mailing list seems to be the only alternative. But, a mailing list is not really a #bugtracker. Besides, #mail has its own problems.
-
@vinzv @petter @mmn Also, it's not just single sign on that I'm worried about.
#Gogs instances need to allow public registration so that contributors can work on the project and submit pull requests. So, if somebody signs up on my instance and forks a few repos, am I obliged to keep their forks and their accounts forever? Is that scalable in terms of storage space?
!selfhosting !decentralife
-
@arunisaac Like @bob says, it should be federated. So you can authenticate ("join") with your own domain but your repo is always kept at your server and merge requests etc. go over some other channel (like email for the Linux kernel, http for weblovers).
-
@nakal @arunisaac Sure, on code things. Ever tried to migrate issues and pull requests away from Github.
-
@nakal You're right. But the way you describe is a) not the way Github is intended to use by themselves and b) not the solution @arunisaac was looking for, I assume.
-
@arunisaac@social.systemreboot.net Maybe GitTorrent? http://blog.printf.net/articles/2015/05/29/announcing-gittorrent-a-decentralized-github/