GitLab Acceleration Initiative meeting on 21 Sept, 2022
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3310982. -->
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 06: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>
<h2>0️⃣ Who is here today? Comment in the thread below to introduce yourself!</h2>
<table>
<tr>
<td>chrisfromredfin</td>
<td>Hi all! Lurking from Prague while I test out recipes and other things. I am reinvigorated with how much GitLab can help, and want to just help inch it forward where I can.</td>
</tr>
<tr>
<td>irinaz</td>
<td>Hi, Irina working from California 🙂</td>
</tr>
<tr>
<td>chrisfromredfin</td>
<td>We love GitLab CI... esp. according to this commit message.</td>
</tr>
<tr>
<td>quietone</td>
<td>Catching up</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️⃣ Some bittersweet news. A more formal goodbye post will be coming soon, but since it's so relevant to this initiative, we wanted to let you all know that @mixologic is moving on from the Drupal Association, and is now going to be working for the Linux Foundation.He'll still be a Drupal community member of course, and will likely contract back with the DA from time to time.</h2>
<table>
</table>
<h2>3️⃣ The biggest issue that overtook all of our attention was the performance issue that plagued us prior to the conference. A combination of changes in performance profile after recent updates, and significant load increase due to the lead up to D10 beta meant our GitLab instance was really struggling.We have significantly upsized this instance, and as far as we can tell it's working much, much better.</h2>
<table>
<tr>
<td>hestenet (he/him)</td>
<td>Old GitLab instance:Intel XEON 2450 2.5Ghz16 vCPUs32 GB DDR3 ECCSpinning HDDsLoad peak: 40+New GitLab instance: AWS EC2 8xLarge32 CPUs128 GB MemorySSD EBS volumesLoad peak: 2.5</td>
</tr>
<tr>
<td>Björn Brala (bbrala)</td>
<td>Great work guys</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>@wimleers (he/him) I know you ran headfirst into most of the performance problems before these changes - it would be good to get your feedback on how it has been during DrupalCon week.</td>
</tr>
</table>
<h2>4️⃣ Recapping the overall mission:These are the major components of the project that was announced as the 'GitLab Acceleration' initiative:</h2>
<table>
</table>
<h2>4️⃣ 1️⃣ Account creation improvements - these are not GitLab per se, but were lumped together as part of the contributor struggle.We have a KeyCloak based new authentication system, where we've performed test user account migrations. We have a few final details to button up, like some final testing, and reimplementation of spam protections, but we'll be able to schedule deployment soon.</h2>
<table>
</table>
<h2>4️⃣ 2️⃣ Simplyfing Drupal.org - Many of the git integration points on Drupal.org have been removed/replaced with GitLab links where appropriate. There may be a few more of these to go, but most fo the remainign ones are related to issues, which are a separate topic.</h2>
<table>
</table>
<h2>4️⃣ 3️⃣ IssuesIssue Collaboration - we believe we have the workflow correctly outlined, but need to do some validation testing. Issue Migration - The code for this is largely written, including migrationg issue references and autoexpansion [#123], there is some follow up work related to Change Records based on core feedback.Ultimately issue migration will still be blocked on GitLabCI Issue Credit - we have a conceptual architecture, and can move on to that implementation when we're done getting the issue migration code ready. </h2>
<table>
</table>
<h2>4️⃣ 4️⃣ GitLabCIThis is the more obvious area where we've been struggling. There is one GitLab side blocker, and then a lot of templating work we still need to do. We just need to refocus here.This is the GitLab blocker, work in progress: <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/351147#note_1079851987This">https://gitlab.com/gitlab-org/gitlab/-/issues/351147#note_1079851987This</a> is the outline of key requirements that need to be supported in the templates we provide for projects to opt into.</h2>
<table>
<tr>
<td>fjgarlin</td>
<td>my suggestion for this is to create 4 templates, one of each major case, rather than trying to create just the one to fit all the cases.we’ll need to play and experiment with this as maybe some bits can be reused, but in any case, all of them seem perfectly doable in gitlab ci.</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>+1 - let's see if we can find time to sprint on this after the con</td>
</tr>
<tr>
<td>drumm</td>
<td>That’s somewhat how DrupalCI operated. <a href="https://git.drupalcode.org/project/project_issue_file_test/-/tree/7.x-3.x/job_templates">https://git.drupalcode.org/project/project_issue_file_test/-/tree/7.x-3.x/job_templates</a> could be the same 4. legacy / not-legacy certainly matches up. Not entirely sure on development / regression. Those define the order steps are done in, particularly getting the dependency sandwiches together.</td>
</tr>
</table>
<p>Participants:</p>
<p>hestenet, Björn Brala (bbrala), fjgarlin, drumm</p>
issue