[dfd3132] | 1 | Maintainers |
---|
| 2 | =========== |
---|
[4689f30c] | 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 | |
---|
[e40c589] | 23 | Write After Approval is granted to experienced but also trusted |
---|
[4689f30c] | 24 | RTEMS developers. These developers may be less familiar with |
---|
| 25 | the breadth of RTEMS. Developers with write after approval need |
---|
[e40c589] | 26 | to submit their patches for review. Once the patches have been approved by a |
---|
| 27 | developer with Blanket Write Privileges, the patches may be checked in. |
---|
| 28 | A BSP-specific patch may be checked in three work days after sending it to |
---|
| 29 | devel@rtems.org in case nobody explicitly rejected the patch. |
---|
[4689f30c] | 30 | |
---|
| 31 | Localized Write Permission is for developers who have primary |
---|
| 32 | responsibility for a port and all associated BSPs, a BSP, or other |
---|
| 33 | specific aspects of RTEMS. These folks are allowed to make changes to |
---|
| 34 | areas they maintain and related documentation, web pages, and test cases |
---|
| 35 | without approval from anyone else, and approve other people's changes |
---|
| 36 | in those areas. They must get approval for changes elsewhere in RTEMS. |
---|
| 37 | |
---|
| 38 | Blanket Write Privileges |
---|
| 39 | ======================== |
---|
| 40 | Jennifer Averett jennifer.averett@OARcorp.com |
---|
| 41 | Thomas Doefler Thomas.Doerfler@embedded-brains.de |
---|
| 42 | Sebastian Huber sebastian.huber@embedded-brains.de |
---|
[6dde1121] | 43 | Chris Johns chrisj@rtems.org |
---|
[4689f30c] | 44 | Joel Sherrill joel.sherrill@OARcorp.com |
---|
[c87ff97] | 45 | Gedare Bloom gedare@rtems.org |
---|
[4689f30c] | 46 | |
---|
| 47 | Write After Approval |
---|
| 48 | ==================== |
---|
[724eb8c4] | 49 | Daniel Hellstrom daniel@gaisler.com |
---|
[3b8e395] | 50 | Ben Gras beng@rtems.org |
---|
[8dcb8837] | 51 | Pavel Pisa ppisa@pikron.com |
---|
[9704efb4] | 52 | Christian Mauderer christian.mauderer@embedded-brains.de |
---|
[43a6991] | 53 | Hesham Almatary heshamelmatary@gmail.com |
---|
[486829b2] | 54 | Amaan Cheval amaan@rtems.org |
---|
[4689f30c] | 55 | |
---|
| 56 | Localized Write Permission |
---|
| 57 | ========================== |
---|
[f04dff4] | 58 | sparc Daniel Hellstrom (daniel@gaisler.com) |
---|
[3b8e395] | 59 | beagle Ben Gras (beng@rtems.org) |
---|
[8dcb8837] | 60 | tms570 Pavel Pisa (pisa@cmp.felk.cvut.cz) |
---|
| 61 | raspberrypi Pavel Pisa (pisa@cmp.felk.cvut.cz) |
---|
[486829b2] | 62 | x86_64 Amaan Cheval (amaan@rtems.org) |
---|
[9b55ef5] | 63 | |
---|