Agenda 20160414

• CFC Update (Chairs)
  • Decision
  • Schedule
• Publishing after FPWD
  • Finer grain updates possible after FPWD; based on large changes (with WG decisions) and small ones (editorial, bug fixes).
    • Non-editors that wish to make concrete change proposals needs to fork the spec repo.
    • Participants who cannot do this (e.g., due to company network policy) please contact the chairs.
  • Decision process
    • Example: Where there is consensus on substantive proposals and issues and proposals (expressed via GitHub and email), allow Editors to incorporate proposals into the Editors' Drafts without further WG decision. Where there is not consensus, organize group discussion and decision. For editorial and bug fixes, allow Editors to make changes in the Editor's Drafts.
    • Because Editors Drafts thus reflect consensus, allow editors to update TR drafts automatically on merge
  • PROPOSAL TO THE GROUP:
    • The WPWG will use the auto-publish mechanism
    • Adopt decision policy above (Editors can merge proposals with consensus + editorial; others discussed before decision)
    • Adopt publish-TR-on-merge policy.
    • Create a twitter account to build community around the specs (and inform them of key publications)
• Overview of extensibility topics
  • Goals (after discussion)
    • Capture all the extensibility topics the WG cares about, and get shared understanding of how they relate
    • Reach consensus on requirements to guide specification development
• Consensus to publish FAQ with FPWD?
• Face-to-face meeting update

If time:

• Issue discussion (AHB)
  • PR #133, which merges PaymentRequest params.
  • Transaction types (issue 19)
  • Spec organization: mediator, payment app
• Encouraging contributions (Ian)
  • GitHub intro?
  • WebIDL intro?
  • Monthly summary (new/closed issues, important decisions, upcoming meetings)?

NEXT WEEK:

• Decisions to take up ** HTTP API proposal ** Payment App Registration proposal ** SEPA Payment Method Spec proposal