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.
| benjifisher |
I know that @robpowell and @bsnodgrass (he/him) have commented on this thread in recent weeks.Over the weekend, at DrupalCamp CO, I asked Bob to help with some testing.Maybe I can ask Rob to help with some stalled issue. |
| robpowell |
Would love to help on that front. |
| Arctic.Cheetah |
I like to explain difficult concepts to beginners. I'm new myself to Drupal but I feel like Documentation is where I'd like to contribute most. (To the community as a whole) (edited) |
| benjifisher |
The first two NR issues on https://www.drupal.org/project/issues/drupal?status=8&component=migratio... look like a good place to start. They have only 5, 11 comments, so you do not have to wade through a long discussion.Testing and/or code review will be welcome.Improved errror messages are some of the low-hanging fruit of DX. |
| benjifisher |
@Arctic.Cheetah: How about this issue for Migrate Plus? Documentation, NR: #3283457: Improve entity_generate documentation |
| benjifisher |
NW for tests: #3007709: Add XPath-style filtering ability in JSON data parser plugin.I do not use JSON sources much. If writing an automated tests is not something you want to do, then attaching a sample JSON source file and a sample custom migration to the issue would help. Divide and conquer! |
| benjifisher |
If you want to discuss any of those issues, then I can open a separate thread. |
| bbombachini |
Last week I’ve mentioned this, it’s also regarding documentation and I can fix:https://www.drupal.org/docs/8/api/migrate-api/migrate-process-plugins/li... - all of the process plugins’ links take you to an error page.I think now we need to specify the branch? I just would like to confirm if I just add the link to the newest branch or what would be better in this case. (edited) |
| benjifisher |
I am not sure. If adding the branch fixes them for now, then that will be a step forward. Let me see if I can guess how to get a perma-fix. |
| bbombachini |
Adding the branch fixes for now… the link points to HEAD, maybe the branch defaults to master when it’s not specified? Master branch only has one .info file (edited) |
| benjifisher |
I tried a few things, none of which worked. I guess we need to add a branch name.Some of those links use cgit.drupalcode,org instead of git.drupalcode.org. I do not know the history, but cgit seemes to redirect to git. As long as you are updating the links, you may as well use git to save us from the redirects. |
| bbombachini |
Sounds good, I’ll fix for now using the latest branch. Thanks for looking into it @benjifisher |
| benjifisher |
Good thought about the default for HEAD, but I do not think it checks out. I looked at a project that I maintain. In the GitLab settings, the default branch is set correctly. But https://git.drupalcode.org/project/ptoc/-/blob/8.x-1.x/src/Form/PtocConf... works and replacing 8.x-1.x with HEAD does not.There are no other branches for that repository. |
| bbombachini |
Hmmm, that’s good to know… |
| benjifisher |
$ git branch -a
* 8.x-1.x
remotes/origin/8.x-1.x
remotes/origin/HEAD -> origin/8.x-1.x |
| benjifisher |
As long as we are looking at that page, @joachim added a comment:This page should be merged with the list of core plugins. It's not convenient to readers to have to search in two separate pages to find the right plugin for their needs.Opinions? |
| bbombachini |
I think people may assume it’s provided by core (even if it’s written otherwise..) |
| joachim |
The problem with the 2 pages is that you always need to open both to find whether there is a plugin for your particular need. And that’s if you even know there are two pages. |
| joachim |
I agree that some people will manage to miss that some plugins are in a contrib module — even if we put a paragraph at the top of the page that explains it, or text on every single relevant item in the list. But it is better that users think ‘Oh this is the plugin I need…. but where is it? ah I will google it’ than not even know such a plugin exists. |
Comments
Comment #2
benjifisherComment #8
benjifisherComment #9
mikelutzComment #10
benjifisher