Skip to content

Community (TDC) Meeting Agenda backlog #2482

Closed

Description

@MikeRalphson

@OAI/tsc please add items here for future discussion.

Topic Owner Date Discussed/Issues/PRs - recording link
Presentation on SLA4OAI work @pjmolina 2021-02-25
links, backlinks and requestBody properties #1594 @mkistler / @luckybroman5 2021-03-04
overlays @darrelmiller / @MikeRalphson 2021-04-01 / 2021-04-22
"Housekeeping" of existing issues @webron 2021-04-15
Codegen vocabulary #2542 @mkistler 2021-04-22
Big list of post 3.1 possibilities @earth2marsh 2021-05-13
discriminator deprecate or improve? @Relequestual / @philsturgeon 2021-05-20
format and extension registry @MikeRalphson 2021-05-27
Diversity & Inclusion training @ncaidin 2021-06-10
Discriminator improvements and bundling TDC 2021-06-17
$ref in pathItem Objects @char0n 2021-07-08
Optional and multi-segment path parameters @darrelmiller 2021-07-15
SIG reports and milestone review @darrelmiller 2021-07-22
discriminator next steps @OAI/tsc 2021-07-29
SIG updates, schema PR reviews @OAI/tsc 2021-08-19

Wider TDC, please comment below with items you'd like us to cover on future TDC calls.

Activity

  1. self-assigned this
    on Feb 25, 2021
  2. pinned this issue on Feb 25, 2021
  3. luckybroman5 commented on Feb 25, 2021

    @luckybroman5

    @MikeRalphson Simply put, that was an amazing presentation. Things were very well thought out, and the feedback was unimaginably intelligent.

    For the item you have listed for me and @mkistler above, what sort of preparation work might I do to have a similar conversation around that improvement?

    Thank you kindly,

  4. MikeRalphson commented on Feb 25, 2021

    @MikeRalphson
    MemberAuthor

    We're not always that focussed, i.e. with a presentation, but any examples you might want to put together of link improvements either as new syntax or a proposal/extension would be welcome. It's always good to have something concrete to look at. Sorry we didn't get to introductions this week, we normally give new attendees a bit of floor space at the top of the meetings.

  5. luckybroman5 commented on Feb 25, 2021

    @luckybroman5

    @MikeRalphson No problem, I was just glad to listen in. I will work on preparing something such that when the time comes and there is availability we'll be ready.

  6. mkistler commented on Feb 25, 2021

    @mkistler

    @luckybroman5 There is a formal "proposal process" that the TSC put together a while back. I don't see it described in the repo but the basic idea is to create a proposal from this template:

    https://github.com/OAI/OpenAPI-Specification/blob/master/proposals/000_OAS-proposal-template.md

    The idea is to use the proposal process to get general consensus a feature change before trying to put together a PR to spec itself. I think this is probably the path we should take with improvements to links.

  7. luckybroman5 commented on Mar 1, 2021

    @luckybroman5

    Thanks @mkistler, I am working on putting something together now and will post here when complete, unless you all ready have something?

  8. mkistler commented on Mar 2, 2021

    @mkistler

    I had the best intentions to start on this but life got in the way, so I'll gladly yield to you to get things rolling.

  9. karenetheridge commented on Mar 2, 2021

    @karenetheridge
    Member

    @MikeRalphson Simply put, that was an amazing presentation

    bummer, I missed it -- was it recorded?

  10. MikeRalphson commented on Mar 3, 2021

    @MikeRalphson
    MemberAuthor

    bummer, I missed it -- was it recorded?

    Sorry it's not obvious, see the dated link above or in last week's agenda issue.

  11. luckybroman5 commented on Mar 4, 2021

    @luckybroman5

    @mkistler It took me some time, but here is my proposal. Any feedback is welcomed from anyone willing to give it.

    @MikeRalphson I'm planning on attending the TSC meeting tomorrow, however it's very understandable if it's too late to get this into this week's agenda. When there is time and if desired, I'm happy to go over the proposal whenever the TSC deems fit.

  12. mkistler commented on Mar 4, 2021

    @mkistler

    @luckybroman5 Thanks. This looks like a great "strawman" to get the discussion started. I do have some feedback and will try to organize my thoughts for today's meeting or, if we don't get to it today, will give feedback directly.

  13. changed the title [-]TSC Agenda backlog[/-] [+]Community (TDC) Meeting Agenda backlog[/+] on Apr 10, 2021
  14. earth2marsh commented on Sep 30, 2022

    @earth2marsh
    Member

    Let's devote the next meeting to discussing what might be radically different (or not) in v4! Here's a repo called Moonwalk that serves as a starting point.

  15. josephgardner commented on Oct 12, 2022

    @josephgardner

    Is there an updated list of recordings available anywhere?

  16. Saud96525 commented on Mar 18, 2023

    @Saud96525

    baywet:feature/formats-abstract

  17. EllaMartinez1981 commented on Oct 1, 2023

    @EllaMartinez1981

    @luckybroman5 There is a formal "proposal process" that the TSC put together a while back. I don't see it described in the repo but the basic idea is to create a proposal from this template:

    https://github.com/OAI/OpenAPI-Specification/blob/master/proposals/000_OAS-proposal-template.md

    The idea is to use the proposal process to get general consensus a feature change before trying to put together a PR to spec itself. I think this is probably the path we should take with improvements to links.

  18. LasneF commented on Dec 18, 2023

    @LasneF
    Member

    @MikeRalphson , @Relequestual , @philsturgeon

    in this one there is the mentionned of discriminator , is there any clarification toward
    the statement

    discriminator deprecate or improve?

    my personal opinion this should be fully dropped , and push to a json schema concern
    it would be even cleanner to have data modeling in JSon Schema (we could even have think about XSD! ) and keep OAS specification to Path / Body / header and so on

    this would have also avoid the issue about XML mapping than none of the linter / gateway support (Redocly / Spectral / Vaccum etc)

    Redocly/redocly-cli#1276 (comment)

  19. spacether commented on Jan 11, 2024

    @spacether

    When there is time, can we discuss this issue?
    Proposal: Create new repo for openapi tests, similar to json schema test suite
    #3486

  20. lornajane commented on Jan 25, 2024

    @lornajane
    Contributor

    Closing this issue since we rarely check it, and it would be better to bring items to the weekly meeting, for whichever week you would most like your suggestion to be discussed.

  21. unpinned this issue on Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions