Skip to content

Commit 0ab44fd

Browse files
authored
Replace documentation mentions of IRC with Discord (llvm#114276)
This does not touch code owners or credits files that list IRC handles, that can be done separately if we want to make that change. See https://discourse.llvm.org/t/rfc-remove-irc-as-a-recommended-communication-channel/82808/3 for the RFC.
1 parent 5581e43 commit 0ab44fd

File tree

9 files changed

+25
-39
lines changed

9 files changed

+25
-39
lines changed

clang/www/OpenProjects.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -160,8 +160,8 @@ <h1>Open Clang Projects</h1>
160160
<p>If you hit a bug with Clang, it is very useful for us if you reduce the code
161161
that demonstrates the problem down to something small. There are many ways to
162162
do this; ask on <a href="https://discourse.llvm.org/c/clang">Discourse</a>,
163-
<a href="https://discord.com/channels/636084430946959380/636725486533345280">Discord</a>,
164-
or <a href="https://llvm.org/docs/GettingInvolved.html#irc"IRC</a> for advice.</p>
163+
<a href="https://discord.com/channels/636084430946959380/636725486533345280">Discord</a>
164+
for advice.</p>
165165

166166
</div>
167167
</body>

libunwind/docs/index.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ and `Getting started with LLVM <https://llvm.org/docs/GettingStarted.html>`__.
7878

7979
If you think you've found a bug in libunwind, please report it using
8080
the `LLVM bug tracker`_. If you're not sure, you
81-
can ask for support on the `Runtimes forum`_ or on IRC.
81+
can ask for support on the `Runtimes forum`_ or on Discord.
8282
Please use the tag "libunwind" for new threads.
8383

8484
**Patches**

llvm/docs/CodeOfConduct.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -24,12 +24,12 @@ the spirit in which it's intended - a guide to make it easier to communicate
2424
and participate in the community.
2525

2626
This code of conduct applies to all spaces managed by the LLVM project or The
27-
LLVM Foundation. This includes IRC channels, mailing lists, bug trackers, LLVM
28-
events such as the developer meetings and socials, and any other forums created
29-
by the project that the community uses for communication. It applies to all of
30-
your communication and conduct in these spaces, including emails, chats, things
31-
you say, slides, videos, posters, signs, or even t-shirts you display in these
32-
spaces.
27+
LLVM Foundation. This includes IRC and Discord channels, mailing lists, bug
28+
trackers, LLVM events such as the developer meetings and socials, and any other
29+
forums created by the project that the community uses for communication. It
30+
applies to all of your communication and conduct in these spaces, including
31+
emails, chats, things you say, slides, videos, posters, signs, or even t-shirts
32+
you display in these spaces.
3333

3434
In rare cases, violations of this code outside of these spaces may affect a
3535
person’s ability to participate within these spaces. Important examples

llvm/docs/CodeReview.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -248,8 +248,8 @@ larger features. Common ways to speed up review times for your patches are:
248248
get this patch landed and ping it every couple of days. If it is
249249
not urgent, the common courtesy ping rate is one week. Remember that you're
250250
asking for valuable time from other professional developers.
251-
* Ask for help on IRC. Developers on IRC will be able to either help you
252-
directly, or tell you who might be a good reviewer.
251+
* Ask for help on Discord. Developers on Discord will be able to either help
252+
you directly, or tell you who might be a good reviewer.
253253
* Split your patch into multiple smaller patches that build on each other. The
254254
smaller your patch is, the higher the probability that somebody will take a quick
255255
look at it. When doing this, it is helpful to add "[N/M]" (for 1 <= N <= M) to

llvm/docs/Contributing.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Contributing to LLVM
66
Thank you for your interest in contributing to LLVM! There are multiple ways to
77
contribute, and we appreciate all contributions. In case you have questions,
88
you can either use the `Forum`_ or, for a more interactive chat, go to our
9-
`Discord server`_ or the IRC #llvm channel on `irc.oftc.net`_.
9+
`Discord server`_.
1010

1111
If you want to contribute code, please familiarize yourself with the :doc:`DeveloperPolicy`.
1212

llvm/docs/DeveloperPolicy.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -201,7 +201,7 @@ within an area of a project:
201201
* aid release managers with backporting and other release-related
202202
activities,
203203
* be a point of contact for contributors who need help (answering questions
204-
on Discord/Discourse/IRC or holding office hours).
204+
on Discord/Discourse or holding office hours).
205205

