I really don’t see the benefit of forge federation. Why do people care that completely separate projects run in completely separate forges?

A project’s issues and pull requests are only useful for that project.

The author mentions avoiding multiple logins and searching across forges. The former is already addressed by social logins / federated identity. The latter is not very useful today, on a centralized GitHub, aside from finding leaked credentials and vulnerable code.

In fact, the tiny barrier of entry for contributing in a new forge might be a desirable quality, to filter out low-effort contributions.

▲

notdefio 3 days ago | parent | next [-]

On a GitHub issue page, it will show backlinks to anywhere on GitHub that issue has been referenced. This is quite helpful at times because it leads me to find how other teams have worked around an issue I'm dealing with.

There's value in related information being aggregated and linked across many projects.

▲

Arrowmaster 2 days ago | parent | prev | next [-]

> The author mentions avoiding multiple logins and searching across forges. The former is already addressed by social logins / federated identity. The latter is not very useful today, on a centralized GitHub, aside from finding leaked credentials and vulnerable code.

Absolutely not. Social logins are unacceptable and I refuse to use sites that depend on them and do not provide a normal method to make an account.

Ideally projects like this can bring us a model where you don't need to login to some other forge to interact with a project but do it by forking it onto your own forge and submitting pull requests between forges.

▲

vitally3643 2 days ago | parent | prev | next [-]

You can accept issues and pull requests from users of other forges without requiring or even allowing new account signups on your forge.

I'd like it if people could contribute to the projects I host on my own personal GitLab, but not enough that I'm willing to deal with open registration.

▲

edent 3 days ago | parent | prev [-]

> A project’s issues and pull requests are only useful for that project.

I don't think that's always true. A bug in library A might be referenced in project B with a fix in fork C.

Yes, a hyperlink works to show you where to find info. But it doesn't alert you when a PR on C is merged by A meaning that B is now unblocked.

▲

drdexebtjl 3 days ago | parent [-]

Fair point.

That said, I don’t think that works well in a single centralized forge today either. Usually you still need A to actually make a release with the fix, which isn’t tracked by the issue/PR system.

	▲	edent 3 days ago \| parent [-]
		I'm not sure. On GitHub I see plenty of bug reports which say "this is broken" with references to other repos. Those backlins are useful when someone does figure out the fix. That said, I'm very much in favour of people and projects moving away from GitHub.