Contribute to Oxiverse
No CLA. No corporate capture. Just developers, researchers, and privacy advocates building together on Codeberg.
Our Principles
No CLA
Contributions stay under Oxiverse Community License (OCL) v1.2. You keep copyright; we get a license. No rights grabs. We never place your contributed code into a closed-source deployment — it is used only under OCL or an OSI-approved open source license (see LICENSE §6).
Privacy First
Every PR must pass the privacy test: no telemetry, no tracking, no data leaks.
Merit Based
Code speaks. No hierarchy, no gatekeeping. Good ideas win regardless of source.
Ways to Contribute
Code
- • Core search engine (IntentForge)
- • Browser, mail, productivity apps
- • API SDKs (TypeScript, Python, Rust)
- • Performance & privacy audits
- • Bug fixes & regression tests
Documentation
- • API reference & guides
- • Architecture decision records
- • Self-hosting tutorials
- • Privacy implementation guides
- • Translations (i18n)
Research
- • Intent extraction papers
- • Privacy-preserving ML
- • Search quality evaluation
- • Cognitive architecture studies
- • Adversarial robustness
Design & UX
- • Privacy-first UI patterns
- • Accessibility audits (WCAG)
- • Dark/light theme systems
- • Motion & interaction design
- • Iconography & illustrations
Community
- • Answer questions on issues
- • Write blog posts / tutorials
- • Organize local meetups
- • Review PRs & test releases
- • Report bugs with minimal repro
Security
- • Responsible disclosure
- • Penetration testing
- • Dependency auditing
- • Privacy threat modeling
- • Crypto implementation review
First Contribution in 5 Minutes
Code Contributors
- 1. Fork intentforge on Codeberg
- 2. Pick a
good first issuelabel - 3.
pnpm install && pnpm dev - 4. Write code + tests
- 5. Open PR → Codeberg (not GitHub)
Non-Code Contributors
- 1. Join discussions on Codeberg
- 2. Read docs — find gaps
- 3. Edit
.mdfiles directly in browser - 4. Submit PR with improvements
- 5. Get merged → you're a contributor
Development Standards
Code Quality
- • TypeScript strict mode
- • ESLint + Prettier (config in repo)
- • 80%+ test coverage for new code
- • No
anywithout justification - • Conventional commits
Privacy Requirements
- • Zero telemetry by default
- • Opt-in only for any data collection
- • Local-first architecture preferred
- • Encryption at rest & in transit
- • Data deletion on account removal
Review Process
- • 2 approvals for core changes
- • Security review for auth/crypto
- • Privacy review for data handling
- • Performance benchmarks for hot paths
- • Docs updated with code
Contributing Across Projects
Oxiverse is a multi-repo ecosystem. Contribution processes are per-repository:
intentforge (core search)
- Intent extraction, ranking, meta-search, caching
- Privacy-first search APIs, self-healing infrastructure
- Codeberg: codeberg.org/oxiverse/intentforge
- Contributors: activity/contributors
ravana (cognitive architecture)
- GRACE 27-phase homeostatic core, BeliefStore, IdentityEngine
- Decoder-first ML, continuous web training, emergent identity
- Codeberg: codeberg.org/oxiverse/ravana
- Contributors: activity/contributors
api (search & discovery APIs)
- Public REST/GraphQL APIs for IntentForge
- Rate limiting, auth, usage analytics (privacy-safe)
- Codeberg: codeberg.org/oxiverse/api
Always submit PRs to the correct repository. Issues without a repo reference will be closed with a redirect.
Contributors
We value every contribution — code, docs, research, design, community, security. Contributor recognition lives in each project's repository on Codeberg.
Questions?
Open an issue, start a discussion, or email us. We'd rather over-communicate than leave you guessing.