[development] Module retirement?

[Greg Knaddison - GVS]

On 10/6/06, AjK <drupal at f2s.com> wrote:
> I don't want to ditch/retire a module on a whim but to sum up: what's a
> responsible position, as a module maintainer, to take where obvious (big)
> duplication is starting given you can see a better route (but may not be so
> good a route for the user community)?

I'd say that the *most responsible* thing is to provide a "smooth"
path to get your users into the new modules and then retire the
current ones.  This happens pretty often - see:
http://drupal.org/project/dashboard

If you just say "module is retiring, use X instead" and don't provide
an upgrade path then that's OK too.  It's certainly better than just
dropping it and leaving people hanging.  If possible document the
manual steps to move to the module, but ideally provide code that will
take current data in the module and move it to the format needed by
the replacement module.

You could also offer on the project page to let someone else
update/maintain the module if they are really tied to it - maybe
somebody likes your module more than the replacements.

Regards,
Greg

-- 
Greg Knaddison | Growing Venture Solutions
Denver, CO | http://growingventuresolutions.com
Technology Solutions for Communities, Individuals, and Small Businesses