今天和咨询单位访谈开源，老师无意中提到Cloudera的开源政策有了变化，我倒是最近没有看到相关的文章，下午就找到Cloudera的News Room和Blog，果然就找到了。有这么几个重要变化：

1、好消息：接下来的6个月，Cloudera将把原先的闭源产品Cloudera Manager，Cloudera Navigator和Cloudera Data Science Workbench等组件开源，但是会采用AGPL许可协议。

2、原有的开源系统依然会保持Apache许可。

3、Cloudera会提供没有支持的开源系统和商业化订阅服务（类似RedHat的服务）

4、无论CDH、HDP，还是CDP，都会采用新商业模式开展业务

 

Cloudera和HortonWorks 2018年10月3日宣布合并之后，开源许可的问题就提上了日程，毕竟HortonWorks是100%开源的公司，而Cloudera则采用核心开源，管理系统和系统性产品闭源的商业模式。当然，其中还有一些重复的内容，目前还没有看到具体的整合，或者就是内部还在争夺地盘。这次整合或许是整体整合中的一一个阶段性成果。

 

中国移动大云（Big Cloud）计划开发了超过10年作用（2007年启动），这段时间我们围绕开源做了很多的产品，同时也在演进中走了不少弯路、填了一些坑，有些经验确实需要总结和分享，供后来者参考：

1、仅仅使用开源系统只能表示你达到了行业平均水平，只有深度的介入，才能表示超越了平均水平

2、不是自己主导的开源系统，基本不会成为C位，而是为主导者服务、为社会服务

3、开源已经不是原先的自由软件（Freeware）运动了，开源已经成为了一种商业行为，甚至是一种商业模式

4、选择开源系统除了看许可证之外，还要看社区的活跃度和技术先进性，中美贸易冲突后，还要看看是否受BIS管制

5、开源系统产品化是很多企业从起步到领先的一条途径，什么时候脱离舒适区主要需考虑自身的能力水平层级、技术条件和市场需求

6、开源的合规是很多企业忽略的问题，这在内部使用、小规模商用都不是问题，但是一旦规模商用，就可能出现问题

 

===========Google Translate==========

开源是Hortonworks和Cloudera的使命的核心，也是我们的价值观和文化的核心。我们公司在新Cloudera拥有700多名工程师，每年编写大量的开源代码，为30多个不同的开源项目做出贡献。我们也是一家非常具有创新性的开源公司，自两家公司成立以来共同推出了十几个新的开源项目。

在合并之前，两家公司在不同的开源许可模式下分销他们的产品。对齐这两个模型是我们合并待办事项列表中的最后一项。与此同时，在过去几年中，我们看到许多业界同行修改了他们的开源许可策略和/或他们与Apache软件基金会的关系，产生了我们是否计划修改我们的方法的问题。

在这篇博客文章中，我们将分享我们的新开源许可模式，该模型将Hortonworks和Cloudera以前使用的许可模型对齐，并引入了一些新的变化。我们认真对待我们的开源领导角色，并认识到我们需要调整自己的许可证也是领导和更新我们对开源软件的承诺的机会。

使我们的开源许可策略和业务模型保持一致也是一个社区流程。在完成我们前进的道路之前，我们咨询了我们的客户，行业专家，律师，同行公司和员工。这些讨论强化了我们的许多开源目标：

 

1. 免于供应商锁定。 客户将他们最宝贵的资产（他们的数据）委托给我们的数据管理平台。 他们希望向平台供应商支付额外价值，而不是担心转换成本。
2. 社区标准，而不是Cloudera标准。 Cloudera已经开发了许多开源项目，这些项目已经成为行业标准，但没有一家公司能够成为唯一的创新来源。 通过投资Spark，Kubernetes和Kafka等开源项目，我们让客户保持可持续的长期架构，而不是将他们带到Cloudera开发的工具岛上。
3. 开放生态系统 我们的平台面向各种工具，应用程序和基础架构提供商。 我们为合作伙伴生态系统维护开放，向后兼容的API，即使生态系统与我们的部分产品竞争也是如此。

 

考虑到这些目标，我们已经达成了一个新的，一致的开源许可模式，我们计划在未来几个月内推出。 我们更新的开源许可模式将是：

1. 在接下来的6个月中，我们计划将Cloudera目前根据封闭源许可证许可的少量项目合并并转换为开源许可证。例如，Cloudera Manager，Cloudera Navigator和Cloudera Data Science Workbench等组件最终都将在开源许可下提供。
2. 我们所有的开源许可证都将遵循两个OSI批准的许可证之一：Apache许可证，第2版或GNU Affero通用公共许可证第3版（“AGPL”）。我们考虑了修改后的开源许可证，但确定我们使用社区接受的许可证非常重要。
3. 我们贡献的所有开源项目都由Apache Software Foundation（“ASF”）托管，将继续作为ASF管理项目。此外，我们将继续为这些上游项目提供增强和修复，因为两家公司自成立以来就已经开始。
4. 客户和开发人员将能够通过与Cloudera的订购协议访问我们的产品。我们将为开发人员和试用版提供免费（不受支持的）订阅协议，我们将为商业客户支付订阅费用。订阅协议将涵盖支持和维护条款，以及对最新更新和安全补丁的访问。通过这种方式，我们将使Cloudera的开源战略尽可能与红帽开发的市场领先的开源战略保持一致，并被全球数千家企业所接受。
5. 我们计划为所有正在发布的新版本制定许可证更改，包括HDP，CDH和即将推出的Cloudera数据平台（“CDP”）。通过这种方式，无论客户计划使用哪种平台版本，我们都可以平等对待客户。我们计划在所有版本和版本中进行软件分发更改。

