Adding mailto link in upstream opportunities doc
This is adding mailto link in upstream opportunities doc which was a feedback in the original change - https://review.opendev.org/c/openstack/governance/+/872233/2/reference/upstream-investment-opportunities/2023/community-infrastructure-sysadmins.rst#113 Change-Id: Ifd9753eed21f9d04453477294ab4ccce2f23fcc0
This commit is contained in:
parent
55461489a8
commit
71593ec64b
@ -109,5 +109,5 @@ Contact
|
||||
|
||||
Join the OpenStack Infra or TC IRC channel (``openstack-infra`` on `OFTC
|
||||
<https://www.oftc.net/>`_) or (``openstack-tc`` on `OFTC <https://www.oftc.net/>`_).
|
||||
You can also reach out through the openstack-discuss mail list at list.openstack.org
|
||||
if you would like to get involved.
|
||||
You can also reach out through the `OpenStack Community Mailing List
|
||||
<mailto:openstack-discuss@lists.openstack.org>`_ if you would like to get involved.
|
||||
|
@ -99,8 +99,8 @@ Contact
|
||||
-------
|
||||
|
||||
Join the OpenStack QA IRC channel (``#openstack-qa`` on `OFTC IRC`_), email
|
||||
the openstack-discuss mailing list at list.openstack.org, or contact the `QA
|
||||
PTL`_ directly if you would like to get involved.
|
||||
the `OpenStack Community Mailing List <mailto:openstack-discuss@lists.openstack.org>`_,
|
||||
or contact the `QA PTL`_ directly if you would like to get involved.
|
||||
|
||||
|
||||
.. _`Zuul project`: https://zuul-ci.org
|
||||
|
@ -85,7 +85,8 @@ Contact
|
||||
-------
|
||||
|
||||
To contribute to this initiative, contact the `champion`_ of this goal or the
|
||||
`OpenStack Technical Committee`_.
|
||||
`OpenStack Technical Committee`_ or reach out through the `OpenStack Community
|
||||
Mailing List <mailto:openstack-discuss@lists.openstack.org>`_.
|
||||
|
||||
.. _community-wide rbac goal: https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rbac.html
|
||||
.. _champion: https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rbac.html#champion
|
||||
|
Loading…
Reference in New Issue
Block a user