It has always been our goal to lower the barriers to contributor participation.

–, kwok keung

ApacheCon is the official global series of conferences of the Apache Software Foundation (ASF). ApacheCon is one of the most celebrated events in the open source world and one of the early days of the open source movement.

Back in 1998, before the ASF was founded, ApacheCon had attracted participants at all levels to explore the “technologies of tomorrow” in more than 300 Apache projects and their various communities. It was also during this session that the developers of HTTPD services got together and decided to form the Apache Software Foundation.

ApacheCon is held annually in Europe or North America and is a great opportunity for Apache developers to meet, discuss, and share ideas. Demonstrate the latest developments and innovations in the Apache project through hands-on presentations, keynote speeches, real-life case studies, training, hackathons, and more.

This year, in order to better serve the rapidly growing number of Apache users and contributors in Asia Pacific, the ApacheCon Organizing Committee and the Apache Software Foundation are pleased to announce that ApacheCon Asia, the first online conference for Asia Pacific time zones, will be held on August 6, 2021.

In order to give you a better understanding of Open Source and ApacheCon Asia, SegmentFault will interview some Track chairs or conference lecturers to let you know the background of the conference preparation and the stories of these experts.

Today we are presenting an interview with the Apache DolphinScheduler PMC Guo Qiang.

The following is SegmentFault Sifter’s interview with Guo Qiang:

About kwok keung

Hello, I am PMC-Guo Qiang from the Apache DolphinScheduler community.


Guo Qiang first contact with the story of open source

In my first company after graduation, two-dimensional fire. Was set in a brother doing open source related things, he is the PMC Dubbo, few Chinese contributors and Netty list, if you feel like writing code can affect many people, a lot of companies, so also calculate as individuals, to stay a little something of value in this world, and then to participate in the contribution of the open source community. The things I started to do were relatively simple, and I participated in more projects. Later, when I came across the Dolphinscheduler by chance, I felt that the community was very nice and active, so I began to be deeply involved in the Dolphinscheduler.


What have individuals and companies gained from participating in open source and contributing to the Apache community?

Increasing the depth and breadth of personal skills: The average active contributor is an expert in the field, and there are many opportunities to communicate with them when participating in open source. Through them, I can make up for a lot of my knowledge gaps. DolphinScheduler is a framework that is closely integrated with other domains, such as resource management, registry, file storage, monitoring systems, etc. For me, it covers a wide range of domains but also requires expertise as an infrastructure software. In the community, there are specialists in various domains. For example, when we released version 1.3.6 in April, a Committer@haili0 from Skywalking implemented the DolphinScheduler’s link monitoring (Skywalking) for us. I had the opportunity to learn how Skywalking’s plugin was designed and implemented. It was a great experience and learning opportunity for me.

Have lots of friends to talk to: Can mix in an open source community is a group of like-minded people, all because I like a certain technology, like the way open source and worship of the geek culture, so we can very good together and to achieve something, at the same time, because of like-minded, so everyone is easy to become the friend, to me, open source brings me a lot of friends, They are in different companies, in different regions, and in addition to technology, we also talk about life, hobbies, food and so on. I even met my former company colleague Guo Jiwei in the Dolphin community, we didn’t know each other, we just met through open source. Later a ask, you which company ah, I also in this company at that time. Also is really very coincidental, never thought once missed the person will know in this way. He is also a very strong and warm-hearted person, and has been the PMC of many projects. In other words, participating in open source is a unique and effective way to socialize.

Give full play to personal advantages: in a previous interview of teacher Wu Sheng, developers of 40+ are needed in the open source field, as well as young people with more publicity are also needed. It was mentioned that: In our daily project operation, we see many young engineers have energy and enthusiasm, but it is easy for them to go in the wrong direction because they have little experience in the industry and work according to past experience. We don’t know what kind of pit may be waiting for them. But if you have a developer over the age of 40 who can help you figure out what’s wrong with you, you can save yourself a lot of detours. Even if they have a small amount of code, the code quality will be relatively good, and they will be more calm to solve problems, and more able to accept long-term operational projects, like China’s Nth Five-Year Plan. I think this is a position for older programmers.

