docs/devel/maintainers.rst

11   - reviewing patches and suggesting changes
12   - collecting patches and preparing pull requests
13   - tending to the long term health of their area
14   - participating in other project activities
22 --------------------
25 <https://gitlab.com/qemu-project/qemu/-/blob/master/MAINTAINERS>`__
29 patches that touch their area of code.
31 The file also describes the status of the area of code to give an idea
34 .. list-table:: Meaning of support status in MAINTAINERS
36    :header-rows: 1
38    * - Status
39      - Meaning
40    * - Supported
41      - Someone is actually paid to look after this.
42    * - Maintained
43      - Someone actually looks after it.
44    * - Odd Fixes
45      - It has a maintainer but they don't have time to do
47    * - Orphan
48      - No current maintainer.
49    * - Obsolete
50      - Old obsolete code, should use something else.
54 the code comes with no warranty and the project makes no guarantees
60 -------------------
63 is welcome to review code on the mailing list getting added to the
68 marks you as a 'designated reviewer' - expected to provide regular
73 ---------------------
76 asked by others to keep an eye on an area of code. They have generally
77 demonstrated to the community, usually via contributions and code
82 The process is simple - simply send a patch to the list that updates
84 series when a new sub-system is being added to the code base. This can
89 sure your GPG key is signed.
97 coming from the maintainer. If your key is not already signed by
101 key signed by an attendee. Key signing requires meeting another