Meeting Proposal 20161128
Pages 89
- Home
- A Payments Initiation Architecture for the Web
- Adoption2017
- 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 20160728
- Agenda 20160804
- Agenda 20160811
- Agenda 20160818
- Agenda 20160825
- Agenda 20160901
- Agenda 20160908
- Agenda 20160915
- Agenda 20161006
- Agenda 20161020
- Agenda 20161027
- Agenda 20161103
- Agenda 20161110
- Agenda 20161117
- Agenda 20161201
- Agenda 20161208
- Agenda 20161215
- Agenda 20170105
- Agenda 20170112
- Agenda 20170119
- Agenda 20170126
- Agenda 20170202
- Agenda 20170209
- Agenda 20170216
- Agenda 20170223
- Agenda 20170302
- 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
- FTF March2017
- FTF Sep2016
- How it Works
- How the Working Group works
- Issue Summary
- MagWebinar
- Meeting Proposal 20161128
- Meetings
- Mobile Platform
- Networks List
- PaymentApp_Notes
- PaymentRequestFAQ
- PMI_Notes
- Proposed F2F Day 2 agenda
- RegistrationTypes
- Security and Privacy Considerations
- Spec_Notes
- Support for multi price and currency
- Synchronizing Github Issues with W3C Mailing Lists
- TestSuite
- 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 74 more pages…
Mailing list archives
Issues
- General
- Payment Request API
- Payment Method Identifiers
- Basic Card Payment
- Payment Apps API
- HTTP API and Messages
Tests
Adoption
Previous Topics
Clone this wiki locally
Proposal for WPWG Teleconferences
Background
Currently, the WPWG conducts most of its work asynchronously via GitHub and email.
The WPWG also holds a weekly teleconference and meets FTF 3-4 times per year. Task forces within the WPWG also meet periodically by phone as needed. While many of us value these teleconferences, some people cannot attend because of the time zone or schedule conflicts.
In addition, the current agenda of the Working Group is technical (rather than direction setting or high level requirements) and so the group's agenda --especially on calls-- is not conducive to contributions from participants who are not intimately following the group's technical discussion.
The WPWG has considered in the past holding two meetings, alternating weekly at different times, to 'distribute the pain.' In the end, however, participants expressed a preference for holding a single meeting.
This is a new proposal that attempts to foster participation and contributions in teleconferences.
Proposal
- We maintain the currently weekly call, Thursdays at 10am ET
- In addition, we organize a 1-hour call every three weeks at 9:00 UTC (11am Cape Town, 5pm Beijing, 6pm Tokyo and Seoul, 8pm Melbourne). We don't yet know the preferred day of the week of the group. Both chairs (and we hope one team contact) would be present at this meeting. This call would have equal standing with the Thursday call. Please note that, per the Working Group Charter, that decisions taken during a call are provisional, allowing others to comment asynchronously or at a subsequent call.
- In addition, we organize a non-technical meeting every two months where we summarize recent discussions, gather requirement-level feedback and questions, and discuss topics such as communications, strategies to encourage adoption of the standard, industry awareness and participation, etc.
- Task forces continue to organize teleconferences as needed.