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.
Below will cover the more project specific information you need to get started with os-testr.
IRC channel #openstack-qa
at OFTC
Mailing list (prefix subjects with [qa]
for faster responses)
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
Please refer to the os-testr Core Team contacts.
If you want to propose a new feature please read Feature Proposal Process os-testr features are tracked on Launchpad BP.
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 Launchpad. More info about Launchpad usage can be found on OpenStack docs page
All changes proposed to the os-testr require two Code-Review +2
votes from
os-testr core reviewers before one of the core reviewers can approve the patch by
giving Workflow +1
vote.
All common PTL duties are enumerated in the PTL guide.
The Release Process for QA is documented in QA Release Process.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.