as much as many projects could use a clean slate here, i dont think the burden of migranting them manually or the act of just dumping them is realistic.
So is much of the technology behind Discourse.[1]
[1] https://discord.com/open-source (click on "OS Libraries")
A better term would be something like "Tied programmers" or "Dependent progammers". Maybe "sharecropper progammers"?
A large base of existing users, easy onboarding, and good visibility makes a big difference for many OSS projects. Using a self-hosted Git hosting system and mailing list is a lot of work—and it adds a not-insignificant barrier to entry for potential contributors. What issues exist with popular, proprietary Git and chat tools that make them unsuitable for OSS development?
What are some of the considerations you're thinking of where using a popular option is not pragmatic?