Rohit, The same problems exist for all software, indie or enterprise.
If you depend on it, be prepared to one day either own it or find a replacement. Such is the way of the world. On Fri, Nov 30, 2012 at 11:37 PM, Rohit Rao <[email protected]> wrote: > Ken brings up a good point. The biggest risk with indie tech like this is > that it might get abandoned due to unforeseen circumstances. > > It would behoove us to have some sort of fallback so users don't get > negatively affected with their projects due to something like this. > > > On Dec 1, 2012, at 2:14 AM, Marak Squires <[email protected]> wrote: > > Ken - > > Are you actually using hook.io? I suspect you are not. If you are, you have > the code and can continue to use it if you feel so inclined. > > If you are genuinely concerned about continued development, you can fork and > rename the project at any time. > > I'm telling you as the creator, you should not waste your time. There are > several fundmental problems with hook.io ( many of which are technical ). > Solving these problems would require an entire new suite of libraries and > tools, which do not exist. > > - Marak > > > > > On Sat, Dec 1, 2012 at 12:20 PM, Ken <[email protected]> wrote: >> >> 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 > > > -- > 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 > > -- > 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 -- 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
