OpenEoX
summary
A standard-format project that encodes product lifecycle phases, versioning and support scope as machine-readable records, mapping versions to identifiers such as CPE IDs for version mapping, linking SBOM/CSAF/VEX artifacts, and expressing phase scopes (e.g. bug fixes, new features, security patches filtered by CVSS) with precise dates or date-plus-x relations. The repo contains example OpenShift streams serialized per-version, validation rules to prevent inconsistent phase ordering, and an early-spec rollout that is workable but not yet broadly adopted.
AI-written summary · about
chapters (14)
- 0:00OpenEoX project introduction
- 1:06Product life cycle challenges
- 3:57Product versioning standards
- 6:29Defining OpenEoX life cycle
- 9:41Human-readable life cycle issues
- 11:10Machine-readable format goals
- 13:22OpenEoX life cycle example
- 16:55OpenEoX development challenges
- 18:21OpenEoX for security standards
- 23:36Q&A: OpenEoX terminology
- 24:26Q&A: OpenEoX phasing approach
- 25:53Q&A: Handling uncooperative vendors
- 26:58Q&A: Measuring OpenEoX adoption
- 27:41Q&A: OpenEoX and CESAF
related talks
41mPlanning for Retirement: How Can We Prepare for Software’s...- 41mPlanning for Retirement: How Can We Prepare for Software’s...
50mEclipse Apoapsis - Open Source based Software Composition Analysis at scale
26mFlagship Projects: CycloneDX
36mSBOMs, VEX, and Kubernetes
26mLeveraging SBOMS to Automate Packaging, Transfer, and Reporting of D...
51mAll Good Things: End of Life and End of Support in Policy and Practice
30mContinuous Compliance in Open Source: Safety Assurance Through S...