1 | Maintainers |
---|
2 | =========== |
---|
3 | This file contains information about people who are permitted to make |
---|
4 | changes to RTEMS and its associated components and add-ons. Please do |
---|
5 | not contact the people in this file directly to report problems with RTEMS. |
---|
6 | |
---|
7 | For general information about RTEMS, please visit: http://www.rtems.org |
---|
8 | |
---|
9 | To report problems in RTEMS, please visit: http://www.rtems.org/bugs.html |
---|
10 | |
---|
11 | RTEMS is maintained by collection of volunteers. RTEMS is a very |
---|
12 | broad and diverse project which requires expertise in many areas. |
---|
13 | This breadth of knowledge exceeds the capabilities of any |
---|
14 | single person. Each volunteer has areas of expertise where they |
---|
15 | are more comfortable but each is capable of making technical |
---|
16 | decisions across the entirety of RTEMS. |
---|
17 | |
---|
18 | Blanket Write Privileges are granted to experienced RTEMS developers |
---|
19 | who can be trusted to distinguish between changes which require |
---|
20 | others to review, require a problem report, or can be safely committed |
---|
21 | with limited review. |
---|
22 | |
---|
23 | Write After Approval is granted to experienced but also trusted |
---|
24 | RTEMS developers. These developers may be less familiar with |
---|
25 | the breadth of RTEMS. Developers with write after approval need |
---|
26 | to submit their patches for review. Once the patches have been |
---|
27 | approved by a developer with Blanket Write Privileges, the patches |
---|
28 | may be checked in. |
---|
29 | |
---|
30 | Localized Write Permission is for developers who have primary |
---|
31 | responsibility for a port and all associated BSPs, a BSP, or other |
---|
32 | specific aspects of RTEMS. These folks are allowed to make changes to |
---|
33 | areas they maintain and related documentation, web pages, and test cases |
---|
34 | without approval from anyone else, and approve other people's changes |
---|
35 | in those areas. They must get approval for changes elsewhere in RTEMS. |
---|
36 | |
---|
37 | Blanket Write Privileges |
---|
38 | ======================== |
---|
39 | Jennifer Averett jennifer.averett@OARcorp.com |
---|
40 | Ralf Corsepius ralf.corsepius@rtems.org |
---|
41 | Thomas Doefler Thomas.Doerfler@embedded-brains.de |
---|
42 | Sebastian Huber sebastian.huber@embedded-brains.de |
---|
43 | Chris Johns chrisj@rtems.org |
---|
44 | Eric Norum eric.norum@rtems.org |
---|
45 | Joel Sherrill joel.sherrill@OARcorp.com |
---|
46 | |
---|
47 | Write After Approval |
---|
48 | ==================== |
---|
49 | Gedare Bloom gedare@rtems.org |
---|
50 | |
---|
51 | Localized Write Permission |
---|
52 | ========================== |
---|
53 | sparc64 Gedare Bloom gedare@rtems.org |
---|
54 | |
---|