(upbeat music) >> Narrator: Live, from Boston, Massachusetts, it's theCube! Covering Red Hat Summit 2019. Brought to you by Red Hat. >> Welcome back, live here on theCube, as we continue our coverage here of Red Hat Summit, along with Stu Miniman, I'm John Walls. It's great to have you here, in one of America's great cities! We're in Boston, Massachusetts, for day one of the three-day conference. And we're now joined with Denise Dumas, who is with Red Hat, and working on the RHEL 8 release that just became, I guess, available today, right? >> Today! >> Huge news! >> Yes! >> I have to first of compliment you on rocking these Red Hat red earrings. And then I look down below you've got the Red Hat sneakers on too, so you are company-branded >> Absolutely. >> up and down, literally, from head-to-toe. >> I'm very proud of the earrings, because some of the support guys made them up on their 3D printer back at the office. >> John: How cool is that? >> I love it. >> Now we had Stefanie Chiras on a little bit earlier, and we were talking about RHEL 8 and all that came with that, and we talked about the deeper dive we're gonna take with you a little bit later on, now we're at that moment. Just first off, in general, how do you feel when something like this finally gets out of the beta stage, gets moved into a much more active space, and now it's available to the marketplace? >> It's like fresh air, right? >> Thrilled. >> Oh, thrilled. Well, you know, and in a way, it's almost an anti-climax, because we're working on 8.1 already, and we're talking about RHEL 9, but this is just such an opportunity to take a moment, especially for so many of the RHEL engineering and QE team who are wandering around the summit, and for us all to just kind of say, (sighs) it's out. It's out, let's see if they like it, I hope they do. But you know, we've been working with so many of the customers and partners through the High Touch Beta Program, 40,000 downloads of the beta, and it has been tremendous feedback. We've been really pleased to see how many people are willing to pick it up and experiment with it, and tell us what they like and what they don't like. >> So Denise, it's always great to hear the customers, but take a second and celebrate that internal work, 'cause so much code, so many engineers, years worth of planning and coding that go into this, so give us a little but of a look behind the curtain, if you would. >> Well, you know so much community as well, right, because, like everything else that Red Hat does, it's totally Open Source. So, many communities feed into Fedora, and Fedora feeds into RHEL, so we took Fedora 28, and pulled it in, and then did a lot more work on it, to try to move it into, this year, we've done the distro differently. There's a core kernel, the noodles, you know, and then there are the application streams. So we've done a lot of work to separate out the two types of package that make up RHEL, so that we can spin the application streams faster. That's where things like developer tools, and language runtimes, databases, the things that are more aimed at developers, where a ten-year life cycle is not a natural for those, right, and yet the core of RHEL, the kernel, you rely on that, we're gonna support it for ten years, but you need your application streams to keep the developers happy. So we tried to make the admin side happy, and the developer side happy. >> All right so, as Vice President of Software Engineering, your team had, certainly, its focuses along this way. >> Denise: Oh, yeah. And dealing with, I guess, the complexities that you were, was there maybe a point in the process where you had an uh-oh moment, or, I'm just curious, because it's not always smooth sailing, right, you run into speed bumps, and some times there're barriers, they're not just bumps, but in terms of what you were trying to enable, and what your vision was to get there, talk about that journey from the engineering side of the equation, and maybe the hiccups you had to deal with along the way. >> So, RHEL 8 has been interesting because in the course of putting the product together, the RHEL organization went through our own digital transformation. So just like our customers have been moving to become more agile, the RHEL engineering team, and our partners in QE, and our partners in support, have worked together to deliver the operating system in a much more agile way. I mean, did you ever think you would hear agile and operating system in the same breath, right, it's like, wow. So that has been an interesting process, and a real set of challenges, because it's meant that people have had to change work habits that have served them well for many, many years. It's a different world. So we've been very fortunate to take people through a lot of changes, they've been very flexible. But there have been some times when it's just been too much too fast, like (gasps), And so it's like, everybody take a deep breath, okay, will do. You know, a couple of weeks, we'll consolidate. It's been a really interesting process. Clearly the kernel, so we've got the 4.18 kernel, and the kernel comes in and we have to understand what the kernel configuration is gonna be. And that can be a lengthy process, because it means you have to understand, when you pull a kernel out of the upstream some of the features are pretty solid, some are maybe less solid. We have to make an educated call about what's ready to go and what's not. So figuring out the kernel configuration can take a while. We do that with our friends in the performance team. And so every inch of the way, we build it, we see how the performance looks, maybe we do some tweaking, change that lock, everything we do goes back upstream, to make the upstream kernel better. So that, as well, has been an interesting process, because there's a lot of change. We're really proud of the performance in RHEL 8, we think that it's a significant improvement in many different areas. We've got the Shack and Larry Show tomorrow, we'll talk all the way through performance, but that's been a big differentiator, I think. >> All right so, Denise, security, absolutely is at top of mind always? >> Denise: Always. >> Some updates in RHEL 8, maybe if you walk us through security and some of the policy changes. >> Yeah, we bake security in, right, we have a secure supply chain, and, talk about difficult things for RHEL 8, right, every package that comes in, we totally refresh everything from upstream. But when they come in, we have to inspect all the crypto, we have to run them through security scans, vulnerability scanners, we've got three different vulnerability scanners that we're using, we run them through penetration testing, so there's a huge amount of work that comes just to inherit all that from the upstream. But in addition to that, we put a lot of work into making sure that, well, our crypto has to be FIP certified, right, which means you've got to meet standards. We also have work that's gone in to make sure that you can enable a security policy consistently across the system, so that no application that you load on can violate your security policy. We've got nftables in there, new firewalling, network-bound disk encryption, that actually, it kind of ties in with a lot of the system management work that we've done. So a thing that I think differentiates RHEL 8 is we put a lot of focus on making it easy to use on day one, and easy to manage day two. It's always been interesting, you know, our customers have been very very technical. They understand how to build their golden images, they understand how to fine-tweak everything. But it's becoming harder and harder to find that level of Linux expertise. I'll vouch for that. And also, once you have those guys, you don't want to waste their time on things that could be automated. And so we've done a lot of work with the management tooling, to make sure that the daily tasks are much easier, that we're integrated better with satellite, we've got Ansible system roles, so if you use Ansible system roles we wanted to make it easy, we wanted to make the operating system easy to configure. So the same work that we do for RHEL 8 itself also goes into Red Hat Enterprise Linux core OS, which will be shipping with OpenShift. So it's a subset of the package set, same kernel. But there it's a very, very focused workload that they're gonna run. So we've been able to do a really opinionated build for RHEL core OS. But for RHEL 8 itself, it's got to be much more general purpose, we've focused on some of our traditional workloads, things like SAP, SAP HANA, SQL Server, so we've done a lot to make sure that those deploy really easily, we've got tuning profiles that help you make sure you've got your system set up to get the right kind of performance. But at the same time, there are lots of other applications out there and we have to do a really good general-purpose operating system. We can be opinionated to some extent, but we have to support much, much wider range. >> Yeah, I mean, Denise, I think back, it's been five years since the last major release. >> Yeah. >> And in the last five years, you know, Red Hat lived a lot of places, but, oh, the diversity of location in today's multi cloud world, with containerization and everything happening there, and from an application standpoint, the machine learning and new modern apps, there's such breadth and depth, seems like in order of magnitude more effort must be needed to support the ecosystem today than it was five years ago. >> Well, it's interesting that you say ecosystem, because you don't play in those places without a tight network of partnerships. So we have lots, of course, hardware partnerships, that's the thing that you think about when you think about the operating system, but we also have lots of partnerships with the software vendors. We've done a lot of work this year with Nvidia, we've supported their one and two systems, right, and we've done a lot to make sure that the workloads are happy. But, increasingly, as ISVs move to containerize their applications, when you containerize you need a user space that you bring along with you, you need your libraries, you need your container runtime. So we've taken a lot of the RHEL user space content, and put it into something that we're calling the Universal Base Image. So, you can rely on that layer of RHEL content when you build your container, put your application into a container. You can rely on that, you can get a stream of updates associated with that, so you can maintain your security, and when you deploy it on top of RHEL, we're with OpenShift, we can actually support it well for you. >> Walk me through the migration process, a little bit, if I'm running 7, and I'm shifting over, and I'm gonna make the move, how does that work? >> Denise: Carefully (laughs). >> Yeah sure, right. (laughs) 'Cause I've got my own concerns, right, I've got-- >> Of course! >> Sure, I've got to think, daily operation, or moment-to-moment operation, I can't afford to have downtime, I've got to make sure it's done in a secure way, I've got to make sure that files aren't corrupted, and things aren't lost, and, so that in itself is a, teeth-gnashing moment I would think, a bit, how do you make that easier for me? >> Yeah, well, especially when you've got 10,000 servers that you need to manage, and you want to start migrating them. You absolutely have to come to tomorrow morning's demo, we're gonna do, it's live! >> It's always tricky, right, live is always, yeah. >> Yeah, but migration, so we've put a lot of effort into migration. We're looking at, it's no good if the applications can't come along, why would you migrate the operating system, you wanna migrate the application. So we've got tooling that examines your environment, and tries to automate as much of it as we can. It looks at your existing environment, it looks at what you're gonna move through, it'll ask a few questions, it's totally driven by plug-in equivalents, we call them actors, and they understand the various, like one understands how to do network configuration, one understands how to replicate your disk configuration. It's integrated with automated backup and rollback, which is a thing that people have wanted for a long time so that we've got a much tighter level of safety there. We won't be able to migrate everything, I'm sure, but, as time goes along we add more and more and more into that utility as we learn more about what matters to customers. >> So, tomorrow morning, live demo. >> Denise: Live demo! >> Get a good night's sleep tonight! >> Denise: Put on your crash helmets! >> Fingers crossed. But thanks for joining us here and talking about the RHEL 8, about the rollout, and we wish you well with that, off to a great start for sure. >> Thank you so much, >> Thank you Denise. >> the RHEL teams are amazing, I love my guys. >> Great, thanks for being with us. >> Denise: Thank you so much. >> We'll continue here at the Red Hat Summit. You're watching theCUBE, live from Boston. (upbeat music)

