From a8debff67e9b7c479cce7dc9f72e46e2677cfb9b Mon Sep 17 00:00:00 2001 From: Richard Hartmann Date: Fri, 22 Apr 2022 20:26:46 +0200 Subject: [PATCH] Remove freenode Signed-off-by: Richard Hartmann --- content/blog/2015-06-24-monitoring-dreamhack.md | 2 +- .../blog/2016-01-26-one-year-of-open-prometheus-development.md | 2 +- content/docs/instrumenting/writing_exporters.md | 2 +- snippets/saved_replies.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/blog/2015-06-24-monitoring-dreamhack.md b/content/blog/2015-06-24-monitoring-dreamhack.md index 71679860..acbe4d41 100644 --- a/content/blog/2015-06-24-monitoring-dreamhack.md +++ b/content/blog/2015-06-24-monitoring-dreamhack.md @@ -238,7 +238,7 @@ We're really excited about Prometheus and how easy it makes setting up scalable monitoring and alerting from scratch. A huge shout-out to everyone that helped us in `#prometheus` on -[FreeNode](https://freenode.net/) during the event. Special thanks to Brian +FreeNode during the event. Special thanks to Brian Brazil, Fabian Reinartz and Julius Volz. Thanks for helping us even in the cases where it was obvious that we hadn't read the documentation thoroughly enough. diff --git a/content/blog/2016-01-26-one-year-of-open-prometheus-development.md b/content/blog/2016-01-26-one-year-of-open-prometheus-development.md index cb73dc6b..ab639462 100644 --- a/content/blog/2016-01-26-one-year-of-open-prometheus-development.md +++ b/content/blog/2016-01-26-one-year-of-open-prometheus-development.md @@ -73,7 +73,7 @@ To give you an idea of the ecosystem, we now have: - 200+ contributors - 2300+ pull requests (60+ open) - 1100+ issues (300+ open) -- 150+ people in our IRC channel (`#prometheus` on [FreeNode](http://freenode.net/)) +- 150+ people in our IRC channel (`#prometheus` on FreeNode) - 250+ people on the mailing list who have created 300+ threads - 20+ Prometheus-related talks and workshops - 100+ articles and blog posts diff --git a/content/docs/instrumenting/writing_exporters.md b/content/docs/instrumenting/writing_exporters.md index 2c34b8b1..4cbd54ac 100644 --- a/content/docs/instrumenting/writing_exporters.md +++ b/content/docs/instrumenting/writing_exporters.md @@ -16,7 +16,7 @@ exporter or custom collector. The theory covered will also be of interest to those doing direct instrumentation. If you are writing an exporter and are unclear on anything here, please -contact us on IRC (#prometheus on Freenode) or the [mailing +contact us on IRC (#prometheus on libera) or the [mailing list](/community). ## Maintainability and purity diff --git a/snippets/saved_replies.md b/snippets/saved_replies.md index 69225b0b..bc532d08 100644 --- a/snippets/saved_replies.md +++ b/snippets/saved_replies.md @@ -24,7 +24,7 @@ It's not always feasible, or even possible, to fill out the XXX used in the snip Thanks for your report. It looks as if this is actually a question about usage and not development because XXX -To make your question, and all replies, easier to find, we suggest you move this over to our [user mailing list](https://groups.google.com/forum/#!forum/prometheus-users), which you can also search. If you prefer more interactive help, join or our [IRC channel](https://webchat.freenode.org/?channels=prometheus), #prometheus on irc.freenode.net. Please be aware that our IRC channel has no logs, is not searchable, and that people might not answer quickly if they are busy or asleep. If in doubt, you should choose the mailing list. +To make your question, and all replies, easier to find, we suggest you move this over to our [user mailing list](https://groups.google.com/forum/#!forum/prometheus-users), which you can also search. If you prefer more interactive help, join or our [IRC channel](https://web.libera.chat/#prometheus), #prometheus on irc.libera.chat. Please be aware that our IRC channel has no logs, is not searchable, and that people might not answer quickly if they are busy or asleep. If in doubt, you should choose the mailing list. If you think this is not purely a support question, feel free to comment in here or take the underlying issues to our [developer mailing list](https://groups.google.com/forum/#!forum/prometheus-developers).