Interpersonal drama aside, I actually think this is a very interesting scenario and something the node community should probably consider developing some best practices around. To abstract a bit, what, if anything, can and should the community do when a popular package is abandoned by its sole maintainer?
As far as github and the code goes it looks like Nathan Rajlich has an up-to-date version here (package.json matches NPM, not sue if he's got custom hacks though): https://github.com/TooTallNate/hook.io It seems like NPM is a slightly bigger problem, as Marak is the only maintainer and there are over 60 packages that depend on hook.io https://npmjs.org/package/hook.io so while it would be possible to fork the package it would be a tremendous effort to repoint all of the dependents at the new fork. Perhaps we should have some mechanism for interested parties to petition the registry to take over as maintainer of abandoned packages? --Ken -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
