On June 5, 2021, the 2021 China Developer Ecosystem Summit hosted by SegmentFault came to a successful conclusion. At the meeting, Wu Sheng, Director of Apache Software Foundation, Founding Engineer of Tetrate. IO, and Founder of Apache Skywalking, delivered a speech entitled “Skywalking and those things about Apache Software Foundation”.

Wu Sheng, Director of Apache Software Foundation, Founding Engineer of Tetrate. IO, Founder of Apache Skywalking

Sort and publish shorthand: SegmentFault Editorial Department

I’m going to talk a little bit more lightly, and we’re going to talk a little bit about what’s happened to the whole Skywalking project from 2015 to the present six or seven years ago, and some of the choices we’ve made along the way. I’m from a North American company called TetRate, which is a Service mesh company. I myself am a director of the Apache Foundation and the founder of Apache Skywalking.

Skywalking is actually Apache’s top project right now, and is probably the largest open source APM system in the world right now. If you are familiar with the monitoring and application performance management field, since 2000 or 1998, there has never been a single piece of software in this field that was built entirely on the open source ecosystem or with an open source background. All of the world-famous APM software has a commercial background. So Skywalking didn’t start out as complex as it seems to be today, it was really designed to solve very simple problems, and open source and the open source community pushed it to where it is today. Today’s Skywalking is actually very, very complex. It involves people monitoring what you see in logs, metrics, distributed tracking, event detection, and all kinds of everyday operating systems, containers, and some of the architecture on the front end. Some people are even expanding the stack of technologies including mobile, WeChat applets and so on, to look at metrics and performance data and perspective performance across platforms, so it’s a very, very large state.

You’ll also find plenty of technology stacks, including ecosystems like Prometheus, Openelemetry, Zipkin, FileBeat, Fluentd, and many other global vendors. We don’t do everything ourselves from day one, we work with many, many manufacturers and foundations around the world, and that’s how it’s come to this. We have a lot of friends, from other manufacturers around the world, to give us relevant support, to make things more convenient for everyone to integrate, use is also in line with everyone’s habits. This is a picture I recently captured from the system. The project was open source at the end of 2015, and it had a very long stable period, with few people participating in the project. In 2017 and 18, there were very few contributors to the project. When we joined the Apache Foundation at the end of 2017, there were only more than 20 contributors to the project, including me. Today, the not-so-complete count is close to 500 code contributors, and it doesn’t include documentation, or any other publicity.

No matter which company Skywalking is, there has never been a so-called position called community operation. We rely on the developers themselves, or relying on the project, relying on our understanding of open source ecology, to cooperate with everyone, to cooperate with other projects around the world to complete the incubation and expansion of the project. Here’s what we found on the Apache website on Skywalking around the world.

Not surprisingly, for all Apache projects, including the Apache website, China is definitely the dominant traffic. China is certainly the largest user of open source projects at any foundation, but at least we are not yet the largest contributor to these projects. We haven’t been a major contributor to Skywalking, to the Apache Foundation as a whole, to the CNCF, to the Linux Foundation, to every global foundation you can think of. But you will see that the projects that are incubated in China are the ones that once even code comments were written in Chinese. If you’re really willing to go global, and you’re willing to go global in a reasonable way, then you can also get global users, and you can see a very, very large global audience except for some places that are disconnected or in Africa where there’s almost no IT industry. And Skywalking has different manufacturers in China, North America, India, East Asia, Eastern Europe and Western Europe, based on Skywalking to engage in the construction of their commercial products, such as manufacturers in the UK, Poland, South America developers, they are doing their own commercial things, Including my own company in North America. If you use a reasonable way run open source, you can do some suitable for their own thinking, if your project is not the sort of exclusivity, you can actually some imaginary space is very, very big, just like what we see today, we often said in the Linux operating system, all of its economic benefits of Linux is not all people go to earn, It’s getting more industry-level support, more enterprise, more different directions, but it’s getting a positive industry cycle out of the middle of things, so I want to share this with you, and you’ll see that there are 15,000 sessions a month visiting our system, and the actual traffic is harder to calculate, This is because all metrics are recorded at the session level. Back in the first 15 years, we were talking about what a good open source project would look like. All open source projects, if it’s just for open source, or if you do open source thinking, it’s very hard to succeed. The same goes for Skywalking. If it’s just about solving problems, what’s the problem?

