From c69da57d63ca11aaf8523020a3d8eeaacdbf91d8 Mon Sep 17 00:00:00 2001 From: Patrick Georgi Date: Wed, 27 Oct 2021 21:36:45 +0200 Subject: [PATCH] Documentation: Open up avenue for codifying our best practices Change-Id: I3a2612ae64ecea2d1d7ecb695215bc50dccb1b19 Signed-off-by: Patrick Georgi Reviewed-on: https://review.coreboot.org/c/coreboot/+/58663 Reviewed-by: Arthur Heymans Reviewed-by: Martin Roth Reviewed-by: Paul Menzel Reviewed-by: Angel Pons Tested-by: build bot (Jenkins) --- Documentation/index.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Documentation/index.md b/Documentation/index.md index c518c5085b..bdfb6bf622 100644 --- a/Documentation/index.md +++ b/Documentation/index.md @@ -45,6 +45,12 @@ to the payload), but it's also a value that is deeply ingrained in the project. We fearlessly rip out parts of the architecture and remodel it when a better way of doing the same was identified. +That said, since there are attempts to coerce coreboot to move in various +directions by outside "standardization", long-established practices of +coreboot as well as aligned projects can be documented as best practices, +making them standards in their own right. However we reserve the right to +retire them as the landscape shifts around us. + ### One tree for everything Another difference to various other firmware projects is that we try