|
We have a long history with maintainers files and good and bad experiences. There
are people who'd like to see a kernel style machine readable file which defines
exactly which people should be reviewing which areas. In practise, the files we
do have struggle to stay up to date (e.g. the recipe maintainers file) and such
a file would also cause conflicts of expectations where person X would want to be
cc'd on patches touching file Y and want a revert if they hadn't acked it. We also
don't have clearly defined boundaries in some areas, e.g. toolchain.
We have a wide peer review system and nobody gets to make changes without that
review, even myself as the lead for OE-Core/Bitbake.
I do want to recognise that some people are key experts on particular areas and
hightlight that their views on those areas do carry weight. With that also comes
repsonsibility to help try and figure out bugs, help with review and so on.
I've tried to strike a balance with this file to detail who some of the experts
for particular areas are and to also highlight where we don't have coverage and
that there are opportunities.
I've tried to put the file in the wider context of the project, not just OE-Core.
It is in a repo rather than a wiki so we have visibility to changes through the
change control process.
I'm sure I will miss people, sorry, it is inevitable when you try and make a
list. There may be people who want to step down and don't want to be in this
role, I'm also hoping there are going to be some new volunteers to help in some
areas. Please do send follow up updates, this patch is really meant to help get
us started.
Volunteers to maintainer specific areas of the project are very welcome and
feel free to reach out to ask about areas or getting started and working towards
an official maintainer role (e.g. help with bug fixing).
(From OE-Core rev: b629978efae35d5ea3821f4375bc0d8228b6cc26)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|