[docs] Update bug report section in CONTRIBUTING.md

[rpallavisharma]

User description

removed mailing list .
added slack.

🔗 Related Issues

💥 What does this PR do?

bug report section

🔧 Implementation Notes

💡 Additional Considerations

🔄 Types of changes

• Cleanup (formatting, renaming)
• Bug fix (backwards compatible)
• New feature (non-breaking change which adds functionality and tests!)
• Breaking change (fix or feature that would cause existing functionality to change)

---

PR Type

Documentation

---

Description

• Updated bug reporting guidance in CONTRIBUTING.md

• Replaced mailing lists with GitHub issues and Slack

• Modernized community support channels

---

Diagram Walkthrough

flowchart LR
  A["Old mailing lists"] -- "replaced with" --> B["GitHub issues"]
  A -- "replaced with" --> C["Selenium Slack"]

Loading

File Walkthrough

	Relevant files
Documentation	CONTRIBUTING.md Updated bug reporting and support channels                              CONTRIBUTING.md Removed references to selenium-users and selenium-developers mailing lists Added GitHub issues link for bug reporting Added Selenium Slack channel for discussions +3/-5

---

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis 🔶 1234 - Partially compliant Compliant requirements: None Non-compliant requirements: Investigate regression where clicking a link with JavaScript in href no longer triggers in Selenium 2.48.x. Provide reproduction details and validate the behavior difference between versions. Determine if browser/version specifics impact behavior. Requires further human verification: None 5678 - Partially compliant Compliant requirements: None Non-compliant requirements: Diagnose "ConnectFailure (Connection refused)" when instantiating multiple ChromeDriver instances. Identify conditions causing first instance to succeed and subsequent instances to fail. Provide steps to reproduce and potential fixes/workarounds. Requires further human verification: None

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Formatting The sentence with the GitHub issues link has mismatched punctuation and parentheses, which may render incorrectly and confuse readers. Please fix the Markdown/link formatting and sentence structure. Issues shouldn't be used for support. To raise a bug, please go here- (https://github.com/SeleniumHQ/selenium/issues)). Clarity Consider clarifying that GitHub Issues are for bugs/feature requests and that support should go to Slack; current phrasing "Issues shouldn't be used for support. To raise a bug, please go here-" is awkward and split across lines. Issues shouldn't be used for support. To raise a bug, please go here- (https://github.com/SeleniumHQ/selenium/issues)). Discussion of high level project ideas or non-technical topics should move to the Selenium Slack channel (https://inviter.co/seleniumhq).

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	✅ Fix malformed bug report link Suggestion Impact: The malformed bug report lines were corrected to a properly worded sentence with a valid link, addressing the extra parenthesis and formatting issues (though the exact wording differs). code diff: -Issues shouldn't be used for support. To raise a bug, please go here- -(https://github.com/SeleniumHQ/selenium/issues)). +Issues shouldn't be used for support. To raise a bug, please go to the +[Issue tracker](https://github.com/SeleniumHQ/selenium/issues). Fix the malformed sentence and extra parenthesis to avoid confusing readers and broken rendering. Combine the text and link properly, using a single closing parenthesis and clear wording. CONTRIBUTING.md [17-18] -Issues shouldn't be used for support. To raise a bug, please go here- -(https://github.com/SeleniumHQ/selenium/issues)). +Issues shouldn't be used for support. To report a bug, please open an issue at: https://github.com/SeleniumHQ/selenium/issues [Suggestion processed] Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies and fixes a malformed sentence and link, which has an extra parenthesis and unusual punctuation, improving the clarity and correctness of the documentation.	Medium
General	✅ Clarify Slack channel reference Suggestion Impact: The commit changed the Slack reference to a descriptive Markdown link "[Slack channel](https://inviter.co/seleniumhq)", addressing the readability concern. code diff: Discussion of high level project ideas or non-technical topics should -move to the Selenium Slack channel (https://inviter.co/seleniumhq). +move to the Selenium [Slack channel](https://inviter.co/seleniumhq). Clarify the Slack reference by using a direct, descriptive link label and avoid bare URLs in parentheses for better readability and accessibility. This reduces ambiguity and improves formatting consistency. CONTRIBUTING.md [19-20] -Discussion of high level project ideas or non-technical topics should -move to the Selenium Slack channel (https://inviter.co/seleniumhq). +Discussion of high level project ideas or non-technical topics should move to the Selenium Slack channel: https://inviter.co/seleniumhq [Suggestion processed] Suggestion importance[1-10]: 3 __ Why: The suggestion proposes a minor stylistic change to improve readability by replacing parentheses around a URL with a colon, which is a valid but low-impact improvement.	Low
Update