Ghanshyam Mann 4578f98944 [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: I870955fda7ee6e0d7809faa309bbc31c2ddd653a

2020-04-23 02:56:13 +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 Devstack.

Communication

IRC channel #openstack-qa at FreeNode
Mailing list (prefix subjects with [qa][devstack] for faster responses) http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss

Contacting the Core Team

Please refer to the Devstack Core Team contacts.

New Feature Planning

If you want to propose a new feature please read Feature Proposal Process Devstack features are tracked on Launchpad BP.

Task Tracking

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. More info about Launchpad usage can be found on OpenStack docs page

Getting Your Patch Merged

All changes proposed to the Devstack require two Code-Review +2 votes from Devstack core reviewers before one of the core reviewers can approve the patch by giving Workflow +1 vote. One exception is for patches to unblock the gate which can be approved by single core reviewers.

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