We commit to always provide free and public access to our Open Source repositories. If you see repository on our GitHub today, then it will be here tomorrow and thereafter in perpetuity.
From time to time, we might decide we can no longer maintain a repository. If that happens, we will mark it as "archived" on GitHub. This will ensure you will continue to have access to the code.
The best way to get involved is to checkout our "getting started" guide.
Then join us in our Slack
#community channel to get support or talk with others in the community.
Cloud Posse accepts contributions from the community. In the interest of fostering an open and welcoming environment, we have a strict code of conduct to ensure participation in our projects and our community is a harassment-free experience for everyone.
If you want to make some big changes or don't know where to begin, it's best to first get in touch. You can discuss the change you wish to make via GitHub issues, email, or join our
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
- Fork the repo on GitHub
- Clone the project to your own machine
- Commit changes to your own branch
- Push your work back up to your fork
- Submit a Pull request so that we can review your changes
NOTE: Be sure to merge the latest from "upstream" before making a pull request!
Cloud Posse actively maintains all projects on our GitHub.
There's a lot going on in our GitHub. With over 200+ Open Source repositories, keeping track of all the Open Issues, Feature Requests, and Pull Requests is a fulltime job.
We use Kanban board to manage our Open Source projects.
Get in touch with us.