MySQL 许可常见问题(MySQL Licensing FAQ)

admin

作者:yejr      发表于：2006-11-15 09:52:02   出自: imysql.cn, 译者:叶金荣, 转载请注明.

原文摘录自: http://dev.mysql.com/tech-resources/articles/mysql-network-and-you.html, 作者: Arjen Lentz(Community Relations Manager of MySQL AB)

End users

终端用户

If you are an end-user, you can use a GPL licensed server and will not require a commercial license to use MySQL. This applies even if you are an ISP or if you sell services on your e-commerce web site, since you are not distributing anything. If you are distributing anything, please see under the Developer heading below.

如果你是一个终端用户,则你可以使用GPL服务器而无需使用商业许可的MySQL.不管你是ISP还是电子商务销售服务网站,都适用这个原则,因为你没有分发(分发给其他人)任何东西.如果你分发了,那么看看下面的开发者的前面那部分.

If you want to take advantage of MySQL Network for your servers, you can get a yearly subscription. In case your organization is apprehensive about GPL licensed software, you can then ask for a commercial (non-GPL) license as an optional (but free) extra.

如果你想让MySQL Network提供更多高级服务的话,就可以每年订阅MySQL Network的服务.如果你(所在的组织)对GPL许可下的软件不放心的话,就可以索要一个商业许可(非GPL)作为额外的选择(但免费).

If you later decide that you no longer want to subscribe to MySQL Network, you can continue to use GPL licensed servers.

如果你将来决定不再订阅MySQL Network的服务,则可以继续使用GPL许可下的服务器.

Developers (including ISVs/OEMs)

开发者(包括分公司(ISV)和代工(OEM))

If you build an application, and link it with MySQL code, check out these possibilities:

