Gregory's Server@jwildeboer I think some of the comment threads are missing the point. The tools of choice don't matter as much as the accessibility.
For OSS projects, we want a codebase, associated docs that are accessible. Install/usage instructions, etc and some manner of contacting the maintainers. Then some form of issue tracker.
If I'm looking for bugs, I like to search through all of the above to see if there is any relevant info already out there. This could be a mailing list archive, a bugzilla issue, GitHub issue, etc. What matters to me in that moment is finding the information. I don't need to login to any of these tracking mechanisms, and they're easily indexed by search engines which makes my quest simple.
When the issue tracker, discussions, and means of contacting the maintainers are in a walled garden like discord or slack, it adds barriers. Additionally, I can't just search across different issue trackers. I have to individually go to each one and use a proprietary search (if available).
1/
@jwildeboer
I'm often working through tracking an issue from an application layer all the way down to the kernel and some old big in malloc that makes things weird. I should be able to use a search engine to get to the different bits of correlated information. Some apps have a discord only knowledgebase and I have to sacrifice anonymity to join a server, do their onboarding, search through things, find a linked bugzilla ticket that is closer to what I'm looking for, then leave the server to get rid of the clutter, then go from there. Usually I'll bounce through some mailing lists, some GitHub discussions, a code review with a discussion on a specific chunk of code, then more mailing lists, a detour to Wikipedia to confirm something, etc. Along this journey, I don't have to sign up for anything other than those walled gardens of discord/slack. I don't really want a future where I'm hopping between several proprietary apps to find a chain of discussions for *open-source* projects.
2/
@jwildeboer
I'm often working through tracking an issue from an application layer all the way down to the kernel and some old big in malloc that makes things weird. I should be able to use a search engine to get to the different bits of correlated information. Some apps have a discord only knowledgebase and I have to sacrifice anonymity to join a server, do their onboarding, search through things, find a linked bugzilla ticket that is closer to what I'm looking for, then leave the server to get rid...