PEP Team Meeting – Mar 05 2015

  • New Intern PR from Colin
    • https://github.com/jquery/PEP/pull/167
    • Fixes bad test completion
    • Adds Travis CI support using BrowserStack to launch browsers
    • Shows some failing tests
    • Should add a method for spawning the browsers locally without specifying BrowserStack credentials
      • Can use grunt-selenium-server or we can write a tunnel for Dig Dug
      • Scott and Alex to work on a Dig Dug tunnrl
  • Release script
    • Scott has started working on this
    • We need a different name than PEP for publishing to npm
      • Should make sure the name is available on Bower as well
      • pepjs suggested, not too much interest in any name
    • Should we automate updating gh-pages or keep that manual?
      • Automate copying samples

PEP Team Meeting – Feb 26 2015

PEP Team Meeting – Feb 12 2015

  • ES6 modules are in master
  • Added some people to jquery-devs-team
    • Still waiting on CLA signatures from many of the team members
  • Perhaps we need a more formal commitment to determine who actually intends to be a team member and who is just interested in following progress
    • Scott to create an issue asking everyone to say how they’re interested in helping with PEP, then send an email to everyone who has expressed interest so far pointing them to the issue
  • Still waiting on updated PR from Jacques for Intern testing
  • No objections so far for using jquery-release, so we’ll go with that
  • No update on formal objection to spec
  • Would like to test PEP against the W3C spec tests
    • Mostly manual tests, might be able to automate with Intern
    • Jacob might be able to run them in Microsoft’s lab using touch automation
  • We should have a logo

PEP Team Meeting – Feb 05 2015

  • Using ES6 modules for source
  • Using Intern for testing
    • Issue #153
    • PR #158
    • Will redo on top of the ES6 change after that's merged
    • Remove with, use tdd properties directly or create local aliases
  • Release process
    • Create distributable files and commit in a detached head for the tag
    • Publish to Bower
    • Update samples in gh-pages
    • Use jquery-release if there are no objections
  • jquery-devs-team mailing list
    • Used for cross-project discussion for jQuery Foundation
    • Also controls who has write access to the agendas
    • Scott will add PEP team members
  • Formal objection was raised against advancing Pointer Events spec to Recommendation

PEP Team Meeting – Jan 12 2015

  • Testing
    • Currently using Mocha and Chai
    • Adopt Intern
      • Provides non-simulated events through Webdriver API
      • Compatible with Chai
    • Colin available to answer any questions about Intern and assist with implementation.
    • Jacques to work on initial implementation.
    • Would be nice to run W3C tests, but they require user interaction.
      • Can manually run them on occasion to verify proper functionality.Nom
      • Can skip anything that involves capabilities that a device doesn’t have, like multi touch on IE8
  • Browser support (overlaps with testing)
    • Adopt baseline from jQuery UI/Mobile? Currently means IE8+
    • Or stick with IE9+, provide hooks to implement IE8 support elsewhere, probably using jQuery events
    • Need to at least test that the polyfill doesn’t crash IE8
    • Need to automate tests with the jQuery wrapper in IE8, to verify the hooks actually work
  • Project Lead
    • Volunteers or nominations?
    • Nominations for Scott
      • Scott willing to accept, but is happy to have someone take over at any point
  • Scott replaced Polymer loader
    • Less crazy now, but should probably use a real build system
    • Go for AMD with r.js, instead of just concatenating files
    • Single entry point that includes everything in the correct order
  • Schedule for future meetings
    • Weekly, reduce later if there’s not enough to discuss
    • Scott to send another Doodle
    • Fall back to today’s time if we can’t find something else
    • Create Freenode channel: #pep
      • Move notifications from #jqueryui-dev to #pep
      • Add to CONTRIBUTING.md
    • 10 minutes for planning, 50 minutes for venting
  • Adoption
    • Planned
      • Dojo 2
      • jQuery UI
      • Intel App Framework (eventually)
    • Replace IBM’s dpointer?
      • Was supposed to go into Dojo 2
      • IBM will discuss internally
      • Requires support for AMD and IE9 (from last meeting)
    • Talk to about adoption:
      • Wikipedia
      • WordPress
    • MS Open Tech will promote it and contribute code, no immediate plans for using it
  • Misc.
    • Rename repo to PEP
  • Touch action