The OmniBOR project consists of:

• The OmniBOR specification
• A set of first-party OmniBOR implementations, including:
  • omnibor-rs: A Rust implementation
  • omnibor-go: A Go implementation
  • omnibor-dotnet: A .NET implementation
  • omnibor-py: A Python implementation
• A set of patches for third-party software to add OmniBOR support, including:
  • patch-omnibor: A patched version of GNU patch.
  • gcc-omnibor: A patched version of GCC.
  • binutils-omnibor: A patched version of binutils.
  • llvm-omnibor: A patched version of LLVM.
• Miscellaneous other tools related to OmniBOR, including:
  • bomsh: Shell scripts for interacting with OmniBOR data.
  • jbor: A Java agent to log OmniBOR Artifact IDs.
• The OmniBOR website
• OmniBOR project spaces, including:
  • GitHub Discussions under on any OmniBOR repositories.
  • The weekly OmniBOR Working Group meetings.
  • Any other meetings or discussion spaces operated by the OmniBOR project.

Code of Conduct

All OmniBOR projects and spaces are covered by the OmniBOR Project Code of Conduct.

Governance

The OmniBOR Project is governed by consensus among active project participants. Generally, being an "active project participant" means participating in the weekly OmniBOR Working Group meetings, currently held over Zoom from 10am to 11am Pacific Time on Mondays.

Proposals for improvements to the language are generally discussed during these meetings, and when consensus is reached on a design, a formal proposal is made to the relevant repository and the change is merged.

The project does have a Core Team of long-term active participants. The OmniBOR Core Team currently consists of:

• Aeva Black
• Ed Warnicke
• Ashley Williams
• Frederick Kautz
• David Pollak
• Andrew Lilley Brinker