2013/5/25 Alex Kocharin <a...@equenext.com>:
>
>> Whoever likes can publish to npm, whoever likes can push to Github. Both
>> should be given equal chance of discovery though.
>
> Github is a tool for development, npm registry is a tool for deployment. Am
> I missing something here? By the way, mix of those two is very well known to
> create serious trouble (https://github.com/isaacs/npm/issues/1727).
>
> Also, there was a holywar in npm issues about namespacing... I guess
> anything about "proper naming" has been said there already:
> https://github.com/isaacs/npm/issues/798
>

They're both public data containers that you upload stuff into. One
has a single namespace, the other has a username-based namespace.
What's for "deployment" and what's for "development" are purely
personal choices.

>
> On Saturday, May 25, 2013 3:49:36 PM UTC, stagas wrote:
>>
>> 2013/5/25 Alex Kocharin <al...@equenext.com>:
>> >
>> > It's an answer to unrelated question. If a package is intended to be
>> > used in
>> > public, it should be in public registry (npmjs.org). If it's for
>> > internal
>> > use, github will do fine.
>> >
>> > But namespaces could do the job if you publish a package with a name
>> > like
>> > "stagas.merge". It's quite uncommon though.
>> >
>>
>> I want both visibility and proper naming. That logic isn't valid.
>> Github is very public. We just need to find a way to index these along
>> with the rest npm modules. Whoever likes can publish to npm, whoever
>> likes can push to Github. Both should be given equal chance of
>> discovery though.
>>
>> >
>> >
>> > On Saturday, May 25, 2013 1:39:19 PM UTC+4, Jonathan Ong wrote:
>> >>
>> >> just don't bother publishing it. use github namespaces in npm.
>> >>
>> >> {
>> >>   "dependencies": {
>> >>     "merge": "stagas/merge"
>> >>   }
>> >> }
>> >>
>> >> On Saturday, May 25, 2013 1:34:51 AM UTC-7, Alex Kocharin wrote:
>> >>>
>> >>>
>> >>> RPG name generator could do the job. :)
>> >>>
>> >>> --
>> >>> // alex
>> >>>
>> >>> 25.05.2013, 10:49, "George Stagas" <gst...@gmail.com>:
>> >>> > Hi all,
>> >>> >
>> >>> > I really want to name my modules however I like and be installable
>> >>> > and
>> >>> > require-able.
>> >>> >
>> >>> > For example, I want to write a 'merge' utility, and I don't want to
>> >>> > struggle coming up with a random set of letters because I want my
>> >>> > code
>> >>> > to read require('merge') not require('golalamergifiable').
>> >>> >
>> >>> > What are my options currently? Anyone have any solutions?
>> >>> >
>> >>> > --
>> >>> > --
>> >>> > 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 nod...@googlegroups.com
>> >>> > To unsubscribe from this group, send email to
>> >>> > nodejs+un...@googlegroups.com
>> >>> > For more options, visit this group at
>> >>> > http://groups.google.com/group/nodejs?hl=en?hl=en
>> >>> >
>> >>> > ---
>> >>> > 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 nodejs+un...@googlegroups.com.
>> >>> > For more options, visit https://groups.google.com/groups/opt_out.
>> >
>> > --
>> > --
>> > 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 nod...@googlegroups.com
>> > To unsubscribe from this group, send email to
>> > nodejs+un...@googlegroups.com
>> > For more options, visit this group at
>> > http://groups.google.com/group/nodejs?hl=en?hl=en
>> >
>> > ---
>> > 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 nodejs+un...@googlegroups.com.
>> > For more options, visit https://groups.google.com/groups/opt_out.
>> >
>> >
>
> --
> --
> 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 nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> 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 nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
-- 
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
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 nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to