GitLab abandons federation plans!

Submitted ⁨⁨3⁩ ⁨weeks⁩ ago⁩ by ⁨thann@lemmy.dbzer0.com⁩ to ⁨fediverse@lemmy.world⁩

https://gitlab.com/groups/gitlab-org/-/epics/11247#note_2597450590

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.

source

Comments

Sort:hotnew top

NuXCOM_90Percent@lemmy.zip ⁨3⁩ ⁨weeks⁩ 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?

source
- rglullis@communick.news ⁨3⁩ ⁨weeks⁩ ago
  What advantage does a “fediverse” frontend have?
  
  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:
  
  Find your instance.
  
  Create an account.
  
  Deal with an unfamiliar interface
  
  Create the ticket
  
  Hope it gets seen.
  
  Potentially forget about it, unless they set up notifications.
  
  A Federated forge solves all of that.
  
  You follow remote projects without having to create an account in the remote instance.
  
  You open an issue on the remote forge without having to open in an account in the remote instance, and you do it from your local server.
  
  If you have a PR ready, the remote instance gets notified.
  
  It makes a lot easier to separate CI/CD from source management.
  
  It makes a lot easier to separate source management from issue tracking.
  
  etc
  
  etc
  
  etc
  
  source
- russjr08@bitforged.space ⁨3⁩ ⁨weeks⁩ 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.
  
  source
  - ademir@lemmy.eco.br ⁨3⁩ ⁨weeks⁩ ago
    
    This is where a lot of the reliance of GitHub comes from, in my opinion.
    
    100% agree with you here.
    
    source
  - lambalicious@lemmy.sdf.org ⁨2⁩ ⁨weeks⁩ ago
    People could just submit issues by e-mail, tbh.
    
    I have most of my projects on either notabug or chiselapp (Fosil, not Git) and to this day I get e-mails asking for stuff or notifying about issues, so it’s not like the “social” / “Hub” aspect of “GitHub” is needed.
    
    source
  - Fizz@lemmy.nz ⁨2⁩ ⁨weeks⁩ ago
    Couldnt this be done with email reminders and single sign on?
    
    source
- onlinepersona@programming.dev ⁨3⁩ ⁨weeks⁩ ago
  
  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).
  
  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?
  
  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.
  
  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”.
  
  source
  - NuXCOM_90Percent@lemmy.zip ⁨3⁩ ⁨weeks⁩ 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.
    
    That’s what signed commits are for
    
    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.
    
    Also, pull/merge requests and issues are sent to the origin instance, just like in the fediverse
    
    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.
    
    source
    -> View More Comments
QuazarOmega@lemy.lol ⁨3⁩ ⁨weeks⁩ ago
That sucks majorly, I knew GitLab isn’t our friend, but to plain dismiss a development effort that didn’t even come from their own employees is just spitting in our face.
Forgejo federation can’t come any sooner ✊

source
jaredwhite@piefed.social ⁨3⁩ ⁨weeks⁩ ago
This was literally the only reason I had any potential interest in GitLab. What a joke. 😠

source
fxomt@lemmy.dbzer0.com ⁨3⁩ ⁨weeks⁩ ago
Damn, that’s incredibly disappointing…

I use forgejo and it’s expected to have federation eventually, but it would’ve been amazing for gitlab to have AP support. Hopefully in the future it might be picked up again.

source
- irelephant@lemmy.dbzer0.com ⁨3⁩ ⁨weeks⁩ ago
  It annoys me that we have on one atproto, but there’s no fediverse one.
  
  source
  - fxomt@lemmy.dbzer0.com ⁨3⁩ ⁨weeks⁩ ago
    It’s cool af (i don’t know much abt atproto, but my friend who knows much more about the technical stuff of fedi/matrix/etc likes it more than AP :shrug:) but i wouldn’t trust my sensitive repos with it for now. But i guess its the best we have right now :c
    
    source
- corsicanguppy@lemmy.ca ⁨3⁩ ⁨weeks⁩ ago
  Oh noo; forgejo is still not connected? I had high hopes. What’s the timeline?
  
  (Honestly, but for the wonky CI spec language I may have switched already)
  
  source
  - fxomt@lemmy.dbzer0.com ⁨3⁩ ⁨weeks⁩ ago
    I’m not sure, it hasn’t been announced. They’re waiting for forgefed to finish being developed until they implement federation
    
    source
Ulrich@feddit.org ⁨3⁩ ⁨weeks⁩ ago
It’s hard for me to imagine how this benefits a for-profit company, and probably requires significant resource dedication so it’s not surprising.

source
- corsicanguppy@lemmy.ca ⁨3⁩ ⁨weeks⁩ ago
  Company A permits federation of project 2 with contractor B who agrees. Oh look! No need to add 21 people to your AD. Contract done? De-fed.
  
  Google feds with GH for AOSP dev, because it’s 2023. Users don’t need to even know where the repo is hosted or whether the real meat is another hop inside.
  
  Company “BCFerries”, an imaginary organization, happens to run the largest fleet of mobile DCs in the country, with each mobile DC being 6 HA racks, three on a side, dehumidifiers o-plenty. Engineers stationed aboard need to lob tickets and hot fixes on the go, and sub them for review when the mobile DCs get a good link, 30 min out of every 2 hours. Roaming 2/2/2tb node swaps spit with the stationary nodes when it smells the VPN, and then gets ready to go again.
  
  Repeat that above, but say ‘Maersk’. I’m betting evergreen/evergiven is on VSS.
  
  Enough examples?
  
  Running a federated GL is conceivably a set-it-and-forget-it like a lot of federated stuff already is, and you debug the glitches and patch like normal.
  
  Given the 5GLs I still run were all installed by VMware/terraform/chef/RPM, patched automatically with package promotion and watched for anomalies, it’s already negligible effort. Double nothing is …let’s see …carry the 0 …integrate the square …nothing.
  
  source
  - Ulrich@feddit.org ⁨3⁩ ⁨weeks⁩ ago
    I don’t understand anything you just said.
    
    source
GreenKnight23@lemmy.world ⁨3⁩ ⁨weeks⁩ ago
I love that this thread is filled with opinions of people who have no clear idea of what a federated gitlab does or looks like and yet still believes that federation is the only answer just “because”.

source
nroth@lemmy.world ⁨2⁩ ⁨weeks⁩ ago
Git itself is a distributed VCS…

source
- oysvendsen@lemmy.world ⁨2⁩ ⁨weeks⁩ ago
  Tha is true, but the social aspect of sharing and following projects does not itself have distributed protocol. This is were AP makes sense.
  
  source
Cris_Color@lemmy.world ⁨3⁩ ⁨weeks⁩ ago
Awww :(

source
W3dd1e@lemmy.zip ⁨3⁩ ⁨weeks⁩ ago
Does anyone know if there is another federated version of GitLab/GitHub? That’s something I wouldn’t absolutely switch to.

source
- thann@lemmy.dbzer0.com ⁨2⁩ ⁨weeks⁩ ago
  ForgeJo
  
  source