From d7271187ca5f96efa1a1a56066b9486c7bfc260a Mon Sep 17 00:00:00 2001 From: Gilles Peskine Date: Fri, 13 Jan 2023 12:08:50 +0100 Subject: [PATCH] Improve test and coding standards overview Make testing and coding standards separate bullet points. For the coding standards, add a "must", since some of it is now enforced on the CI. For tests, don't ask for "fully tested before submission": we don't expect contributors to run all the tests locally. Ask for basic local testing, and remind users to check CI results after submission. Signed-off-by: Gilles Peskine --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index fc79e49d2..a7bf198da 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -14,8 +14,8 @@ More details on all of these points may be found in the sections below. Coding Standards ---------------- -- We would ask that contributions conform to [our coding standards](https://mbed-tls.readthedocs.io/en/latest/kb/development/mbedtls-coding-standards/), and that contributions are fully tested before submission, as mentioned in the [Tests](#tests) and [Continuous Integration](#continuous-integration-tests) sections. -- The code should be written in a clean and readable style. +- Contributions should include tests, as mentioned in the [Tests](#tests) and [Continuous Integration](#continuous-integration-tests) sections. Please check that your contribution passes basic tests before submission, and check the CI results after making a pull request. +- The code should be written in a clean and readable style, and must follow [our coding standards](https://mbed-tls.readthedocs.io/en/latest/kb/development/mbedtls-coding-standards/). - The code should be written in a portable generic way, that will benefit the whole community, and not only your own needs. - The code should be secure, and will be reviewed from a security point of view as well.