@zeenix@jele OK, so GitHub has its issues too (proprietary tool, owned by Microsoft), but I'm *less* focussed on that in this particular instance; at least with GitHub, I can see discussion in GitHub issues and obtain code without needing an account. That's not the case with Discord.
As mentioned, there are also plenty of platforms (e.g. Gitea, Forgejo, GitLab etc) that make it trivial to use GitHub's API to import your repo *and* its Issues and PRs. It's not perfect, but at least it's not *quite* as closed as Discord is.
But also, yes, if you can use an open-source software forge, that's great too. The downside of that though, is that people need to currently create accounts on each individual forge to contribute, whereas (for better or worse) GitHub accounts are relatively ubiquitous). Once forges like @forgejo make more progress on federation (https://forgejo.org/faq/#is-there-a-roadmap-for-forgejo), hopefully this will reduce friction there.
@zeenix@jele OK, so GitHub has its issues too (proprietary tool, owned by Microsoft), but I'm *less* focussed on that in this particular instance; at least with GitHub, I can see discussion in GitHub issues and obtain code without needing an account. That's not the case with Discord.
As mentioned, there are also plenty of platforms (e.g. Gitea, Forgejo, GitLab etc) that make it trivial to use GitHub's API to import your repo *and* its Issues and PRs. It's not perfect, but at least it's not *quite*...
@zeenix
Ah.
I think it is allowed to widen the conversation with an answer π«’π
@mattcen