2013/5/28 Isaac Schlueter i...@izs.me:
How many disputes do you receive per month?
Usually less than 2 per month. But I have no way of knowing how often
authors talk amongst themselves if they already have some sort of
relationship.
Is there a mailing list or something where I can see
At the risk of making things worse, I don't think this is that bad George.
I think the responses you've gotten here have been pretty much in line with
what you asked. You got a little negativity, but not a lot. And it was good
for you to expand on your ideas because your initial message didn't
I apologize for adding to the drama, but after reading your comments I
still legitimately believed that what you were arguing towards was muddying
the water between single namespace npm and dual namespace GitHub (whether
through the discovery and search system or the storage is less
consequential
Thanks guys, I think the point has been made and I appreciate your
last comments. I think I reacted a bit aggressively at some points and
sounded trollish now that I read back so your responses might have not
been entirely without basis so I apologize as well. My faith in
humanity is restored.
In the earlier days of node, when isaac and i were first putting up the
registry, we did think about the problems that come with a single global
namespace. In the end it was still a better decision to go with a single global
namespace for the following reasons.
1. Manufactured Scarcity. The
and another person had another fork named the same thing
I hate the fact that when you fork something in github it inherits the same
name, same readme, etc. Many times I thought I had found the origin of a
project because I didn't notice the fine print. And, for some reason
google will
On May 27, 2013, at 03:27, George Stagas wrote:
Good to know about your thoroughly explained arguments but nobody's
suggesting npm or the npm registry namespacing to change. Learn to
read.
My enjoyment in reading the discussions in this group is increased when the
conversation remains
How many disputes do you receive per month?
Usually less than 2 per month. But I have no way of knowing how often
authors talk amongst themselves if they already have some sort of
relationship.
Is there a mailing list or something where I can see ownership changes and
reasons for such
[image: Inline image 1]
On Mon, May 27, 2013 at 3:52 PM, Isaac Schlueter i...@izs.me wrote:
How many disputes do you receive per month?
Usually less than 2 per month. But I have no way of knowing how often
authors talk amongst themselves if they already have some sort of
relationship.
2013/5/26 Marco Rogers marco.rog...@gmail.com:
It's not clear from this thread what you want exactly. You want to name your
modules whatever you want, not use namespaces, have them on npm, and also
avoid name collision? How exactly do you see that working?
:Marco
I'm sorry, we lost it
2013/5/26 George Stagas gsta...@gmail.com:
2013/5/26 Marco Rogers marco.rog...@gmail.com:
It's not clear from this thread what you want exactly. You want to name your
modules whatever you want, not use namespaces, have them on npm, and also
avoid name collision? How exactly do you see that
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
RPG name generator could do the job. :)
--
// alex
25.05.2013, 10:49, George Stagas gsta...@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
With project-local node_modules directories, this kind of name
collisions should not be an issue.
--
Göktuğ Kayaalp goktug.kaya...@gmail.com
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this
2013/5/25 Jonathan Ong jonathanrichard...@gmail.com:
just don't bother publishing it. use github namespaces in npm.
{
dependencies: {
merge: stagas/merge
}
}
It seems to work, but then, there's the issue of discoverability. It's
a double edged sword now, either obscure naming and
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.
2013/5/25 Alex Kocharin a...@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
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
It's not clear from this thread what you want exactly. You want to name
your modules whatever you want, not use namespaces, have them on npm, and
also avoid name collision? How exactly do you see that working?
:Marco
On Saturday, May 25, 2013 11:06:28 AM UTC-7, stagas wrote:
2013/5/25 Alex
19 matches
Mail list logo
