Ext JS许可选项 [英] Ext JS Licensing Options

问题描述

如果我使用它， Ext JS图书馆的哪些许可选项将适用在我们的内部公司CMS？

Which of the licensing options for the Ext JS library will apply if I use it in our in-house company CMS?

推荐答案

看看这个报价从：

Take a look at this quote from Planet MySQL - GPL and Javascript:

[...]当GPL应用于
JavaScript库时，整个故事变得更加
复杂。当用户
使用库时，他们将下载
HTML，CSS图像和javascript
库。首先要实现的是
，您正在分发代码。它的
在您的服务器上，现在它在用户的
计算机上。这给任何
用户有权查看
的JavaScript代码，并重新使用
另一个项目。这意味着你
不能模糊javascript代码
，人们可以复制/粘贴
自己使用。这可能是你如何
目前看javascript。
但是HTML，CSS和
图片怎么会被公开使用？没有
它不能。那些项目不是在GPL许可证中定义的
的代码，所以应该将
视为数据。因此，GPL
不隶属于
应用程序的那一部分。

[...] The whole story becomes a bit more complicated when GPL is applied to a javascript library. When users are using the library, they will download HTML, CSS images and the javascript library. The first thing to realize is that you are distributing the code. It was on your server and now it on the computer of the user. This gives any user the right to look at the javascript code and reuse it for another project. This means that you can’t obfuscate the javascript code and people can copy/paste it for there own use. This probably how you currently look at javascript anyway. But how about the HTML, CSS and images, can that be publicly used? No it can’t. Those items aren’t code as defined in the GPL license, it should be considered data. Therefor GPL doesn’t ally to that part of the application.

Web应用程序可能不会
只有客户端代码中，
在
表单中的服务器上也有一部分作为PHP（或JSP或Ruby或...）
脚本。最大的问题是，我们是否需要
发布该部分以及
（根据GPL许可证）。虽然我们作为
开发人员认为客户端和
服务器部分是相同的
应用程序的两个部分，GPL没有。当使用
AJAX时，客户端代码正在与服务器交互
。但是，您可以将
与任何其他客户端/服务器
应用程序进行比较。这可以解释为
作为两个应用程序之间的数据
被转移，因此两者可能有
不同的许可证。这被称为
'ASP漏洞'，并且作为
的一个错误。当GPLv3被起草时，一个明确的
决定是不能关闭这个
的漏洞。

A web application will probably not only have client side code, it will also have a part on the server in the form as PHP (or JSP, or Ruby, or ..) scripts. The big question is, do we need to release that part as well (under GPL license). Although we as developers think of the client and server part being 2 parts of the same application, GPL does not. When using AJAX, the client code is interacting with the server. However you can compare it to any other client/server application. This may be interpreted as 2 applications between which data is transfered, therefor both may have different license. This is called the ‘ASP loophole’ and is as an error by some. When GPLv3 was drawn up, a clear decision was made to not close this loophole.

关于内部使用是否构成分配，这是从 GPL常见问题解答：

As with regards to whether or not internal usage constitutes distribution, this is from the GPL FAQ:

在一个组织或公司分配中制作和使用多个副本？不，在这种情况下，组织只是为自己制作副本。因此，公司或其他组织可以开发修改后的版本，并通过自己的设施安装该版本，而不需要向员工发放修改后的版本。但是，当组织将副本转移给其他组织或个人时，即分发。特别是向承包商提供副本用于场外使用的是分发。

Is making and using multiple copies within one organization or company "distribution"? No, in that case the organization is just making the copies for itself. As a consequence, a company or other organization can develop a modified version and install that version through its own facilities, without giving the staff permission to release that modified version to outsiders. However, when the organization transfers copies to other organizations or individuals, that is distribution. In particular, providing copies to contractors for use off-site is distribution.

所以IANAL，但我会说你会很安全地使用GPL的内部系统的JavaScript库，即使您开始将其暴露给世界其他地方，唯一适用的限制是，如果您在前端代码中使用GPL的JavaScript库，则必须对您的javascript文件进行无误模糊化的版本。如果您只使用ExtJS作为管理区域（管理员区域只能由您的员工访问），那么您仍然可以明白GPL的分发条款，我明白了这一点。

So IANAL, but I'd say you'd be pretty safe to use a GPL'd javascript library for internal systems, and even if you start exposing it to the rest of the world, the only restriction that applies is that if you use GPL'ed javascript libraries in your front end code, you'd have to make unobfuscated versions of your javascript files available. If you only use ExtJS for the admin area (and the admin area is only accessed by your employees) you'd still be clear of the distribution clause of GPL, the way I understand it.

有趣的是，还有另一个版本的GPL称为 AGPL ，试图关闭此漏洞。

Interestingly, there's another version of GPL called AGPL, which tries to close this "loophole".

这篇关于Ext JS许可选项的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！