>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3491176. --> Reported by: [berdir](https://www.drupal.org/user/214652) >>> <p>I originally started writing this this in <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/3491129" title="Status: Closed (fixed)">#3491129: Drupal Core strategy for 2025-2028, developer consultation</a></span>, but realized that it's probably neither about the strategy nor Drupal Core but something else. Governance? And it's more about Drupal CMS than Drupal Core but I guess really it's just about Drupal.</p> <p>Apart from Drupal Core, Drupal CMS for the most part consists of (many) contrib projects. We all rely on contrib and its maintainers to provide the features we need to build our websites, but we also kind of know that the rules for contrib so far were different, more relaxed and up to the specific maintainer(s). In regards to test coverage, stability, release management, ... </p> <p>With Drupal CMS, there's quite a shift. A large chunk of contrib is now suddenly part of the official Drupal product. But unlike Drupal Core, which has a team of maintainers as well as more or less active subsystem maintainers, probably the majority of contrib projects are one-person shows. While there are often contributors for specific things, it's typically one person that does the reviewing, committing and releasing. What impact will this have on governance, funding and other aspects of contrib maintenance? Will this result in different types of contrib, the official ones that are part of Drupal CMS and the others?</p> <p>As someone who maintains quite a lot of contrib projects, several of which are and will be in Drupal CMS, I have some concerns and questions about how that will play out. What if the product managers of Drupal CMS want a Redirect feature that I'm not willing to maintain? What if I add a feature to Pathauto that conflicts with the strategy of Drupal CMS?</p> <p><span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupal_cms/-/work_items/3488829" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupal_cms/-/work_items/3488829</a></span> is a good example, and I'll add a separate comment there as well. A policy is suggested that RC/stable releases must not have patches. But what if a patch doesn't get committed?</p> > Related issue: [Issue #3447882](https://www.drupal.org/node/3447882) > Related issue: [Issue #3501710](https://www.drupal.org/node/3501710)