Community

BubuStack is built in the open. We're a small project with big ambitions, and we need contributors who want to build something meaningful.

Where to find us

• GitHub — bubustack organization. Code, issues, discussions, and examples all live here.
• Discord — Join our server for real-time chat, questions, and collaboration.

How to contribute

1. Pick something — Browse operator/runtime issues, registry/CLI issues, Bubuilder issues, website/docs issues, or check the Roadmap for what needs help.
2. Fork & branch — Work from a feature branch. Keep commits scoped.
3. Test — Add unit and integration tests. Use KinD for operator/transport changes.
4. PR — Reference the issue, include context. Reviews target 2 business days.

Issues vs discussions

• Use repo issues for concrete bugs or scoped feature work in bobrapet, bubu-registry, bubuilder, website, or a specific component repo.
• Use GitHub Discussions for cross-repo design topics: registry policy, Bubuilder UX/API direction, SDK/runtime contracts, and roadmap proposals.

Contribution areas

• Operator — Controllers, webhooks, CRDs, reconciliation logic.
• Transports — Bobravoz gRPC and new transport implementations.
• SDK — Go SDK, testing harnesses, new language SDKs. The current contributor-ready backlog is tracked in the Roadmap.
• Registry & CLI — Template packaging, discovery, publishing, and registry docs.
• Bubuilder — UI/API, run inspection, YAML editing, auth, and workflow authoring UX.
• Operator hardening — Security model cleanup, ownership boundaries, and least-privilege reductions that keep secret propagation and managed runner identities working.
• Engrams & Impulses — New reusable components for the catalog.
• Docs & examples — Tutorials, guides, production runbooks.
• Bug fixes — Triage, reproduce, fix. Always welcome.

Coding standards

• Go: gofmt, goimports, golangci-lint.
• TypeScript/React: repo ESLint rules.
• YAML: deterministic, kubectl apply --server-side friendly.

Contributor ladder

We follow an open contributor ladder modeled on CNCF practices:

Role	How you get there	What you gain
Contributor	Merge your first PR	Listed in CONTRIBUTORS, community recognition
Reviewer	Consistent quality contributions, domain knowledge	Review permissions, input on design decisions
Maintainer	Sustained contribution, trust from existing maintainers	Merge rights, release authority, project direction

Early contributors shape the project. The people who show up now will have outsized influence on where BubuStack goes.

Security & responsible disclosure

Follow the project security policy in SECURITY.md. Report vulnerabilities through the GitHub Security Advisory form:

• https://github.com/bubustack/bobrapet/security/advisories/new

Do not report vulnerabilities in public issues.

Code of Conduct

We enforce the Code of Conduct in every repo and channel. For moderation concerns, contact:

• community@bubustack.com