In 10 to 15 years, you should start from the original Dubbo ecosystem, from the SpringCloud ecosystem, from ESB SOA, all of the applications will move from monolithic applications to integrated applications. So what kind of problems did we have in those years? We when I am in a project to do for China unicom, we encounter problems is eight manufacturer to work on a project, you can imagine how much this state of disaster, all people are accused of others system instability caused by the whole distribution system is not stable, as you now within the group to group accused the other of program to write is not good, this is the same. But when you become eight factories, communication will be more difficult, because you have the boss in the company can take out clappers, now you have no chance to even the clappers, so at that time, when doing the SkyWalking, developers are all received a training, we let you know, when your distribution system problems may not be the problem of your code, Your upstream, downstream, network, and intermediate ESB components have to be any one of them.

So Skywalking was originally designed to solve such a simple problem. There were already two famous open source projects, Zipkin and Pinpoint, so why did we decide to start from scratch? The Zipkin is still around, you can go and see it, first of all it’s very simple, it’s not designed to be a complex system. It’s designed for simple functionality, which means it’s really going to be what we’re doing right now, it’s a demo, not something that can be mass-produced. Pinpoint was the product of Naver, a search engine company in South Korea, and it used big data that was hot at the time. No use reason is actually very simple, today we have a lot of reasons to target Pinpoint and SkyWalking, but as a monitoring product, if you use big data, then, you may be more difficult than the target business system stability. Since HBase is a highly distributed system, do you use a distributed system to monitor which other distributed systems crush first? The monitoring system is the first to crush. We didn’t want to do world class APM, we thought at least we could solve the current problem, so we wrote a very, very simple version of Skywalking, you can go to the original 1.0 code on GitHub now, very, very simple, and even back then we tried to use HBase, Let’s see how it works, how many problems do we have if we do it in their model? So, Skywalking was a testing project for a long time. We were hanging around on GitHub without any publicity, without any external contact, just putting code on it.

Even back then, the License was GPLv3 for a while. In terms of our consciousness, we were not ready to play it as a community, we thought more, anyway, I put a project, and it has a certain protective effect, put GPLv3, we found that it took two and a half years to go from the earliest V1 to 3.2.6. Skywalking is a testing project all the time. It does not have any KPIs, it does not complete any specified functional areas, it is just people who participate in the project to solve daily problems, to contribute code, write whatever can be written, to complete whatever features can be completed, more entertainment work. Or it’s a test, it’s not a test of technology, it’s a test of ideas that you have in your head, to see if they fall off the ground. Why 3.2.6 is 3.2.6, because it is the last version of 3.0. And 3.2.6 is the first time I stand on the stage, in the GOPS global operations and maintenance conference, I stand on the stage for the first time to speak: there is such a project, what functions it wants to complete, what problems it can help you solve, it is Apache 2.0 open source project. For the first time, we saw it as a true open source project and allowed ourselves to see it as a true open source participant. And when open source comes out, you actually find that, for example, you start to get a lot more users, but the feedback is more like, oh, you’re not ready, you can’t do this.

Because it’s very, very difficult to go online as a monitoring system. It is very difficult for a user to put his own life on the unstable monitoring system, and all his data are from this monitoring system. Although you do not carry any business data, if you hack it, the whole production system of the user will be hacked, which is very dangerous. Skywalking has not been available in production for a very long time, including 3.2.6. In fact, it has not been running in a full production environment, more often in just-in-time production and test environments, or in a compressed environment. It is used more as a tool than as an APM platform. At the beginning we wanted to expand the community, and we had two options, Apache or CNCF. I had already worked in Huawei at that time, so theoretically, CNCF was available. If you are not familiar with the difference between Foundation, in fact, CNCF will be more manufacturer-driven with a stronger commercial flavor. He needs the manufacturer to intervene, he needs the manufacturer to contribute money or manpower to guarantee. Skywalking was a personal project, and it was not born in Huawei, because we did it in our spare time. It did not assign IP to any company from the beginning to the end. Naturally, there was no way to simply transfer IP to the so-called Huawei and let Huawei follow the path of CNCF.

