Scriptorium welcomes people of every background and experience level. Treat participants with respect regardless of age, disability, race, ethnicity, nationality, caste, religion, gender, sexual orientation, appearance, education, or economic circumstances. Beginners and experienced contributors are equally entitled to a constructive environment.
AI-assisted participation is welcome. Harassment or exclusion solely because a person uses AI tools violates this policy. See AI_POLICY.md.
- Discuss the work with specific, constructive feedback.
- Be patient with questions and respectful when disagreeing.
- Acknowledge mistakes, correct inaccurate claims, and credit others' work.
- Respect privacy and keep vulnerability details in the reporting channels described in SECURITY.md.
- Keep issues and pull requests relevant, understandable, and reviewable.
Unacceptable conduct includes harassment, intimidation, discriminatory abuse, sexualized remarks or unwanted sexual attention, personal attacks, threats, publication of private information without permission, and retaliation against good-faith reporters. Deliberate malware, credential theft, sabotage, spam, and sustained disruption of project discussions are also prohibited.
Strong technical disagreement and requests for tests, documentation, clearer designs, or compatibility handling are legitimate when expressed without personal attacks. Reviewers may reject unsafe, incorrect, or unsuitable work regardless of the tools used to create it.
This policy applies in Scriptorium's repository, issues, pull requests, official communication channels, and events, and when someone officially represents the project elsewhere. It applies to Maintainers, Contributors, and Participants. It does not grant the project authority over independently operated sites built with Scriptorium.
Email info@logbie.com with the subject Scriptorium Code of Conduct.
Include what happened, relevant dates and links, and supporting material you
can safely share. Include any immediate safety or privacy concerns. Do not
publish private information in an issue to make a report.
Maintainers handle reports as confidentially as practical, sharing details only as needed to investigate and respond. Absolute confidentiality cannot be promised. Retaliation against someone who reports or assists in good faith is itself a violation. For vulnerabilities or security-related abuse, use SECURITY.md.
Maintainers enforce this policy under GOVERNANCE.md. They may moderate content, request a correction, issue a warning, limit participation, remove elevated access, or impose a temporary or permanent ban. They consider the impact, severity, and pattern of behavior; serious threats, doxxing, or sabotage may require immediate restrictions.
Where practical, Maintainers explain the action and its scope to the affected person without exposing reporter information. A person may request reconsideration by emailing the reporting address with relevant context. Reports involving a Maintainer should be reviewed by an uninvolved Maintainer when one is available. The project currently has a single primary Maintainer and does not claim an independent appeals body.
Policy amendments follow GOVERNANCE.md. This policy adapts the maintainer-led and AI-inclusive approach used in WFL's governance suite for Scriptorium.
Effective: 2026-09-12.