Yeah I feel like this is the one instance of applying EULA’s to free software projects that I don’t disagree with on principle, because the source code remains free software (unlike FUTO, Commons Clause, and so on). For another example, Mozilla applies an EULA to Firefox binaries and still releases the source code under a free license, which is an overall good to the free software movement.

Maintainership of a free software project can be very taxing so it’s refreshing to see attempts to address that that aren’t intrinsically at odds with the free software movement. Remember that users of free software have no entitlement to anything other than source code. There is no requirement in any free software license that a project have maintainers, take bug reports, accept pull requests, offer support, etc.

Also remember there are avenues to obtain third party builds of free software projects (e.g. GNU/Linux distros, F-Droid, etc) and those third parties should be able to take up the support burden for their user communities.

Edit: From their faq, this is the most concerning thing to me:

Also, if you choose to not pay the Maintenance Fee, but find yourself returning to check on the status of issues or review answers to questions others ask, you are still using the project and need to pay the Maintenance Fee.

This seems like an over-reach. Limiting participation in communities to fee-payers is understandable but attempting to restrict people from even reading in these communities is a bit too far (and I am not even sure if it can be enforced, but I am not a lawyer).