diff options
author | Nico Huber <nico.huber@secunet.com> | 2018-11-05 13:42:35 +0100 |
---|---|---|
committer | Nico Huber <nico.h@gmx.de> | 2018-11-14 15:43:41 +0000 |
commit | c9826d79347256b7efd65075740fbf2ae9f48812 (patch) | |
tree | 33ded7ea9c07f080ef6040a1ca808c3983e49c98 /util/testing/Makefile.inc | |
parent | d72d52a7e4710e7af0b9a8279f2514c6bd339e35 (diff) | |
download | coreboot-c9826d79347256b7efd65075740fbf2ae9f48812.tar.xz |
MAINTAINERS: Clarify this is about active upstream development
<vendor> seems to be confused about the meaning of our maintainers list.
I get the feeling some use it to organize corporate internal teams and
branches, adding names to the list that don't show up in Gerrit and even
if, often don't react to reviewing requests (within months). Maybe they
even don't know that this is about coreboot.org?
To clarify this:
o Add an introductory paragraph mentioning development on coreboot.org.
o Explicitly state that maintainers should be registered to Gerrit.
o If a topic is tagged as `Supported` or `Maintained`, expect that
somebody reacts to review requests.
Change-Id: I9ee038dc5ee1f4993ba1d230ef6e737f20e2ff8a
Signed-off-by: Nico Huber <nico.huber@secunet.com>
Reviewed-on: https://review.coreboot.org/29471
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Angel Pons <th3fanbus@gmail.com>
Reviewed-by: David Guckian
Diffstat (limited to 'util/testing/Makefile.inc')
0 files changed, 0 insertions, 0 deletions