The best way to join the community and get involved is to talk with others online or at a meetup and offer contributions. Here are some of the many ways you can contribute to the Tacker project:
Before you start contributing take a look at the Openstack Developers Guide.
You can find tacker guys in our publicly accessible channel on freenode
#tacker
. All conversations are logged and stored for your
convenience at eavesdrop.openstack.org. For more information regarding
OpenStack IRC channels please visit the OpenStack IRC Wiki.
Like other OpenStack related projects, we utilize Launchpad for our bug and release tracking.
Note
Bugs should be filed on Launchpad, not Github.
The official Tacker source code is available in following repositories:
The mirror repositories on Github:
Like other OpenStack related projects, we utilize the OpenStack Gerrit review system for all code reviews. If you’re unfamiliar with using the OpenStack Gerrit review system, please review the Gerrit Workflow wiki documentation.
Note
Pull requests submitted through GitHub will be ignored.
Enhancement to Tacker functionality can be done using one of the following two development process options. The choice depends on the complexity of the enhancement.
The developer, or an operator, can write up the requested enhancement in a Tacker launchpad [1] bug.
This process is recommended for smaller enhancements that can be described easily and it is relatively easy to implement in a short period of time.
The developer, or an operator, can write up the requested enhancement by submitting a patchset to the tacker-spec repository [2].
This process is recommended for medium to large enhancements that needs significant code-changes (LOC), community discussions and debates.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.