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.

you are viewing a single comment's thread
view the rest of the comments

[–] NuXCOM_90Percent@lemmy.zip 42 points 3 days ago (19 children)

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?

[–] russjr08@bitforged.space 19 points 2 days ago (3 children)

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.

[–] Fizz@lemmy.nz 1 points 2 days ago

Couldnt this be done with email reminders and single sign on?

load more comments (2 replies)

load more comments (17 replies)