jQuery Mobile Team Meeting – Nov 13 2014

  • Ticket Triage:
    • 254 tickets -10
    • 32 pull requests +3

link 1.4.5

link 1.5.0

  • all updates from ui pulled in
    • tests need fixing started by gabriel, cgack taking over
  • Classes
    • PRs need updating - in progress
  • Declarative Widgets Module
    • no update
  • Table
    • no update
  • Navbar
    • pr has been updated
  • Toolbar
  • CSS update (button, checkboxradio, controlgroup)
  • Accordion
    • from ui will replace collapsible/set has been pulled in
    • Sarah Frisk will be working on new css
  • Checkboxradio as well as button and controlgroup
    • waiting for ui updates, hopefully can be done next week

link Other topics

  • jsbin
    • 2 options will work on new template hoping for vanity urls
      • Have talked to remy we will be getting something along the lines of jquerymobile.jsbin.com
  • website spider
    • grunt-spider plugin coming
      • still working on it very slow
  • Pointer Events
    • call today went well
  • CSS Framework
  • Google Summer of Code
    • Anyone interested in being a mentor?
    • Alex agreed to be a mentor

Project Leads Meeting – Nov 12 2014

Attending: Dave, Jörn, Alex, Scott, Kris, Rafael, Sarah

link Core

  • Working towards 3.0
  • Need roadmap … it will be simple
  • Need some new blog posts about changes coming

link UI

  • Working toward 1.12.0

link Mobile

  • 1.5 work continues

link Modules

link Globalize

  • New members on javascript-globalization@googlegroups.com: Cameron from Twitter (maintainer of twitter-cldr), Edwin (globalization architect) from LG, Bruno and Daniel (globalization managers) from Microsoft, Eirik (globalization director) from Oracle, Xiang (senior developer) from Paypal.
  • JavaScript Globalization overview page had additions from Yahoo (format.js), Google (Closure i18n), Wikipedia (jquery.i18n) and LG (iLib).
  • ICU Message Format Support waiting approval to use slexaxton/messageformat.js license.

link CSS Framework

  • Should we support IE8? How about Android 2.x?
  • General feeling: No IE8 support

link QUnit

link Testing

  • BrowserStack had unrelated “hacking” issues (very thorough post mortem!), hopefully will have time to address Travis integration issue soon

link Infrastructure

  • jsbin - talking with Remy about using it for demos and default template
  • Alex to intro Kris and Remy, we'll get 10 accounts w templates ($1000)

link 2015

  • Kris to create a summary of roadmaps to share with the board, Core roadmap still missing. Also budget requests from dev rel and infrastructure.

jQuery UI Team Meeting – Nov 12 2014

jQuery Mobile Team Meeting – Nov 06 2014

  • Ticket Triage:
    • 264 tickets +0
    • 29 pull requests +0

link 1.4.5

  • DONE!
    • 1 minor regression

link 1.5.0

  • all updates from ui pulled in
    • Again
  • Classes
    • PRs need updating - in progress
  • Declarative Widgets Module
    • pr was delayed by classes updates
  • Table
    • no update
  • Navbar
    • waiting on merger from new pr
  • Toolbar
  • CSS update (button, checkboxradio, controlgroup)
    • no update
  • Accordion
    • from ui will replace collapsible/set has been pulled in
    • Sarah Frisk will be working on new css
  • Checkboxradio as well as button and controlgroup
    • waiting for ui updates, hopefully can be done next week

link Other topics

jQuery Core Team Meeting – Nov 03 2014

Attending: DaveMethvin, markelog, timmywil

link Additional issue tracker things

  • wontfix? (done)
  • cantfix?
  • needs review (team needs to review the issue/PR) (done)
  • I don't think we want "fixed" or "notabug", too noisy and not particularly useful to search
  • "valid and fixed" issues should be assigned to a milestone, be sure they are when committing code that closes an issue
  • Always set a milestone when assigning an issue, and always assign the issue before closing with a fix/patch
  • Always create an issue for a PR, so the issues have a complete list of the problems solved

link Branch naming still needs to be done

link Issues and PRs in the 3.0 milestone

link $.xhr -- replaced by $.fetch

  • Let's do this as a plugin with its own schedule

