blob: 4afeaf5f287378fdb6b6d3c08b692039f838d9c8 [file] [log] [blame]
Joakim Bech8e5c5b32018-10-25 08:18:32 +02001.. _contact:
2
3#######
4Contact
5#######
6
7GitHub
8******
9Our preference is to use GitHub for communication. The reason for that is that
10it is an open source project, so there should be no real reason to hide
11discussions from other people. GitHub also makes it possible for anyone to chime
12in into discussion etc. So besides sending patches as pull requests on GitHub we
13also encourage people to use the "issues_" to report bugs, give suggestions, ask
14questions etc.
15
16Please try to use the "issues" in the relevant git. I.e., if you want to discuss
17something related to optee_client, then use "issues" at :ref:`optee_client` and
18so on. If you have a general question etc about OP-TEE that doesn't really
19belong to a specific git, then please use `issues at optee_os`_ in that case.
20
21Email
22*****
23You can reach the :ref:`core_team` by sending an email to
Joakim Beche58b15c2020-04-15 10:48:41 +020024``op-tee[at]lists.trustedfirmware.org``. However note that it's a public
25mailinglist and **not** just TrustedFirmware engineers behind that email
26address.
Joakim Bech8e5c5b32018-10-25 08:18:32 +020027
28For pure Linux kernel patches, please use the appropriate Linux kernel
29mailinglist, basically run the ``get_maintainer.pl`` script in the Linux kernel
30tree to figure out where to send your patches.
31
32.. code-block:: bash
33
34 $ cd <linux-kernel>
35 $ ./scripts/get_maintainer.pl drivers/tee/
36
37
38IRC
39***
40Some of the OP-TEE developers can be reached at Freenode (``chat.freenode.net``)
41at channel ``#linaro-security``. Having that said, the activity there is a bit
42limited, so it is probably **not** the best place to discuss OP-TEE.
43
44.. _vulnerability_reporting:
45
46Vulnerability reporting
47***********************
Joakim Bechb6f91302020-06-22 08:10:29 +020048The OP-TEE project as part of the TrustedFirmware.org organization is using the
49security incident process as described at the `TrustedFirmware.org security incident`_
50page. To report an issue, please follow the process as specified here. The email
51address to use can be found at the `Mailing Aliases`_ page.
Joakim Bech8e5c5b32018-10-25 08:18:32 +020052
53.. _core_team:
54
55Core Team
56*********
Joakim Beche58b15c2020-04-15 10:48:41 +020057The core team consists of engineers from TrustedFirmware.org. Related, see the
58`core team`_ at GitHub.
Joakim Bech8e5c5b32018-10-25 08:18:32 +020059
60.. _core team: https://github.com/orgs/OP-TEE/teams/linaro/members
61.. _issues: https://help.github.com/articles/about-issues/
62.. _issues at optee_os: https://github.com/OP-TEE/optee_os/issues
Joakim Bechb6f91302020-06-22 08:10:29 +020063.. _Mailing Aliases: https://developer.trustedfirmware.org/w/collaboration/security_center/mailing_aliases
64.. _TrustedFirmware.org security incident: https://developer.trustedfirmware.org/w/collaboration/security_center