For general information on contributing to OpenStack, please check out the `contributor guide `_ to get started. It covers all the basics that are common to all OpenStack projects: the accounts you need, the basics of interacting with our Gerrit review system, how we communicate as a community, etc. The information below will cover the project specific information you need to get started with TripleO. Documentation ============= Documentation for the TripleO project can be found `here `_ Communication ============= * IRC channel ``#tripleo`` at FreeNode * Mailing list (prefix subjects with ``[tripleo][validations]`` for faster responses) http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss Contacting the Core Team ======================== Please refer to the `TripleO Core Team `_ contacts. Bug Tracking ============= We track our tasks in `Launchpad `_ and in `StoryBoard `_ Reporting a Bug =============== You found an issue and want to make sure we are aware of it? You can do so on `Launchpad `__. Please, add the validations tag to your bug. More info about Launchpad usage can be found on `OpenStack docs page `_ Getting Your Patch Merged ========================= All changes proposed to the TripleO requires two ``Code-Review +2`` votes from TripleO core reviewers before one of the core reviewers can approve patch by giving ``Workflow +1`` vote. Project Team Lead Duties ======================== All common PTL duties are enumerated in the `PTL guide `_. The Release Process for TripleO is documented in `Release Management `_. Documentation for the TripleO project can be found `here `_