Note from another list by OSI's Patrick Masson

[Lawrence Rosen <lr...@rosenlaw.com>]

FYI. /Larry

 

************ By Patrick Masson masson@opensource.org
<ma...@opensource.org> . 

 

Here is some general information in our FAQ:
http://opensource.org/faq#approved-licenses-only

Interestingly, as this appears to be increasing (i.e. governments/agencies
looking to adopt "open source software") we have begun cataloging
policies/laws that site the OSI and OSI Approved Licenses as a determiner of
software being open source or not. This is here:
http://opensource.org/authority

There are many more, but we have yet to capture them all. This is a summer
intern project :-)

Re: Note from another list by OSI's Patrick Masson

[Ralph Goers <ra...@dslextreme.com>]

Larry, this is a very good article.  Of interest to me is the section titled Can I write proprietary code that links to a shared library that's open source?  

I would assert that the answer given in that paragraph, “Sometimes you can”, is exactly why the ASF provides guidance on which licenses can be safely incorporated into ASF projects. 

Ralph



> On May 20, 2015, at 11:48 AM, Lawrence Rosen <lr...@rosenlaw.com> wrote:
> 
> FYI. /Larry
>  
> ************ By Patrick Masson masson@opensource.org <ma...@opensource.org>. 
>  
> Here is some general information in our FAQ: http://opensource.org/faq#approved-licenses-only <http://opensource.org/faq#approved-licenses-only>
> 
> Interestingly, as this appears to be increasing (i.e. governments/agencies looking to adopt "open source software") we have begun cataloging policies/laws that site the OSI and OSI Approved Licenses as a determiner of software being open source or not. This is here: http://opensource.org/authority <http://opensource.org/authority>
> 
> There are many more, but we have yet to capture them all. This is a summer intern project :-)