Henry Andrews

Splitting out from #3509 so I can close that massive issue, in a recent(ish) TDC call, we agreed to the following (leaving out points that I already did the day...

Splitting off from #3509, I've been using the milestones as follows: * Issues go in the oldest open milestone to which they are relevant, _if_ it seems likely that they...

Define a policy using draft PRs when waiting on specific approvals

5

We've had some understandable confusion on when PRs get merged, as we came up with some exceptions to the "2 TSC approvals" rule in TDC calls. But not everyone is...

Add info to security considerations about outdated security practices, and link in new versions

4

See PR #3584 from @AxelNennker for the background. We agreed in the TDC meeting 2024-02-22 to add info in security considerations and probably also on the learn site, and link...

Add requirements or recommendations about allow/deny lists for reference target retrieval

2

As multi-document OADs become more important due to both new use cases and an increasing number of OADs that are far too large to work with as a single document,...

schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, update terminology

1

I'd like to merge this and address it in the build scripts rather than resuming publication of schemas with absent dates and misleading patch release guidance. * Replace all dates...

Currently, we have the following schema document `$id`s for OAS 3.1 (shown relative to a base URI of `https://https://spec.openapis.org/oas/3.1/`, and without the trailing date segment that all schemas need to...

We have previously turned away quite a few suggested schema changes, particularly from @karenetheridge and @jeremyfiel, that attempted to enforce sensible but not mandatory constraints. These often involve SHOULDs or...