Updated: Comment #0
Problem/Motivation
Far more core issues are filed against "base system" than anything else -- 617 total open issues, with 70 of them major or critical. The label is so vague, and the category so broad, that it makes it difficult to triage this queue, identify stakeholders, etc.
The maintainers for "base system" in MAINTAINERS.txt are:
Base system
- Károly Négyesi 'chx'http://drupal.org/user/9446
- Damien Tournoud 'DamZ'http://drupal.org/user/22211
- Moshe Weitzman 'moshe weitzman'http://drupal.org/user/23
- Kat Bailey 'katbailey'http://drupal.org/user/172987
- Larry Garfield 'Crell' http://drupal.org/user/26398All people who deal with low-level plumbing, for sure. But what, in particular? And can these people really provide maintainership for so many issues?
Base system is not:
- The installer (has a separate entry)
- Routing (has a separate entry)
Base system might include:
- Bootstrap
- The kernel
- The container
- Stuff in core/includes that doesn't have its own listing, especially stuff from
common.incandbootstrap.inc. - Stuff people don't know how to file.
Proposed resolution
Let's refine the "base system" component.
- Identify specific sub-categories that could be added as separate components:
- Look for patterns in the "base system" queue.
- Get feedback from "base system" maintainers and core developers.
- Add these components to 3060.
- Add these components to MAINTANERS.txt, and identify maintainers for them.
- Triage the "base system" queue to move relevant issues to new (or existing) components where appropriate.