

I’m not sure if you’ve ever had a public project, but for most people, be it YouTube, twitch, github, whatever, its not so easy. Negative comments grate on you, and, over time, can really take a toll.
William Osman interviewed a bunch or creators about this: https://youtu.be/DVCpKfedfok
Its not as easy as to call people out. Some people go great lengths out of spite, doxx you, send you death threats… Is it really worth it? Not that a “fuck off” will work anyway.
You say people will join you but they really don’t. The reality is there are a ton of crucial open source projects being run by one person on the edge of burnout. See curl, xy, etc.
Money absolutely would help and I wish the EU would put additional funding into this.
Basically it works by every component validating the next one before loading it.
They do this by checking a cryptographic signature. Specifically, UEFI checks that the bootloader is signed by a certificate that is in turn signed by a certificate authority (CA). You can upload custom CA keys in the UEFI interface.
Per default, every UEFI ships with the Microsoft CA. That does not mean you can only run secureboot with Windows and you absolutely should enable secureboot on every machine you own. Microsoft does sign other signing keys allowing them to be also used with secureboot. For example, every major Linux distro has keys signed by the Microsoft CA and so secureboot works out of the box with those.
Even if you have an OS that does not have a signing key signed by the Microsoft CA, you can upload your own secureboot keys to get around that.
It should be pretty clear at this point that all of this is pointless if you do not set a UEFI password.