source: rtems/MAINTAINERS @ 2ce44de

Last change on this file since 2ce44de was e40c589, checked in by Sebastian Huber <sebastian.huber@…>, on Mar 20, 2018 at 12:43:07 PM

MAINAINERS: Add rule for BSP-specific patches

  • Property mode set to 100644
File size: 2.8 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
38Blanket Write Privileges
39========================
40Jennifer Averett           jennifer.averett@OARcorp.com
41Thomas Doefler             Thomas.Doerfler@embedded-brains.de
42Sebastian Huber            sebastian.huber@embedded-brains.de
43Chris Johns                chrisj@rtems.org
44Joel Sherrill              joel.sherrill@OARcorp.com
45Gedare Bloom               gedare@rtems.org
46
47Write After Approval
48====================
49Daniel Hellstrom           daniel@gaisler.com
50Ben Gras                   beng@rtems.org
51Martin Galvan              martin.galvan@tallertechnologies.com
52Pavel Pisa                 ppisa@pikron.com
53Christian Mauderer         christian.mauderer@embedded-brains.de
54
55Localized Write Permission
56==========================
57sparc                      Daniel Hellstrom (daniel@gaisler.com)
58beagle                     Ben Gras (beng@rtems.org)
59tms570                     Pavel Pisa (pisa@cmp.felk.cvut.cz)
60raspberrypi                Pavel Pisa (pisa@cmp.felk.cvut.cz)
61
Note: See TracBrowser for help on using the repository browser.