Github dislikes email "aliases" so much that they will shadow ban your otherwise normal activities for months, and once flagged, support will request not only a "valid" email domain but also that you remove the "alias" email from the account completely.
Github is unfortunately the premier platform for collaborating with others to build FOSS. Until alternative forges support federation, any other forge is usually a dead end.
There are several independent options for all of those that, while they suck to go to a different site, often do a much better job than the code forge—think how Gerrit makes PRs look foolish, Bugzilla, Trac, Trello, etc. even the humble mailing list. What’s also important to note is a separate servdce offers different (or even better) organization options. Say you wanted a “polyrepo”… well, new you need a separate issues/review for every repository which often doesn’t fit as concerns can apply to mulitple repos (which now that I think about it might be one of those pressures on folks to create monorepos due to tooling lock-in choices from certain forges). That’s not to say there isn’t a cost/benefit to losing the integration of a central spot or less servers to deploy, but it very well could mean that a small orchestra of independent services could better suit a project compared to opting into every feature a code forge is offering.
That is to say, the one feature you see in all code forges—even the simple ones like cgit—is the ability to browse code/commits.
The pull request model Microsoft GitHub force on users ends up being a colossal waste of everyone’s time & it’s the only model offered. It’s also a social media platform which encourages star hacking, READMEs that are actually RENDERMEs, focusing too much on making one’s graph green, etc. that are bad for project quality & mental health IMO. This doesn’t sound like a “premier” platform but the result of lock-in & network effect. The way to break is to go host elsewhere… & since Git is a distributed version control system, this should be encouraged.
Sure, self-hosting is a great option for very large projects, but a random python library to help with an analytics workflow isn’t going to self-host. Those projects, along with 27,999,990 others have chosen GitHub, often times explicitly to reduce the barrier to contribution.
Also, all of those examples are built on thousands of other FOSS projects, 99% of which aren’t self-hosting. This is the same as arguing only Amazon is a bookseller and ignoring the thousands of independent book publishers creating the books Amazon is selling.
This isn’t to say every project should self-host, but that they could self-host. And if you don’t want to self-host, you can join groups like Notabug, or a server hosted by a foundation like Codeberg, or the privately-held SourceHut, or even the open-core GitLab with its free tier (tho publicly-traded, most of the source is open & one can run the community edition if they wish). To assume if not self-hosted GitLab CE, then one must use a closed-source, US-based, publicly-traded, megacorporate, social media + code forge platform that’s trying to monopolize the developer tooling space is a false dichotomy.