the single most important criteria when replacing Github
Consider all the data that's used to provide the value-added features on top of git. Issue tracking, wikis, notes in commits, lists of forks, pull requests, access controls, hooks, other configuration, etc.
Is that data stored in a git repository?
@joeyh @technomancy Even if you were to distribute your issues inside a git repo or etc (though, a PR inside a git repo? Do you have PRs for your PRs?) you'll still need a mechanism for notify someone that an update to that repository is available for consideration right? In which case you probably need some sort of messaging layer
@cwebber btw, activitypub (or ssb) could be very very useful for the whole social network side of things, which is sorta kinda orthagonal to what I've been talking about.
(But we also know how hard it is to get social network traction, any this is all going to mostly blow over soon; the gitlab import graphs are predictably trailing off. So my optimisim is slight.)