>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3310981. --> Reported by: [hestenet](https://www.drupal.org/user/54034) >>> <p>This meeting:<br> &#10148; Is for core developers, initiative contributors, the Drupal Association and anyone interested in the initiative.<br> &#10148; Usually happens every other Wednesday at 11:00 PT / Thursday 06:00 UTC<br> &#10148; Is done over chat.<br> &#10148; Happens in threads, which you can follow to be notified of new replies even if you don&rsquo;t comment in the thread. You may also join the meeting later and participate asynchronously!<br> &#10148; 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> &#10148; Has a public agenda anyone can add to in the issue<br> &#10148; *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&#65039;&#8419; Who is here today? Comment in the thread below to introduce yourself!</h2> <table> <tr> <td>Nick_vh</td> <td>Nick - Following from GitLab's side &#128578;</td> </tr> <tr> <td>wimleers (he/him)</td> <td>Catching up after the fact :nerd_face:</td> </tr> </table> <h2>1&#65039;&#8419; 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&#65039;&#8419; our main focus right now is the performance issues that have been going on for our instance.A few things are under way:Increasing resources on the current vm hostAltering some configurationDoing some db index repairsLooking for runner instances causing extra loadMost seriously, since config isn't enough to dig us out and this vm host is now maxed out, looking at moving the instance to an oversized AWS machine. </h2> <table> </table> <h2>3&#65039;&#8419; GitLab CI/CD limits, @irinaz is actively working with a GitLab contributor to try and get that feature over the finish line so we can migrate more projects.</h2> <table> <tr> <td>Nick_vh</td> <td>How is that progressing? Anything I can do to speed it up? I might be able to help from end of October with resources. No promises yet</td> </tr> <tr> <td>hestenet (he/him)</td> <td>I think the biggest difficulty (and this is not unexpected or unsurprising) is just understanding enough of the codebase to know how to plug in - it looks like even Anatoli who were working with now has a bit of trouble with that.So just responsiveness to questions is really the most important thing</td> </tr> <tr> <td>irinaz</td> <td>@Nick_vh, thanks!&nbsp; Here is most recent question - it is very Gitlab-specific and also very technical <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/351147#note_1087645090">https://gitlab.com/gitlab-org/gitlab/-/issues/351147#note_1087645090</a> .&nbsp; Any pointers are very much appreciated!</td> </tr> </table> <h2>4&#65039;&#8419; pre-work for Change record changed will be deployed soon, holding on to final changes to the in review tab for now.</h2> <table> <tr> <td>wimleers (he/him)</td> <td>What does this mean?</td> </tr> <tr> <td>wimleers (he/him)</td> <td>moving d.o's "change records" functionality to GitLab? :thinking_face:</td> </tr> <tr> <td>fjgarlin</td> <td>moving d.o&rsquo;s &ldquo;change records&rdquo; functionality to GitLabthere is no immediate plan for this.what we are changing now is how CR reference issues. so far it&rsquo;s an entity reference to Drupal&rsquo;s internal issues, and we are changing this to links (and removing the entity references) so we can put gitlab issue links when issues are moved to gitlab.</td> </tr> <tr> <td>fjgarlin</td> <td>but for now, change records stay in Drupal as we know them</td> </tr> <tr> <td>hestenet (he/him)</td> <td>For much more detail from a previous meeting: <a href="https://drupal.slack.com/archives/CGKLP028K/p1660153794994589?thread_ts=1660153756.113269&amp;cid=CGKLP028K">https://drupal.slack.com/archives/CGKLP028K/p1660153794994589?thread_ts=1660153756.113269&amp;cid=CGKLP028K</a></td> </tr> </table> <h2>5&#65039;&#8419; Issue migration tools are in reasonably good shape, but precursors like some background dependencies, the ci work, and credit type will all need to be done before the first project can hit go. Getting closer tho!</h2> <table> <tr> <td>mlhess</td> <td>We need to get the security issue workflow resolved as well @hestenet (he/him)</td> </tr> <tr> <td>mlhess</td> <td>or not move projects that have been opted in to coverage (which might be a good idea either way &#128578; )</td> </tr> <tr> <td>wimleers (he/him)</td> <td>Can we see screenshots of intermediate state?</td> </tr> <tr> <td>wimleers (he/him)</td> <td>Where can I read what information will be lost/omitted?</td> </tr> <tr> <td>hestenet (he/him)</td> <td>I'll dig up the issue and the migration demo video from a previous meeting as well.&nbsp;(edited)</td> </tr> <tr> <td>hestenet (he/him)</td> <td>And yeah @mlhess - we should regroup. We're not deploying this imminently but all the tooling to do it is getting ready, just cause we were able to prep that in parallel to other ongoing blocker work (performance issues, ci/cd issues, contribution record type, backend version control work, and sec-team workflow are the big ones)</td> </tr> <tr> <td>hestenet (he/him)</td> <td>This meeting:&#10148; Is for core developers, initiative contributors, the Drupal Association and anyone interested in the initiative.&#10148; Usually happens every other Wednesday at 11:00 PT / Thursday 06:00 UTC&#10148; Is done over chat.&#10148; Happens in threads, which you can follow to be notified of new replies even if you don&rsquo;t comment in the thread. You may also join the meeting later and participate asynchronously!&#10148; 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.&#10148; Has a public agenda anyone can add to in the issue&#10148; *Transcript will be exported and posted* to the agenda issue. For anonymous comments, start with a &#128100; emoji. To take a comment or thread off the record, start with a &#128683; emoji.ping: @mixologic @FeyP @jurgenhaas (go to the issue of the next meeting to add or remove yourself from the list)</td> </tr> </table> <h2>6&#65039;&#8419; DrupalCon!</h2> <table> <tr> <td>hestenet (he/him)</td> <td>Myself, @drumm, and @fjgarlin will be there, with updates for the community at large.</td> </tr> <tr> <td>Nick_vh</td> <td>I'll be there as well! Only until Wednesday morning - if you'd like to talk - I'm there Monday &amp; Tuesday!</td> </tr> <tr> <td>G&aacute;bor Hojtsy (he/him)</td> <td>Monday is a buildup day though, no conference yet :smile:</td> </tr> <tr> <td>Nick_vh</td> <td>I know, but board meeting is Sat/Sun! Can't go home for just a day right? :sweat_smile:</td> </tr> </table> <p>Participants:</p> <p>Nick_vh, Wim Leers, hestenet, irinaz, fjgarlin, mlhess, G&aacute;bor Hojtsy</p>