Ask HN: Open source developers, would you do paid support for your projects?

If I use some FOSS component, I know that if I use it in the usual way, there's a community of others doing similar things that I can ask if I get stuck. I don't expect to pay for that (nor do I expect payment for my own contributions to those discussions).

I don't want to pay for a "support contract" for FOSS. - First and foremost, that's not the model: if I want commercial software, I can buy it already - I use way too many components to manage support for all of them - Many of the components I use are too small to warrant paid support at a practical level - Most of the time, it works just fine anyway - When it breaks, I'm usually happy to fix it myself and contribute that back (and that's the indirect cost I'm happy to pay).

I am willing to contribute to community costs: funding eg. Python Software Foundation, Software Freedom Conservancy, etc, on an annual basis.

I am willing to pay "support aggregators", eg. RHEL licenses. My expectation there is that I have one support contract that covers everything shipped with the OS, and that Red Hat will use their aggregated income to perform my community obligations (and do better because they're full-time experts in a team). I pay extra for convenience, and they take a profit.

I also strongly support a bounty-style model. I'm happy to pay someone (either by tasking an employee, or contracting an external developer) to add significant new functionality, or to tackle a backlog of maintenance, or to start a new project.