Comments (4)
A few points from my notes/memory:
@earth2marsh announced provisional new membership of the TSC this week. Alongside #3669 which expands some of our existing project governance, the newest provisional members are @ralfhandl @mikekistler, @miqui and @lornajane
We talked about our general enthusiasm for getting better OAuth2 examples and, where needed, additional support in the specification to support OAuth2 as it evolves. This includes #3612 for DPoP and #3625 for the metadata URL field - but also support for missing flows like token exchange and device code flow.
We also talked about our git versioning/branching/development workflow and it's clear that we are in need of a change. A fruitful discussion seems to have happened this week in the Moonwalk SIG meeting. A high-level summary of what I understood would be:
- there is one file in the repository called
oas.md
and this is the canonical spec version (so I guess onmain
it's the latest stable release? We didn't talk about that) - we maintain one branch for 3.0, where
oas.md
is under active development and will become the 3.0.4 release. The branch will be tagged at release time. The same pattern for a 3.1 branch where the next tag would be 3.1.1 and a 3.2 branch where we'll tag 3.2.0. - when we tag a new version, we also copy the
oas.md
into themain
branch under theversions
structure that we have now.
The advantages of this structure are that we can diff the different versions and revisions of the same file in a sane way. There are fewer branches to keep track of so things should be easier to reason about. And it gives a simpler workflow for adding versions (hello 4.0) as we move forward.
My questions: where are we having the discussion about this that isn't in an agenda comment thread? And how do we apply changes such as tooling updates to the minor version branches without affecting the oas.md
file? /cc @miqui since I know you're putting something together on this.
As a followup to getting the branches sorted, at some point we can change our use of github pages - currently it uses a branch, which was a very early implementation. We think it would be more useful to use a subfolder now.
from openapi-specification.
Security PRs (I haven't looked at these recently, just figured I'd highlight the cluster of security stuff):
from openapi-specification.
Let's cover #3669 today, too.
from openapi-specification.
@lornajane I filed #3677 for the branching discussion. I almost filed a Discussion discussion but I wanted to put it in the Automation & Infrastructure project and you can't put discussions in projects. Plus this is pretty close to actionable.
from openapi-specification.
Related Issues (20)
- Schema development: main or branch, in parallel or at release time?
- Should we-organize our GitHub pages to a directory on main?
- Why does the JSON schema for 3.0 specify patternProperties for component names but allows additional properties?
- Support for `multipart/mixed` (and possibly better `multipart/*` support in general) HOT 11
- `description`/`summary` for Paths Object
- Support `multipart/byteranges` for 206 responses
- Support application/json-seq and similar JSON-based sequential formats HOT 1
- Did we break 3.2 compatibility by removing the Path Item $ref special case? HOT 12
- pipeDelimited and spaceDelimited style examples can be unresolvable HOT 10
- Encoding Object `contentType` field: "comma-separated list of the two types"? HOT 8
- Add appendix "Informative references" to published spec documents HOT 4
- Open Community (TDC) Meeting, Thursday 02 May 2024 HOT 3
- How are conflicts between `allowReserved` and RFC 3986 handled? HOT 6
- "body parameter" example in 3.x does not fit how Request Body Objects work HOT 6
- Open Community (TDC) Meeting, Thursday 09 May 2024 HOT 2
- Establish governance docs for working groups HOT 1
- Codify the meaning of "undefined" and "implementation-defined" HOT 3
- Use URI references for Security Requirements in 3.2
- remove "Optional OAuth2 security" examples HOT 2
- Style guide / release checklist for the specification HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from openapi-specification.