Skip to content

update old freenode channel link to libera #15698

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

Merged
merged 1 commit into from
May 6, 2025
Merged

Conversation

t7ru
Copy link
Contributor

@t7ru t7ru commented May 4, 2025

User description

🔗 Related Issues

💥 What does this PR do?

Changed freenode irc link to the libera irc

🔧 Implementation Notes

💡 Additional Considerations

🔄 Types of changes

  • Cleanup (formatting, renaming)

PR Type

Documentation


Description

  • Updated IRC channel references from Freenode to Libera

  • Improved documentation accuracy for contributor communication


Changes walkthrough 📝

Relevant files
Documentation
CONTRIBUTING.md
Update IRC reference to Libera in contributor guide           

CONTRIBUTING.md

  • Changed IRC channel reference from Freenode to Libera
  • Updated communication instructions for contributors
  • +1/-1     
    README.md
    Update IRC reference to Libera in JS README                           

    javascript/selenium-webdriver/README.md

  • Updated mention of IRC channel from Freenode to Libera
  • Clarified resource listing for community support
  • +1/-1     

    Need help?
  • Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
  • Check out the documentation for more information.
  • @CLAassistant
    Copy link

    CLAassistant commented May 4, 2025

    CLA assistant check
    All committers have signed the CLA.

    @selenium-ci selenium-ci added the C-nodejs JavaScript Bindings label May 4, 2025
    Copy link
    Contributor

    qodo-merge-pro bot commented May 4, 2025

    PR Reviewer Guide 🔍

    (Review updated until commit 1a9668f)

    Here are some key observations to aid the review process:

    🎫 Ticket compliance analysis ❌

    5678 - Not compliant

    Non-compliant requirements:

    • Fix the "ConnectFailure (Connection refused)" error when instantiating ChromeDriver
    • Address issue with multiple ChromeDriver instantiations
    • Provide a solution for Ubuntu 16.04.4 with Chrome 65.0.3325.181 and ChromeDriver 2.35

    1234 - Not compliant

    Non-compliant requirements:

    • Fix issue with JavaScript in link's href not triggering on click() in Firefox
    • Address regression between Selenium 2.47.1 and 2.48.0/2.48.2
    • Ensure compatibility with Firefox 42.0

    ⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ No major issues detected

    Copy link
    Contributor

    qodo-merge-pro bot commented May 4, 2025

    PR Code Suggestions ✨

    No code suggestions found for the PR.

    @titusfortner
    Copy link
    Member

    I wonder if it would make sense to only include the link to our website where we list the communciation options
    .

    @titusfortner titusfortner reopened this May 5, 2025
    Copy link
    Contributor

    qodo-merge-pro bot commented May 5, 2025

    PR Code Suggestions ✨

    No code suggestions found for the PR.

    @t7ru
    Copy link
    Contributor Author

    t7ru commented May 5, 2025

    I wonder if it would make sense to only include the link to our website where we list the communciation options

    .

    It's fine the way it is right now, no? Having things directly available on the same site is always more convenient and intuitive I think.

    Though I am not necessarily against doing something like: "See for information"

    @cgoldberg
    Copy link
    Contributor

    I wonder if it would make sense to only include the link to our website where we list the communication options

    I think that makes the most sense. Currently it mentions the selenium-developers mailing list, which is dead... and doesn't even mention Slack, which is the primary means of communication.

    @titusfortner titusfortner merged commit 3ab2f49 into SeleniumHQ:trunk May 6, 2025
    26 checks passed
    @titusfortner
    Copy link
    Member

    Part of my issue is that we have so much different info in all the various readme docs that it's hard to keep it straight

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    5 participants