Developer Zone
Everything you need to contribute to OCUDU: code style, logging conventions, testing requirements, and the full merge request process.
Read the Code Contribution Guide for an overview of the process, then check the GitLab issue tracker for issues labelled good first issue.
Architecture
Architecture Guide
Vision, design principles, and implementation patterns for the OCUDU codebase.
Codebase Guide
Module-by-module breakdown of the OCUDU codebase: CU-CP, CU-UP, DU-high, DU-low, MAC, RLC, and the scheduler.
Code Standards
The conventions that keep the OCUDU codebase consistent and readable. Familiarise yourself with these before opening a merge request.
C++ Code Guide
Language choices, library usage, source structure, naming conventions, and commit message formatting.
Logging Guide
Log levels, subsystem tags, and formatting rules for the OCUDU logging framework.
Testing Policy
Test coverage expectations for each type of contribution: unit, integration, and system tests.
Contributing
Code Contribution Guide
Ways to contribute, how to propose ideas, opening merge requests, and licensing requirements.
Docs Contribution Guide
How to add pages, write integration guides, follow the style rules, and submit a documentation merge request.
Using Claude Code
Pre-configured CLAUDE.md files for working on the OCUDU documentation with Claude Code.
Reporting Issues
How to report bugs and feature requests for the OCUDU codebase via GitLab issues.
API Reference
Doxygen
Auto-generated API reference for the OCUDU codebase, built from source documentation.