Svg.js: npm org and scoping

[Fuzzyma]

For the 3.0 release I would like to create an npm organisiation so that we can prefix all our packages like @svgdotjs/svg.js.
That has several advantages:

• multiple users can be part of an org and can publish packages
• no name clashing with other packages
• every user sees directly which plugin is maintained by us and which not

Having all 3.0 ready plugins published as organisation also makes it easy for the user to know wether a plugin is (already) supported for 3.0.

Opinions? @wout @saivan @dotnetCarpenter

[saivan]

I like it! Are there any downsides?

[saivan]

I'm actually thinking @svgjs is a better organisation name though :P not loving the dot.

[wout]

All good for me. The dot is fine since it reflects the Github repo.

[Fuzzyma]

No downsides (well - the user needs to type more: npm install @svgdotjs/svg.js.

I would also prefer to have npm org and github org names as the same

[Fuzzyma]

Ok - I went ahead and created the @svgdotjs organisation on npm. I have to figure out how all of this works but it doesnt seem to be that hard :)

[saivan]

So this is done, lets close it