Excited about #ForgeFed but unsure what the status is? 😅

Want to help but unsure how? 🤔

Wondering what's separating us from having a fediverse of forges? 🤓

How do we, the free software community, stop depending on proprietary centralized tools and switch over to a free, by-the-people, decentralized hosting and collaboration platform?

I have an idea: Let's start doing biweekly/monthly community meetings! What do you think?

Please vote, and also comment and share your thoughts 😊

--fr33

@forgefed
As you asked for my thoughts: sourcehut already exists and works. No need for another solution for an already solved problem.

@musicmatze @forgefed what would you say is left to be done, or what's required, to have sourcehut replace githu8 and the other centralized proprietary forges? Why are so many people still using githu8, gitlab.com or even their own GitLab CE/Gitea server, and how do we as a community switch everyone to sourcehut instances?

@musicmatze @forgefed and what should people use instead? Will githu8 users just find intuitively on Sourcehut everything they expect? Will they know how to submit patches, open issues, etc. etc.?

Otherwise you also need to educate them.

What is the social reason githu8 is still in use?

Since Sourcehut can't federate with any other forge AFAIK, it would suddenly become the only forge software of the federated network... are there docs for other forges to implement federation with Sourcehut?

Is there a list of Sourcehut instances that people can join?

Does the UI allow people to interact with remote repos and users?

Idk the answers and not inplying any, just asking that seems important to me :P

@fr33domlover @forgefed

> just find intuitively on Sourcehut everything they expect?

No.

> Will they know how to submit [...]?

No.

Reason is that #shithub educated them a really bad and messy workflow, nothing clean and _git_ tailored.

> Since Sourcehut can't federate

False. Email is federated and so is git. #sourcehut is just a UI for those two.

@musicmatze @forgefed

What makes the githu8 workflow bad and messy? Not taking a side, just asking. Side note and nice reminder for ourselves, the workflow needs to be ultimately _human_ tailored.

And that "false" there - It seems you have a strong opinion about git & email & how they should be used? I respect that, but can we still look at the facts with honesty?

I mean, the fact is, Sourcehut doesn't federate with most other forges, and they don't federate with Sourcehut. Because most forge websites seem to be Gitea and GitLab, which don't federate, with any protocol. So I just mean, if we want to switch to email based federation with a web UI like Sourcehut's, we need to either implement this federation in more web forges, or decide it's going to be a Sourcehut-only federation (kind of like a Postfix-only email federation or a Mastodon-only short-text-message federation). No sidrbtakrn, jist pointingbthis out. What is our vision? ^_^

@musicmatze @forgefed

Whoops, *no side taken, pointing out

Yeah, git federates via email just fine, but, e.g. can users from gitea.io, gitlab.com, sr.ht etc. etc. use the web UI to open issues on each other's projects? Comment? Submit patches? etc. etc.

They can't, they don't inter-operate. At least so far. That's what I mean by no federation.

Follow

@fr33domlover @musicmatze People can use email to communicate to sourcehut. Sourcehut can't do that backwards though since all other forges are locked-in into their UIs and private protocols.

There's no web UI from other forges to sourcehut and there's no need for it, because this would require people to register on at least one of forges to contribute, whereas with the current approach you only need an email address.

Sign in to participate in the conversation
Fosstodon

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.