docs/process/contributing.rst

24 -  Clone the Trusted Firmware-A source code on your own machine as described in
58    -  If you are submitting new files that you intend to be the code owner for
60       :ref:`code owners` file.
113    -  At least one code owner for each module modified by the patch. See the
114       list of modules and their :ref:`code owners`.
118    -  If some module has no code owner, try to identify a suitable (non-code
119       owner) reviewer. Running ``git blame`` on the module's source code can
121       the code.
128    the only code owner of a module modified by the patch. Getting a second pair
129    of eyes on the code is essential to keep up with the quality standards the
145    In the case where a code owner could not be found for a given module,
148    In addition to these various code review labels, the patch must also get a
193 and vulnerabilities in a code base, such as dereferences of NULL pointers, use
196 The TF-A source code is submitted daily to this service for analysis. Results of
202 tools on the integration branch of the TF-A code base and make them available on
207 code, it is important to maintain the appropriate TF-A CI scripts. Details of
211 configurations of various platforms in order to cover the entire source code
244 .. code:: shell
255 .. code:: shell
276 At the bare minimum, TF-A code should build without any errors for every
290 .. code:: shell
302 .. code:: shell
320    binary repository`_ if they require code that the contributor is unable or
329    component that contains all the actual code will not be accepted.
330 -  Only platform port code (i.e. in the ``plat/<vendor>`` directory) may rely on
331    binary components. Generic code must always be fully open-source.
346 …_How to Contribute Code: https://tf-ci-users-guide.readthedocs.io/en/latest/#how-to-contribute-code