>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3416778. --> Reported by: [hestenet](https://www.drupal.org/user/54034) >>> <p>This meeting:<br> &#10148; Is for core developers, initiative contributors, the Drupal Association and anyone interested in the initiative.<br> &#10148; Usually happens every other Wednesday at 11:00 PT / Thursday 18:00 UTC<br> &#10148; Is done over chat.<br> &#10148; Happens in threads, which you can follow to be notified of new replies even if you don&rsquo;t comment in the thread. You may also join the meeting later and participate asynchronously!<br> &#10148; Lots of threads get posted all at once! Don't worry - start at the top and then jump into the threads that most interest you.<br> &#10148; Has a public agenda anyone can add to in the issue<br> &#10148; *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 @FeyP @jurgenhaas (go to the issue of the next meeting to add or remove yourself from the list)</p> <p>:zero: Who is here today? Comment in the thread below to introduce yourself!</p> <p>:one: 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.</p> <h2>0&#65039;&#8419; Who is here today? Comment in the thread below to introduce yourself!</h2> <table> <tr> <td>hestenet (he/him)</td> <td>Tim from the DA :wave::skin-tone-3:</td> </tr> <tr> <td>markdorison</td> <td>Mark from Chromatic :wave:</td> </tr> <tr> <td>dww</td> <td>Derek (dww) :wave:</td> </tr> </table> <h2>1&#65039;&#8419; 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> <tr> <td>smustgrave</td> <td>Curious where we are with giving sub maintainers ability to close MRs</td> </tr> </table> <h2>2&#65039;&#8419; GitLab CI</h2> <table> </table> <h2>2&#65039;&#8419; 1&#65039;&#8419; Fix for 'Argument list too long' is in RTBC:<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/3401988" title="Status: Closed (fixed)">#3401988: Spell-checking job fails with "Argument list too long" when too many files are changed</a></span>&nbsp;(edited)&nbsp;</h2> <table> <tr> <td>acbramley</td> <td>This is biting me on almost every issue I touch, would be awesome to get it committed!</td> </tr> <tr> <td>wimleers (he/him)</td> <td>:100:&nbsp; same as @acbramley. Bumped it to Critical for that reason.</td> </tr> </table> <h2>2&#65039;&#8419; 2&#65039;&#8419; There was some question about updating some variable names, but about the impact this has on backwards compatibility for folks already using the templates.One idea:We could add a 'legacy' variables section to the variables include file in the templates, that maps any legacy variable names to the new ones we standardize on.&nbsp;(edited)&nbsp;</h2> <table> <tr> <td>G&aacute;bor Hojtsy (he/him)</td> <td>Sounds good IMHO. New major versions of the template can drop those.</td> </tr> <tr> <td>pingwin4eg</td> <td>There is a backward-compatibility example here - <a href="https://git.drupalcode.org/project/gitlab_templates/-/blob/1.0.x/includes/include.drupalci.main.yml?ref_type=heads#L652-658So">https://git.drupalcode.org/project/gitlab_templates/-/blob/1.0.x/includes/include.drupalci.main.yml?ref_type=heads#L652-658So</a> yes, just add new vars, and assign legacy ones to them.</td> </tr> </table> <h2>2&#65039;&#8419; 3&#65039;&#8419; Some updates to the runner cluster may be coming soon.&nbsp;(edited)&nbsp;</h2> <table> </table> <h2>3&#65039;&#8419; General GitLab Feature requests:This was recently submitted:<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/3416660" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/3416660</a></span></h2> <table> <tr> <td>fjgarlin</td> <td>Note that the compare link does exactly that, as you have the Create Merge Request in the page that it takes you to.So maybe we just style it as a button and call it Create MR?&nbsp;(edited)</td> </tr> <p>INCOMPLETE</p> <h2>4&#65039;&#8419; GitLab API paths - @drumm is unblocking various things from our HAProxyThere is some progress in new versions on permissions on certain things, making some of this easier.Also GitLab is properly redirecting you to where you were after login now, thanks to a recent update on their end.</h2> <table> <tr> <td>hestenet (he/him)</td> <td>Anything else to add on the general pass over GitLab stuff you've been doing, @drumm?</td> </tr> <tr> <td>drumm</td> <td>This is what was done:<a href="https://drupal.slack.com/archives/CGKLP028K/p170605024078554[#3414548]Removed">https://drupal.slack.com/archives/CGKLP028K/p170605024078554[#3414548]Removed</a> some paths that were doubled up since GitLab changed some user-related paths in their 16.7 release</td> </tr> <tr> <td>cmlara</td> <td>As always, it is appreciated opening up more endpoints. It does indeed help having them.</td> </tr> <tr> <td>wimleers (he/him)</td> <td>Nice RE: redirect upon signing in!</td> </tr> </table> <h2>5&#65039;&#8419;<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupalci/issues/3412417" title="Status: Closed (fixed)">#3412417: Disable DrupalCI testing</a></span> projects without DrupalCI can no longer start using DrupalCI. Tentatively, before DrupalCon Portland in May, no existing DrupalCI schedules will be able to be updated, and all new DrupalCI testing will be shut down on July 1st</h2> <table> <tr> <td>G&aacute;bor Hojtsy (he/him)</td> <td>@drumm with "all new DrupalCI testing will be shut down on July 1st" you meant "all testing" (not just new?)</td> </tr> <tr> <td>drumm</td> <td>Want to communicate that no DrupalCI tests will be started after then. Previously-run test results will remain for 6 months, if <a href="http://dispatcher.drupalci.org">dispatcher.drupalci.org</a> makes it that long</td> </tr> <tr> <td>G&aacute;bor Hojtsy (he/him)</td> <td>Yeah my definition of "testing" was the running of them, so we are on the same page. I realize the artifacts need to stay longer.</td> </tr> </table> <h2>6&#65039;&#8419; GitLab IssuesWe're mostly back up to full strength here from holidays and post-holiday vacations etc.There were a series of blockers to this next step, because it involves connectivity for migration between the current D7 site and GitLab and D10 for credit &amp; fork managementDatabase upgrades - Not fully complete, but complete enough to unblock the next step - the secondary db is upgraded enough to allow the next step to proceed. SSO review/deployment/migration - this needs to be scheduledFinal review of the Meta Data to Labels decisions - which should be global? Which should be up to individual maintainers to decide for their projects? -<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/infrastructure/-/work_items/3254602" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/infrastructure/-/work_items/3254602</a></span>#comment-15409139This could use your input!(edited)</h2> <table> <tr> <td>drumm</td> <td>Not mapping exactly, every bit of metadata in issues will be migrated. Should the labels remain standard for all projects and new projects? Questions like &ldquo;should every project have category::bug/feature/plan/task&rdquo; like we have now, or leave it to every maintainer to decide what is right for their project?&nbsp;(edited)</td> </tr> <tr> <td>hestenet (he/him)</td> <td>(Clarified above)</td> </tr> <tr> <td>Juraj Nemec</td> <td>There was also another discussion about keeping the issues IDs. Currently it is mixed in the implementation issue here:<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/3295357" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/3295357</a></span> .. Should we create a separate issue for this instead? I think this is also pretty important to decide</td> </tr> <tr> <td>drumm</td> <td>That can stay in implementation issues, there isn&rsquo;t anything to decide. Since it looks like GitLab lets us preserve issue IDs, we&rsquo;re certainly going to do that. We only need to make sure issue summaries are updated so we won&rsquo;t forget</td> </tr> <p>INCOMPLETE</p> <h2>7&#65039;&#8419; Giving sub-system and other maintainers more permissions so they can close MRs[#3392124]&nbsp;(edited)&nbsp;</h2> <table> <tr> <td>hestenet (he/him)</td> <td>Raised by @smustgrave</td> </tr> <p>INCOMPLETE</p> <p>Participants:</p> <p>hestenet, markdorison, dww, smustgrave, acbramley, Wim Leers, G&aacute;bor Hojtsy, pingwin4eg, fjgarlin, drumm, cmlara, poker10, catch</p> <p>Meeting link: <a href="https://drupal.slack.com/archives/CGKLP028K/p1706117137448149">https://drupal.slack.com/archives/CGKLP028K/p1706117137448149</a></p> </table></table></table>