Problem/Motivation
In #2281691: User interface for migration-based upgrades we added a new migrate_drupal_ui module. This issue will discuss whether the separation of migrate_drupal and migrate_drupal_ui is valid.
Discuss. The basic reason for this is the fact that loadsa modules is confusing and unnecessary. We have migrate, migrate_drupal and migrate_drupal_ui. None of these modules are meant to be on in production so the usual UI vs API distinction is not so relevant.
After reviewing a lot of the code in https://www.drupal.org/project/migrate_upgrade and thinking about how it is tied into the assumptions made in the core migrate_drupal module, I think we should not be adding yet another module to core. Rather this should become part of the migrate_drupal codebase. The migrate_upgrade codebase basically contains a form, a drush command and a trait for both the form and the drush command to use to migrate a Drupal site. Obviously we're not going to be putting the drush commands in core so we're adding a form and trait to migrate a Drupal site through the UI. That would seem to be a pretty good fit with the existing migrate_drupal module especially since this module is designed to be turned off once the migration is done.
(alexpott #2281691-109: User interface for migration-based upgrades
OR
The proposal makes perfect sense purely from the point of view of the full upgrade path. However, we are going to want to provide tools for custom Drupal-to-Drupal migrations in contrib, which will need migrate_drupal but not the upgrade UI... Perhaps they could disable the /upgrade path?
(mikeryan #2281691-113: User interface for migration-based upgrades
Proposed resolution
tdb
Remaining tasks
Stances of Migrate maintainers and framework and release managers
- Migrate maintainer - Adam Globus-Hoenich (phenaproxima) - Merge (#11)
- Migrate maintainer - Ben Doughtery (benjy) -
- Migrate maintainer - Lucas Hedding (heddn) - Do not merge - (#21)
- Migrate maintainer - Mike Ryan (mikeryan) - Do not merge (#8)
- Migrate maintainer - Vicki Spagnolo (quietone) - Merge (#19, #26)
- Framework manager - Alex Pott (alexpott) - Merge (#17)
- Release manager - Jess (xjm) -