Public Code With Public Funds

Paw Prints: Writings of the maddog
I was summoned to a large bank the other day. This bank administers funds for various philanthropic organizations, and often oversees grants for software development.
The bank had an interesting idea. Since the grants they handed were purportedly for the "common good", why not make a stipulation that any software developed through a grant be a free and open source license?
At first the bank thought about insisting that all of the software be GPL. That way the bank could be assured that the maximum number of people could use the code that was developed with these philanthropic funds.
However, the bank worried about companies who wanted to take the GPLed software and make a significant investment of their own money in improving it. Would the wording of the GPL discourage the re-use of this code if the company investing their own money in the new code had to disclose all of their work?
Eventually the bank decided that the correct path was to have the copyright for the code transferred to the bank. If the bulk of the code was developed under the bank's financing, then the code would be licensed back to the developing company as GPLed code. If that company (or another company) wanted to make a significant improvement in the software with their own resources, then the bank would be able to license the code to them under a different Open Source license....the dual-licensing model, with a twist.
This model might also be useful at publicly funded universities for their publicly funded research projects. Those people and companies that wish to simply use the code and research created by the university would be able to do so under the GPL. Those that felt they needed a different type of license could go back to the University and negotiate for that different license.
comments powered by DisqusSubscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

News
-
Wayland 1.24 Released with Fixes and New Features
Wayland continues to move forward, while X11 slowly vanishes into the shadows, and the latest release includes plenty of improvements.
-
Bugs Found in sudo
Two critical flaws allow users to gain access to root privileges.
-
Fedora Continues 32-Bit Support
In a move that should come as a relief to some portions of the Linux community, Fedora will continue supporting 32-bit architecture.
-
Linux Kernel 6.17 Drops bcachefs
After a clash over some late fixes and disagreements between bcachefs's lead developer and Linus Torvalds, bachefs is out.
-
ONLYOFFICE v9 Embraces AI
Like nearly all office suites on the market (except LibreOffice), ONLYOFFICE has decided to go the AI route.
-
Two Local Privilege Escalation Flaws Discovered in Linux
Qualys researchers have discovered two local privilege escalation vulnerabilities that allow hackers to gain root privileges on major Linux distributions.
-
New TUXEDO InfinityBook Pro Powered by AMD Ryzen AI 300
The TUXEDO InfinityBook Pro 14 Gen10 offers serious power that is ready for your business, development, or entertainment needs.
-
LibreOffice Tested as Possible Office 365 Alternative
Another major organization has decided to test the possibility of migrating from Microsoft's Office 365 to LibreOffice.
-
Linux Mint 20 Reaches EOL
With Linux Mint 20 at its end of life, the time has arrived to upgrade to Linux Mint 22.
-
TuxCare Announces Support for AlmaLinux 9.2
Thanks to TuxCare, AlmaLinux 9.2 (and soon version 9.6) now enjoys years of ongoing patching and compliance.