If you search the proposal of the new CNCF project, you will actually find Skywalking, because we have applied for it before, and Kris, the COO of CNCF, actually invited us to make a presentation, but we didn’t choose to go through a long process in the end. Because I’m too busy. And for the project, at the time, we were more concerned about getting more people involved in the project. Whether or not there are so many people promoting the project is not that important to us, because throughout, it is not a KPI project, because no one evaluates it. Even if we were in Huawei at that time, it was not an appraisal system, which had no direct relationship with the company. It doesn’t mean how many contributors you need, or how many STAR companies you need to evaluate you, and only today can we get bonus. This has never had much to do with Skywalking, and there is a very convenient reason why we choose Apache because it needs mentors, which will be discussed later. It happens that my friends around me, one is in Australia, one is in Huawei and one is in Shanghai. We were able to quickly find three Apache members to become Skywalking mentors into the Apache Incubator. We made an adjustment from GPLv3 to Apache before entering the Apache Incubator.

There are actually two reasons for the change. This reason was not triggered by Apache, but came from Ali. Ali’s team contacted us and said that they wanted to cooperate with us to build part of the function.

In those early days, it was very rare for a big thing to happen to a developer. But they said there is concern this thing you GPL, or I will report not in the company in the past, actually was a very simple reason, we think there are more people to participate in, as long as it doesn’t matter if it is GLPv3, who can give it the commercialization of the best, who can take it to make money, we are standing in the Angle of the fair on this matter.

We made a quick decision in the community to change GPLv3 to Apache v2. If we look at it from a more rigorous level today, what V2 actually gives you is a better opportunity to do commercial distribution, for example, more products including Skywalking to do secondary public release, You see a lot of private cloud platforms today, and a lot of products that contain a full or secondary distribution of Skywalking natively. This is very common, and you’ve probably seen some or all of it on many, many open source projects, and it’s a good foundation for doing cross-organizational collaboration in the future.

But when we really stepped into Foundation, we found that there was a very big gap. For a long time, open source was entertainment for me. But when I brought the project to Apache, I became more of a professional open source developer. At the same time you find yourself in a different role. When I speak on behalf of Apache, when I say anything in Apache, it’s not a business, it’s about the quality of the software project itself, it’s about safety, it’s about iterative future development. Maybe I have a way of making money in my mind. But that can’t be at the project level. So what you find later on is that you have all kinds of constraints, and that’s what the Foundation does, it gives you a very good name, it thinks you’re famous, you’re an Apache Foundation project, but it also gives you more constraints, Branding You can only use your own branding on the Apache Foundation, but you can’t use this famous trademark indefinitely without editing it, because the Apache Foundation doesn’t want to handle it.

The Apache Foundation has more than 350 click projects. Almost every piece of software you use around the world has to come from the Apache Software Foundation. But at the same time, the Apache Software Foundation costs less than 1.6 million dollars a year to run, and almost none of that money goes to the members of the Apache Software Foundation in the form of salaries, all of them working with some logic, you do some project, maybe it’s a hobby, maybe it’s writing a book, training, You have your own logic, which makes your activities in the foundation profitable.

Of course, do you have a hobby? Will be.

But the interests of the participants, he must be a relatively low intensity, such as his time is very difficult to for more than five hours a week, because is the equivalent of more than five hours he will waste the time of day, and this is impossible, for the vast majority of people especially many people was going to six days in class, five hours, it is unlikely. And what about the vast majority of volunteer contributors we see in China? Although he got off work late, he was interested in this issue and felt that he had something to contribute. Therefore, in the emails submitted by Skywalking, people often found pull requests at 2 o ‘clock and 3 o ‘clock in the morning. This is called hobby. If you were facing a pro developer, he would never do that, Skywalking has a lot of pro developers, and the pro developers we see at night must be from the US, South America, Argentina, Brazil, because they are working normal hours at night. This is a pro. Different people should know that they have different preferences. You know foundation has 22 years old, was first made in 98 in 99, the foundation is relatively old things you think are the foundation of, things will slowly, discussed because it is asynchronous, everyone by email all things have to wait for 72 hours, because it is in order to let all the people in the world can see and be around at the weekend, It becomes three days. Any resolution, any small thing, as long as it goes up to the resolution level, is an extremely long time to wait.

