Berlin Summit videos are available now.  Catch up on everything you missed!     Watch now

May 2-4, 2019

Colorado Convention Center
Denver, Colorado



The Project Teams Gathering (PTG) is an event organized by the OpenStack Foundation. It provides meeting facilities allowing the various technical community groups working with OpenStack (user workgroups, development teams, operators, SIGs) to meet in-person, exchange and get work done in a productive setting. It lets those various groups discuss their priorities for the upcoming cycle, assign work items, iterate quickly on solutions for complex problems, and make fast progress on critical issues. The co-location of those various meetings, combined with the dynamic scheduling of the event, make it easy to get specific people in the same room to discuss a specific topic, or participate in multiple team meetings. Evenings allow for relationship building and problem sharing.


Who Should Attend

Developers / Operators / End Users

Upstream developers, cloud operators and end users who are involved with an OpenStack group that decided to meet at the PTG


Leaders from teams, SIGs, working groups that decide not to meet at the PTG should attend to represent the views of their group at the event.

Who Should Not Attend

The event is optimized for engaged community members that are involved in one of the various teams working with OpenStack (workgroups, development teams, SIGs…). If you’re brand new to OpenStack, you might want to attend the OpenStack Summit event instead, which features presentations, forum sessions (designed to get wider community feedback) and on-boarding sessions.

The event is not the occasion to sell goods or to propose jobs to the attendees -- hiring managers and product vendors will therefore also probably feel out of place.

How can this benefit my organization?

Our community is global. This creates challenges that cannot easily be solved using asynchronous, low-bandwidth communication tools. Getting technical community members to meet in-person regularly is essential to build the amount of shared understandings and trust that is necessary to successfully cooperate. Participants to the event are therefore a lot more productive and efficient the rest of the year.

PTG’s are organized in cost-effective transportation hubs in order to minimize travel expense. At the same time, we aim to maximize the ability of contributors to work through their workgroup objectives in an environment that is focused towards work and productivity.

Code of Conduct

All attendees of the OpenStack Project Teams Gathering must follow the OpenStack community Code of Conduct.

Frequently Asked Questions

Q: What is the price of registration?

A: Ticket prices for this PTG will be announced soon.

Q: Are OpenStack operators welcome to the PTG?

A: Yes! Engaged operators and developers are all contributors helping to make OpenStack better. If the teams, workgroups or SIGs they are involved with are taking the opportunity to meet at the PTG, all team members should join to get work done with their co-workers.

Q: Which groups can meet at the PTG?

A: Contributing to OpenStack and helping to make it better comes in various shapes and forms. We have upstream project teams, User Committee working groups, Special Interest Groups (SIGs), pop-up work groups around a specific issue, and other styles of teams. Event organizers have taken a pretty liberal approach as to which group can request a “track” at the event: if you’re engaged and openly collaborating to make OpenStack better, your team can meet at the PTG!

Q: Is my workgroup forced to meet at the PTG?

A: Each team is free to decide if they want to leverage the PTG to meet in-person or not. Sometimes a team is small, or dominated by one organization, or coming from the same far-away geographic region and it does not make much sense for team members to travel to the PTG to meet. And sometimes it would benefit from getting together to build trust and get work done more effectively over the next 6 months. The decision to participate is theirs.

We still encourage leaders and cross-team liaisons from all workgroups to participate to the event to represent their team, whether their team actually meets at the PTG or not

Q: Why are you running PTGs separately from Summits?

A: In the past, the OpenStack community has published the latest release, hosted the OpenStack Conference, and held the Design Summit for contributors to plan the next version—all in the same feverish, two-week timespan. There have been a few problems with this approach. It has been hard on users because there was very little time get acquainted with the new release before the conference. It has been hard for strategic discussions, because they happened too late in the cycle to be taken into account. It has been hard on contributors, torn between the opportunity to reach out beyond their team, and the necessity to get a lot of things done with your team. And it has been hard on downstream companies who are working to build product based on the new releases.

