 Hi, welcome to SuperUserTV here at the OpenStack Summit Boston. Please go ahead and introduce yourself. Hello, my name is Thierry Caraz. I am the vice president of engineering for the OpenStack Foundation and also the chair of the OpenStack Technical Committee. Awesome, welcome. So with these work streams that you all are doing, what is the objective of your particular strategic focus work stream? So the work stream, one of the work streams we have identified is the need for better communications around what is OpenStack. And because we used to have this very long list of 60 projects, we don't really know how they relate to each other. It's really hard to communicate around that. And so one of the work streams that was identified during that workshop that united the board of directors, the technical committee, the user committee around the same table is the need for clearer communication about what is OpenStack. And part of the solutions that we looked into were producing more of a mapping experience, like producing a set of maps that will help clarify exactly how everything relates to everything else. And not just one map, but more a collection of maps because you always have so much you can express in a single map. So like we're thinking about a project map that would show what is the core infrastructure pieces, what are the services that are facilitating consumption of that stack, what are the services that are facilitating operating that stack, what are the services that are packaging or helping deploy the stack, and basically what are the teams that are helping all the other teams to achieve those objectives. And once you start mapping them out this way becomes way more clearer exactly how everything fits. And it's a lot less intimidating than a long list of 60 projects. Definitely. So you kind of touched on this. So what has your team learned since you identified this as a problem that needed to be fixed? Well, we learned that the exercise of mapping is as much about what you include in a map as it is about what you leave out of the map. And so that's why we came up with a set of maps rather than trying to cram everything on a single map. The other thing that was pretty apparent during those discussions was that we also need to move away from all the terminology around the big tent, which introduced more confusion than clarity about what exactly we meant by that. So that means we're talking now about official projects and official projects, but we will probably move to official OpenStack projects on one side and projects that are hosted on OpenStack infrastructure just being hosted on the OpenStack infrastructure side. So try to move away from confusing terms that are not really helpful in the discussion and map more clearly exactly how everything fits. Okay, and so what are the next steps after the summit that this team will take? So for the mapping exercise, we identified two maps that we can immediately work on. The first one is that in the hands of designers now, like trying to turn my diagrams into something more pretty to look at. Another is more at the design phase where we are trying to exactly show how we can represent maturity versus adoption in a 2D graph to get people excited about projects that are functionally complete, but are not necessarily having the degree of adoption as are more popular projects. Try to make clear which of those 60 projects, those promising projects, up and coming projects are so that people can start more actively looking to those in terms of adoption. Okay, and so where could people who are hearing you talk about this now, where can they learn more after this about the outcomes and then the progress that you all are making? Where can we learn more about it? So we'll try to turn the mapping exercise to more of a community maintained map because there is no reason why those maps should be essentially produced. So I expect us to try to find a way to produce those maps out of the community input and feedback rather than just being built out of the blue. It's difficult because there is like a design step there that you want to produce maps that are also nice to look at. So we need to figure out exactly how to do that. And we also, we should expect a number of changes being proposed to the technical committee as well for migrating the vocabulary away from the Big Ten terminology to a more direct meaning of the words like a hosted project, official projects. So that is clear exactly what they mean. We need to purge the documentation of the whole terminology. So a number of changes that will be up for public review on our Garrett code review system. So like the community can get involved in that step. Awesome. Well, thank you for joining us today on SuperUserTV and we look forward to learning more. Thank you.