2022-10-13 TATF Meeting Notes

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 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 DiscussionsAndor

Proposal to turn on GHP Discussions for our repo. See this guide if you are new to GitHub Discussions.

DECISION: We will turn on Github Discussions in our Github repo.

ACTION: Drummond Reed to ask Elisa Trevino turn on the Discussions feature in our Github repo.

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: Drummond Reed to update the GitHub Issues Management wiki page to include: a) this revised list of labels, b) a table explaining how each label ties into the process, c) more detail about the Editor role, including managing issue assignments, d) the Maintainer role. DONE.

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

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 -

ACTION: Editors to come up with a list of proposed permissions and work with Elisa Trevino to assign the necessary access rights.

  • #40: Merge process discussion - Whats the process and who can merge? 

    @wenjing suggested break out: Editor and Maintainer.

    Antti:

    • Maintainer decides what goes into which version. Own the document/published version.
    • Someone needs to decide who goes into the release.


ACTION: Antti Kettunen volunteered to propose a repo management process. DONE.

  • Abbie:

    • It can help to assign a Lead editor who can help drive decisions among the Editors.
    • Drummond agreed and suggested letting the Editors self-organize.

ACTION:  Christine Martin and/or Drummond Reed to create an #tswg-tech-arch-editors channel on Slack. DONE.

10 minsReview a set of issues and their proposed labelsDrummond Reed 

To get us going, Drummond has added comments including proposed labels on the following issues: #36#34#32#31#29.

APAC:

We discussed issue #31, which concerns the differences between Figure 4 in Working Draft 03 (Google doc) and Figure 4 in the Github Markdown document.

Andor very helpfully copied both figures into the issue so it is much easier to compare them.

Jo Spencer added a comment about what he believes the essence of the distinction is.

ACTION: Drummond Reed to collect his thoughts on issue #31 and add a comment.

5 minsPlan for the upcoming weekEditors

Given that the APAC call consisted of just four editors (Andor, Christine, Jo, Drummond), we concluded that with the labels now set up and assignments being made, we should be able to proceed asynchronously at maximum speed over the next week.

ACTION: Drummond Reed to post a message to the #tswg-tech-arch-tf channel urging all TF members to being self-assigning and working issues.

5 mins
  • Review decisions/action items
  • Planning for next meeting 
ChairsNext week's meeting should focus entirely reviewing, assigning, and closing issues.

Decisions

Action Items

  • ACTION: Drummond Reed to ask Elisa Trevino turn on the Discussions feature in our Github repo.
  • ACTION: Drummond Reed to update the GitHub Issues Management wiki page to include: a) this revised list of labels, b) a table explaining how each label ties into the process, c) more detail about the Editor role, including managing issue assignments, d) the Maintainer role. DONE.

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

  • ACTION:  Christine Martin and/or Drummond Reed to create an #tswg-tech-arch-editors channel on Slack. DONE.
  • ACTION: Editors to come up with a list of proposed permissions and work with Elisa Trevino to assign the necessary access rights.
  • ACTION: Antti Kettunen volunteered to propose a repo management process. DONE.
  • ACTION: Drummond Reed to collect his thoughts on issue #31 and add a comment.
  • ACTION: Drummond Reed to post a message to the #tswg-tech-arch-tf channel urging all TF members to being self-assigning and working issues.