Patrick Georgi has uploaded this change for review. ( https://review.coreboot.org/c/coreboot/+/52951 )
Change subject: Documentation/gerrit: Describe core developer responsibilities ......................................................................
Documentation/gerrit: Describe core developer responsibilities
Change-Id: I8885e9fb401838229ead72b97394f3e2343aabed Signed-off-by: Patrick Georgi pgeorgi@google.com --- M Documentation/getting_started/gerrit_guidelines.md 1 file changed, 12 insertions(+), 0 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/51/52951/1
diff --git a/Documentation/getting_started/gerrit_guidelines.md b/Documentation/getting_started/gerrit_guidelines.md index a372ea8..8c91615 100644 --- a/Documentation/getting_started/gerrit_guidelines.md +++ b/Documentation/getting_started/gerrit_guidelines.md @@ -349,6 +349,18 @@ at the regular [coreboot leadership meetings](../community/forums.md) where a decision is made.
+Core developers are expected to use their privileges for the good of the +project, which includes any of their own coreboot development but also beyond +that. They should make sure that [ready changes] don't linger around needlessly +just because their authors aren't well-connected with core developers but +submit them if they went through review and generally look reasonable. They're +also expected to help clean-up breakage as a result of their submissions. + +Since the project expects some activity by core developers, long-term absence +(as in "years") can lead to removal from the group, which can easily be +reversed after they come back.
Requests for clarification and suggestions for updates to these guidelines should be sent to the coreboot mailing list at coreboot@coreboot.org. + +[ready changes]: https://review.coreboot.org/q/age:1d+project:coreboot+status:open+is:mergeab...