français

Title: Web Experience Toolkit project leads meeting (2013/08/29)

Present:

• @pjackson28
• @masterbee
• @EricDunsworth
• @jeresiv
• @chrismajewski
• @patheard
• @rlambert27
• @andrewnordlund
• @sinkinsona
• @duboisp
• @nschonni

Item 1: CodeFest 2013 post-mortem

• Two codesprints in one room is awkward and distracting. Too difficult to focus on tasks. If need to combine in the same room then need a lot more coordination between the codesprint leads in advance.
• Smaller tasks for the codesprints. Difficulty in getting things done.
• Codesprints were too short, needed more time to get started.
• A lot of time was spent getting things setup. Some people came without laptops or the basic configurations needed.
• Would be helpful to have communal laptops or computer rooms (like at IC) so people can still help out when they don't have a laptop of their own.
• Cloud9 (c9.io) was very helpful with collaborative coding.
• Need to get things setup in advance for codesprints. Some of the codesprints were disorganized.
• Ottawa U space was very nice. Tech setup was nice, wi-fi was good.
• Would have been helpful to have the rooms closer to each other.
• Strong preference for printable badge. More professional and easier.
• Have second-days worth of signs to replace the ones that inevitably go missing overnight
• Went much better from last year.
• Print you own badges? Perhaps print at home?
• Presenter computers were initially in French. Needed more instructions on how to switch.
• Should have a scheduled half hour to have a tour of the equipment and brief tutorial so less confusion the day of.
• More rainbow unicorns and other memes in the keynote presentations
  • Comms people were a bit bored with GitHub presentation but more interested in Adobe presentation because of rainbow unicorns and other memes
• Have more schedules posted such as the elevator entrances on each of the floors as well as post in advance online.
• Submitting ideas and descriptions for codesprints and breakout sessions earlier would be helpful.
• Be clearer about how sessions are scheduled.
• Have WET 101 sessions running all day so people who are not prepared for codesprints can be redirected to WET 101 to get up to speed.
• Have video tutorials (e.g., WET 101) that can be viewed in advance to prepare for codesprints. Can also reference existing GitHub video tutorials so can focus on WET in separate videos.
• Perhaps split WET 101 up into sub-sessions so people can go to the parts they need (e.g., WET building, GitHub 101, etc.).

Item 2: WET v4.0 planning

• WET has an IRC (#wet-boew) channel on FreeNode.org
  • https://webchat.freenode.net/ is a Java web client
• New folder structure pushed into v4.0 branch. Now have base, core, plugins and polyfills directories.
• Now will have unminified, minified and source maps for all product lines
• Using Bower for dependency management
• Build can handle both CoffeeScript and JavaScript files (so take your pick)
• Integrated jQuery Mobile touch events and transitions (without the rest of the framework)
• Twitter BootStrap to add Grunt customization making it easy to correct contrast issues without directly altering Twitter Bootstrap source.
• Leveraging CSS3 instead of JavaScript wherever possible to reduce complexity
• Jekyll for documentation with a Prose interface
• More mini-CodeFests/Hackfests coming focused on speeding up and spreading out migration.
• Rudimentatry working examples to be set up and automated and will be more fullsome when themes get integrated
• Using QUnit or Mocha for automated unit testing (still determining which to use, see #800)
• Still looking into automated performance testing solutions
• Issue with Node Sass on Windows binary (old version that needs to be rebuilt to incorporate upstream placeholder bug fix)
• Bower doesn't automatically download new dependencies when they become available. Need to run init to refresh dependencies.