Document the ideas process

Created on 12 September 2017, over 7 years ago
Updated 1 April 2025, 1 day ago

Based on some of the discussion at #2905741: *DRAFT* Proposed product goals for Drupal 8.5/8.6(+) core , we need to document "how a bill becomes a law" (or how an idea, becomes a proposed plan, becomes an approved plan, becomes an active initiative, gets added to the list of product goals for a given release). We discussed a lot of this in #2785735: [policy, no patch] Agile process for bigger changes in core (Part A: Ideation) , at DrupalCons, etc. but it hasn't really made its way to the docs.

Started in on some stuff here, to replace the current project page:

https://docs.google.com/document/d/1fMjEeftW7uiDy1TDLkdudzZjoMt5AuBKwPpy...

Not really ready for review yet.

📌 Task
Status

Closed: won't fix

Component

Active Initiative

Created by

🇨🇦Canada webchick Vancouver 🇨🇦

Live updates comments and jobs are added and updated live.
  • 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.

Production build 0.71.5 2024