 Hi, I'm Heidi Joy Trethewey with the OpenStack Foundation and I'm here with my colleague Terry Perez, who is vice president of engineering for the OpenStack Foundation. And Terry, thank you, today we're talking about Stackalytics. So thanks for joining us. Can you tell us a little bit what is Stackalytics, first of all? Yeah, so Stackalytics is a website that has all kind of metrics on contributor activity like number of commits, number of reviews, which company or organization they're affiliated with and so that that's a convenient website to go to to get an idea of like who is contributing to a given project or what are the projects that some contributors are working on. Yeah, and so can you give us a little background about the history of Stackalytics and where we're at now? So it was originally created by Mirantis as like an independent source of information to get an idea of which companies were leading on which development, which project and it was migrated to the OpenStack infrastructure project. So now it's more run by the OpenStack infrastructure team, but it's still heavily maintained by people that come out of Mirantis originally and it's basically evolved from where it was before to the current situation. So here at the summit and the forum we're talking about Stackalytics. What are some of the discussions about it? So it was one topic of discussion we had, so we did a 40-minute session on the future of Stackalytics because on the one hand it's a very convenient way to get numbers on the projects but on the other hand it also provides wrong incentives to contribute to projects so you end up with a lot of like empty commits or empty reviews just so that your scores go up and so as a way to incentivize the right behavior it's not working at all for us. So the discussion was about should we keep Stackalytics? Should we evolve it? What should we do with it? And it was a lively discussion with lots of various opinions like engineering team managers saying that they actually rely on that to get an idea of what their teams are working on or developers complaining about those type of commits that are not really useful and then are incentivized by the current Stackalytics forms. And the conclusion of that discussion we managed to get to reach some kind of a consensus at the end was that we should probably not kill Stackalytics because like metrics having numbers is good but we should definitely make another way of driving the right behavior emerge like have a list of strategic goals that people could sign up for doing and give proper credit to those who actually signed up for that so that we have more of a strategic approach to contribution rather than very tactical numbers and then finalize the migration of Stackalytics to the OpenStack infrastructure team because it's still work in progress and then maybe retire the most deceiving graphs that are produced out of Stackalytics because we have like graphs by default that show commits over all the OpenStack projects and it's like adding apples to oranges and the numbers don't really add up or so yeah we'll probably evolve Stackalytics and complement it with something that drives better behavior or more useful behavior for our community. Yeah so I'm hearing you say some of the structure of Stackalytics and the rewards that are attached to Stackalytics kind of invites people to game the system as well as some of the ways that it's set up are not necessarily comparable you can't you can't compare them well tell me more generally looking at the forum itself I've been hearing in the hallway is a lot of folks talking about how often they're seeing users and developers talking face-to-face and how great that is what are some of your impressions on how the forum has gone now that we're we're here on Thursday just kind of wrapping up the summit I think it's been great because we had that invisible barrier between operators and developers in previous design summits mostly because the space was branded either operator or developer and that created that created a sense that some people were just invited in the session and not really part of it and the new branding around around a forum event where everyone is welcome to participate to the discussion as long as they're interested in the topic really removed that invisible barrier and it's like a single team working together toward a goal where like two different groups trying to have competing interests around it like an anecdote we that we used to have lots of us versus them discussions in those in those rooms and during this week it's only always we like we as a group need to reach an objective so perception matters those invisible barriers heard us in the in the past and I'm I'm happy to see that the forum has been just reformatting how would think about those events I would communicate about them was enough to drive the right type of collaboration between those two groups so it's a huge leap of faith on your part of the foundations part to really change up this whole development process and cycle as well as the structure of the forum and then the newly launched project teams gathering what what do you think is maybe a misconception that you're helping to clear up now people misinterpreting I see still quite a few questions so what what would you share to help people think about the forum and the next project teams gathering that's that's coming up in September so the forum is really for everyone in the community to get together like we have representation of all the segments of our community so developers on open stock developers and other open source projects users of open stack clouds operators and employers of open stack clouds or or or like people are just just have vendors that have products built on open stack it's really the unique opportunity to hear from from everyone and and so having the forum and removing the work sessions that the developers used to do during the semi-tweak is really freeing up a lot of time for everyone to engage with with another and and during this week it was pretty obvious that everyone had more time to engage reach out to other people from different origins in our community and that was really good so we invite we need to have developers coming to the summit we need to have everyone in the community come into the summit especially if you're originally close to to the area where where the the next summit happens you should should take the opportunity to join there the project team gathering is slightly different approach it's it's more for project teams to get together to organize the work for the for the upcoming development cycle so it's more like a work environment if you're part of a team if you if you identify as a part of the team then you will be much more productive if you spend that week at the beginning of cycle with all your other team members so it's a way to meet the way to to drive productivity in those teams so it's more a question of employers sending whoever is participating to those teams to send them to that event to to make sure that they're actually given all the chances to be very productive over the next six months it's slightly different approach a slightly different theme and and slightly different vibe as well like much more work work at the ptg much more like engagement community reach out to the discussions here and I think to have two events complement one each other yeah very good well thank you very much and we're looking forward to seeing more what comes out of the forum sure thank you