openbmc/docs/maintainer-workflow.md

5 for sub-project maintainers to follow before approving patches.
7 - Manually verify the contributor has signed the ICLA (individual) or is listed
9   - Executed CLAs can be found [in the CLA repository][1].
10   - If you were not added to the appropriate CLA repository ACL send an email to
12   - If a CLA for the contributor is found, accept the patch(1).
13 - If a CLA is not found, request that the contributor execute one and send it to
15   - Do not accept the patch(1) until a signed CLA (individual _or_ corporate)
17   - The CCLA form can be found [here][2].
18   - The ICLA form can be found [here][3].
21 forks of upstream projects, like the Linux kernel or U-Boot.
26 copied from the web, and maintaining the quality of the code.
31 - responsible: have a continuing desire to ensure only high-quality code goes
33 - leadership: foster open-source aware practices such as [FOSS][4]
34 - expertise: typically demonstrated by significant contributions to the code or
37 (1) The semantics of accepting a patch depend on the sub-project contribution
40 - GitHub pull requests - Merging the pull request.
41 - Gerrit - +2.
42 - email - Merging the patch.
47 [2]: https://drive.google.com/file/d/1d-2M8ng_Dl2j1odsvZ8o1QHAdHB-pNSH
49 [4]: https://en.wikipedia.org/wiki/Free_and_open-source_software