Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open Community (TDC) Meeting, Thursday 02 February 2023 #3149

Closed
github-actions bot opened this issue Jan 26, 2023 · 5 comments
Closed

Open Community (TDC) Meeting, Thursday 02 February 2023 #3149

github-actions bot opened this issue Jan 26, 2023 · 5 comments

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Jan 26, 2023

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 some more visibility into the topics we cover in the TDC meetings here is the planned agenda for the next meeting. Hopefully this will allow people to plan to attend meetings for topics that they have an interest in. And for folks who cannot attend they can comment on this issue prior to the meeting. 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

The agenda backlog is currently maintained in issue #2482

Topic Owner Decision/NextStep
Broken Markdown links
Separation of concerns in OpenAPI
Reports from Special Interest Groups TDC
AOB (see below) TDC
New issues / PRs labelled review @OAI/triage
New issues without response yet @OAI/triage

/cc @OAI/tsc Please suggest items for inclusion

@darrelmiller
Copy link
Member

Topic for this meeting: How do we separate concerns in OAS in order to manage complexity?

@ralfhandl
Copy link
Contributor

Housekeeping: how to repair the broken links in the spec markdown files, see for example issue #3132.

Apparently GitHub changed the way it treats anchors embedded in headlines, for example

#### <a name="schemaObject"></a>Schema Object

This used to copy the anchor element verbatim to the HTTP output, and links such as [Schema Object](#schemaObject) worked fine.

Now the anchor name is prefixed with user-content-, resulting in

<a name="user-content-schemaObject">

and all links broken.

This also affects the document at https://spec.openapis.org/oas/latest.html, try for example the links in this "Fixed Fields" table. These links now only scroll the table of contents on the left and no longer jump to the referenced section.

@frankkilcommins
Copy link
Contributor

@ralfhandl I'm due to talk to @MikeRalphson about this. I'm happy to fix assuming I know the pipeline expectations

@darrelmiller
Copy link
Member

Action: Darrel to go hunting in GitHub about anchor naming change

@darrelmiller
Copy link
Member

I did some spelunking about the broken links thing and ended up here gjtorikian/commonmarker#229

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants
@darrelmiller @ralfhandl @frankkilcommins and others