Introduce MAINTAINERS file

The MAINTAINERS file is a list of people who take special care of
specific things and places of the tree. Also, it gives an overview
about which people are good points for contact in case of questions
appear.

In addition to that, this file is hooked up to Gerrit so that when a
patch is pushed, which touches any of these places, the related people
are added to reviewers or CC. This is done by a tool which looks up the
changed places in the MAINTAINERS file.

To clarify: This MAINTAINERS file does *not* mean that any reviews,
comments or thoughts from other people not listed there aren't welcome
anymore. We just want to make sure that patches don't get lost.

The initial file was copied from the coreboot repository. The format is
the same as the one which is used for coreboot.

Signed-off-by: Felix Singer <felixsinger@posteo.net>
Change-Id: Ic9a302055d941eeb2499a84c62c5fe1d4c9944cf
Reviewed-on: https://review.coreboot.org/c/flashrom/+/65569
Reviewed-by: Edward O'Callaghan <quasisec@chromium.org>
Reviewed-by: Peter Marheine <pmarheine@chromium.org>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Angel Pons <th3fanbus@gmail.com>
Reviewed-by: Anastasia Klimchuk <aklm@chromium.org>
Reviewed-by: Thomas Heijligen <src@posteo.de>

MAINTAINERS

@@ -0,0 +1,81 @@
+
+
+		    List of upstream flashrom maintainers
+
+This represents the list of maintainers that work on the upstream flashrom
+code base (on flashrom.org).  Maintainers are assigned to topics and when
+applicable to subtrees of the source tree. You'll find some subtrees that
+don't have a maintainer. If you are looking for reviewers for such a subtree,
+it's often a good choice to look at the git history to see who worked on
+it last.
+
+Please try to follow our [development guidelines]. This will make things
+easier on the maintainers. Not all of these guidelines matter for every
+trivial patch. So apply some common sense.
+
+[development guidelines]: https://www.flashrom.org/Development_Guidelines
+
+Happy hacking!
+
+Descriptions of section entries:
+
+	M: Maintainer: FullName <address@domain>
+	   Must be registered to Gerrit (https://review.coreboot.org) and
+	   must have experience with upstream flashrom development.
+	R: Designated reviewer: FullName <address@domain>
+	   These reviewers are CCed on patches.
+	L: Mailing list that is relevant to this area
+	W: Web-page with status/info
+	S: Status, one of the following:
+	   Supported:	Someone is continuously paid to look after this and
+			a reaction to review requests can be expected
+			within a few days, a month at most.
+	   Maintained:	Someone actually looks after it and a reaction to
+			review requests can usually be expected within a
+			few weeks.
+	   Odd Fixes:	It has a maintainer but they don't have time to do
+			much other than throw the odd patch in. See below..
+	   Orphan:	No current maintainer [but maybe you could take the
+			role as you write your new code].
+	   Obsolete:	Old code. Something tagged obsolete generally means
+			it has been replaced by a better system and you
+			should be using that.
+	F: Files and directories with wildcard patterns.
+	   A trailing slash includes all files and subdirectory files.
+	   F:	drivers/net/	all files in and below drivers/net
+	   F:	drivers/net/*	all files in drivers/net, but not below
+	   F:	*/net/*		all files in "any top level directory"/net
+	   One pattern per line.  Multiple F: lines acceptable.
+	N: Files and directories with regex patterns.
+	   N:	[^a-z]tegra	all files whose path contains the word tegra
+	   One pattern per line.  Multiple N: lines acceptable.
+	   scripts/get_maintainer.pl has different behavior for files that
+	   match F: pattern and matches of N: patterns.  By default,
+	   get_maintainer will not look at git log history when an F: pattern
+	   match occurs.  When an N: match occurs, git log history is used
+	   to also notify the people that have git commit signatures.
+	X: Files and directories that are NOT maintained, same rules as F:
+	   Files exclusions are tested before file matches.
+	   Can be useful for excluding a specific subdirectory, for instance:
+	   F:	net/
+	   X:	net/ipv6/
+	   matches all files in and below net excluding net/ipv6/
+	K: Keyword perl extended regex pattern to match content in a
+	   patch or file.  For instance:
+	   K: of_get_profile
+	      matches patches or files that contain "of_get_profile"
+	   K: \b(printk|pr_(info|err))\b
+	      matches patches or files that contain one or more of the words
+	      printk, pr_info or pr_err
+	   One regex pattern per line.  Multiple K: lines acceptable.
+
+Note: The categories and topics in this list are meant to remain in alphabetical
+      order. Please keep them sorted when you change them.
+
+Maintainers List (try to look for most precise areas first)
+
+		-----------------------------------
+
+################################################################################
+# First category
+################################################################################