Added missing doc, for example for serial tests, fixed 404 links, spellings, formatting and etc Change-Id: I07a8cf9508d3cba33bd04afdc301bb7145153d59
2.6 KiB
So You Want to Contribute...
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 Tempest.
Communication
- IRC channel
#openstack-qa
at OFTC - Mailing
list (prefix subjects with
[qa]
for faster responses)
Contacting the Core Team
Please refer to the Tempest Core Team contacts.
New Feature Planning
If you want to propose a new feature please read Feature Proposal Process Tempest features are tracked on Launchpad BP. It also helps to bring the feature up during the next PTG and contact the current PTL of QA project. Information about PTG is always posted on the Mailing list.
Task Tracking
We track our tasks in Launchpad.
If you're looking for some smaller, easier work items to pick up and get started on, search for the 'low-hanging-fruit' tag.
Reporting a Bug
Have 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
Getting Your Patch Merged
All changes proposed to the Tempest require a single
Code-Review +2
vote from a Tempest core followed by a
Workflow +1
vote. More detailed guidelines for reviewers
are available at ../REVIEWING
.
Project Team Lead Duties
All common PTL duties are enumerated in the PTL guide.
The Release Process for QA is documented in QA Release Process.