============================
So You Want to Contribute...
============================
For general information on contributing to OpenStack, please check out the
`contributor guide <https://docs.openstack.org/contributors/>`_ 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 freezer-api.

Communication
~~~~~~~~~~~~~
* IRC channel #openstack-freezer at OFTC
* Mailing list (prefix subjects with ``[freezer]`` for faster responses)
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss

Contacting the Core Team
~~~~~~~~~~~~~~~~~~~~~~~~
Please refer the `freezer-api Core Team
<https://review.opendev.org/admin/groups/489539270c16cfb7990bb3f1a0f62f3e45a94635,members>`_ contacts.

New Feature Planning
~~~~~~~~~~~~~~~~~~~~
freezer-api features are tracked as `Specs <https://specs.openstack.org/openstack/freezer-specs/>`_.
You can submit new spec file to the `repository <https://opendev.org/openstack/freezer-specs>`_.

Reporting a Bug
~~~~~~~~~~~~~~~
You found an issue and want to make sure we are aware of it? You can do so on
`Launchpad <https://bugs.launchpad.net/freezer>`_.

Getting Your Patch Merged
~~~~~~~~~~~~~~~~~~~~~~~~~
All changes proposed to the freezer-api project require one +2 votes
from freezer-api core reviewers with approving patch by giving
``Workflow +1`` vote.

Project Team Lead Duties
~~~~~~~~~~~~~~~~~~~~~~~~
All common PTL duties are enumerated in the `PTL guide
<https://docs.openstack.org/project-team-guide/ptl.html>`_.
