Quantcast
Channel: Issues for Drupal core
Viewing all articles
Browse latest Browse all 292913

[meeting] Migrate Meeting 2020-06-11

$
0
0

Hello all, it’s time for the weekly migration initiative meeting. The meeting will take place in slack in various threadsThis 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 over chat.➤ 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: #3146005: [meeting] Migrate Meeting 2020-06-11➤*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. (edited) 

0️⃣ Who is here today? What can you say to cheer us all up?

heddnLucas, its sunny today. I need cheering up.
damienmckennaDamien's here, it has been a while.
mikelutzHello.
narendra.rajwar27Hello everyone..
quietoneVicki. This too shall pass
damienmckenna@quietone: .. like a kidney stone :wink:
steinmbRaise his hand
quietone@damienmckenna sure, why not?
benjifisherBenji Fisher. I live in Massachusetts in the US. For a while, we were near the top of the list of US states in number of COVID-19 cases, but our numbers have been going down and we are serious about contact tracing.
dinarconHello everyone :wave: I will be updating the examples of the 31 days of migration series to Drupal 9 very soon. Almost everything can be ported with minimal effort. And in the near future I hope to release an updated version of the series covering the latest developments and new things I have learn over the last year. :slightly_smiling_face: (edited)
Nick Dickinson WildeNick, he/him, My island - Vancouver Island BC, pop 870k, has zero active COVID cases - and no new ones for 3 weeks.
sharma.amitt16Hey everyone.. ahhh little but late
alisonHi! We had an awesome socially distanced outdoor, small-group-shifts baby shower this weekend for my sister in law, it was really fun, gorgeous weather, great people.
heddn@alison it might just be me, every time I see your profile photo I have to double take cause I think it looks like a moose! But its a dog.
benjifisherIt looks like a :cow: to me.
alisonhahaha that cheers me up, too :D I've heard cow before, but not moose. Love it.
ashishdalviAshish Dalvi from India.I am here for the first time. Curious to know more about initiative and looking forward to start my contribution.Its first rain season in mumbai, India :slightly_smiling_face:
benjifisher@ashishdalvi: Welcome! Have a look at 8️⃣ . That might be a good place to start.
ashishdalviThanks @benjifisher Taking look at it.

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

damienmckennaI'd love to see Commerce Migrate upgraded to be D9-compatible, I started work on it yesterday.
benjifisherLink?
damienmckenna#3150733: Drupal 9 compatibility fixes for Commerce Migrate
benjifisherWe have a lot of NR issues. Some have been waiting about 2 weeks, which is not too bad. Is there any "low hanging fruit" on the list? https://www.drupal.org/project/issues/drupal?text=&status=8&priorities=A...
quietoneI think this can be close but need to check, #3003920: Plan how to expose deprecated migration entities
quietoneIn the #bugsmash a migrate issue about file migration running out of memory was a suggested target issue. But to look at that properly, this should be done first, #3006750: Move memory management from MigrateExecutable to an event subscriber  Can someone review and hopefully RTBC
benjifisherFor the record: "a lot of NR issues" means 32. One has been waiting almost three weeks.

2️⃣ Action items. To be added later.

benjifisher3. #3039240: Create a way to declare a plugin ID defined in a yml file as deprecated: set to NW and say what needs to be done. @heddn or @andypost4. #2925899: MigrateUpgradeImportBatch does not use source_private_file_path & source_base_path correctly, making it impossible to have public & private files in separate locations: close to RTBC. @benjifisher5. #3150733: Drupal 9 compatibility fixes for Commerce Migrate: commit changes to `.info.yml` and move forward. @heddn, @damienmckenna, @quietone6. #2607524: [meta] Migrations from Drupal 8 to Drupal 8 and Drupal 8 to Drupal 9: Open new issue for a JSON:API source plugin. @benjifisher, @heddn, or @quietone7. #3003920: Plan how to expose deprecated migration entities: close as outdated. @quietone or @mikelutz8. #2993367: Add the migration from D7 Picture to Responsive Image: Set to NW for nits, mark as Novice (@benjifisher). Fix nits (novice or @quietone). Review (@mikelutz).9. #2974445: [Meta] Refactor MigrateUpgradeExecute tests: Review child issues. @benjifisher10. #3006750: Move memory management from MigrateExecutable to an event subscriber: Needs review, needs volunteer.

