| /openbmc/docs/process/ |
| H A D | subproject-maintainership.md | 28 3. If the complaint is valid the TOF notifies the current maintainers of the
29 impending addition of maintainers
30 1. The TOF identifies the set of candidate maintainers
32 maintainers
36 4. If the complaint is partially valid then the TOF must notify the maintainers
37 of the impending addition of maintainers in the event of continued
65 maintainers, through changes of roles, organisational direction or other factors
80 > creating new subprojects (git repositories), approving subproject maintainers,
90 > - Supervising subproject maintainers.
100 introduce maintainers to subprojects to ensure the community can make forward
[all …]
|
| /openbmc/linux/Documentation/maintainer/ |
| H A D | feature-and-driver-maintainers.rst | 4 Feature and driver maintainers
13 responsibilities of maintainers of a small(ish) section of the code.
29 maintainers cannot afford to wait a long time to hear from reviewers.
43 Maintainers must be subscribed and follow the appropriate subsystem-wide
48 Maintainers must know how to communicate on the list (plain text, no invasive
54 Maintainers must review *all* patches touching exclusively their drivers,
58 When there are multiple maintainers for a piece of code an ``Acked-by``
71 of the kernel as a whole. Maintainers are expected to be present and
77 Maintainers must ensure severe problems in their code reported to them
81 Maintainers furthermore should respond to reports about other kinds of
[all …]
|
| /openbmc/linux/Documentation/sphinx/ |
| H A D | maintainers_include.py | 7 maintainers-include
10 Implementation of the ``maintainers-include`` reST-directive.
15 The ``maintainers-include`` reST-directive performs extensive parsing
16 specific to the Linux kernel's standard "MAINTAINERS" file, in an
32 app.add_directive("maintainers-include", MaintainersInclude)
40 u"""MaintainersInclude (``maintainers-include``) directive"""
44 """Parse all the MAINTAINERS lines into ReST for human-readability"""
52 maintainers = False
65 if descriptions and line.startswith('Maintainers'):
71 # between the Maintainers heading and the first subsystem name.
[all …]
|
| /openbmc/u-boot/tools/ |
| H A D | genboardscfg.py | 8 Converter from Kconfig and MAINTAINERS to a board database.
38 # Status, Arch, CPU, SoC, Vendor, Board, Target, Options, Maintainers
63 *_defconfig, MAINTAINERS and Kconfig*. False otherwise.
86 not filename == 'MAINTAINERS'):
276 """The database of board status and maintainers."""
309 """Return the maintainers of the given board.
312 Maintainers of the board. If the board has two or more maintainers,
316 print >> sys.stderr, "WARNING: no maintainers for '%s'" % target
322 """Parse a MAINTAINERS file.
324 Parse a MAINTAINERS file and accumulates board status and
[all …]
|
| /openbmc/qemu/docs/devel/ |
| H A D | maintainers.rst | 3 The Role of Maintainers
6 Maintainers are a critical part of the project's contributor ecosystem.
21 The MAINTAINERS file
24 The `MAINTAINERS
25 <https://gitlab.com/qemu-project/qemu/-/blob/master/MAINTAINERS>`__
34 .. list-table:: Meaning of support status in MAINTAINERS
62 Most maintainers start by becoming subsystem reviewers. While anyone
64 MAINTAINERS file with a line like::
75 Maintainers are volunteers who put themselves forward or have been
83 the ``MAINTAINERS`` file. Sometimes this is done as part of a larger
[all …]
|
| /openbmc/linux/Documentation/process/ |
| H A D | code-of-conduct-interpretation.rst | 24 Maintainers chapter
27 The Code of Conduct uses the term "maintainers" numerous times. In the
29 subsystem, driver, or file, and is listed in the MAINTAINERS file in the
36 maintainers, and this needs some further clarifications.
38 First and foremost, it is a reasonable expectation to have maintainers
42 requirement for maintainers to unilaterally handle how other people
48 Maintainers should be willing to help when problems occur, and work with
50 the Technical Advisory Board (TAB) or other maintainers if you're
53 uncertain about approaching the TAB or any other maintainers, please
68 secondary by the expectations of contributors and maintainers.
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/ |
| H A D | distrodata.py | 44 …Summary: Test that oe-core recipes have a maintainer and entries in maintainers list have a re…
45 …(except a few special static/testing ones) should have a maintainer listed in maintainers.inc file.
46 Expected: All entries in maintainers list should have a recipe file that matches them
65 …feature = 'require conf/distro/include/maintainers.inc\nLICENSE_FLAGS_ACCEPTED += " commercial"\nP…
80 # instead of maintainers.inc
95 maintainers = tinfoil.config_data.keys()
96 for key in maintainers:
106 … maintainer assigned to them. Please add an entry to meta/conf/distro/include/maintainers.inc file.
111 The list of oe-core recipes with maintainers is empty. This may indicate that the test has regresse…
116 Unable to find recipes for the following entries in maintainers.inc:
|
| /openbmc/openbmc/poky/ |
| H A D | MAINTAINERS.md | 9 workflow works well for single or small numbers of maintainers but we have
25 Recipe Maintainers
28 See meta/conf/distro/include/maintainers.inc
30 Component/Subsystem Maintainers
46 Maintainers needed
60 Layer Maintainers needed
65 Shadow maintainers/development needed
|
| /openbmc/linux/Documentation/driver-api/media/ |
| H A D | maintainer-entry-profile.rst | 22 OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS maintainers
23 (see the MAINTAINERS file). So, changes there must be reviewed
33 maintainership model is to have sub-maintainers that have a broad
34 knowledge of a specific aspect of the subsystem. It is the sub-maintainers'
63 Media maintainers
68 sub-maintainers), and another senior developer responsible for the
70 media maintainers do the review.
72 The media maintainers that work on specific areas of the subsystem are:
92 Media maintainers may delegate a patch to other media maintainers as needed.
100 reviewed by the Device Tree maintainers. So, DT maintainers should be
[all …]
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | MIGRATION.txt | 14 The subsystem itself has been converted and maintainers should submit patches
25 and maintainers should submit patches switching over to using CONFIG_DM_USB and
35 and maintainers should submit patches switching over to using CONFIG_AHCI and
44 In concert with maintainers migrating their block device usage to the
55 Board Maintainers should submit the patches for enabling DM_SPI and DM_SPI_FLASH
95 The PCI subsystem has supported driver model since mid 2015. Maintainers should
104 The video subsystem has supported driver model since early 2016. Maintainers
|
| /openbmc/bmcweb/ |
| H A D | OWNERS | 1 # Below lists the current bmcweb maintainers. bmcweb is used in a number of
4 # made within the codebase, maintainers on this list are expected to:
10 # It is expected that bmcweb maintainers participate on a majority of code
11 # reviews, and although maintainers may work with each other to segment the
12 # responsibilities into sub-parts the codebase, it is expected that maintainers
25 # for resources implemented within the Redfish standard. bmcweb maintainers
51 # forms a component of the alleged attack. Maintainers should be prepared to
61 # the above requirements being met, and the existing maintainers will happily
|
| /openbmc/u-boot/doc/ |
| H A D | README.kconfig | 95 Status -> "S:" entry of MAINTAINERS
103 Maintainers -> "M:" entry of MAINTAINERS
124 [4] Add a MAINTAINERS file
125 It is generally placed at board/<board>/MAINTAINERS or
126 board/<vendor>/<board>/MAINTAINERS
135 [4] Update MAINTAINERS if necessary
145 Board maintainers are expected to implement proper Kconfig options
|
| /openbmc/linux/Documentation/devicetree/bindings/ |
| H A D | submitting-patches.rst | 38 and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify
39 all of the DT maintainers.
70 II. For kernel maintainers
74 the devicetree maintainers for guidance. This will help them prioritize
79 maintainers after a few weeks, go ahead and take it.
95 devicetree maintainers overrules this document. In that situation, a patch
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-kernel/linux/files/corstone1000/ |
| H A D | 0003-dt-bindings-remoteproc-Add-Arm-remoteproc.patch | 12 MAINTAINERS | 1 +
30 +maintainers:
91 diff --git a/MAINTAINERS b/MAINTAINERS
93 --- a/MAINTAINERS
94 +++ b/MAINTAINERS
|
| /openbmc/linux/scripts/ |
| H A D | parse-maintainers.pl | 7 my $input_file = "MAINTAINERS";
8 my $output_file = "MAINTAINERS.new";
33 --input => MAINTAINERS file to read (default: MAINTAINERS)
34 --output => sorted MAINTAINERS file to write (default: MAINTAINERS.new)
35 --section => new sorted MAINTAINERS file to write to (default: SECTION.new)
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | xfs-maintainer-entry-profile.rst | 40 entry in the kernel MAINTAINERS file.
61 and fstests MAINTAINERS files.
69 the XFS section of the fstests MAINTAINERS file.
76 the kernel MAINTAINERS file.
87 the kernel MAINTAINERS file.
100 ``M:`` entry in the MAINTAINERS file for that LTS tree.
113 the maintainers of XFS and the relevant subsystems to decide how to
185 To find reviewers, either consult the MAINTAINERS file, or ask
|
| /openbmc/linux/Documentation/translations/sp_SP/ |
| H A D | index.rst | 24 :ref:`linux_doc` es altamente improbable. Los maintainers y colaboradores
37 también a las traducciones. Los maintainers de las traducciones aceptan
56 los maintainers pueden utilizar el español con el que dichos maintainers se
59 pero en caso de duda se puede consultar a los maintainers.
|
| /openbmc/phosphor-host-ipmid/docs/ |
| H A D | contributing.md | 85 MAINTAINERS file to determine who needs to approve your review in order for your
87 Gerrit; reviewers are not currently added automatically. Maintainers may not see
101 the maintainers (addresses available in MAINTAINERS file) - but a reasonable
105 be approved; please check the MAINTAINERS file for the full list ("Change
108 The maintainers' job is to ensure that incoming patches are as correct and easy
110 contributors can come and go easily - so maintainers tend not to put stock in
|
| /openbmc/openpower-inventory-upload/ |
| H A D | MAINTAINERS | 3 your change lives and add the reviewers (R) and maintainers (M) as
28 if omitted from an entry, assume one of the maintainers from the
29 MAINTAINERS entry.
42 START OF MAINTAINERS LIST
|
| /openbmc/openpower-logging/ |
| H A D | MAINTAINERS | 3 your change lives and add the reviewers (R) and maintainers (M) as
28 if omitted from an entry, assume one of the maintainers from the
29 MAINTAINERS entry.
42 START OF MAINTAINERS LIST
|
| /openbmc/phosphor-pcie-presence/ |
| H A D | MAINTAINERS | 3 your change lives and add the reviewers (R) and maintainers (M) as
28 if omitted from an entry, assume one of the maintainers from the
29 MAINTAINERS entry.
42 START OF MAINTAINERS LIST
|
| /openbmc/openpower-sbe-interface/ |
| H A D | MAINTAINERS | 3 your change lives and add the reviewers (R) and maintainers (M) as
28 if omitted from an entry, assume one of the maintainers from the
29 MAINTAINERS entry.
42 START OF MAINTAINERS LIST
|
| /openbmc/google-ipmi-sys/ |
| H A D | MAINTAINERS | 3 your change lives and add the reviewers (R) and maintainers (M) as
28 if omitted from an entry, assume one of the maintainers from the
29 MAINTAINERS entry.
42 START OF MAINTAINERS LIST
|
| /openbmc/pyphosphor/ |
| H A D | MAINTAINERS | 3 your change lives and add the reviewers (R) and maintainers (M) as
28 if omitted from an entry, assume one of the maintainers from the
29 MAINTAINERS entry.
42 START OF MAINTAINERS LIST
|
| /openbmc/phosphor-mboxd/ |
| H A D | MAINTAINERS | 3 your change lives and add the reviewers (R) and maintainers (M) as
28 if omitted from an entry, assume one of the maintainers from the
29 MAINTAINERS entry.
42 START OF MAINTAINERS LIST
|