​
Maintainers

OCP is maintained by the loopmath project; loopmath is its reference implementation. The maintainers review issues and pull requests, decide on proposals, and cut releases.

​
How decisions are made

  • Every change is discussed in public, on GitHub, before it is merged.
  • Maintainers aim for agreement among the people who write and read OCP. When there is none, the maintainers decide, and write down why.
  • The JSON Schema for each version, with the meaning its description strings give each field, and the rules the schema cannot express are the authority; the specification pages give their full text. When the reference checker disagrees with them, the checker is fixed.

​
Stability

A reader accepts every published version. 0.3 is a strict superset of 0.2 (every field it adds is optional), though 0.2 is not a superset of 0.1, and a field is removed only after a deprecation notice that names its replacement and stays in the specification for at least two minor versions. The full promise is on the Versioning page.

​
License

The specification, the schemas and the example documents are open source under the MIT license.

​
Changes to this page

This page describes how OCP is run today, with the loopmath project as its only maintainer. It will change as other tools adopt OCP and more people take part, and those changes will be made in the open like any other.

Privacy