🤝 Open Source & Community

Help Us Build The Future of Cloud

CloudNexus is built by developers, for developers. Whether you're fixing a typo, writing docs, or shipping core infrastructure features, your contributions matter.

Get Started →

How You Can Contribute

There are many ways to get involved. Pick what fits your skills and schedule.

💻

Core Infrastructure

Contribute to our Go/Python backend, Kubernetes operators, or networking stack. High impact, well-documented codebase.

📚

Documentation

Improve guides, fix outdated API references, or write tutorials. Docs live in `/docs` and build with MkDocs.

🐛

Bug Reports & Triage

Report reproducible issues, verify existing bugs, or help label and prioritize community submissions.

🌍

Localization

Help translate UI strings, docs, and CLI help text into your native language using our Crowdin workflow.

Getting Started

Follow these steps to set up your local development environment.

1

Fork & Clone

Fork the repository on GitHub, then clone your fork locally.

bash
git clone https://github.com/your-username/cloudnexus.git
cd cloudnexus
2

Install Dependencies

We use Docker Compose for local services and Go 1.21+ for the core runtime.

bash
make deps
docker compose up -d db redis kafka
3

Run Locally

Start the development server with hot-reload enabled.

bash
make dev
1

Create a Feature Branch

Use semantic naming: feat/short-description, fix/issue-123, or docs/update-api.

bash
git checkout -b feat/autoscaling-tuning
2

Commit Changes

Follow Conventional Commits. We use commitlint in pre-commit hooks.

bash
git commit -m "feat(k8s): add horizontal pod autoscaler tuning"
3

Open Pull Request

Push to your fork and open a PR against main. Fill out the template, link related issues, and add tests.

Every PR must pass our CI pipeline before merging. We enforce:

  • Unit & integration tests (make test) with ≥80% coverage
  • Linting & formatting (golangci-lint, prettier)
  • Security scans (Trivy, Semgrep) and dependency audits
  • End-to-end acceptance tests on staging infrastructure
bash
# Run full local CI suite
make lint test coverage

Guidelines & Standards

📜 Code of Conduct

  • We are committed to providing a harassment-free experience for everyone.
  • Respect differing viewpoints and experiences. Accept constructive criticism gracefully.
  • Focus on what is best for the community. Unacceptable behavior will not be tolerated.

🔐 Security & Responsible Disclosure

  • Never submit security vulnerabilities as public PRs.
  • Use security@cloudnexus.io or our HackerOne program.
  • We respond within 48 hours and reward valid findings.

Still Have Questions?

Join our developer community, ask for mentorship, or hop into our real-time chat. We're here to help.