使用具有“相互公共许可证1.5"的项目怎么办?是说我必须处理我的代码? [英] What does using a project that has the "reciprocal public license 1.5" mean I have to do with my code?

查看:112
本文介绍了使用具有“相互公共许可证1.5"的项目怎么办?是说我必须处理我的代码?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

因此,我找到了一个使用 相互公共许可证1.5的开源项目. /a> (RPL). RPL似乎意味着您必须将所有代码重新发布回社区.

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 -第5段
此外,在RPL下,您编写的所有组件都包括架构,脚本, 源代码等-无论它们是否被编译为一个 二进制或用作客户端/服务器应用程序的两半-必须共享. 您必须共享整个饼,而不是孤立的饼.

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.

所以我想知道,这真的是RPL的功能吗?是否需要发布什么内容有限制?还是真的只有涉及RPLed项目的任何事情也必须在RPL下成为开源软件?

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?

推荐答案

对于商业软件,RPL甚至比GPL更差.

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.

也在GNU网站上说:

相互公共许可证是 非免费许可证,原因是三 问题. 1.它限制了价格 收取初始副本费用. 2.它 需要通知原件 出版者的开发者 修改后的版本. 3.它要求 任何修改版本的发布 一个组织使用的,甚至 私下.

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.

修改

RPL 1.5中的报价:

Quatation from RPL 1.5:

6.0您的义务和补助金.考虑并表示为 授予的条件 根据本许可协议,您在此谨此声明 同意任何修改, 衍生作品,或必填 组件(统称为扩展) 您创建或创建的 贡献受条款约束 (包括但不包括) 限制,第4节.任何扩展 您创建或向您创建的 捐款必须部署在 本许可条款或将来的条款 根据以下版本发布的本许可版本 第7节.您在此授予 许可方和所有第三方a 世界范围内的,非排他性的, 那些免版税许可 您拥有的知识产权 或控制使用,复制,显示, 执行,修改,创建衍生产品, 分许可,并分发许可 任何形式的软件.任何扩展 您进行的部署必须具有 独特的标题,以便于讲述 任何后续用户或贡献者 扩展由您决定.你 必须包括本许可证的副本,或 有关如何获取副本的说明 与您的扩展的每个副本 分发.您同意不提供或 将任何条款强加于任何源代码或 许可的可执行版本 软件或其可更改的扩展 或限制适用的版本 本许可证或接收者的权利 在这里.

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.

这篇关于使用具有“相互公共许可证1.5"的项目怎么办?是说我必须处理我的代码?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