Give conduct reports a private first contact - #12
Merged
Conversation
Replace the public issue handshake with the maintainer-approved email channel so reporters can contact the project privately from the start. Constraint: Publish only the maintainer-provided conduct contact. Rejected: Reuse private vulnerability reporting | Security advisories are not a conduct-reporting channel. Confidence: high Scope-risk: narrow Directive: Keep conduct reports out of public issues and discussions. Tested: git diff --check and enforcement-link inspection. Not-tested: Delivery to the external mailbox.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
Conduct reporters should be able to contact the maintainer privately from the first step rather than opening a public issue before a private channel exists.
Impact
This is a documentation-only change. It does not change the application, analyzer, API, runtime capture, or security boundaries.
Validation
git diff --check./scripts/check.sh(typecheck, lint, 28 JavaScript tests, 154 Python tests, build, 39 E2E tests)The existing Vite chunk-size and Playwright
NO_COLOR/FORCE_COLORwarnings remain non-failing.