Community
The community space is the right place for open-ended discussion, governance, and collaboration that falls outside the scope of the main OCUDU code repository. For code bugs and feature requests, use the main issue tracker directly.
Get Involved
Use Discussions for open-ended questions, feedback, or ideas that are not yet ready to be filed as a code issue (including cases where you are unsure whether something is a bug). Use GitLab Issues for specific, reproducible bugs and concrete feature requests against the OCUDU codebase.
Discussions
Questions, feedback, and early ideas. Open an issue with the label that fits your topic.
Mailing List
Low-traffic list for release announcements and major project updates. Subscribe to stay informed without following the issue tracker.
Community Calls
Monthly open calls covering roadmap, recent work, and Q&A with the SRS engineering team.
GitLab Issues
Bug reports and feature requests for the main OCUDU repository. Report security vulnerabilities directly to the team rather than filing a public issue.
Improvement Proposals
OCUDU Improvement Proposals (OIPs): the process for proposing significant changes. Browse accepted, active, and historical proposals.
Governance
Project charter, Technical Steering Committee membership, and the framework for Working Groups and Special Interest Groups.
Community Highlights
Community highlights include field reports, use cases, integration guides, benchmarking results, and research from practitioners building with OCUDU. Browse the full collection at ocudu.org/news.
Submit Your Use Case
Share how you are deploying or researching OCUDU. Submissions are reviewed by the OCUDU team and featured on ocudu.org.
Use Case Submission Guide
Step-by-step guidance for completing the submission form, with tips for each field.
Community articles are open to anyone using or researching OCUDU. Submit via GitLab merge request. See the Code Contribution Guide for the format and review process.