3️⃣ Create a way to declare a plugin ID defined in a yml file as deprecated

benjifisher@andypost suggested that we discuss #3039240: Create a way to declare a plugin ID defined in a yml file as deprecated
heddnIts been sitting in NR for way to long. Anyone want to just mark it RTBC to get the next step started?
quietoneIf I understood the comment correct, andypost was suggesting that we add into that patch the deprecation of the action_setting plugin as an example.
andypostHey, last time I checked it was not ready
andypostIt missing example and test
andypostSo I suggested actions
benjifisherMaybe the status should be NW.
andypostFor me the question is chicken-egg - allow deprecation with synthetic example or use it for actions in the same issue (edited)
heddnuse it for action in same issue. that way it dog foods its own.
heddn+1 on NW and using a real example. if there are others that need to do the same later, we can pick that up in follow-ups. $0.02

4️⃣ MigrateUpgradeImportBatch does not use source_private_file_path & source_base_path correctly, making it impossible to have public & private files in separate locations

benjifisher@quietone and I have been discussing #2925899: MigrateUpgradeImportBatch does not use source_private_file_path & source_base_path correctly, making it impossible to have public & private files in separate locations. We could use input on the BC issue raised at Comment 33.11.
benjifisher@heddn, @mikelutz any input?
heddn@benjifisher I responded. forms are not BC.
mikelutzAgreed. We can change it. It won't affect existing migrations. It's a bugfix, not a bc issue.
benjifisher:+1: In that case, it is really close to RTBC.
quietoneWhat a relief. Thanks
benjifisherThe patch looks good, but I set the issue to NW for a CR and a release-notes snippet.

5️⃣ Commerce Migrate

