Over at #2785735: [policy, no patch] Agile process for bigger changes in core (Part A: Ideation) we're discussing possible implementation strategies for core ideation.

One idea that's come up there is adding more nuanced options in the "category" selector for various stages of planning; for example:

While these (or something like them) would have utility in core, I'm unsure about their utility across all contrib projects (categories are not project-specific), and also unsure how much bikeshedding is required to get to a list that works for everyone, so splitting this off for discussion here.

Hopefully this is pretty easy to implement though when/if consensus is achieved; David_Rothstein pointed out that this seems to be all that was required to add "Plan."

Comments

webchick created an issue. See original summary.

webchick’s picture

Title: Create new issue categories to adjust for different planning stages » Create new issue categories to account for different planning stages
frob’s picture

My only concern for having this be a Category instead of a separate queue is the core component select list is massive and difficult to navigate and required. I don't want to hold this up, I just want to know if there are any solutions to this that I am not aware of.

David_Rothstein’s picture

I think the most intuitive categories would be (in order):

  • Bug report
  • Support request
  • Feature request
  • Big change - idea
  • Big change - roadmap
  • Big change - prototype
  • Task

(where "Big change - roadmap" is a renamed version of the current "Plan" category)

I do think these new categories would be useful to the larger contrib projects in the Drupal ecosystem, not just Drupal core. (Especially for distributions, but for some large contrib modules also.)

"Plan" (an overall plan, similar to #2755073: WI: Content Moderation module roadmap.
....
"To-do" list (plan's been agreed on, now onto implementation, broken up into smaller steps, ala #2735005: PHPUnit initiative: Convert all Simpletest web tests to BrowserTestBase (or UnitTestBase/KernelTestBase)

I don't really see the difference; the first one looks like a to-do list to me also :)

But it does suggest that "roadmap" might be a much better name than "to-do list", so I used that above. It is interesting that "roadmap" never seems to have come up as a suggestion in #1815826: Add "Plan" category to categorize what is called "meta issues" in core right now.

... the core component select list is massive and difficult to navigate and required. I don't want to hold this up, I just want to know if there are any solutions to this that I am not aware of.

#2797887: Add a default component 'Unknown' to the Drupal core issue queue would hopefully help.

frob’s picture

@David_Rothstein, yes there looks to be some good work going on to fix the core component list. Thank you.

Fabianx’s picture

+1 to #4, but we need a patch :)