forked from openkylin/docs
update en/Community-Engagement-Guides/Participation_Guide.md.
Signed-off-by: 康艳红 <731193006@qq.com>
This commit is contained in:
康艳红
Gitee
parent
07b6a298ff
commit
ea253b106f
|
|
@ -17,7 +17,7 @@ The process of enterprise signing is more complicated, and the enterprise CLA si
|
|||
|
||||
The process for companies to sign the CLA is shown in the following diagram
|
||||
|
||||
! [image-20220719113819070](./assets /participation-guide/enterprise CLA-signing-process.png)
|
||||
! [image-20220719113819070](./assets/participation-guide/企业CLA签署流程.png)
|
||||
|
||||
1. First, submit the basic information for enterprise signing in the [enterprise signing](https://cla.openkylin.top/cla/sign/corporation_cla/openKylin-f46f289e01bc11edb8990242ac110005) page, where `enterprise`, ` contact person`, `position`, `email` and `validation code` are required fields, other information can be left out;
|
||||
2. after clicking the sign button, you will receive an email in the email address you filled in the previous step, which includes the basic information filled in the previous step and three attached files, follow the instructions in the email to complete the subsequent steps;
|
||||
|
|
@ -33,7 +33,7 @@ The process for companies to sign the CLA is shown in the following diagram
|
|||
After your enterprise has finished signing the enterprise CLA, you can use the mailbox that matches your enterprise mailbox suffix to sign the employee CLA, the process of employee signing is shown below.
|
||||
|
||||
The process of employee signing is shown below.
|
||||
！[image-20220719134148656](./assets /participation-guide/employee-cla-signing-process.png)
|
||||
！[image-20220719134148656](./assets/participation-guide/员工CLA签署流程.png)
|
||||
|
||||
1. Open the [Employee Signing](https://cla.openkylin.top/cla/sign/employee_cla/openKylin-f46f289e01bc11edb8990242ac110005) page, fill in the basic information, click the Send Captcha button, and enter the email verification code into the verification code box, check the box **I have read the agreement and agree to sign**, click the sign button, a pop-up prompt employee sign has been submitted;
|
||||
2. contact the enterprise administrator, who will activate the employee signing request submitted by you on the employee management page;
|
||||
|
|
@ -43,7 +43,7 @@ The process of employee signing is shown below.
|
|||
|
||||
If you are an individual developer or your company does not have an enterprise CLA, you can submit your contribution to the openKylin community by signing a personal CLA, the personal CLA signing process is similar to the employee CLA signing process, as shown in the figure below.
|
||||
|
||||
! [image-20220719134322666](./assets /participation-guide/personal-signing-cla-process.png)
|
||||
! [image-20220719134322666](./assets/participation-guide/个人签署CLA流程.png)
|
||||
|
||||
1. Open the [Personal Signing](https://cla.openkylin.top/cla/sign/person_cla/openKylin-f46f289e01bc11edb8990242ac110005) page, fill in your basic personal information, click the Send Captcha button, put the verification code from your email address Enter the verification code into the verification code box, check **I have read the agreement and agree to sign**, click the sign button, and a pop-up will appear to indicate successful signing;
|
||||
2. open the personal signing mailbox, you can receive a personal CLA signing audit approval email;
|
||||
|
|
@ -57,7 +57,7 @@ If you are an individual developer or your company does not have an enterprise C
|
|||
|
||||
Speaking of which, some of you may ask, "Why do we need to make these three forms of CLA signature? Don't worry, let me see the following picture
|
||||
|
||||
! [image-20220719113249904](./assets /participation-guide/difference-between-three-forms-of-CLA-signing.png)
|
||||
! [image-20220719113249904](./assets/participation-guide/三种CLA签署形式区别.png)
|
||||
|
||||
Employee signing is mandatory for enterprises. If the enterprise where the developer works signs the enterprise CLA, then all employees of that enterprise can sign the employee CLA belonging to that enterprise, so **contributions submitted by employees in the openKylin community (including but not limited to PR, ISSUE, etc.) are attributed to the enterprise's contribution to the openKylin community**.
|
||||
|
||||
|
|
@ -81,7 +81,7 @@ pacman -S git
|
|||
|
||||
After the installation is complete, type `git version` in the terminal. If the output corresponds (similar to the image below), the installation was successful.
|
||||
|
||||
! [image-20220718104036962](./assets /participation-guide/git-version.png)
|
||||
! [image-20220718104036962](./assets/participation-guide/git版本.png)
|
||||
|
||||
After confirming that the git installation is complete, we can enter commands in the terminal to configure our personal information, we just need to configure the simplest user information.
|
||||
|
||||
|
|
@ -98,11 +98,11 @@ git config --global user.name "zhangsan" # Configure the committer username
|
|||
|
||||
In the previous section, we completed the `git` environment locally, the next is the code contribution process, before that we need to go to `gitee` to create an account, if you do not have a `gitee` account, you can click this link to create https://gitee.com/signup, after creating a good gitee account, you can You can submit your contributions to the openKylin community on gitee. The process of submitting contributions is shown in the figure below.
|
||||
|
||||
! [image-20220722094610738](./assets /participation-guide/PR-process.png)
|
||||
! [image-20220722094610738](./assets/participation-guide/PR流程.png)
|
||||
|
||||
1. Fork a copy of the repository you are interested in to your personal account on gitee (this article uses ukui-menu as an example), as follows, click the fork button to copy the repository to your personal account
|
||||
|
||||
! [image-20220718174332874](./assets /participation-guide/fork-example.png)
|
||||
! [image-20220718174332874](./assets/participation-guide/fork示例.png)
|
||||
|
||||
2. After forking the repository to your personal account, you can modify the code in our local environment by cloning the code locally with the following command
|
||||
|
||||
|
|
@ -127,12 +127,12 @@ In the previous section, we completed the `git` environment locally, the next is
|
|||
git commit -m "add README-zh.md file" # Commit the changes
|
||||
git push # Push the changes to the remote repository
|
||||
git push
|
||||
! [image-20220718174332874](./assets /participation-guide/successfully-pushed-modifications-to-personal-repository.png)
|
||||
! [image-20220718174332874](./assets/participation-guide/成功推送修改到个人仓库.png)
|
||||
|
||||
|
||||
4. After pushing our changes, you can commit your PR on gitee by clicking on the `Pull Requests` option in the image above, then click on `New Pull Request` on the right side to create a new `Pull Request`, fill in the corresponding information on the page, click on Create Pull Request, and you You have successfully submitted your first PR.
|
||||
|
||||
! [image-20220718174332874](./assets /participation-guide/gitee-submit-pr.png)
|
||||
! [image-20220718174332874](./assets/participation-guide/gitee提交PR.png)
|
||||
|
||||
> **TIPS!**
|
||||
>
|
||||
|
|
@ -145,7 +145,7 @@ In the previous section, we completed the `git` environment locally, the next is
|
|||
|
||||
After the PR submission is completed, there will be a record of the submission information on the personal homepage by clicking on it to jump to the PR details page, where you can see the information shown below
|
||||
|
||||
! [image-20220718174332874](./assets /participation-guide/view-pr-status.png)
|
||||
! [image-20220718174332874](./assets/participation-guide/查看PR状态.png)
|
||||
|
||||
Clicking on the link in the green box in the image above will both jump to the build log and view detailed build information! In short, everything you care about PR can be seen on the details page of your PR submission.
|
||||
|
||||
|
|
@ -158,7 +158,7 @@ In addition to the PR contribution method, issue is also a contribution method.
|
|||
- If it is a system-level bug, then you can submit a `bug issue` under the [openKylin/community](https://gitee.com/openkylin/community/issues) repository.
|
||||
- If it is an application-level bug, you can submit `bug issues` under the corresponding repository in the openKylin community. For example, if you find a bug that sometimes flickers when you use kylin video, you can submit `bug issues` under [openKylin/kylin-video](https://gitee.com/) openkylin/kylin-video/issues) repository;
|
||||
|
||||
! [image-20220718174332874](./assets /participation-guide/submit-issue.png)
|
||||
! [image-20220718174332874](./assets/participation-guide/提交issue.png)
|
||||
|
||||
> **TIPS!**
|
||||
>
|
||||
|
|
@ -168,7 +168,7 @@ In addition to the PR contribution method, issue is also a contribution method.
|
|||
|
||||
SIG is called Special Interest Group, if you want to participate deeply in the openKylin community, you can apply to join the SIG of the direction you are more interested in, the current `openKylin` community SIG list can go to https://www.openkylin.top/join The current list of `openKylin` community SIGs can be viewed at /sig-cn.html, and the process for developers to join SIGs is as follows.
|
||||
|
||||
! [image-20220718174332874](./assets /participation-guide/join-sig-process.desktop)
|
||||
! [image-20220718174332874](./assets/participation-guide/加入sig流程.desktop)
|
||||
|
||||
Next, let's demonstrate how to join the SIG by a chestnut, if I want to join the `HTML5` SIG
|
||||
|
||||
|
|
@ -218,7 +218,7 @@ Next, let's demonstrate how to join the SIG by a chestnut, if I want to join the
|
|||
|
||||
Because the community's SIG member privileges are too high, if you want to join the SIG in the openKylin community, you need to have certain contributions in the community before the technical committee may pass your application to join the SIG, so for general developers, it is recommended to apply for single package maintainer at the beginning, the process of single package maintainer is shown in the figure below, the specific instructions for single package maintainer can be viewed in [this link document](https://gitee.com/openkylin/community/blob/master/packages/README.md)
|
||||
|
||||
! [image-20220719152436970](. /assets/individual-developer-contribution-guidelines/application-for-single-package-maintainer-process.png)
|
||||
! [image-20220719152436970](./assets/participation-guide/申请单包维护者流程.png)
|
||||
|
||||
#### 4.1 Applying to become a new single package maintainer
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue