 the Narra Connect and who are you? I'm Mike Holmes, I'm the director of the core development team. So the core development team, that's the team that's in the core? Yeah, there's four teams. There's the kernel working group, security working group, power management, and virtualization. And they try to do the work that the segment groups, who really talk to the members, bring in that's common to everybody. So that's four groups that you are, what do you do with them? Well, yes, I guess, I'm the director. Fortunately, the tech leads of those four teams are very good. And within those teams, there are quite a few kernel maintainers themselves. So they're all talented, they don't need technical direction. So I try to do my best to connect the work they're doing to the members, so the members understand what's happening and can influence what they see as a core need to be solved. Do all the members really get it, really know what they want and what they would like things to go and do everybody agree? Or is there a lot of discussion going on all the time? Yeah, that's actually one of the things. So I've been in this role only since the Budapest Connect, about six months. And one of the things I was tasked with is improving exactly that, because historically, we haven't been good at communicating what we're doing. And so the members haven't been able to influence it or understand the benefits. You're doing a lot, right? The NINER is doing a lot. Yes, probably people are aware. We tend to score well in the top 10 of the Linux kernel contributions. And Opti was just merged with the kernels on the security side. Power management is now even tighter collaboration with ARM on the future things like dynamic and other technologies. So there's a lot happening. So what's your impression of the NINERO in the last six months? It's got a huge influence already, but it could be even bigger or it could be more targeted or there's many different things that could happen? It's driven by identified need. And I guess identified things are obviously, there's the ongoing IoT, there's automotive. So the real task for a NINERO is to find the interested members and understand where the common work is and start trying to upstream the solutions and pull people together. There's still some very big challenges ahead, right? There's still some big mountains to climb. But I think there's always the ongoing things. Members are trying to make money from things and they're trying to get value from the NINERO. So it's finding those pieces of the work which are common that they're happy to give away and work collaboratively on versus the pieces that have to be kept behind to make money. And do all the engineers have their own visions, kind of like ideas, what things should happen and stuff and you take this in and try to make it fit and make it work and all that stuff? I think so. I think, like I say, I'm lucky the teams I'm involved with, there are a number of maintainers and the tech leads are very talented at working the areas. So yeah, there's good opinions but also they're very familiar with working with lots of opinions. You work upstream, you get a lot of opinions.