This will usually mean that if you build a patch or other modification of the program and want to distribute it you must also publish the sources of that modification under a license explicitly mentioned in the program license text.
In some license types this includes both the other program and any program using that (including your program). In others (like LGPL) this will only be required only for modification made to that program, but not to your program if they are separated (LGPL is typically used for libraries and doesn't enforce publishing the library consumers).
you can sell (and release with your own commercial license) your own app built with the provided code.
but:
you can not improve on the code (of the software you are using within your app) directly and not give it to public domain (usually it is in the original license of the software).
Instead of relying on those summaries, you would be advised to carefully read the license for any open source license you plan to use in a closed source product.
For instance, LGPL does not actually require you to release source code changes to the public domain. Rather, it requires you to release them under the terms of the LGPL.
If you are nor sure that you understand the implications of a particular license, talk to your company's lawyers.
发布评论
评论（3）
这通常意味着，如果您构建程序的补丁或其他修改并想要分发它，您还必须根据程序许可证文本中明确提到的许可证发布该修改的源。
在某些许可证类型中，这包括其他程序和使用该程序的任何程序（包括您的程序）。 在其他系统中（例如 LGPL），仅当对该程序进行修改时才需要这样做，但如果它们是分开的，则不需要对您的程序进行修改（LGPL 通常用于库和不强制发布图书馆消费者）。
This will usually mean that if you build a patch or other modification of the program and want to distribute it you must also publish the sources of that modification under a license explicitly mentioned in the program license text.
In some license types this includes both the other program and any program using that (including your program). In others (like LGPL) this will only be required only for modification made to that program, but not to your program if they are separated (LGPL is typically used for libraries and doesn't enforce publishing the library consumers).
简单地：
但：
simply:
but:
建议您仔细阅读您计划在闭源产品中使用的任何开源许可证，而不是依赖这些摘要。
例如，LGPL 实际上并不要求您将源代码更改发布到公共领域。 相反，它要求您根据 LGPL 的条款发布它们。
如果您不确定自己是否理解特定许可证的含义，请咨询您公司的律师。
Instead of relying on those summaries, you would be advised to carefully read the license for any open source license you plan to use in a closed source product.
For instance, LGPL does not actually require you to release source code changes to the public domain. Rather, it requires you to release them under the terms of the LGPL.
If you are nor sure that you understand the implications of a particular license, talk to your company's lawyers.