You can easily see from the commit logs what commits were made after the 
fork which gives insight on why they were forked and how they differed 
(looks like net-ping2 was forked because net-ping depended on an old 
version of raw-socket and it looks like raw-socket2 was forked to add 
support for node 0.11/0.12?).

Other thing of note that is different: raw-socket2 has a valid repository 
URL in the package.json, the one in raw-socket is not a valid URL (creates 
a dead link from NPM).

As to why these forks were published to NPM instead of sent as pull 
requests, only the author would know (you could try asking 
<https://github.com/steffengy/node-raw-socket/issues>), but my guess is 
because it was easier to do that than to try to figure out how to use 
BitBucket and submit patches through there (I'm assuming there's no easy 
way to send a PR from a fork on GitHub back to the original BitBucket 
project...).

On Friday, August 28, 2015 at 7:41:49 PM UTC-7, Stephen Vickers wrote:
>
> Hi All,
>
> I am the author of the raw-socket module at:
>
> https://www.npmjs.com/package/raw-socket
>
> I've noticed that there are now a few fork's of this module which have 
> been published to npm:
>
> https://www.npmjs.com/package/raw-socket-ng
>
> https://www.npmjs.com/package/raw-socket2
>
> I can't tell the difference between my version and these fork'd versions 
> (other than that they look to be behind in terms of version/features).
>
> Can anyone shed any light on the differences?
>
> I don't mind taking patches if my module is missing something.
>
> Note that this is also true for the net-ping module I author at:
>
> https://www.npmjs.com/package/net-ping
>
> This has a fork at:
>
> https://www.npmjs.com/package/net-ping2
>
> The questions above apply to this too.
>
> Thanks for your input.
>
> Steve
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/415f62fd-ddd3-47fe-ac4a-198f4ec077f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to