Ghanshyam Mann 1031cab577 [ussuri][goal] Update contributor documentation

This patch updates/adds the contributor documentation to follow
the guidelines of the Ussuri cycle community goal[1].

[1] https://governance.openstack.org/tc/goals/selected/ussuri/project-ptl-and-contrib-docs.html
Story: #2007236
Task: #38554

Change-Id: I5106dca0f379a9ced19ea209de460980d407345f

2020-04-22 14:04:58 +00:00

2.2 KiB

Raw Blame History

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 os-performance-tools.

Communication

IRC channel #openstack-qa at FreeNode
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 os-performance-tools 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 os-performance-tools, 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 os-performance-tools. More info about Launchpad usage can be found on OpenStack docs page

Getting Your Patch Merged

All changes proposed to the os-performance-tools requires single Code-Review +2 votes as minimum from os-performance-tools 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.

2.2 KiB Raw Blame History