Versions Compared

Old Version 1

changes.mady.by.user Craig McNally

Saved on

compared with

New Version 2

changes.mady.by.user Craig McNally

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

TimeItemWhoNotes
1 minScribeAll

Marc Johnson is next, followed by Ingolf Kuss

Reminder:  Please copy/paste the Zoom chat into the notes.  If you miss it, this is saved along with the meeting recording, but having it here has benefits.

5-10 minLiaison Updates

Maccabee Levine

Tod Olson

Jakub Skoczen

Craig McNally

Jenn Colt 

1 minUpcoming MeetingsAll
  • - Dedicated discussion: Topic TBD
  • - Regular TC meeting
  • - Dedicated discussion: Cancel for American Thanksgiving?
  •   - Regular TC Meeting
  •   - Dedicated discussion: TBD

Topics for dedicated discussions:

  • Voting rules (continued)?  
  • New language adoption policy?  
  • Eureka adoption (RFC, TCRs, etc.)
5-10 minTCR Board ReviewAll
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyTCR-44
    • Julian Ladisch: mod-reporting is finished. Could be moved to "under review".
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyTCR-46
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyTCR-47
    • Presently assigned to Craig McNally, but need someone to collaborate with to avoid a potential COI
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyTCR-48
    • Assigned to Tod Olson, but it sounds like he may not have bandwidth... skip to Jenn Colt? 
    • From Tod:  "I will be out of the office the next two weeks, and won't be able to look at anything before December. By way of setting parameters. If this need quicker action, it should go to someone else."
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyTCR-49
5 min

Technical Council Sub-Groups Updates



1 min

GitHub RFCs

Wiki RFCs

All

I don't think there's anything to discuss here.

Reminder to formally close the Go language RFC

1 minDecision LogAll

Nothing new here.

5 min

Officially Supported Technologies (OST)

All

Check Recurring Calendar...

1 minTC member changesAll
*Voting RulesAll

Are we able to make a decision?  There were two things we wanted to make a decision on today:

  1. Moving from "majority of members" to "majority of votes"
  2. Whether we want to allow slack voting
    1. There are still some open questions about when slack voting would be used...  Is this right?
      1. Lazy Consensus → Zoom vote
        1. if someone requests a vote
      2. Zoom vote → Slack vote
        1. if there aren't enough votes to make a decision?
        2. If margin is very close (something passing by as few as 4 votes)?
    2. Benefits:
      1. Slack voting allows members who were not present to factor into the decision
      2. It could help in cases where there are not enough members present (after abstentions) to make a decision
    3. Concerns:
      1. This has the potential to slow things down.  E.g. decisions on TCRs often happen right against the deadline.  Introducing further delays is likely to cause a lot of frustration.
      2. There's no guarantee that this will help in cases where there are not enough members present (after abstentions) to make a decision.  So now we've just delayed the decision, only to find that we still cannot make one.
      3. Could be perceived that attending meetings is less important as critical votes will happen in slack.
NAZoom Chat



...