Seeing as NASA and NOAA are paid for by taxes, it actually is. Now with the (decidely American) pedantics aside...
I agree with you in principle, but ultimately if people want to be paid they need to make that need or desire explicitly clear and on the record. Voluntary generosity can and will only go so far.
If someone releases their code under free-as-in-libre and/or -beer licensing, they don't get to subsequently complain if acts of voluntary generosity are "insufficient".
You are hitting shortcomings of copyright, rather than mistakes if the authors
The point is that it is in society's interest to just pay for some things that are widely benefited from. Weather data's just one example.
> if people want to be paid they need to make that need or desire explicitly clear and on the record
Nope!
> they don't get to subsequently complain
Also nope! You are not a person who gets to decide that for everybody.
A free license isn't a suicide pact or a ball gag. People can do things and then complain if it's not working out. Or not, as they prefer! But that too is beside the point. Which is that as a society we should figure out ways to support public goods like certain open-source software. Whether or not a given package maintainer asks.
https://www.af.mil/About-Us/Fact-Sheets/Display/Article/1045...
Of course, enforcing that might be pretty difficult in practice.
There are plenty of "free for personal use; restrictions apply for commercial use" type products and licenses out there. To use a specific software example, almost all mods for Kerbal Space Program are open source with a "free for personal use, commercial use prohibited; redistribution prohibited" license.
Also note how there are plenty of free-as-in-beer, closed source software out there. Commercial, open source software is simply a mirror opposite of them.
Free-as-in-beer vs. Commercial, and Open vs. Closed source, are separate concepts that can co-exist in any combination.
Open source code is simply source code that is open. Nothing more and nothing less.
The OSI says those should be "whoever receives a copy of the binaries" and "open to read/run/modify/distribute for original/modified versions".
The OSI definition is much more useful to me as a software user and programmer than any other definition I have seen.
The reason why I suggest AGPL is because it closes the "running it on a web server isn't distribution" loophole in GPL and that makes AGPL code persona non grata at Google and most SAAS companies. This license scares many companies either because they want to modify GPLed code without sharing changes or because they're afraid of having to open source other code that the AGPLed code is integrated with. This would effectively be virtually the same as a non-commercial/proprietary dual license but you'd be able to rely on the Software Freedom Conservancy's lawyers to enforce your copyrights for you and you'd have the support of the existing FOSS community.
The key however is that you have to do the contributor agreement and secure copyright or an unrestricted license to all code before merging it into your project. Otherwise offering the proprietary license option would be copyright infringement on your part if any contributor objects because you'd only have rights to their contributions under AGPL. (It's also a good idea in general to make sure any employed contributor's employer isn't going to attempt to claim copyright to their FOSS contributions before accepting the pull request.)
> Of course, enforcing that might be pretty difficult in practice.
Maybe not if there was a big organization collecting payments on behalf of the developers.
Were I a billionaire, I'd just set up a program of grants to individual developers with proven track records of making things useful to the world. Something like the MacArthur Fellows program [2] (also known as "genius grants"). There's a lot of library code that we feel should just be free, and for whom pricing and charging for it would be such a giant pain in the ass that it's uneconomical.
Sometimes that work gets big enough that it can support the overhead of a non-profit that can go out and hustle grants and donations. E.g., numpy. [3] But it's not easy for a project to get to that level and then to attract the new set of right people to make it happen. I still think there's a huge gap between what we are funding and what's societally optimal to fund.
[1] https://creativecommons.org/licenses/by-sa/4.0/
It's not about obligation. Nobody is claiming we're legally obliged to pay developers of free or open-source projects. It's about interest. As in it's in society's interest to pay for valuable infrastructure that's available to the public.
As an example, consider weather data. It's a huge benefit to all sorts of people to have good weather and climate data. It supports not just the activity of citizens, but of many businesses. Are we obligated to pay for that? No. But is it in our interest to? Definitely. If we want things to be sustained, we need to make them sustainable.
Otherwise, eventually the person in Nebraska will decide they have something better to do: https://xkcd.com/2347/