diff options
| author | Gunnar Mills <gmills@us.ibm.com> | 2019-02-11 15:54:02 -0600 |
|---|---|---|
| committer | Gunnar Mills <gmills@us.ibm.com> | 2019-02-13 02:37:37 +0000 |
| commit | 563414d96f1b680c82f9f32a0c9ccdb020b46b47 (patch) | |
| tree | 1d99bf298217b8b4b5c88ec3c5c6f2e760d7cdd5 | |
| parent | b142fdd1578b2d3def7d6e6e07a7079575a58afc (diff) | |
| download | openbmc-docs-563414d96f1b680c82f9f32a0c9ccdb020b46b47.tar.gz openbmc-docs-563414d96f1b680c82f9f32a0c9ccdb020b46b47.zip | |
maintainer-workflow: Fix links
Tested: Copied into https://jbt.github.io/markdown-editor/
Change-Id: I8e78f322af3e2ba7519977b3b2c7e46dc9809a32
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
| -rw-r--r-- | maintainer-workflow.md | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/maintainer-workflow.md b/maintainer-workflow.md index d5b2d40..583d9a3 100644 --- a/maintainer-workflow.md +++ b/maintainer-workflow.md @@ -5,8 +5,7 @@ checklist for sub-project maintainers to follow before approving patches. * Manually verify the contributor has signed the ICLA (individual) or is listed on an existing CCLA (corporate). - * Executed CLAs can be found [in the CLA repository] - (https://drive.google.com/drive/folders/1Ooi0RdTcaOWF1DWFJUAJDdN7tRKde7Nl). + * Executed CLAs can be found [in the CLA repository][1]. * If you were not added to the appropriate CLA repository ACL send an email to openbmc@lists.ozlabs.org with a request to be added. * If a CLA for the contributor is found, accept the patch(1). @@ -14,10 +13,8 @@ email to openbmc@lists.ozlabs.org with a request to be added. to openbmc@lists.ozlabs.org. * Do not accept the patch(1) until a signed CLA (individual _or_ corporate) has been uploaded to the CLA repository. - * The CCLA form can be found [here] - (https://github.com/openbmc/openbmc/files/1860741/OpenBMC.CCLA.pdf). - * The ICLA form can be found [here] - (https://github.com/openbmc/openbmc/files/1860742/OpenBMC.ICLA.pdf). + * The CCLA form can be found [here][2]. + * The ICLA form can be found [here][3]. An executed OpenBMC CLA is _not_ required to accept contributions to OpenBMC forks of upstream projects, like the Linux kernel or U-Boot. @@ -32,7 +29,7 @@ Repository maintainers ought to have the following traits as recognized by a consensus of their peers: - responsible: have a continuing desire to ensure only high-quality code goes into the repo - - leadership: foster open-source aware practices such as [FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) + - leadership: foster open-source aware practices such as [FOSS][4] - expertise: typically demonstrated by significant contributions to the code or code reviews @@ -44,3 +41,8 @@ process. * email - Merging the patch. Ensure that accepted changes actually merge into OpenBMC repositories. + +[1]: https://drive.google.com/drive/folders/1Ooi0RdTcaOWF1DWFJUAJDdN7tRKde7Nl +[2]: https://github.com/openbmc/openbmc/files/1860741/OpenBMC.CCLA.pdf +[3]: https://github.com/openbmc/openbmc/files/1860742/OpenBMC.ICLA.pdf +[4]: https://en.wikipedia.org/wiki/Free_and_open-source_software |
