Skip to content

Update communication channels in documentation #20429

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

jphamgithub
Copy link

  • Add GitHub Discussions and Slack as primary support channels
  • Update README.md with current communication options
  • Update Contact.md with organized channel hierarchy
  • Update CONTRIBUTING.md to include GitHub Discussions
  • Maintain references to existing IRC and mailing list channels

Addresses #20234

This change updates outdated communication channel references in the project documentation. The issue specifically requested updating Freenode IRC references (no longer active) and consolidating current official support channels.

Verification

Documentation changes verified by:

  • README.md - Added GitHub Discussions and Slack links in the "Getting Help" section
  • Contact.md - Reorganized with clear hierarchy: Primary channels (GitHub Discussions, Slack) and Additional channels (IRC, mailing lists, social media)
  • CONTRIBUTING.md - Added GitHub Discussions reference alongside existing support channels
  • Verify all links are functional and point to correct destinations
  • Verify formatting is consistent with existing documentation style
  • Verify no broken references or outdated information remains

This documentation update provides users with current, accurate information about how to get support and engage with the Metasploit community!

- Add GitHub Discussions and Slack as primary support channels
- Update README.md with current communication options
- Update Contact.md with organized channel hierarchy
- Update CONTRIBUTING.md to include GitHub Discussions
- Maintain references to existing IRC and mailing list channels

Addresses rapid7#20234
@jphamgithub
Copy link
Author

jphamgithub commented Jul 31, 2025

Thank you for the feedback @jheysel-r7. I committed all of them and changed the other Twitter reference to X

- **Mastodon**: [@[email protected]](https://infosec.exchange/@metasploit)
- **Blog**: [Rapid7 Blog - Metasploit Tag](https://www.rapid7.com/blog/tag/metasploit/)
- **YouTube**: [Metasploit YouTube](https://youtube.com/@MetasploitR7)

# Abuse

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to [email protected] which goes to all the current committers. If the incident involves a committer, you may report directly to [email protected] or [email protected].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caitlin is not part of R7, so maybe we should replace that? @zeroSteiner, would it make sense to add you there instead?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah we should probably update it with my info, [email protected].

Copy link
Author

@jphamgithub jphamgithub Aug 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@msutovsky-r7 msutovsky-r7 self-assigned this Aug 4, 2025
Replace outdated [email protected] with [email protected]
as requested by maintainers in PR feedback.
@jphamgithub jphamgithub force-pushed the update-communication-channels branch from f4df679 to c2da23a Compare August 4, 2025 18:40
- Update Twitter references to X in Contact.md and README.md
- Add YouTube channel to Contact.md
- Remove IRC reference from CONTRIBUTING.md as requested
- Address all maintainer suggestions from PR review
@jphamgithub
Copy link
Author

Done making changes for now unless there is further feedback: https://github.com/rapid7/metasploit-framework/pull/20429/files

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.

4 participants