Re:The White House just open sourced their first Github repo
by SoftwareMaven on Thursday August 23, 2012 @07:32PM
(#4425442)
This was exactly my question. How can they put limitations on public domain code?
[ Parent
| on HN ]
Re:The White House just open sourced their first Github repo
by cdibona on Thursday August 23, 2012 @07:51PM
(#4425511)
So obviously I don't work for the white house, but I suspect that since this code depends on bits of gpl'd code to function, they made the entire project licensed similarly.
Also, it is not as simple as you think, government code isn't always pd. If written by a contractor, the contractor/contracting organization can decide to not release code/work to the public.
Finally, if this code was written by Macon's team, and not by contractors, then you could maybe make an argument that the parts of the code that came from original gpl parts would be gpl'd, but not the code written by the wh team that doesn't depend on the gpl'd parts, as the code isn't distributed to end users the way the gpl mandates sharing.
Anyhow, I'm trying to simplify a lot here, but thought I'd chime in.
Re:The White House just open sourced their first Github repo
by dllthomas on Thursday August 23, 2012 @07:55PM
(#4425524)
They can't, but only part of the code is public domain. If you want to use the whole pile of it, you do so under the GPL - if you pick out the changes made by the govt, then you can apply those elsewhere.
Re:The White House just open sourced their first Github repo
by mmahemoff on Thursday August 23, 2012 @10:48PM
(#4425972)
So effectively GPL imposes a dual (or multiple) license on the non-GPL part.
Re:The White House just open sourced their first Github repo
by dllthomas on Thursday August 23, 2012 @11:11PM
(#4426011)
Insofar as the non-GPL part is specific to the GPL code, yes. If you reimplement the GPL code under a different license, you could reuse the public domain bits. I expect in most cases, it wouldn't be terribly worthwhile.