Apache StreamPark (incubating) is a stream processing application development management framework. The original intention is to make stream processing easier, aiming to easily build and manage stream processing applications, and provide a development framework for writing stream processing applications using Apache Flink and Apache Spark. At the same time, StreamPark provides a stream processing application management platform, and its core capabilities include but are not limited to stream application development, debugging, interactive query, deployment, operation and maintenance, real-time data warehouse, etc. It will be open-sourced under the name of StreamX in April 2021, and will be renamed StreamPark in August 2022. It will then officially become an incubation project of the Apache Open Source Software Foundation through voting in September.
Plagiarized and Infringed
A few days ago, a developer gave us feedback that there was a project that copied the code of StreamPark without declaring copyright. At first we didn't believe it. Given the popularity of the Apache project and the looseness of the Apache open source agreement, generally no project would do this. After all, directly in Just indicate the reference in the code, and the agreement has no restrictions on code distribution. With doubts and puzzles, we found the homepage and code of the Chitu Real-time Computing Platform project on GitHub. It was shocking to find that there were indeed a lot of plagiarism of the Apache StreamPark code, and all references to the code were deleted. The Apache License raised its head and changed the Apache License 2.0 protocol to GPL 3.0 .
Several evidences are listed here to prove this point, and each reader can download the source code for comparison.
Chitu code:
https://github.com/streamxhub/chitu-sdp
StremaPark:
Note: The Chitu code here is forked to our warehouse, not the original warehouse, the original warehouse can be checked by yourself
Facts about copying StreamParm source code
There are a large number of StreamPark project source codes in its flink module. Due to the limited space, only some content comparisons are listed here. Let's look at the common module first, and you can see that the directory structure is as follows:
Then we just open a few files for source code comparison:
After comparison, it is found that the entire common module code comes from StreamPark , but the package name is changed . Then we look at the flink-submit module:
Let's open another source code file for comparison:
The results of the comparison show that, except for the changes in some package names and class names, the source code is basically from StreamPark. Conclusion: More than 80% of the code in the entire chitu-sdp-flink module is copied from StreamPark.
unclaimed source
Software licensed under the Apache Software License allows modification of the code, but the use of the code requires relevant notices. Chitu's development team changed all soft package names, deleted the title of the Apache Software Foundation, and did not retain the LICENSE (license) and NOTICE (notification) files of the Apache Software Foundation and Apache StreamPark when re-released.
In addition, we couldn't find any copyright statement about the use of StreamPark code on the other party's website and official account , and the Chitu team never mentioned that this part of the code came from StreamPark.
Changing the license and reissuing it is not in compliance
Apache StreamPark uses the Apache-2.0 license open source license, and Chitu uses the GPL 3 open source license . If the copied code is redistributed without retaining the Apache License Header , the default is the GPL 3.0 open source license consistent with the project's open source agreement . According to the relevant provisions of the Apache 2.0 License , this is explicitly prohibited, and the Apache 2.0 license cannot be used The code is converted to another license without authorization.
The above facts prove that the Chitu real-time platform violated the Apache 2.0 license and did not respect the intellectual property rights and brands of the Apache Software Foundation and Apache StreamPark.
About Chitu's high-profile announcement of open source
Not only did the team fail to recognize the objective fact of infringement, but instead declared that the project was open-sourced in a high-profile manner, completely treating the open-source agreement as nothing, and not respecting the contributions of others. What is the psychology of the team when they declared open source at such an important conference? Have a reverence for code? Is there any respect for the original author? Are you confident in the glory that was exchanged for doctrine?
The following content is excerpted from the official account of Chitu:
As an open source partner of O*****, Leap Express Group was invited to participate in its open source ecological conference - O**** DevCon held in Beijing on March 25. At that time, **, the senior architect of Leapfrog Express Group, will be an invited guest to share with you "Chitu + O**** Building Real-time Applications", and at the same time announce that the "Chitu" product is open source.
In addition, you can see in its official public account that the team has participated in related technology summits many times and given keynote speeches .
The following content is excerpted from the official account of Chitu:
The Chitu real-time computing platform was officially announced as open source at the O****e Developer Conference on March 25. The open source of Chitu has attracted widespread attention in the industry.
In order to let more developers understand Chitu and empower more enterprise users, Mr. *** will go to Suzhou again on April 1 to participate in the Suzhou GDG "AIGC and Data Science" special sharing session, and further introduce the guests , industry experts, etc. shared the application scenarios and usage methods of the Chitu real-time computing platform, so as to promote the implementation and application of Chitu in enterprises, and expand the industry's brand awareness of Kuaiyun.
In the past two years, I often hear people say that software changes the world, and open source devours software. From national policies to various forms of open source organizations, everyone is encouraged to actively participate in various open source projects. This is good, and the development of open source in China has been soaring. However, issues such as code plagiarism, open source compliance, and intellectual property rights also follow. Whether these related awareness can keep up is a question worth discussing . I believe that StreamPark is neither the first nor the last to be infringed. How developers should protect their legal rights is also a problem we have to face . I don’t know what do you think about this behavior of holding the source code of other people’s projects, removing the statement, modifying the open source agreement, participating in the industry summit, and calling for everyone to actively join?
Our requirement
Apache StreamPark (incubating) was developed from the initial conception to the development, which was exchanged by the sweat of the developers, and the project has also been known to more people through our efforts. With more developers joining, there is A large number of enterprises have used it, and some training schools have released relevant tutorials , which have gradually won the recognition of some industry professionals and some awards. What we never expected is that our project is facing the dilemma of being plagiarized and illegally infringed. We have put forward relevant opinions on this infringement and reserve the right to use legal means to defend our rights :
1. The source code of the copy must comply with the compliance requirements of the Apache-2.0 license , keep the Apache-2.0 License Header, and declare the source
2. Respond publicly and apologize, eliminate the impact, and use open source code in compliance
Finally, we would like to say: As the maintenance team of the project, we know that our strength is small and we have no intention of competing with big companies. We only hope to use our experience to tell you personally and call for the protection of open source agreements and intellectual property rights. Open source is because of love. Birth, technology has become better because of open source. As every technology practitioner, we must stick to the bottom line of open source in order to make the open source world develop better. I hope that there will be fewer such incidents, more original projects, and more sincere contributions, so as not to chill the hearts of developers and ruin my own name.