source: rtems/MAINTAINERS @ c15842d

Last change on this file since c15842d was f91f30f6, checked in by Karel Gardas <karel@…>, on 05/26/22 at 18:40:34

MAINTAINERS: Add myself to Write After Approval

Add myself also to Localized Write Permission for x86_64.

  • Property mode set to 100644
File size: 3.3 KB
Line 
1Maintainers
2===========
3This file contains information about people who are permitted to make
4changes to RTEMS and its associated components and add-ons.  Please do
5not contact the people in this file directly to report problems with RTEMS.
6
7For general information about RTEMS, please visit: http://www.rtems.org
8
9To report problems in RTEMS, please visit: http://www.rtems.org/bugs.html
10
11RTEMS is maintained by collection of volunteers.  RTEMS is a very
12broad and diverse project which requires expertise in many areas.
13This breadth of knowledge exceeds the capabilities of any
14single person. Each volunteer has areas of expertise where they
15are more comfortable but each is capable of making technical
16decisions across the entirety of RTEMS.
17
18Blanket Write Privileges are granted to experienced RTEMS developers
19who can be trusted to distinguish between changes which require
20others to review, require a problem report, or can be safely committed
21with limited review.
22
23Write After Approval is granted to experienced but also trusted
24RTEMS developers.  These developers may be less familiar with
25the breadth of RTEMS.  Developers with write after approval need
26to submit their patches for review.  Once the patches have been approved by a
27developer with Blanket Write Privileges, the patches may be checked in.
28A BSP-specific patch may be checked in three work days after sending it to
29devel@rtems.org in case nobody explicitly rejected the patch.
30
31Localized Write Permission is for developers who have primary
32responsibility for a port and all associated BSPs, a BSP, or other
33specific aspects of RTEMS.  These folks are allowed to make changes to
34areas they maintain and related documentation, web pages, and test cases
35without approval from anyone else, and approve other people's changes
36in those areas. They must get approval for changes elsewhere in RTEMS.
37
38Emeritus Maintainers are those developers who have had Blanket Write
39Privileges in the past and who retain the honorary title of maintainer
40with the RTEMS Project.
41
42Blanket Write Privileges
43========================
44Sebastian Huber            sebastian.huber@embedded-brains.de
45Chris Johns                chrisj@rtems.org
46Joel Sherrill              joel.sherrill@OARcorp.com
47Gedare Bloom               gedare@rtems.org
48
49Write After Approval
50====================
51Daniel Hellstrom           daniel@gaisler.com
52Ben Gras                   beng@rtems.org
53Pavel Pisa                 ppisa@pikron.com
54Christian Mauderer         christian.mauderer@embedded-brains.de
55Hesham Almatary            heshamelmatary@gmail.com
56Vijay Kumar Banerjee       vijay@rtems.org
57Jan Sommer                 jan@rtems.org
58Karel Gardas               karel@functional.vision
59
60Localized Write Permission
61==========================
62sparc                      Daniel Hellstrom (daniel@gaisler.com)
63beagle                     Ben Gras (beng@rtems.org)
64tms570                     Pavel Pisa (pisa@cmp.felk.cvut.cz)
65raspberrypi                Pavel Pisa (pisa@cmp.felk.cvut.cz)
66x86_64                     Karel Gardas (karel@functional.vision)
67beagle                     Vijay Kumar Banerjee (vijay@rtems.org)
68
69Emeritus Maintainers
70====================
71Jennifer Averett           jennifer.averett@OARcorp.com
72Thomas Doefler             Thomas.Doerfler@embedded-brains.de
73Eric Norum                 eric@norum.ca
74
Note: See TracBrowser for help on using the repository browser.