Author: HelloGitHub- Stewed eggs

Join 35K Star on GitHub to share interesting, entry-level open source projects on GitHub, and let’s make it a pure land for open source enthusiasts.

There are less than 10 of us. Do you want to be a member of the top 10? Then come on

Recruiting: operations, content, development, or anything else you want to do for HG. Hope you are:

  1. HG’s readers and fans, who identify with what HelloGitHub does, love open source culture.
  2. Fun, loving, dependable, responsible; Be curious about the unknown and dare to explore.

We can provide:

  1. Honor: Joining HG is not something one is proud of, contributing is. It wasn’t blown or given. It was earned.
  2. Money: HG is currently profitable, so if you need a monetary return, you can specify your expectations directly in your submission.
  3. Opportunity: give yourself a chance to do a good job, I hope you can grow into the highest point in my eyes, the person standing.
  4. Friendship: brother, please write you and HelloGitHub story, we know horsepower, time.

Application method (mail application only) :

  1. Email title: Join HelloGitHub team (position), content in the form of MD attachment, send to [email protected] email
  2. All content (job requirements and self-introduction) should be written in the Markdown file. Be sure to include an attachment in the email. Markdown syntax: github.com/younghz/Mar…
  3. Please be responsible for your submission, typography requirements: github.com/sparanoid/c…
  4. No matter what position you are in, you should start with an introduction and attitude. Contains:
    • The basic information
    • What you do, what you’re good at. What’s the thing you’ve done the longest
    • What makes your eyes light up and excited
    • What is your attitude towards open source and what HG is trying to do
    • What was your original intention in joining HG

Note: all team members will participate in the discussion of HG’s future construction and decision making. If they do not like it, please note in the materials.

Harm, all buddy ~ how to think how to write, do not turn straight to communicate, I will protect your privacy.

Below are the specific requirements and responsibilities of operation, content and development positions, please read carefully!

I. Operation (unlimited number of people)

I look forward to your interesting soul to make HG dynamic and personalized!

Platforms that HelloGitHub has settled in: wechat, Toutiao, Zhihu, Nuggets of Gold, Jike, Blog Park, CSDN

Things:

  1. Responsible for account operation of one or more HG platforms
  2. Increase the influence of HelloGitHub on the platform
  3. Operate open source and GitHub related content; Synchronize daily features and articles
  4. Interact with fans (topics, sweepstakes, replies, comments, retweets, likes, etc.)

Requirements:

  1. Interested in reviewing, learning, and understanding the rules and regulations of the platform and engaging with the community
  2. Ability to write short content related to GitHub theme and open source (tweets, answers, etc.)
  3. Ability to read English materials
  4. Don’t fool around, recognize the importance of typography
  5. Ensure that the HG account is operated for at least one hour every day

Materials to be provided:

  1. Pick a random item that HelloGitHub recommends and write a similar recommendation. This paragraph contains welcome, project name, and recommendations (less than 100 words)
  2. Pick a platform you want to be responsible for and write down why you chose it
  3. What do you want to do if you run an account on a certain platform

Two, content (unlimited number of people)

Let your words, find more people like it!

The current contents of HG are as follows:

  • Open Source Project Series (author with programming skills required) : For readers who want to advance their technology through the open source community
  • Introduction to the Open Source Project series (no programming skills required) : For all readers interested in the open source community

2.1 Open source project series

Help open source enthusiasts understand, use, and join open source projects faster, and learn real technology and knowledge in this series. Divided into single and series:

  • Single: Introduce an open source project and get started quickly in one or two chapters. herewith

  • Series: In 5 to 13 installments, an in-depth introduction to an open source project, from installation steps to principles and design ideas. herewith

2.1.1 requirements:

  1. Like to small white preaching, between the lines is full of doting, identify with the importance of typesetting
  2. Have been engaged in a certain programming field for more than 1 year, have the driving force and ability to study open source project by oneself, have the pursuit of technology
  3. Commit to delivering at least one original article every two weeks
  4. Articles need to be original and first published on HelloGitHub, the author name is unified as: HelloGitHub- your nickname

2.1.2 Materials to be prepared:

  1. Please provide your previous work, including but not limited to: open source projects, articles, blogs, answers, etc
  2. Talk about a technology or project you are currently working on (300 words or less)
  3. What criteria do you use to select projects for presentation (if it’s your own project, write down what your readers will learn from it)

