After 5 years of foot-dragging they finally close the ticket to community protest:
This feature request is being closed as our current focus isn’t in this area.
We appreciate your input and contribution to improving our product. While this feature may have merit, we need to prioritize our efforts elsewhere at this time.
If you’d like to provide additional context about why this feature is important, please feel free to leave a comment on this issue. This will help us better evaluate the feature if we revisit this area in the future.
Thank you for your understanding and continued support in helping us build a better product.
NuXCOM_90Percent@lemmy.zip 19 hours ago
For those who were out of the loop:
What exactly is the idea of federated gitlab? Git is already inherently distributed and automagically mirroring to other remotes is generally like three lines in any CI syntax (and there is probably a precommit hook for it too).
Also: I can see a LOT of security issues with not having a centralized source of truth on what the commit hashes should be and so forth. is fedgit dot zip the source of truth for this app or fedgit dot ml or fedgit dot ca? Theoretically that is where signing comes into play but that gets back to: What advantage does a “fediverse” frontend have?
rglullis@communick.news 19 hours ago
Github’s dominance comes from the network effects. Everyone’s on github, so if you have your project on a different repo, you won’t get as many visibility. If your project is on gitlab only and someone wants to report a bug, they need to:
A Federated forge solves all of that.
russjr08@bitforged.space 19 hours ago
I always assumed it was more or less targeting the federation of issues/MRs.
The git side of things is already distributed as you said, but if you decide to host your random project on your own GitLab instance you’ll miss out on people submitting issues/MRs because they won’t want to sign up for an account on your random instance (or sign in with another IdP).
This is where a lot of the reliance of GitHub comes from, in my opinion.
ademir@lemmy.eco.br 18 hours ago
100% agree with you here.
Fizz@lemmy.nz 8 hours ago
Couldnt this be done with email reminders and single sign on?
onlinepersona@programming.dev 19 hours ago
Git is, but what about everything else? When you clone a project on gitlab or github, does it come with all the issues, discussions, MRs, and so on?
That’s what signed commits are for. Also, pull/merge requests and issues are sent to the origin instance, just like in the fediverse. Like now, you made a comment on a post on Fediverse@lemmy.world through your instance lemmy.zip. The same would happen with your comments, pull/merge requests, issue reports, and so on. There’s no need for a “central authority”.
NuXCOM_90Percent@lemmy.zip 19 hours ago
Partially addressed in the other branch but:
Issues from people who can’t even be bothered to make a burner account are almost never useful. And issue tracking that is not fed directly to passionate people who care about maintaining a project is worse than worthless.
Then it is a good thing I addressed the existence of those. And… those also more or less need a semi-centralized source of truth that is independent of gitlab/hub/whatever.
So everything would still happen on the single source of truth for an a project? But you can have an account on whatever service you want?
Homie? You just described oauth.