Contrib.social

GitLab Acceleration Initiative meeting on 26 July, 2023

Open on Drupal.org →
Created on 12 July 2023, 12 months ago
Updated 3 January 2024, 6 months ago

This meeting:
➤ Is for core developers, initiative contributors, the Drupal Association and anyone interested in the initiative.
➤ Usually happens every other Wednesday at 11:00 PT / Thursday 06:00 UTC
➤ Is done over chat.
➤ 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!
➤ 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.
➤ Has a public agenda anyone can add to in the issue
➤ *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.

ping: @mixologic @FeyP @jurgenhaas (go to the issue of the next meeting to add or remove yourself from the list)

Transcript

0️⃣ Who is here today? Comment in the thread below to introduce yourself!

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.

2️⃣ Question:Should changes to issue meta data happen in the existing queue, or be saved for after GitLab issues? For example: 🌱 [Plan] Update core components Fixed

3️⃣ Upcoming improvements

3️⃣ 1️⃣  Enabling CI in all issue forks: 🐛 GitLabCI does not allow MRs from forks opened by non-members to run in the parent project Fixed

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.

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) 

Participants:

hestenet, markdorison, quietone, Björn Brala, moshe weitzman, tyler36, larowlan, drumm

🌱 Plan
Status

Fixed

Component

Meeting

Created by

🇺🇸United States hestenet Portland, OR 🇺🇸

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024