Following up on the #github fiasco, maybe on top of only using #FOSS software, and federating as much as possible along #selfhosting, what we really need is agent-centric naming and #identity system (also to allow for nomadic identity for #Mastodon and the fediverse).
What we really need would be a federated code hosting platform. Everybody could run a own instance or join one he/she can trust in but interact with projects that are hosted on other instances without need for an extra account there. All tools we would need to build something like this are already there. Git is made for distributed code management and the rest could be done with ActivityPub.
The flip side of the #GitHub exodus is that it will become harder to find out about new software projects since it won't be mostly centralized in a single place. Time to revive a Freshmeat of sorts?
YOUR ATTENTION PLEASE. SDF has just acquired Microsoft. Our first act as the new owner of Microsoft is to release GITHUB under the NetBSD license and revert our company logo back to HEAVY METAL...... #GitHub
@delores My comment is mostly about the projects that migrate away from #GitHub. Even though I emptied out my GH account years ago, I still have it, so reporting issues on random software projects there remains easy.
If you're concerned about #Microsoft buying #GitHub (and you should be) please do not simply move to GitLab.com (the hosted #GitLab instance), it also runs on MS servers, (Azure) - always self-host GitLab, or if it's too heavy, go with Gitea.
Whatever you do, do not simply move from one silo to another.
I'd really rather not use any Microsoft tools unless I really have to, but I know there are a ton of folks using GitHub and it's a nice way of connecting with people.
So, who has started working on an #ActivityPub#ActivityStreams federation protocol for #git pull requests, forking, issue tracking, identity/membership/permissions, following, etc?