Introduction Basic Process Choose a project Encountered in work Daily use Familiar with the tech stack used by the project … Identify a problem Code Spelling Documentation Tests … Fork Modify Code Tests Comments Documentation Sign contributor agreement CLA DCO Submit pull request CI Review Merge Follow-up Close issue Wait for release Continuous contribution to become a maintainer General Principles How to Be a Qualified Open Source Project Contributor Identify your skills and tech stack, and choose a matching open source project. Understand the code structure, functions, and specifications of the open source project, and read its contribution guidelines. Various types of contributions are welcome, such as fixing bugs, adding features, writing documentation, tests, etc. Start with small changes, such as modifying documentation, spelling, adding test code, fixing bugs with a small scope. Core process: Create and submit a pull request (PR), and wait for reviews and feedback from other contributors. Maintain good communication and collaboration with other contributors. Follow the open source project’s code of conduct. How Non-Native English Speakers Can Participate Better Improve English proficiency, especially reading and writing skills, to better understand project requirements, documentation, and code, and to clearly express ideas and suggestions. Choose open source projects with active communities and friendly atmospheres to get more help and support, and learn from other contributors’ experiences. Follow the open source project’s contribution process, such as fork, clone, branch, commit, push, and pull request, and abide by the project’s coding style and specifications. When submitting issues or PRs, try to use simple and clear English to describe the problem or feature, and attach relevant screenshots or code snippets. When communicating with other contributors, be polite and respectful, don’t be afraid to ask or answer questions, and respond to their reviews and feedback in a timely manner. If unsure about certain English words or expressions, use dictionaries, translation tools, or grammar checkers to assist communication. How to Get Open Source Project Maintainers to Quickly Review Your PR Follow project guidelines: Before submitting a pull request, be sure to check and follow the project’s contribution guidelines. Ensure the request meets the project’s specifications and standards. Ensure consistent code style: Follow the project’s code style and formatting requirements to reduce the amount of code that maintainers need to modify during review. Provide detailed description: When submitting a pull request, ensure you provide a sufficiently detailed description explaining how the modification solves the problem or improves the project. Provide test cases: Try to ensure that new code is covered. Some projects check unit test coverage and covered lines. Reply to comments promptly: Once your pull request is reviewed, reply to the maintainer’s comments as quickly as possible and consider the opinions and suggestions discussed. Github Flow ...