forked from OSchip/llvm-project
Update references to the mailing lists that have moved to Discourse.
This commit is contained in:
Tanya Lattner
parent
14101f48d2
commit
b4990ac330
|
|
@ -96,21 +96,18 @@ Information about LLVM's development process.
|
|||
:doc:`Release notes for the current release <ReleaseNotes>`
|
||||
This describes new features, known bugs, and other limitations.
|
||||
|
||||
.. _mailing-lists:
|
||||
.. _lists-forums:
|
||||
|
||||
Mailing Lists
|
||||
-------------
|
||||
Forums & Mailing Lists
|
||||
----------------------
|
||||
|
||||
If you can't find what you need in these docs, try consulting the mailing
|
||||
lists. In addition to the traditional mailing lists there is also a
|
||||
`Discourse server <https://llvm.discourse.group>`_ available.
|
||||
If you can't find what you need in these docs, try consulting the
|
||||
Discourse forums. There are also commit mailing lists for all commits to the LLVM Project.
|
||||
|
||||
`Developer's List (llvm-dev)`__
|
||||
This list is for people who want to be included in technical discussions of
|
||||
LLVM. People post to this list when they have questions about writing code
|
||||
for or using the LLVM tools. It is relatively low volume.
|
||||
`LLVM Discourse`__
|
||||
The forums for all things LLVM and related sub-projects. There are categories and subcategories for a wide variety of areas within LLVM. You can also view tags or search for a specific topic.
|
||||
|
||||
.. __: http://lists.llvm.org/mailman/listinfo/llvm-dev
|
||||
.. __: https://discourse.llvm.org/
|
||||
|
||||
`Commits Archive (llvm-commits)`__
|
||||
This list contains all commit messages that are made when LLVM developers
|
||||
|
|
@ -127,18 +124,10 @@ lists. In addition to the traditional mailing lists there is also a
|
|||
|
||||
.. __: http://lists.llvm.org/pipermail/llvm-bugs/
|
||||
|
||||
`Test Results Archive (llvm-testresults)`__
|
||||
A message is automatically sent to this list by every active nightly tester
|
||||
when it completes. As such, this list gets email several times each day,
|
||||
making it a high volume list.
|
||||
`LLVM Announcements`__
|
||||
If you just want project wide announcements such as releases, developers meetings, or blog posts, then you should check out the Announcement category on LLVM Discourse.
|
||||
|
||||
.. __: http://lists.llvm.org/pipermail/llvm-testresults/
|
||||
|
||||
`LLVM Announcements List (llvm-announce)`__
|
||||
This is a low volume list that provides important announcements regarding
|
||||
LLVM. It gets email about once a month.
|
||||
|
||||
.. __: http://lists.llvm.org/mailman/listinfo/llvm-announce
|
||||
.. __: https://discourse.llvm.org/c/announce/46
|
||||
|
||||
.. _online-sync-ups:
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ How to report a security issue?
|
|||
|
||||
To report a security issue in the LLVM Project, please `open a new issue`_ in the LLVM project page, on the chromium issue tracker. Be sure to use the "Security bug report" template.
|
||||
|
||||
We aim to acknowledge your report within two business days since you first reach out. If you do not receive any response by then, you can escalate by sending a message to the `llvm-dev mailing list`_ asking to get in touch with someone from the LLVM Security Group. **The escalation mailing list is public**: avoid discussing or mentioning the specific issue when posting on it.
|
||||
We aim to acknowledge your report within two business days since you first reach out. If you do not receive any response by then, you can escalate by posting on the `Discourse forums`_ asking to get in touch with someone from the LLVM Security Group. **The escalation mailing list is public**: avoid discussing or mentioning the specific issue when posting on it.
|
||||
|
||||
|
||||
Group Composition
|
||||
|
|
@ -177,7 +177,7 @@ We also occasionally need to discuss logistics of the LLVM Security Group itself
|
|||
* Propose member removal.
|
||||
* Suggest policy changes.
|
||||
|
||||
We often have these discussions publicly, in our :ref:`monthly public sync-up call <online-sync-ups>` and on public LLVM mailing lists. For internal or confidential discussions, we also use a private mailing list.
|
||||
We often have these discussions publicly, in our :ref:`monthly public sync-up call <online-sync-ups>` and on the Discourse forums. For internal or confidential discussions, we also use a private mailing list.
|
||||
|
||||
Process
|
||||
=======
|
||||
|
|
@ -230,6 +230,6 @@ The parts of the LLVM Project which are currently treated as non-security sensit
|
|||
.. _open a new issue: https://bugs.chromium.org/p/llvm/issues/entry
|
||||
.. _chromium issue tracker: https://crbug.com
|
||||
.. _GitHub security: https://help.github.com/en/articles/about-maintainer-security-advisories
|
||||
.. _llvm-dev mailing list: https://lists.llvm.org/mailman/listinfo/llvm-dev
|
||||
.. _Discourse forums: https://discourse.llvm.org
|
||||
.. _MITRE: https://cve.mitre.org
|
||||
.. _example nomination is available here: https://reviews.llvm.org/D99232
|
||||
|
|
|
|||
|
|
@ -803,7 +803,6 @@ tracked by performing a `bugzilla search
|
|||
<https://bugs.llvm.org/buglist.cgi?cmdtype=runnamed&namedcmd=Statepoint%20Bugs&list_id=64342>`_
|
||||
for [Statepoint] in the summary field. When filing new bugs, please
|
||||
use this tag so that interested parties see the newly filed bug. As
|
||||
with most LLVM features, design discussions take place on `llvm-dev
|
||||
<http://lists.llvm.org/mailman/listinfo/llvm-dev>`_, and patches
|
||||
with most LLVM features, design discussions take place on the `Discourse forums <https://discourse.llvm.org>`_ and patches
|
||||
should be sent to `llvm-commits
|
||||
<http://lists.llvm.org/mailman/listinfo/llvm-commits>`_ for review.
|
||||
|
|
|
|||
|
|
@ -201,8 +201,8 @@ about it. In that sense, code will never be removed outright without a series
|
|||
of steps are taken.
|
||||
|
||||
A minimum set of steps should be:
|
||||
#. A proposal for removal / deactivation should be made to the developers'
|
||||
mailing lists (``llvm-dev``, ``cfe-dev``, ``lldb-dev``, etc), with a clear
|
||||
#. A proposal for removal / deactivation should be made to the Discourse forums
|
||||
(under the appropriate category), with a clear
|
||||
statement of the maintenance costs imposed and the alternatives, if
|
||||
applicable.
|
||||
#. There must be enough consensus on the list that removal is warranted, and no
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ LLVM welcomes contributions of all kinds. To learn more, see the following artic
|
|||
|
||||
* :doc:`GettingInvolved`
|
||||
* :ref:`development-process`
|
||||
* :ref:`mailing-lists`
|
||||
* :ref:`lists-forums`
|
||||
* :ref:`meetups-social-events`
|
||||
* :ref:`community-proposals`
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue