GitLab Acceleration Initiative meeting on 6 Mar, 2024
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3426154. -->
Reported by: [hestenet](https://www.drupal.org/user/54034)
>>>
<p>This meeting:<br>
➤ Is for core developers, initiative contributors, the Drupal Association and anyone interested in the initiative.<br>
➤ Usually happens every other Wednesday at 11:00 PT / Thursday 18:00 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>
➤ 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>
➤ Has a public agenda anyone can add to in the issue<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 @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️⃣ Who is here today? Comment in the thread below to introduce yourself!</h2>
<table>
<tr>
<td>larowlan</td>
<td>Hey</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>:wave::skin-tone-3:</td>
</tr>
<tr>
<td>markdorison</td>
<td>Hey hey! Mark here :blob_wave:</td>
</tr>
<tr>
<td>tyler36</td>
<td>Hi from Japan :wave:</td>
</tr>
<tr>
<td>James Shields</td>
<td>Oops, sorry I'm late. Must put these in my diary.</td>
</tr>
<tr>
<td>hlopez</td>
<td>Hi, Hector here :wave:</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>
<tr>
<td>smustgrave</td>
<td>Question (didn’t want to interrupt the thread). How are people grabbing optional modules? Example I have a search_api plugin that can work with search_api_solr but not a dependency in composer file. So I get a ton of failures2. There a recommended way to point a core dev branch like 10.3.x3. Is cspell automatically ran? Prepping a few modules for 10.3/11 and getting a ton of cspell errors I never got before</td>
</tr>
<tr>
<td>hlopez</td>
<td>I just started looking into this initiative, where can I look to see where I can help out?</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>Some open issues for the GitLabCI part of the initiative (which are definitely the easiest for community members to participate in) are here: <a href="https://www.drupal.org/project/issues/gitlab_templates?categories=All">https://www.drupal.org/project/issues/gitlab_templates?categories=All</a></td>
</tr>
<tr>
<td>hlopez</td>
<td>Oh awesome, thanks @hestenet (he/him) !</td>
</tr>
</table>
<h2>2️⃣ We have a very hard focus right now on our SSO migration, which is the primary blocker to the next step for migrating credit and issue/fork management into D10 and begin the gitlab issue opt-in process.We have a goal to determine our migration window by the end of the month, with newly added support from @marvil07 to help us validate the migration prep started already and help us get it over the finish line. (edited)</h2>
<table>
</table>
<h2>3️⃣ GitLab CI is almost now out of scope as part of the 'initiative' - and more of an ongoing part of regular Drupal infrastructure support.There are a lot of feature requests and enhancements of course, but the last feature parity issue is to add the test-only job from core to contrib ci config.</h2>
<table>
<tr>
<td>Jonathan1055</td>
<td>I have had finished the work on the test-only changes job (for both D10 and D7) and it in in final review. It is likely to be merged in soon.EDIT: Just remembered that the last review asked for some changes (re-factoring to take script out of the .yml and into a separate file). So it will be a short wait (edited)</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>:thankful:</td>
</tr>
</table>
<h2>4️⃣ Fran has also conducted a cool test of GitLab Pages + Material + Mkdocs to provide the more detailed technical side of GitLabCI documentation in git-based documentation: <a href="https://project.pages.drupalcode.org/gitlab_templates/This">https://project.pages.drupalcode.org/gitlab_templates/This</a> is not something restricted to us - anyone can be experimenting with these things with all the tools already enabled.</h2>
<table>
<tr>
<td>smustgrave</td>
<td>Thanks for sharing that link!</td>
</tr>
</table>
<h2>5️⃣ per @smustgrave - How are people grabbing optional modules? Example I have a search_api plugin that can work with search_api_solr but not a dependency in composer file. So I get a ton of failures</h2>
<table>
<tr>
<td>cmlara</td>
<td>require-dev in composer. Downloads it so you can test but doesn’t make it a requirement for sites to install the module in production. (edited)</td>
</tr>
<tr>
<td>smustgrave</td>
<td>Perfect! I didn’t know if a special case was needed for gitlab</td>
</tr>
<tr>
<td>fjgarlin</td>
<td><a href="https://project.pages.drupalcode.org/gitlab_templates/info/common/#including-a-non-required-module-for-testing">https://project.pages.drupalcode.org/gitlab_templates/info/common/#including-a-non-required-module-for-testing</a></td>
</tr>
</table>
<h2>6️⃣ per @smustgrave What is the recommended way to point a core dev branch like 10.3.x</h2>
<table>
<tr>
<td>cmlara</td>
<td>Depends a bit on what you are asking, there is the option next minor job if your looking to test multiple versions, If your just asking about what values _TARGET_CORE can be some samples are in the variables file.<a href="https://git.drupalcode.org/project/gitlab_templates/-/blob/b0976eea34559218896fe46e234b445f77210b4f/includes/include.drupalci.variables.yml#L227-L263">https://git.drupalcode.org/project/gitlab_templates/-/blob/b0976eea34559218896fe46e234b445f77210b4f/includes/include.drupalci.variables.yml#L227-L263</a></td>
</tr>
<tr>
<td>smustgrave</td>
<td>So like_TARGET_CORE:<br>
value: CORE_NEXT_MINOR</td>
</tr>
<p>INCOMPLETE</p>
<h2>7️⃣ per @smustgrave Is cspell automatically ran? Prepping a few modules for 10.3/11 and getting a ton of cspell errors I never got beforeAnswer: Yes as of:<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/gitlab_templates/-/issues/3405955" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/gitlab_templates/-/issues/3405955</a></span></h2>
<table>
<tr>
<td>smustgrave</td>
<td>Should some default files be added to ignore? Like composer.json</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>I am not close to this one, but my instinct is yes.... maybe we need a follow up for some of these things.. or for some default dictionary terms..</td>
</tr>
<tr>
<td>fjgarlin</td>
<td>We’re providing artifacts that can be placed in the module to help with it</td>
</tr>
<p>INCOMPLETE</p>
<p>Participants:</p>
<p>larowlan, hestenet, markdorison, tyler36, James Shields, hlopez, smustgrave, Jonathan1055, cmlara, fjgarlin</p>
<p>Meeting link: <a href="https://drupal.slack.com/archives/CGKLP028K/p1709752041092739">https://drupal.slack.com/archives/CGKLP028K/p1709752041092739</a></p>
</table></table>
issue