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. 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 :bust_in_silhouette: emoji. To take a comment or thread off the record, start with a :no_entry_sign: emoji.

Core migration issues

Next video meeting 2023-07-27 2100Z (tentative)

0️⃣ Who is here today?

mikelutz (he/him) I am. 🙂
Dan Davis Present
Stephanie I'm 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.

mikelutz (he/him) #3247718: Allow process plugins to flag a row to be skipped
dinarcon Could we revisit Drush and migrate_tools integration? #3213947: Drush core migrate commands integration refactor? migrate_tools is overriding Drush core commands. So, it is not clear to me what is the scope of the above issue. (edited)

2️⃣ Action items. To be added later.

3️⃣ Statistics

benjifisher Fixed in the last 2 weeks: 1 (not counting issues for meetings).
benjifisher RTBC: 12, 1 of which is Major.
benjifisher NR: 6, including 2 Major.
benjifisher Needs subsystem maintainer review: 6
benjifisher 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.

6️⃣ Announcements

7️⃣ Consolidate code in the migrate_drupal module.

mikelutz (he/him) We should invite some of the committers to the video call in 2 weeks. (edited)

8️⃣ Allow process plugins to flag a row to be skipped

benjifisher #3247718: Allow process plugins to flag a row to be skipped
benjifisher I owe you a review on that.
benjifisher One thing that makes it hard to review is that I am not familiar with the whole Executable class. IIRC from my first look at that issue, there are a lot of changes in there, and I do not have a good idea of the overall approach.

@mikelutz (he/him), can you give a few pointers?
mikelutz (he/him) Well, the changes in the executable are really just complementing the logic of processing the migrate skip row exception.  So any try/catch block that catches a migrate skip row exception also checks if the row skip flag is set and should end up handling it the same way as if a skip row exception was thrown.  Once this is in we can deprecated the skip row exception and eventually remove the try/catch blocks and just process the flag.
benjifisher Thanks, that helps.

9️⃣ Add XPath-style filtering ability in JSON data parser plugin

benjifisher #3007709: Add XPath-style filtering ability in JSON data parser plugin
benjifisher Integration between merge requests and issues on d.o is still incomplete. It looks as though @Stephanie updated the MR, but I missed it because I rely on updates to the issue.
benjifisher If this issue is ready for review, let's update the status.
Stephanie Sorry, @benjifisher I was not sure what was supposed to happen, I will update the issue status.

1️⃣0️⃣ Drush core migrate commands integration

benjifisher #3213947: Drush core migrate commands integration refactor
benjifisher This issue may be outdated.
benjifisher We were tied up in knots for a while, worrying about version compatibility and whether that required a new major version of migrate_tools. One way or another, I think we have moved past that.
dinarcon I think the original plan was to extend Drush core commands. If I understand things properly, migrate_tools is no longer trying to integrate, but instead overrides Drush commands. So, is this outdated in the sense that it is no longer needed? Or outdated because it needs a review of current status and more work is needed? (edited)
benjifisher Yes. :wink:
dinarcon Yes, to no longer needed or to needs issue summary update? :sweat_smile: If the latter, do we want to extend instead of override the commands?
benjifisher The :wink: indicated that I was saying "yes" to "A or B". My guess is "no longer needed", but I do not know.
dinarcon I also think it would no longer be needed. @heddn thoughts on this?
mikelutz (he/him) From the issue summary it looks to be about refactoring the way that we are overriding the drush core commands to minimize code duplication.  I think the issue is valid, but it’s not major, it’s purely a cleanup issue.
heddn yes, just cleanup. if someone had time. i don't

1️⃣1️⃣ Activity level in this channel and support for D7 migrations (edited) 

benjifisher My impression is that this channel has been more active than usual in the last few weeks. Agree, disagree?
benjifisher I have been wondering whether the EOL announcement for D7 would have an effect on D7 migrations, or if the owners of D7 sites would continue to ignore the long-term prospects for their sites.
benjifisher If my impression of the activity level is correct, then it could be an indication that the EOL announcement did "wake up" those site owners. In that case, we can expect there to be a lot of work on D7 migrations until the EOL in January 2025.
benjifisher Maybe this should be a separate thread, but what should we be doing to support D7 migrations for the next 18 months?
benjifisher This RTBC issue should help with some migrations (when the site is simple enough that the migration can be done through the UI): #3063856: Add ability to view migrate_message table data
benjifisher Probably the most important thing we can do now to support D7 migrations is more documentation.
mikelutz (he/him) It does seem more active as of late.

1️⃣2️⃣ Develop concise library of resources for Drupal 7 site owners

benjifisher #3374227: Develop Drupal 7 end of Life Landing Pages with concise library of resources
benjifisher The new page is already live: https://www.drupal.org/about/drupal-7/end-of-life. I am not sure whether it is findable from the menus, yet.
benjifisher The Drupal Association will be working with community volunteers to add a more robust resource library to this page, as well as the listing of certified migration partners who we recommend to support your Drupal 7 migration project.
benjifisher "Community volunteers": that means us!
benjifisher The key phrase here is "for ... site owners". We will include links to information for developers, but this page is aimed at site owners.
benjifisher Links for developers have to be in a section that says something like this: "If you already have a relation with a Drupal developer, then these are the resources they will need to plan and execute the upgrade to Drupal 10".

1️⃣3️⃣ Wrap up

benjifisher Thanks for participating! I will update 2️⃣. Please continue to add comments in the threads. In 1-7 days, we will post a transcript for today's meeting.
benjifisher I will also have to update 3️⃣, 5️⃣, and 6️⃣. (edited)

Comments

benjifisher created an issue. See original summary.

benjifisher credited dinarcon.

benjifisher credited heddn.

benjifisher credited mikelutz.

benjifisher credited Stephanie.

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Issue summary: View changes
Status: Active » Needs review
smustgrave’s picture

smustgrave commented
Status: Needs review » Fixed

Went into the #migration slack channel for 7/13/2023.

All the threads appear to be captured

All users who participated in conversation (outside the "here") portion have been credited.

Status: Fixed » Closed (fixed)

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