Skip to content

Open Community (TDC) Meeting, Thursday 01 February 2024 #3519

Closed

Description

@github-actions

NOTE: This meeting is on Thursday at 9am - 10am PT

Zoom Meeting link: https://zoom.us/j/975841675. Dial-in passcode: 763054 - Code-of-Conduct

In order to give visibility into the topics we cover in the TDC meetings, here is the planned agenda for the next meeting.
Sharing agenda items allows people to plan to attend meetings for topics that they have an interest in.
Everyone can comment on this issue prior to the meeting, to suggest topics or add comments on planned topics, whether attending or not.
Feel free to suggest other potential agenda topics.

Please submit comments below for topics or proposals that you wish to present in the TDC meeting

F10B5460-B4B3-4463-9CDE-C7F782202EA9

Topic Owner Decision/NextStep
Housekeeping issues (10 mins) TDC
Reports from Special Interest Groups (10 mins) SIG members
AOB (add comments below to suggest topics) TDC
Approved spec PRs TDC
New issues without response yet @OAI/triage

/cc @OAI/tsc Please suggest items for inclusion

Activity

  1. baywet commented on Jan 25, 2024

    @baywet
  2. lornajane commented on Jan 28, 2024

    @lornajane
    Contributor

    (I won't be at the meeting, here are some things that might be worth your time though)

  3. handrews commented on Jan 29, 2024

    @handrews
    Member

    I have several things I'd like to bring up, and will start a list here and update it:

    • Do we want to keep any requests regarding JSON Schema keywords in-scope for 3.x? Or do we want to declare them all to belong with JSON Schema (either the standard or extension vocabularies)? If we want any in-scope, are we entertaining all requests or is there a criteria for what we'll consider vs not?
    • Can we agree to use milestones to group issues for releases, putting each issue into the oldest relevant release line (e.g. 3.0.4 if it applies to both 3.0.4 and 3.1.1) and actively forward-porting fixes as we make them? That will get rid of our confusing milestone/label overlap
    • Does anyone object to me removing GitHub labels that are either unused, duplicate what we can do with milestones, or had to do with ways past teams managed releases years ago?
  4. handrews commented on Jan 29, 2024

    @handrews
    Member

    Easy PR review/merges, could all be done async!

  5. baywet commented on Jan 31, 2024

    @baywet
  6. handrews commented on Feb 1, 2024

    @handrews
    Member

    [EDIT post-meeting: "Apollo" turns out to be associated with GraphQL, so @baywet proposed "Gemini" as the previous incremental space program that laid the groundwork for Apollo and the moon landing. After the meeting, there were also valid concerns raised about it being better to just ship a release than create too much confusing jargon. We'll be holding off on deciding this until there's been plenty of time to consider the impacts.]

    I'd like to propose naming the 3.2+ minor releases the Apollo Series, in reference to the Apollo Program that took incremental steps leading up to the first humans walking on the Moon.

    I also think that we should publish a blog post about how the Apollo Series will bring near-term incremental improvements that is as exuberant and widely promoted as the Moonwalk 2024 post.

    In this weeks' Moonwalk call, I proposed a way to split up the Moonwalk functionality, specifically around deployments vs shapes, to make a more incremental transition possible - I can explain more on the TDC call.

  7. miqui commented on Feb 1, 2024

    @miqui
    Contributor

    Adding #3523

  8. handrews commented on Feb 1, 2024

    @handrews
    Member

    @miqui we can't properly address #3523 until the new TSC is in place.

  9. earth2marsh commented on Feb 1, 2024

    @earth2marsh
    Member

    Recording and an experimental summary written by Zoom's AI assistant.

  10. unpinned this issue on Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions