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

•  ACTION: A "Public Review Process Group" consisting of Drummond Reed Darrell O'Donnell , Christine Martin , Judith Fleenor , Elisa Trevino, and Jory Burson will sort out and propose the public review process we will use in GitHub plus any other acceptable "channels" (e.g., Google docs, email). Drummond Reed  to post meeting time in slack once set.
•  ACTION: Drummond Reed to post to Slack and send to the TSWG mailing list a summary of these proposals for processing and resolution of GitHub issues and a call for any other volunteers for the Editors team.
  • In response to the email, Daniel Bachenheimer volunteered to join the Editors team. So the current team is: , joining Wenjing Chu, Darrell O'Donnell, Drummond Reed, Andor, Christine Martin, Daniel Bachenheimer .
  • In today's meeting, Antti Kettunen and Jo Spencer also volunteered to join the Editor team, making it a total of 8.
•  ACTION: The Editors team will: 1) Document to the TSWG branch of the ToIP wiki the process for raising, discussing, and closing issues; 2) Link to that page from the landing page for the ToIP Technology Architecture Specification.
  • See this new wiki page: GitHub Issues Management - if anyone would like to give feedback, please go ahead and propoe propose edits.

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: Wenjing Chu will Drummond Reed to ask Elisa Trevino turn on the Discussions feature in our Github repo (or ask Elisa Trevino to do it).

Drummond Reed Andor 

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: Add label for "needs-editor-review".ACTION: Editors (Drummond Reed volunteered) to  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.

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

• #45: Decide roles and provide permissions - TODO

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 .

  Drummond:

  • No formal role of lead editor but someone would step upwho 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. 

Discussion:

. DONE.

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.

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.