从2019年9月开始，我们将推出更新的订阅协议和软件分发模型。 从2019年9月到2020年1月，我们将为以前封闭的源组件建立新的开源项目，并根据AGPL开始许可。

您可以通过这个方便的常见问题解答了解有关我们计划详情的更多信息：https：//www.cloudera.com/products/faq.html

Charles Zedlewski和Arun Murthy

 

===========原文如下==========

Our Commitment to Open Source Software

July 10, 2019 By Charles Zedlewski & Arun MurthyNo Comments

Categories: Cloudera News General

Open source has been core to the missions of both Hortonworks and Cloudera and central to our values and culture.  With more than 700 engineers in the new Cloudera, our company writes a prodigious amount of open source code each year that’s contributed to more than 30 different open source projects.   We’re also a very innovative open source company, having collectively launched more than a dozen new open source projects since the founding of the two companies. 

Prior to the merger, the two companies distributed their products under somewhat different open source licensing models.  Aligning the two models was one of the last items on our merger to-do list. Meanwhile over the past few years, we’ve seen many of our industry peers revise their open source licensing strategies and/or their relationship with the Apache Software Foundation, generating questions of if we’re planning to revise our approach as well.

In this blog post, we are sharing our new open source licensing model, which aligns the licensing models previously used by each of Hortonworks and Cloudera and also introduces some new changes.  We take our open source leadership role seriously, and recognize that our need to align our own licenses is also an opportunity to lead and to renew our commitment to open source software.

Aligning our open source licensing strategy and business model was a community process as well.  We consulted with our customers, industry experts, lawyers, peer companies and employees before finalizing our path forward.  These discussions reinforced many of our open source goals:

1. Freedom from vendor lock-in.  Customers are entrusting their most valuable asset (their data) to our data management platform. They want to pay their platform vendor for added value, not out of fear of the cost of switching.
2. Community standards, not Cloudera standards.  Cloudera has developed many open source projects that have gone on to become industry standards, but no one company can be the sole source of innovation.  By investing in open source projects such as Spark, Kubernetes and Kafka, we keep our customers on a sustainable long-term architecture vs. pulling them onto an island of Cloudera-only developed tools.
3. Open ecosystem.  Our platform is open to a wide range of tools, application and infrastructure providers.  We maintain open, backward-compatible API’s for our partner ecosystem and do so even when the ecosystem competes with part of our product.

Taking these goals into account, we’ve arrived at a new, aligned open source licensing model that we plan to roll out in the coming months.  Our updated open source licensing model will be:

1. Over the course of the next 6 months, we plan to consolidate and transition the small number of projects currently licensed by Cloudera under closed source licenses to open source licenses.  For example, components such as Cloudera Manager, Cloudera Navigator, and Cloudera Data Science Workbench will all eventually be available under an open source license.
2. All of our open source licenses will adhere to one of two OSI approved licenses: the Apache License, Version 2, or the GNU Affero General Public License, Version 3 (“AGPL”).  We considered a modified open source license, but determined that it was important that we use community-accepted licenses.
3. All of the open source projects that we contribute to that are hosted by the Apache Software Foundation (“ASF”) will continue to be ASF governed projects.   Furthermore, we will continue to contribute our enhancements and fixes to those projects upstream first, as both companies have since their founding.
4. Customers and developers will be able to access our products with a subscription agreement with Cloudera.  We will have free (unsupported) subscription agreements for developers and for trials, and we will have paid subscriptions for commercial customers.  The subscription agreement will cover the terms of support and maintenance, as well as access to the latest updates and security patches. In this way, we will align Cloudera’s open source strategy as closely as possible with the market leading open source strategy developed by Red Hat and accepted globally by thousands of businesses .
5. We plan to enact the license changes for all new releases moving forward including HDP, CDH and the upcoming Cloudera Data Platform (“CDP”).  In this way, we can treat customers equally regardless of which platform version they plan to use. We plan to make the software distribution changes across all releases and versions.

Starting in September 2019, we’ll roll out our updated subscription agreement and software distribution model.  Between September 2019 and January 2020, we’ll establish the new open source projects for formerly closed source components and begin licensing them under the AGPL.

You can learn more about the details of our plans with this handy FAQ: https://www.cloudera.com/products/faq.html

Charles Zedlewski & Arun Murthy

 

相关信息：

1. Our Commitment to Open Source Software
2. Cloudera Reports First Quarter Fiscal Year 2020 Financial Results