Skip to content

Latest commit

 

History

History
51 lines (36 loc) · 2.33 KB

june-24.md

File metadata and controls

51 lines (36 loc) · 2.33 KB

June 24 (discuss)

Attendees

Agenda

Discussed Roadmap

  • Most important feature is documentation for Webpack 2.0.
  • There is a lot of great overlap with SurviveJs Book and Juho mentioned his willingness to take the lead on documentation.
  • Agreed that the Roadmap documentation should reflect bugs which have been fixed, as well as bugs that still are critical blocking for 2.0

2.0 Documentation.

  • New Repo (and new page? webpack.io? (looks like domain grabber owns it))
  • Sean mentioned that the angular team uses a 3rd party for angular.io, and potentially we could investigate the same thing. (Maybe even a team willing to put out their brand on our page if they did it or a portion or all for free).

Tobias added a new AgressiveSplittingPlugin for webpack 2.0

  • Support HTTP2 caching level 4

Bounty Sourcing / Sponsorship

  • Sean mentioned that he is in communication with parties who are investigating the possibility of sponsorship or ‘helping’ in some way. He will find out more information on this today for next meeting.

Weekly Meetings

  • Everyone agreed that meeting weekly to continue transparency.
  • Meeting notes will be published to webpack/meeting notes.
  • Next meeting slated for Jun. 29th 2016

Takeaways

  • Look into finding a team for documentation (Juho)
  • Continue looking for Support/Sponsors for Webpack (Sean)
  • Update Roadmap to reflect where we are (Sean)
    • Inform on Breaking Changes (Johannes)
    • Work on Standardized Ts loaders/plugins (Sean)
    • WP 2.0 Typings (Sean)
  • Keep Close Communication with Loader and Plugin Authors (Johannes/Sean)
    • Create Chat for communication on gitter? (Sean/Tobias) Loader Authors
    • Get List of Webpack loaders and plugins that need maintainers (Tobias)
  • Talk about Issue Tracking for Github Webpack Next Week.
  • Work with Webpack users to get a list of common questions. We’ll leave top 3 with answers in notes (Sean).

Please feel free to discuss these notes in the corresponding issue.