The OCM Community

Communication channels, community calls, and ways to engage with the Open Component Model project.

The Open Component Model is developed in the open. Whether you want to understand the project, contribute code, or follow along - this section has you covered.

Developer Onboarding

New to the project? Understand what OCM is, how the repo is structured, and where to start.

Contributing

Fork, code, and submit - everything you need for your first contribution.

How We Work

Meetings, rituals, project boards, and decision-making processes.

Governance

Special Interest Groups, Technical Steering Committee, and project structure.

Get in Touch

GitHub

Our GitHub repositories are the central hub for all project development. Report issues, submit pull requests, and follow the project’s progress. New contributors can find issues labeled good first issue to get started.

Slack

Join #open-component-model in the Kubernetes Slack workspace.

Kubernetes Slack Membership

If you aren’t already a member in the Kubernetes Slack workspace, please request an invitation.

Zulip

Join neonephos-ocm-support on the Linux Foundation Zulip instance for technical discussions. Zulip is open to everyone and does not require prior membership. Its threaded conversation model makes it well-suited for longer design discussions and contributor questions.

RSS Feed

Stay up to date with the latest OCM blog posts and announcements by subscribing to our RSS feed.

Community Calls

We hold regular community calls open to everyone:

  • Frequency: Every first Wednesday of the month
  • Time: 17:00-18:00 (Europe/Berlin)
  • Duration: 1 hour
  • Location: Zoom Link

Call history and recordings are available on GitHub.

These calls are moderated by at least one OCM Core Maintainer. Bring anything you like - ideas, issues, concepts, or questions about upcoming work.

Code of Conduct

To make OCM a welcoming and harassment-free experience for everyone, we follow the NeoNephos Code of Conduct.

Security

To report security vulnerabilities, please do not use public GitHub issues. See Reporting Security Vulnerabilities for instructions.