Hacker Remix
Ask HN: How do you make a living contributing to and/or creating OSS projects?
88 points by Brysonbw 2 weeks ago | 68 comments
nickjj 2 weeks ago
I have a bunch of repos with 500-1000+ stars. I've gotten folks who emailed me entire stories on how a project I created helped them get over being blocked on something, or how it kick started them into getting more involved with programming. I've on many occasions had folks email me asking me why I put some of the things I do up for free on GitHub.
All in all I've made around $17 in almost 10 years through donations (GitHub sponsorships).
But I don't do it for the money, although I'll admit it would be nice to receive income for doing something you'd happily do for free anyways. I create almost all of my projects based on a personal need and the idea of openly sharing what I can is built into how I operate given how much I've learned from others, I feel very strongly about returning the favor when I can with no strings attached.
255kb 2 weeks ago
It’s probably due to a few famous projects being massively successful (think Vue.js), but I believe it’s directly tied to the project's size (audience), the maintainers' activities (conferences, etc.), and the type of audience. This last point is important—individuals are more likely to donate, while companies often need months of convincing, and it usually doesn't work, or they expect their logo everywhere with analytics (CTR, etc.) to justify it, which is basically advertising.
I have a sizeable seven-year-old open-source project (Mockoon) and, over its lifetime, I’ve received low four figures in donations, which is awesome, but far from enough to make a living from it.
Now, I’m creating a cloud version of the software, which has started generating revenue. It’s a lot of work, but leveraging the open-source success and sell something seems like a safer path.
bruce511 2 weeks ago
Eh? The only people who think you can make a living from Open Source (without working for a corporate) has never bothered to try. The number who have done it is a rounding error from zero. It's quite literally the hardest way to make money in software.
>> individuals are more likely to donate, while companies often need months of convincing, and it usually doesn't work, or they expect their logo everywhere
Companies cannot donate. People make donations, not companies. The only way to get a person at a company to send you money is by sending them an invoice for pretty much anything. Since you're giving the code away for free, advertising is pretty much all what you've got left to sell.
Repeat after me - Donations are not a business model. It's a hobby model.
Hosting can work at small scale. But I can host your product for less than you can. So if you're popular I can just host your software, and siphon off a chunk of your market.
marginalia_nu 2 weeks ago
Seems fairly important to somehow write or talk about what you do[1]. Building stuff and never telling anyone about it never got anyone paid. You don't need to become a shill, but the world needs to learn about what you're doing. Will say with full certainty I would not have been able to quit my job and do this full time if I didn't blog about my misadventures.
Risk of this being mostly survivorship bias, but I think in general it's helpful to build something that's more of an end product and not a library or some other widget in the making of products. Possibly also helpful if yours is an ambitious project that somehow seems doable. Ladybird is possibly an even better case of this going well. Exception possibly being if you end up as a linchpin tech like curl.
In general I don't think patreon/github/etc. donations will ever add up to much than coffee money. Most of my money has been from grants, one large donation from some rando anonymous person, and a nonprofit.
[1] Basically this: https://www.codusoperandi.com/posts/increasing-your-luck-sur...
benhoyt 2 weeks ago
cedws 2 weeks ago
plankalkyl 2 weeks ago
But I saw this talk by Evan Czaplicki (author of Elm) a while ago.[1]
The talk is primarily about the economics of open-source programming languages, but I think that a lot of the issues discussed overlap with other areas of OSS.
From the description of the youtube video:
> In the mythology of open source, programming languages are created by people who seemingly have no direct economic function. They are just really good at compilers (somehow) and have a house to live in (somehow) and have a lifetime to devote to creating a useful programming language (somehow!)
> We will examine specific organizations that create programming languages. Where do the salaries for compiler engineers come from? How does Go end up with 5 engineers and Dart end up with 30? Who signs off on these expenses and why? Does this put any boundaries on language design or development practices? And how do the economics work for people outside of the major tech corporations?
> My goal is to give the talk I needed to hear 10 years ago when I was just starting on Elm. By clearly delineating the many variations of corporate funding and independent funding, I hope users will come away with a better foundation for evaluating and comparing programming languages.