 Hi, I'm Shamal Bahir and I'm here with the Mitaka series. We're about a week after design summit so far and today with me, I've got Dim. Dim, please tell us a little bit about yourself. My name is Devanam Srinivas. My nickname is Dim. I'm the project technical lead for Oslo project for the Mitaka cycle. I work for Merantys. I work from home just south of Boston. Great. Thank you. And today we'll be talking a little bit about Oslo. So Dim, what were the hot topics that the Tokyo Design Summit for your project? Oslo is really a family of projects. So we talked about some old projects, some new projects, and some drivers for new projects, some old projects as well. Got it. And what did you identify as user needs or problems to solve in the upcoming release? Yeah, this time we concentrated on a few things. One was feedback from operator summit. The other one was how we work closely with the logging and security work groups and also ongoing feedback in terms of bugs and things like that that come our way to construct some really good answers to the ongoing problems that we see in different projects. Got it. And what are the top three priorities for new features and enhancements and then the top three that we can accept from Oslo? So there's a few things coming down the pike. First of all, we are trying to evangelize some of the existing projects that we have built over the last few cycles. One example is Taskflow. Taskflow is for making distributed systems easier. And a new project example would be we are trying to come up with a new idea about how to solve the privilege mechanism problem previously that we used Oslo root rap project for. That's another one. The third one is how do we introduce distributed locking mechanisms in different projects by using things like zookeeper which will help with, you know, sharing locks, service existence and things like that. And what are some of the key things that your project will apply to Mitaka? One important theme that came out of operators was hardening the messaging infrastructure. So in Mitaka, we will be working on Oslo messaging a lot. We are introducing new drivers for zero MQ, probably a driver for Kafka, at least for notifications. We will be working on a new Oslo messaging driver that uses a brand new library called Vika that we haven't used before. All these are an attempt to stabilize the infrastructure so we can scale out to a huge number of nodes, or compute nodes for example. Anything else that you'd like to add that we didn't mention? Typically Oslo developers work primarily on other projects with larger code bases. So we tend to be folks who work part-time on things that we really care about at Oslo. So we welcome folks to start and contribute and we usually quickly promote them as a course. Great. Well, thank you so much for your time, James. Thank you, Shamay.