If you're major concern is copilot : Microsoft sucking up your codebase, you better not be producing open source applications anywhere.

Not a single open source license will protect you. (And it won't help even if they add an exclusion clause for AI).

The author appears to highly appreciate being able to contribute without an account, just an email.

I didn't quite get why that is. Isn't an account effectively just an email, with an additional password?

One very crucial point that no forge (IIRC) supports that the article missed (or I accidentially skipped it) is that email supports tree-style discussion! That is a HUGE benefit IMHO, especially for patchsets, but also for "issue" discussion!

Patches / PR

> It’s probably the core reason developers choose GitHub as their main git forge. I get it. It does have it’s advantages of giving a better experience for reviewing a set of changes. Initially. But what if I told you there was a time when submitting email-based patches was the standard for version control?

The author explains well how you can bear with patches, but not why patches were chosen in the first place. What advantages do they have over PR? I see none, and I won't lose my precious time working-around an inferior process to Github's already subpar PR one.