After solving 2961 user feedback, I made such a change

2961  A question ？ So much ？ you 're right ,Zadig Open source in the past year , On average, there are more than a dozen or dozens of questions every day , In fact, the exact number cannot be known , But a large amount is certain ！ The process of getting along with community partners this year , I have learned the most in my career / The fastest growing year , Want to know my story ？ Then keep looking down ！

Hello, everyone. My name is MinMin, Graduated from UIUC,（ Yes , The one who invented Netscape netscape Browser egg Sen's alma mater ）

Community partners should be familiar with me , you 're right , The following one is under .

Of course, they are often active in GitHub On , From time to time, I will see my reply , This is also me .

Zadig The English version of each release Release Note translate , Or me .

The work is so miscellaneous , It must not be a development engineer , No no no .. Now let me tell you about my R & D experience .

Workplace exploration

That is 2020 Year of 11 month , after 2 After years of career exploration , With pure Golang Engineers join KodeRover The team , At that time, we mainly developed some business modules , At that time, I had a strong interest in cloud native and container technology . Looking back on the past, it was a little ambitious 、 have grandiose aims but puny abilities , But experienced a series of strange experiences , Like the code warehouse import service , Workflow timer 、 The development of trigger reconfiguration and other functions , until 2021 year 7 month Zadig Official open source , My career path began to have some new changes .

Upgrade to play blame

stay Zadig When announcing open source , There are a large number of users flocking , I am mainly responsible for writing the installation script . What I didn't expect was , This function has become a bridge between me and the community . Install as the first step , Directly affect the trial experience , Through analysis , We will divide the installation into several scenarios ：

1. All in One For a scenario with only one host , built-in K8s, Quickly set up Zadig, To experience .
2. Scenarios for official use , Can be based on K8s Environment quick installation Zadig And do persistence .
3. High level usage scenarios , be based on Helm Command to install , You can customize many configuration items .

Although much preparation was made at that time , But after it was released, the community group was still fried , There are still a lot of installation problems caused by environmental specificity , There are many problems in wechat roast Group , Almost all installation problems , To be honest, I was under a lot of pressure at that time , The mentality is also quite flustered , It basically takes 80% Spend more time on wechat groups and GitHub On , Solve installation problems interactively , At the same time, I feel it is difficult to concentrate on the design and implementation of larger functional modules . I kind of wanted to flinch , I thought that this kind of time allocation is not conducive to the improvement of personal development ability .

Period borrowing 1on1 Communication and Landy Ditch through this concern , She said something to me “ Writing code is very important , It is more important for products to be used stably , The ability to solve problems is more important for an engineer than writing a few lines of code , Of course, you can choose to go back to the product ”.

I bit my teeth , Decided to turn the mountain over ...

stay 100% The second version immediately after open source （v1.3.0）, We decided to spend a lot of energy on the second round of in-depth optimization of installation ease of use , immediately ：

1. A large number of cloud resources have been applied for measurement ：All in One The script passed nearly 50 Host test , be based on K8s The script of has also passed Tencent 、 Ali 、 Huawei 、AWS etc. 23 A public cloud K8s Version and self built standard K8s、 Mirror warehouse 、 Object stores measured .
2. Full test , Be the first user ： We admire "Eat own dog food", every last Zadig The developer is also a user . For compatibility testing , We have organized two installation experience meetings internally , The whole staff tested in the small black room .

Hence the Compatibility list . Follow up on this ability , I also did image slimming 、 built-in Regsitry、 The script is further shortened , Realized 10 It can be installed and experienced in minutes Zadig. today , install Zadig It has become a so easy It's something , The problem of community roast group is also getting higher and deeper .

The slope of Enlightenment

Think back to that time , My mentality has undergone great changes , During this period, some events have made me have a new understanding of community communication and developers .

The first thing is actually community partners Zadig Expectation and evaluation of products , Every time I publish a website, I feel pushed by my friends in the community , No matter how late , There are always some friends ” Wail “.

