Skip to content

Commit c9210ef

Browse files
authored
doc: update Build WG Slack channel (#2928)
The Slack channel for the Build WG has been moved to #nodejs-build on the OpenJS Foundation Slack instance. Update references to the Slack channel, and remove outdated references to IRC. Refs: https://openjs-foundation.slack.com/archives/C03BJP63CH0
1 parent b5b5073 commit c9210ef

File tree

3 files changed

+11
-10
lines changed

3 files changed

+11
-10
lines changed

GOVERNANCE.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -71,8 +71,8 @@ all reflect on the Build WG.
7171

7272
If you are interested in helping out with the Build WG, please reach out to
7373
existing members to let us know. The best means for communication with the Build
74-
WG are either here via GitHub issues or through the `#node-build` channel on
75-
Freenode [IRC][].
74+
WG are either here via GitHub issues or through the `#nodejs-build` channel on
75+
the OpenJS Foundation [Slack][].
7676

7777
Membership is granted by way of a pull request adding a new individual to the
7878
members list on the README (e.g. [#524][]). New members can open such a pull
@@ -158,9 +158,9 @@ These Pull Requests must be:
158158
* Use the squash merge button workflow on Github
159159

160160

161-
[IRC], specifically `#node-build` is important for communicating with
161+
[Slack], specifically `#nodejs-build` is important for communicating with
162162
other Node.js project members, and how we receive many initial signals
163-
of downtime. IRC logs are maintained at http://logs.libuv.org/node-build
163+
of downtime.
164164

165165

166166
### Special Access Requests
@@ -343,6 +343,6 @@ The [Node.js Code of Conduct][] applies to this WG.
343343
[Node.js Moderation Policy]: https://github.com/nodejs/TSC/blob/HEAD/Moderation-Policy.md
344344
[Node.js Foundation calendar]: https://nodejs.org/calendar
345345
[the onboarding doc]: /ONBOARDING.md
346-
[IRC]: /README.md#nodejs-build-working-group
346+
[Slack]: https://openjs-foundation.slack.com/archives/C03BJP63CH0
347347
[#524]: https://github.com/nodejs/build/pull/524
348348
[resources.md]: /doc/resources.md

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -258,7 +258,7 @@ companies that have donated miscellaneous hardware:
258258

259259

260260
If you would like to donate hardware to the Node.js Project, please reach
261-
out to the Build Working Group, via the [#build channel on the Node.js slack
261+
out to the Build Working Group, via the [#nodejs-build channel on the OpenJS Foundation Slack
262262
instance][1] or contact [Rod Vagg](mailto:[email protected]) directly. The Build
263263
Working Group reserves the right to choose what hardware is actively used
264264
and how it is used, donating hardware does not guarantee its use within the
@@ -282,7 +282,7 @@ months after the release goes End-of-Life, in case further build or test runs
282282
are required. After that the configuration will be removed.
283283

284284

285-
[1]: https://node-js.slack.com/archives/C16SCB5JQ
285+
[1]: https://openjs-foundation.slack.com/archives/C03BJP63CH0
286286
[2]: https://digitalocean.com/
287287
[3]: https://www.rackspace.com/
288288
[5]: https://www.mailgun.com/

doc/jenkins-guide.md

+4-3
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ ansible-playbook playbooks/jenkins/worker/create.yml --limit test-rackspace-free
5151
If all goes according to plan, then Ansible should be able to run the
5252
playbook with no errors. If you do encounter problems, there are usually
5353
some WG members available in the
54-
[Node.js Build Slack channel](https://node-js.slack.com/archives/C16SCB5JQ), who can try and
54+
[Node.js Build Slack channel][], who can try and
5555
lend a hand.
5656

5757
## Security releases
@@ -129,7 +129,7 @@ Relevant logs:
129129
## Solving problems
130130

131131
Issues with the Jenkins clusters are usually reported to either the
132-
[Node.js Build Slack channel](https://node-js.slack.com/archives/C16SCB5JQ), or to the
132+
[Node.js Build Slack channel][], or to the
133133
[`nodejs/build` issue tracker](https://github.com/nodejs/build/issues).
134134

135135
When trying to fix a worker, ensure that you `mark the node as offline`,
@@ -369,7 +369,7 @@ to its desired state, including refreshing and restarting the Jenkins
369369
agent configuration.
370370
371371
If none of the above steps work, please post in the
372-
[Node.js Build Slack channel](https://node-js.slack.com/archives/C16SCB5JQ), or the
372+
[Node.js Build Slack channel][], or the
373373
[`nodejs/build` issue tracker](https://github.com/nodejs/build/issues), to allow
374374
for escalation and other WG members to troubleshoot.
375375
@@ -381,3 +381,4 @@ take a look.
381381
[secrets repo]: https://github.com/nodejs-private/secrets
382382
[ci]: https://ci.nodejs.org/computer/test-softlayer-ubuntu1804_container-x64-1/
383383
[1]: https://ci.nodejs.org/computer/test-softlayer-ubuntu1804_container-x64-1/
384+
[Node.js Build Slack channel]: https://openjs-foundation.slack.com/archives/C03BJP63CH0

0 commit comments

Comments
 (0)