206206
Each top-level project in the monorepo will specify one or more
207207
lead maintainers who are responsible for ensuring community needs are

llvm/docs/GettingInvolved.rst

Lines changed: 9 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -373,11 +373,7 @@ Guidance for office hours hosts
373373
* When starting an office hours session, consider typing something like "*Hi,
374374
I'm available for chats in the next half hour at* video chat URL. *I'm
375375
looking forward to having conversations on the video chat or here.*" on the
376-
LLVM chat channels that you are already on. These could include:
377-
378-
* the `#office-hours Discord channel
379-
<https://discord.com/channels/636084430946959380/976196303681896538>`__.
380-
* :ref:`IRC`
376+
the `#office-hours Discord channel <https://discord.com/channels/636084430946959380/976196303681896538>`__.
381377

382378
Doing this can help:
383379
* overcome potential anxiety to call in for a first time,
@@ -388,27 +384,18 @@ Guidance for office hours hosts
388384
from the list above.
389385

390386

391-
.. _IRC:
392-
393-
IRC
394-
---
387+
Discord
388+
-------
395389

396390
Users and developers of the LLVM project (including subprojects such as Clang)
397-
can be found in #llvm on `irc.oftc.net <irc://irc.oftc.net/llvm>`_. The channel
398-
is actively moderated.
391+
can be found on the community's `Discord <https://discord.com/channels/636084430946959380/636725486533345280>`_
392+
chat server. The server is actively moderated.
399393

400-
The #llvm-build channel has a bot for
394+
The #buildbot-status channel has a bot for
401395
`LLVM buildbot <http://lab.llvm.org/buildbot/#/console>`_ status changes. The
402-
bot will post a message with a link to a build bot and a blamelist when a build
403-
goes from passing to failing and again (without the blamelist) when the build
404-
goes from failing back to passing. It is a good channel for actively monitoring
405-
build statuses, but it is a noisy channel due to the automated messages. The
406-
channel is not actively moderated.
407-
408-
In addition to the traditional IRC there is a
409-
`Discord <https://discord.com/channels/636084430946959380/636725486533345280>`_
410-
chat server available. To sign up, please use this
411-
`invitation link <https://discord.com/invite/xS7Z362>`_.
396+
bot will update the channel with a link to a build bot when a build goes from
397+
passing to failing and again when the build goes from failing back to passing.
398+
It is a great way to actively monitor the status of the build.
412399

413400

414401
.. _meetups-social-events:

llvm/docs/ResponseGuide.rst

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -189,7 +189,7 @@ taken, but below is a list of possible resolutions:
189189
violation.
190190
* A private verbal warning and/or reprimand from the committee to the
191191
individual(s) involved and request to stop this behavior. This conversation
192-
may happen in person, email, by phone, video chat, or IRC.
192+
may happen in person, email, by phone, video chat, or Discord.
193193
* Request that the reportee avoid any interaction with, and physical proximity
194194
to, another person for the remainder of the event.
195195
* Refusal of alcoholic beverage purchases by the reportee at LLVM events.
@@ -202,8 +202,7 @@ taken, but below is a list of possible resolutions:
202202
* Immediately ending any volunteer responsibilities and privileges the reportee
203203
holds.
204204
* An imposed suspension (e.g., asking someone to "take a week off" from mailing
205-
lists, bug tracker, IRC, Discord, repositories, or other communication
206-
forms).
205+
lists, bug tracker, Discord, repositories, or other communication forms).
207206
* A permanent or temporary ban from some or all LLVM Project spaces (online or
208207
in person).
209208

llvm/docs/_templates/indexsidebar.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ <h3>Getting Involved</h3>
1515
<li><a href="https://llvm.org/docs/Contributing.html">Contributing to LLVM</a></li>
1616
<li><a href="https://llvm.org/docs/HowToSubmitABug.html">Submitting Bug Reports</a></li>
1717
<li><a href="https://llvm.org/docs/GettingInvolved.html#mailing-lists">Mailing Lists</a></li>
18-
<li><a href="https://llvm.org/docs/GettingInvolved.html#irc">IRC</a></li>
18+
<li><a href="https://llvm.org/docs/GettingInvolved.html#discord">Discord</a></li>
1919
<li><a href="https://llvm.org/docs/GettingInvolved.html#meetups-and-social-events">Meetups and Social Events</a></li>
2020
</ul>
2121

0 commit comments

Comments
 (0)