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.
The hope is that most or all of the maintainers will attend. We will try to focus on longer-term goals than in the weekly meeting.
| quietone |
Wanted to check that the recent restructure is moving in the right direction and what other changes should be made. |
| mikelutz (he/him) |
https://www.drupal.org/docs/upgrading-drupal |
| quietone |
There are to 'preparation pages', https://www.drupal.org/docs/upgrading-drupal/prepare-major-upgrade/prepa... and https://www.drupal.org/docs/upgrading-drupal/upgrading-from-drupal-6-or-.... Can we get that into one? |
| srjosh |
Is this about upgrading migration modules/code to compatibility with D10, or about upgrading sites using migration? |
| dinarcon |
Or about about updating the documentation itself? |
| bsnodgrass (he/him) |
Good topic, mobile ATM but wanted to check in! |
| quietone |
This is about the changes to the documentation itself. |
| quietone |
And more about structure than the details. Although, details need to be considered when there are two pages for 'preparing'. |
| quietone |
What are your thoughts about making the 'Upgrading Drupal' guide easier to navigate? |
| bsnodgrass (he/him) |
I'll be glad to review the detail on this... it's a topic that is very timely for us, and I've been getting deep into details on a number of projects currently |
| bsnodgrass (he/him) |
I have a reminder set for tomorrow sometime if my day stays under control |
| srjosh |
Oh, I wish I could make it this year! |
| irinaz |
JOin us for online sprint !!!! https://docs.google.com/document/d/1GruXFHmdSVj7H_mGZdUQGrZQDsPVIPMRlhuu... |
| irinaz |
https://www.badcamp.org/community/contribution-lounge |
| irinaz |
and for sessions https://www.badcamp.org/events/schedule |
| srjosh |
interesting! |
| mikelutz (he/him) |
@irinaz If you want me to make threads in the meeting, please comment in 1️⃣ . Please don’t post threads with number icons in the middle of a moderated meeting. |
| irinaz |
@mikelutz (he/him) my apologies. I can delete this thread and send you content directly |
| mikelutz (he/him) |
In the future.. It’s done now, and a worthwhile thread to have in the meeting. |
| bsnodgrass (he/him) |
I set a reminder for myself on this one as well. |
| bsnodgrass (he/him) |
@irinaz per for contrib sprints, those are online? Is there a need to register or just show up? and are there Sessions that will be available online? I couldn't find anything that looked like registrations for remote attendees |
| irinaz |
yes, today and tomorrow |
| irinaz |
sprint is online, camp is in person |
| irinaz |
no need to register for sprint 🙂 |
| bsnodgrass (he/him) |
@irinaz thanks! |
| bsnodgrass (he/him) |
Tight schedule, but I will see what I can do. |
| mikelutz (he/him) |
#3266491: Add content in migrate UI functional tests only when needed |
| mikelutz (he/him) |
Needs a reroll, any volunteers? |
| benjifisher |
Correction: the latest reroll needs a review. Any volunteers? |
| benjifisher |
It was RTBC before the reroll. |
| quietone |
I can reroll it, probably today. |
| quietone |
Ugh, read the thread! It does not need a reroll, it needs a review. |
| quietone |
I can look at it but I can't RTBC. |
| benjifisher |
I did the reroll, so I cannot RTBC. |
| mikelutz (he/him) |
You can RTBC your own reroll... |
| mikelutz (he/him) |
As long as you didn't write the code in the original patch. |
| benjifisher |
OK, I am on it. |
| mikelutz (he/him) |
And even then you are fine, as long as someone else RTBCed the original. |
| benjifisher |
I think I owe you a snarky comment ... |
| benjifisher |
... #3266491: Add content in migrate UI functional tests only when needed#comment-14713566 |
| mikelutz (he/him) |
#2960204: Make it possible for optional log messages from *skip* process plugins to contain context |
| danflanagan8 |
I have an approach that works well for this, but it also seems like something that maybe doesn’t provide much value anymore. |
| mikelutz (he/him) |
I'm not a huge fan of adding more code around this. I think it's of limited usefulness given modern debugging tools. This is turning into the migration equivalent of adding print statements throughout your code, and I'm not a huge fan of enabling that or having to maintain the code and functionality around it when we want to make real improvements to the system. |
| danflanagan8 |
What do you think about closing as “will not fix” then? And justifying it by saying that it’s no longer of significant value given the related issue I added in my most recent comment? |
| mikelutz (he/him) |
I love closed won't fix... |
| mikelutz (he/him) |
Just in general.. |
| mikelutz (he/him) |
But here too. |
| danflanagan8 |
Closing anything always feels good |
| benjifisher |
I do not think we give issue credit for Closed (won't fix). It is a shame.
Less is more. |
| danflanagan8 |
It’s ok, most of the patches on this one were unnecessary credit-farming things anyway |
| mikelutz (he/him) |
I don't think we should give issue credit for closed won't fix... |
| danflanagan8 |
We get credit for talking about it in the meeting 🙂 |
| benjifisher |
:rolling_on_the_floor_laughing: |
| danflanagan8 |
Is one of you going to close it? Feels like a maintainer should flip the switch on a closed won’t fix |
| mikelutz (he/him) |
Done, and commented on my reasons. |
| danflanagan8 |
thanks! |
| danflanagan8 |
ha ha, I just read it |
| mikelutz (he/him) |
Feel free to elaborate regarding the discussion here. ;-) |
| danflanagan8 |
will do |
Comments
Comment #8
benjifisherComment #11
benjifisherComment #12
quietone commentedI reviewed the minutes and the number of replies is correct for each discussion. But I did find a missing sentence in the reply from Matroskeen in Announcements and have added that. And made formatting corrections. I agree with the credit.
Comment #14
quietone commentedThere have been no comments here that there are errors in the minutes. I am going to close this now.