You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Meeting Date & Time

  •  
    • NA/EU 07:00-8:00 PT / 14:00-15:00 UTC 
    • APAC 18:00-19:00 PT / 01:00-02:00 UTC <== NOTE THE NEW TIME!!!

Zoom Meeting Links / Recordings

Attendees

Main Goal of this Meeting

1) Review use case / test case proposals from Allan Thomson, 2) check on progress of the spec, 3) discuss whether we can start using GitHub issues together with the current Google doc of the spec.

Agenda Items and Notes (including all relevant links)

TimeAgenda ItemLeadNotes
3 min
  • Start recording
  • Welcome & antitrust notice
  • Introduction of new members
  • Agenda review
Chairs
  • Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.
  • New Members:
    • Sid Haniff — solution architect in travel, finance, and online banking. Joined ToIP as a Contributor Member. 
    • Thomas Shelton — working with Northern Block.
5 minAnnouncementsAllUpdates of general interest to TATF members.
2 minReview of previous action itemsChairs
  • ACTION: Neil Thomson will consolidate the terms being defined for purposes of this spec into a glossary at the end of the spec. Available for comment/suggest @ TATF Spec - Working Glossary
  • ACTION: Drummond Reed will work with the Concepts and Terminology WG members to set up a terms wiki for the Technology Stack WG that we can begin using immediately with this spec.
  • ACTION: Drummond Reed to add two items to next week's agenda: 1) Allan Thomson presenting on use cases, 2) Moving the spec from Google docs to GitHub.
30 minProposed use / test casesAllan Thomson

Review a proposal from Allan.

  • --
5 minsUpdate on spec progressWenjing ChuCheck-in on progress on the ToIP Technical Architecture Spec - Working Draft.
10 minsStart using GitHub issues?All

It has been suggested we start using GitHub to either edit the spec in Markdown. However Darrell O'Donnell (among others) feels the spec is still incomplete enough that Google docs is a much more user-friendly editing platform until the document is closer to completion. However an intermediate step would be to start using GitHub issues to discuss issues that are flagged in the Google doc. 

5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs

Screenshots/Diagrams (numbered for reference in notes above)

#1


Decisions

  • Sample Decision Item

Action Items

  • Sample Action Item


  • No labels