[TSC]: create an npm organization

[bjohansebas]

To make access to the packages easier, we should have an npm organization. With this, TSC members would be owners and could manage access to the packages more easily

Having an organization does not mean that packages must change their names to adopt a scoped name (i.e., @webpack/package-name), they can continue to be published under the same names they use today.

[evenstensberg]

This will be a lot of work to standardize. So we need to discuss this more

[evenstensberg]

Status: Filed document to npm to get ownership.

[alexander-akait]

@evenstensberg @bjohansebas

I added almost all packages, except (due permissions):

• webpack-bundle-analyzer (@valscion Can you add me as an owner to webpack-bundle-analyzer npm and also please provide the link to your profile) Done
• css-loader (@sokra @jhnns need to more permissions in npm to add this package to our npm org)
• mini-css-extract-plugin (@sokra @jhnns need to more permissions in npm to add this package to our npm org)
• thread-loader (@sokra @jhnns need to more permissions in npm to add this package to our npm org)

Also invited all core developers + @evenstensberg (in case of emergency)

[alexander-akait]

@valscion Friendly ping

[valscion]

Sure, I'll add you as an owner but I hope you'll still let me decide when to release new versions of webpack-bundle-analyzer as long as the delays are not too severe or you don't hear from me for a while. My npm profile is in https://www.npmjs.com/~valscion

[alexander-akait]

@valscion invited your to webpack-bundle-analyzer team

[evenstensberg]

@alexander-akait close if finished