>> Announcer: Live from San Francisco, it's theCUBE, covering Red Hat SUMMIT 2018, brought to you by Red Hat. >> Okay welcome back everyone. We are here live in San Francisco at Moscone West. This is theCube's exclusive coverage of Red Hat SUMMIT 2018. I'm John Furrier, co-host of theCube. This week John Troyer, guest analyst, he's the co-founder of TechReckoning, an advisory and consulting firm around community. Our next guest Matt Hicks, Senior Vice President of Engineering at Red Hat. He's going to give us all the features, and specs of the road map, and all the priorities. Thanks for coming on. >> Hey, thanks guys. >> John: He's like, "I'm not." >> So thanks for comin' on, obviously a successful show for you guys, congratulations. >> Matt: Thank you Paul Cormier was on earlier talking about some of the bets you guys made and it's all open source, so those bets are all part of the community, with the community. But certainly there's a big shift happening, we're seeing it now with containers, and Kubernetes really showing the way, giving customers clear line of sight of where things are startin' to fall in the stack. Obviously you got infrastructure and application development all under a DevOps kind of concept, so congratulations. >> Thank you, thank you, it's been fun, it's been, I think Paul shared this a couple weeks, we started OpenShift in 2011, so it's pretty cool to be here now, 2018, and just see how far that's come in terms of how many customers using it, how successful they've been with it. So that's, it's been great. >> Yeah we always like to talk on theCube, we love talkin' to product people and engineers because we always say the cloud is like an operating system. It's just all over the place, decentralized network, distributing computing, these are concepts that have been around. A lot of the Red Hat DNA comes from systems, you have SELinux operating system, that you offer for free but also have services around it. It's a systems problem as we look at the cloud, cloud economics. So when you go look at some of the product and engineering priorities, how do you guys keep that goin'? What are some of the guiding principles that you guys have with your team? Obviously open-source, being in up-stream projects, but as you guys have to build this out in realtime, what are some of the principles that you guys have? >> That's a great, that's a great question. I'll try to cover it on two areas. I think the first for us is workload compatibility, where you get down into the, building that new apps is great, it's fun, a lot of people can do it, and that's an exciting area. The customers also, they have to deal with apps they built over 10 plus years, and so in everything we design, we try to make sure we can address both of those use cases. I think that's one of the reasons, yeah we talk about OpenShift and how coupled it is to RHEL and Linux. It's for that you can take anything that runs on RHEL, run it in a container on OpenShift, stateful, not stateful. That's one really key design principle. The other one, and this we've actually experienced ourselves, of the roles and responsibilities separation. We run an OpenShift host environment publicly, I joke, like anyone that gives me an email address, I'll run their code and my operations team doesn't have to know what's inside of the containers. They have a really clear boundary which is make the infrastructure infinitely available for them, and know that you can run anything on that environment. So that separation, you know when customers talk about DevOps, and getting to agile, I think that's almost as critical as the technology itself, is letting them be able to do that. >> Yeah, that's been a real theme here at the show, I've certainly noticed. Sure there were technology demos up on stage, but also a lot of talk about culture, about process or anti-planning maybe, or you know helping people. The role of Red Hat with OpenShift and the full stack all the way down is bigger now than it was, just when it was just Linux. So I mean, is it you and your team, I mean your in engineering as you work with the open source communities, surely it seems like you're having to deal with a much broader scope of responsibilities. >> Yeah, that's true. I started in Red Hat when it was just Linux and part of it is, you know Linux is big, and it's complex, and that in and of itself is a pretty broad community. But these days it is, we get to work with customers that are transforming their business and that touches everything from how they're organizationally structured, how we make teams work together, how I make the developers happy with their rate of innovation and the security team still comfortable with what they're changing. I love it, like it is, you know and we open source at our core, so I fell like, I'm an open source guy. I always have been. You're seeing open source drive a much wider scope of change then I ever have before. >> Let's talk about functionality product-wise, 'cause again we interviewed Jim Whitehurst yesterday and we had Denise Dumas on as well, on the RHEL side, and we talked about security. These things going on, and with OpenShift, and with Kubernetes, and containers, it makes your job harder. You got to do more right? So talk about what does that mean for you guys and how does that translate to the customer impact because it's more complicated. There's abstraction layers that are abstracting away the complexity. The complexity is not going away, it's just being abstracted away. This is harder on engineering. How are you handling that and what's your approach? >> So I've looked at it as a great opportunity for us. I've been working with Linux for a long time and I was a big fan when we introduced SELinux, and for a long time moving from traditional Linux hosting to operations teams wanting to turn on SELinux, it's been a really tough climb. It's, it'll break things, and they're not comfortable with it. They know they need that layer of security, but turning it on has been a challenge. Then go to cgroups, or different namespaces, and they're not going to get there. With OpenShift, the vast majority of OpenShift deployments, under the covers we run with SELinux on by default, customize policies, everything's in control groups, containers uses Linux namespaces. So you get a level of workload isolation that it was unimaginable you know five, 10 years ago, and I love that aspect, 'cause you start with one aspect of security, you get much, much stronger. So it's our ability to, you know we know all the levers and knobs in Linux itself, and we get to turn 'em all and pull 'em all so, >> I want to put you on the spot, I want to, and it's not an insult to you guys at all. But we've heard some hallway conversations. You know just in a joking way 'cause everyone loves Linux, open source, we all love that. But they say, nothings perfect either. No software actually runs all the time great. So one customer said, I won't say the name, "When OpenShift fails, it fails big." Meaning there's, it's very reliable but it's taking on a lot of heaving lifting. There's a lot of things going on in there, 'cause that's, 'cause it's Linux, when it breaks, it breaks a lot, and I know you're tryin' to avoid that. But my point is, is that just as these are important components. How do you make that completely bullet proof? How do you guys stay on top of it so that thinks don't break? I'm not saying they do all the time. I'm just saying it's common. It was more an order of magnitude kind of thing. >> Yeah, yeah, no, well I think it's a coupla things. So we invested in OpenShift Online and OpenShift Dedicated and those were new for Red Hat, and for running hosting environments, so we could learn a lot of the nuances of how do you, OpenShift Online is roughly a single environment, how do we make that never break as a whole. A user might do something in their app and make their app break. How do we not make the whole break? The second challenge I think we've hit is just skills in the market of it's not necessarily an easy system there are lots of moving pieces there. The deal with Azure and the partnership there, having managed service offerings I think is really going to help users get into, I have a highly available environment, I don't have to worry about SED replication or those components but I can still get the benefits. And then I think over time as people learn the technology, they know how to utilize it well, we'll see, we'll see less and less of the it catastrophically failed because I didn't know that I could make it highly available. Those are always painful to me, where it's you know, >> John: That's education. >> Yeah >> So Matt, there's a clear conversation here. Very clarity of roles and responsibilities even in the stack. I think even as recently as a year or two ago, people were having conversations about the role of OpenStack, versus Kubernetes, and you were getting kind of weird, like what's on top of what? And even in terms of, you know other parts of the stack, I mean here it's clear, very clear, you know OpenStack is about infrastructure, OpenShift you know on top of it, and even in terms of virtualization, containers versus VMs. The conversation this year seems more clear. As an engineer, you know and an engineering leader, were the, did the engineering teams rolling their eyes going well we knew how this was going to work out all along, or did you all also kind of come along on that journey the last couple years? >> I think seeing the customer use cases refined a little bit while education builds those has been great. We always, like we're engineers, we like clear separation and what each products good at, so for us it's fantastic. You know OpenStack is great at managing metal. One of my favorite demonstrations was using OpenStack Director to on a, you know boot machines, put OSs on 'em, and leave OpenShift running, and be able to share network and storage clients with OpenStack. Those things are, you know they're great for me as an engineering lead because we're doing that once as well as we can, but it's nice in engineering if you get to optimize each side of the stack. So I think I have seen the customers understanding, as they've done more with OpenStack, and they've done more with OpenShift, they know which product they want to use, what for. That has helped us accelerate the engineering work towards it. >> You mention skills, skills gaps, and skills in general. How is the hiring going? Is there a new kind of DevOps rockstar out there? Is there a new kind of profile? Is there pieces of the stack that you want certain skills for? Is there generalism? Are the roles in engineering changing? If you could just add some color to that conversation around, you know cause we're talkin' about engineering now. It used to be called software engineering when I graduated, and then you became a developer. I don't know which ones better, but you know to me this is real engineering going on, which is using software development techniques. So what's the skills situation? >> For us I think, it is nice that you're seeing a lot of gravitation to Linux at the host level, and Kubernetes has helped, just at the distributed system level, so obviously skills there play pretty well in general. I would say what we have seen is there has been a stronger increase in having operational skills as well as development skills, and it's a spectrum. You're still going to have operational experts and algorithmic experts, but the blended role where you do know what it takes to run an application in production to some extent, or you do know something about infrastructure and development. I certainly look for that on our teams because that's, where customers I've seen struggle for years and years is in the handoff in the shift between, everyone can write functional apps, they usually struggle getting them into production. And it's really neither teams fault, it's in that translation and these platforms help bridge that. People that have some skills on either side have become incredibly valuable in that. >> John: So that's were the DevOps action is right, the overlay. >> It really is yeah. >> So thinking about network as the networking growth with DevOps. DevOps has always been infrastructure as code. And it all comes to, there's to many, many, I don't want to talk about it. It's always the network that gets beat on the most, I need better latency. And so networking software to find networking is not a new concept, self-defined data centers are out there. What's new in networking that you could point to that's part of this new wave? >> Two geeky things that might not have been noticed. One is the work we've done on Ansible networking has been stunningly popular to me, and that was just this simplicity of Ansible just needs us to sage in a minimal set of dependencies. Most switches out there can actually, they have SSH running, and having automation of switches in the actual gear itself was surprisingly not unified. And Ansible was able to fit that niche where you could remotely configure switches and that has grown and exploded. Because if you think of the, I'm going to do a DevOps workflow but now I need to actually change routing or bleed something, you're often talking to switches, and being able to couple that in has been, it has been fun to watch, so I've loved that aspect. The other portion when we combine OpenShift on OpenStack the courier work which we've talked about some, is, you know OpenShift often described as it consumes infrastructure that OpenStack provides, and the one exception was usually the networking tier. It was like we have to run an overlay network on it. When we run OpenShift on OpenStack it can actually utilize OpenStack's networking to be able to try that instead of doing it's own overlay. That is critical at the larger scale. >> John: So the policy comes in handy there is that, or configurations, where's the benefit? >> Both on network topology, which do you have two teams that are building different structures that may collide in the night. So it gets it from two teams down to one, and then the second is just the knock controls in isolation, it's done once. It's been nice for me on the engineering side where we'd put a ton of effort in the OpenStack community, we put a ton of effort in Kubernetes and the OpenShift communities, and we're able to pretty nicely combine those. We know 'em both really well. >> So take us through some inside baseball at Red Hat. What's going on internally within' your group. I want to probe on developer and software engineers productivity. If the quote DevOps works, the test is the freeing up their time from doing mundane tasks, and you got cool things like you said about the network things, pretty positive. This is going to free up some intellectual capital from engineering. So okay if that's true, I'm assuming it's true, if it's not then say it's not true, but it sounds like it's probably going to be true for you. What are your guys working on, what's next? So can you share some of what, 'cause you guys are doing your own thing, you're using your own software. Is that intellectual capital being freed up on the developers side? Are they doing some more programming? Are you seeing some more creativity? What are they doing with that free time, free time, extra intellectual cycles? >> All our excesses, I'll tell Paul that. He was up before me. Like, Ops team barely has to work anymore. >> There in there clipping coupons at the beach you know. It's all running, we're busy. >> So a good creative example, and this was I think the second demo we showed. Red Hat Insights has been in the market for a while and that was our, can we glean enough information from systems to get ahead of a support issue, and this year we showed the, it's not just known fixes, you know we match it to a knowledgebase article. But can we interpret fixes from peer analysis and you know machine learning type techniques? That's a classic example where we use the creativity and free time, and say you know what that stack internally runs on OpenShift, running on OpenStack, using Red Hat storage, and we're applying some of, you know TensorFlow and other capabilities to do that. That was probably my favorite example at SUMMIT where if we weren't getting more efficient at what we worked on, we wouldn't of been able to stand up that stack ourselves, much less execute to it, and show it live in SUMMIT, doing the analysis across a hybrid cloud. >> But this is the whole point of DevOps. This the whole purpose, being highly productive, to use those intellectual cycle times to build stuff, solve problems. >> Yeah absolutely. >> Not provision servers or networks. Awesome, well thanks for coming on theCUBE, really appreciate it. >> Matt: Thank you guys. >> What's the priorities for you guys this year? What's the focus? Share your plans for the year. >> You know I think it's similar to the last thing we showed today. We really want to make customers feel like they can deploy hybrid cloud. Whether it's compute, applications, they have the services they need, down to storage, it works. They're on premise. They know we're going to have the best combination we can. This year is a stay ahead of people on that path, make sure their successful with it. >> We'll see you guys at OpenStack SUMMIT, Vancouver. Thanks for comin' on, Matt Hicks, Senior Vice-President of Engineering at Red Hat. I'm John Furrier, John Troyer, Stay with us, we're day three of three days of live coverage here in San Francisco, Red Hat SUMMIT 2018. Stay with us, we'll be right back after this short break. (digital music)

[Music] and y'all know that these [Music] ladies and gentlemen please take your seats and silence your cellphone's our program will begin shortly ladies and gentlemen please welcome Red Hat executive vice president and chief people officer dallisa Alexander an executive vice president and chief marketing officer Tim Layton [Music] hi everyone we're so excited to kick off this afternoon day 2 at the Red Hat summit we've got a stage full of stories about people making amazing contributions with open source well you know dallisa you and I both been coming to this event for a long long time so what keeps you coming back well you know the summit started as a tech conference an amazing tech conference but now it's expanded to be so much more this year I'm really thrilled that we're able to showcase the power of open source going way beyond the data center and beyond the cloud and I'm here also on a secret mission oh yes I'm here to make sure you don't make too many bad dad jokes so there's no such thing as a bad dad they're just dad jokes are supposed to be bad but I promise to keep it to my limit but I do have one okay I may appeal to the geeks in the audience okay so what do you call a serving tray full of empty beer cans yeah we container platform well that is your one just the one that's what I only got a budget of one all right well you know I have to say though in all seriousness I'm with you yeah I've been coming to the summit since its first one and I always love to hear what new directions people are scoring what ideas they're pursuing and the perspectives they bring and this afternoon for example you're gonna hear a host of different perspectives from a lot of voices you wouldn't often see on a technology mainstage in our industry and it's all part of our open source series live and I have to say there's been a lot of good buzz about this session all week and I'm truly honored and inspired to be able to introduce them all later this afternoon I can tell you over the course the last few weeks I've spent time with all of them and every single one of them is brilliant they're an innovator they're fearless and they will restore your faith in the next generation you know I can't wait to see all these stories all of that and we've got some special guests that are surprised in store for us you know one of the things that I love about the people that are coming on the stage today with us is that so many of them teach others how to code and they're also bringing more people that are very different in to our open-source communities helping our community is more innovative and impactful and speaking of innovative and impactful that's the purpose of our open brand project right that's right we're actually in the process of exploring a refresh of our mark and we'd really like your help as well because we're doing this all in the open we've we've been doing it already in the open and so please join us in our feedback zone booth at the summit to tell us what you think now it's probably obvious but I'm big into Red Hat swag I've got the shirt I've got my pen I've got the socks so this is really important to me personally especially that when my 15 year old daughter sees me in my full regalia she calls me adorable okay that joke was fed horrible as you're done it wasn't it wasn't like I got way more well Tim thanks for helping us at this stage for today it's time to get started with our first guest all right I'll be back soon thank you the people I'm about to bring on the stage are making outstanding contributions to open source in new and brave ways they are the winners of the 2018 women and open source Awards the women in open source awards was created to highlight the contributions that women are making to open source and to inspire new generations to join the movement our judges narrowed down the panel a very long list just ten finalists and then the community selected our two winners that were honoring today let's learn a little bit more about them [Music] a lot of people assume because of my work that I must be a programmer engineer when in fact I specifically chose and communications paths for my career but what's fascinating to me is I was able to combine my love of Communications and helping people with technology and interesting ways I'm able to not be bound by the assumptions that everybody has about what the technology can and should be doing and can really ask the question of what if it could be different I always knew I wanted to be in healthcare just because I feel like has the most impact in helping people a lot of what I've been working on is geared towards developing technology and the health space towards developing world one of the coolest things about open-source is bringing people together working with other people to accomplish amazing things there's so many different projects that you could get involved in you don't even have to be the smartest person to be able to make impact when you're actually developing for someone I think it's really important to understand the need when you're pushing innovation forward sometimes the cooler thing is not [Music] for both of us to have kind of a health care focus I think it's cool because so many people don't think about health care as being something that open-source can contribute to it took a while for it to even get to the stage where it is now where people can open-source develop on concepts and health and it's an untapped potential to moving the world for this award is really about highlighting the work of dozens of women and men in this open source community that have made this project possible so I'm excited for more people to kind of turn their open-source interest in healthcare exciting here is just so much [Music] I am so honored to be able to welcome to the stage some brilliant women and opensource first one of our esteemed judges Denise Dumas VP of software engineering at Red Hat she's going to come up and share her insights on the judging process Denise so you've been judging since the very beginning 2015 what does this judge this being a judge represents you what does the award mean to you you know every year it becomes more and more challenging to select the women an opensource winner because every year we get more nominees and the quality of the submissions well there are women involved in so many fabulous projects so the things that I look for are the things that I value an open source initiative using technology to solve real world problems a work ethic that includes sin patches and altruism and I think that you'll see that this year's nominees this year's winners really epitomize those qualities totally agree shall we bring them on let's bring them on let's welcome to the stage Zoe de gay and Dana Lewis [Music] [Applause] [Applause] [Music] alright let's take a seat [Applause] well you both have had an interesting path to open-source zuy you're a biomedical engineering student any of it you have a degree in public relations tell us what led to your involvement and open source yeah so coming to college I was new I was interested in science but I didn't want to be a medical doctor and I didn't want to get involved in wet lab research so through classes I was taking oh that's why I did biomedical engineering and through classes I was taking I found the classroom to be very dry and I didn't know how how can I apply what I'm learning and so I got involved in a lot of entrepreneurship on campus and through one of the projects I was asked to build a front end and I had no idea how to go about doing that and I had some basic rudimentary coding knowledge and what happened was I got and was digging deep and then found an open source library that was basically building a similar thing that I needed and that was where I learned about open source and I went from there now I'm really excited to be able to contribute to many communities and work on a variety of projects amazing contributions Dana tell us about your journey well I come from a non-traditional background but I was diagnosed with type 1 diabetes at the age of 14 and over the next couple years got really frustrated with the limitations of my own diabetes devices but felt like I couldn't change them because that wasn't my job as a patient but it was actually through social media I discovered someone who had solved one of the problems that I had been found having which was getting date off my diabetes device and that's how I learned about open source was when he was willing to share his code with me so when we turned around and made this hybrid closed-loop artificial pancreas system it was a no brainer to make our work open source as well that's right absolutely and we see using the hash tag we are not waiting can you tell us about that yeah so this hash tag was created actually before I even discovered the open source diabetes world but I loved it because it really illustrates exactly the fact that we have this amazing technology in our hands in our pockets and we can solve some of our most common problems so yes you could wait but waiting is now a choice with open source we have the ability to solve some of our hardest problems even problems dealing with life and death that's great so zuy with the vaccine carrier system that you helped to build how were you able to identify the need and where did you build it yes so I think before you even build anything first need to understand what is the problem that you're trying to solve and that really was the case when starting this project I got to collaborate with engineers in Kampala Uganda and travel there and actually interview stakeholders in the medical field medical doctors as well as pharmaceutical companies and from there I really got to understand the health system there as well as what is how do vaccines enter the country and how can we solve this problem and that's how we came up with the solution for an IOT based vaccine carrier tracking system I think it's really important especially today when products might be flashy to also understand what is the need behind it and how do we solve problems with these products yeah yeah it's so interesting how both of you have this interest in health care Dana how do you see open-source playing a role in healthcare but first before you answer that tell us about your shirt so this shirt has the code of my artificial pancreas on it and I love it as an illustration of no thank you I love it as an illustration of how open-source is more than we think it is I've just been blown away by the contributions of people in my open-source communities and I think that that is what we should apply to all of healthcare there's a lot of tools and technologies that are solving real world problems and I think if we take what we know in technology and apply it to healthcare we'll solve a lot of problems more quickly but it really needs to be recognizing everything an open source it's the documentation it's the collaboration it's the problem-solving it's working together to take technologies that we didn't previously think we're applicable and finding new ways to apply it it's a great answer Sooey yeah I think especially where healthcare is related to people and open-source is the right way to collaborate with people all over the world especially in the project I've been working on we're looking at vaccines in Uganda but the same system can be applied in any other country and then you can look at cross countries health systems there and from there it becomes bigger and bigger and I think it's really important for people who have an idea and want to take it further to know that open-source is a way that you could actually take your idea further whether you have a technical background or not so yeah stories are amazing you're just an inspiration for everyone in open-source I want to thank you so much for joining us here today let's give another round of applause to our winners [Applause] [Music] you know the tagline for the award is honor celebrate inspire and I feel like we've been doing that today very very well and I know that so many people have been inspired today especially the next generation who go on to do things we can't even dream of yet [Music] I think collabs important because we need to make sure we get younger children interested in technology so that they understand the value of it but also that there are a lot of powerful women in technology and they can be one of them I hope after this experience maybe we'll get some engineers and some girls working our hot so cool right well we have some special guests convite for the club stage now I'd like to invite Tim back and also introduce Red Hat's own Jamie Chappell along with our collab students please welcome Gabby tenzen Sofia lyric Camila and a Volyn [Applause] you've been waiting for this moment for a while we're so excited hear all about your experiences but Jamie first tell us about collab sure so collab is red hats way of teaching students about the power of open source and collaboration we kicked off a little over a year ago in Boston and that was so successful that we decided to embark on an East Coast tour so in October we made stops at middle schools in New York DC and Raleigh and these amazing people over here are from that tour and this week they have gone from student to teacher so they've hosted two workshops where they have taught Red Hat summit attendees how to turn raspberry pies into digital cameras they assigned a poem song of the open road by Walt Whitman and they've been working at the open source stories booth helping to curate photos for an installation we're excited to finish up tomorrow so amazing and welcome future women in open source we want to know all about your experiences getting involved can you tell us tenzen tell us about something you've learned so during my experience with collab I learned many things but though however the ones that I valued the most were open source and women empowerment I just I was just so fascinated about how woman were creating and inventing things for the development of Technology which was really cool and I also learned about how open source OH was free and how anyone could access it and so I also learned that many people could you know add information to it so that other people could you learn from it and use it as well and during Monday's dinner I got this card saying that the world needed more people like you and I realized through my experience with collab that the world does not only need people like me but also everyone else to create great technology so ladies you know as you were working on your cameras and the coding was there a moment in time that you had an AHA experience and I'm really getting this and I can do this yes there was an aha moment because midway through I kind of figured out well this piece of the camera went this way and this piece of the camera did it go that way and I also figured out different features that were on the camera during the camera build I had to aha moments while I was making my camera the first one was during the process of making my camera where I realized I was doing something wrong and I had to collaborate with my peers in order to troubleshoot and we realize I was doing something wrong multiple times and I had to redo it and redo it but finally I felt accomplished because I finished something I worked hard on and my second aha moment was after I finished building my camera I just stared at it and I was in shock because I built something great and it was so such a nice feeling so we talked a lot about collaboration when we were at the lab tell us about how learning about collaboration in the lab is different than in school so in school collaboration is usually few and far between so when we went to collab it allowed us to develop new skills of creativity and joining our ideas with others to make something bigger and better and also allowed us to practice lots of cooperation an example of this is in my group everybody had a different problem with their pie camera and we had to use our different strengths to like help each other out and everybody ended up assembling and working PI camera great great awesome collaboration in collab and the school is very different because in collab we were more interactive more hands-on and we had to work closer together to achieve our own goals and collaboration isn't just about working together but also combining different ideas from different people to get a product that is so much better than some of its parts so girls one other interesting observation this actually may be for the benefit of the folks in our audience but out here we have represented literally hundreds and hundreds of companies all of whom are going to be actually looking for you to come to work for them after today we get first dibs that's right but um you know if you were to have a chance to speak to these companies and say what is it that they could do to help inspire you know your your friends and peers and get them excited about open source what would you say to them well I'm pretty sure we all have app store and I'm pretty sure we've all downloaded an app on that App Store well instead of us downloading app State well the computer companies or the phone companies they could give us the opportunity to program our own app and we could put it on the App Store great idea absolutely I've got to tell you I have a 15 year old daughter and I think you're all going to be an inspiration to her for the same absolutely so much so I see you brought some cameras why don't we go down and take a picture let's do it [Applause] all right I will play my very proud collab moderator role all right so one two three collab okay one two three [Applause] yeah so we're gonna let leave you and let you tell us more open source stories all right well thank you great job thank you all and enjoy the rest of your time at Summit so appreciate it thanks thank you everyone pretty awesome pretty awesome and I would just like to say they truly are fedorable that's just um so if you would like to learn more as you heard the girls say they're actually Manning our open-source stories booth at the summit you know please come down and say hello the stories you've seen thus far from our women and open-source winners as well as our co-op students are really bringing to life the theme of this year's summit the theme of ideas worth exploring and in that spirit what we'd like to do is explore another one today and that is how open-source concepts thrive and expand in the neverending organic way that they do much like the universe metaphor that you see us using here it's expanding in new perspectives and new ideas with voices beyond their traditional all starting to make open-source much bigger than what it was originally started as fact open-source goes back a long way long before actually the term existed in those early days you know in the early 80s and the like most open-source projects were sort of loosely organized collections of self-interested developers who are really trying to build low-cost more accessible replicas of commercial software yet here we are 2018 the world is completely different the open-source collaborative development model is the font of almost all original new innovation in software and they're driven from communities communities of innovation RedHat of course has been very fortunate to have been able to build an extraordinary company you know whose development model is harnessing these open-source innovations and in turning them into technologies consumable by companies even for their most mission-critical applications the theme for today though is we see open-source this open source style collaboration and innovation moving beyond just software this collaborative community innovation is starting to impact many facets of society and you're starting to see that even with the talks we've had already too and this explosion of community driven innovation you know is again akin to this universe metaphor it expands in all directions in a very organic way so for red hat you know being both beneficiaries of this approach and stewards of the open collaboration model we see it important for us to give voice to this broader view of open source stories now when we say open source in this context of course will meaning much more than just technology it's the style of collaboration the style of interaction it's the application of open source style methods to the innovation process it's all about accelerating innovation and expanding knowledge and this can be applied to a whole range of human endeavors of course in education as we just saw today on stage in agriculture in AI as the open source stories we shared at last year's summit in emerging industries like healthcare as we just saw in manufacturing even the arts all these are areas that are now starting to benefit from collaboration in driving innovation but do we see this potentially applying to almost any area of human endeavor and it expands again organically expanding existing communities with the addition of new voices and new participants catalyzing new communities and new innovations in new areas as we were talking about and even being applied inside organizations so that individual companies and teams can get the same collaborative innovation effects and most profound certainly in my perspective is so the limitless bounds that exist for how this open collaboration can start to impact some of humankind's most fundamental challenges we saw a couple of examples in fact with our women and open-source winners you know that's amazing but it also potentially is just the tip of the iceberg so we think it's important that these ideas you know as they continue to expand our best told through storytelling because it's a way that you can embrace them and find your own inspirations and that's fundamentally the vision behind our open-source stories and it's all about you know building on what's come before you know the term we use often is stay the shoulders are giants for a lot of the young people that you've seen on this stage and you're about to see on this stage you all are those giants you're the reason and an hour appears around the world are the reasons that open-source continues to expand for them you are those giants the other thing is we all particularly in this room those of us have been around open-source we have an open-source story of our own you know how were you introduced the power of open-source how did you engage a community who inspired you to participate those are all interesting elements of our personal open-source stories and in most cases each of them are punctuated by you here my question to the girls on stage an aha moment or aha moments you know that that moment of realization that enlightens you and causes you to think differently and to illustrate I'm going to spend just a few minutes sharing my open-source story for for one fundamental reason I've been in this industry for 38 years I am a living witness to the entire life of open-source going back to the early 80s I've been doing this in the open-source corner of the industry since the beginning if you've listened to Sirhan's command-line heroes podcasts my personal open story will actually be quite familiar with you because my arc is the same as the first several podcast as she talked about I'm sort of a walking history lesson in fact of open source I wound up at most of the defining moments that should have changed how we did this not that I was particularly part of the catalyst I was just there you know sort of like the Forrest Gump of open-source I was at all these historical things but I was never really sure how it went up there but it sure was interesting so with that as a little bit of context I'm just gonna share my aha moment how did I come to be you know a 59 year old in this industry for 38 years totally passionate about not just open source driving software innovation but what open source collaboration can do for Humanity so in my experience I had three aha moments I just like to share with you the first was in the early 80s and it was when I was introduced to the UNIX operating system and by the way if you have a ha moment in the 80s this is what it looks like so 1982 mustache 19 where were you 2018 beard that took a long time to do all right so as I said my first aha moment was about the technology itself in those early days of the 80s I became a product manager and what at the time was digital equipment corporation's workstation group and I was immediately drawn to UNIX I mean certainly these this is the early UNIX workstation so the user interface was cool but what I really loved was the ability to do interactive programming via the shell but by a--basically the command line and because it was my day job to help figure out where we took these technologies I was able to both work and learn and play all from the same platform so that alone was was really cool it was a very accessible platform the other thing that was interesting about UNIX is it was built with networking and and engagement in mind had its own networking stack built in tcp/ip of course and actually built in a set of services for those who've been around for a while think back to things like news groups and email lists those were the first enablers for cross internet collaboration and that was really the the elements that really spoke to me he said AHA to me that you know this technology is accessible and it lets people engage so that was my first aha moment my second aha moment came a little bit later at this point I was an executive actually running Digital Equipment Corporation UNIX systems division and it was at a time where the UNIX wars were raging right all these companies we all compartmentalized Trump those of the community and in the end it became an existential threat to the platform itself and we came to the point where we realized we needed to actually do something we needed to get ahead of this or UNIX would be doomed the particular way we came together was something called cozy but most importantly the the technique we learned was right under our noses and it was in the area of distributed computing distributed client-server computing inherently heterogenous and all these same companies that were fierce competitors at the operating system level were collaborating incredibly well around defining the generation of client-server and distributed computing technologies and it was all being done in open source under actually a BSD license initially and Microsoft was a participant Microsoft joined the open group which was the converged standards body that was driving this and they participated to ensure there was interoperability with Windows and and.net at the time now it's no spoiler alert that UNIX lost right we did but two really important things came out of that that sort of formed the basis of my second aha moment the first is as an industry we were learning how to collaborate right we were leveraging open source licenses we realized that you know these complex technologies are best done together and that was a huge epiphany for the industry at that time and the second of course is that event is what opened the door for Linux to actually solve that problem so my second aha was all about the open collaboration model works now at this point to be perfectly candidates late 1998 well we've been acquired by compacts when I'm doing the basically same role at Compaq and I really had embraced what the potential impact of this was going to be to the industry Linux was gaining traction there were a lot of open source projects emerging in distributed computing in other areas so it was pretty clear to me that the in business impact was going to be significant and and that register for me but there was seem to be a lot more to it that I hadn't really dropped yet and that's when I had my third aha moment and that was about the passion of open-source advocates the people so you know at this time I'm running a big UNIX group but we had a lot of those employees who were incredibly passionate about about Linux and open source they're actively participating so outside of working a lot of things and they were lobbying more and more for the leadership to embrace open source more directly and I have to say their passion was contagious and it eventually spread to me you know they were they were the catalyst for my personal passion and it also led me to rethink what it is we needed to go do and that's a passion that I carry forward to this day the one driven by the people and I'll tell you some interesting things many of those folks that were with us at Compaq at the time have gone on to be icons and leaders in open-source today and many of them actually are involved with with Red Hat so I'll give you a couple of names that some of whom you will know so John and Mad Dog Hall work for me at the time he was the person who wrote the first edition of Linux for dummies he did that on his own time when he was working for us he he coined he was part of the small team that coined the term open source' some other on that team that inspired me Brian Stevens and Tim Burke who wrote the first version to rent out Enterprise Linux actually they did that in Tim Burke's garage and cost Tim's still with Red Hat today two other people you've already seen him on stage today Denise Dumas and Marko bill Peter so it was those people that I was fortunate enough to work with early on who had passion for open-source and much like me they carry it forward to this day so the punchline there is they ultimately convinced us to you know embrace open-source aggressively in our strategy and one of the interesting things that we did as a company we made an equity investment in Red Hat pre-ipo and a little funny sidebar here I had to present this proposal to the compact board on investing in Red Hat which was at that time losing money hand over fist and they said well Tim how you think they're gonna make money selling free software and I said well you know I don't really know but their customers seem to love them and we need to do this and they approve the investment on the spot so you know how high do your faith and now here we are at a three billion dollar run rate of this company pretty extraordinary so from me the third and final ha was the passion of the people in the way it was contagious so so my journey my curiosity led me first to open source and then to Red Hat and it's been you know the devotion of my career for over the last thirty years and you know I think of myself as pretty literate when it comes to open source and software but I'd be the first one to admit I would have never envisioned the extent to which open source style collaboration is now being brought to bear on some of the most interesting challenges in society so the broader realization is that open source and open can really unlock the world's potential when applied in the collaborative innovative way so what about you you know you many of you particular those have been around for a while you probably have an open source story of your own for those that maybe don't or they're new to open source are new to Red Hat your open source story may be a single inspiration away it may happen here at the summit we certainly hope so it's how we build the summit to engage you you may actually find it on this stage when I bring up some of the people who are about to follow me but this is why we tell open-source stories and open source stories live so each of you hopefully has a chance to think about you know your story and how it relates over source so please take advantage of all the things that are here at the summit and and find your inspiration if you if you haven't already so next thing is you know in a spirit of our telling open source stories today we're introducing our new documentary film the science of collective discovery it's really about citizen scientists using open systems to do serious science in their backyards and environmental areas and the like we're going to preview that I'm gonna prove it preview it today and then please come see it tonight later on when we preview the whole video so let's take a look I may not have a technical scientific background but I have one thing that the scientists don't have which is I know my backyard so conventional science happens outside of public view so it's kind of in this black box so most are up in the ivory tower and what's exciting about citizen science is that it brings it out into the open we as an environmental community are engaging with the physical world every day and you need tools to do that we needed to democratize that technology we need to make it lightweight we need to make it low-cost we needed to make it open source so that we could put that technology in the hands of everyday people so they go out and make those measurements where they live and where they breathe when you first hear about an environmental organization you mostly hear about planting trees gardens things like that you don't really think about things that are really going to affect you hey we're the air be more they'd hold it in their hand making sure not to cover the intake or the exhaust I just stand here we look at the world with forensic eyes and then we build what you can't see so the approach that we're really centered on puts humans and real issues at the center of the work and I think that's the really at the core of what open source is social value that underlies all of it it really refers to sort of the rights and responsibilities that anyone on the planet has to participate in making new discoveries so really awesome and a great story and you know please come enjoy the full video so now let's get on with our open stories live speakers you're going to really love the rest of the afternoon we have three keynotes and a demo built in and I can tell you without exaggeration that when you see and hear from the young people we're about to bring forward you know it's truly inspirational and it's gonna restore totally your enthusiasm for the future because you're gonna see some of the future leaders so please enjoy our open source stories live presentation is coming and I'll be back to join you in a little bit thanks very much please welcome code newbie founder Saran yep Eric good afternoon how y'all doing today oh that was pretty weak I think you could do better than that how y'all doing today wonderful much better I'm Saran I am the founder of code newbie we have the most supportive community of programmers and people learning to code this is my very first Red Hat summits I'm super pumped super excited to be here today I'm gonna give you a talk and I'm going to share with you the key to coding progress yes and in order to do that I'm gonna have to tell you a story so two years ago I was sitting in my hotel room and I was preparing for a big talk the next morning and usually the night before I give a big talk I'm super nervous I'm anxious I'm nauseous I'm wondering why I keep doing this to myself all the speakers backstage know exactly what I'm what I'm talking about and the night before my mom knows this so she almost always calls just to check in to see how I'm doing to see how I'm feeling and she called about midnight the night before and she said how are you how are you doing are you ready and I said you know what this time I feel really good I feel confident I think I'm gonna do a great job and the reason was because two months ago I'd already given that talk in fact just a few days prior they had published the video of that talk on YouTube and I got some really really good positive feedback I got feedback from emails and DMS and Twitter and I said man I know people really like this it's gonna be great in fact that video was the most viewed video of that conference and I said to my office said you know what let's see how many people loved my talk and still the good news is that 14 people liked it and a lot more people didn't and I saw this 8 hours before I'm supposed to give that exact same talk and I said mom I gotta call you back do you like how I did that to hang up the phone as if that's how cellphones work yeah and so I looked at this and I said oh my goodness clearly there's a huge disconnect I thought they were really liked they were I thought they were into it and this showed me that something was wrong what do you do what do you do when you're about to give that same talk in 8 hours how do you begin finding out what the problem is so you can fix it I have an idea let's read the comments you got to believe you gotta have some optimism come on I said let's read the comments because I'm sure we'll find some helpful feedback some constructive criticism some insights to help me figure out how to make this talk great so that didn't happen but I did find some really colorful language and some very creative ideas of what I could do with myself now there are some kids in the audience so I will not grace you with these comments but there was this one comment that did a really great job of capturing the sentiment of what everyone else was saying I can only show you the first part because the rest is not very family-friendly but it reads like this how do you talk about coding and not fake societal issues see the thing about that talk is it wasn't just a code talk it was a code and talk is about code and something else that talked touched on code and social justice I talked a lot about how the things that we build the way we build them affect real people and their problems and their struggles and that was absolutely not okay not okay we talk about code and code only not the social justice stuff it also talked about code and diversity yeah I think we all know the diversity is really about lowering the bar it forces us to talk about people and their issues and their problems in their history and we just don't do that okay absolutely inappropriate when it comes to a Tech Talk That Talk touched on code and feelings and feelings are squishy they're messy they're icky and a lot of us feel uncomfortable with feelings feelings have no place in technology no place in code we want to talk about code and code I want you to show me that API and when you show me that new framework that new tool that's gonna solve my problems that's all I care about I want to talk about code and give me some more code with it now I host a podcast called command line heroes it's an original podcast from Red Hat super excited about it if you haven't checked it out and totally should and what I love about this show as we talk about these really important moments and open swords these inflection points moments where we see progress we move forward and what I realized looking back at those episodes is all of those episodes have a code and something let's look at a few of those the first two episodes focused on the history of operating systems as a two-part episode part 1 and part 2 and there's lots of different ways we can talk about operating systems for these two episodes we started by talking about Windows and Mac OS and how these were two very powerful very popular operating systems but a lot of a lot of developers were frustrated with them they were closed you couldn't see inside you can see what it was doing and I the developer want to know what it's doing on my machine so we kind of had a little bit of a war one such developer who was very frustrated said I'm gonna go off and do my own thing my name is Linus this thing is Linux and I'm gonna rally all these other developers all these other people from all over the old to come together and build this new thing with me that is a code and moment in that case it was code and frustration it was a team of developers a world of developers literally old world of developers who said I'm frustrated I'm fed up I want something different and I'm gonna do something about it and what's really beautiful about frustration is it the sign of passion we're frustrated because we care because we care so much we love so deeply then we want to do something better next episode is the agile revolution this one was episode three now the agile revolution is a very very important moment in open-source and technology in general and this was in response to the way that we used to create products we used to give this huge stack of specs all these docs from the higher-ups and we'd take it and we go to our little corner and we lightly code and build and then a year with Pastor here's a pass a few years have passed and we'd finally burst forth with this new product and hope that users liked it and loved it and used it and I know something else will do that today it's okay no judgment now sometimes that worked and a lot of times it didn't but whether or not it actually worked it hurt it was painful these developers not enjoy this process so what happened a dozen developers got together and literally went off into their own and created something called the agile manifesto now this was another code and moment here it's code and anger these developers were so angry that they literally left civilization went off into a mountain to write the agile manifesto and what I love about this example is these developers did not work at the same company we're not on the same team they knew each other from different conferences and such but they really came from different survive and they agreed that they were so angry they were going to literally rewrite the way we created products next as an example DevOps tear down the wall this one is Episode four now this is a bit different because we're not talking about a piece of technology or even the way we code here we're talking about the way we work together the way that we collaborate and here we have our operations folks and our developers and we've created this new kind of weird place thing called DevOps and DevOps is interesting because we've gotten to a point where we have new tools new toys so that our developers can do a lot of the stuff that only the operations folks used to be able to do that thing that took days weeks months to set up I can do it with a slider it's kind of scary I can do it with a few buttons and here we have another code and moment and here that blink is fear for two reasons the operations focus is looking over the developer folks and thinking that was my job I used to be able to do that am I still valuable do I have a place in this future do I need to retrain there's also another fear which is those developers know what they're doing do they understand the security implications they appreciate how hard it is or something to scale and how to do that properly and I'm really interested in excited to see where we go with that where we take that emotion if we look at all of season one of the podcast we see that there's always a code and whether it's a code and frustration a code and anger or a code and fear it always boils down to code and feelings feelings are powerful in almost every single episode we see that that movement forward that progress is tied back to some type of Oshin and for a lot of us this is uncomfortable feelings make us feel weird and a lot of those YouTube commenters definitely do not like this whole feeling stuff don't be like those YouTube commenters there's one thing you take away from this whole talk let it be that don't be like these YouTube commenters feelings are incredibly powerful so the next time that you're working on a project you're having a conversation about a piece of software or a new piece of technology and you start to get it worked up you get angry you get frustrated maybe you get worried you get anxious you get scared I hope you recognize that feeling as a source of energy I hope you take that energy and you help us move forward I would take that to create the next inflection point that next step in the right direction feelings are your superpowers and I hope you use your powers for good thank you so much [Applause] please welcome jewel-box chief technology officer Sara Chipps [Music] Wow there's a lot of you out here how's it going I know there's a lot of you East Coasters here as well and I'm still catching up on that sleep so I hope you guys are having a great experience also my name is Sarah I'm here from New York I have been a software developer for 17 years it's longer than some of the people on stage today I've been alive big thanks to the folks at Red Hat for letting us come and tell you a little bit about jewel box so without further ado I'm gonna do exactly that okay so today we're gonna do a few things first I'm gonna tell you why we built jewel BOTS and why we think it's a really important technology I'm gonna show you some amazing magic and then we're gonna have one of the jewel bus experts come as a special guest and talk to you more about the deep technology behind what we're building so show hands in the audience who here was under 18 years old when they started coding it's hard for me to see you guys yep look around I'd have to say at least 50% of you have your hands up all right keep your hand up if you were under 15 when you started coding I think more hands up just what is it I don't know how that mouth works but awesome okay great yeah a little of I think about half of you half of you have your hands up that's really neat I've done a bunch of informal polls on the internet about this I found that probably about two-thirds of professional coders were under 18 when they started coding I myself was 11 I was a homeschooled kid so a little weird I'm part of the generation and some of you maybe as well is the reason we became coders is because we were lonely not because we made a lot of money so I was 11 this is before the internet was a thing and we had these things called BBS's and you would call up someone else's computer in your town and you would hang out with people and chat with them and play role-playing games with them it didn't have to be your town but if it wasn't your mom would yell at you for a long distance fees and I got really excited about computers and coding because of the community that I found online okay so this is sometimes the most controversial part of this presentation I promised you that they dominate our lives in many ways even if you don't even if you don't even know a 9 to 14 year old girl even if you just see them on the street sometimes they are deciding what you and I do on a regular basis hear me out for a second here so who here knows who this guy is okay you don't have to raise your hands but I think most people know who this guy is right so this guy used to be this guy and then teenage girls were like I think this guy has some talent to him I think that he's got a future and now he's a huge celebrity today what about this guy just got his first Oscar you know just kind of starting out well this guy used to be this guy and I'm proud to tell you that I am one of the many girls that discovered him and decided this guy has a future all right raise your hand if you listen to Taylor Swift just kidding I won't make you do it but awesome that's great so Taylor Swift we listen to Taylor Swift because these girls discovered Taylor Swift it wasn't a 35 year old that was like this Taylor Swift is pretty neat no one cares what we think but even bigger than that these huge unicorns that all of us some of us work for some of us wish we invented these were discovered by young teenage girls no one is checking to see what apps were using they're finding new communities in these thin in these platforms and saying this is how I want to commune with my friends things like Instagram snapchat and musically all start with this demographic and then we get our cues from them if you don't know what musically is I promise you ask your nearest 9 to 14 year old friend if you don't do that you'll hear about it in a few years but this demographic their futures are all at risk everyone here knows how much the field of software development is growing and how important technical literacy is to the future of our youth however just 18% of computer science graduates are girls just 19% of AP computer science test takers and just 15% of Google's tech force identify as female so we decided to do something about that we were inspired by platforms like MySpace and Geocities things like Neopets and minecraft all places where kids find something they love and they're like okay to make this better all I have to do is learn how to code I can totally do that and so we wanted to do that so we talked to 200 girls we went to schools we sat down with them and we were like what makes you tick what are you excited about and what we heard from them over and over again is their friends their friends and their community are pivotal to them and this time in their lives so when we started talking to them about a smart friendship bracelet that's when they started really freaking out so we built Jewel BOTS and Jewel BOTS has an active online community where girls can work together share code that they've built and learn from each other help each other troubleshoot sometimes the way they work is when you are near your friends your bracelets light up the same color and you can use them to send secret messages to each other and you can also code them so you can say things like when all my swimming friends are together in the same room all of our bracelets should go rainbow colors which is really fun you can even build games jewel BOTS started shipping about a year and a half ago about after a lot of work and we are about to ship our 12,000 jewel bot we're in 38 city sorry 38 countries and we're just getting started okay so now it's time for the magic and I have an important question does anyone here want to be my friend pick me all right someone today Gary oh I don't have many friends that's awesome I'm so glad that we'll be friends okay it's awesome so we just need to pair our jewel BA okay okay and in order to do that we're gonna hold the magic button in the middle down for two seconds so one locomotive two locomotive great and then we got a white flashing I'm gonna do yours again I did it wrong locomotive two locomotive it's we're adults we can't do it okay it's a good that are smart alright so now we get to pick our friendship color I'm gonna pick red hat red does that work for you sure okay great so now I just picked a red hat red and my jewel bot is saying alright Tim's jewel bot do you want to be my friend and imageable about it's like I'm thinking about it I think so okay now we're ready okay great so now we're red friends when we're together our bracelets are going to be red and I will send you a secret message when it's time for you to come out and trip and introduce the next guest awesome well thank you so much thank you tailor gun so glad we could be friends and if only people would start following me on Twitter it'd be a great day awesome alright so now you can see the not so technical part of jewel box they use bluetooth to sense when your friends are nearby so they would work in about a 30 meter hundred foot range but to tell you about the actual technology part I'm going to introduce is someone much more qualified than I am so Ellie is one of our jewel box ambassadors she's an amazing YouTube channel that I would please ask you to check out and subscribe she's le G Joel BOTS on YouTube she's an amazing coder and I'm really excited to introduce you today to Ellie Galloway come on out Ellie [Applause] hello my name is le gallais I'm gonna show you how I got coding and then show you some coding in action I first started coding at a6 when my dad helped me code a game soon after I program form a code for Minecraft then my dad had shown me jo bot I keep coding because it helps people for instance for instance you could code auto crack to make it a lot smarter so it can help make people stay run faster but what about something more serious what if you could help answer 911 calls and give alerts before we start I have three main steps to share with you I often use these steps to encoding my jaw bot and continue to use some of these now step one read the instructions and in other words this means for Jabba to memorize the colors and positions a way to memorize these because it's tricky is to remember all the colors and positions you O type will be capital and remember that the positions are either short for north west south west north east and south east step to learn the basic codes when it comes to coding you need to work your way up step 3 discover feel free to discover once you mastered everything now let's get to coding let's use or let's first use combining lights so under void loop I'm going to put LED turn on single s/w and blue and before we make sure that this works we got to put LED LED okay now let's type this again LED dot turn on single now let's do SW green now we have our first sketch so let's explain what this means led LED is a function that to control the LED lights LED turn on single SW blue tells that SW light to turn blue and green flashes so quickly with the blue it creates aqua now let's do another code lets you i'm going to use a more advanced command to make a custom color using RGB let's use a soft pink using 255 105 and 180 now let's type this in the button press function so let's do LED led LED dot set light and now we can do let's do position 3 255 105 and 180 now let's explain what this means the first one stands for the position the three others stand for red green and blue our GPS can only go up to 255 but there are 256 levels but if you count the first one as zero then get 255 so let's first before we move on let's show how this works so this is it before and now let's turn it on to see how our aqua turned out now let's see how our RGB light turned out so we are looking for a soft pink so let's see how it looks think about how much the code you write can help people all around the world these are ideas are just the beginning of opening a new world in technology a fresh start is right around the corner I hope this helped you learn a little bit about coding and even made you want to try it out for yourself thank you [Applause] alright alright alright I need your help for a second guys alright one second really really fascinating we're short on time today is Ellie's 11th birthday and I think we should give her the biggest present that she's gonna get today and it's something none of us have experienced and that is thousands of people saying happy birthday Elliott wants so when I say three can I get a happy birthday Elly one two three happy birthday Elly great job that's the best part of my job okay so those are that's two of us we're just getting started this numbers out Dana would almost shipped 12,000 jewel BOTS and what I'm really excited to tell you about is that 44% of our users don't just play with their jewel bots they code them and they're coding C do you even code C I don't know that you do but we have 8 to 14 year olds coding C for their jewel box we also have hundreds of events where kids come and they learn how to code for the first time here's how you can help we're open source so check out our github get involved our communities online you can see the different features that people's are asking for we're also doing events all over the world a lot of people are hosting them at their companies if you're interested in doing so reach out to us thank you so much for coming and learning about jewel box today enjoy the rest of your summit [Music] ladies and gentlemen please welcome hacker femme au founder Femi who Bois de Kunz [Music] good afternoon red hat summit 2018 i'm femi holiday combs founder of hacker femme Oh I started coding when I was 8 when I was 9 I set up South London raspberry jam through crowdfunding to share my passion for coding with other young people who might not otherwise be exposed to tech since then I've run hundreds of coding and robot workshops across the UK and globally in 2017 I was awarded an inaugural legacy Diana award by their Royal Highnesses Prince William and Prince Harry my service and community we welcome young people who have autism or like me tract syndrome because coding linked me up to a wider community of like-minded people and I'm trying to do the same for those who might also benefit from this I also deliver workshops to corporate companies and public organizations whilst feeding back ideas and resources into my community work we like to cascade our knowledge and experience to other young coders so that they can benefit too we're learning new tech every day we're starting to use github to document and manage our coding projects we've no dread we're using the terminal and beginning to really appreciate Linux as we explore cybersecurity and blockchain it's been quite a journey from South London to the world-famous Tate Modern museum to Bangladesh to this my first trip to the States and soon to China where I hope to translate my microwave workshops into Mandarin on this journey I'm noticed it is increasingly important for young coders to have collaborative and community led initiatives and enterprise and career ready skills so my vision now is to run monthly meetups and in collaboration with business partners help a hundred young disadvantaged people to get jobs in the digital services in fact out of all the lessons I've learned from teaching young coders they all have one thing in common the power of open source and the importance of developing community and today I want to talk about three of those lessons the value of reaching out and collaborating the importance of partnering event price and the ability to self organize and persist which translated into English means having a can-do attitude getting stuff done when you reach out when you show curiosity you realize you're not alone in this diverse community no matter who you are and where you're from from coding with minecraft to meeting other young people with jams I found there are people like me doing things I like doing I get to connect with them that's where open-source comes to the fourth second the open source community is so vast then it crosses continents it's so immersed perspectives that it can take you to amazing places out of space even that's my code running on the International Space Station's Columbus module let's take a lesson and playing was an audio representation for the frequencies recorded in space my team developed Python code to measure and store frequency readings from the space station and that was down linked back to earth to my email box Thomas who's 10 developed an audio file using audacity and importing it back into Python how cool is that Trulli collaboration can take you places you never thought possible because that's how the community works when you throw a dilemma a problem a tip the open source community comes back with answers when you give the community gives back tenfold that's how open source expands but in that vast starscape how do you know what to focus on there are so many problems to solve where do I start your world enterprice enterprise software is very good at solving problems what's the big problem how about helping the next generation be ready for the future I want to do more for the young coding community so I'm developing entrepreneurial business links to get that done this is a way to promote pathways to deal with future business problems whether in FinTech healthcare or supply chains a meeting the skill shortage it is a case for emerging in it's a case for investing in emerging communities and young change enablers throwing a wider net equates to being fully inclusive with a good representation of diversity you know under the shadow of the iconic show back in London there are pockets of deprivation where young people can't even get a job in a supermarket many of them are interested in tech in some way so my goal for the next three years is to encourage young people to become an active part of the coding community with open source we have the keys to unlock the potential for future innovation and technological development with young coders we have the people who have to face these problems working on them now troubleshooting being creative connecting with each other finding a community discovering their strengths along the way for me after running workshops in the community for a number of years when I returned from introducing coding to young street kids in Bangladesh I realized I had skills and experience so I set up my business hacker Famicom my first monetized fehmi's coding boot camp at Rice London Barclays Bank it was a sellout and a few weeks later shows my second I haven't looked back since but it works the opposite way - all the money raised enable me to buy robots for my community events and I was able to cascade my end price knowledge across to other young coders - when you focus on business problems you get active enthusiastic support from enterprise and then you can take on anything the support is great and we have tons of ideas but what does it really take to execute on those ideas to get things done can-do attitudes what open source needs you've seen it all this week we're all explorers ideator z' thinkers and doers open source needs people who can make the ideas happen get out there and see them through like I did setting up Safford and raspberry jam as an inclusive space to collaborate and learn together and that that led to organizing the young coders conference this was about organizing our own two-day event for our partners in industry to show they value young people and wanted to invest in our growth it doesn't stop there oh nice now I'm setting up monthly coding meetups and looking at ways to help other young people to access job opportunities in end price and digital services the underlying ethos remains the same in all I do promoting young people with the desire to explore collaborative problem-solving when coding digital making and building enterprise you fled having the confidence to define our journey and pathways always being inclusive always encouraging innovation and creativity being doers does more than get projects done makes us a pioneering force in the community dreaming and doing is how we will make exponential leaps my generation is standing on the shoulders of giants you the open-source pioneers and the technology you will built so I'd love to hear about your experiences who brought you into the open-source community who taught you as we go to upscale our efforts we encounter difficulties have you and how did you overcome them please do come to talk to me I'll be in the open-source stories booth both today and tomorrow giving workshops or visit the Red Hat page of my website hack Famicom I really value your insights in conclusion I'd like I'd like to ask you to challenge yourself you can do this by supporting young coders find the crowdfunding campaign kick-start their ideas into reality I'm proof that it works it's so awesome to be an active part of the next exponential leap together thank you [Applause] so unbelievable huh you know he reminds me of be at that age not even close and I can tell you I've spent a lot of time with Femi and his mom grace I mean what you see is what you get I mean he's incredibly passionate committed and all that stuff he's doing that long list of things he's doing he's going to do so hopefully today you get a sense of what's coming in the next generation the amazing things that people are doing with collaboration I'd also like to thank in addition to femi I'd like to thank Sauron Sarah and Ellie for equally compelling talks around the open source stories and again as I mentioned before any one of you can have an open source story that can be up here inspiring others and that's really our goal in telling these stories and giving voice to the things that you've seen today absolutely extraordinary things are happening out there and I encourage you to take every advantage you can hear this week and as is our theme for the summit please keep exploring thank you very much [Applause] [Music]

