The parent of this thread is someone in marketing suggesting ways this could come out of the marketing budget, very similar to the workaround of invoicing suggested in your linked comment. Both are ways to make donating to OSS a business expense rather than a charitable donation.
No, not really. Adding logos and yadda in exchange for remuneration is a really well established form of commercial monetization. In contrast, invoicing OSS is a new and innovative way to get cash for what you already do, just like a donation.
If people want to go that route, my comments on the internet aren't some kind of bar to that approach, so I'm not sure why you seem to feel some need to argue it.
But if you are doing open source for idealistic reasons and yadda, as per my comment, then invoicing per Patrick McKenzie's explanation is actually something new and innovative that serves a similar function to the donation model in terms of preserving an element of the OSS model that matters to some folks/projects, but opens up the possibility of getting it from a company. In addition to being something of a green field for the donation model and extra source of money, companies generally have deeper pockets than individuals.
I'm not telling anyone they aren't allowed to commercialize their project. I'm just saying it's a space I've thought long and hard about for many years and researched and yadda, and if you are in open source because a business model is antithetical to your mental models and goals for the project, then invoicing may suit your needs in cases where corporate sponsorship feels like the wrong answer.
Invoicing support, maintenance and custom development of open-source software is a more established practice than patreon-style donations to open-source developers.
We’re discussing it right now... I’m referring to the concept of “invoicing open-source” which you describe as “new and innovative”. I’m arguing that it’s not. It’s a variation of the support and custom development model which is already very common.
Thanks.