In reply to Brad Touesnard.

The reason why it's named "wp-migrate-db" is because it's built on a fork of the original open-source plugin. I had hoped it would provide a cleaner commit history, but the first version of the pro plugin turned out to be almost a total rewrite. Nevertheless, it seems semantically correct because it is an extension of the goals of the original. And it still indicates that the "pro" version that Delicious Brains made offers something more (support).

As for Press Trends, I'm glad that you're removing that! When I first noticed the kind of information that it was sending I was pretty upset. Especially since there wasn't any option to disable it, and it was a fairly well hidden feature.

But, Press Trends isn't the only issue - I just mentioned that in my comment because it's an easy-to-explain change. The main reason why I started work on wp-migrate-db is because it's an incredibly important plugin in my stack. It's something that I need to pay close attention to the development of, and I needed to make installation as simple as possible. So, all that license validation code had to go - dealing with that in my provisioning scripts would have been a huge pain. And finally there's the ethical issue of using closed-source software (which, after all, is a pretty big part of the GPL's purpose).

Anyway, after I made the improvements I needed, I decided to release them for everyone to use - hopefully allowing others to improve on the changes I made and catch any bugs I may have introduced.

I really wish I could do this without interfering with Delicious Brains, but I don't have any good solution for that.