Become a contributor
We believe that discussions and interactions make for a great tool. Driftctl is free and open source and our community of users is growing day by day. Here is how you can join us and start taking part to the life of project.
Open source means community. We are very grateful for all interactions that help us shape a better tool. You can learn more on how we’d like these interactions to contribute to an open, welcoming, diverse, inclusive, and healthy community in our community code of conduct.
Here is how you can start taking part to the life of the project:
We listen a lot to users feedback to sort through our roadmap and decide of our next steps. GitHub discussion directly related to the product are a great help. Feel free to open a discussion, upvote an existing topic or add comments to a thread. You can also come say Hi on our community discord server. We’re always happy to chat!
Our code is open source and we are grateful for your help. Do not hesitate to pick up an issue. Some of them are flagged as “good first issues”, which is probably a great way to get started. On your way in, make sure to read the guidelines where we explain the contribution process and pull requests lifecycle.
This is probably one of the most helpful contributions you can make. We test thoroughly everything we ship (seriously, we test a lot). Still, there’s no way we can go through 100% of all possible scenarios and bugs can happen. As a user, you can help us by reporting bugs in various ways : the simplest one is to open an issue on GitHub and tell us about your problem. You can also report the bug on discord and live chat with the core team that will investigate with you. Feel free to interact with the maintainers on the #support channel. By the way, if you’d like to see what’s cooking, we also have a #dev channel where all things related to engineering are openly discussed.
In all cases, sharing your crash data will help a lot. You can do so by adding
--send-crash-report when running driftctl (see related documentation here).
If you think that there’s a missing part on the documentation or something that should be updated, feel free to suggest edits either by opening an issue on the documentation repo, or with a direct message on one of the channels listed above.
If you are already using driftctl a lot why not share your knowledge? Pick up a question from less experimented users on one of our channels and help them out. You can also give your take on a discussion, or share a workaround on a specific problem.
If you are the writer’s type, you can write a blog post about your use case. Each story is unique : your journey to infrastructure automation, your setup, your team, your constraints… We love to see users share their story on why they started using driftctl and how they do it. We are open to guest blog posts, so do not hesitate to share your story to hello[at]driftctl.com for review.
Same as above : share your screen and turn on your microphone. We’ll be glad to republish your video on our YouTube channel.
If you’d like to talk about infrastructure drift, you can showcase the tool in your webinars, workshops or meetups. We’ll be glad to provide you with support like contents, tweets, stickers… Just reach out to hello[at]driftctl.com with some information about what you are planning and we’ll help as much as we can.
Get product updates and occasional news.