So, a tangential answer to your question is to explore your premise that the business model of the 80s and 90s is better. As one who has programmed since then I can offer this perspective, which will apply equally to what you do.
Up until 2011 we "sold" our software. Users bought it, and it was theirs to use. We funded support (and development) out of new sales.
However this model is not sustainable. As the installed base grows we hired more full-time support which in turn meant less money for development. Or put another way, if new sales dried up, we'd close our doors. That is not helpful to the existing customers.
For a while we had a "support contracts" model, but customers not on contract "just want this quick question answered" and sets up internal fights between support and revenue over helping customers not on contract. (customers expect _some_ support on purchase and they get used to that)
So we changed to a subscription model. This is sustainable. Subscriptions pay for support staff, new sales pay for developers. Our goal is to get subscriptions to cover both, which takes the pressure off the "need to sell more"
Obviously we are doing commercial software, not FOSS, but the basic premise is the same - to be effective you need to be sustainable. So your model needs that built-in from the start. Alas "donations" is not sustainable, and only a lucky few get big company support (which could disappear quickly.)
I wish you success though - let us know if you find a better model.