Support open source that you use by paying the maintainers to talk to your team
23rd February 2022
I think I’ve come up with a novel hack for the challenge of getting your company to financially support the open source projects that it uses: reach out to the maintainers and offer them generous speaking fees for remote talks to your engineering team.
Everyone agrees that open source projects deserve more financial support. Actually supporting projects can be surprisingly difficult though:
- Many projects don’t offer any clear mechanism for sponsoring them.
- More to the point: open source projects are often really bad at asking for or thinking about money—it’s rarely a core competency!
- Projects that do often get the tiers wrong: a $5/month “buy a coffee” GitHub sponsorship isn’t really going to make a meaningful impact on a project.
- But… making the case that a for-profit company should hand over money for something they’re getting for free is hard! You need a lot of buy-in from a lot of stakeholders for anything involving spending money—and many of the people who care about this within a company won’t have enough internal clout to get it to happen.
If you can make sponsorship happen, great: you should do that. But if not… how about reaching out to the maintainers and offering to hire them for an hour-long “consultancy” speaking engagement instead?
Thanks to the rise of remote working and Zoom, giving a talk no longer requires traveling to a venue—which could easily turn an hour-long opportunity into a full day.
One-off paid speaking opportunities are much more likely to fit into a regular company’s model of how money should spent than monthly donations.
What if they’re not experienced speakers?
The obvious flaw in this idea is that being an open source maintainer doesn’t necessarily mean that someone is a great public speaker: speaking is a skill unto itself.
If that’s the case, I propose running the session as a moderated Q&A instead.
Find a member of your team with speaking experience to act as a host. Gather questions from your other engineers in advance, and share them with your guest so that they can prepare. Then run the session as a Q&A.
This takes a huge deal of pressure off the speaker, and means you get a conversation that’s much more targeted to your team’s interests and needs as well.
So go and do it!
Remember, the key problem we’re trying to solve here is how to financially support projects and maintainers that may not be very good at asking for the money.
I want to take the pressure off those maintainers to learn how to market and sell their services.
So reach out to some projects you use and ask them if you can pay them to spend an hour of their time talking to your team! I’m excited to see how well this works.
Be generous: This isn’t about negotiating the best speaking rate from someone who may never have been paid to speak before. This is about compensating them for the enormous value that your company has gained from their work, and using a clever accounting trick to do so. So offer them a generous fee up front! Paying over the odds should be part of your goal here.
For larger companies there’s probably an upper cap on the amount that can be expensed easily. Finding out what that is might be helpful here too.
Your company likely has an existing education budget which might be a good source of funds for this kind of engagement.
(If your team would benefit from a talk from me about Datasette, sqlite-utils, Git scraping or any of the other projects I have going on, please drop me a line at
swillison at gmail dot com. You can also sponsor my work on GitHub!)
This post is being discussed on Hacker News.
More recent articles
- llamafile is the new best way to run a LLM on your own computer - 29th November 2023
- Prompt injection explained, November 2023 edition - 27th November 2023
- I'm on the Newsroom Robots podcast, with thoughts on the OpenAI board - 25th November 2023
- Weeknotes: DevDay, GitHub Universe, OpenAI chaos - 22nd November 2023
- Deciphering clues in a news article to understand how it was reported - 22nd November 2023
- Exploring GPTs: ChatGPT in a trench coat? - 15th November 2023
- Financial sustainability for open source projects at GitHub Universe - 10th November 2023
- ospeak: a CLI tool for speaking text in the terminal via OpenAI - 7th November 2023
- DALL-E 3, GPT4All, PMTiles, sqlite-migrate, datasette-edit-schema - 30th October 2023
- Now add a walrus: Prompt engineering in DALL-E 3 - 26th October 2023