Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 3 Next »

Meeting Date & Time

  •   This Task Force holds TWO meetings weekly every Thursday at the following times (to cover global time zones - see the Calendar of ToIP Meetings):
    • NA/EU 07:00-8:00 PT / 14:00-15:00 UTC 
    • APAC 18:00-19:00 PT / 01:00-02:00 UTC

Zoom Meeting Links / Recordings

Attendees

NA/EU Meeting

APAC Meeting

Main Goals of this Meeting

1) Decide about using GitHub Discussions, 2) Review GitHub issues management process, 3) Agree on a set of issue labels, 4) Agree on roles and merge management, 5) Review a set of issues per this process.

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:
5 minAnnouncementsAll

Updates of general interest to TATF members.

  • The Governance Stack Working Group has a special topic meeting on Oct 20th at which Drummond Reed has proposed to brief them on the Technology Architecture Spec so they can better understand the "governance targets". Who else wants to join him to help present the spec and answer questions? Wenjing Chu to join Drummond
5 minReview of previous action itemsChairs

ToIP Technology Architecture Specification Review Topics

Discussion of progress on the working draft of the ToIP Technology Architecture Specification (TAS). Links to relevant documents and diagrams:

5 minsGitHub DiscussionsAndorProposal to turn on GHP Discussions for our repo. See this guide if you are new to GitHub Discussions.
10 minsLabels for GitHub issues

Andor raised issue #37 for us to figure out the set of labels we want to use for organizing and prioritizing our work on GitHub issues. The thread so far has arrived at this list (see the thread for more details):

  • priority-1
  • priority-2
  • priority-3
  • defer-to-V2
  • editorial
  • substantial
  • correction
  • needs-special-group
  • needs-proposal
  • needs-PR
  • PR-exists
  • last-call-to-close

Is this list complete? Any revisions or additions?

ACTION: Andor volunteered to implement the set of labels in issue #37.

10 minsGitHub roles and merge management processAndor 

Andor posted the following two issues so we can start moving forward at speed with issues processing:

  • #45: Decide roles and provide permissions
  • #40: Merge process discussion

Discussion:

  • -
10 minsReview a set of issues and their proposed labelsDrummond Reed 

To get us going, Drummond has added comments including proposed labels to the following issues:

5 minsPlan for the upcoming weekEditorsDiscuss how we will proceed at maximum speed over the next week.
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