GitLab Acceleration Initiative meeting on 26 July, 2023
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3374206. -->
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>Transcript</h2>
<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, managing these threads</td>
</tr>
<tr>
<td>markdorison</td>
<td>Mark from Chromatic here :blob_wave:</td>
</tr>
<tr>
<td>quietone</td>
<td>Catching up</td>
</tr>
<tr>
<td>tyler36</td>
<td>Hi :wave:</td>
</tr>
<tr>
<td>Björn Brala (bbrala)</td>
<td>Björn :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️⃣ Question:Should changes to issue meta data happen in the existing queue, or be saved for after GitLab issues? For example: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2660144" title="Status: Closed (fixed)">#2660144: [Plan] Update core components</a></span> </h2>
<table>
<tr>
<td>hestenet (he/him)</td>
<td>Question per @quietone</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>The issue migration process we have prototyped out recreates the components it finds as labels as part of the migration - so it would make sense to me to go ahead and move forward with those updates for core.</td>
</tr>
<tr>
<td>markdorison</td>
<td>I don’t think it should be a blocker for issue migration, but it would be great if it gets done beforehand for the reason you mentioned</td>
</tr>
<tr>
<td>quietone</td>
<td>Thanks for the information! That helps me to order priorities for the next issue to focus on at <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/3351644" title="Status: Active">#3351644: [meta] Improve issue management</a></span></td>
</tr>
</table>
<h2>3️⃣ Upcoming improvements</h2>
<table>
</table>
<h2>3️⃣ 1️⃣ Enabling CI in all issue forks:<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/3361106" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/3361106</a></span></h2>
<table>
<tr>
<td>hestenet (he/him)</td>
<td>Being managed by @drumm</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>The process of doing this bulk update is reasonably well understood from previous bulk project configuration updates we have done.</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>We're fully agreed on doing this and the precursor work: (ensuring that the default ci template doesn't run a bunch of extra testing) has been committed.</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>Neil is currently doing another (non-Gitlab) bulk update process to put security advisory information in the composer endpoints for the auto updates initiative - this should be the next item on the list.</td>
</tr>
<tr>
<td>Björn Brala (bbrala)</td>
<td>Is it possible to disable this for a project?</td>
</tr>
<tr>
<td>Björn Brala (bbrala)</td>
<td>For project_analysis this could leak a secret I don't want to leak when the bot starts running on gitlab.</td>
</tr>
<tr>
<td>moshe</td>
<td>No secrets will leak by default. You'd have to flip a switch to get that behavior.</td>
</tr>
<tr>
<td>Björn Brala (bbrala)</td>
<td>What if you make a Mr and manipulate the var then print it bypassing the replacements. Although it's an assumption that would work</td>
</tr>
<tr>
<td>moshe</td>
<td>Secrets are simply not shared with CI pipelines that run in forks. No manipulation will reveal them. Therefore its quite likely whatever you are doing with a secret wont work on fork pipelines. This secret-hiding is a gitlab feature (and github, circleci, etc).</td>
</tr>
<tr>
<td>Björn Brala (bbrala)</td>
<td>That is good to know thank yoy</td>
</tr>
<tr>
<td>moshe</td>
<td>The lack of this feature could be considered a (small) security concern. We are expecting maintainers to review and approve the PR changes before clicking the 'Run Pipeline' button. This gets tedious enough that some maintainers will run the pipeline and then review code. An example affected PR is <a href="https://git.drupalcode.org/project/akamai/-/merge_requests/14#note_202028">https://git.drupalcode.org/project/akamai/-/merge_requests/14#note_202028</a></td>
</tr>
<tr>
<td>Björn Brala (bbrala)</td>
<td>I think this got popular when bitcoin miners started to appear on ci</td>
</tr>
<tr>
<td>Björn Brala (bbrala)</td>
<td>Which is kinda troublesome</td>
</tr>
<tr>
<td>moshe</td>
<td>Hmm. Slightly different. Thats a 'first time run' roadblock. This is a 'no permission to run pipeline in the fork' issue, which happens every PR.</td>
</tr>
<tr>
<td>Björn Brala (bbrala)</td>
<td>Sorry wrong thread lol :sweat_smile:</td>
</tr>
</table>
<h2>3️⃣ 2️⃣ Getting Personal Access Tokens enabled[#3199831]We have a good handle on the different items this will be useful for, and are agreed on moving forward with it.There are a few next steps.</h2>
<table>
<tr>
<td>hestenet (he/him)</td>
<td>Non-blocker: I should to summarize our bot policy on a d.o page somewhere. Most uses of PATs are fine, but we need to watch out for people running away with things (seen a bunch of ChatGPT generated contribution spam in the last couple weeks) Our GitLab staging environment needs rebuilding so we can properly validate unblocking all the relevant ha proxy paths and things. There are some technical debt pieces building up with GitLab itselfThe hosting/replication environment needs some updatesThe pgsql version requirements have increased, etc. (edited)</td>
</tr>
<tr>
<td>tyler36</td>
<td>Super excited about this!</td>
</tr>
</table>
<h2>4️⃣ Roadmap to Gitlab Issues[#3265096] 0. (unrelated, but priority blocking) We finish critical work for the AutoUpdates/Project Browser initiative (package signing) to unblock their progress.SSO - We review and deploy our new SSO solution, allowing us to cross-authenticate between D7/D10Solution is built, some early migration tests have been done - needs reviewWe deploy the new credit record/fork management in D10 - setting up CDN/paths for accessNew content types for each are builtWe migrate existing credit to the new content typeMigration code is writtenWe add an opt-in issue migration tool to projects, allowing the maintainer to migrate issuesPossibly we just do the first project or two manually without a ui buttonThe actual migration button needs to be builtBut the migration code itself is writtenWe then need to support this with documentation, in concert with the first users. (edited) </h2>
<table>
<tr>
<td>hestenet (he/him)</td>
<td>How far can we get on these items before DrupalCon Lille in October?That's something:myself@fjgarlin @drumm @nnewton (currently on vacation)Need to regroup on.</td>
</tr>
<tr>
<td>larowlan</td>
<td>Happy to be guinea pig for migration</td>
</tr>
<tr>
<td>markdorison</td>
<td>Is there somewhere you can link to that has a summary of the status on 0? How close to completion is that work? How likely is it that it will become blocked and therefore block movement on this?</td>
</tr>
<tr>
<td>drumm</td>
<td>The overall issue is our team size. If that’s blocked by an external factor, we switch to a priority we can make progress on. If its blocked by something that becomes higher priority, we’re concentrating on that</td>
</tr>
<tr>
<td>markdorison</td>
<td>I completely understand</td>
</tr>
<tr>
<td>hestenet (he/him)</td>
<td>For specific details on item 0 - check out the last initiativ emeeting in #autoupdates</td>
</tr>
</table>
<p>Participants:</p>
<p>hestenet, markdorison, quietone, Björn Brala, moshe weitzman, tyler36, larowlan, drumm</p>
issue