mirror of
https://github.com/ARM-software/arm-trusted-firmware.git
synced 2025-04-16 09:34:18 +00:00
doc: Stop advising the creation of Phabricator issues
We have noticed that Phabricator (the ticketing system on tf.org [1]) has far less visibility within the community than the mailing list [2]. For this reason, let's drop usage of Phabricator for anything else than bug reports. For the rest, advise contributors to start a discussion on the mailing list, where they are more likely to get feedback. [1] https://developer.trustedfirmware.org/project/board/1/ [2] https://lists.trustedfirmware.org/mailman/listinfo/tf-a Change-Id: I7d2d3d305ad0a0f8aacc2a2f25eb5ff429853a3f Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>
This commit is contained in:
parent
b3385aa08e
commit
a88b3c296a
3 changed files with 21 additions and 17 deletions
|
@ -27,9 +27,9 @@ You can see a `summary of all the lists`_ on the TrustedFirmware.org website.
|
||||||
Issue Tracker
|
Issue Tracker
|
||||||
^^^^^^^^^^^^^
|
^^^^^^^^^^^^^
|
||||||
|
|
||||||
Specific issues may be raised using the `issue tracker`_ on the
|
Bug reports may be filed on the `issue tracker`_ on the TrustedFirmware.org
|
||||||
TrustedFirmware.org website. Using this tracker makes it easy for the
|
website. Using this tracker gives everyone visibility of the known issues in
|
||||||
maintainers to prioritise and respond to your ticket.
|
TF-A.
|
||||||
|
|
||||||
Arm Licensees
|
Arm Licensees
|
||||||
^^^^^^^^^^^^^
|
^^^^^^^^^^^^^
|
||||||
|
@ -44,4 +44,4 @@ via their partner managers.
|
||||||
|
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
*Copyright (c) 2019, Arm Limited. All rights reserved.*
|
*Copyright (c) 2019-2020, Arm Limited. All rights reserved.*
|
||||||
|
|
|
@ -6,12 +6,16 @@ Getting Started
|
||||||
|
|
||||||
- Make sure you have a Github account and you are logged on both
|
- Make sure you have a Github account and you are logged on both
|
||||||
`developer.trustedfirmware.org`_ and `review.trustedfirmware.org`_.
|
`developer.trustedfirmware.org`_ and `review.trustedfirmware.org`_.
|
||||||
- Create an `issue`_ for your work if one does not already exist. This gives
|
|
||||||
everyone visibility of whether others are working on something similar.
|
|
||||||
|
|
||||||
- If you intend to include Third Party IP in your contribution, please
|
- If you plan to contribute a major piece of work, it is usually a good idea to
|
||||||
raise a separate `issue`_ for this and ensure that the changes that
|
start a discussion around it on the mailing list. This gives everyone
|
||||||
include Third Party IP are made on a separate topic branch.
|
visibility of what is coming up, you might learn that somebody else is
|
||||||
|
already working on something similar or the community might be able to
|
||||||
|
provide some early input to help shaping the design of the feature.
|
||||||
|
|
||||||
|
If you intend to include Third Party IP in your contribution, please mention
|
||||||
|
it explicitly in the email thread and ensure that the changes that include
|
||||||
|
Third Party IP are made in a separate patch (or patch series).
|
||||||
|
|
||||||
- Clone `Trusted Firmware-A`_ on your own machine as described in
|
- Clone `Trusted Firmware-A`_ on your own machine as described in
|
||||||
:ref:`prerequisites_get_source`.
|
:ref:`prerequisites_get_source`.
|
||||||
|
@ -29,8 +33,7 @@ Making Changes
|
||||||
Makefile target is provided for convenience.
|
Makefile target is provided for convenience.
|
||||||
|
|
||||||
- Keep the commits on topic. If you need to fix another bug or make another
|
- Keep the commits on topic. If you need to fix another bug or make another
|
||||||
enhancement, please create a separate `issue`_ and address it on a separate
|
enhancement, please address it on a separate topic branch.
|
||||||
topic branch.
|
|
||||||
- Avoid long commit series. If you do have a long series, consider whether
|
- Avoid long commit series. If you do have a long series, consider whether
|
||||||
some commits should be squashed together or addressed in a separate topic.
|
some commits should be squashed together or addressed in a separate topic.
|
||||||
- Make sure your commit messages are in the proper format. If a commit fixes
|
- Make sure your commit messages are in the proper format. If a commit fixes
|
||||||
|
|
|
@ -21,12 +21,12 @@ Although we try to keep TF-A secure, we can only do so with the help of the
|
||||||
community of developers and security researchers.
|
community of developers and security researchers.
|
||||||
|
|
||||||
If you think you have found a security vulnerability, please **do not** report
|
If you think you have found a security vulnerability, please **do not** report
|
||||||
it in the `issue tracker`_. Instead, please follow the `TrustedFirmware.org
|
it in the `issue tracker`_ or on the `mailing list`_. Instead, please follow the
|
||||||
security incident process`_. One of the goals of this process is to ensure
|
`TrustedFirmware.org security incident process`_. One of the goals of this
|
||||||
providers of products that use TF-A have a chance to consider the implications
|
process is to ensure providers of products that use TF-A have a chance to
|
||||||
of the vulnerability and its remedy before it is made public. As such, please
|
consider the implications of the vulnerability and its remedy before it is made
|
||||||
follow the disclosure plan outlined in the process. We do our best to respond
|
public. As such, please follow the disclosure plan outlined in the process. We
|
||||||
and fix any issues quickly.
|
do our best to respond and fix any issues quickly.
|
||||||
|
|
||||||
Afterwards, we encourage you to write-up your findings about the TF-A source
|
Afterwards, we encourage you to write-up your findings about the TF-A source
|
||||||
code.
|
code.
|
||||||
|
@ -69,6 +69,7 @@ Security Advisories
|
||||||
+-----------+------------------------------------------------------------------+
|
+-----------+------------------------------------------------------------------+
|
||||||
|
|
||||||
.. _issue tracker: https://developer.trustedfirmware.org/project/board/1/
|
.. _issue tracker: https://developer.trustedfirmware.org/project/board/1/
|
||||||
|
.. _mailing list: https://lists.trustedfirmware.org/mailman/listinfo/tf-a
|
||||||
|
|
||||||
.. |TFV-1| replace:: :ref:`Advisory TFV-1 (CVE-2016-10319)`
|
.. |TFV-1| replace:: :ref:`Advisory TFV-1 (CVE-2016-10319)`
|
||||||
.. |TFV-2| replace:: :ref:`Advisory TFV-2 (CVE-2017-7564)`
|
.. |TFV-2| replace:: :ref:`Advisory TFV-2 (CVE-2017-7564)`
|
||||||
|
|
Loading…
Add table
Reference in a new issue