2.2 Introduction to the Open source project series

Help open source enthusiasts understand and use open source projects. The series doesn’t need to be technical, but hopefully it will be accessible to readers with no programming background. Let them feel the convenience (tools), the charm (cool), and the fun (fun) of the open source community.

  • A selection of open source projects under a particular topic.herewith
    1. Select a topic, such as a collection of handy VSCode plug-in open source projects
    2. Select open source projects (5 or so) that fit this theme. The projects must have characteristics and be suitable for a wide range of people
    3. Write a sincere introduction for each project, along with links, the language of the project (if needed), information on the number of stars, and finally the introduction to the beginning of the body and the conclusion of the deductions
  • Introduces an open source project.Sample (ignore the code)
    1. What does the project do
    2. What are the features and highlights of the project
    3. Download, installation methods and solutions to problems encountered in the installation process
    4. Simple usage and main functions (multi-picture)

2.2.1 requirements:

  1. Follow the open source community and enjoy playing with open source projects. Ability to read English materials
  2. Know how to solve problems and use search engines, Google
  3. Commit to delivering at least one original article every two weeks
  4. Have certain writing skills, recognize the importance of typesetting
  5. Articles need to be original and first published on HelloGitHub, the author name is unified as: HelloGitHub- your nickname

2.2.2 Materials to be provided:

  1. Describe where you find interesting open source projects
  2. If you encounter a project you don’t understand and have problems with the installation process, how do you resolve it
  3. Write an article: an original article that highlights or introduces an open source project on a topic

Iii. Development (3rd)

God, give me some code!

The developer’s contribution may not be easily visible to users, but write code in HG. All users will know about your code and your contributions. Use your code, say you are powerful. Recruitment development is the most demanding:

  • A person who can stand on his own two feet, who has a desire to succeed
  • Design (front end) and product (back end) capabilities
  • Be the master of your own code
  • Initiative: Since it’s your spare time to participate in open source, don’t take tasks like work, let people chase ass to schedule
  • Ensure at least 2 hours of development time per week

HelloGitHub to rebuild a community, it is not an easy task, need to be able to carry the people. As long as you get on with it, you can count on all my support, and your contributions will be known and remembered.

3.1 Front End (2 bits)

3.1.1 requirements:

  1. I don’t know the front end. I have to imagine

3.1.2 Materials to be provided:

  1. Check out this project: github.com/HelloGitHub… Then talk about what you think
  2. If you were designing a community of open source enthusiasts, what front-end technologies would you use to build it?
  3. Please provide your open source projects or written code (project level)

3.2 Back-end (1 bit)

3.2.1 requirements:

  1. Have used Python for over 2 years
  2. Crawlers, Web, operations are best, but you can also specialize
  3. Agree on the importance of documentation and typography
  4. Good taste in code, but also good stomach for refactoring
  5. Be willing and willing to experiment with new Python technologies and frameworks

3.2.2 Materials to be provided (choose one answer) :

  1. If you were given a 2C2G 2M machine to crawl GitHub data. What information do you crawl, how do you design to maximize data richness and quantity, and service stability?
  2. Which Python asynchronous non-blocking Web frameworks do you know about, and which do you like best? How does the framework guarantee concurrency when it encounters frequent database operations? What would you do if you used it to implement a data visualization interface (such as the number of clicks per item in a monthly issue)?
  3. We have three servers respectively deployed: Web, crawler, database service, and an additional 1C1G Intranet machine at this time. What will you do with it? And give your reasons.

I want to find a brother who can not only write code with me, but also carry things with me, so that we can tighten our belts together

Finally, paste the application method again

Application method (mail application only) :

  1. Email title: Join HelloGitHub team (position), content in the form of MD attachment, send to [email protected] email
  2. All content (job requirements and self-introduction) should be written in the Markdown file. Be sure to include an attachment in the email. Markdown syntax: github.com/younghz/Mar…
  3. Please be responsible for your submission, typography requirements: github.com/sparanoid/c…
  4. No matter what position you are in, you should start with an introduction and attitude. Contains:
    • The basic information
    • What you do, what you’re good at. What’s the thing you’ve done the longest
    • What makes your eyes light up and excited
    • What is your attitude towards open source and what HG is trying to do
    • What was your original intention in joining HG

Welcome to HelloGitHub