There has been a lot of talk about companies and individuals adopting licenses that aren’t OSI opensource to protect themselves from mega-corp leechers. Developers have also been condemned who put donation notices in the command-line or during package installation. Projects with opensource cores and paid extensions have also been targets of vitriol.
So, let’s say we wanted to make it possible for the majority of developers to work on software that strictly follows the definition of opensource, which models would be acceptable to make enough money to work on those projects full-time?
Universal basic income
The best solution for a lot of problems. Imagine how awesome OSS could be if any dev could work on it at least part-time while still being able to eat and pay rent/mortgage.
Imagine how awesome any creative field could be
I’m for it but what do we do in the meantime?
My partner is on SSDI for disability. If she works, she will lose her SSDI income, but she’s allowed to generate income that isn’t work/labor.
She is exploring FOSS as a career path because she could accept donations and that wouldn’t impact her SSDI. She understands donations would be minimal, but she’s hoping it’s a way for her to break into the FOSS scene.
deleted by creator
Three examples of open source software where at least one developer could give up their regular job and work full-time on the open source project. I’m sure there’s more (The Linux kernel maybe ?) :
- Mastodon
- Lichess
- SerenityOS
In both cases possible because of people donating. The last example is quite remarkable given the personal history of the developer and the fact that it was “just” a fun project with the developer sharing videos about programming for the fun project.
deleted by creator
As mentioned in books published TWENTY YEARS AGO, many companies working in Open-Source make their money in value-added services and support.
My side gig has been doing that for the last 22 years.
And, that’s the number-one answer from chatGPT.
It’s also totally okay to not blithely jam the words together but to pretend hyphens are a thing.
As mentioned in books published TWENTY YEARS AGO, many companies working in Open-Source make their money in value-added services and support.
And the world hasn’t changed in 20 years?
It’s also totally okay to not blithely jam the words together but to pretend hyphens are a thing.
What?
I think the route of giving it all away for free and either offering hosting if the project needs it or (business) support is the most successful way of doing this.
I have no problems whatsoever with donation buttons / banners (like Krita does) but I’m afraid random donations is not really a sustainable model for most projects. I try to remember to donate to projects I use a lot (especially if it’s for work) but it is another thing on my todo list and not one with high priority, so I don’t do it as often as I’d like … 😓
That’s possibly fine for services, but what happens when a large, well-known competitor decides to offer the service at a lower price (possibly on their own infrastructure), takes away the customers, but doesn’t contribute back?
Also, how should libraries (aka stuff that can’t be hosted or doesn’t have an interface) be handled?
Yeah, very good points. A while ago there was talk about some kind of foundation where maintainers could bill their hours and people and big tech companies could donate. Not sure if / how that would work …
During the xz incident I also talked about this on Mastodon and someone suggested that big tech could just employ maintainers without them having to do anything for the company directly, just work on the project / library the company uses. Again not everybody would want to do that …
I’m afraid there’s no easy one-fits-all solution here.
Do you believe breaking away from the strict OSI opensource definition would be acceptable? It could allow things like:
- royalties for commercial instances
- service fees for commercial instances
- no commercial use
not all at one of course





