Skip to content

docs: add Code of Conduct #34

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.

Sign up for GitHub

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
BLCCoreStudio merged 1 commit into from
Aug 31, 2026
Merged

docs: add Code of Conduct #34

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions CODE_OF_CONDUCT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
# Code of Conduct

BLCCoreStudio projects are technical communities. Discussions, issues, reviews, and contributions should stay respectful, evidence-driven, and useful.

## Expected behavior

- Be respectful and constructive, including when you disagree.
- Critique code, designs, benchmarks, documentation, and evidence rather than people.
- Give others room to correct mistakes and ask questions.
- Keep reports relevant and avoid spam or low-effort bulk submissions.
- Follow each repository's documented safety, security, and responsible-disclosure boundaries.

## Unacceptable behavior

Harassment, discriminatory or demeaning language, threats, doxxing, deliberate misinformation, malicious disruption, or publishing private or security-sensitive information without permission are not acceptable.

## Security and sensitive research

Potential vulnerabilities should be reported according to `SECURITY.md` rather than disclosed publicly before maintainers have had a reasonable opportunity to investigate. Security, reverse-engineering, root, or device-tooling work must stay within the repository's documented scope and applicable authorization boundaries.

## Enforcement

Maintainers may edit or remove content, close or lock discussions, reject contributions, or restrict participation when necessary to keep the project safe and productive.
Loading