Can the webpack team help out? webpack-contrib

[TheLarkInn]

Hey there @kevlened, first off: thank you for maintaining and creating this webpack plugin. I'm one of the maintainers of webpack, and on behalf of the team, we'd like to know if you would consider allowing our team to help maintain this plugin?

We have a new GitHub organization called webpack-contrib which hosts a majority of our popular plugins and loaders!

A lot of the immediate benefits include help from the team keeping up with issues, maintenance and more feature collaboration. Let us know your thoughts, we'd love to help!

~ webpack team ~

[kevlened]

I gladly welcome the team to help maintain this plugin! What's the process?

[joshwiens]

@kevlened - There are a few steps, all reasonably simple.

1.) You need to commit the following to the LICENSE. Do not change the license filed in the package.json
2.) NPM Owner access needs to be granted to @bebraw & @d3viant0ne ( We will handle the npm groups after that )

Copyright JS Foundation and other contributors

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
'Software'), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Webapck & Webpack-Contrib are a part of the JavaScript Foundation, hence the license.

3.) Transfer this repository to me (d3viant0ne). Only an Admin or Owner can transfer into an Organization, I will transfer it into webpack-contrib. Given that there is a time window for transfers & I have to accept the transfer, it's usually makes the process go a bit smoother if I know it's coming. I have my DM's open on Twitter, just ping me once the license / NPM change has happened & you have 5 minutes to get it transferred.

From there it is just a matter of maintenance expectations.

1.) Webpack-contrib can take over maintenance if you just don't have the time / desire to anymore.
2.) Webpack-contrib can help you maintain the repo going forward. You will be invited into the Webpack Slack, retain write access to the repository and the webpack-contrib/org-maintainers group works with you.

In either case, once transferred the code base will be refactored to our standard project setup which can be found here. https://github.com/webpack-contrib/webpack-defaults. It's essentially, ES6+ via Babel with Jest as the test running with defaults handling updates across the organization to simplify the maintenance across 50+ libraries.

The defaults upgrade isn't something you need to worry about ( unless you want to ), I will most likely be the one doing the refactoring along with setting up Travis, Appveyor, Codecdov & so on.

A DM on Twitter goes directly to my cell & I am reachable until ~ 02:00 CST on any given day. If you have any questions about anything above, feel free to reach out & i'll be happy to get them answered.

[mikesherov]

@kevlened any progress here?

[mikesherov]

Hooray!