-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace/remove references to defunct freenode instance #16873
Conversation
The preferred channel for communication about LS is the elastic discussion forum, this commit updates the source code and readme files to reflect that.
Quality Gate passedIssues Measures |
💚 Build Succeeded
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks for the review @robbavey Does this just need to go into the |
Let's just put it in |
@logstashmachine backport 8.x |
🤦 of course this wont cleanly backport #16873 (comment) due to #16863 will work up a manual one. |
The preferred channel for communication about LS is the elastic discussion forum, this commit updates the source code and readme files to reflect that.
Backport PR #16897 |
The preferred channel for communication about LS is the elastic discussion forum, this commit updates the source code and readme files to reflect that.
Release notes
[rn:skip]
What does this PR do?
Remove references to defunct freenode IRC and replace with preferred discussion forum.
Why is it important/What is the impact to the user?
Point folks at the preferred public discussion forum.
Checklist
[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding change to the default configuration files (and/or docker env variables)[ ] I have added tests that prove my fix is effective or that my feature worksRelated issues
Closes #16851