link Issues and Pull Requests

  • Assign milestones to all issues

jQuery Mobile Team Meeting – Oct 30 2014

  • Ticket Triage:
    • 264 tickets -87
    • 29 pull requests -19

link 1.4.5

  • lets get this done
    • will review all 1.4.5 prs this afternoon

link 1.5.0

  • all updates from ui pulled in
  • Classes
    • PRs need updating - in progress
    • everything updated from ui again
  • Declarative Widgets Module
    • pr was delayed by classes updates
  • Table
    • no update
  • Navbar
    • waiting on merger from new pr
  • Toolbar
  • CSS update (button, checkboxradio, controlgroup)
    • no update
  • Accordion
    • from ui will replace collapsible/set has been pulled in
    • Sarah Frisk will be working on new css
  • Checkboxradio as well as button and controlgroup
    • waiting for ui updates, hopefully can be done next week

link Other topics

  • jsbin
    • 2 options will work on new template hoping for vanity urls
      • Have talked to remy we will be getting something along the lines of jquerymobile.jsbin.com
  • website spider
    • grunt-spider plugin coming
      • still working on it very slow
  • CSS

Project Leads Meeting – Oct 29 2014

Attending: Dave, Jörn, Alex, Adam, Scott, Kris, Rafael

link Core

  • Publishing the jQuery 3.0 blog post today
  • Starting to knock down the issue/PR backlog

link UI

  • Nothing interesting

link Mobile

  • Releasing 1.4.5 tomorrow
  • 1.5 work continues
    • continuing update loop with ui
    • Front-end dependency management
  • What would we want npm to support to make publishing UI on npm useful?
    • To release on npm, would need dozens of different packages, one for each widget, each with its own dependency tree
    • Difficult to find/build the actual files, which are inside node_modules
  • Possible solution: If requireJS could find modules loaded by npm inside the node_modules directory, that would fix this?
  • Talk to James Burke about how to deal with this? -- dave

link Globalize

link CSS Framework

  • There was a meeting yesterday. Minutes will be sent out later by Scott
  • Open up our css-framework repo, after some cleanup, to collaborate with the group there.
    • Alex to ask Sarah to update the readme

link QUnit

  • No update, Leo and James currently unavailable. Jörn will look into remaining 1.16 issues.

link Testing

  • Some improvements for browserstack-runner landed, still trying to get it working in Travis builds and with requirejs

link Infrastructure

  • jsbin - talking with Remy about using it for demos and default template

link 2015

  • High level roadmaps with goals for 2015 for your project
  • Budget requests to achieve those goals
    • including contracts, additional resources

jQuery Core Team Meeting – Oct 27 2014

Attending: timmywil, DaveMethvin, gibson042, m_gol

link Trac issues migrated

link Branch naming

  • "compat-only" and "master-only" for issues applying to just one -- done
  • rename "1.x-master" to "compat"
  • also change name in package.json - “jquery-compat”
  • Both versions need package.json rename to 3.0.0-pre
  • land PRs before renaming

link Promises/A+ compat

link $.xhr -- replaced by $.fetch

  • Should this start as a plugin? Yes

link Publish 3.0 blogpost

  • Dave to do this week

link Browser support for 3.0.0

  • Drop official support for Opera 12 and Safari 5.1
  • Keep IE9 in the master branch
  • Support Android 2.x on both (dammit)

link Additional things to reconsider as of 3.0?

  • remove deprecated stuff like andSelf
  • fractional width/height?

link Testing

  • Continue to test Opera (latest, latest-1), but on the weekly job
  • We could test Yandex browser there if it's on browserstack
  • Let's switch to private browser sets (m_gol)
    • jquery and jquery-periodic
    • jquery-compat and jquery-compat-periodic

link Issues and Pull Requests

  • Assign milestones to all issues
  • https://github.com/jquery/jquery/issues/1784
  • Shadow DOM is a pain
    • Is this something jQuery should try to fix?
    • code size and performance implications could be big
    • dave to get some input from Polymer or web standards groups on whether this is reasonable to do, and if so what devs (and jQuery) should be doing to make this work without horrible perf

link Roadmap wiki page?

  • Collect all features/enhancements for feedback