Skywalking has a contributor born in the 1990s, who is someone who knows he or she has little experience but insists on expressing himself so that he or she can do something that he or she might not have thought of before. For example, he integrated Skywalking into the IDE, so you can see the metrics in the source code, which is a very special idea. That’s the unique value of being young, and it’s something that a 40-year-old developer can’t offer. However, a 40-year-old developer can ensure that your wonderful ideas can be realized in a good and fast way and avoid going off the road. For me, the same is true. One of my ideas can be realized in the community (of course, the premise is a useful idea). I don’t agree, but I support you. It seems contradictory, but in fact, this support leads me to constantly go deep to correct my design, and finally win everyone’s approval. A lot of big designs actually start with a few immature ideas that bump into each other and eventually become perfect. Where is the tall building in the beginning?

This has never been an era of unmet talent, it just depends on how you choose. With open source, you can reveal yourself to the fullest.

Because open source is a place where you can really talk code, collaborate and communicate with people in different languages and countries on the same project, and become who you are. The other thing is that the open source community treats everyone the same, no matter where you’re from, what company you’re from, what degree you’re in, etc. This mechanism allows everyone to truly express themselves. Your contribution to open source is completely open, and anyone can see it, and see how good you are.

Acceptance: Maslow’s theory of needs talks about people’s higher needs, such as the need for respect. Through open source, I have achieved this to the greatest extent. Of course maybe to satisfy my vanity 🙂

No matter what role you play, you need to be recognized. The reason why I first got involved in open source is very simple. I hope that this can be used as a topic for me to talk about. No matter in an interview or chatting with friends, I can confidently say that the open source software you are using has the code written by me. I wanted to be admired by others, just as I had admired my brother then.

Think about the sense of accomplishment when your code runs on tens of thousands of machines and creates a lot of value.

Open source satisfies my vanity to the greatest extent.

What impressed me most was that I received an email from an Indian contributor. I merge his first PR for the Apache Dolphin scheduler. He wrote an email of about a few hundred words, expressing his longing for open source, his thanks to me, and asking for a way for me to contribute in the future. I do such things almost every day, which is nothing to speak of, but his gratitude makes me very satisfied. Helping others is also a very happy thing, and even every thing we do may affect the life trajectory of others in the future, just like what my senior brother did to me.


Guo Qiang’s understanding of “The Apache Way”?

Community Over Code: Community Over Code This is my feelings more deep, code as it is the home I come into contact with a lot of open source projects write very beautiful, but very few can remain active, many projects are just open source code, the project’s early users, but not a good community culture to support the development of the project, so in after a period of time, stopped maintenance project, The Apache community advocates that the community is more important than the code, because with a good community, the code will become better and better. Even if the code is bad at first, through the collaboration of an active community, the bad code will become better and better. Without a good community, the code will rot and eventually die. At the same time, the Apache Foundation believes that contributions to the community, beyond code, bug reports, documentation, testing, blogging, and participation in online and offline activities, are all contributions to the project. For example, contributors to our community are quite diverse, including code contributions, documentation contributions, conference sharing, event organization, and so on. It is because of these contributors that the community continues to thrive.

Meritocracy: Meritocracy is a Committer or PMC role that will be given to anyone who contributes in compliance with the Apache Way and when your contribution is recognized by the community. It’s about giving power to people who actually do the work. Mr. Dai likes to call this earning merit. Your contribution to the community is also the accumulation of people’s recognition and personal influence. I would add that being a PMC or Committer is not the end point at some level. It’s just a title. There’s nothing wrong with being a contribution to a title, but if being a PMC is the end point of your contribution to the project, it doesn’t really mean much. You know exactly what you’ve achieved. PMC is recognition of your contribution, but only for your immediate contribution. The benefits of long term involvement in open source projects are far greater than the title itself. Keeping an eye on it means you have to stay engaged, to see how people are going to use your product, to see how your product is going to be compatible as the technology evolves, and to increase your depth in a particular area.

The reason behind Apache’s success is The Apache Way. Here is a quote from Jim (ASF’s longest-serving director) about InnerSource and The Apache Way. You may take a look.

With Jim Jagielski

