jQuery Mobile Team Meeting – Oct 17 2013

  • Attending: Jasper de Groot, Gabriel Schulhof, Alexander Schmitz, Anne-Gaelle Colom, Ghislain Seguin

Time: 2pm ET

link Official Agenda:

  • 1.4 RC release
    • open tickets 1.4
  • 1.4 final status
    • Demos
      • new homepage (Jasper)
      • open tickets for new demos
    • API docs
      • make overview of what needs to be done (Alex)
    • ThemeRoller
      • Jasper working on updating for 1.4
    • Download Builder
      • Alex will look into why it doesn’t work with 1.4
    • upgrade guide
      • Jasper will finish this before final release
    • supported platforms
      • add new list on new web site (Jasper)
    • changelog
      • Alex made a script for auto generating complete changelog
    • new web site (Jasper)
    • blog post (Jasper)
  • new PR’s
    • those can wait until we are done with 1.4

link Updates:

link Jasper de Groot

  • worked on updating demos and new global nav and search
  • made some changes in default theme, based on suggestions from Todd
  • working on updating TR

link Alexander Schmitz

  • triage
  • bug fixes
  • update demos search
  • update jqm-demos.js
  • accessibility summit
  • continuing work on button
  • continuing work on classes option
  • will be working with ui on making some boiler plate for issues and pr’s and standards on how long to keep open as well as a PR checklist

link Gabriel Schulhof

  • Bug fixing
  • API docs
  • New job (from Intel): also working on Cordova (making the cordova workflow work on Tizen)

link Ghislain Seguin

  • No update

link Anne-Gaelle Colom

  • No update

jQuery UI Team Meeting – Oct 16 2013

  • AMD
  • download builder
    • Fixed bug in cache module, fixing that should prevent further service outage
    • Also fixed client-side theme URL handling
  • Accessibility
  • Button
  • Dialog
    • Jörn submitted another bug fix PR, needs help with unit tests
  • Selectmenu
    • Felix waiting on feedback on width option and a fix from Kris
    • Alex and TJ to review width option, Felix to include it on the wiki page
  • Ticket triage
    • 0 pending tickets -3
    • 377 tickets total +1
    • 56 pull requests +5
  • PR triage
    • Need one or two people to review new PRs
    • TJ and Mike to do a bash and keep up with new PRs.
    • Check for: CLA signature; ticket; unit tests, coding standards, commit message standards.
    • One of them to document these, until we can get it all automated. Rewrite contribute.md, get all the details on the contribute site.
    • Alex to help as well and sync guidelines for Mobile
  • Documenting return values
    • Done, just needs to be deployed
    • Jörn to help with deployment, once TJ tested Scott's commits locally
  • Classes Option
  • Effects Rewrite
    • https://github.com/jquery/jquery-ui/pull/1017
    • Corey? Scott?
    • Mike asked for review, still pending.
    • Otherwise, two issues: 1. failing tests (which I think are faulty tests), 2. one of the effects actually needs to modify layout, so that one should use placeholder, but the placeholder should shrink accordingly
  • CLDR
    • Unit tests migrated to QUnit, working with AMD, running with Grunt
    • Now to finish datetime/format
    • Rafael to test date formatting/parsing with datepicker rewrite; number formatting/parsing with spinner
  • Datepicker
    • TJ working on fixing multi-month next
    • Fill out the options list on the wiki. Make suggestions, at least write down the questions we need to answer.
    • Alex to test the rewrite on mobile and report issues. Inline datepicker seems like the wrong solution.
    • Update $.date to remove the jQuery dependency.

jQuery Mobile Team Meeting – Oct 10 2013

  • Attending: Jasper de Groot, Gabriel Schulhof, Alexander Schmitz, Anne-Gaelle Colom

Time: 2pm ET

link Official Agenda:

  • RC
  • PR’s
  • Samsung guys have offered to implement widgets, initially in web-ui-fw for possible adoption later. Any ideas what widgets they should be?

link Updates:

link Jasper de Groot

  • Have been working on:
    • Updating demos and API docs
    • New global nav and custom CSS for demos (branch demos-nav)
    • finishing Upgrade Guide
    • ThemeRoller update
    • Triage
  • Next week:
    • ThemeRoller update
    • new web site

link Alexander Schmitz

  • Prototyping and meetings on new shared button widget
    • combines the best of both ui and mobile buttons
    • css only layer for 90% of cases
    • widget really only for dynamic icons
    • may end up including checkboxradio and controlgroup in some form
  • Bug fixes
  • Triage
  • Some demos updates
    • removing global nav
    • working on demo to do nested listviews as dynamic pages
  • Accessibility summit with deque systems

link Gabriel Schulhof

  • Fixing bugs
    • Made pre-rendering work for columntoggle table
    • Stop generating two back buttons on toolbars - why is _setOptions (which adds the back button) called twice?
  • Working on API docs
    • Added script to systematically change core and mobile versions in examples/entries2html.xsl
    • Added pre-rendered example to popup

