This meeting:
➤ Is for core developers, initiative contributors, the Drupal Association and anyone interested in the initiative.
➤ Usually happens every other Tuesday at 1700 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!
➤ Has a public agenda anyone can add to
➤ *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.
:zero: Who is here today? Comment in the thread below to introduce yourself and tell us why you are joining us.
: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.
0️⃣ Who is here today? Comment in the thread below to introduce yourself and tell us why you are joining us.
hestenet (he/him) | Tim from the DA. |
TravisCarden | Travis Carden from Acquia. |
tedbow | Ted from Acquia |
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️⃣ At some point (hopefully this week?) I plan to catch up the meeting credits for this initiative from Q1 of this year.
3️⃣ AutoUpdates infrastructureCore package mirror for signing. Full redeploy of staging with core package signing + root keys(edited)
hestenet (he/him) | @nnewton has been getting help from @Max Whitehead on the provisioning of the core packaging mirror infra for @drumm. |
hestenet (he/him) | One of the things I'm currently looking at is the comparison between the HSM runbook:https://rugged.works/how-to/hsm/init_tuf_repo/And the process we call generating 'intermediate keys' in the old signify runbook:https://git.drupalcode.org/project/infrastructure/-/tree/main/signing#dr... |
5️⃣ 1️⃣ Composer Stager Symfony 7 https://drupal.slack.com/archives/C7QJNEY3E/p1712010554181099
5️⃣ 2️⃣ Package Managerhttps://drupal.slack.com/archives/C7QJNEY3E/p1712010629789249
5️⃣ 3️⃣ Any other aspects of the client side code?
hestenet (he/him) | I think @effulgentsia you have summarized some in-flight issues here:#3346707: Add Alpha level Experimental Package Manager module#comment-15525901 |
effulgentsia | Yes, from my perspective, the two key next steps are:Get Composer Stager committed (or at least RTBC'd if we want to postpone the actual commit until Package Manager is also ready) to core. See[#3346707]) once @tedbow updates it. |
tedbow | @effulgentsia do you think it is useful to update even if a bunch of tests might fail? thinking of this https://github.com/php-tuf/composer-stager/pull/351 |
6️⃣ Are there any other blocking issues (server, client or otherwise) that we should be tracking?The roadmap issue for review is:#3319030: Drupal Core Roadmap for Automatic Updates (edited)
7️⃣ I created an issue to make Automatic Update Extensions stabl[#3436741]This allows updating modules and themes.It is only in the contrib version but I think entice more people totry contrib and therefore the code that is in the Core merge requestsThere are few child issues to resolve but nothing major
hestenet (he/him) | Nice! That's really cool |
@TravisCarden I think we will need new beta of Composer Stager with the Symfony 7 changes to be able to make the core merge requests work
TravisCarden | When would you like that? And would you like it to contain that change and nothing else? |
tedbow | @TravisCarden I guess as soon possilbe.I guess would like just that change or at least not other BC breaking changes.Just quickly looking at the commit log this jumps out at me https://github.com/php-tuf/composer-stager/commit/6f1051ccffa4f312f71eb0... |
Comments
Comment #5
hestenet