@anthk @jwildeboer I understand the distinction. There are a lot of ways to use git, and you always need some additional tooling around it because git doesn’t manage queues of proposed changes, discussion of those changes, code reviews, etc. when that tooling doesn’t follow one obvious de-facto standard you’re still turning away contributions due to friction.
@anthk @jwildeboer a self-hosted GitHub clone is fine, but it’s still extra friction (decentralized identity management and notification management with *good UX* remains an unsolved problem) and extra work for small OSS teams who are always short on resources.