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

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