>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3324660. --> Reported by: [hestenet](https://www.drupal.org/user/54034) >>> <h2>Transcript</h2> <h2>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)0&#65039;&#8419; 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. :wave::skin-tone-3:</td> </tr> <tr> <td>markdorison</td> <td>Mark from Chromatic here. :blob_wave:</td> </tr> <tr> <td>irinaz</td> <td>Hi!</td> </tr> <tr> <td>longwave</td> <td>Dave, core contributor</td> </tr> <tr> <td>kimb0</td> <td>Kim, longtime listener</td> </tr> <tr> <td>irinaz</td> <td>@kimb0, great to see you here.&nbsp; You are using Gitlab CI/CD - it would be great to have your feedback on how well it works for you and if you new default templates are useful.</td> </tr> <tr> <td>hestenet (he/him)</td> <td>:clock11: Hi everyone, it's time for our regular GitLab Acceleration initiative meeting. I was hosting a webinar that ran long so give me just a second to get organized..</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; GitLab CI:Next steps:Figuring out concurrencyFiguring out Nightwatch testingGitLab feature to allow us to set per-project CI/CD minute limits for cost controls has an active MR and is getting really close to commit: <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/351147Has">https://gitlab.com/gitlab-org/gitlab/-/issues/351147Has</a> anyone done more work with the templates we made available to our opted-in users?&nbsp;(edited)&nbsp;</h2> <table> <tr> <td>Nick_vh</td> <td>Don't want to get your hopes up too high - there is indeed a lot of collaboration happening but I'm not sure how close we are to the finish line &#128578;</td> </tr> <tr> <td>hestenet (he/him)</td> <td>Ah well, 'really close' in open source speak then - haha</td> </tr> <tr> <td>Nick_vh</td> <td><a href="https://www.youtube.com/watch?v=NbEHPcrP3_0&amp;ab_channel=GitLabUnfiltered ">https://www.youtube.com/watch?v=NbEHPcrP3_0&amp;ab_channel=GitLabUnfiltered </a> here is the recording of the office hours with the team re: ci/cd limits</td> </tr> <tr> <td>Nick_vh</td> <td>(cc @irinaz / @hestenet (he/him) / @drumm )</td> </tr> <tr> <td>hestenet (he/him)</td> <td>Thanks! James Heimbruck sent us that link as well. That's helpful!</td> </tr> <tr> <td>irinaz</td> <td>@Nick_vh, is there anything that folks that do not work at Gitlab can help with at this stage?</td> </tr> <tr> <td>Nick_vh</td> <td>Please ask that in the issue, or maybe it even is described there :)</td> </tr> </table> <h2>3&#65039;&#8419; Contribution Record (credit)This is being rearchitected into a content type separate from issues, so that a webhook can be used from a bot-posted message on GitLab issues to populate the credit record in Drupal.The plan has been documented here, and @fjgarlin has made significant progress on implementation, although we're not set up to share a dev environment for it just yet:&nbsp; <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/infrastructure/-/work_items/3322116" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/infrastructure/-/work_items/3322116</a></span></h2> <table> <tr> <td>hestenet (he/him)</td> <td>One question I was asked is if the contribution record has a simple link to an external record, could that be used to create credit for non-GitLab issues, like for projects that live on GitHub.There are further complications with this idea, because we're also making some api calls to gather data from those issues that assume we're looking at GitLab.But in principle, as a further enhancement after we're done with the migration to GitLab, we could look at making this a generic solution somehow.(Or having 'credit formatters' for different sources, git.drupalcode.org vs gitlab.com vs github &lt;-- though those would likely have to be community contribuitions rather than DA priorities).</td> </tr> <tr> <td>hestenet (he/him)</td> <td>So tldr: it's not a priority and we need to focus our resources on the main migration right now. But perhaps it could be revisited after.</td> </tr> <tr> <td>longwave</td> <td>I came across this feature in github recently and realised it could be extended for credit and other attributions <a href="https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors">https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors</a></td> </tr> <tr> <td>longwave</td> <td>GitLab also supports it and it would improve the authorship of our git history and also is extensible enough that I think credits could be recorded here too</td> </tr> <tr> <td>moshe</td> <td>last I checked gitlab did not support that. docs?</td> </tr> <tr> <td>longwave</td> <td>@moshe <a href="https://gitlab.com/gitlab-org/gitlab-foss/-/issues/31640">https://gitlab.com/gitlab-org/gitlab-foss/-/issues/31640</a> implies it was implemented</td> </tr> <tr> <td>longwave</td> <td>having said that I think git commit trailers are only really used by Linux kernel and probably not many other projects - but then Drupal has led the way on other collaborative work so we could do something here too</td> </tr> <tr> <td>moshe</td> <td>yeah thats part of the github feature. the other part is using that feature when squashing commits</td> </tr> <tr> <td>moshe</td> <td>its not super clear if that was done in <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/20421">https://gitlab.com/gitlab-org/gitlab/-/issues/20421</a></td> </tr> <tr> <td>moshe</td> <td>looks promising for sure</td> </tr> <tr> <td>longwave</td> <td>tooling support is also quite poor, but we already give users copy-and-paste commit commands so we could do that for this too I think</td> </tr> <tr> <td>hestenet (he/him)</td> <td>They've also recently been working on: <a href="https://gitlab.com/gitlab-org/gitlab/-/merge_requests/101458">https://gitlab.com/gitlab-org/gitlab/-/merge_requests/101458</a></td> </tr> <tr> <td>moshe</td> <td>Er, folks can create multiple author commits via the UI, so it isnt that poor</td> </tr> <tr> <td>nicxvan</td> <td>I'm curious if this refactor is accounting for credit for non code contributions</td> </tr> <tr> <td>nicxvan</td> <td>We use issues for crediting speakers at camps and for guests on the podcast so if this is refactoring to a new content type how will we credit users in those situations&nbsp;(edited)</td> </tr> <tr> <td>nicxvan</td> <td>I know this isn't strictly gitlab related, but wasn't sure where to post</td> </tr> <tr> <td>moshe</td> <td>All proposed solutions preserve the ability for non-code contributions to be credited. Its a must-have.</td> </tr> <tr> <td>hestenet (he/him)</td> <td>Yup. You could continue making issues if that fit the model of your project, but we're also doing more to directly measure contribution activities. Now that we have events data on drupal.org we can begin to measure that without having extra issues filed.</td> </tr> <tr> <td>nicxvan</td> <td>Nice, is that related to the events spoken at section?</td> </tr> <tr> <td>hestenet (he/him)</td> <td>Yup - that's the idea. Since we have that data, we can start incorporating it directly rather than have people 'do the paperwork again' by filing issues.</td> </tr> <tr> <td>nicxvan</td> <td>Awesome</td> </tr> <tr> <td>fjgarlin</td> <td>One question I was asked is if the contribution record has a simple link to an external record, could that be used to create credit for non-GitLab issues, like for projects that live on GitHub.we&rsquo;re designing a structure that allows different source links. right now there is a (WIP) source for gitlab and a (WIP) source for drupal.org.the problems with other external platforms that we don&rsquo;t control or manage are: validation of the source against a drupal project (to make sure that they are legit links) and api integration (to get meta info like title, project, status of the issue, people that participated&hellip;)so fully agree with what Tim said after. first priority will be the two above. then we will know more about what&rsquo;s needed and once that&rsquo;s in place we could explore/investigate the options for other sources.</td> </tr> <tr> <td>Nick_vh</td> <td>Thanks @hestenet (he/him) for mentioniing the reviewed_by. For recognition, this is very useful when combining this with platforms like bitergia assuming everything is a git commit. I'll keep you updated as we continue to expand what a contribution is or could be in GitLab&nbsp;(edited)</td> </tr> <tr> <td>Nick_vh</td> <td>If you turn this upside down, you could even preserve attribution of issues in git commits and not roll your own solution :smile: but I get the need for correcting it. Be mindful, an issue in GitLab only has 2 states, open or closed. So you don't really know if it was resolved. Getting something merged means it is resolved and that's the only place where attribution happens today, including authors etc..</td> </tr> <tr> <td>hestenet (he/him)</td> <td>We have all sorts of non-code issues, and we also allow credit to be updated/corrected after the fact, which can't be accommodated using pure commit messages, unfortunately</td> </tr> <tr> <td>hestenet (he/him)</td> <td>We talked about that when we first came up with the credit idea way back in 2015, and that was the concern.</td> </tr> <tr> <td>moshe</td> <td>I recall a proposal to use git notes which can be amended, fwiw</td> </tr> <tr> <td>moshe</td> <td>I&rsquo;m not suggesting we revisit that suggestion.</td> </tr> </table> <h2>4&#65039;&#8419; Workflow revisitAfter the performance scaling issues we discovered when trying to add many developers to the same group, in order to create the collaboration permissions, @drumm has been working on developing a new collaboration model.The won't fix issue for our first choice solution: <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/infrastructure/-/work_items/3250923" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/infrastructure/-/work_items/3250923</a></span>&nbsp;(edited)&nbsp;</h2> <table> </table> <h2>5&#65039;&#8419; IssuesThe migration code for issues is ready and waiting, to be updated with the relevant additions for toggling over CI or the Contribution Credit Record etc.These three pieces together, CI, Contribution Record, Workflow are all getting very close to the point where we pivot to actually figuring out the opt-in process for issue migration&nbsp;(edited)&nbsp;</h2> <table> </table> <p>Participants:</p> <p>hestenet, markdorison, irinaz, longwave, kim.pepper, Nick_vh, moshe, nicxvan, fjgarlin</p>