Add MAINTAINERS.md file

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).

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>

1 files changed, 71 insertions, 0 deletions

diff --git a/MAINTAINERS.md b/MAINTAINERS.md
new file mode 100644
index 0000000000..604d800f63
--- /dev/null
+++ b/MAINTAINERS.md
@@ -0,0 +1,71 @@
+OpenEmbedded-Core and Yocto Project Maintainer Information
+==========================================================
+
+OpenEmbedded and Yocto Project work jointly together to maintain the metadata,
+layers, tools and sub-projects that make up their ecosystems.
+
+The projects operate through collaborative development. This currently takes
+place on mailing lists for many components as the "pull request on github"
+workflow works well for single or small numbers of maintainers but we have
+a large number, all with different specialisms and benefit from the mailing
+list review process. Changes therefore undergo peer review through mailing
+lists in many cases.
+
+This file aims to acknowledge people with specific skills/knowledge/interest
+both to recognise their contributions but also empower them to help lead and
+curate those components. Where we have people with specialist knowledge in
+particular areas, during review patches/feedback from these people in these
+areas would generally carry weight.
+
+This file is maintained in OE-Core but may refer to components that are separate
+to it if that makes sense in the context of maintainership. The README of specific
+layers and components should ultimately be definitive about the patch process and
+maintainership for the component.
+
+Recipe Maintainers
+------------------
+
+See meta/conf/distro/include/maintainers.inc
+
+Component/Subsystem Maintainers
+-------------------------------
+
+* Kernel (inc. linux-yocto, perf): Bruce Ashfield
+* Reproducible Builds: Joshua Watt
+* Toaster: David Reyna
+* Hash-Equivalence: Joshua Watt
+* Recipe upgrade infrastructure: Alex Kanavin
+* Toolchain: Khem Raj
+* ptest-runner: Aníbal Limón
+* opkg: Alex Stewart
+
+Maintainers needed
+------------------
+
+* Pseudo
+* Layer Index
+* recipetool
+* QA framework/automated testing
+* error reporting system/web UI
+* wic
+* Patchwork
+* Patchtest
+* Prelink-cross
+* Matchbox
+* Sato
+* devtool
+* eSDK
+* Autobuilder
+
+Layer Maintainers needed
+------------------------
+
+* meta-gplv2 (ideally new strategy but active maintainer welcome)
+
+Shadow maintainers/development needed
+--------------------------------------
+
+* toaster
+* bitbake
+
+