Comprehensive legal framework for the Project Tick ecosystem.
Project Tick Code of Conduct ============================ =*=*=*=*=*=*=*=*=*=*=*=*=*=* |Version 2, 15 February 2026| =*=*=*=*=*=*=*=*=*=*=*=*=*=* 1. Purpose ---------- Project Tick is a free software infrastructure initiative committed to technical excellence, legal clarity, and long-term sustainability. This Code of Conduct defines the behavioral and ethical standards expected across all Project Tick spaces. Its purpose is to protect contributors, maintain the integrity of the ecosystem, and ensure the security and reliability of our infrastructure. Participation in Project Tick constitutes agreement to abide by this Code. 2. Core Principles ------------------ Project Tick operates according to the following foundational principles: - Respect for human dignity - Commitment to technical integrity - Strict adherence to licensing and attribution requirements - Protection of infrastructure security and supply-chain integrity - Good-faith collaboration These principles apply equally to maintainers, contributors, and participants. 3. Expected Conduct ------------------- All participants are expected to: 1. Engage in respectful, constructive, and technically relevant discussion. 2. Accept review, feedback, and architectural decisions professionally. 3. Provide accurate attribution and comply fully with applicable licenses. 4. Disclose conflicts of interest where relevant. 5. Protect confidential or sensitive information. 6. Act in ways that strengthen the reliability and long-term sustainability of the ecosystem. 7. Respect differing technical or philosophical viewpoints without personal hostility. Criticism of ideas is encouraged. Personal attacks are not. 4. Prohibited Conduct --------------------- The following behaviors are considered violations of this Code of Conduct: 4.1 Personal and Social Misconduct ********************************** - Harassment, intimidation, or threats - Discriminatory behavior based on identity or personal characteristics - Insulting, demeaning, or hostile personal attacks - Sexualized behavior inappropriate to a professional technical environment - Sharing private information without explicit consent 4.2 Technical and Legal Misconduct ********************************** - Intentional submission of malicious code - Supply-chain compromise attempts - License violations or intentional misattribution - Plagiarism or failure to credit sources - False copyright claims - Impersonation of maintainers or other participants - Infrastructure abuse, including CI/CD exploitation or service disruption - Repeated bad-faith technical disruption Project maintainers reserve the right to determine whether conduct violates the spirit or intent of this Code. 5. Scope -------- This Code of Conduct applies to: - All Project Tick repositories - Mailing lists and communication channels - Issue trackers and merge requests - Continuous integration systems - Infrastructure services and hosting environments - Official Project Tick domains and email accounts - Public representation of the project Individuals representing Project Tick in any official capacity are expected to uphold this Code at all times. 6. Reporting ------------ Violations may be reported confidentially to: conduct@projecttick.org Reports will be reviewed in a timely and objective manner. Confidentiality will be respected to the extent reasonably possible. Malicious or knowingly false reports may themselves constitute a violation. 7. Enforcement -------------- Enforcement decisions are made by the Project Tick maintainers. Depending on severity, actions may include: 1. Private warning 2. Temporary communication restriction 3. Temporary suspension of repository access 4. Permanent removal of access to Project Tick spaces Serious security, infrastructure, or legal violations may result in immediate permanent removal. Enforcement decisions are final and are not subject to public vote. 8. Remediation -------------- Where appropriate, resolution may involve: - Acknowledgment of harm - Corrective action or documentation - License compliance remediation - Demonstrated behavioral improvement Reinstatement after suspension is at the sole discretion of the maintainers. 9. Independence --------------- This document was inspired by Contributor Covenant 3.0 but has been independently written and adapted to reflect the governance, infrastructure, and legal priorities of Project Tick. Project Tick maintains full authority over the interpretation and enforcement of this Code.