Why Did I Contribute to the LitmusChaos Project for Hacktoberfest 2021
Tags: hacktoberfest, chaosengineering, cloudnative, kubernetes
Published: 2022-05-30 15:26:51

For the eighth edition of Hacktoberfest, I chose to contribute to [LitmusChaos](https://litmuschaos.io/), a CNCF sandboxed project for Cloud-Native Chaos Engineering. It was a month-long celebration of making Chaos Engineering simpler for all the SREs and Developers who aspire to make their services more resilient. So if you are a software developer like me, then why should you consider contributing to the [LitmusChaos project](https://github.com/litmuschaos/litmus)?

### 1. Buzzing Community

The Litmus community boasts of some 1000+ community members who profoundly promote the Cloud-Native resiliency paradigm shift by redefining the Chaos Engineering experience for everyone. It is the community members who bring out the best qualities of Chaos Engineering for their distinct use cases by leveraging the diverse set of chaos experiments offered by LitmusChaos. The regular community meetups and sync-ups highlight these interesting use cases, which helps every community member to learn from each other.

### 2. Excellent Code Quality

LitmusChaos is an awesome project for beginners who want to kick-start their journey into the world of open-source as the LitmusChaos project has been developed and contributed by all kinds of developers belonging to a varied number of organizations. This has enabled a robust project codebase that adheres to the best coding practices and is easy to understand and contribute. Further, the LitmusChaos project makes use of a wide range of open-source tools such as Kubernetes, GraphQL, Argo Workflows, React JS, etc. which allows every developer to contribute to something of their own choice.

### 3. Awesome Documentation

The Litmus project features extensive [documentation](https://docs.litmuschaos.io/) that encompasses every single aspect of the project. It aids the developers who want to gain a deeper insight into the project and want to contribute to it with its detailed user documentation, experiment documentation, and API reference. Contributing to the documentation and tutorials is also an excellent option, which helps LitmusChaos to be used by more community members and end-users.

### 4. Flexible Litmus SDK

[Litmus SDK](https://medium.com/@ispeakc0de/getting-started-with-litmus-sdk-f2d1fc8c8dea) allows developers to define their chaos experiments for the LitmusChaos framework. It helps developers to easily bootstrap the experiment files where the SDK is responsible for generating all the requisite artifacts and the developer is only responsible for defining the experiment business logic. The best part about Litmus SDK is that it’s available in multiple programming languages such as Go, Python, and Ansible, allowing developers to develop chaos experiments in any programming language of their choice.

### 5. Mentorship Programs

Apart from Hacktoberfest, LitmusChaos also takes part in all the major open-source mentorship programs such as Google Summer of Code (GSoC), GitHub India Externship, The Linux Foundation Mentorship Program (LFX Mentorship), and Google Summer of Docs (GSoD) among the others. These mentorship programs provide a very lucrative opportunity to the mentees for not only contributing to the open-source but also to learn and gain recognition as a quality developer since you’ll be making very significant contributions to the Litmus project under the guidance of a LitmusChaos project maintainer.

## Join the Litmus Community:

Want to get help with queries, learnings, & contributions? Join the Litmus community on slack. To join the slack community please follow the following steps:
**Step 1:** Join the Kubernetes slack using the following link: [https://slack.k8s.io/](https://slack.k8s.io/)
**Step 2:** Join the #litmus channel on the Kubernetes slack or use this link after joining the Kubernetes slack: [https://slack.litmuschaos.io/](https://slack.litmuschaos.io/)

Looking forward to seeing you in the world of Open Source!