Distribution Modernization Initiative meeting on Jan 4, 2022
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3261814. -->
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: @kingdutch @bircher @briangilbert @navneet0693 @Tiago Barreiro de Siqueira @Mohammed Razem @finn @dww @Rajab Natshah (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.</h2>
<table>
<tr>
<td>hestenet (he/him)</td>
<td>Tim from the DA</td>
</tr>
<tr>
<td>Rajab Natshah</td>
<td>Rajab, Technical Product Lead at Vardot. A maintainer of the Varbase distribution.Love to help in speeding up the work of web developers to ship websites in a swift way.</td>
</tr>
<tr>
<td>dwkitchen</td>
<td>David from Centarro working on Commerce Kickstart 3.x</td>
</tr>
<tr>
<td>bircher</td>
<td>Fabian, long term interest</td>
</tr>
<tr>
<td>briangilbert (realityloop) (he/him)</td>
<td>Brian reporting, though still on holidays really</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️⃣ From the DA side, we've had much of the team out for the holidays - so we don't have major updates today - the main thing we're doing is stabilizing some testing infrastructure changes that are going to support the new architecture of distributions on d.o planned in this issue:<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></h2>
<table>
<tr>
<td>bircher</td>
<td>I think this sounds like a good plan. I think the templates for projects should continue with the -project suffix, that seems like much less confusion</td>
</tr>
<tr>
<td>Aaron McHale</td>
<td>I quite like this idea, could this eventually influence how Drupal itself is distributed, if we think of the drupal project page as a distribution of Core, and the drupal/recommended-project and drupal/legacy-project as the "templates" of the "Drupal distribution"?</td>
</tr>
<tr>
<td>bircher</td>
<td>yes drupal/recommended-project is how you start a project based off the standard distribution (or minimal distribution) ie just core. Pun intended :wink:</td>
</tr>
<tr>
<td>Aaron McHale</td>
<td>Yeah I understand what drupal/recommended-project etc are. What I mean is, are we going to get to a point where drupal/recommended-project is technically the same as say drupal/thunder-project. For instance, right now we have the project-core content type on D.o but project-distribution for all other distributions, are we heading in the direction where those would actually merge.</td>
</tr>
<tr>
<td>Aaron McHale</td>
<td>Maybe that's a question that isn't in scope right now, because when you download one of the zip/tar files from /project/drupal you don't get a Drupal distribution, you get a full installation of Drupal including Core.</td>
</tr>
<tr>
<td>Aaron McHale</td>
<td>Right now drupal/recommended-project and drupal/legacy-project are basically special snowflakes, and what we're doing here is saying we want to open this up to any other Drupal project to take advantage of. So I guess, that might mean that /project/recommended and /project/legacy should be created on D.o, and then, instead of <a href="https://github.com/drupal/recommended-project">https://github.com/drupal/recommended-project</a> and <a href="https://github.com/drupal/legacy-project">https://github.com/drupal/legacy-project</a> just being subtree splits of a directory of core (or whatever they are), they actually become their own Git repositories on <a href="https://git.drupalcode.org/">https://git.drupalcode.org/</a>. That essentially means that drupal/recommended-project and drupal/legacy-project would actually be the same thing as a future Thunder or Commerce template, and gives other projects a working example to start from.</td>
</tr>
<tr>
<td>Aaron McHale</td>
<td>(Okay I guess technically even as D.o projects recommended and legacy could still be subtree splits of core, but by doing it that way it means they're no longer special snowflakes and everyone benefits from that) (edited)</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>(@mixologic ^^ think you may find this interesting)</td>
</tr>
<tr>
<td>Aaron McHale</td>
<td>We will need to redesign what is presented to end users when they navigate to the distribution section of drupal.org (linked off the main menu under Build->Distributions)If we did what I just suggested, then this discoverability work (I presume we're talking on the project page itself) could also be done for project-core, win win.</td>
</tr>
<tr>
<td>Aaron McHale</td>
<td>Distribution templates will use the "general project" type. If a general project has a composer.json, and that composer.json declares itself to be of "type": "project", then we will add that project template to the drupal/ namespace on packagist.org.As a side question, I presume that in reality this would mean that said projects would be mirrored on github.com/drupal, or has Packigist made it possible to use something other than GitHub?</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>Yeah - I think this was meant to be more explicit in that issue, but yes - we'd put those templates in the github.com/drupal namespace for packagist visibility the way we do with recommended-template now and such</td>
</tr>
<tr>
<td>Aaron McHale</td>
<td>Yeah - I think this was meant to be more explicit in that issue, but yes - we'd put those templates in the github.com/drupal namespace for packagist visibility the way we do with recommended-template now and suchCool, sounds good, just wanted to clarify that. Yeah maybe the issue could use a sentence about that then :slightly_smiling_face: (edited)</td>
</tr>
</table>
<p>Participants:</p>
<p>hestenet, Rajab Natshah, dwkitchen, bircher, briangilbert (realityloop) (he/him), Aaron McHale</p>
issue