There are a lot of things about the foundation that you’re not used to. We talk about the Apache Foundation all the time. So what is the Apache Foundation? Here is actually Apache official explanation, for these three words inside everyone has their own explanation.

Some people explain business logic, some people explain from the perspective of the pursuit of fame and interests, some people love software development and coding, some people have the idea of helping others, some people want to reduce the burden of others, many, many, everyone’s idea is different.

Foundations are diversified, and their starting points are different. Don’t use your own starting point to speculate about why the other party wants to do this. His explanation may completely surprise you. Because some people are really doing it for their hobby, for example, we’ve seen some young engineers in some parts of Eastern Europe, 16, 17 years old, who are going to work on projects for their vision of starting a business after they are 20 years old, to work for years on a feature that may not be used by two people for a very long time. Skywalking has a subproject developed by the Eastern Europeans that takes all of your monitoring data and feeds it back into the IDE, and when you see the code, it tells you what the system metrics look like in the production environment, and this thing doesn’t have any commercial scenarios at the moment. But he’s been doing this for almost two years, and he’s young, and he’s probably taking a long view, and he thinks it’s going to help him in the future, whether it’s starting this business, or using this energy to prepare for his own business. For professional developers like me, I don’t think this is a good deal. My time should not be spent on something that has no commercial benefit, is long term, is highly complex, and has a lot of code.

This is just a simple example of how you should stay relatively humble and ask questions when you get involved. It’s important to know that when someone asks you a question, he doesn’t necessarily disagree with you, he just wants you to be more truthful about the situation. We also saw several local Chinese projects donate to the Apache incubator this year, and we found a lot of problems. Questions often understand the environment of a question in Chinese, because China is the habit of all of our things are first discuss good, when I send out of something publicly, is on behalf of the resolution has been formed, nobody will say in public to a word in English, is it, it translated into Chinese is basically the concept of an argument. In the whole cultural environment, you need to be able to have a certain tolerance, when you cooperate with people who are not from your own culture, how do you hold on. So just say the diversified things, it guarantees is also diversified state, it all efforts to ensure that the manufacturers, for example, your project can not be controlled by a single manufacturer for, especially the top projects, it is, after all, diverse, regardless of gender, regional, skin color, age, if every way diverse, its code to be trusted, No malicious program can be buried in it on purpose. For example, we can see that some projects in China are collecting deployment information from users when they are using the open source version. He had to know this project in how many points customers online open source users deployed, if it is a by-product of business contract, I think there is no problem, but if you also in charge to open source users information, that is, in fact, very dangerous thing, this kind of situation in some countries, in some places, it even suspected of illegal, because you in to steal the user privacy data. Security is more about the security that is available to the code itself, which means that once the code is delivered to you, I can’t undo it. In addition, there is security, because it opens the source code and opens all the copyright to you, you can repair the security loopholes faster, and even make patch by yourself, which is also very common.

Well, community over code actually, as Jun Ping said this morning, everybody talks about it when they talk about Apache culture. Everyone will have different understanding of this sentence, but in the end, we must agree on one thing: people are the most important.

