Contributing Guidelines

How to contribute to my open source projects

Contributing

Thank you for your interest in contributing! I welcome contributions from the community and appreciate your time and effort.

Getting Started

  1. Fork the repository - Create your own copy of the project
  2. Clone your fork - Download your fork locally
  3. Create a branch - Make a new branch for your changes
  4. Make your changes - Implement your feature or fix
  5. Test your changes - Ensure everything works as expected
  6. Submit a pull request - Open a PR against the main branch

Code of Conduct

Please be respectful and considerate of others. I expect all contributors to:

  • Use welcoming and inclusive language
  • Be respectful of differing viewpoints and experiences
  • Gracefully accept constructive criticism
  • Focus on what is best for the project and community

How to Contribute

Reporting Bugs

If you find a bug, please open an issue with:

  • A clear, descriptive title
  • Steps to reproduce the issue
  • Expected vs actual behaviour
  • Your environment details (OS, version, etc.)

Suggesting Features

Feature suggestions are welcome! Please open an issue with:

  • A clear description of the feature
  • The problem it would solve
  • Any implementation ideas you have

Submitting Pull Requests

  1. Ensure your code follows the project’s coding style
  2. Update documentation if needed
  3. Add tests for new functionality
  4. Make sure all tests pass
  5. Keep commits atomic and write clear commit messages

Pull Request Guidelines

  • Keep PRs focused - One feature or fix per PR
  • Write descriptive titles - Summarize what the PR does
  • Include context - Explain why the change is needed
  • Reference issues - Link to related issues if applicable
  • Be patient - Reviews may take some time

Development Setup

Check the project’s README.md for specific setup instructions. Generally:

  1. Install dependencies
  2. Run tests to ensure everything works
  3. Make your changes
  4. Run tests again before submitting

Questions?

If you have questions about contributing, feel free to open an issue and I’ll be happy to help.


Thank you for contributing!

Latest Posts

MCP Servers - Teaching AI to Read the Manual (So You Don't Have To)
MCP Servers - Teaching AI to Read the Manual (So You Don't Have To)

We’ve all been there. It’s 2am, you’re knee-deep in a ClickHouse query that refuses to cooperate, the Helm chart values file looks like it was written in ancient Sumerian, and your AI assistant confidently suggests a Karpenter configuration option that hasn’t existed since version 0.27. The AI is brilliant, creative, and occasionally a magnificent liar when it comes to niche technical documentation.

Kafka Auth Handler Goes Multi-Cloud
Kafka Auth Handler Goes Multi-Cloud

Back in December 2024, I wrote about gcp-kafka-auth-handler, a utility I created to bridge the authentication gap between Apache Beam Dataflow and GCP Managed Kafka. Since then, the project has evolved significantly as part of our broader multi-cloud journey. Today, I’m pleased to announce that the library has been renamed to kafka-auth-handler and now supports both GCP and AWS MSK.

Building an Open Deployment Framework with GitHub Actions
Building an Open Deployment Framework with GitHub Actions

Managing CI/CD pipelines across multiple repositories can quickly become unwieldy. Each project needs versioning, container builds, deployments, and releases—often with subtle variations that lead to duplicated workflow code. This post introduces an open deployment framework built entirely on GitHub Actions, designed to bring consistency and reusability to cloud-native deployments.