As a result, we moved Summits further away from release dates, and focus on cross-community communication and strategic discussions there. We created a separate event at the start of the development part of the release cycle for team meetings in a productive, distraction-free setting.

Q: Why are you merging the Ops Meetup with the PTG?

A: The Ops meetup is a bi-annual event where operators get together to discuss common pain points and priorities, and meet within working groups to get work done. It happened a few weeks away from the PTG, in a different location. It made it quite costly to travel to both events, and therefore discouraged operators from participating in other work groups and SIGs that were meeting at the PTG (or the other way around). The format of the Ops meetup being compatible with the format of the PTG, the User Committee decided to try to run the Ops meetup at the PTG.

Q: What is the Forum?

A: Forum is the name for the part of the Design Summit (Ops+Devs) that still happens at the main Summit event. It is primarily be focused on strategic discussions and planning for the next release (the “what”), essentially the start of the next release cycle even though development will not begin for another 3 months. We should still take advantage of having all of our community (Devs, Ops, End users…) represented to hold cross-community discussions there. That means getting feedback from users and operators over specific projects in our last release, gathering pain points and priorities for upcoming development, proposing changes and see what the community thinks of them, and recruiting and onboarding new team members. We will do that in a neutral space (rather than have separate “Ops” and “Dev” days) so that the discussion is not influenced by who owns the session. This event will happen at least two months after the previous release, to give users time to test and bring valuable feedback.

Q: What is the difference between PTGs and Forums?

A: he Forum is a part of the OpenStack Summit event. It’s organized in 40-min slots to discuss specific topics. The Forum takes advantage of having a larger cross-section of our community present to gather wide feedback on strategic issues, helping to shape the future of OpenStack and set priorities. At the Forum, we discuss the “what”, we take the pulse of the community, we engage outside of our existing teams and established contributor base.

In contrast, the PTG is more to discuss within our teams, between people engaged to actively work on making OpenStack better. At the PTGs, we discuss the “how”, get agreement, build trust, assign work items and get work done. Of course there is a grey area and some key topics end up being discussed in both venues.

Q: Are ops and devs still needed at the main Summit?

A: Operators and developers are still very much needed at the main Summit. The Summit is where all of the OpenStack community gets together and where the feedback loop happens. All OpenStack teams need to be represented there, to engage in strategic discussions, collect the feedback on their project, communicate about their group work, discuss cross-community topics, reach out to new people and onboard new developers. We also very much want to have operators and developers give presentations at the conference portion of the Summit.

Q: The Project Teams Gathering sounds like a huge event. How am I expected to be productive there? Or to be able to build social bonds with my small team?

A: Project Teams Gatherings are much smaller events compared to Summits (think 400 people rather than 5000). Each workgroup is allocated a specific, separate meeting area, in which they will be able to organize their schedule and work however they see fit. Past attendees have described the PTG as one of the most productive events they ever attended. The only moment where everyone meets is around lunch. We organize a limited number of social events (happy hours, karaoke, game night) and encourage teams to organize team dinners and build strong social bonds.

Q: I heard that you were reconsidering Project Teams Gatherings for 2019. What is the future of this event?

A: Project Teams Gatherings are very popular with attendees, who praise the productivity of the event coming from a distraction-free environment. However, not everyone can attend the event, especially when they need to prioritize attendance to the Summit for business reasons. Those contributors feel excluded, and would prefer if the PTG would happen directly around (or concurrently to) Summits.

Holding Project Teams Gatherings is therefore a complex trade-off between productivity and inclusion. After having held 3 of those events (and committing to hold a 4th one in September 2018), the OpenStack Foundation is gathering wide feedback before deciding on the 2019 strategy.

Want to find out more?

Most questions can be answered by reading the PTG FAQs. Still more questions? Email [email protected] or add your email below to be kept up to date with the latest about Project Teams Gathering.

Thank you for your interest in the Project Teams Gathering.
You will be notified of any important updates.