Discussion for first meeting.

[TheLarkInn]

@webpack/collab-team the initial meeting notes I'll leave for public discussion in this issue. For future ones I'll leave discussions in PR's so people can get notifications.

https://github.com/webpack/meeting-notes/blob/master/2016-06/june-24.md

[Awk34]

In terms of sponsorship, have you looked into Open Collective?

[TheLarkInn]

@Awk34 I am looking into a variety of options. When we have more mature decisions on these options we'll publish this.

[mxstbr]

Fwiw, we're using Open Collective for react-boilerplate and the team behind it is amazing. They helped us out a bunch of times getting everything just the way we wanted it, everything is completely custom and works perfectly.

[TheLarkInn]

@mxstbr Awesome. I will definitely keep that in mind, and will possibly reach out to you for specifics.

[Awk34]

We also use Open Collective for angular-fullstack/generator-angular-fullstack

[TheLarkInn]

@gaearon @gdi2290 as huge representatives of the React and Angular community we'd love some input from you guys on critical blocking issues in your setups, loaders, plugins etc, that need to be addressed to adopt webpack 2.

A lot of webpack's power is derrived by the sum of its parts and we want to support those parts as best as we can.

[gaearon]

Are you only interested in Webpack 2 blockers, or generally frustrating issues with Webpack? I have a couple.

[TheLarkInn]

@gaearon Both. They may be tagged and tracked separately for organizational purposes, both equally important.

[dashed]

Are meeting agendas established in advance? Are these public?

[TheLarkInn]

@dashed the meetings themselves are not public, but the notes created from them will be. We plan to meet once a week and once meeting notes are ready to publish I will create a pull request so that anyone who is watching the repository can track the notes. From there on, questions and clarifications will happen inside the PR instead of an issue.

[gaearon]

This is super frustrating for me: gaearon/react-transform-boilerplate#122. Basically I want a simple workflow:

• If I make a syntax error, I don’t want a hot update. I want a syntax error overlay.
• After I fix the syntax error, I want the hot updates to continue working.
• If I refresh the app while I have the syntax error, I want to see the syntax error overlay right away.

[XVincentX]

I just want to say that it's great you're sharing this with the community! 🚀

[niieani]

I saw that you want to write TypeScript typings - I've recently written some typings for the Webpack configuration file: https://github.com/easy-webpack/core/blob/master/src/webpack.ts. Feel free to use that as a starting point.

[TheLarkInn]

@niieani Would you like to look into creating 2.0 typings for the changes made (IE new plugins, function syntax for config, etc.)

[niieani]

@TheLarkInn what's the function syntax for config? As to your question, unfortunately that sounds like a pretty large undertaking. Perhaps if you make a public call for this, it could be a joint project together with other Webpack & TypeScript users?

[webdesserts]

Will y'all be needing any design/dev help for the upcoming webpack 2.0 site?

[mxstbr]

This guy is a genius, he created http://reactboilerplate.com basically by himself! 👏 @webdesserts

[TheLarkInn]

@TheLarkInn what's the function syntax for config? As to your question, unfortunately that sounds like a pretty large undertaking. Perhaps if you make a public call for this, it could be a joint project together with other Webpack & TypeScript users?

@niieani I will create an issue on webpack/webpack and then we can discuss what needs to be added. I'll make sure to tag you there.

Will y'all be needing any design/dev help for the upcoming webpack 2.0 site?
@webdesserts @mxstbr Im certain we will want assistance with this. My ultimate goal would be to accomplish something like angular.io has (which is a 3rd party company who specialize in this doing the whole docs and website) as a donation in exchange for their branding somewhere on the page. If none of these options work out, then, we would certainly need to plan and architect the doc page ourselves. You can follow webpack/webpack.io to track the website and @bebraw and @jhnns can help give you some direction.