GitLab Acceleration Initiative meeting on 29 May, 2024
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3447415. -->
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 coordinating</td>
</tr>
<tr>
<td>markdorison</td>
<td>Hello hello :blob_wave:</td>
</tr>
<tr>
<td>Björn Brala (bbrala)</td>
<td>Bjorn, hi!</td>
</tr>
<tr>
<td>Juraj Nemec</td>
<td>Hi :wave:</td>
</tr>
<tr>
<td>tyler36</td>
<td>Hi all :wave:</td>
</tr>
<tr>
<td>el7cosmos</td>
<td>Hello :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>
</table>
<h2>2️⃣ GitLab Issues:Blocking work: We have deadlines for Rugged for AutoUpdates and Project Browser endpoints that have made significant progress in the last couple weeks. SSO deployment has been pretty thoroughly tested, so we'll set a window for this after the Rugged/PB work is deployedThen we'll get the content type for fork management and the new contrib record type together, and test the migration processThen we'll be able to accept the first opt-ins to GitLab Issues. </h2>
<table>
<tr>
<td>Björn Brala (bbrala)</td>
<td>Will opt in to issues mean only gitlab issues for that project?</td>
</tr>
<tr>
<td>Juraj Nemec</td>
<td>Given that there are still open questions about the overall migration process (how to convert each drupal issue settings, how exactly would redirects work, ..), can we first create a demo project with the migration done, to be able to test the outcome? I suppose this is different from GitlabCi, which can be turned on/off at any time (so there the early opt-in process made sense), but once the migration is done, I think that is permanent and would be difficult to make additional changes if needed[#3254602]</td>
</tr>
<tr>
<td>larowlan</td>
<td>I am happy to volunteer a project to be guinea pig</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>Yes, once opting on you would be wholly on GitLab Issues from there. And yeah, we'll find a good demo project to start with to get more concrete answers to some of those open questions</td>
</tr>
<tr>
<td>Björn Brala (bbrala)</td>
<td>I'd really like a project to play with with project update bot. Need to be ready for the switch, or even the while that we have both situations. Depending on the timing it's the time that upgrade issues are quite important.</td>
</tr>
</table>
<h2>3️⃣ GitLab CI</h2>
<table>
</table>
<h2>3️⃣ 1️⃣ GitLab CI support for D11 release window - what might still be outstanding?</h2>
<table>
</table>
<p>Participants:</p>
<p>hestenet, markdorison, bbrala, poker10, tyler36, el7cosmos, larowlan</p>
<p>Meeting link: <a href="https://drupal.slack.com/archives/CGKLP028K/p1717005818315179">https://drupal.slack.com/archives/CGKLP028K/p1717005818315179</a></p>
issue