So I found an open source project that uses the reciprocal public license 1.5 (RPL). It seems that the RPL means that you must post all of your code back out to the community.
RPL 1.5 - Paragraph 5
Further, under the RPL all components you author including schemas, scripts, source code, etc. -- regardless of whether they're compiled into a single binary or used as two halves of client/server application -- must be shared. You have to share the whole pie, not an isolated slice of it.
I work for a health care company that is not going to be ok with me posting our proprietary code out on the internet.
So I am wondering, is that really what the RPL does? Is there limitations on what needs to be published? Or is it really just any thing that touches the RPLed project must also go open source under the RPL?
“Reciprocal License” means a license of an item of Software that requires or that conditions any rights granted in such license upon: (i) the disclosure, distribution or licensing of any other Software (other than such item of Software as provided by a third party in its unmodified form); (ii) a requirement that any ...
You can add or change to whatever license you or your company wants to. Otherwise there may be other copyright holders that you need agreement from in order to change licenses.
Can I restrict how people use an Open Source licensed program? No. The freedom to use the program for any purpose is part of the Open Source Definition. Open source licenses do not discriminate against fields of endeavor.
Open source software licenses govern how others – besides the originator – can use, modify, or distribute software code. They grant other users the permission and rights to use or repurpose the code for new applications or to include the code in other projects.
For a commercial software RPL is even worse than GPL.
It is true that you have to publish your source code on any derivative work.
Also in GNU web site it says:
The Reciprocal Public License is a non-free license because of three problems. 1. It puts limits on prices charged for an initial copy. 2. It requires notification of the original developer for publication of a modified version. 3. It requires publication of any modified version that an organization uses, even privately.
source
Edit
Quatation from RPL 1.5:
6.0 Your Obligations And Grants. In consideration of, and as an express condition to, the licenses granted to You under this License You hereby agree that any Modifications, Derivative Works, or Required Components (collectively Extensions) that You create or to which You contribute are governed by the terms of this License including, without limitation, Section 4. Any Extensions that You create or to which You contribute must be Deployed under the terms of this License or a future version of this License released under Section 7. You hereby grant to Licensor and all third parties a world-wide, non-exclusive, royalty-free license under those intellectual property rights You own or control to use, reproduce, display, perform, modify, create derivatives, sublicense, and distribute Licensed Software, in any form. Any Extensions You make and Deploy must have a distinct title so as to readily tell any subsequent user or Contributor that the Extensions are by You. You must include a copy of this License or directions on how to obtain a copy with every copy of the Extensions You distribute. You agree not to offer or impose any terms on any Source Code or executable version of the Licensed Software, or its Extensions that alter or restrict the applicable version of this License or the recipients' rights hereunder.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With