Feature Request Process

🌐 EN | PT | ES

This document explains how to propose new features for AIOX.

Quick Ideas

For quick ideas or small improvements:

Open a Discussion in the "Ideas" category
Describe the problem and proposed solution
Community and maintainers will discuss
If there's interest, it may be promoted to RFC

RFC Process (For Significant Features)

For larger features that require design decisions:

When to Write an RFC

New major features
Breaking changes
Significant architectural changes
Changes affecting many users

RFC Lifecycle

Draft: Author writes RFC using our RFC Template
Under Review: 2-week comment period
Decision: Maintainers accept/reject
Implementation: If accepted, implementation begins

Criteria for Acceptance

Aligns with project vision
Technically feasible
Has clear implementation path
Community demand demonstrated
Maintainable long-term

Voting

Use :+1: reactions to show support
Top-voted ideas are prioritized
Maintainers have final decision

Timeline

Ideas: No fixed timeline
RFCs: 2-week minimum review period
Implementation: Based on roadmap capacity

From Idea to Implementation

Community Idea (Discussion)
        │
        │ [Approved by maintainers]
        ▼
Internal Backlog Item
        │
        │ [Prioritized by Product Owner]
        ▼
Sprint Planning
        │
        │ [Implemented by Development Team]
        ▼
Release (credited in CHANGELOG.md)

Who Can Add to Backlog?

The Product Owner (@po) is the sole authority for adding items to the internal backlog. This ensures proper prioritization and alignment with project goals.

Contributor Credit

Contributors whose ideas are implemented will be credited in:

The CHANGELOG.md release notes
The PR that implements the feature
Our contributors page (if applicable)

Questions?

Ask in GitHub Discussions or Discord.