- 1 Teams
Teams are groups of people sharing a common interest for a task or code subsystem in OpenStack.
Those teams work on a task that is common to every OpenStack core project.
Project Infrastructure team
- Launchpad team: https://launchpad.net/~openstack-ci
- Meeting: Project Infrastructure team meeting
- lead - mordred
- More information: ReleaseTeam
- Launchpad team: https://launchpad.net/~openstack-release
- Meeting: Project & Release status meeting
- lead - ttx
Stable Branch Maintenance Team
- Launchpad team: https://launchpad.net/~openstack-stable-maint
- lead - apevec/adam_g
- Launchpad team: https://launchpad.net/~openstack-community
- Join the mailing list if you're coordinating an OpenStack user group around the world
- lead - reed
Vulnerability Management team
- More information: VulnerabilityManagement
- Launchpad team: https://launchpad.net/~openstack-vuln-mgmt
- lead - ttx
Python3 Compatibility Team
- Launchpad team: https://launchpad.net/~openstack-py3-team
- lead - ewindisch
The Nova team meets weekly: Meetings/Nova. In addition to a project-wide Nova gathering each week, there are some sub-teams. These sub-teams get together to discuss work going on in a focused area of Nova.
Notes on Sub-teams:
- The linked wiki page should include:
- The mission of the team
- A regular meeting time
- A coordinator / point of contact
- Meeting Agenda
- Links to logs from previous meetings
- A sub-team representative should regularly attend the main Nova meeting to provide a sub-team status report.
- A sub-team is *not* exclusively responsible for an area of code. Anyone is welcome to contribute anywhere. However, you are encouraged to communicate regularly with others working in the same area as you and sub-teams help encourage that.
- A sub-team is about organizing development efforts, but not necessarily setting direction for the project in a given area. Review of patches is still done by the nova-core team and it is beneficial to publish designs to the openstack-dev mailing list for vetting in advance.