Proposal: kill off the drush convert-makefile functionality

Greetings distribution maintainers.

In the past, there were a bunch of restrictions for what kinds of things you could put in your drupal-org.make file if you wanted your distribution packaged by drupal.org for download. Thanks to all the work I've been doing as part of http://drupal.org/community-initiatives/drupalorg/distribution-packaging nearly all of those restrictions are now gone.

Previously, there was a drush command called "convert-makefile" that would take a generic .make file for a distribution and convert it into something you could safely put in your drupal-org.make file. It did things like mapping raw project names into the latest official point releases of those projects, stripping out anything that wasn't going to be allowed (e.g. 3rd party libraries, etc).

Now that almost all the restrictions are gone, I'd like to just kill convert-makefile entirely. It seems like the better workflow is to just use drush verify-makefile to ensure your .make file will be okay, and if not, you should just fix it directly. But, it just doesn't seem like convert-makefile is still useful, and it's a fair bit of code to maintain that I'd much rather just remove if no one is actually going to use it.

SO...

A) Does anyone in here actually care about and use convert-makefile?

B) If so, is it only because of the old restrictions drupal.org used to enforce? Given what's allowed now, would you still keep using it?

There's no issue on drupal.org yet about actually killing convert-makefile (and it's going to span a few different projects) so I figured I'd just open a discussion here to solicit feedback. Please leave your thoughts either way, so I can get a sense of what the various distro maintainers think. My hunch is no one uses this tool anymore, and we can safely kill it, but I wanted to get more hard data to back that up. ;)

Thanks!
-Derek