============================ 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 Kolla. Basics ~~~~~~ The source repository for this project can be found at: https://opendev.org/openstack/kolla .. _communication: Communication ~~~~~~~~~~~~~ IRC Channel ``#openstack-kolla`` (`channel logs`_) on `OFTC `_ Weekly Meetings In the IRC channel (`meeting information`_) Mailing list (prefix subjects with ``[kolla]``) https://lists.openstack.org/pipermail/openstack-discuss/ Meeting Agenda :ref:`Meeting agenda ` Whiteboard (etherpad) Keeping track of CI gate status, release status, stable backports, planning and feature development status. https://etherpad.opendev.org/p/KollaWhiteBoard .. _channel logs: https://meetings.opendev.org/irclogs/%23openstack-kolla/ .. _meeting information: https://meetings.opendev.org/#Kolla_Team_Meeting Contacting the Core Team ~~~~~~~~~~~~~~~~~~~~~~~~ In general it is suggested to use the above mentioned public communication channels, but if you find that you need to contact someone from the Core team directly, you can find the lists in Gerrit: - `Kolla core team `__ - `Kayobe core team `__ New Feature Planning ~~~~~~~~~~~~~~~~~~~~ New features are discussed on PTG, via IRC or mailing list (with [kolla] prefix). Task Tracking ~~~~~~~~~~~~~ Kolla family projects track tasks and bugs in Launchpad: - `Kolla `__ - `Kolla Ansible `__ - `Ansible Collection Kolla `__ - `Kayobe `__ If you're looking for some smaller, easier work item to pick up and get started on, search for the 'low-hanging-fruit' tag in the relevant project. A more lightweight task tracking is done via etherpad - `Whiteboard `__. Reporting a Bug ~~~~~~~~~~~~~~~ You found an issue and want to make sure we are aware of it? Please report it in the appropriate Launchpad project: - `Kolla `__ - `Kolla Ansible `__ - `Ansible Collection Kolla `__ - `Kayobe `__ Note these are also used for task tracking. Getting Your Patch Merged ~~~~~~~~~~~~~~~~~~~~~~~~~ Most changes proposed to Kolla require two +2 votes from core reviewers before being approved and sent to the gate queue for merging. A release note is required on most changes as well. Release notes policy is described in :ref:`its own section `. Significant changes should have documentation and testing provided with them. To see an overview of in-progress patches, sorted into useful sections, you can view the: - `Kolla Review Dashboard `__ - `Kolla Ansible Review Dashboard `__ - `Ansible Collection Kolla Review Dashboard `__ - `Kayobe Review Dashboard `__ .. note:: If you feel that your change is getting overlooked, reach out via :ref:`preferred communication methods ` to let us know. Project Team Lead Duties ~~~~~~~~~~~~~~~~~~~~~~~~ All common PTL duties are enumerated in the `PTL guide `_. Kolla-specific PTL duties are listed in `Kolla PTL guide `_.