Evaluations for moving core modules to contrib

Problem/Motivation

At DrupalCon Portland, Dries proposed a new initiative to move approximately 20% of core's current modules to contrib by Drupal 11. Some of these are already being worked on for Drupal 10 in #3118154: [meta] Deprecate dependencies, libraries, modules, and themes that will be removed from Drupal 10 core by 9.4.0-beta1. Others might not happen in time for Drupal 10 and can be deprecated in Drupal 10 and removed from Drupal 11.

In that keynote, Dries proposed the following evaluation criteria for evaluating which modules would be best suited for moving out of core:

1. Does it fall under one of the 4 foundational capabilities that Dries defined: content modeling, content authoring, content delivery, or system operations?
2. Is it used by a lot of sites?
3. Does it have significant strategic value to Drupal?
4. Is it straightforward to maintain?

Modules that have more No's than Yes's to the above questions are good candidates for moving out of core.

Proposed resolution

The next step is for the core committer team to share our initial evaluation of modules against those 4 questions.

Then, we can use this issue to gather feedback with which to refine that evaluation.

Remaining tasks

See above.