You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This document outlines the responsibilities of the contributor role in the organization. The project is subdivided into sub projects according to sig. Most roles are bound to these subprojects.
4
6
5
7
Here we provide some baseline of roles' responsibilities and requirements, it varies from sig to sig.
@@ -11,20 +13,35 @@ Here we provide some baseline of roles' responsibilities and requirements, it va
11
13
| approver | approve accepting contributions | Experienced and active reviewer + sub project contributor |
12
14
| subproject owner | set direction and priorities for a subproject | Demonstrate a sense of responsibility and good technical judgment on sub projects |
13
15
14
-
## Member
16
+
###Member
15
17
16
18
Members are continuous and active contributors to the community. They can assign problems and PR to them, participate in sig through GitHub team, and automatically run pre commit tests for their pr. It is hoped that members will continue to make positive contributions to the community.
17
19
18
-
## Reviewer
20
+
###Reviewer
19
21
20
22
Reviewers are able to review the quality and correctness of code in some parts of a subproject. They have a good understanding of the code base and the principles of software engineering.
21
23
22
-
## Approver
24
+
###Approver
23
25
24
26
Code reviewers are able to review and approve code contributions. Code review focuses on code quality and correctness, while approval focuses on overall acceptance of contributions, including backward / forward compatibility, compliance with API and flag conventions, subtle performance and correctness issues, interaction with other parts of the system, etc.
25
27
26
-
## Subproject Owner
28
+
###Subproject Owner
27
29
28
30
Note: This is a high-level, high-level description of roles. The responsibilities of the subproject owner role and the details of the related processes must be defined for a single sig or subproject.
29
-
The sub project owner is the technical license for the sub project of the kubernetes project. They must show good judgment and responsibility for the health of the subprojects. The subproject owner must set the technical direction and make or approve design decisions for the subproject, either directly or by delegating these responsibilities.
31
+
The sub project owner is the technical license for the sub project of the PaddlePaddle project. They must show good judgment and responsibility for the health of the subprojects. The subproject owner must set the technical direction and make or approve design decisions for the subproject, either directly or by delegating these responsibilities.
32
+
33
+
## Org Membership
34
+
35
+
Add new members to PaddlePaddle GitHub org. This process outlines the steps to add someone to PaddlePaddle GitHub organization.
36
+
37
+
### Membership Requirements
38
+
39
+
All members of the PaddlePaddle GitHub organization must do the following:
40
+
41
+
- List positive contributions
42
+
- List the activities which candidate participated in
43
+
- Sponsored by two active members from PaddlePaddle org
44
+
45
+
### Apply for the org membership
30
46
47
+
- Open a PR against the PaddlePaddle/community repo, adding the potential member's GitHub username to the members list.
0 commit comments