Earlier quoted context omitted.
This is a take I have seen and don't hear often. I depended on a FOSS project once that was mostly done by one maintainer, and would sometimes send feature or fix patches upstream. Once I sent an e-mail that I could give him hundreds of dollars for some bug bounties - his program would improve and he would make some money out of it. He said thanks but no, he made enough in his day job and only had limited time to mai…
I think your experience may be different from the psychology-of-obligation issue that the GP describes. For someone in a stable, salaried job that pays reasonably well (assuming USA level or the better paid parts of Europe), it rarely makes financial sense to accept "hundreds of dollars" for a complex task. That's due to the amount: "Thousands to tens of thousands" would likely get a different sort of response, assum…
This affects my end as well - I was monetizing their product, and could probably justify an unsolicited bug bounty as external work. I don't know what the status of an unsolicited donation would be, I would have to ask my accountant.
The main premise is that some FOSS projects turn down smaller donations. In my case for a bug bounty, in GP's case a more general donation. When people discuss the need for FOSS donations, these cases aren't always mentioned.
In this specific case for me, the upstream was already fixing bugs in the tree, (as was I), and upstream was monetizing their product as well, so I thought it might work out well for everyone. At the end of the day I felt better about it anyway, because I was monetizing and using their product, and I did make an offer. I wound up contributing back with feature and bug patches (the bugs I could figure out how to fix).