Core migration issues

Next video meeting TBD

Hello all, it’s time for the biweekly migration subsystem meeting. The meeting will take place in slack in various threads. This meeting:
➤ Is for core migrate maintainers and developers and anybody else in the community with an interest in migrations
➤ Usually happens every second Thursday and alternates between 1400 and 2100 UTC.
➤ Is done on the #migration channel in Drupal Slack (see www.drupal.org/slack for information).
➤ 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. #3456078: [meeting] Migrate Meeting 2024-07-18 2100Z)See the parent issue for an idea of the typical agenda.
Transcript will be exported and posted to the agenda issue. For anonymous comments, start with a 👤 emoji. To take a comment or thread off the record, start with a 🚫 emoji.

0️⃣ Who is here today?

benjifisher Hello. Happy end of July!
dinarcon Hey :wave:
Nick Opris Hello! Is this like the AI Initiative meeting?
dinarcon It is the Migrate initiative meeting.
benjifisher @Nick Opris: Welcome! Have you read the meeting description in the main channel (right before the post that started this thread)?
thejimbirch Checking in.
longwave :wave:
Dan Davis Here

1️⃣ What should we talk about today? Suggest topics here and I will add threads. I will also check for comments on the issue for today's meeting.

benjifisher Migrations fail due to missing dependency when dependency has skipped rows by the source plugin
benjifisher Deprecate migrate_drupal source plugins
benjifisher Deprecate Migrate Drupal UI
thejimbirch Is anyone working on Migrate <> Modeler API?

2️⃣ Action items. To be added later.

3️⃣ Statistics

Migrate Initiative Meeting 354 total; 0 Fixed; 0 RTBC; 4 NR, including one Major
Migrate Initiative Meeting Google sheet for recording stats: https://docs.google.com/spreadsheets/d/1o0Rjlc1vnnLP5bM5P-SMMyGzqn7258hi...

4️⃣ Comment in this thread if you are looking for ways to contribute. Give us some idea of what you would like to do: documentation, code review, testing, project management, ...

5️⃣ Previous minutes.

Migrate Initiative Meeting https://www.drupal.org/project/drupal/issues/3533968 (edited)
benjifisher We need to add a transcript to that issue.
benjifisher Now NR

6️⃣ Announcements

dinarcon The D7 -> D10/11 migration series was packaged as an ebook which can be downloaded for free at https://www.tag1consulting.com/migrate-book

7️⃣ Migrations fail due to missing dependency when dependency has skipped rows by the source plugin

Migrate Initiative Meeting https://www.drupal.org/project/drupal/issues/2797505 (edited)
Migrate Initiative Meeting (Original Request) https://drupal.slack.com/archives/C226VLXBP/p1753970742319669?thread_ts=... (edited)
benjifisher This is the NR issue marked Major.
benjifisher @heddn: You commented on this issue. Have you looked at it lately?
heddn my initial thought is that the dependency should be marked as optional instead of required. but taking a look again
heddn re-reading, the issue is about something slightly different though
heddn there's still 2 open comments that havent' been responded to
benjifisher Can you post a comment? Say what you think about the general approach and point out the open questions?
longwave fwiw i have only just read what's in this thread but i have run into this recently, and my fix was to mark the migration as optional if i know that the parent migration will skip some rows
heddn exactly, that's what I commented

8️⃣ Deprecate migrate_drupal source plugins

Migrate Initiative Meeting https://www.drupal.org/project/drupal/issues/3507572 (edited)
Migrate Initiative Meeting (Original Request) https://drupal.slack.com/archives/C226VLXBP/p1753970915783299?thread_ts=... (edited)
benjifisher I have been meaning to look at this issue since @longwave mentioned a new approach to handling the deprecations.
benjifisher @mikelutz (he/him): You have already looked at this issue. Can you either suggest improvements or mark it RTBC?
longwave I think Mike was leaving the decision in #15 to someone of higher authority
longwave i guess we need to try adding the annotation and seeing what the impact is
benjifisher Mike is a a maintainer of the migration subsystem, and you are a core committer. Who would be a higher authority?
benjifisher For handling deprecations, I guess that would be a release manager.
benjifisher We could add the "Needs release manager review" issue tag, or we could mark the issue RTBC. Either one is likely to get the attention that the issue needs.
longwave i am a release manager too :smile:
longwave going to mark NW to try out the annotation
benjifisher Then what are we waiting for?
longwave (by the way, thank you for highlighting this issue again; this sort of indecision is why so many issues go stale)

9️⃣ Deprecate Migrate Drupal UI

Migrate Initiative Meeting https://www.drupal.org/project/drupal/issues/3463321 (edited)
Migrate Initiative Meeting (Original Request) https://drupal.slack.com/archives/C226VLXBP/p1753971350709239?thread_ts=... (edited)
benjifisher @quietone worked on this issue, and I reviewed it a few weeks ago. I should be able to move this issue along.

🔟 Is anyone working on Migrate <> Modeler API?

Migrate Initiative Meeting References: #modeler_api Slack channel and https://www.drupal.org/project/modeler_api (edited)
Migrate Initiative Meeting (Original Request) https://drupal.slack.com/archives/C226VLXBP/p1753971422755039?thread_ts=... (edited)
benjifisher I have thought about that, but I have not had time since DrupalCon Atlanta to do anything about it.
benjifisher A good first step (proof of concept) would be a contrib module (maybe a sandbox project) that uses modeler_api to edit migrate_plus.migration.* configuration. Maybe limit it to the csv source plugin and the entity destination plugin and one or two process plugins.
benjifisher In fact, that might already provide value (not just proof of concept).
benjifisher The problem is that the Migrate API does not provide enough information to tell the modeler how to build the config form for each (source, process, destination) plugin. That is a long-term project.
thejimbirch Would you be able to sketch out a Meta issue for this, and I can see if any of my team is interested in helping out?
benjifisher I could do that. Where should I add that? It does not reallly belong in the issue queue for the modeler_api module. :thinking_face:
thejimbirch Migrate queue?  Since it is meta and recommending a contrib solution, it could live there until a solution is accepted.
benjifisher Good idea. After all, that queue is for the "migration subsystem", not any particular module.

1️⃣1️⃣ Wrap-Up

Migrate Initiative Meeting Thanks for coming all! See you in 2 weeks
benjifisher Thanks all. This was a productive meeting! Please continue the discussion: we will wait at least a day before copying the transcript.
benjifisher Now I have to get back to my day job, and put out some fires. :fire: :wink:

Comments

benjifisher created an issue. See original summary.

benjifisher credited heddn.

benjifisher’s picture

Issue summary: View changes
Status: Active » Needs review
smustgrave’s picture

Status: Needs review » Fixed

Reviewed the threads and active participants were credited and conversation captured.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.