OpenStack Project Team Guide

Contents:

• Preface: Project Creation
• Introduction: A Bit of OpenStack History
  • The origin
  • The mission
  • The Four Opens
  • A quick history of OpenStack governance
• Open Source
  • Fully Functional Open Source
  • Acceptable Licensing
  • Dependencies and Optional Modules
• Open Community
  • Public Meetings on IRC
  • Project IRC Channels
  • Mailing Lists
  • Community Support Channels
  • Planet OpenStack
  • Technical Committee and PTL Elections
• Open Design
  • Common development cycle
  • Forum
  • Project Teams Gathering
  • Sprints
• Open Development
  • Project Team Lead
  • Core Reviewers
  • Reviews Guidelines
  • Specifications
• How to Review Changes the OpenStack Way
  • Code Review +2
  • Code Review +1
  • Code Review 0
  • Code Review -1
  • Code Review -2
  • Workflow -1
  • Follow-up Changes
  • Modifying a Change
• Repository Handling
  • Project Renames
  • Retiring a Repository
  • Deprecating a Repository
• Release Management
  • Deliverables handled by the Release management team
  • Release cycle
  • Choosing a release model
  • How to release ?
  • Release Liaisons
  • Typical Development Cycle Schedule
  • Managing Release Notes
  • Cycle Highlights
• Release Cadence Adjustment: SLURP Model
  • History
  • Challenges
  • Proposed Solution
  • Details
  • Example sequence
• Stable Branches
  • Maintenance phases
  • Appropriate Fixes
  • Stable maintenance teams
  • Review guidelines
  • Processes
  • Project teams which asserted they follow the stable branch policy
• Other branches
  • Feature branches
  • Bug Branches
  • Driverfixes Branches
• Bugs
  • Bugs Reference
  • Bugs lifecycle
• Vulnerability Management
  • Vulnerability Management Team
  • Embargoed Vulnerability Management
  • Public Vulnerability Reports
  • Security Contacts
  • Security Enhancements
• Dependency Management for OpenStack Projects
  • Why do we have a global requirements list?
  • Solution
  • Update Processes
  • Review Guidelines
  • Tools
  • Tox & Stable Branches
  • Resources
• Testing (QA and CI)
  • Types of Tests
  • Automated Test Systems
  • Project Gating
  • How to Handle Test Failures
• Oslo
  • Libraries
  • Brief History
  • The Incubator
  • Liaisons
  • Naming Libraries
• Documentation
  • Documentation for Contributors
  • Documentation for Developers
  • Documentation for Operators and Users
  • How to Contribute Documentation
• Internationalization and Translation
  • Translation Platform
  • Translation of Documents
  • Translation of Repositories
  • Translation priorities
• Becoming a Project Team Lead (PTL)
  • Recurrent tasks
  • Core member maintenance
  • At the beginning of a new cycle
  • During the cycle
  • Conference and event tasks
  • At the end of the cycle
  • Collecting feedback
  • Stable
  • One offs
  • Tips and tricks
  • Handing over PTL duties
• Spreading the Word
  • Live Streams
  • Blogging
• Common Terms
• Deprecation
  • Justification for careful deprecation
  • Guidelines
• Technical Guides
  • Using Unified Limits
  • Base services
  • API guidelines
  • Best practices for project setup
• Legal Issues FAQ
  • Frequently Asked Questions

Indices and tables

• Search Page