GitLab Acceleration Initiative meeting on 7 Feb, 2024
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3419864. -->
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>hestenet (he/him)</td>
<td>Tim from the DA, kicking things off.</td>
</tr>
<tr>
<td>tyler36</td>
<td>Hi from Japan.</td>
</tr>
<tr>
<td>andypost</td>
<td>:wave::skin-tone-3: Andy, lurking</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>andypost</td>
<td>Maybe discussion about[#3404082]As 8.3-apache-ubuntu added for sqlite version purpose and this list can grow</td>
</tr>
</table>
<h2>2️⃣ GitLab IssuesSome progress on the infrastructure blockers - but still a lot longer to goWe've made progress on the D10 env for the www. migration itself, which will include: Project browser end points (unrelated to this initiative) Issue fork managementCredit records Fran has recently reviewed and updated the work on this, checked over the migration stuff. We have had some server melt downs and other things going on in the background (very proud that it doesn't affect things you all end users can see 🙂 ) but still disruptive This means we haven't yet: Finished our needed db migrationGotten to the SSO migration</h2>
<table>
</table>
<h2>3️⃣ GitLab CIAs mentioned in the last call - this really has mostly moved from the big lift - to ongoing maintenance, feature requests, and improvements. We're very grateful for the help of everyone continuing to work on refinements, it really improves our capacity, and lets us work on the GitLab issues stuff more Feel free to highlight any active GitLab CI related work in this thread</h2>
<table>
</table>
<h2>4️⃣ DrupalCI Deprecation and patch testing schedule fully announced:<a href="https://www.drupal.org/about/core/blog/drupalci-and-all-patch-testing-will-be-turned-off-on-july-1-2024">https://www.drupal.org/about/core/blog/drupalci-and-all-patch-testing-will-be-turned-off-on-july-1-2024</a></h2>
<table>
</table>
<h2>5️⃣ We have had at least one person raise the issue of education on merge requests vs. patches (from pretty much first principles)There's so much out there, that I don't think these are educational resourcse we should be trying to create from scratchBut maybe you have a really good 'pull request 101' that we can link somewhere in our existing docs. </h2>
<table>
<tr>
<td>tyler36</td>
<td>The move from patches to MRs is a different workflow change and highlighting the benefits will improve confidence and competence.While there are a lot of resouces available, they are not always correct, current or applicable to Drupal's implementation.</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>That's a fair enough point. Do you have any suggestions on good generic resources to start with and use as the basis to provide more Drupal-y versions?</td>
</tr>
<tr>
<td>xurizaemon</td>
<td>Anecdata: I've observed reluctance/resistance from:Desire for a non-idempotent patch URLResistance to changeOne of those is upstream with Gitlab (gitlab#15593 and gitlab#217206).The other ... yep, highlighting benefits and making it easy to do the new thing, some education (eg not knowing about DrupalCI changes). (edited)</td>
</tr>
<tr>
<td>tyler36</td>
<td>Desire for a non-idempotent patch URLThis is the one I hear the most, especially from developer that used Drupal 6-7@hestenet (he/him) I don't on hand but will keep an eye out.:)</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>Yeah. That one is a big deal. There are 4 different features requests open with GitLab for basically the same thing, heh.</td>
</tr>
</table>
<h2>6️⃣ Conversation about semver for the Environments themselves, and ability to adopt a few new types of environments - feedback in issue appreciate[#3404082]</h2>
<table>
</table>
<p>Participants:</p>
<p>hestenet, tyler36, andypost, xurizaemon</p>
<p>Meeting link: <a href="https://drupal.slack.com/archives/CGKLP028K/p1707332538433129">https://drupal.slack.com/archives/CGKLP028K/p1707332538433129</a></p>
issue