Skip to main content
Open Source · Community

Build together.
Public AI infrastructure.

OCC is community-driven. All repos are public on gitlab.occ.iio.space — Apache-2.0, CC-BY 4.0. Contributions welcome.

What is Open Source?

OCC uses the open-core principle. What goes into the OSS repos — and what doesn't.

What is Apache-2.0 / CC-BY
  • Layer definitions (layer.yaml, interfaces.yaml)
  • Flow schema + generic flows
  • Projection engine (project-node.py)
  • Drift-Detector
  • Compliance templates (generic)
  • AI literacy curricula
  • OCC-Glossar (689 Chunks, CC-BY 4.0)
  • Scripts + utility tools
What stays proprietary
  • Tenant-spezifische Daten (Kundendaten)
  • Server credentials + API keys
  • HITL boundary policy (security-relevant)
  • Internal intelligence pipeline
  • Strategic roadmap details
  • Solution prices + contract details

How to contribute

Fork → Branch → DCO-Commit → MR → Review → Merge. No CLA — just DCO (Developer Certificate of Origin).

1
Fork the repo
Your own namespace on gitlab.occ.iio.space. No account needed to read — only to contribute.
2
Feature branch
Naming convention: feat/topic, fix/description, docs/what-changed.
3
Commit with DCO
git commit -s -m "feat: ..." → generates Signed-off-by. Developer Certificate of Origin (DCO) instead of CLA.
4
Open Merge Request
MR against main. Description: What? Why? Tests?
5
Review + Merge
Maintainer (Intelego or OCC Board) approves. Your name goes into CONTRIBUTORS.md.
DCO sign-off — how it works
git commit -s -m "feat(layer-gdpr): add Art. 22 handling"
# Erzeugt automatisch:
# Signed-off-by: Dein Name <deine@email.com>

DCO means: you confirm you have the right to contribute this code under Apache-2.0. No forms, no lawyers. developercertificate.org ↗

Open roles

Voluntary · Remote · 2–8 h/month. Three roles needed now.

Knowledge
Source Curator

Review and verify new sources for the Knowledge Companion. Knowledge of GDPR, AI Act or related standards.

2–4 h/month

Safety
Safety Reviewer

Red-team testing before releases. Bias assessment, memorization tests, release gate review.

4–8 h/quarter

Community
Community Steward

Coordinate RFCs, moderate community calls, onboard new contributors, maintain Code of Conduct.

4–6 h/month

Architecture
Layer-Author

Define new IIO layers or improve existing ones. Know the YAML schema, understand the HITL principle.

as needed

Getting started: Good First Issues

Want to contribute but don't know how? These tasks are a good starting point.

Translate a glossary term (Esperanto / other languages)
Translate a missing AI governance term into a language. No programming skills needed — just edit YAML.
Create ISO 42001 layer definition
Write a new layer YAML for a missing AI management component. Template is in the repo.
Red-team question for the glossary
Formulate a tricky governance question the OCC assistant should be able to answer. Tests RAG quality.
Verify source + update Source Registry
Review a new public domain source on AI governance (copyright, license, relevance) and add it to source_registry.yaml.

Community Calls

Monthly · 45 min · Online · Public · Recorded.

Next call: August 2026 (date to follow via Matrix)
Matrix: #occ-community:matrix.iio.space
Issues + announcements: GitLab Issues ↗
Agenda (CC-001, Aug 2026)
  1. OCC status + graduation progress 10 min
  2. compliance-qwen: progress + demo 10 min
  3. How to contribute? Contributing guide 10 min
  4. Open discussion 15 min

Questions?

Fastest response
Matrix

#occ-community:matrix.iio.space — open to everyone.

Technical questions
GitLab Issues

Open an issue ↗ — public, archived, searchable.

Everything else
Email

hello@opencognitioncommons.org — for board enquiries, grants, partnerships.