>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #2968984. --> 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 maintainer, configuration system maintainer - interested in installing from configuration and improving the system.</li> <li>mtodor, thunder distribution - config management and updating as part of the distribution - update helper module. Interested in how to update new configuration provided by a distribution - how to add new features to live sites.</li> <li>bircher, maintainer of config_split, config_filter, config_distro module. Works for Nuvole, an early adopter of config management in D8. Interested in site instance specific configuration and improving the extensibility of the configuration system.</li> </ul> </li> <li>Ways of working <ul> <li>Do we have a regular meeting, frequency <ul> <li>For a start every two weeks over hangout - at 15:00 UTC (or for calendar entry GMT)</li> </ul> </li> <li>Meeting format - hangouts vs something? Slack only like JS and DD&amp;I? The nice thing about doing in Slack is no need for someone to take notes and we can do meeting credits - see <a href="https://www.drupal.org/project/jsdrupal/issues/2968860">https://www.drupal.org/project/jsdrupal/issues/2968860</a> <ul> <li>We use #config on slack to discuss but have regular hangouts for spoken conversations</li> <li>Everyone tries to collect meeting notes during hangout meeting and put them in Google Doc - after meeting it will be copy/pasted into issue so that other community members read it too</li> <li>General preference of attendees was for hangouts but if attendance increases or people raise it as an issue will move to slack-only to accommodate.</li> </ul> </li> <li>How to recruit people to initiative &amp; how do we say hello? <ul> <li>Create project with description how to join initiative (infos like: slack channel, meeting times, issue queue tags, people to ask, etc.)</li> <li>Post to <a href="http://groups.drupal.org/core">http://groups.drupal.org/core</a></li> </ul> </li> <li>How do we reduce administrative burden whilst maximising inclusion and success? <ul> <li>Not resolved</li> </ul> </li> </ul> </li> <li>The idea <a href="https://www.drupal.org/project/ideas/issues/2957423">https://www.drupal.org/project/ideas/issues/2957423</a> - how do we break this down into deliverables and what are they? <ul> <li>Try to prioritize features, if it's possible with some scoring</li> <li><strong>Action</strong>: alexpott to ask for spreadsheet from webchick</li> <li><strong>Action</strong>: alexpott to speak to mglaman about using <a href="https://contribkanban.com">https://contribkanban.com</a> </li> </ul> </li> <li>Possible areas of focus: <ul> <li>Installing from config - we're pretty sure we know what we are doing here in terms of adding the plumbing (<a href="https://www.drupal.org/project/drupal/issues/2788777">https://www.drupal.org/project/drupal/issues/2788777</a>) and then making a UI and it more useful.</li> <li>Distributions - lots of issues on how to manage <ul> <li>Installing them</li> <li>Deploying them</li> <li>Updating them</li> </ul> </li> <li>Site instance specific configuration <ul> <li>Modules that are installed on one instance and not meant to be deployed. For example, the devel module or file stage proxy</li> <li>Contact reply to emails</li> <li>API keys</li> </ul> </li> <li>Documentation lacking. <ul> <li>Try to get best practices</li> <li>What goes in config</li> <li>Configuration management workflows</li> </ul> </li> </ul> </li> </ul>