There is a well known migrate module that is basically a set of drush commands. drush_migrate is bound to be confused with migrate's drush integration.

I am the maintainer of drush and the co-maintainer of migrate. Thanks.

Comments

brianpkennedy’s picture

brianpkennedy commented

Sorry. I didn't think there would be a collision.

I didn't think you can change the project's name once the CVS structure is created though. Do you know how i can go about doing that? I am willing to rename the project to something like drush_drake, but since I have added in more commands for migrating permissions and settings, I chose the name drush_migrate.

brianpkennedy’s picture

brianpkennedy commented

In the mean time i've updated the project description to link to the migrate module.

brianpkennedy’s picture

brianpkennedy commented

The project page has been renamed to "Drush Drake", however the url is still /project/drush_migrate, the module is still drush_migrate.module, and the CVS path is still drush_migrate. I don't mind renaming it, but from what I understand that is a difficult process. Since the project is really only a day or two old I don't have any problem with starting a new project called drush_drake and committing the code there, but I'd want drush_migrate to be removed completely.

brianpkennedy’s picture

brianpkennedy commented

I made a request in the infrastructure queue about getting the project renamed or removed. #881364: drush_migrate Project rename or removal

TheDoctor’s picture

TheDoctor commented

Subscribing; this sounds epic!