Use Reciprocal Public License or new license

After reviewing the existing approved licenses, our team thought the Reciprocal Public License 1.1 meets our needs, however our industrial affairs team wanted to make some small changes. Could you let me know if these 4 changes are reasonable, or if we need to go through the new license approval

A potential transfer problem

Any code developer who releases FOSS code under an unsigned, nonexclusive license retains the original copyright ownership rights. If the code developer subsequently legally transfers his copyrights to a new owner, the code released under the license is no longer protected from infringement claims

Re: Use Reciprocal Public License or new license

Hi Paul, On Mar 19, 2004, at 7:29 AM, Fearn, Paul A./Urology wrote: After reviewing the existing approved licenses, our team thought the Reciprocal Public License 1.1 meets our needs, however our industrial affairs team wanted to make some small changes. Could you let me know if these 4 changes

Re: A potential transfer problem

I do not see section 205(e) creating a problem for open source at all. Rod On Fri, 19 Mar 2004, daniel wallace wrote: Any code developer who releases FOSS code under an unsigned, nonexclusive license retains the original copyright ownership rights. If the code developer subsequently legally

RE: Use Reciprocal Public License or new license

Ernie, Thanks for the feedback. I am specifically looking to 1. advertise OSD compliance (use the OSI Certification Mark) 2. do the right thing by the community Regards, Paul - Do you want your new license posted on our website, and the ability to advertise OSD

Re: Use Reciprocal Public License or new license

On Mar 19, 2004, at 1:12 PM, Fearn, Paul A./Urology wrote: Thanks for the feedback. I am specifically looking to 1. advertise OSD compliance (use the OSI Certification Mark) 2. do the right thing by the community Well, someone official will have to comment on the threshold issue. However, it