Starting with 2.2, each major version will be composed of feature proposals, each proposal will be in a 3 month period, where it is open for discussion on the forum. After that, proposal will be either rejected, accepted or moved to other major version planning.
Everyone will be able to propose changes/feature, but only the best will be moved forward.
Proposal statuses: #review_pending < → #more_information_needed → #open_for_discussion → #accepted or #rejected or #frozen where frozen means that proposal discussion will be continued in the next major milestone
Each proposal will have progress status updated and PRs linked.
Proposal requirements
Each proposal must contain:
-
a clear description of the proposal: is it a completely new feature, extension of existing system or overhaul of existing system.
-
A clear description of what proposal solves and what is the rationale behind it
-
Who will benefit from the described changes (what group of users will feel the changes)
-
References if available
Proposal needs to be professionally written, proper research about the topic must be included. Low effort submissions will result in automatic rejection as we only care about well thought, human-made proposals.
How is proposal different to feature requests on Forum/GitHub?
Proposal requires more work and it goes through a longer process, but if accepted, it is guaranteed to be implemented in a given version. We guarantee to at least give feedback about why proposal got rejected.
Whereas feature requests are a way to dump your idea and show us, that you’d like something. We might consider it if we decide it is a good idea. It’s entirely up to core developers if feature request is considered.
Core development team will use proposals for major features and redesigns, so it can be discussed with the community.