Agenda 20160310
ianbjacobs edited this page Mar 9, 2016
·
9 revisions
Pages 55
- Home
- A Payments Initiation Architecture for the Web
- Agenda 12th November 2015 at 1700 UTC
- Agenda 17th December 2015 at 1700 UTC
- Agenda 19th November 2015 at 1700 UTC
- Agenda 20160107
- Agenda 20160121
- Agenda 20160128
- Agenda 20160204
- Agenda 20160211
- Agenda 20160310
- Agenda 20160317
- Agenda 20160331
- Agenda 20160407
- Agenda 20160414
- Agenda 20160421
- Agenda 20160428
- Agenda 20160505
- Agenda 20160512
- Agenda 20160519
- Agenda 20160526
- Agenda 20160602
- Agenda 20160609
- Agenda 20160616
- Agenda 20160623
- Agenda 3rd December 2015 at 1700 UTC
- Agenda for 3rd March telco
- All in the Browser
- Browser with remote Payment Apps
- Call for Consensus FPWD
- CFC_20140412
- Checkout API
- Components
- DeploymentExamples
- Extensibility_Notes
- F2F Agenda
- How it Works
- How the Working Group works
- Issue Summary
- MagWebinar
- Meetings
- Mobile Platform
- PaymentApp_Notes
- PaymentRequestFAQ
- PMI_Notes
- RegistrationTypes
- Spec_Notes
- Support for multi price and currency
- Synchronizing Github Issues with W3C Mailing Lists
- TPAC 2015 issues list
- Web Payment Deployment Examples
- Web Payments Working Group FTF Meeting (July 2016)
- Web Payments Working Group Plan
- WPWG FTF Feb 2016
- WPWG FTF Feb 2016 Requirements
- Show 40 more pages…
Mailing list archives
Current Work
Issues
Clone this wiki locally
Agenda
-
FPWD update from editors.
- What will the editors seek to do between now and 17 March?
- Suggest people log issues now (but can be done later).
- Concrete text proposals via pull requests welcome at any time.
- Editors will try to incorporate non-controversial pull requests in FPWD.
- Proposed:
- Publish all four specs
- All RECS except for architecture document (NOTE)
- Are the editors looking for proposals for particular topics?
- Other than raising issues, how else can the group help?
- What will the editors seek to do between now and 17 March?
-
Notifications from the spec repo
- For the main WG repo, we mirror GitHub notifications to a W3C mailing list.
- We have not set that up for the spec repo. Should we?
- If so, should we mirror messages to the main group list or a new list just for (all) spec notifications?
- If the latter, should participants opt-in or opt-out? (Which is more convenient?)
-
TPAC 2016 planning
- Plan is to choose dates (Monday/Tuesday or Thursday/Friday) based on our ability to meet with other groups.
- Proposed to try to meet with some subset of these groups: Accessible Platform Architectures, Browser Testing and Tools, Web App Sec, Web Authentication, Internationalization, Privacy IG, Web Security IG.
-
Next meetings (to be confirmed)
- 17 March (for call for consensus)
- 24 March (to finalize decision to go to FPWD)
HEADS-UP ON DAYLIGHT SAVINGS TIME!
- Most of the US and Canada will be moving theirs clocks forward on Sunday, 13 March. This is two weeks earlier than Europe. Most European clocks will move 1 hour forward on Sunday, 27 March.
- In WebEx, our meeting is specified in US Eastern. This means that on 17 March and 24 March people joining the meeting some people outside the US will need to join the call 1 hour earlier.
More Meeting logistics