blob: 16434b9bd9dedc35e7c67b75224ed19d69394000 [file] [log] [blame]
Adrian Ambrożewicz3df84722020-01-27 17:20:38 +01001Maintainers
2===============================
3
4`MAINTAINERS` files list the maintainers and reviewers for each individual
5repository. The `MAINTAINERS` file is found within the root directory of the
6repository. This `MAINTAINERS` file is for the telemetry repository.
7
8How to use this list:
9 Find the most specific section entry (described below) that matches where
10 your change lives and add the reviewers (R) and maintainers (M) as
11 reviewers. You can use the same method to track down who knows a particular
12 code base best.
13
14 Your change/query may span multiple entries; that is okay.
15
16 If you do not find an entry that describes your request at all, someone
17 forgot to update this list; please at least file an issue or send an email
18 to a maintainer, but preferably you should just update this document.
19
20Description of section entries:
21
22 Section entries are structured according to the following scheme:
23
24 X: NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>
25 X: ...
26 .
27 .
28 .
29
30 Where REPO_NAME is the name of the repository within the OpenBMC GitHub
31 organization; FILE_PATH is a file path within the repository, possibly with
32 wildcards; X is a tag of one of the following types:
33
34 M: Denotes maintainer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
35 if omitted from an entry, assume one of the maintainers from the
36 MAINTAINERS entry.
37 R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
38 these people are to be added as reviewers for a change matching the repo
39 path.
40 F: Denotes forked from an external repository; has fields URL.
41
42 Line comments are to be denoted "# SOME COMMENT" (typical shell style
43 comment); it is important to follow the correct syntax and semantics as we
44 may want to use automated tools with this file in the future.
45
46 A change cannot be added to an OpenBMC repository without a MAINTAINER's
47 approval; thus, a MAINTAINER should always be listed as a reviewer.
48
49START OF MAINTAINERS LIST
50-------------------------
51
52M: Adrian Ambrozewicz <adrian.ambrozewicz@linux.intel.com> <aambroze!>
53R: Piotr Matuszczak <piotr.matuszczak@intel.com>