from San Francisco it's the queue covering Red Hat summit 2018 brought to you by Red Hat hey welcome back everyone live here in San Francisco California Moscone West is the cubes live coverage of Red Hat Summer 2018 I'm John furry and my co-host John Troyer our next guest is Denise Dumas vice president software engineering operating system group the Red Hat welcome back to the cube good to see you thank you so much great to be here with you so operating systems Linux the base base with everything yeah now you got all those other goodness going on you have some acquisitions permit bit we were just talking about before he came on a lot of action going on yeah what's new well you know you think that the world of operating systems would be boring but honest to god it is so not especially now right because there is a whole generation of change going on in the hardware and when the hardware changes the operating system has got to change to keep up right you look at the stuff that's going on with GPUs with FPGA right I mean and that's just like tip of the iceberg yeah and everything has to be programmable so you need software to keep track of it so it's not just the patches you gotta keep on top of the DevOps automations a big part of it and security models are changing with the cloud there's no perimeter so you have to have maybe chip level encryption os the way up this is challenging so what is it what's the impact to Red Hat as these new things come on because you know you got you know fishing out there sphere fishing is a big problem you got to handle it all how do you guys handle all the security challenges well you know it's it's actually interesting because rel is the base the core of Red Hat's product line which means that we provide the firm underpinning for everything else in the portfolio so we have the FIP certification we're doing the Common Criteria certification we provide the reliable crypto that everybody else can just expect to have in their world and we have to be the really firm basis for everything that layers on top and it's really great to have the additional products in the portfolio working very closely with us to make sure that we can be end-to-end secure end-to-end compliant and that we're looking at the bigger problems because it's not about the operating system it's about the infrastructure and what you're going to run on top of it right a lot of people have been saying security oh it's hard to do security open source is actually a problem for security and then the world shifts back and says wait a minute open source is better to attack security problem because it's out more people working on it versus the human problem of having proprietary so obviously open source is a good thing - security what's the modern approach that you see now that that that you guys are watching and building around that because that's the number one question that coot at kubernetes con we saw a great thing do some kubernetes we saw is do service meshes but Security's got to be thought of on the front end of all the application developers that means it's on you put it into the OS and it's a different world right because the application developers are not accustomed to having to deal with that because that was always the job of the IT guys right that was a problem for the infrastructure to deal with and so clearly we have to provide better security better better tooling available to them but the operations guys right they still they need help in this new world as well because suddenly there's this explosion of containers in their environment and who knows what's in those containers right we've got to have the ability to scan the containers and make sure that they get patched regularly right so it's just it's a whole different set of problems but it all starts with making sure it's secure underneath all the rest of it well so that's that brings up the console of this concept of layers right there's all the operational things there's the apps and the containers and then you know rail is running underneath that that's the hardware and the micro code and all the rest of the stuff so this year we the whole entire IT industry - the kind of a gasp with with the meltdown inspector problems that that surfaced or you know I guess it was in January I think yeah when they were Republican what that was that was how the colonel team spent their Christmas vacation oh my goodness yeah I the colonel team the performance team the security team the virtualization team all those guys so Red Hat shuts down for a week at Christmastime if they didn't yeah that was exciting I mean we've been trained security is one of these things but there's another one coming because cyber attacks are there what's that what's the viewpoint how do you keep on how do you how do you keep on top of it yeah well you know we have a fabulous security team so if you happen to get up to the second floor go talk with chrome Chris Robinson his guys they monitor what's going on in the upstreams they work with mitre they work with the organization's right and when they discover that something is in the wind they come to us and disclose people as needed and then we get to go and figure out how we're gonna get fixes in usually a lot of this stuff happens as you know under embargo so we really we can't talk about it that's a real problem if a lot of the upstream hasn't been read in right so like for instance with meltdown inspector a lot of that was going on not so much in the upstream so there were kind of divergent patches that we got to bring back together that was really we knew that well we had a really strong suspicion that the embargo was gonna break early there that's why my guys were over Christmas right they had to have something ready secure for when it broke and then we could worry about the performance afterwards yeah right and then you had to roll that out into the entire customer base there's some fairly standard mechanisms was there anything special with that because it was fairly high priority I suppose yeah well I mean anything like that we make available a synchronously cuz we want to have it available that the day that that embargo goes public right because that's when we're gonna be getting the phone calls that's when people say oh my god now what do I do but if but the hard part with this one was that you had to have the microcode as well right but we had to do a lot of Education because this was this the side channel attacks it's just a different way of thinking right it's not so much a flaw in the code as in the overall hardware architecture that we get to deal with that stuff what did you learn what's the learnings that were magnifying we have to be as transparent as we can possibly be because security researchers are going to keep on looking for this kind of flaw and we you know we just have to be able to work as much in the open as we can but we also have to have an education function right this is not an area of core expertise for a lot of people who are working in databases right or who are who are designing Java apps and yet we have to be able to explain to them why there's a performance impact on some of the stuff that they're doing and how we can work together to try to get back some of that performance over time no meltdown inspector that's kind of off my radar now but I don't think we're completely out of it right you people have had to patch and reboot and and update but it sounds like we're not I don't think we're at 100% for sure of all systems yeah well you know IT infrastructure right there's your window in which you can actually afford to reboot your systems and I think a lot of those are very tightly scheduled I mean we have customers who get you know ten minutes a year yeah up times of years and years I mean old rebooting is kind of old fashioned at this point yeah really right as it should be as it should be but but when it's the minor code you're kind of stuck yeah I mean that's a hardware thing getting back to the hardware still hardware's even though cloud is extracting away the complexities Hardware still is out there so you never gonna go away for you and as you said it's changing look at the GPU side and you got all kinds of new things coming on the horizon like blockchain and decentralized infrastructure that's encrypted amen right so you know this is you know systems level code mm-hmm with software guys who don't know micro code mm-hmm so you guys got to be on top of it so so I guess the big question is is that operating system that you guys have is very reliable and the support is phenomenal use of industries how do you take the support and the engineering in rel and operating systems and bring that operate system mindset to the next level up as you move up the stack kubernetes new OpenStack as well openshift yeah and apps they all want the same reliability you all want the same kind of robustness nature of an ecosystem at the same time more people are being certified yeah so you have a balance of growth and reliability how do you how do you guys see that and it's also speed and time to market right which is the other factor because there's so much pressure on any emerging technology to get the features out there that you end up carrying the technical debt right or you end up not being able to be as hardened as you might like to be the instant that you go out the door and so it's always gonna be a balancing act and a trade-off so you I know you guys were just talking with Mark Oh bill Peter and he was probably talking about how we're trying to focus on use cases right we need to understand the use cases that our customers have and now those are clearly across the entire product portfolio right but those are the test scenarios that I need to get in flight and those are also the the paths that I need to make sure we've optimized for right and so it's a partnership with the rest of the products in the portfolio and we really do a lot to work together as tightly as we can which is one of the benefits of being at the core right I'm working with everybody yeah and you got the instrumentation too so the other theme yeah the automation big time theme here is breaking down the two of real granular level sets of services which actually is a good thing because if you can instrument it then it's just easy to manage because then he can isolate things so I mean this is a good thing in the OS people love this because you can see couple and make things work well but the instrumentation if you have the API API and you need the instrumentation and looking in so how is that created a challenge because it's all those great for Red Hat's business and then you see in the the forecast and the analysts are seeing the growth you guys are seeing the successes but it makes your job harder a bit that one's a harder but I mean it's you know you get it right more code and make glue layers of abstraction layers yeah but I wouldn't want it to be boring well I do want it to I want it to be boring for our customers I want our customers to just be able to pick up and no drum and exciting homes not ringing with no spectra again it's working like a charm no problem yeah drama llama does not live here yeah yeah that's an interesting point though just a lot of talk about the whole Red Hat stack here right and you got as we've said you the base of it where does where does Linux where is this Linux and especially rail go from here what are you looking at that over the next few years some different technologies you're looking to pull it etc mm-hmm there's always I mean we have to keep up with the hardware advances clearly right but then there's let's oh look at our permaban what a great ad right so perma bit for people who don't know they do a video virtual data optimizer so they do D dupe and compression on the fly on the path to the disk and with rail 75 as part of your subscription you get so we buy we buy companies and we open-source their soft code side their software and we make it available to you as part of your subscription right how good is that so is when you deploy 75 in your environment now suddenly you're gonna need a whole lot less storage right depending on of course it depends upon your data footprint right but but you might find that you're able to shrink the amount of all that expensive storage and expensive cloud storage particularly that you need significantly and you get the compression right was avenge compression was very popular we know we followed in fallen permit bit question on permit bit for you was that open source was that they build their front open stores because now and are you guys open sourcing that that's okay so you have to go gain and and then open it up and do a review and clean it up and yeah yeah and we have to help them get it into an upstream right so they actually they were fabulous the perma because they have been so fabulous to work with best acquisition ever seems to be pretty good at acquiring companies and incorporating their tacit that seems to be part of the culture here yeah that's cuz we're not you know people think we're like big and scary right I'll tell you I have worked for companies that are big and scary Red Hat is not it we're really open and it's really in many ways in engineering culture which is wonderful it's a great fit if you happen to be from a startup culture because we don't overwhelm you with process right I mean we a lot of smart people again I can attest to my interactions over the years smart people very humble a lot of systems people to which is cooperating system hello the world's turning into an operating system good for that but humble and plays the long game you guys I've been you deserve credit for that and that's that's attracting and reason why you successful but you know the thing is we really believe in our core values right we really truly honest-to-god believe in open source and the power that it has to change the world that you know you say oh yeah sure right she's part of the management change she's gonna see him anyway yeah but you guys are growing so I mean over the years again since we started the cube nine years ago we've watched red add just in that time span grow significantly I'll see it's well documented an alternative to the other proprietary os's second-tier citizen now running the world the first tier great job so the youth success business model of open source is now mainstream but you got to onboard more people more ecosystem partners in a really dynamic big wave of innovation coming yeah how do you maintain the recruiting how do you get the great people how do you preserve the culture I'm sure these are questions how do you the more inclusion and diversity questions this is all happening right they're gonna have to catch him at nine years old and grown I mean although honest to god we do a lot of university outreach right if you look in the Czech Republic for instance we have a huge operation in Brno which is the second largest city there and we are so tied in to the university system we bring in lots and lots and lots of interns and it's wonderful right because we want to teach people about open-source we find people who have passion projects and we bring them in this is this is our world right we don't we want non-traditional people as well as traditional computer science majors open-source is a great leveler your CV is online I mean imagine right you're you want to change careers you want a new life you love to code you've been working on writing games in your in your spare time you are our people that's the code your code is who you are your code is it's your CV well this is what Oh doing your things on the open means and also it's been great for your business and we had gym writers on earlier there's no a/b testing they just go into the community and find out what's they want and they just that's the a B C's e testing it's just right there you guys do the due diligence sometimes make big time real fun decisions on features based upon what is in demand practically speaking not just focusing on the new tech that's a good business model we hope so cuz you know I mean as as one of our former CFO I said there are a lot of people a lot of Associates at Red Hat who are dependent on Red Hat for a paycheck and it's very important to us that we remain profitable stable and and really good for our people right we've got a lot of people that we need to take care of in the time it's a good place to be in the timing spray with kubernetes and containers we're taking it up a notch and bringing that extensibility you know just beyond stand-alone Linux so congratulations Denise thanks for coming on and sharing your perspective as always we love these conversations in the cube talk and everything from operating systems to core OS and kubernetes and culture as the cue here out in the open on the floor at Moscone West John Troy yer stay with us we'll be back with more day two of three days of live coverage on the cube net we'll be right back