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-stress.

Communication¶

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

Contacting the Core Team¶

Please refer to the tempest-stress Core Team contacts.

New Feature Planning¶

If you want to propose a new feature please read Feature Proposal Process

Task Tracking¶

There is no separate task tracking tool for tempest-stress, we track our tasks in Launchpad.

Reporting a Bug¶

You found an issue and want to make sure we are aware of it? You can do so on Launchpad. There is no separate Launchpad for tempest-stress. More info about Launchpad usage can be found on OpenStack docs page

Getting Your Patch Merged¶

All changes proposed to the tempest-stress requires single Code-Review +2 votes as minimum from tempest-stress core reviewers who 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 QA is documented in QA Release Process.

So You Want to Contribute…