Skip to content

Commit e93827e

Browse files
committed
workflow: add gatekeepers section
1 parent 8743e79 commit e93827e

File tree

1 file changed

+34
-32
lines changed

1 file changed

+34
-32
lines changed

docs/reference/contributing/guidelines/workflow.md

Lines changed: 34 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,39 @@
11
### Workflow
22

3+
#### Gatekeepers
4+
5+
##### Mbed OS maintainers
6+
7+
The maintainers are a small group of Mbed OS engineers who are responsible for the Mbed OS codebase. Their primary role is to progress contributions, both internal and external, from the initial pull request state through to released code.
8+
9+
Responsibilities:
10+
11+
1. Check for CLA compliance.
12+
1. Ensure the relevant stakeholders review pull requests.
13+
1. Guide contributors both technically and procedurally.
14+
1. Run pull requests through the CI systems.
15+
1. Put label version.
16+
1. Merge pull requests into the requested branches.
17+
1. Make periodic patch and feature releases.
18+
19+
The current maintainers are:
20+
21+
* Anna Bridge (adbridge).
22+
* Martin Kojtal (0xc0170).
23+
* Jimmy Brisson (theotherjimmy).
24+
* Shrikant Tudavekar (studavekar).
25+
* Sam Grove (sg-).
26+
* Cruz Monrreal (cmonr).
27+
28+
##### Stakeholders
29+
30+
They are responsible for a specific mbed OS module or feature.
31+
32+
Responsibilities:
33+
34+
1. Review pull request and coordinate reviews within the team
35+
1. Ensure the version label is correct
36+
337
#### Contributions
438

539
All code changes and additions to Mbed OS are handled through GitHub. If you want to contribute, either by adding features or by fixing bugs, please follow the guidelines for [new features](#contributing-new-features-to-mbed-os) and [bugs](#reporting-and-fixing-bugs). In both cases, please follow the [code style guide and GitHub pull request guidelines](/docs/v5.7/reference/guidelines.html#style)</a>. Please also read the [CLA](/docs/v5.7/reference/guidelines.html#cla) guidelines because we will immediately close pull requests submitted without a CLA.
@@ -60,38 +94,6 @@ Each feature has a tech lead. This person is responsible for:
6094
- rebasing often to track master development
6195
- reviewing any addition to the feature branch (approval required by the feature owner or a person assigned to do instead)
6296

63-
#### Mbed OS maintainers
64-
65-
The maintainers are a small group of Mbed OS engineers who are responsible for the Mbed OS codebase. Their primary role is to progress contributions, both internal and external, from the initial pull request state through to released code.
66-
67-
Responsibilities:
68-
69-
1. Check for CLA compliance.
70-
1. Ensure the relevant stakeholders review pull requests.
71-
1. Guide contributors both technically and procedurally.
72-
1. Run pull requests through the CI systems.
73-
1. Put label version.
74-
1. Merge pull requests into the requested branches.
75-
1. Make periodic patch and feature releases.
76-
77-
The current maintainers are:
78-
79-
* Anna Bridge (adbridge).
80-
* Martin Kojtal (0xc0170).
81-
* Jimmy Brisson (theotherjimmy).
82-
* Shrikant Tudavekar (studavekar).
83-
* Sam Grove (sg-).
84-
* Cruz Monrreal (cmonr).
85-
86-
#### Stakeholders
87-
88-
They are responsible for a specific mbed OS module or feature.
89-
90-
Responsibilities:
91-
92-
1. Review pull request and coordinate reviews within the team
93-
1. Ensure the version label is correct
94-
9597
#### GitHub pull requests workflow
9698

9799
Each pull request goes through the following workflow:

0 commit comments

Comments
 (0)