From 0583fe54fa42c341b8883e2a4fc4b7d3b4cb2a0c Mon Sep 17 00:00:00 2001 From: jo Date: Sun, 26 Feb 2023 13:59:14 +0100 Subject: [PATCH] docs: adapt c4 to our workflows --- CONTRIBUTING.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 205456afd..66903d052 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -6,9 +6,12 @@ LibreTime, your time is valuable, and your contributions mean a lot to us. Before any contribution, read and be prepared to adhere to our [code of conduct](https://github.com/libretime/organization/blob/main/CODE_OF_CONDUCT.md). -In addition, LibreTime follow the standardized -[C4 development process](https://rfc.zeromq.org/spec:42/c4/), in which you can -find explanation about most of the development workflows for LibreTime. +LibreTime development workflows follow the standardized [C4 development process](https://rfc.zeromq.org/spec:42/c4/), with some LibreTime specific changes: + +- [2.3. Patch Requirements](https://rfc.zeromq.org/spec/42/#23-patch-requirements) + - 7. A patch commit message MUST follow the [conventional commits specification](https://www.conventionalcommits.org/en/v1.0.0/). +- [2.4. Development Process](https://rfc.zeromq.org/spec/42/#24-development-process) + - 16. Maintainers MAY NOT merge incorrect patches. **How to contribute**