Home Explore Help
Sign In
OWEALs
/
arm-trusted-firmware
mirror of https://github.com/ARM-software/arm-trusted-firmware
2
0
Fork 0
Files Issues 1 Wiki
Branch: master
Branches Tags
arm-trusted-fir...
/
docs
/
process
/
maintenance.rst

maintenance.rst 2.1 KB
Permalink History Raw

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455 
  1. Project Maintenance Processes
    2. 

  2. =============================
    3. 

  3. 

  4. Trusted Firmware-A (TF-A) project follows the generic `trustedfirmware.org
    5. 

  5. Project Maintenance Process`_. The present document complements it by defining
    6. 

  6. TF-A project-specific decisions.
    7. 

  7. 

  8. How to become a maintainer?
    9. 

  9. ---------------------------
    10. 

  10. 

  11. Qualifying Criteria
    12. 

  12. ~~~~~~~~~~~~~~~~~~~
    13. 

  13. 

  14. To be elligible to become a maintainer for TF-A project, all criteria outlined
    15. 

  15. `here`_ must be fullfilled. These are:
    16. 

  16. 

  17. - Being an active member of the project for at least a couple of years.
    18. 

  18. 

  19. - Having contributed a substantial number of non-trivial and high-quality
    20. 

  20.   patches.
    21. 

  21. 

  22. - Having reviewed a substantial number of non-trivial patches, preferably in the
    23. 

  23.   generic layer, with high-quality constructive feedback.
    24. 

  24. 

  25. - Behaving in a professional and polite way, with the best interests of the
    26. 

  26.   project at heart.
    27. 

  27. 

  28. - Showing a strong will to improve the project and to do the right thing, rather
    29. 

  29.   than going for the quick and easy path.
    30. 

  30. 

  31. - Participating in design discussions on the development mailing list and during
    32. 

  32.   TF-A tech forums calls.
    33. 

  33. 

  34. - Having appropriate bandwidth (minimum 2 hours per week) to deal with the workload.
    35. 

  35. 

  36. Election Process
    37. 

  37. ~~~~~~~~~~~~~~~~
    38. 

  38. 

  39. To put an individual's name up for election,
    40. 

  40. 

  41. #. Send an email to all existing TF-A maintainers, asking whether they have any
    42. 

  42.    objections to this individual becoming a TF-A maintainer.
    43. 

  43. 

  44. #. Give existing maintainers one calendar week to participate in the discussion.
    45. 

  45. 

  46. #. If there are objections, the existing maintainers should try to resolve them
    47. 

  47.    amongst themselves. If they cannot, this should be escalated to the
    48. 

  48.    trustedfirmware.org Technical Steering Commitee (TSC).
    49. 

  49. 

  50. #. If there are no (more) objections, announce the news on the TF-A mailing list
    51. 

  51.    and update the list of maintainers on the :ref:`Project
    52. 

  52.    Maintenance<maintainers>` page.
    53. 

  53. 

  54. .. _trustedfirmware.org Project Maintenance Process: https://trusted-firmware-docs.readthedocs.io/en/latest/generic_processes/project_maintenance_process.html
    55. 

  55. .. _here: https://trusted-firmware-docs.readthedocs.io/en/latest/generic_processes/project_maintenance_process.html#how-to-become-a-maintainer
    56.