Code of conduct
Keep technical collaboration respectful, safe, evidence-based, and accountable.
Lumen contributors must make project spaces safe, respectful, and technically honest. This applies to issues, pull requests, reviews, discussions, synchronous project spaces, and other interactions made on behalf of the project.
Expected behavior
Contribute with constructive disagreement, clear evidence, patience across experience levels, and respect for different identities and perspectives. Handle private information carefully. Correct your own mistakes plainly, distinguish observation from inference, and avoid claiming proof that has not been run.
Unacceptable behavior
Harassment, discrimination, threats, sexualized attention, doxxing, deliberate disruption, sustained bad-faith participation, and publishing another person's sensitive report details are not acceptable. Technical disagreement is welcome; personal attacks, intimidation, and manipulation of evidence are not.
Report a concern
Contact the repository owner privately through the contact methods on the maintainer's GitHub profile. Do not open a public issue containing sensitive conduct details. Include enough context to understand the affected project space, behavior, dates, and available evidence, but do not collect or redistribute unnecessary personal information.
A maintainer named in a report must not adjudicate it alone. If the normal contact is involved, use another available maintainer or repository-owner contact. Vulnerabilities follow the separate security-reporting process.
Enforcement
Maintainers may edit or remove contributions, comments, or other participation that violates this standard and may issue a warning, temporary restriction, or permanent ban proportionate to the behavior. Enforcement should protect affected people, minimize unnecessary disclosure, document the decision privately, and avoid conflicts of interest. The pre-release project does not publish a fixed response-time guarantee.