Contributing

BlazeBee thrives on community input, accelerating its evolution as a premier open-source metrics collector for modern infrastructures.

Purpose of This Page

This section motivates and guides contributions. Use it to join the project effectively.

Why Contribute?

• Influence features for your use cases.
• Gain experience with Rust and systems programming.
• Build a portfolio in open-source infrastructure tools.

Contribution Process

1. Fork and Clone: Fork on GitHub, clone locally.
2. Branch: Create a feature branch.
3. Code: Follow rustfmt.toml for style.
4. Test: Add/run tests with cargo test.
5. Commit: Use clear messages.
6. Pull Request: Submit with description; reference issues.

Areas for Contribution

• New collectors or metrics.
• Documentation improvements.
• Bug fixes.
• Performance optimizations.

Code of Conduct

Respectful, inclusive collaboration under Apache-2.0 license.

Your contributions help make BlazeBee more robust, inviting participation from DevOps professionals worldwide.