Hello all, it’s time for the weekly migration initiative 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 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 here: https://www.drupal.org/project/drupal/issues/3174359. 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:

0️⃣ Who is here today? What simple thing have you been putting off for too long?

damienmckenna :wave:  Uploading Contrib Half Hour videos :wink:
benjifisher I have been squinting and suffering eye strain, and finally bought myself some slightly stronger reading glasses two days ago.
dinarcon Hello :wave: Updating the example repository for the 31 days of migrations series to make it D9 compatible. For the most part, it is about updating info.yml files.
heddn I need to absentee vote my ballot
quietone Setting up samba file sharing on the home server.

1️⃣ What should we talk about today? Suggest topics here and I will add threads.

damienmckenna How about moving the migrate modules back to d.o?
damienmckenna (many of them were moved to DrupalSpoons and the d.o issue queues were disabled)

2️⃣ Action items. To be added later.

damienmckenna Update Commerce Migrate Ubercart 7 database
dinarcon Start the glossary at https://www.drupal.org/docs/8/api/migrate-api/migrate-api-overview
quietone Follow up old issue, and probably close, https://www.drupal.org/project/drupal/issues/2317865
quietone Fix tests, https://www.drupal.org/project/drupal/issues/2845340

3️⃣ Statistics

benjifisher Fixed since last week's meeting: 10 (not counting issues for meetings). One of the fixed meetings is from June, so it looks as though @quietone is working on the backlog. :+1:
benjifisher RTBC: 12, including two that have been waiting more than 4 weeks and two Major issues.
benjifisher NR: 17, including one that has been waiting almost 4 weeks and three Major.

4️⃣ Commerce migration: documentation

benjifisher Scroll up to yesterday's questions in this channel. I do not know how to answer questions like this: how much is expected to work at this point? Is there a page I can point to? Perhaps a meta issue? I know that work is in progress, but people are trying to do migrations right now.
damienmckenna A number of docs files were committed, these two are left: #3167818: Add README for Ubercart
benjifisher Is there a release for the ones that have already been committed or do you have to look at the dev version?
damienmckenna They're in the dev version, quietone wanted to finish these before tagging another release.
quietone @damienmckenna Are you able to update the Ubercart 7 fixture?
damienmckenna I'll take a look next week, will need to first see what the requirements are - thank you system table for making this a bit easier.

5️⃣ MigrateExecutable should catch not only exceptions, but also fatal errors

benjifisher #3167267: MigrateExecutable should catch not only exceptions, but also fatal errors
benjifisher There has been a lot of discussion on this issue, mostly between @mikelutz (he/him) and @wimleers (he/him).What are the right questions to ask? For example:We know it is better to fix errors than to catch them, but does catching them here really affect long-term maintainability?What are some real-life scenarios where this comes up?What is the practical effect when running a migration of not catching errors?
mikelutz (he/him) At this point, we just need to get the opinion of one of the framework managers as to whether it's something we want to do.
mikelutz (he/him) I've said all I want to say on it. Your questions are fine, but the root of my objection is that this fundamentally changes the relationship and the responsibility that core code has with respect to contrib code, and if we go down this path, then we have to start doing this around all hooks, events, plugin calls, and anywhere else core runs dynamic code that could be provided by modules, and that is a big decision that needs to be made by the framework and release managers as to whether it's something we want to tackle.

6️⃣ Add a migration source plugin for JSON:API

benjifisher #3150949: Add a migration source plugin for JSON:API (edited)
benjifisher Kudos to @quietone for starting to work on this issue.

7️⃣ Add required variables config to Variable migrate source plugin, and if one of those are missing, return zero rows

benjifisher #3152789: Add required variables config to Variable migrate source plugin, and if one of those are missing, return zero rows
benjifisher RTBC. The patch was already committed (which means that it fails to apply when re-tested every two days). We are just waiting forpproval of the CR.

8️⃣ migrate mapping & messages table names are truncated, can lead to incorrect mapping lookups

benjifisher #2845340: migrate mapping & messages table names are truncated, can lead to incorrect mapping lookups
benjifisher RTBC, but the PostgreSQL test is failing. Do we care? (I think we do.) Why doesn't the testbot throw it back to NW?

9️⃣ Documentation (glossary)

benjifisher @dinarcon, are you planning to add a Glossary section to https://www.drupal.org/docs/8/api/migrate-api/migrate-api-overview?
benjifisher Everyone else: are there terms you would like to see included?
dinarcon Yes, I will get started later today.

1️⃣0️⃣ Config schema definitions for plugins aren't applied to their derivatives - Migration plugins

benjifisher #2320937: Config schema definitions for plugins aren't applied to their derivatives - Migration plugins
benjifisher This is a follow-up to/child issue of #2317865: Config schema definitions for plugins aren't applied to their derivatives, which was fixed in 2014.The issue here ^ has just the default issue template: nothing is filled in.I searched for "migrat" (to match both -e and -ion) on the parent (fixed) issue and the only match is the reference to the child issue.There is one other child issue, for Views plugins.
benjifisher What is the relation between config schemas and migration plugins? Does this issue make sense in core or only in the context of Migrate Plus?
quietone Or did it make sense back when migration were configuration?
benjifisher I am glad you know the history of this system, since I do not! If that is what is going on, then we can either close this issue as outdated or move it to the MP issue queue ... but see the discussion under 1️⃣2️⃣.

1️⃣1️⃣ Wrap up.

benjifisher Thanks for participating! I will update 2️⃣. Please continue to add comments in the threads. In 1-7 days, I will post a transcript for today's meeting.

1️⃣2️⃣ DrupalSpoons vs. d.o for Migrate Plus, Migrate Tools, etc.

benjifisher How has this experiment worked out? Has the issue fork capability on d.o advanced to the point where we can move back to d.o?
benjifisher There are a few drawbacks to using DrupalSpoons. Maybe it is just the friction of adapting to a new system, but that does not mean it is irrelevant.
benjifisher I do not like that many (all?) open issues on d.o were closed (as duplicates) in favor of the migrated issues on DS.
benjifisher I recently looked for some issues on Migrate Plus. There were patches on the d.o issues, but I did not see how to get the equivalent branch or fork or whatever on DS.
damienmckenna The movie to DS didn't copy over the patches, didn't create merge requests from the patches, it just copied the issue discussion. This made it less than useful.
heddn as I've had time, I've added a handful of PR/MRs for patches. And commented as such. I know there is also some effort underway to automate the re-creation of patches. I've not had as much time to track that as I'd like :disappointed:

Participants:

damienmckenna, benjifisher, dinarcon, heddn, quietone, mikelutz (he/him)

Comments

benjifisher created an issue. See original summary.

benjifisher’s picture

Issue summary: View changes

quietone credited dinarcon.

quietone credited heddn.

quietone credited mikelutz.

quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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