At its core, InnerSource applies the “lessons learned” from successful, healthy Open Source projects to guide and direct enterprise IT development. Another way to look at InnerSource is applying the principles and tenets of Open Source development to internal processes and principles. With this in mind, It’s critical for those adopting InnerSource to understand the what and how, but even more importantly the why of those tenets, as well as which particular ones to emulate. We have found that the best model by far are tenets used by the Apache Software Foundation (ASF), collectively termed “The Apache Way.”

In a nutshell, The Apache Way can be condensed into what is the unofficial motto of the ASF: Community Before Code. This does not mean that the code (or the software project) is unimportant, but rather that secure, innovative, enterprise-quality, and healthy code depends on the health and vitality of the community around it. This realization emerged at the origin of the Apache Web Server project and the Apache Group.


Guo Qiang and Apachecon Asia

My TRACK is Workflow/Data Governance, My topic is Apache DolphinScheduler – An Excellent Scheduler Tool for Massive Complicate Tasks, The Apache Dolphinscheduler is a scheduling tool for stable scheduling of a large number of complex tasks. This topic will focus on the stability and ease of use of the Dolphinscheduler. We will also introduce a 2.0- microkernel architecture design, in which components of the DolphinScheduler will be exposed in SPI so that users can quickly implement their own features.

I hope that the audience will be able to join the community of contributors after hearing this, because there was another point in the DolphinScheduler community that I mentioned earlier, which is that there are currently many contributors from other communities. For example, Skywalking, ShardingSphere, Dubbo, etc., the scheduling system is closely integrated with other big data ecology. We hope that through the way of micro-kernel plug-in, experts in various fields can contribute at the lowest cost. It has always been our goal to lower the barriers to contributor participation.


Join us at ApacheCon Asia!

Welcome to ApacheCon Asia!


About the Apache DolphinScheduler

The Apache DolphinScheduler is a powerful distributed workflow scheduling platform for big data with a directed acycled graph (DAG) visual interface, which addresses complex task dependencies and simplifies the choreography of data tasks. It connects many big data ecological components into a data task scheduling system that can handle 100,000 levels in an out-of-the-box, easily scalable manner. More than 300 people have contributed to the project. From China, Germany, India, Australia and beyond, we welcome more students to join the community and build a great open source project together.


About ApacheCon

ApacheCon is the official global conference series of the Apache Software Foundation. Since 1998, ApacheCon has been attracting participants at all levels, exploring “today’s technology of tomorrow” in more than 350 Apache projects and their various communities. In 2020 and 2021, the ApacheCon event will provide a virtual showcase of ubiquitous Apache projects and emerging innovations through conferences, keynote speeches, real-world case studies, community events, and more, all online and free of cost. For more information, please visit http://apachecon.com/ and https://twitter.com/ApacheCon.

About Apache Software Foundation (ASF)

Founded in 1999, the Apache Software Foundation is the largest open source Foundation in the world, managing more than 227 million lines of code and providing more than $20 billion worth of Software to the public, 100% free. ASF’s all-volunteer community has grown from its original 21 founders overseeing The Apache HTTP server to more than 850 individual members and 200 project management committees who work with more than 8,200 submitters through ASF’s “The Apache Way “, Successfully led over 350 Apache projects and initiatives. Apache software is an integral part of almost all end-user computing devices, from laptops to tablets to mobile devices for enterprise and mission-critical applications. The Apache project powers much of the Internet, manages terabytes of data, performs terabit operations, and stores billions of objects in almost every industry. The commercially friendly and relaxed Apache License v2 is an open source industry standard that has helped launch multi-billion dollar companies and benefited countless users around the world. ASF is a US 501(c)(3) non-profit charitable organization funded by individual donations and corporate sponsors, Including Aetna, Alibaba Cloud Computing, Amazon Web Services, Anonymous, Baidu, Bloomberg, Budget Direct, Capital One, Cloudera, Comcast, Confluent, and Didi Chuxing, Facebook, Google, Handshake, Huawei, IBM, Microsoft, Namebase, Pineapple Fund, Red Hat, Reprise Software, Target, Tencent, Union Investment, Verizon Media and Workday. For more information, please visit http://apache.org/ and https://twitter.com/TheASF.

ApacheCon Asia full agenda address: https://www.apachecon.com/aca…

Immediately registered address: https://hopin.com/events/apac…