News for hackers. Stuff that matters.
Re:US government commits to publish publicly financed softwa... by phkahler on Sunday April 03, 2016 @08:16PM (#11418559)
Licensing problems. For new projects this sounds great, put the code either in the public domain or they pick a license. Which one? MIT/BSD, GPL/LGPL, or something else? The former can generally be incorporated into the later, but what if they pick something else that's incompatible? At least we can see what was done and learn from it I guess. And what if they require a particular license as part of the policy and it prevent government projects from extending existing OSS project? That would be a shame.

The intent seems good, but the details will be everything.

Re:US government commits to publish publicly financed softwa... by batbomb on Sunday April 03, 2016 @10:37PM (#11419049)
GPL is discouraged in government software (speaking from DOE/NSF experience) but BSD or similar is encouraged. The path of least resistance is private/closed source, followed by open source BSD/MIT/Apache, followed by GPL/LGPL, followed by commercialization.

The reason why there is a bit of resistance with open source as a default is because funding has to be traced.

Re:US government commits to publish publicly financed softwa... by meanduck on Sunday April 03, 2016 @09:16PM (#11418802)
Its only the article stating (and misleading) that softwares be Free Software but in actual the draft never once mention Free Software. So unlikely it would be GPL/LGPL/etc.

Its also suprising to see that this question popped up after 500+ points.