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