2 ms·
That is great if you are e.g. Facebook and pour a lot of resources into the community. But there are multiple archetypes of open source developers, and for most
by franciscop 6y ago
That is great if you are e.g. Facebook and pour a lot of resources into the community. But there are multiple archetypes of open source developers, and for most others reducing the amount of noise is more important than adding more channels. For many tools that add friction, thus increasing the quality would be much better.
Some random examples:
- Requiring any Issue to have some mandatory fields (version number, output, etc)
- Add some sort of "reputation" like StackOverflow for devs and require a minimum threshold
- Limit issues to those who actively contribute on Open Source (PRs, own open source, etc)
All of these would be opt-in by the maintainers of the project.
Could also kill two birds with one stone by limiting Issues and/or Discussions to Sponsors only (and collaborators)