This is cool, but I do find it odd that GitLab and Gitea isn't supported. It's always strange to me seeing people choose to build their platforms dependent on proprietary 3rd party infrastructure when good open-source self-hosted alternatives are available and easy to set up.

Maybe I’m alone with this but when I’m on GitHub, for some reason it feels more like I’m part of a community. For some reason gitlab doesn’t convey that when I write an issue there. Maybe it’s due to the packages that are on GitHub and gitlab themselves. That’s why I prefer GitHub over gitlab, although everything we do in my team we do on gitlab.

Hey there,

I'm on the Community Relations team at GitLab. I'd love to learn more about your experience as a member of the GitLab community.

When you say that opening an issue on GitLab doesn't make you feel part of a community, are you referring issues on one of GitLab's projects (ex: https://gitlab.com/gitlab-org/gitlab) or are you referring to issues on open source projects being hosted on GitLab.com?

Community is very important to us so when there are areas for improvement that feedback is really valued.

I wish that somehow people carried identity across Github / Gitlab / Gitea / other services. Like, a federated issue tracker. Or otherwise that the issues themselves were easily movable between platforms, with no lock-in. But the incumbent platforms rarely want something like this.

An alternative is to eschew platform issues entirely, and use decentralized issue comments hosted as Git repositories, like https://github.com/dspinellis/git-issue or https://github.com/neithernut/git-dit or https://github.com/MichaelMure/git-bug - I think that Gitlab should offer integration with one of them. I mean: both allowing to export issues and PRs into a Git branch, and allowing people to comment on issues and PRs by pushing to a Git branch.