>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #2973567. --> Reported by: [alexpott](https://www.drupal.org/user/157725) >>> <ul> <li>Introductions - who's who, if people would like to say why they are interested in the initiative. <ul> <li>Alexpott - core committer</li> <li>Mtodor - thunder maintainer</li> <li>Moshe - core contributor / drush maintainer</li> <li>Vijaycs85 - config schema / CMI contributor</li> <li>Bircher - config module maintainer</li> </ul> </li> <li>Initiative recruitment / mentoring <ul> <li>The initiative seems to be really complicated</li> <li>We need easier issues to start for people to start with <ul> <li>Also split bigger issues into smaller ones, so that it's easier for contributors to start with providing solutions</li> <li>Clean-up issue queue, provide feedbacks and propose solutions - in short: do as much as possible preparation on issues for potential contributors</li> </ul> </li> <li>Action still to do: post to <a href="http://groups.drupal.org/core">http://groups.drupal.org/core</a></li> <li>Reach out mpotter to join team</li> <li>Attending Drupal events and reach out in person/sprints <ul> <li>Increase or try to keep high presence in Drupal events</li> <li>DDD session proposal: <a href="https://lisbon2018.drupaldays.org/sessions/cmi-20-and-configuration-management-contrib-today">https://lisbon2018.drupaldays.org/sessions/cmi-20-and-configuration-management-contrib-today</a></li> </ul> </li> </ul> </li> <li>Discussion on CMI 2.0 problem matrix <a href="https://docs.google.com/spreadsheets/d/1MVZPpj4h7o-wb5JzSI-gGgdmPZ_KwGf3kmAWOq7kn2E/edit#gid=0">https://docs.google.com/spreadsheets/d/1MVZPpj4h7o-wb5JzSI-gGgdmPZ_KwGf3kmAWOq7kn2E/edit#gid=0</a> \<br> <a href="https://www.drupal.org/project/cmi2/issues/2969036">https://www.drupal.org/project/cmi2/issues/2969036</a> <ul> <li>Agreed scoring matrix columns and multipliers</li> <li>Discussed whether the task list was complete based on the plan issue</li> <li>How do we address the tension between reliable repeatable deployments vs the flexibility needed for distribution update / feature sharing / different configuration in different environments -&gt; <ul> <li>Only edit config on export / import</li> <li>Is there such a thing as safe config?</li> </ul> </li> </ul> </li> <li>Open discussion <ul> <li>We touched topic related to protecting configuration from editing in different environments (fe. blocking of configuration change on production) and should that be part of CMI. Where we came to conclusion that such functionality should stay part of contrib (like config_readonly module), but that core could provide some API for achieving such goal easier</li> <li>We came to conclusion that additional topics should be added to problem matrix and adjusted it accordingly. Two new entries added: <ul> <li>Documentation</li> <li>Different config in different environments</li> </ul> </li> </ul> </li> <li>Preparation for next meeting <ul> <li>Go over issue queue and find existing issue related to topics listed in Problem Matrix, so that we have list of defined tasks related to major topics</li> <li>Write additional missing issues related to topics listed in Problem Matrix</li> </ul> </li> </ul>