@@ -4,7 +4,7 @@ Just a collection of questions and answers.
...
@@ -4,7 +4,7 @@ Just a collection of questions and answers.
[Open a feature request](https://www.drupal.org/node/add/project-issue/drupal_cms) and explain what the module/recipe does and why it would benefit Drupal CMS. Don't be afraid to get detailed, but **_don't_** make a merge request yet.
[Open a feature request](https://www.drupal.org/node/add/project-issue/drupal_cms) and explain what the module/recipe does and why it would benefit Drupal CMS. Don't be afraid to get detailed, but **_don't_** make a merge request yet.
Drupal CMS's development, which includes decisions about which modules it should include, is guided by the product owner and UX lead (see [MAINTAINERS.txt](https://git.drupalcode.org/project/drupal_cms/-/blob/2.x/MAINTAINERS.txt?ref_type=heads)). If the product owner agrees that your module should be in Drupal CMS, it will be added. If you want to discuss it with them in real time, the correct place to do that is the `#drupal-cms-development` channel on Drupal Slack.
Drupal CMS's development, which includes decisions about which modules it should include, is guided by the product owner and UX lead (see [MAINTAINERS.txt](https://git.drupalcode.org/project/drupal_cms/-/blob/2.x/MAINTAINERS.txt?ref_type=heads)). If the product owner agrees that the proposed module or recipe should be in Drupal CMS, it will be. If you want to discuss it with the maintainers in real time, the correct place to do that is the `#drupal-cms-development` channel on Drupal Slack.
Once the product leadership signs off, getting the module into Drupal CMS falls to the committers, who will work closely with you to get everything ready, tested, merged, and released.
Once the product leadership signs off, getting the module into Drupal CMS falls to the committers, who will work closely with you to get everything ready, tested, merged, and released.