link Anne-Gaelle Colom

  • No update… been ill all week :-(

Testing Team Meeting – Oct 10 2013

Location: #jquery-meeting on Freenode

Attending: Timo, James, Jörn

link QUnit

  • Timo working on source split, will rebase assert work on top of that. In the future, a build step is necessary, as in jQuery Core
  • Provide “grunt watch” to quickly rebuild “dist/qunit.js”, which unit tests will reference

link TestSwarm

link Testing infrastructure

  • Timo updated TestSwarm browsers: Firefox 21/22 to 23/24, added Opera 15, added iPad w/ iOS 5.1 and iPhone w/ iOS 6.0

jQuery UI Team Meeting – Oct 09 2013

jQuery Core Team Meeting – Oct 07 2013

Attending: jaubourg, timmywil, rwaldron, davemethvin, gibson042, m_gol (slightly afk)

link jQuery 1.11/2.1 beta 2 TODOs

##jQuery Migrate

link How to solve the problem of people not installing Bower/Grunt?

  • https://github.com/jquery/jquery/pull/1393
  • Keeping instructions means only non-README people get local copies
  • What does Bower want to do in this case?
    • ask danheberden he can tell us
  • In the meantime, land Scott's big WARNING message (timmywil)

link Sourcemaps

  • Dave tried to start discussion, seem to have fizzled
  • Is the Chrome fix (no 404) sufficient? Now it silently doesn't work?
  • http://bugs.jquery.com/ticket/14415
  • Dave to bug paul_irish
  • m_gol to start a Google Doc with (another) summary

link jQuery 1.11/2.1 final

  • How do we publish to npm?
  • How do we publish to bower?
  • Need to update build script to create tagged headless commit for release
  • Should include bower deps and built file for simplicity
  • Timmy to update the release script

jQuery Mobile Team Meeting – Oct 03 2013

  • Attending: Jasper de Groot, Alexander Schmitz, Anne-Gaelle Colom, Todd Parker

Time: 2pm ET

link Official Agenda:

link Updates:

link Jasper de Groot

  • triage
  • worked on updating demos
  • fixed issues with checkbox, radio and custom multiple select icon and state classes
  • looked into https://github.com/jquery/jquery-mobile/issues/6349 (fixed toolbars disappear after opening a panel on WP8) but it looks like we can’t fix
  • looking at some tweaks for new default theme
  • will work on ThemeRoller update after I posted the upgrade guide

link Anne-Gaelle Colom

  • added wijmo to the resources page (both current and on jquerymobile.com)
  • added changelogs (1.4.0 beta1 and 1.4.0 alpha 2)

jQuery UI Team Meeting – Oct 02 2013

  • Dialog
    • Jörn is working through open tickets
    • Switched back to z-index shuffling
    • Scott to start discussion about different focus handling in ARIA and HTML5
  • Selectmenu
    • Working on remaining TODOs
  • Ticket triage
    • 4 pending tickets -0
    • 373 tickets total -4
    • 50 pull requests +1
  • CLDR

jQuery Core Team Meeting – Sep 30 2013

Attending: gnarf, mikesherov, markelog, m_gol, gibson042

link jQuery 1.11/2.1 beta 2

link Automatically find prefixed event names?

link jQuery Migrate

  • Look into unit test failures - dave
  • Time for another release, maybe timed with 1.11/2.1?

link Sourcemaps

  • Dave to come up with a list of issues regarding them for discussion with the browser devs

link "Inconclusive" test results?

  • extend qunit to have tests with flags indicating whether we expect them to fail in this platform (or should be skipped without trying)
  • don't litter checks in the unit test code? (centralize somehow)
  • put on the back burner unless someone wants to adopt this

link jQuery 1.11/2.1 final

  • How do we publish to npm?
  • How do we publish to bower?
  • Need to update build script to create tagged headless commit for release
  • Should include bower deps and built file for simplicity

Testing Team Meeting – Sep 26 2013

Location: #jquery-meeting on Freenode

Attending: James, Michał, Oleg, Jörn

link Availability

  • Jörn busy with lots of other projects, mostly jQuery UI, still working on esformatter
  • James to ramp back up in October, go back to finishing node compat
  • Timo busy with events and school, going to ramp up in October back to ~ 10h/week.

link QUnit

  • Discussion about setup/teardown logging callbacks, triggered by this PR: https://github.com/jquery/qunit/pull/471
    • We at least agree on adding a Per-test setup/teardown, defined at the page level
    • Maybe a Per-module setup/teardown, defined at the module level, for something like this
    • Syntax idea: Using QUnit.module( .. ).on(‘setup’, fn).on(‘teardown’, fn); ( or QUnit.module( .. ).on( { setup: fn, teardown: fn })
  • Maybe have Assertion, Test and Module all be EventEmitter (instead of just QUnit) and propagate from the lower-level objects to the higher ones (re-using the event name and data parameters)
  • node compat
    • James to pick up on in October
  • QUnit.Assertion and QUnit.on
    • Timo to pick up again in October

link TestSwarm

link Testing infrastructure

  • Need to add iOS 5.1, 6.1 & 7.0 for Core builds (or whatever BrowserStack can provide that’s close enough)
    • iPad 3rd 5.1, iPhone 5 6.0
  • Add a separate run for Android 2.3, for manual runs, since the Android runs are very slow
  • Looked at preview of BrowserSwarm, which runs QUnit tests through SauceLabs, has better output than grunt-saucelabs, but works more like TestSwarm
  • Timo to prototype a grunt-qunit-saucelabs plugin that makes use of SauceLabs new support for running unit tests