An event for the Elastic community that must be officially announced:

www.elastic.co/cn/blog/lic…

The core translation is as follows:

1. Shay Banon, CEO of Elastic

The title translates as: Double open.

Extended significance: CEO personally signed the document, of course, is an important event, and extraordinary event!

2. What is the core context of A CEO’s document?

For the public, think of it as the transcript of a press conference:

  • Part one: Tell the conclusion directly that we have made a protocol change.
  • Part 2: Elastic origin and the Beginning of Open Source.
  • Part three: enumerate what we have done (trinity) and achievements.
  • Part FOUR: Why modify the agreement?
  • Part V: Subsequent version and development plan of the agreement.
  • Part VI: Forward-looking statements regarding risks and Uncertainties.

What is the original Elasticsearch and Kibana protocol?

Apache 2.0 – licensed.

Apache Licence is a protocol used by Apache, a non-profit open source organization. This protocol is similar to BSD in that it encourages code sharing and respect for the copyright of the original author, and also allows code to be modified and redistributed (as open source or commercial software). The conditions to be met are similar to those for BSD:

  • You need to give the user of your code an Apache Licence.
  • If you change the code, you need to explain it in the modified file.
  • In extended code (modified and derived from source code) it is necessary to carry the agreements, trademarks, patent claims, and other instructions specified by the original author in the original code.
  • If the product to be released contains a Notice file, the Apache Licence must be included in the Notice file. You may add your own license to the Notice, but this should not be construed as a change to the Apache Licence.
  • Apache Licence is also a business-friendly license. Users can also modify the code as needed and distribute/sell it as an open source or commercial product.

4. What will Elasticsearch and Kibana protocols be changed?

Server Side Public License (SSPL) and Elastic License

SSPL is a new open source protocol launched by MongoDB in October 2018.

The SSPL builds on the spirit of the AGPL, but clarifies the conditions under which open source software is offered as a service. SSPL retains the same rights that the open source community has to use MongoDB under AGPL: the freedom to use, review, modify, and redistribute software.

The only substantial change was the addition of an explicit condition that any organisation attempting to exploit MongoDB as a service would have to open up the source code of the software used to provide such a service.

Please refer to the official website for details of SSPL:

www.mongodb.com/licensing/s…

Why did Mongo DB create its own protocol?

When MongoDB launched the new open source protocol SSPL, the main purpose was to limit the use of cloud service providers such as Alibaba, Tencent and Yandex. The CEO of MongoDB said by name: “Once an open source project becomes high-profile or popular, it’s easy for cloud providers to grab all the value and give nothing back to the open source community.”

5. Why did Elastic switch to open source?

The official Elastic translation reads as follows:

Over the past three years, the market has evolved and the community has come to realize that open source companies need to better protect their software in order to maintain high levels of investment and innovation. With the shift to a SaaS delivery model, some cloud service providers have taken advantage of open source products by offering them as services without giving back. This diverts money that should be reinvested in the product and hurts users and communities.

Similar to our open source counterparts, we have experienced this firsthand, from trademark abuse to attempts to completely undermine the community through “open” repackaging of OSS products and even taking “inspiration” from our proprietary code. Although each open source company has taken a slightly different approach to this problem, they have generally modified the open source license to protect their investment in free software, while trying to maintain the principles of openness, transparency, and collaboration. Again, it was natural for us to take the next step, which was to make targeted changes to how we license our source code. This change will not affect the vast majority of our users, but will limit cloud services that offer our software as a service.

There may be some future attempts by some of our competitors to promote various FUDs around this change, but let me be clear to any naysayers: we believe deeply in the principle of free and open products and transparency with the community. Our track record demonstrates this commitment, and we will continue to build on it.

Explanation of FUD (more transparent for all) :

FUD — In plain English: speak ill of (my understanding). Fear, Uncertainty, and Doubt lead to Uncertainty. It was originally said by Gene Amdahl, a former IBM engineer who left IBM to start the Amdahl Corporation as a competitor to IBM, FUD originally referred to IBM salespeople instilling negative beliefs about The products of Amdahl and other competing companies into customers’ heads so they would believe whatever you told them. This marketing ploy is often used in the computer industry, especially when Microsoft tries to convince its customers that Linux and other open source software are bad for them.

Highlight: What do some mean?

  • Contains, but is not limited to: AWS Open Distro for Elasticsearch.

The first release of Open Distro for Elasticsearch in March 2019 announces: Will bring some advanced features to complement Elasticsearch, including:

  • Transmission encryption
  • User authentication
  • Detailed audit
  • Role-based fine-grained access control
  • Event monitoring and alerts
  • Depth performance analysis
  • SQL support.

6. Does it affect ordinary developers and small and medium-sized companies?

Official note:

This change in source code licensing has no impact on the overwhelming majority of our user community who use our default distribution for free. It also has no impact on our cloud customers or self-managed software customers.

This change in the source license has no impact on the vast majority of our community of users who use our default distribution for free. It also has no impact on our cloud customers or self-managed software customers.

To extend: Ali Cloud and Tencent cloud customers naturally have no impact, Ali Cloud and Tencent cloud are established cooperation with the authorities.

The Mongo DB issue also applies to Elasticsearch and Kibana.

7, summary

Such a big matter, must be subject to the official English document!

I’m not making a point, but the two words “open up” on the Elastic website are persuasive.

As for the modification of the agreement, welcome to leave a message and exchange your views.

reference

www.elastic.co/cn/blog/lic…

Cloud.tencent.com/developer/a…

www.v2ex.com/t/630841

www.elecfans.com/d/801792.ht…

www.infoq.cn/article/TL_…

Baike.baidu.com/item/FUD/19…

Medcl teacher, Wei Bin teacher, Ruan Yiming teacher friend circle discussion

China’s largest unofficial Elastic public account \

Elastic6 + Elastic6 + ELAStic6 + ELAStic6 + ELAStic6 + ELAStic6 + ELAStic6 + Elastic6 + Elastic6