Kelsey Hightower: If governments rely on FOSS, they should fund it
theregister.com
theregister.com
Firstly, lots of OSS doesn't have a well defined owner. So who gets the money?
Do they actually want to take money from the "big bad state"?
Is there a mechanism to pay them? If so, which budget does it come from?
Government spending is heavily scrutinised. Why are we spending money on something that is "free"? What due diligence has been done? Should it be a competitive tender?
It was sometimes possible to get round this. Pay for someone to speak at an internal event, buy a support package, pay for training etc.
Governments (and most large orgs) just aren't set up to pay ad hoc amounts to non-suppliers, who aren't charging money.
If you build your business on something that might disappear because someone decides to suddenly stop working on it, it's rational to incentivise them (or others) to not do that.
Same is true of all business dependencies, not just OSS ones. It's a large reason why a lot of companies do M&A - it minimizes the risks of not having control over that dependency.
https://bmannconsulting.com/notes/open-source-beyond-licensi...
(I had mentioned to him I wanted the Canadian government to get involved in funding OSS, and that we needed a way for Canadians(and Canadian Corps) to use for free but everyone else would have to pay)
I work for a non profit that creates FOSS and we were explicitly prevented from using something published as CC-BY-SA-NC (by the author) because our completely “free to access” “not for profit” project was being developed by employees working for money (paid for by a private foundation).
So what’s “non commercial”? Someone at home by themselves? What happens if they amass online followers and then monetize them somehow? They lose the license retroactively then? Was Linux non commercial when it began? (It should have been) Is it still non commercial? (Many would argue it isn’t).
That's a bit facile. For many projects, changing the license from open source to something that's not open source like you are suggesting will cause the project to die. Adoption will drop to indistinguishable from zero and it will lose any hope of achieving critical mass.
yeah you can forget about that bit
But this raises other issues. Let's say you're the US Air Force and you want to sponsor SQLite. I assume because SQLite is everywhere the Air Force runs it in their airplanes, no idea if true. How do you make sure the interests of the developers are aligned with the interests of the Air Force? You probably don't want to accept contributions from foreign nationals, or at least nobody you can't hunt down and prosecute if they do something malicious. You probably also want to vet them with a thorough background check. So they basically have to be employees (or contractors).
If you let your enemies build your highways they'll be hiding antitank mines everywhere. Should we be letting them build our software too? I can't imagine the Air Force, for example, saying "yes". But I could imagine them being quite interested in gaining this kind of control over their infrastructural dependencies.
You can request the change in the existing project in exchange of money, but that to me is asking for trouble.
It's called proprietary software