To create a structured, transparent, and efficient process for handling Joomla feature requests, from initial idea through evaluation, approval, and implementation, using GitHub Discussions and Issues.
- New Feature Ideas: Open space for all contributors to post ideas
- Cold Feature Ideas: Existing feature ideas that are either oldert than X or have had little interest
- Feature Evaluation: Community discussion area; ideas under active review
- Approved Features: Ideas that will be implemented, with target Joomla version indicated
- Implemented Features: Completed and shipped features including Joomla version
- Rejected Features: Ideas that will not be implemented, with reasoning for transparency
- Duplicated Features: Ideas that already exist with link
To organize the current backlog of feature requests:
- All existing issues flagged as Feature will be moved to the new Feature Request Discussion area.
- Classification based on activity:
- NEW Features – Issues with the last comment in 2025/2026.
- COLD Features – Issues with the last comment before 2025.
This ensures maintainers and contributors can focus on active ideas while keeping historical requests accessible.
- Anyone can post a new feature idea in the New Feature Ideas discussion area.
- Each idea should include:
- Problem statement
- Proposed solution
- Expected benefit or use case
- Optional: screenshots, mockups, or links to examples
- Once a new feature is posted, maintainers will either:
- Reject the idea (with explanation), or
- Move it to Feature Evaluation for further community discussion
- Timeline Suggestion: Move within 2–4 weeks of posting
- During Feature Evaluation:
- Anyone can comment, provide feedback, or discuss potential improvements
- Maintain a constructive, collaborative tone
- After evaluation, maintainers will either:
- Reject the feature (with rationale), or
- Approve the feature and move it to Approved Features
- Timeline Suggestion: Decision should occur within 4–6 weeks of entering evaluation
- When approving, maintainers can set a Minimum target Joomla version for implementation (there may be backwards compatibility restrictions)
- Approved features are implemented in the Joomla codebase.
- Once implemented, the feature is moved to Implemented Features, marking it as completed and the Joomla version it has been merged to.
| Role | Permissions / Responsibilities |
|---|---|
| Anyone | Post New Feature Ideas, comment on Feature Evaluation discussions |
| Maintainers | Move ideas through stages (Evaluation → Approved/Rejected), set target Joomla version, provide guidance and timelines, close discussions after decision |
- Encourage community participation but maintain clear timelines
- Maintainers should provide clear rationale when rejecting ideas Have a set of pre-written explanations that can be used.
- Use labels to indicate status (e.g.,
new,evaluation,approved,implemented,rejected) - COLD Features can be reviewed at any time
This workflow creates transparency, encourages community engagement, and ensures Joomla development is responsive to genuine user needs while maintaining maintainers’ oversight.
Changed