| Sandrine Bailleux | a36c5d8 | 2023-05-25 15:55:11 +0200 | [diff] [blame] | 1 | Project Maintenance Processes |
| 2 | ============================= |
| 3 | |
| 4 | Trusted Firmware-A (TF-A) project follows the generic `trustedfirmware.org |
| 5 | Project Maintenance Process`_. The present document complements it by defining |
| 6 | TF-A project-specific decisions. |
| 7 | |
| 8 | How to become a maintainer? |
| 9 | --------------------------- |
| 10 | |
| 11 | Qualifying Criteria |
| 12 | ~~~~~~~~~~~~~~~~~~~ |
| 13 | |
| 14 | To be elligible to become a maintainer for TF-A project, all criteria outlined |
| 15 | `here`_ must be fullfilled. These are: |
| 16 | |
| 17 | - Being an active member of the project for at least a couple of years. |
| 18 | |
| 19 | - Having contributed a substantial number of non-trivial and high-quality |
| 20 | patches. |
| 21 | |
| 22 | - Having reviewed a substantial number of non-trivial patches, preferably in the |
| 23 | generic layer, with high-quality constructive feedback. |
| 24 | |
| 25 | - Behaving in a professional and polite way, with the best interests of the |
| 26 | project at heart. |
| 27 | |
| 28 | - Showing a strong will to improve the project and to do the right thing, rather |
| 29 | than going for the quick and easy path. |
| 30 | |
| 31 | - Participating in design discussions on the development mailing list and during |
| 32 | TF-A tech forums calls. |
| 33 | |
| 34 | - Having appropriate bandwidth (minimum 2 hours per week) to deal with the workload. |
| 35 | |
| 36 | Election Process |
| 37 | ~~~~~~~~~~~~~~~~ |
| 38 | |
| 39 | To put an individual's name up for election, |
| 40 | |
| 41 | #. Send an email to all existing TF-A maintainers, asking whether they have any |
| 42 | objections to this individual becoming a TF-A maintainer. |
| 43 | |
| 44 | #. Give existing maintainers one calendar week to participate in the discussion. |
| 45 | |
| 46 | #. If there are objections, the existing maintainers should try to resolve them |
| 47 | amongst themselves. If they cannot, this should be escalated to the |
| 48 | trustedfirmware.org Technical Steering Commitee (TSC). |
| 49 | |
| 50 | #. If there are no (more) objections, announce the news on the TF-A mailing list |
| 51 | and update the list of maintainers on the :ref:`Project |
| 52 | Maintenance<maintainers>` page. |
| 53 | |
| 54 | .. _trustedfirmware.org Project Maintenance Process: https://developer.trustedfirmware.org/w/collaboration/project-maintenance-process/ |
| 55 | .. _here: https://developer.trustedfirmware.org/w/collaboration/project-maintenance-process/#how-to-become-a-maintainer |