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.
The source repository for this project can be found at:
- IRC Channel
- Weekly Meetings
On Wednesdays at 14:00 UTC in the IRC channel (meetings logs)
- Mailing list (prefix subjects with
- Meeting Agenda
- Whiteboard (etherpad)
Keeping track of CI gate status, release status, stable backports, planning and feature development status. https://etherpad.openstack.org/p/KollaWhiteBoard
Contacting the Core Team¶
In general it is suggested to use the above mentioned public communication channels, but if you find the you need to contact someone from the Core team directly, you can find the lists in Gerrit:
New Feature Planning¶
New features are discussed via IRC or mailing list (with [kolla] prefix). Kolla project keeps blueprints in Launchpad. Specs are welcome but not strictly required.
Kolla project tracks tasks in Launchpad. Note this is the same place as for bugs.
If you’re looking for some smaller, easier work item to pick up and get started on, search for the ‘low-hanging-fruit’ tag.
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? You can do so on Launchpad. Note this is the same place as for tasks.
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 its own section.
Significant changes should have documentation and testing provided with them.