Hello all, it’s time for the weekly 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 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-01-05 2100Z (tentative)
0️⃣ Who is here today?
| benjifisher | :wave: I am chipping away at the NR queue. |
| quietone | Still suffering from timezone changes, but awake now. |
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.
2️⃣ Action items. To be added later.
3️⃣ Statistics
| mikelutz (he/him) | Fixed since last week, 0, RTBC: 1, NR: 15 |
| mikelutz (he/him) | https://docs.google.com/spreadsheets/d/1o0Rjlc1vnnLP5bM5P-SMMyGzqn7258hi... |
| benjifisher | Of the NR issues, 5 out of 15 (now 6 out of 16) are for meetings. I usually do not count those in the stats. |
| mikelutz (he/him) | I guess I didn’t pay attention today.. I’m used to the meeting issues being 1 out of like 43, lol. |
4️⃣ Comment in this thread if you are looking for ways to help. Give us some idea of what you would like to do: documentation, code review, testing, project management, ...
5️⃣ Previous minutes.
7️⃣ SQL source plugins throw exceptions if database is not available
8️⃣ Missing mapping for “nodereference_url” widget
| mikelutz (he/him) | #3000717: Missing mapping for "nodereference_url" widget |
| benjifisher | I am looking at it now. |
| benjifisher | @Anybody: Can you help explain the point of this issue? |
| benjifisher | It looks as though the D6 nodereference module provides two different field types. They both represent node references, and they are both mapped to an entity-reference field. |
| benjifisher | Do the two fields have the same data structure and only differ in the widget? |
| benjifisher | It looks as though the nodereference_select field type is already supported, and this issue adds support for nodereference_url. |
| Slackbot | Ok! I've sent @Anybody a link to your message. |
| quietone | I am inclined to argue that tests are not needing for this. We are only adding strings to a mapping, all the code doing the mapping and converting the field is well tested. |
| quietone | Looking for precedence. |
| quietone | Here is a similar one for a field instance, #3314134: Add i18n_taxonomy_term_reference_plain to TaxonomyTermReference |
| quietone | Also, changing the Drupal 7 fixture might cause tests in contrib to fail. |