jmiller
b9bf7750dd
Updated version in all .ini, .php, .md files to 02.01.08. Added SHA256 checksum to updates.xml for install integrity validation. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
3.8 KiB
Contributing to MokoWaaS (VERSION: 02.01.08)
Overview
Contributions to the MokoWaaS plugin follow standardized development, governance, and quality control expectations defined by Moko Consulting. This document outlines contribution requirements, acceptable change types, branch management, testing expectations, and release readiness standards.
1. Contribution Workflow
All contributions must follow the established workflow:
- Fork the repository or create a feature branch (if internal).
- Ensure your environment matches the supported Joomla and PHP versions.
- Implement changes following coding, documentation, and metadata standards.
- Validate plugin functionality locally.
- Submit a Pull Request (PR) for review.
2. Branching Model
main: Production stable branch.develop: Aggregates work for the next minor release.feature/*: New enhancements or changes.bugfix/*: Hotfixes and corrections.
Internal teams must coordinate with governance before creating major feature branches.
3. Coding and Documentation Standards
All code must:
- Follow MokoStandards coding standards
- Include the unified SPDX license header
- Include a FILE INFORMATION metadata block
- Avoid deprecated Joomla APIs
- Preserve load order compatibility with other system plugins
Documentation must:
- Include metadata
- Maintain revision history
- Use consistent formatting as defined by Moko documentation standards
4. Testing Requirements
Before submitting a PR, contributors must verify:
- Plugin installs successfully in Joomla 5.x
- No load errors appear in logs
- Branding replacements appear as expected
- Terminology strings are correct
- No regressions in administrator UI
Automated testing coverage will expand as part of future roadmap enhancements.
5. Pull Request Requirements
A PR must include:
- Description of change
- Screenshots for UI related updates
- Version updates when appropriate
- Notes for documentation changes
- Reference to related issues or tasks
PRs lacking required information may be flagged or delayed.
6. Release Versioning
Changes must follow semantic versioning:
- MAJOR: Structural branding or architectural changes
- MINOR: Feature updates or terminology expansion
- PATCH: Bug fixes or language corrections
Version updates must be reflected in:
- Manifest files
- PHP headers
- Documentation metadata
7. Code Review Standards
Reviewers validate:
- Code quality and clarity
- Compliance with MokoStandards coding standards
- Impact to templates and WaaS branding rules
- Backwards compatibility expectations
Revision History
| Date | Author | Description |
|---|---|---|
| 2025-12-11 | Jonathan Miller (@jmiller-moko) | Initial creation of contribution guidelines |