Слияние кода завершено, страница обновится автоматически
This document provides guidance on how to participate in the openEuler community.
Welcome to openEuler!
Welcome to openEuler!
You must sign a Contributor License Agreement (CLA) before you can contribute to the community.
openEuler is an open source community, which relies on the friendly development and collaboration environment jointly maintained by the members. Read and comply with the Code of Conduct of the openEuler community before contributing to the community.
Welcome to join us anytime!
The community documents can be improved (such as the one you are reading), code needs to be reviewed, functions or variables can be reconstructed or commented, and test cases can be continuously supplemented and optimized. We will help you understand the organization of openEuler SIGs and walk you through your first contribution. If you're interested, take action now!
SIG is short for Special Interest Group. The openEuler community is organized into different SIGs to better manage and improve the work process.
Finding the SIG you are interested in can help you ask questions in the right place and get a quicker response from the community.
Method 1: If you do not know which SIGs or projects exist, you can view the list of SIGs established in the openEuler community. You can use the list to quickly locate the SIG corresponding to the field that you are interested in. The following information about the SIG is also provided:
Method 2: If you know the project name, you can perform fuzzy search in the repository list of openEuler to quickly locate the home page address of the corresponding project. Generally, you can find the SIG information, communication methods, members, and contact information of the project in the README.md file on the project home page.
If you cannot locate the SIG you are interested in using either of the preceding methods, you can send an email to community@openeuler.org for help. You are advised to use [Development Process Question] as the title of the email and write down the characteristics of the SIG or project that you are looking for in the content. We are glad to help.
Find the issue list: On the toolbar of the home page (repository of the project on Gitee) of the project that you are interested in, click 
to find the issue list of the SIG (for example, the issue list address of the community SIG is https://gitee.com/openeuler/community/issues).
Find an issue that you want to handle: If you want to handle one of the issues, you can assign it to yourself. You only need to enter /assign or /assign @yourself in the comment area. The bot will assign the issue to you and your name will be displayed in the assignee list.
Participate in discussion within an issue: An issue may have been discussed by participants. If you are interested in the issue, you can leave your comment in the comment area.
If you want to contribute code, you need to prepare the openEuler development environment. For details, see Development Environment Preparations.
If you want to download, modify, build, and verify the software packages provided by openEuler, see Software Package Building.
The coding language, development environment, and coding conventions used in each SIG project may be different. If you want to understand and participate in coding, you can find the contributor guide provided by the project for developers. The guide is generally provided in the CONTRIBUTING.md file on the SIG home page or in README.md of the project repository. For details about how to find the project repository, see the previous section.
In addition to these files, the SIG may also provide other guidance information. This information is located in the specific community directory of the SIG or its projects. If you do not find related information or have questions about related information, you can submit issues in the SIG or send the issues or questions to the mailing list of the SIG to which the project belongs. If you do not receive a response for a long time, you can ask community@openeuler.org for help.
To contribute code, you also need to know how to download code from Gitee and merge the code through a pull request (PR). The code of the openEuler community is hosted on Gitee. For details, see Gitee Workflow. The method of using Gitee is similar to that of GitHub. If you have used GitHub before, you can have a quick look at or even skip this chapter.
After the modification is complete on the local branch, perform build and verification locally by referring to Software Package Building.
When you submit a PR, you are starting to contribute code to the community. For details, see Pull Request Submission Guide.
openEuler can automatically create a repository with the same name on openEuler:Factory of OBS when a software package is added to Gitee. In this way, when the code is submitted to the created Gitee repository, the code compilation is automatically checked. For details, see Adding a New Software Package.
openEuler is an open community and everyone involved is expected to be an active reviewer. For details about the roles and responsibilities of different types of contributors, see Community Membership.
As a contributor, to make your submissions easier to accept, you need to:
As a reviewer, it is strongly recommended that you comply with the Code of Conduct and respect others to promote collaboration and improve yourself. When reviewing others' PRs, you can refer to a series of key review points provided in The Gentle Art Of Patch Review, which indicates that the code reviewer is expected to encourage new contributors to actively participate in the program instead of putting off reviewing contributions from new-comers and giving nit-picking comments. Therefore, pay attention to the following points during the review:
Note: If your PR does not attract enough attention, you can ask for help through the mailing list of the SIG or send email to dev@openeuler.org.
Testing is the responsibility of all contributors. The QA SIG is the official organization responsible for testing activities related to the versions of the community edition . If you want to carry out testing on your own infrastructure, see Community Test System.
A successful release of the community edition requires multiple types of testing activities. The code to be tested and environments required for running the tests vary with the test activity types. For details, see Community Developer Test Contribution Guide.
You can also participate in community component packaging. For details, see the openEuler Packaging Guide.
If you are not interested in writing code, you can find the work of your interest in Non-Code Contributions.
See openEuler Download.
Communication methods in the openEuler community include the mailing lists, IRC channels, and video conference. For details, see openEuler Communication.
Information about community meetings and technical exchanges attended or held by openEuler can be found on the openEuler News page.
The community holds developer conferences every year. Get in touch with us through contact information on https://openeuler.org or send email to dev@openeuler.org. Come and join us!
If you have any questions about the contributor guide or the development process, please feel free to tell us through the mailing lists and write down your questions and doubts in the email with the subject line in the format of [Development Process Question]. The openEuler community operations team will coordinate and assign related personnel to answer your questions.
Вы можете оставить комментарий после Вход в систему
Неприемлемый контент может быть отображен здесь и не будет показан на странице. Вы можете проверить и изменить его с помощью соответствующей функции редактирования.
Если вы подтверждаете, что содержание не содержит непристойной лексики/перенаправления на рекламу/насилия/вульгарной порнографии/нарушений/пиратства/ложного/незначительного или незаконного контента, связанного с национальными законами и предписаниями, вы можете нажать «Отправить» для подачи апелляции, и мы обработаем ее как можно скорее.
Опубликовать ( 0 )