Distribution Modernization Initiative meeting on Feb 1, 2022
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3261816. -->
Reported by: [hestenet](https://www.drupal.org/user/54034)
>>>
<p>This meeting:<br>
➤ Is for distribution developers, initiative contributors, the Drupal Association and anyone interested in the initiative.<br>
➤ Usually happens every other Tuesday at 1400 UTC.<br>
➤ Is done over chat.<br>
➤ Happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously!<br>
➤ Has a public agenda anyone can add to.<br>
➤ *Transcript will be exported and posted* to the agenda issue. For anonymous comments, start with a :bust_in_silhouette: emoji. To take a comment or thread off the record, start with a :no_entry_sign: emoji.</p>
<p>ping: @mixologic @kingdutch @bircher @briangilbert @navneet0693 @Tiago Barreiro de Siqueira @Mohammed Razem @finn @dww @Rajab Natshah @Aaron McHale @alexpott (go to the issue of the next meeting to add or remove yourself from the list)</p>
<p>:thankful: I'd also like to take a moment to highlight our initiative sponsor! Discover Global Network has generously stepped forward to provide resources that are allowing the Drupal Association to make the necessary updates to modernize distribution support on Drupal.org. Feel free to check them out at: <a href="https://www.discoverglobalnetwork.com/">https://www.discoverglobalnetwork.com/</a></p>
<h2>0️⃣ Who is here today? Comment in the thread below to introduce yourself and tell us why you are joining us. Also - how's the new year treating you? :slightly_smiling_face:</h2>
<table>
<tr>
<td>hestenet (he/him)</td>
<td>Tim from the DA - in Portland, OR, USA :wave::skin-tone-3:Can't believe Jan is already gone. 2022 moving too fast....</td>
</tr>
<tr>
<td>mixologic</td>
<td>Thats.. too fast. I cant believe Drupalcon is just around the corner</td>
</tr>
<tr>
<td>mixologic</td>
<td>And of course Im here, from the DA</td>
</tr>
<tr>
<td>ronaldtebrake</td>
<td>Ronald from Open Social in Zwolle the Netherlands. Some exciting things planned for the year only to realize its indeed already February :scream:</td>
</tr>
<tr>
<td>Ted Gifford</td>
<td>Ted from WebFirst - in Rockville, MD, USAI'm sad we missed most of the recent nor'easter snowstorm. I'm working on distributions with HHS (primarily for small topic sites on the periphery of hhs.gov).</td>
</tr>
<tr>
<td>Ted Gifford</td>
<td>I'm here to listen today. We're using a distribution as a tool to balance standardization of features and quick site creation against customization and maintenance concerns (multiple development vendors and sites are involved).</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>@Ted Gifford If you haven't already seen it, here is the approximate plan: <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/project_composer/-/issues/3252534" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/project_composer/-/issues/3252534</a></span></td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>(well for the drupal.org side of things)</td>
</tr>
<tr>
<td>Ted Gifford</td>
<td>I have seen, if not fully grokked. We're using Satis and composer create-project at the moment, but we also have a profile and a number of shared internal modules. I'm not sure we'll ever be able to publish a distro on d.o but I want to stay up-to-date on the discussions here. Thanks for organizing these meetings/threads.</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>You're very welcome</td>
</tr>
<tr>
<td>mixologic</td>
<td>Very important is that the plan we’re talking about is for distributions that drupal.org hosts. It is not a comprehensive “how distros can be used, internally” sort of thing.</td>
</tr>
<tr>
<td>Ted Gifford</td>
<td>Understood.</td>
</tr>
<tr>
<td>briangilbert (realityloop) (he/him)</td>
<td>Brian Gilbert (realityloop) upset I will miss DC Portland, travelling from Australia atm with COVID diesn't really seem viable (edited)</td>
</tr>
<tr>
<td>bircher</td>
<td>Fabian Bircher, the new year seems to go super fast, I guess that is what happens when you are busy and get older.</td>
</tr>
</table>
<h2>1️⃣ Do you have any topics to propose for the meeting today? Feel free to propose them in this thread, and then I will give them their own unique threads for discussion. Conversation moving slow? Go ahead and open your own thread in the next numeric order.</h2>
<table>
</table>
<h2>2️⃣ Drupal Association update:As we spoke about in previous meetings - we wanted to update the GitLabCI runner/k8s configuration as a precursor to some additional work on this initiative and in support of the GitLab Acceleration initiative at the same time.That runner configuration is complete, but we've needed to pivot to do some support for the Core release process for the D10 alpha and for some other core testing.</h2>
<table>
<tr>
<td>hestenet (he/him)</td>
<td>@mixologic Feel free to add anything that makes sense.</td>
</tr>
<tr>
<td>mixologic</td>
<td>My only comment is that we dont have a whole lot of public input on the plan outlined here: [#3252534]This is what we'll implement and if theres any way we can do it better, input would be appreciated.</td>
</tr>
<tr>
<td>ronaldtebrake</td>
<td>Out of curiosity, i can potentially see Distributions having a lot more test coverage that might impact the CI. Not sure how that affects the costs or potentially the runners themselves. Is that something to address or mitigate in any way?</td>
</tr>
<tr>
<td>mixologic</td>
<td>The current plan is to investigate runner minute limits.</td>
</tr>
<tr>
<td>mixologic</td>
<td>basically, we cant offer unlimited free testing.</td>
</tr>
<tr>
<td>mixologic</td>
<td>But also, gitlab makes it very easy for a project to bring their own runners if they want.</td>
</tr>
<tr>
<td>Gábor Hojtsy (he/him)</td>
<td>It would be great to discuss this issue on the next core committer + DA meeting too, as there has been a LOT of discussion among core committers recently about where distributions might / should be going :smile: I pinged the above issue to them as well.</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>That would be great feedback - I'll pop it onto our agenda.</td>
</tr>
<tr>
<td>bircher</td>
<td>I'll comment on the issue, I have recently made some experiments.</td>
</tr>
<tr>
<td>bircher</td>
<td>@Gábor Hojtsy (he/him) that sounds super interesting! I am glad distributions come more into focus again on multiple levels</td>
</tr>
<tr>
<td>smccabe</td>
<td>I'm late to the party, but regarding testing profiles, we built a couple of traits specifically for testing profiles. With some profile install caching we've probably cut our test server load down by at least 75% <a href="https://github.com/AcroMedia/drupal-test-traits">https://github.com/AcroMedia/drupal-test-traits</a></td>
</tr>
<tr>
<td>Gábor Hojtsy (he/him)</td>
<td>For the record we ran out of time today on the DA meeting with committers, so we did not succeed talking about this yet there.</td>
</tr>
</table>
<h2>I just created <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/3263053" title="Status: Active">#3263053: Distributions and configuration updates</a></span> which might be of interest to people in this channel.</h2>
<table>
<tr>
<td>hestenet (he/him)</td>
<td>@mixologic An issue we may want to follow</td>
</tr>
<tr>
<td>mixologic</td>
<td>yeah, looks like from a composer facade/build perspective theres nothing to impact us. Right now, if you update a project with composer, there is still an additional step to run the update hooks in drupal if there are DB changes. This seems like a similar pattern where there would still be a composer update step, and a separate configuration update step.</td>
</tr>
<tr>
<td>mixologic</td>
<td>From a “what is a distribution and how can they be maintained” this seems to help solve some of the inherent conflict of shipping a mutable product, and then trying to update that mutated product from upstream.</td>
</tr>
<tr>
<td>alexpott</td>
<td>Yeah there’s nothing for the composer work here. It’s totally about “so you’ve used a distribution to start from and the distribution changes - what should happen”</td>
</tr>
<tr>
<td>mixologic</td>
<td>yep. which has always been tricky. events.drupal.org is based on COD distribution, and trying to make it do what we need it to do while simultaneously trying to keep in sync with upstream was a challenge to say the least.</td>
</tr>
<tr>
<td>mixologic</td>
<td>which sort of begs the question “Should distributions be starting points, or products that receive updates”</td>
</tr>
<tr>
<td>alexpott</td>
<td>Yep - a “debate” that’s go on for years. People want them to do both a the same time. So people want to start from a well configured spot and go off on their own. Other want to receive new things regularly. Some distribution maintainers want to lock down want people can do but then still allow them to make these changes if they really really want to.</td>
</tr>
<tr>
<td>alexpott</td>
<td>Even more fun is when people who start from something like Thunder then want to add commerce and would like to start from commerce kickstarts nice default state.</td>
</tr>
<tr>
<td>mixologic</td>
<td>By some definition of fun…</td>
</tr>
</table>
<p>Participants:</p>
<p>hestenet, Mixologic, ronaldtebrake, Ted Gifford, briangilbert (realityloop) (he/him), bircher, Gábor Hojtsy, smccabe, alexpott</p>
issue