- Site menu:
- Latest Discussions
- Latest Newswire
- Archives
- Submit Story
- Story HOWTO
- Syndicate
- E-mail Alerts
The case for educating judges on open source licensing
|
|
|
Comments (2)
Actually, the case documentation does seem to be a large FUD problem...
The linked article doesn't really include complete context:
The software writer did a bang up job blaming his 1337 hax0r programming faux pas on FOSS and Postgresql. And the court happily published it...
http://www.courts.ca.gov/opinions/nonpub/B252080.PDF
The linked article doesn't really include complete context:
From Legal Opinion: 21ST CAPITAL CORPORATION V. ONODI TOOLING & ENGINEERING COMPANY wrote: David Clark also testified that he wrote the software, including code, and managed the website for 21st Capital. Postgre S.Q.L. is a database system that allows companies
A problem Chenier saw was that 21st Capital used “open source code” and made changes, sometimes on a weekly basis, to its program code without testing or validating those changes. A large percentage of the open source code was “grabbed from several different sources on the internet” and only a small percentage of the code was custom. Open source code is problematic because anonymous people on the internet design it, and “holes” are not fixed by vendor updates. Notifications that there are issues with the code may not go out.
The software writer did a bang up job blaming his 1337 hax0r programming faux pas on FOSS and Postgresql. And the court happily published it...
http://www.courts.ca.gov/opinions/nonpub/B252080.PDF
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post
Windows is developed by anonymous people and 'holes' are not fixed by vendor updates