As the one who has the most contact with external feedback , Realizing that dealing with community problems is not a very “low” Things about , On the contrary , Dealing with community problems efficiently is a very good opportunity to polish products , It's Jean Zadig The only way for a piece of code to generate value . In this process, as problems are solved , My network problem 、K8s knowledge 、 Communication and collaboration skills have been greatly improved .

The second thing is Zadig Contributor Bootcamp The establishment of the , Let me know more about the output of community content . The establishment of this activity is actually a very natural process , For Zadig We plan for better scalability in the future v1.3.1 The scale of the underlying architecture , Introduce key cloud native components . After release , There are a lot of little friends to Zadig Is very interested in the architecture of , There will also be some related discussions , I found Landy： Since so many people are interested , We should share it , Why don't we try to share some issues . At that time, I made a rough plan without much thought , Launch Tencent conference invitation on some important contents and communities , Throw it directly into the group without doing any operation . In fact, at that time Bootcamp The effect is not too much to expect, but also a little uneasy , As a result, it is now completed in one phase , Each period is stable 30 Ask a participant actively 、 communication 、 Offer advice and suggestions , This makes me fully feel the power of openness , The right thing always happens .

The third thing is actually how to make The feedback processing process of the community is efficient , It is also a kind of growth . Community partners have various needs and problems , Sometimes I really want to get angry , If you can't deal with it efficiently , Will drag yourself into a state of inefficiency , I abstract several kinds of problems ：

• Especially Xiaobai's problem , For example, basic network 、Dockerfile/YAML Write these , At first, I will teach you by hand , Later, we decided that this was very inappropriate , This is not conducive to better community construction , So in the follow-up, it is suggested that small partners explore by themselves

• Product use problems , Throw the document directly , Documentation is the best tool , Can systematically explain a capability ,Zadig Document usage is also rising rapidly , This is very conducive to efficient learning and use Zadig, Pure fetchism is not feasible , Nor is it advocated by the community .

• Scene access problem , Best practice of throwing official account directly ,Zadig In a large number of enterprise user scenarios , Precipitated a lot of good practice , The stone of its mountain can be used to attack jade , It can greatly help users find their own path .

Now, with more and more community partners , User practice is getting deeper , There are many enthusiastic developers who act as preachers themselves , In particular, I mentioned the community's Jock 、Aurora、 There are also some students like “ From the very beginning ” Share their experience , Also exchange more and more high-level technical topics , This is the right community opening posture .

Future outlook

Self join KodeRover Since the team , With more and more work , Mentality also changes with growth . I have been full of energy since I first started , To the confusion and uneasiness after the change of duty . Final , This confusion about the future , In practice, it is transformed into confidence in the future .

Now of I , I believe in the power of the community , Also hope to promote Zadig While growing rapidly , Deep links with all partners in the community , Growing up together .

Next will be a new beginning , I will invest a considerable part in the construction of the community , The content of R & D will also focus more on the developer experience , One thing I'm doing recently is building Zadig Forum to precipitate more valuable exchanges .

One more thing： Here comes the community forum

Everyone must be curious about how active the community is every day , How do we deal with community feedback effectively ？ In fact, we will record effective feedback in documents every day , Products will be invited every week 、 The architecture will be discussed for half an hour , The final precipitation is the demand item . Every time after publishing at Go to the corresponding partner , Up to now, the feedback and solution rate of community problems has reached 70%.

Launch of Community Forum , Make communication more efficient , Better precipitation of knowledge . With the Forum , You can not only link Zadig And users / developer , It can also realize the interconnection between developers . Wechat community will continue to be preserved , I can still hear everyone's voice in time .

It's too late to explain , Go to the https://community.koderover.com Register for forum preemption ID！

Zadig, Believe in the power of openness . Welcome to join Make complaints about open source Tucao group

Zadig on Github
Zadig on Gitee