Contrib.social

[policy, no patch] Establish a system for dealing with feature requests

Open on Drupal.org →
Created on 20 May 2015, almost 10 years ago
Updated 4 May 2023, almost 2 years ago

Problem/Motivation

The issue lists are full of feature requests, some very old. With the new plans to have a Drupal release every 6 months, imho the way we deal with feature requests should change.

No feature request should be allowed unless the code , or at least a plan and resource to deliver feature is available.

The new feature would have to be agreed to be desirable for inclusion in core.

To not exclude people from suggesting improvements, who may not be developers and unable to code the new feature / improvement, a new system of submitting ideas that they thought useful would need to be devised.

Comments would be allowed and a voting system added, so that popular ideas for new features would be very visible. An example of how the idea system works in Joomla ( http://ideas.joomla.org/forums/84261-joomla-idea-pool ).

Steps to reproduce

Proposed resolution

Make sure that Feature Requests (FRs) are in the correct queue, either core or Core Ideas queue → . The Core Ideas queue is seeking approval of the idea before working on implementation. These are most often issues requiring product manager → approval. The FRs in the core queue should be for augmenting existing features.

Remaining tasks

  1. Triage the Feature requests in core issue queue → to make sure they are in the correct queue.
  2. Update the definition of Feature request → to include when to use the Core Ideas queue. This needs proposed text.
  3. TBD

User interface changes

API changes

Data model changes

Release notes snippet

🌱 Plan
Status

Active

Version

10.1 ✨

Component
Other  →

Last updated about 6 hours ago

Created by

🇬🇧United Kingdom bill richardson

Live updates comments and jobs are added and updated live.
  • Needs release manager review

    It is used to alert the release manager core committer(s) that an issue significantly affects the overall technical debt or release timeline of Drupal, and their signoff is needed. See the governance policy draft for more information.

  • Needs product manager review

    It is used to alert the product manager core committer(s) that an issue represents a significant new feature, UI change, or change to the "user experience" of Drupal, and their signoff is needed. If an issue significantly affects the usability of Drupal, use Needs usability review instead (see the governance policy draft for more information).

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment almost 2 years ago →
    🇳🇿New Zealand quietone

    Starting to update the IS with a proposed resolution and tasks. These updates are from this slack thread where catch and Gábor Hojtsy responded.

  • Status changed to Postponed: needs info 3 days ago
  • Comment 3 days ago →
    🇳🇿New Zealand quietone

    Since the last comment here the core leadership team decided to stop using the Core Ideas project. That means that the current proposal here is outdated and needs to be re-discussed.

    On the other hand, there has been very little discussion here, so perhaps the community is managing with the current way of doing things?

    Is there interest in outling a more detailed process for feature requests? If there is no interest this may be closed after three months.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024