如果你开发了一个应用软件,并且和MySQL的代码连接,则看看下面的几个可能性:

   1.  Are you only using your application in-house?
      →You are actually an end-user. See above.

  1.  你是否只是在内部使用这个软件?
      →  那么你实际上是终端用户,看上面.

   2.  Are you distributing your application as Open Source under the GPL (free or for money, doesn't matter)?
      →You may link with any GPL licensed MySQL code: client library or embedded server. The end-users of your software can, at their option, subscribe to MySQL Network.

   2.  你是否把你的应用软件在GPL许可下作为开源(是否免费无所谓)分发了?
      →  你可能和GPL许可下的MySQL代码连接了: 客户端库或者嵌入的服务器. 则应用软件的终端客户可以自行选择是否要订阅MySQL Network服务.

   3.  Are you distributing your application and only linking with the MySQL client libraries, not under GPL but with another Open Source license we allow? (see the FLOSS License Exception)
      →Same as the previous point 2.

  3.  你是否在非GPL许可但遵循其他开源许可([url=http://www.mysql.com/company/legal/licensing/foss-exception.html]查看FLOSS例外许可)下分发了你的应用软件,并且只是和MySQL客户端库连接?
      →  看看上面的第2点.

   4.  Are you distributing your application but it is not Open Source, and you want to link with the MySQL server?
   Contact MySQL AB to discuss an OEM agreement for commercial licenses. Embedding the MySQL server with your application can be an excellent idea, as it makes things very easy and cost-effective for your customers. And of course there are volume discounts.

   4.  你以非开源的方式分发了应用软件,并且你想要连接到MySQL服务器上?
      →  联系MySQL AB讨论一下用OEM协议作为商业许可.把MySQL服务器嵌入到你的应用软件中也许是一个绝妙的主意,因为这么做让你的客户非常方便并且效率很高.当然了,他们可以享受很多优惠.

   5. Are you certifying your application, whether it's open source or not, for use with MySQL Network?
   You can sign up to be a MySQL Network Certified Partner. This program helps you certify your software as compatible with MySQL Network and is quite effective when you will have your customers buy MySQL Network. There is a cost associated with this program, but the basic level is very affordable and it also gives you MySQL Network for yourself, which includes access to the knowledge base and the advisors.
As partner, you get listed on our partner web site, and your application will have a strategic advantage over competitors as it is certified for MySQL Network. There are some additional rules that govern the partner program.

   5. 你认证了应用软件,不管是开源也好还是用MySQL Network服务?
      →  [url=http://solutions.mysql.com/program/tech-partners.html]你可以注册成为MySQL Network的认证合作伙伴.这有助于你在需要客户购买MySQL Network产品时,保证你的程序和MySQL Network的产品兼容性更好而且效率更高.同时这是有相关价值的,但都是从MySQL Network能获得的基础的知识,包括访问知识库和建议.作为合作伙伴,在我们的合作伙伴列表网站列表上能看得到,并且由于有了MySQL Network认证可以提高你的战略竞争优势.还有一些其他附加的规则来管理合作伙伴.

          Your customers may want to subscribe to MySQL Network, for which your software will be tested and certified, but you don't have to worry about individual licensing or anything like that. So this is the really big new thing for developers of closed-source software
who want to support MySQL.

          你的客户可能想要订阅MySQL Network,则你的软件会被测试和认证,但不必担心诸如个别许可的事情.这对那些想要支持MySQL的封闭源码开发者来说是件大好事.

Of course, you can always sign up as a MySQL Network Certified Partner even if your situation is not as described above. You would get the benefits of MySQL Network as well as the partnership extras, for a decent price.

当然,就算你的情况没有在上述情况中,你也可以只注册作为MySQL Network的认证合作伙伴.你可以作为额外的合作伙伴从MySQL Network中获得利益,比如较低的价格.

I won't go into the definitions of "linking" or "distribution" here. We follow what the GNU General Public License text and the FSF (Free Software Foundation, the people who wrote the GPL license) say about this (Frequently Asked Questions about the GNU GPL). Lawyers also have (varying!) opinions on this. If you are uncertain but don't want to pay a lawyer, please contact MySQL.

在这里我不想进一步定义"连接"或"分发".我们遵守GNU通用公共许可以及FSF(自由软件基金会的奠基者,他写的GPl许可)所阐述的(GNU GPL FAQ部分).我们的律师在也已经确定这点了.如果你还不确定,又不愿意请律师,请联系MySQL.

KimSeong Loh wrote:
> The article listed some possibilities for Developers.
>
> Case 4: Does "link with the MySQL server" means using MySQL server in embedded mode only or
> does it include using the client libraries to connect to a MySQL database server through TCP/IP or
> other protocol?
> For example: a java application using Connector/J or an application using ODBC.

>那篇文章列出了适用于开发者的一些可能性.
>情况4: "和MySQL服务器连接"是否指只是嵌入式的MySQL服务器或者是否包括使用客户端库通过TCP/IP或其他协议连接到MySQL数据库服务器吗?
>例如,一个使用Connector/J连接的java应用软件,或者使用ODBC的应用软件.

It is about linking with MySQL code.
It definitely applies to libmysqld (the embedded server), as the server is GPL.
It also applies to the libmysqlclient (the client library), in case the application is not open source; the client lib is GPL, but
has the licensing exception to allow other open source licensed apps to link with it too.

这主要是关于和MySQL源代码的连接.
它显然适用于 libmysqld(嵌入的服务器),因为服务器是GPL的.
如果应用软件不是开源的话,它也适用于 libmysqlclient(客户端库);如果客户端库是GPL的,但是有例外的许可允许其他开源的许可下的应用软件也可以连接它.

> Case 5: Certifying the application for use with MySQL Network.
> Does it mean distributing a certified application (non-GPL) do not need a commercial license to use
> the MySQL client library or drivers such as Connector/J or MyODBC?

>情况5: 让应用软件通过MySQL Network的认证.
>是否意味着如果分发应用软件(非GPL)时,就无需购买一个商业许可才能使用MySQL客户端库或者类似 Connector/J 及 MyODBC 那样的驱动?

Certified apps have nothing to do with commercial licenses as such.
It is about certifying that the app works with the certified server. This allows the app vendor to specify a known suitable
environment for the application, and provide support based on that.

让应用软件通过MySQL Network认证跟是否需要商业许可没有任何关系.
这是关于让你的认证应用软件和认证服务器一起工作.它允许应用软件销售商为软件指定一个更合适的环境,并且基于此提供支持.

> What about cases where the developers create custom applications (non open source) for each
> customers?
> In the case of distributing a php application (non open source) which connects to a MySQL database
> through php mysql api, does this falls under case 3, case 4 or case 5? Definitely not case 1 and 2.

>如果是开发者为不同的客户定制应用软件(非开源),这种情况该怎么办?
>如果把一个通过php mysql api连接到MySQL数据库的php应用软件分发了(非开源),那么是对应哪一种情况呢?第3,第4,还是第5种?显然不会是第1,2种.

Again, it primarily comes down to what requirements an application builder has.
It makes sense to be a MySQL partner for MySQL Network, so you have those resources available, the exposure on the MySQL web site, and providing the known tested environment to users.

再说一次,这主要回归到应用软件创建者的要求.
这主要是对MySQL Network的合作伙伴才有意义,所以你才有这些可用资源,MySQL网站上那些公开的资源,以及为用户提供已知的测试环境.

We could debate the (sometimes murky) legal bottom line, but that's not it's really about.
MySQL Network for end users, and network/oem partnerships for developers, offers an environment that provides real value for
all those involved. It's also very affordable.
Inside any of these offers, licensing effectively becomes a non-issue. So why waste time on it?

我们来讨论一下合法的底线(有时候是晦涩,不明确的),不过这不是真正相关的问题.
MySQL Network为终端用户,并且网络/OEM合作伙伴为开发者,提供了一个包括真正价值的环境.
基于以上各种因素,许可证的有效性已经不是问题了,为什么还要浪费时间呢?

注:由于本人的水平有限及对MySQL License理解存在一定局限,翻译可能有误,敬请指出,谢谢!