So how do you make the project really transparent, so that people are willing to take the time to participate in the project, and it’s good for people to trust you or trust the project. A simple conclusion: If you want to be an Envoy between ASF and CNCF, you need to do business marketing quickly. There is no emotional color here. (We do CNCF ourselves. Not that ASF is better than CNCF, at least from my personal perspective, I don’t see any comparison between the two. It’s a completely different operating model. You need to make the normal choice, but you should know where the difference is, ASF must not be the benefit first, it must be the developer first, how to unite is the most important, and CNCF is the interests of the manufacturer above everything.

In the project of CNCF, it requires diversity as well as diversity. It requires at least three manufacturers to participate. It does not require that you need developers from many places, but it cares about which company you are. Therefore, when signing CLA with CNCF, you should say which company you are from. The email address you signed is basically the email address of the company, and the company should sign CCLA together with the affiliated ones.

After selecting the foundation, we will actually have a long-term process of running the project. Of course, there are many stories, many pains or successful experiences, but we have compared a lot, because I have also participated in many open source projects in China. From Apache projects such as Echarts, ShardingSphere, Apisix, DolphinScheduler, or CNCF projects including Opentracing and Zipkin, I have actually been involved in these projects. What we can see, whether in China or abroad, is that as a project leader or a member of the core team of a project, you need to make sure that you can do these things. Although you may not succeed in doing so, if you fail to do so, you will do great harm to your project and your community. Open is an easy word to say, but how can you trust the decisions of other key people when they don’t come from your company and share your business interests? And how do you choose people you can trust?

I believe it works both ways. The more you trust him, the more iterative speed he brings to you, the more characteristic power he brings to you, the more he goes deeper and deeper. If you have everything in your hands, then your time commitment is probably the limit of the project. I probably didn’t write more than 80% of Skywalking’s code right now. I don’t know the details, but I always follow the documentation when people ask me, because I don’t know what they’re going to change the project to. I know what it looks like in general, I know what the data flow looks like, but that’s the limit, and that’s in my case as a professional developer. If you’re not 100 percent full-time, you probably understand even less.

Remote mode in fact disguised said be asynchronous mode, the many engineers in China is always in my heart the pain, you find no one bird you asked the problem, someone else to answer you, have a few hours in the past, Chinese engineers like sentences when asked another way, this line not line, do what, not what, here are personal back no, ok, The day passed. This is not nonsense, you need to master some of the most basic skills of remote work. And when you work like me, because my own company is in the United States, we have engineers from downtown Japan in New Zealand in the far east to downtown Massey in the far west, more than five engineers in almost every city. All of our company’s products are done asynchronously, and we have almost no company-level synchronous meetings.

This is the situation that we face on a daily basis. You think about running the Open Source Community in a company. You have to know these things, or the company won’t do the work. When we do a Google Docs review, they hand you a Google Docs. Some of you agree with it, some disagree with it, some want to improve it, or if you think the other person is wrong from the beginning, how do you express your wishes in words as clearly as possible, which is actually the meaning of remote mode.

We saw a lot of funny things in China during the epidemic last year. Everyone is forced to work from home, constantly checking progress, constantly synchronizing progress, and the leader wants to know if you have gone out and wandered. Companies like us, we will lead at ten o ‘clock in the morning, send you an email to apply for, I will give you a line in an hour, no, I can answer say no, I go down to play with children for a while now, or we meet again when in the evening, or you send me a mail tell me in words, is worried about something? If you are in a hurry, please wait for me for two hours and we can talk at 1pm. The whole culture is top-down. The engineer below me can also talk to me like this. He says that I am not free now, but I am taking care of my child or picking up my wife. He replied that I was picking up my daughter-in-law, and I said I’d talk about it then, and I’d go fill in an email to him.

If you’re going to do that with Open Source, you’ve got to be comfortable with it, and you’ve got to learn how to make people work at high speed. Because the biggest problem with Chinese WeChat culture, QQ culture and real-time communication culture is that the people contacted are constantly interrupted. People think they’re running at their best, but they’re not running at their best, because people are constantly being interrupted. This model, you have to understand, you have to really accept, you have to be able to live in the state, you can integrate with the global community. Skywalking has a Node.js and Python probe, both of which come from an Eastern European company’s engineers in South America. We can only communicate with them for an hour, from 9pm to 10pm. If this thing needs to be communicated in real time, it has to be done within that hour. But there’s a good chance he’s not online, or I’m not online, and everything is done online. I still don’t know what the engineer looked like. I didn’t do a video conference. Everything was just text. When you need to write with others, you need to know the state of others’ expectation of you, because he does not want to be dragged by you, because you are not his leader, and you do not pay him the salary, why do you have to drag him every day, is not to contribute a line of code? Does that make sense? This is the real problem you’re trying to solve when you’re doing Remote.

And what are the more below called? We most of the time in the community called goodwill dictatorship, you try to understand all things, all of your code must conform to your habit, are you going to make their own decisions, or there is a small group to make decisions, or any other similar things, this is very hurtful, when everybody experienced a later decided to no longer ignore you, Because you don’t bring anyone else with you when you make decisions. This is different. I held a public meeting and a public mailing list, but you gave me no feedback, so I did this. It is totally different from the feeling of informing you after I made a decision offline. You can skip it, you can pass it by default, you can ignore it, you can challenge it later, and at least you give the person the opportunity to go back and know why you made the decision. Often it’s not the decision itself that people object to, it’s the list of decisions that people object to. Your business is not open, you did not say that I am going to do this today, because of ABCD and other reasons, this is everyone should pay attention to.

Last but not least, the most difficult thing for Chinese people to do is to disagree with you. This is the most difficult problem for Chinese engineers to solve. There is an expression in English that says “agree to disagree.” It means that people can do things according to their demands. There are some directions that they can explore first. It is not always necessary to vote unanimously on a show of hands when a decision is made, and absentee voting is common.

Whether or not you can do this in doing this, and whether or not you can tolerate it as a leader of the community is very important. And can your software technology survive in this environment? For example, if a wave of groups pass a relatively bad solution, will it cause a devastating blow to your entire ecosystem? Maybe the function of your next version will be completely useless. Whether your automated tests, chaotic tests, stress tests, fully automated tests can ensure that things do not happen, can be in the early stage through theoretical proof, data proof, experimental tests can be concluded that you are not good, I am against you this matter is based on data. Instead of saying my experience is not good, your experience is not good, the Chinese people like to say: our company has so much traffic, you do not, so this is not good. If you’re in open source, no one will talk to you about technical solutions, because you don’t take what others say seriously. Maybe it’s true that traffic is bad at 10 million, but it’s good at 100,000. Many systems are like that. You have to understand how many people are facing 10 million traffic. Just like before, we represent a lot of Singles’ Day schemes in the chat, but how many companies need Singles’ Day? There are very few companies like Ali’s. Your plan is very complicated, but does it work? This is a serious problem.

So this is the incubation process, and I’m not going to go into the details, but if you’re interested in Apache incubation, the key thing is that you have to find three mentors, in a nutshell, the incubator, the foundation, these are social games, you can find people, you can persuade them, you can persuade them with money, you can persuade them with people, you can do it yourself, Whatever it is, it’s social. If you can handle it, you can do it. So at the Apache Foundation, you have a lot of levels, but it’s just a level. Just because someone is at any level doesn’t mean you have more rights than anyone else, it’s often more obligations. The higher you go, the more work you have to do. The only difference from a contributer to a communitier is that you can submit your code directly to a repository. But a lot of mainstream open source software, like myself, can’t submit code directly to Skywalking right now. If we didn’t go through another PMC or review, my code wouldn’t get in.

The following content is a list of common issues that we want you to know about in the Open Source environment in China. This is the biggest pain I’ve experienced in the open source community in my many years on both sides. The Chinese developers have incredibly high requirements for the maintainer of open source projects, and the customer’s requirements are not as high as ours.

For example, Chinese developers say that the documentation is not good and the source code is given to you. Do you care if I write well? You can use it if you want, you can use it if you don’t want. I didn’t charge you. If the project is very early on and you want to go to some seed developer, you’re betting against them, you’re betting that their project is going to work, and they’re betting that you’re going to take their project. But as the project matures, this doesn’t happen. If you look at all the top projects of Apache native to China, I can safely say that Skywalking must be the worst in terms of community environment and attitude in answering questions. Because the most common one is go back and read the documentation, go back and read the code, that’s the answer to most of the questions you ask. Why does this happen? Because it’s not equal, I’m not providing you with a business service, why should I provide an equivalent capability? In other words, Skywalking is looking for developers who can do it themselves. They are the value to the community. If you can contribute a line of code to the community, it’s worth it to spend ten minutes talking to you. If you have a field deployment problem, I don’t care at all, because I have no problems when I deploy. There are a lot of people in the community who say, this is a very urgent thing, there is a problem with production, there is a problem with production what do I have to do with it? Why am I crazy to put so much effort into helping you look at the stack at nine o ‘clock at night? Would it be bad for me to watch a little TV?

Therefore, these are some unrealistic hopes that people often put forward for Chinese projects in logic. Chinese open source software authors complain every day that they are tired because you are spoiling them. Basically, one wants to be spoilt, and the other is willing to be spoilt.

Second, time. What I don’t have time for is that I’m at 996 and I’m at 997 or more. But if you calm down and think about two things, the first thing is, how many workers are actually able to work at 996, 997? Not really. Most nights, we eat, play mobile game, go to the gym downstairs, punch out at the right time, or work at night and come back at twelve in the morning, but we only work eight hours a day. Because normally, why is it that Western IT companies, we say I signed you an eight-hour contract, I don’t want to work today, why? IT engineers write programs, not just because you ask them to work overtime. His brain is not good to write procedures, there are three programmers to help him fill in the blanks, all bugs, it is better not to write. This is especially true in infrastructure software, where the hidden bugs you have buried are so devastating that you can write a program for three minutes and the other side can’t find the bugs for three months. If he is such a person, you can argue that he is not a practitioner of open source software, and I am not saying that such a person does not exist. The open source culture is not about convincing everyone, not telling everyone that open source is hot, so you should open source. Not everyone will pay for it.

As Apache often says, Community Over Code is not suitable for all open source projects, and this is not wrong. Many things that do not follow the Apache Way have been successful. The Linux operating system is typical of the typical. So don’t make it an absolute standard.

Finally, when you’re working on a project, connect to all the resources that are available to you. Engineers, ecosystem players, other project players, and various Global vendors. You need from personal relationships, social skills to your cooperation projects, the same foundation, foundation, another company, or professional players, these professional players will in your publicity and promotion play a decisive role, and that you do some back against commercial manufacturers, they give you professional developers. Which one is needed at different stages, they are not good or bad, money is good or bad, depending on how you use it, how you distribute the structure of the community, every community, every set, has its own subtraction.

In fact, if we look back over the course of six years, we would say: patience. A lot of times when you see Skywalking today, I could just show you the first three pages, and I could say how great Skywalking is. I could do a 30-page PowerPoint presentation about how awesome this project is, how big the deployment is, how big the environment is, and I could talk all afternoon about it, but you have to realize that on day one it’s nothing, and you’re backed by the biggest developer in the world. More than 90% of Skywalking’s functions are done by Chinese engineers, and its users are all over the world. A large number of Chinese engineers write code in open source, which is considered too complex by Western engineers to be possible in an asynchronous environment. However, many Chinese engineers rely on their own ability to complete the work, so I don’t think Chinese engineers lack the ability to open source, but what they lack is correct collaboration methods. There are a lot of things that we’re worried about. Skywalking has a lot of features that were blown out two or three years ago, and we’re only getting results today. I don’t know if you’ve noticed, one of the first slides I wrote, Skywalking today, the 8.5 release last month, We’ve just done what we were talking about five years ago, getting those features into a usable code state, and it’s taken six years, 500 engineers, and tons of testing, and we don’t know how many people around the world have tested this program. Similarly, after finishing what we did six years ago, I will find that what we thought six years ago was the whole landscape, but in the landscape we can see today, we have only completed 50%. We may even need another six years to finish what we think today. This is open source, our Landscape is getting bigger and bigger, and things are getting deeper and deeper. Skywalking went from a Java probe to a full language probe, to a service mesh, and now we have to connect to the operating system, we have to do the database ourselves. We’re going to hook up with other acquisition software, we’re going to hook up with other protocols, and we’re going to see more and more things.

Finally, we will return to the Apachecon event next month and the month after next. Of course, this year, because of the epidemic, we will do it online. The last Apachecon event was held in Las Vegas, and the epidemic started in the 21st year. In the 22nd session, we brought ApacheCon Asia to China for the first time, because after four years of hard work from 17 to 21, China finally had enough Apache members. This will convince the Apache Foundation to hold an ApacheCon that belongs to China and Asia. We also hope that next year, under the better situation of the epidemic, we can get Apache to pass the decision of bringing Apachecon Asia to a Chinese city for the first time to hold some offline activities. Of course, this year has been very good, because 70-80% of the sections of our ApacheCon Asia can be used in Chinese, which is the benefit that ApacheCon Asia brings to us. Because Chinese Apache members covered almost all the track chairs in the whole meeting, they had more right to speak, and we could pass the whole selection of ApacheCon in a better way, which is what we can bring to everyone. In the future, we hope that more engineers can move from Apachecon Asia to Apachecon globally.

This year, the global Apachecon is also in the North American time zone. For the theme of monitoring, basically no matter Chinese engineers or foreign engineers will use the theme of Skywalking. We also hope that more Chinese projects can go out and share more themes in English. Because I have spent a lot of time on the Internet abroad, this is my Twitter, and I will spend more time on it than on the domestic platform. I hope you can talk about open source, Skywalking, or some culture of Foundation. You can find me through Twitter. Thank you very much.