The fork
Outline
This page is an outline. The structure is settled; the prose is not written. Most of the material exists in the repository README and moves here.
What the page must answer
- Why fork rather than contribute upstream?
- Is there a way back?
- Which library should I use if I am not go-openapi?
Sections
- The fork point, and what has changed since
- Hard fork: no upstream merges, no shared release line
- Licensing: Apache-2.0 for this repository’s work, with goccy’s MIT notice
retained in
NOTICEfor the code the fork started from - The relationship to
go.yaml.in/yaml/v3, which the codec’s default struct-tag behaviour matches - go-openapi’s reason for owning this: the toolkit needs a YAML implementation it can hold to the specification