-
Notifications
You must be signed in to change notification settings - Fork 283
Update Code of Conduct #912
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
Conversation
xcorail
left a comment
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.
Remove the language bit
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.
Pull request overview
This PR updates the Code of Conduct to address recent off-topic activity in the Slack workspace. The changes clarify expectations around staying on topic and update the contact email for reporting violations.
Key changes:
- Added guidance to stay focused on open source security topics
- Added sustained off-topic messaging as unacceptable behavior
- Updated enforcement contact email from [email protected] to [email protected]
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.
| * Gracefully accepting constructive criticism | ||
| * Focusing on what is best for the community | ||
| * Showing empathy towards other community members | ||
| * Staying focused on our global topic –securing open source software, getting help securing your project–, or the specific topic of the current Slack channel or discussion thread |
Copilot
AI
Dec 2, 2025
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.
The em dashes need proper spacing. Currently reads "topic –securing" and "project–," but should be "topic – securing" and "project –," with spaces around the dashes.
| * Staying focused on our global topic –securing open source software, getting help securing your project–, or the specific topic of the current Slack channel or discussion thread | |
| * Staying focused on our global topic – securing open source software, getting help securing your project –, or the specific topic of the current Slack channel or discussion thread |
Update of our code of conduct, after several recent off-topic messages in our slack workspace, including some that we had to translate from other languages.