Gregory's Server@jwildeboer I did OSS in that era and I do it in the GitHub era and sorry but no way I’d want to go back. The big gap is de-facto standardization of workflow. I can do a drive-by contribution to a project in minutes, where in the olden days I simply wouldn’t have bothered because I had to spend an hour learning their bespoke workflow.
|
5 comments
 @ef4 @jwildeboer The problem is not Git, it's Github. You have several libre alternatives, even self-hosting. @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. |
@jwildeboer decentralization would be great, but only with a standardization that definitely did not exist in the past. Also: LOL at the conceit that the work of moderating mailing lists and hosting infrastructure was the “simple” way.