nope... that answers my question. my concern was just for devs like
myself who are new to node who might've implemented hook.io and then not
known where to turn when the module is abandoned.
R
On 12/1/12 3:04 AM, Nuno Job wrote:
It's an MIT licensed project:
1. Go to github.com <http://github.com>
2. Click fork
3. Rename the project and change package.json accordingly
4. npm publish
You are now the owner of the `new-hook-io` project.
This is all there is to "pick up where they left off".
If you are concerned about the number of followers the project had,
well you have to recreate it. So did Marak back in the day, hard work
and a lot of passion is what made people have visibility to the project.
You seem to be very passionate about your arguments but quite frankly
there not much substance to it.
Thinking that `forking` is not from the "school of developers" you
come from must mean you don't come from an open source world:
*
http://files.cyberciti.biz/uploads/tips/2007/06/44218-linuxdistrotimeline-7.2.png
Nuno
On Sat, Dec 1, 2012 at 8:55 AM, Ro Rao <[email protected]
<mailto:[email protected]>> wrote:
seven months ago, i posted my first email to this group. the one
you responded to was the second email i've ever posted to this group.
the first one was about a project i was working on that had a
particular set of requirements. the helpful response email i got
was from marak, suggesting that hook.io <http://hook.io> would do
what i needed based on my requirements. i looked into it and
thought it was legit, but for one reason or another, i decided
against using it.
i'm working on another project now, and if the whole idea behind
these modules is "use at your own risk", then that's kinda bs, and
frankly not the school of developer that i come from.
i think it would make sense to have some construct where if a
module is implemented and then abandoned, the submitter would be
willing to let someone else pick up where they left off.
R.
On 12/1/12 2:39 AM, Isaac Schlueter wrote:
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]>
<mailto:[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]>
<mailto:[email protected]> wrote:
Ken -
Are you actually usinghook.io <http://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 withhook.io <http://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]>
<mailto:[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 onhook.io
<http://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 [email protected]
<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:[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 [email protected]
<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:[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 [email protected]
<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:[email protected]>
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
--
Rohit Colin Rao
/Writer / Director / Producer/
ULTRASONIC
ultrasonicmovie.com <http://ultrasonicmovie.com>
206.293.8148 <tel:206.293.8148>
--
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]
<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:nodejs%[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
--
Rohit Colin Rao
/Writer / Director / Producer/
ULTRASONIC
ultrasonicmovie.com <http://ultrasonicmovie.com>
206.293.8148
--
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
