Contributor Guide

This guide is for contributors of the Kolla project. It includes information on proposing your first patch and how to participate in the community. It also covers responsibilities of core reviewers and the Project Team Lead (PTL), and information about development processes.

We welcome everyone to join our project!

• So You Want to Contribute…
  • Basics
  • Communication
  • Contacting the Core Team
  • New Feature Planning
  • Task Tracking
  • Reporting a Bug
  • Getting Your Patch Merged
  • Project Team Lead Duties
• Kolla design philosophy
  • Do not own the deployed services’ config defaults (unless necessary)
  • Prefer documented configuration via config overrides
• Running Kolla Build in development
  • The recommended way to run in development
  • The alternative way to run in development
• Adding a new image
  • Distribution support
• Generating kolla-build.conf
• Release notes
  • Introduction
  • Templates and examples
• Running tests
  • Preferred way to run the tests
  • Running a subset of tests
  • Coverage Report Generation
  • Debugging unit tests
• Code Reviews
  • Core reviewers
• Bug triage
• PTL Guide
  • New PTL
  • Open Infrastructure Summit
  • Project Team Gathering (PTG)
  • After Summit & PTG
  • Day to Day
  • Release Management
  • Handing Over
• Release Management
  • Concepts & Aims
  • Release Schedule
  • Stable Branch Lifecycle
• Weekly Kolla team meeting
  • Agenda
  • Chairing a meeting
  • Previous meetings
• Continuous Integration
  • Distribution, architecture, build type coverage
  • Allowed to fail
• Versions of used components