Isn't it wiser to make a new revision of it, saying that this module is
no longer maintained?
This way, those who are still looking for this module, or any other
unmaintained module, will not get an access-denied, or page-not-found
error pages, but an informative page telling them it's better to look
for an alternative (or better - inviting them to take responsibility
over the module). The page can also include the rational behind the
maintenance halting, so they can decide what to do.
Zohar
Adrian Simmons wrote:
Hello,
Just a short note to say that I'm officially ending development of
themedev.module, and if anyone is intrested in it please get in touch.
I also wanted to ask what the policy is on closing up development of a
module.
I'm of the opinion that deleting the themedev project would be the best
course of action right now (since themedev really has been surpassed by
the likes of the Firefox 'Firebug' extension), I can see no viable use
case for it. The code would of course remain in CVS in case anyone
really wanted to revive it or steal code.
Any objections to me removing the themedev.project from drupal.org?