damienmckenna#3150733: Drupal 9 compatibility fixes for Commerce Migrate
damienmckennaI did some of the simpler changes, I didn't have the time to get into some of the more detailed ones. I also haven't tested the changes, hopefully I didn't break anything :wink:
heddn@damienmckenna would a commit of the .info.yml changes help you with any testing?
damienmckenna@heddn: It might help others, and make the testbot be able to run it against D9.
damienmckennaI haven't checked the dependencies yet either.
damienmckenna(though Commerce is on D9 already, so that's a good step forward)
heddn@damienmckenna when you feel it is ready, I can commit it so we can keep up the velocity.
damienmckenna:thumbsup_all:
heddnjust ping me :slightly_smiling_face:
damienmckennaI have two D7 projects that want to upgrade, one has Ubercart, the other has Commerce, so I'll see if I can help on this.
quietonePing me as well.

6️⃣ [meta] Migrations from Drupal 8 to Drupal 8 and Drupal 8 to Drupal 9

benjifisher#2607524: [meta] Migrations from Drupal 8 to Drupal 8 and Drupal 8 to Drupal 9
heddnI think we should move forward with using json as the source for d8 => d9. anyone want to open up an issue to add a json source plugin to core that can handle our rest api?
benjifisherFYI we have been discussing improved support for JSON:API as a migration source. If it works, then this could reduce a many-to-many problem (migrating from D8, D9, with multiple minor versions to D9, D10, multiple minors) to a many-to-one problem (already solved by the JSON:API module) and a one-to-many problem.
benjifisherI think that issue already exists. Maybe on the Migrate Plus queue.
dinarconIs the goal to move Migrate Plus' url plugin and the JSON parser into core? Or will both coexist?
heddn@benjifisher the json parser in migrate plus has very little tests, has lots of issues and doesn't use any more of a JSON api then json_decode. Let's build something from the ground up with test coverage
heddnBurn it to the ground and start over again.
benjifisherWell, the issue exists. A couple of people said they had done initial work, but IIRC they did not post much in the way of patches.
benjifisherYou think it would be a bad idea to develop it in contrib and plan to move it into core?
heddnThe fetcher / parser paradigm is another question... JSON doesn't technically need it. But we do have some precedence with the download and file_copy chained plugins in core. I'd be inclined to say we use download. then just parse it after download. is less to boil of the ocean then trying to add fetcher/parser $0.02. (edited)
heddn@benjifisher yes, because BC. We already have a contrib solution. It needs to be burned to the ground. And we're talking about json parsing. Nothing super fancy. < 300 lines of code for the source plugin if I had to guess
heddnBC, because adding a new one to contrib means a new name. Then moving it to core. Just a nightmare. Do it right with good test coverage and there's no need.
dinarconHa, I just realized that file_copy automatically uses download for remote URIs. Nice. I wonder if it would pass along guzzle_options? In any case, not having to manually specify a local or remote configuration as with the data fetcher plugin is very nice. This would simplify the configuration and make it easier to grasp. (edited)
heddn@dinarcon yes, it does pass those along
dinarconSweet
quietoneIs there a core issue for this?
quietoneI want to update the issue
benjifisherI do not think there is a core issue yet, and the one for Migrate Plus is no longer on d.o: https://gitlab.com/drupalspoons/migrate_plus/-/issues/224
benjifisherShould we create a new core issue for JSON:API? Regular issue or meta? Or should we change the title and scope of the existing meta?
quietoneA new issue please.
benjifisherIt is also related to #3114899: Future of migrate in core in a post Drupal 7 world
benjifisherI think that @heddn also suggested that some sort of DRY solution for migrations would work well with a JSON:API source. Another issue that is no longer on d.o: https://gitlab.com/drupalspoons/migrate_plus/-/issues/133
benjifisherI added an issue: #3150949: Add a migration source plugin for JSON:API. I am not sure:task or feature request?Normal or Major?

7️⃣ Plan how to expose deprecated migration entities

benjifisher#3003920: Plan how to expose deprecated migration entities
quietone@mikelutz, I think this can be closed but you know the deprecation stuff better than me.
mikelutzYes, we are past this.
mikelutzIt's outdated.

8️⃣ Add the migration from D7 Picture to Responsive Image

benjifisher#2993367: Add the migration from D7 Picture to Responsive Image
benjifisherI have a couple of nits, like s/it's/its in a comment. But it is pretty big and complicated, and it would take me a while to do an honest review.Both @heddn and @mikelutz have reviewed this in the past. Could one of you take this on?
quietoneYea, this is part of the meta for the D7 upgrade path and needs progress.
mikelutzI'm fine to rtbc it, but if you want to point out nits, go for it.
benjifisherOK. The good part about nits is that they are easy to fix.
quietone@benjifisher if appropriate tag it as novice, and if no one does it I will do it when I wake up.
heddn@quietone go to sleep already!!!
benjifisherI added my nits, marked it as Novice, and set to NW.
benjifisherThe patch needed a reroll in addition to my nits. All done now. @mikelutz, can you take it from here?

9️⃣ [Meta] Refactor MigrateUpgradeExecute tests

benjifisher#2974445: [Meta] Refactor MigrateUpgradeExecute tests
benjifisherThere are several NR child issues. I plan to look at some of these over the next week.

1️⃣ 0️⃣ Move memory management from MigrateExecutable to an event subscriber (edited) 

benjifisher#3006750: Move memory management from MigrateExecutable to an event subscriber

1️⃣ :one: Wrap up

benjifisherThanks for participating!
benjifisherI will update 2️⃣ and add an issue for next week's meeting.
quietone@benjifisher thanks for facilitating. I will go wrap up in my duvet now.
benjifisherPlease continue to add comments. In 1-7 days, I will post a transcript to the issue for today's meeting.
alisonThank you, Benji!

Participants:

heddn, damienmckenna, mikelutz, narendra.rajwar27, quietone, steinmb, benjifisher, dinarcon, Nick Dickinson Wilde, sharma.amitt16, alison, ashishdalvi, andypost


Viewing all articles
Browse latest Browse all 292913

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>