jmiller
5ea2fd2b98
Joomla aborts the entire package install on any SQL error in update files. DROP COLUMN fails when catid doesn't exist (fresh installs, or systems where it was already removed). Since install.mysql.sql already omits catid, no runtime migration is needed. Authored-by: Moko Consulting
Code of Conduct
1. Purpose
The purpose of this Code of Conduct is to ensure a safe, inclusive, and respectful environment for all contributors and participants in Moko Consulting projects. This applies to all interactions, whether in repositories, issue trackers, documentation, meetings, or community spaces.
2. Our Standards
Participants are expected to uphold behaviors that strengthen our community, including:
Demonstrating empathy and respect toward others. Being inclusive of diverse viewpoints and backgrounds. Gracefully accepting constructive feedback. Prioritizing collaboration over conflict. Showing professionalism in all interactions.
Unacceptable behavior includes:
Harassment, discrimination, or derogatory comments. Threatening or violent language or actions. Disruptive, aggressive, or intentionally harmful behavior. Publishing others’ private information without permission. Any behavior that violates applicable laws.
3. Responsibilities of Maintainers
Maintainers are responsible for:
Clarifying acceptable behavior. Taking appropriate corrective action when unacceptable behavior occurs. Removing, editing, or rejecting contributions that violate this Code. Temporarily or permanently banning contributors who engage in repeated or severe violations.
4. Scope
This Code applies to:
All Moko Consulting repositories. All documentation and collaboration platforms. Public and private communication related to project activities. Any representation of Moko Consulting in online or offline spaces.
5. Enforcement
Instances of misconduct may be reported to: hello@mokoconsulting.tech
All reports will be reviewed and investigated promptly and fairly. Maintainers are obligated to maintain confidentiality where possible.
Consequences may include:
A warning. Required training or mediation. Temporary or permanent bans. Escalation to legal authorities when required.
6. Acknowledgements
This Code of Conduct is inspired by widely adopted community guidelines, including the Contributor Covenant and major open-source collaboration standards.
7. Related Documents
Governance Guide Contributor Guide Documentation Index
This Code of Conduct is a living document and may be updated following the established Change Management process.