Rename node-xmpp

[sonnyp]

node-xmpp runs in the browser, more transport might be added (Chrome socket API, Web API socket API, WebRTC, ...) while reorganizing the project, maybe it's worth thinking of it?

[dodo]

It still uses the node environment (commonjs requires, npm, and all that). Browserify does the rest of magic.

Also "Chrome socket API, Web API socket API" is already usable through sawrocket (as long as you don't use TLS :/)

[sonnyp]

Ok makes sense.

[sonnyp]

Hey I'm reopening this just to check other contributors opinion.
@dodo you made a good point but still, I think the name is misleading people into thinking this is node only. Also support for io.js kinda make a point too.

[sonnyp]

what about esmpp ?

[smokku]

https://www.npmjs.com/package/xmpp.js is free

[sonnyp]

@smokku IIRC npm forbids . in package name.
Also the availability on the repository is not an issue as we now use the @xmpp scope.

[sonnyp]

(In any case I like the name xmpp.js, simple, concise, explicit)

[astro]

I like the xmpp.js moniker.

[sonnyp]

@astro @smokku if we do rename the project xmpp.js do you think we should publish the xmpp.js package as well? if so how would it differ from our @xmpp scoped packages?

[smokku]

I think we should. To seize the name at least.

xmpp.js package could do nothing - just pull other packages as dependencies.

[smokku]

https://npms.io/search?q=xmpp does not give any hints that one would want @xmpp/client.

xmpp.js with a good description should be clearly visible there.

[sonnyp]

I propose we wait for the rewrite to be stable then rename the project xmpp.js and release 1.0

[sonnyp]

Out of clarity 1.0 will not include BOSH or node-xmpp-server (unless someone is willing to work on this) but I'll work on that later on.

[sonnyp]

#429

a few more fixes, documentation and we'll be ready to rename and hit xmpp.js 1.0.0

[sonnyp]

closing in favor of #434