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 official Tacker source code is available in following repositories:
Below will cover the more project specific information you need to get started with Tacker.
#tacker
at Freenode[tacker]
for faster responses)
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discussAll 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.
Please refer to the Tacker Core Team contacts.
If you want to propose a new feature, Tacker features are tracked on Launchpad BP.
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 Tacker’s Launchpad Bugs.
RFE
tag.Closes-Bug
with bug-id
in the commit message.
Note, if there are multiple patchsets Partial-Bug
header should be used
instead of Closes-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
This process is recommended for medium to large enhancements that needs significant code-changes (LOC), community discussions and debates.
We track our tasks in Launchpad.
If you’re looking for some smaller, easier work item to pick up and get started
on, search for the low-hanging-fruit
tag.
You found an issue and want to make sure we are aware of it? You can do so on Report a bug in Launchpad. More info about Launchpad usage can be found on OpenStack docs page.
All changes proposed to Tacker require two +2 votes from core reviewers
before one of the core reviewers can approve patch by giving
Workflow +1
vote.
PTL may require more than two +2 votes, depending on the complexity of the
proposal.
More detailed guidelines for reviewers of patches are available at
Code Review.
Note
Pull requests submitted through GitHub will be ignored.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.