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.
  • Daniel Bachenheimer volunteered to join the Editors team. So the current team is: Wenjing Chu, Darrell O'Donnell, Drummond Reed, Andor Kesselman, Christine Martin, Daniel Bachenheimer 
• 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 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 turn on the Discussions feature in our Github repo (or ask Elisa Trevino to do it).

Drummond Reed Andor Kesselman 

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

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

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

• #45: Decide roles and provide permissions - TODO: editors to come up with a list of proposed permissions - work with Elisa Trevino for 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.

  Abbie:

  • Lead editor.

  Drummond:

  • No formal role of lead editor but someone would step up.

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

Discussion:

• -