We have been hard at work on Chef Habitat since fall 2015 and are very excited to share it with you as an open-source project licensed under the Apache 2.0 License. You can find the source on the Chef Habitat GitHub repository.
While we believe the foundational elements of Chef Habitat are in place, there will always be more work to do to make sure that we provide the best possible experience in building, deploying and managing applications in the real world. This is where we hope you'll come in and contribute to our community.
The best way to find out how to contribute to Chef Habitat is in our Contributing.md. It is a living document that covers almost all of the aspects of project governance from our triage process, to support channels and workstation setup. It's a great jumping off point.
All participants in the Chef Habitat community are expected to read and follow the Code of Conduct.
The Chef Habitat project is largely written in Rust, which may be a new language for you. We hope that doesn't dissuade you from getting involved. In our repo you'll find issues labeled with both
E-mentored. If you are new to rust and want to give it a shot,we highly encourage you to join the
#rust` channel in the Chef Habitat slack, grab one of these issues, and start Coding.
- Help out with documentation
- Write a blog
- Run a meetup in your town? We've even got slide decks we can share if you want to talk about Chef Habitat but don't have time to build your own slides. Ping us in #general on Slack for assistance.
- Interested in some social programming, or want to share something cool you're working on? Hop on one of our livestreams.
- Contribute packages to the Core origin. If you've packaged something up that you think would be helpful to the community at large but you'd prefer it exist in the core plans repository, you can totally open a pr over there.
If you need any more suggestions on ways to contribute, drop by the community slack and ask in #general. I guarantee we can find plenty of ways for you to get involved.