openstack/openstack-helm-infra
Code Issues Proposed changes
6f576b2db7
openstack-helm-infra/doc/source/contributor/contributing.rst
Roman Gorshunov e4096d84e7 Add Project Specific Contributor and PTL Docs 
This patch amends contributor guidelines for the Ussuri goals.

Change-Id: Idc88bf4e0f6e41c2ac1b89c700314cd9038982d4
Task: 38545
Story: 2007236
2020-04-24 20:59:44 +02:00

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

Additional information could be found in OpenDev Developer's Guide.

Below will cover the more project specific information you need to get started with OpenStack-Helm infra.

Communication

  • Join us on IRC: #openstack-helm on freenode
  • Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on freenode
  • Meeting Agenda Items: Agenda
  • Join us on Slack
    • #openstack-helm

Contacting the Core Team

Project's Core Team could be contacted via IRC or Slack, usually during weekly meetings. List of current Cores could be found on a Members tab of openstack-helm-infra-core Gerrit group.

New Feature Planning

New features are planned and implemented trough the process described in Project Specifications section of OpenStack-Helm documents.

Task Tracking

We track our tasks on our StoryBoard.

If you're looking for some smaller, easier work item to pick up and get started on, search for the 'low-hanging-fruit' tag.

Other OpenStack-Helm component's tasks could be found on the group Storyboard.

Reporting a Bug

You found an issue and want to make sure we are aware of it? You can do so on our Storyboard.

If issue is on one of other OpenStack-Helm components, report it to the appropriate group Storyboard.

Bugs should be filed as stories in Storyboard, not GitHub.

Getting Your Patch Merged

We require two Code-Review +2's from reviewers, before getting your patch merged with giving Workforce +1. Trivial patches (e.g. typos) could be merged with one Code-Review +2.

Changes affecting code base often require CI tests and documentation to be added in the same patch set.

Pull requests submitted through GitHub will be ignored.

Project Team Lead Duties

All common PTL duties are enumerated in the PTL guide.