WET Sub Project Leads Meeting Minutes 2013 05 30

français

Title: WET Sub-Project Leads Meeting Minutes - 2013/05/30

Duration: 1:00 pm to 4:00 pm

Attendees:

• @pjackson28
• @masterbee
• @EricDunsworth
• @patheard
• @thomasgohard
• @nschonni
• @cfarquharson
• @andrewnordlund
• @duboisp

Item 1: WET v4.0 sneak peak/brainstorming

@masterbee WET v4.0 presentation

@masterbee presented a quick overview of the new WET v4.0 codebase. Showed us the difference and the improvement of the new CSS grid system. Also it was noted that the plugin would listen to events (DOM and jQuery). He invited us to explore his source code repository or the branch 4.0 of the wet-boew.

@masterbee and @cfarquharson specified that the new grid system would require a separation of the structure and the decoration. So, instead of decorating a cell "span-2" along with a "module" in the same div, they will be in 2 separate div where the decoration will be on the inner div. Also the new grid system will be able to support an infinity of sub grid.

The new approach of the grid would reduce considerably the number of CSS line of code. approx ~400 for the WET 3.1 to approx ~ 120 for the WET 4.0

Decisions:

• Move @masterbee's code to the wet-boew/wet-boew v4.0 branch so others could work on it.
• Divide up work into stream and assign leads.
• Work divided up as follows:
  • Build: @nschonni
  • Core + Loader: @masterbee
  • Plugin/polyfill architecture: @patheard
  • CSS structure: @cfarquharson
  • Presentation CSS: @thomasgohard
  • Quality Assurance: @EricDunsworth
  • Markup + Auto-Generation: @LaurentGoderre
  • Documentation: @jeresiv
  • Migration: @duboisp
• Further planning details: WET v4.0 issue for the details

Action items:

• Leads to identify tasks, timelines and resource requirements.
• Plan pre-CodeFest information sessions to help ramp people up for work on the stream and to prepare them for CodeFest.
• Build a working prototype for CodeFest in August.

Item 2: Versioning

Discussion about whether or not Semantic Versioning is appropriate for WET.

Decisions:

• Pure Semantic Versioning is not appropriate for WET but a more flexible approach based upon Semantic Versioning would be a good fit. New versioning approach

Action items:

• @nschonni to propose a model for a central change log to help inform implementers of breaking changes when skipping over multiple version when updating (e.g., v3.0.2 to v3.1.1)

Item 3: Alternate support channels

Quick discussion on about using StackOverflow for WET-related questions to free up the GitHub issue tracker for actual issues.

Pros:

• Reduces the load and maintenance effort on the issues tracker
• Increases visibility for WET
• Questions and answers can be found through Google searches

Cons:

• Does not permit non-English questions or answers (will be shut down right away)
• StackOverflow participants can at times be harsh and rude to non-technical people which could discourage participation.
• Takes 1500+ reputation points to set up tags (none in attendance had that number of reputation points)

Decisions:

• Can't be a main option because of French not being permitted. Also does not seem possible to set up the necessary tags because of insufficient reputation points.

Action items:

• Search for alternatives to StackOverflow.