Browse Source

[ussuri][goal] Update contributor documentation

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

Story: #2007236
Task: #38554

Change-Id: I6feaa5e6ef9ec56094cbb725a44893aabb83dd24
Ghanshyam Mann 2 years ago
  1. 19
  2. 55
  3. 9


@ -0,0 +1,19 @@
The source repository for this project can be found at:
Pull requests submitted through GitHub are not monitored.
To start contributing to OpenStack, follow the steps in the contribution guide
to set up and use Gerrit:
Bugs should be filed on Launchpad:
For more specific information about contributing to this repository, see the
eslint-config-openstack contributor guide:


@ -0,0 +1,55 @@
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 eslint-config-openstack.
* IRC channel ``#openstack-qa`` at FreeNode
* Mailing list (prefix subjects with ``[qa]`` for faster responses)
Contacting the Core Team
Please refer to the `eslint-config-openstack Core Team
<,members>`_ contacts.
New Feature Planning
If you want to propose a new feature please read `Feature Proposal Process`_
eslint-config-openstack 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 eslint-config-openstack require single ``Code-Review +2`` votes
as minimum from eslint-config-openstack 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
.. _Feature Proposal Process:


@ -13,6 +13,15 @@ move between projects smoothly, and overall make the code more maintainable.
Even though eslint permits overriding rules on a per-project basis, it should be
the goal of every project to stay as close to the common guidelines as possible.
For Contributor
If you are a new contributor to eslint-config-openstack please refer: :doc:`contributor/contributing`
.. toctree::
Administrator's Guide