Managing Feature Requests for Joomla on GitHub

[HLeithner]

Feature Request Flow

Objective

The new feature workflow introduces a revised approach designed to make our feature process more sustainable and easier to manage—for both themaintainers and the wider community. At this stage, it is being trialled, and we hope it proves successful.

The Flow

1. Feature Areas Overview

• Feature Evaluation: Open space for all contributors to post ideas. Community discussion area; under active review
• Cold Features: Existing feature ideas that are either older on import or have had little interest
• Approved Features: Ideas that will be implemented, with target Joomla version indicated
• Rejected Features: Ideas that will not be implemented, with reasoning for transparency
• Implemented Features: Completed and shipped features included in Joomla
• Archived Discussions: Discussions which are be duplicates or not relevant or other discussions which are read only.

---

2. Existing Feature Requests

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:
  • Feature Evaluation: – 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.

---

3. Workflow for New Feature Requests

Step 1: Create a New Feature Idea

• Anyone can post a new feature idea in the Feature Evaluation discussion area.
• Each idea should include:
  • Problem statement
  • Proposed solution
  • Expected benefit or use case
  • Optional: screenshots, mockups, or links to examples

---

Step 2: Feature Evaluation

• Once a new feature is posted, maintainers will either:
  • Reject the idea (with explanation, ex. duplicate), or
  • Keep it in Feature Evaluation for further community discussion
• Timeline: Move within 2–4 weeks of posting
• During Feature Evaluation:
  • Anyone can comment, provide feedback, or discuss potential improvements, up/down vote
  • Maintain a constructive, collaborative tone

---

Step 3: Approval or Rejection

• After evaluation, maintainers will either:
  • Reject the feature (with rationale), or
  • Approve the feature and move it to Approved Features
• Timeline: 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)

---

Step 4: Implementation

• 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.

---

4. Roles and Permissions

Role	Permissions / Responsibilities
Anyone	Post Feature Evaluation, 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

5. Additional Guidelines

• Encourage community participation but maintain clear timelines
• Maintainers should provide clear rationale when rejecting ideas
• COLD Features can be reviewed at any time

---