 to destabilize the ever-growing strength of the new Jedi Order. A trio of Sith assassins has ambushed one of the last remaining Jedi Force Masters. Their mission? Eliminate him and through the new Jedi Order leadership into chaos. Face me Jedi! I have no conflict with you Sith. Perhaps not, but however your destruction will serve to cripple the Jedi Order. I see. And worry your two companions. Not far behind, but by the time they arrive I will have your head. We shall see. No one loses their head today. I hope that that Jedi puts up a worthy fight when we find him. It would be good to have a true challenge. You believe your skills to be match for a Jedi Master. You should not underestimate my power Master. Really? Show me. Shiva, did you locate the Jedi? She did. Unfortunately for her, you will die today Jedi. That's what she said. I told her I didn't want to fight. Unfortunately Jedi, we do. I did not want this. Surrender now. Lack the will to destroy us Jedi. I don't need to destroy you in order to defeat you. For I am one with the Force. And the Force is with me. Please welcome Red Hat Executive Vice President and Chief People Officer, Delissa Alexander. May the Force be with you. Good morning everyone. Wow, it's been a great week. It's the last day, our grand finale of our Red Hat Summit. What an amazing week it's been. We've heard so many stories about the impact that individuals are having on the lives of others using open source technologies. And today the conversation continues starting with our Women in Open Source Awards. Red Hat created this award to highlight the role that women are playing in open source. And I'm excited and honored to be here today to be able to share the winners with you. The process looked like this. The community made nominations, many, many, and we had an outstanding set of finalists. And over 14,000 of us voted. Thank you for your participation. Two incredibly inspiring women who use open source to break down barriers and open doors are our winners. And I'm excited to be able to share them with you today. First, let me tell you a little bit about our academic award winner. At an age when most young women are just starting to think about entering the workforce, our winner is already sharing her mentorship with many, many young women in technology. A technologist herself, she was surprised when she went to university and saw so few female classmates. But rather than accepting the status quo, she decided to make a difference becoming the director of the Delhi chapter of the Women Who Code and also a mentor for the organization Learn IT Girl. She's an open source contributor contributing to the programming language Fero, and she's receiving research grants from around the globe, and she hasn't even graduated from college yet. Who's this woman? I'm going to keep you in suspense while I share a little bit about our community award winner. This winner is an innovator and an activist. She believes that open source is a platform to break down traditional barriers. She leads the organization Kids on Computers, and she recently co-founded an open source platform called For a Living that allows students and professionals to connect to help the students think about their career possibilities. Other open source contributions include creating the framework that eventually became Open ACS and helping to co-lead the open source track at the Grace Hopper Conference. A longtime technologist, she recently joined Amazon on the Alexa team. Now it's my distinct honor to introduce you to our award winners. I believe that we rise by lifting others and by helping others step into this alluring world of open source has not only impacted them, but also it has created a ripple effect. I realized how much technology had changed my life, how much it had given me access to learning. I just wanted to help other kids who didn't have that access have access to it. My ultimate goal is to contribute something to this technological world and bring new people, especially more women, to this world of open source. I always had this dream of setting up computer labs in underprivileged areas or in developing areas. So I put in my five-year goal. I want a set of computer labs in developing countries. I went to this awesome conference, the Grace Hopper Conference for Women in Computing, and I was so inspired by this conference of like 2,000 women. It was like amazing. So I came back and I looked at my one-year, five-year and ten-year goals and I was like, why do I have to wait five years to start doing this? Coming from an all-girls high school to a university, it was very discouraging to see the disconcerting sex ratio in my batch. This urge to change the perception led me to join many inspirational communities and tech societies. I just want to help bridge the gender gap in this world. I have helped set up these labs with the hopes that kids will be able to utilize the technology and get access to educational content that they don't otherwise have. We're hoping the kids will see what's possible and then come back and help improve their own lives, their family's lives and their community's lives. My vista of life where I'm associated with so many inspirational communities and tech societies, not only provided an important pedestal for me to learn but also to give back to the community. Be it teaching kids or teenage developers to start programming from scratch, to helping women shift their tracks to tech careers and then helping graduate female fellow developers to jump into the open-source bandwagon. Working with different communities and helping people lift is what has created a ripple effect. It has been a pretty exciting journey. I think one thing you realize as you go on these trips is how much one trip can impact the community. I think my dreams have just become grander and my ambitions have become like I can really change the world. Join me in welcoming to the stage our 2017 Women in Open Source Award winners. First our academic award winner, Jigyasa Rover. And now our community award winner, Avni Khatri. These are your 2017 Women in Open Source Award winners. We're next at this way. Please welcome Red Hat Executive Vice President and Chief Marketing Officer, Tim Yaten. Good morning. Good morning. Welcome to day three of the summit. I had my welcome to Delices. So glad you could be here. For those of you who were at the Red Sox game, I hope you had a great time. It was really a treat. I'm a local guy, but it was really a treat to see all the Red Hats in the audience. And it was great to see how many of you made it on the Jumbotron. I'm just a little worried how many of you remember that you were on the Jumbotron since most of the pictures were like this. So hope everybody had a good time. So one other thing I'll just mention at the outset. So one of the things I like to do is to always be on brand. So as you can tell, I've got my red handkerchief. I've got red belt. I got my pin. But today, in deference to the Red Sox, my Red Sox are Red Sox. So there we go. Okay. Enough about me. Although I could go on if I had to. But today is really about two things. The theme of the summit is the impact of the individual. And one of the things that we've done as a company to start to highlight the impact of individuals is tell open source stories. Now, I've been in the industry for 37 years. I was around open source before we even called it that. In fact, a lot of the roots of open source come out of UNIX, UNIX collaboration, a lot of things that happen here at MIT and at Stanford. So if you look at the history of open source, it really started with licenses that made it easier to collaborate and share. But at that time, it was all about creating low cost replicas of existing technologies. But something interesting happened over that period. As a technology industry, we learned how to collaborate. We learned how to collaborate in ways that we never thought of before. So fast forward to the last five or 10 years, most innovation that's happening in software is happening via upstream open source communities. Like things we've never seen before in terms of cloud, mobility, AI, all these things are actually being innovated via open source communities. Well, that model of collaboration has now scaled well beyond software. In fact, it permeates almost every new human endeavor to solve big challenges from healthcare to education to agriculture. So it's become it's moved from just a basic collaboration mechanism to build better software to the font of innovation for technology. And most importantly now, the the means and inspiration for attacking some of the biggest problems that humankind faces. So with our open source stories, we want to bring life to some of these amazing efforts that around this notion of open source collaboration have caused great things to be done and great things to be pursued. Now interestingly enough, the first open source story we told was that the summit two years ago. And it featured a person that will name Charlie. Now that's good because his name really is Charlie. But, you know, he was instrumental change agent at Penn Manor, changing how kids learn by interacting with computers. And, you know, the story is amazing. And he's back two years since to be able to share the story of what they accomplished. And we want to recognize him as an example of, you know, the impact of the individual, a single person with lots of passion, and lots of stick to this fundamentally changed how students were in learning and how they were inspired. And so with that as backdrop, I'd like to cue the video. We know that learning is a system of trial and error of failures, right? The system is telling our teachers and our students it's not okay to fail. Sometimes they're going to fail spectacularly, but that's how you learn and that's how you grow. When I think of Charlie, I think about the very first time my introduction to Penn Manor was one of my very first meetings and then walks this guy that has hair like Malcolm Gladwell. I joke with him that if you ever got a cut, he'd have to rebrand himself. But one of the things that amazed me about Charlie in that first meeting is he wasn't just somebody who ran the tech. He took the time to explain to a room full of teachers how the technology worked, why it was able to do what it did. Knowing the back end and knowing how these things work allowed us to think about how do we use this in our classroom or how can this be effective? Education is without a doubt the most important human endeavor. I mean, everything flows from education from from learning. Several years ago, we began discussing the feasibility of issuing one laptop for every one of our students. We've given our students tremendous trust and responsibility and the ability to customize their own machines. And that's quite unusual for a public school to follow that trajectory. I'm Kyle Smith and I go to Manor Middle School. I am 13 years old and I love to program. Charlie taught me programming for websites and how to program a C file and I have taught my friend how to do that now. I've learned a lot of complicated programming languages now. Ruby, place on Java. I'm probably an expert at HTML now. I'm going to go to Penn Manor High School. There's a student help desk and I'm definitely going to work there. Charlie is infectious. He makes you want to strive to not have the kids be bored. It's always what can I do to help? How can we get rid of the typical paper pencil in your classroom? And I just love how it's changed me as a teacher. It wouldn't be possible if Charlie didn't introduce this one to one laptop program and convince us that it would work. It's not about a curriculum or a computer or a software. Everywhere we look, we have people who are curious, who are investigating, who are taking something and making it better. That's what I think Charlie brings to the table. He brings a passion for learning and a power for transforming our schools into something better than it is today. By unlocking devices and giving kids truly open technology, it empowers them to not only understand what's underneath the hood, but understand that they can impact the world. So and just like Charlie and the leadership he showed and the inspiration he brought to all those kids, you know, many of you in the room do the same things for your organizations, your pioneers and champions of open source and of a lot bigger ideas to help move society forward. So before we proceed, I'd just like to let you know that Charlie's here, as is Mike Licklider, both from the Penn School. And we just wanted to honor him as sort of the embodiment of the individual impact. So Charlie, so Charlie, just one thought, though. We'd really like to get Kyle's resume because we're always looking for HTML5 and Java expertise. So awesome. Thank you. So we wanted to just highlight all that work, you know, after two years, you know, you look at the inspiration in those children, you know, the way they're acclimating to programming STEM, you know, it's just awesome. So thanks to you both, you know, keep it up, you know, we're going to be rooting for you and hopefully we'll see an update in another two years. So thank you. Okay, next thing we'd like to do is talk about what we're going to do from here in terms of these stories. So as I mentioned, our concept of open source stories is to bring to life bigger ideas that fall out of the open source collaboration style model. And we've got two new stories that we want to introduce you to you today. The first is Alicia Gibb. She's executive director and founder of the open source hardware foundation, which is helping to drive the future of physical systems. And also Caleb Harper, who is principal investigator and director of the open agriculture initiative driven out of MIT, right here in Greater Boston and Cambridge. So these are two examples, new examples that you're going to hear from live today of similarly powerful stories of how open collaboration can change other elements in our lives. So with that, enjoy our two next speakers and enjoy the last day of the conference. Thank you very much. Please welcome open source hardware association founder and executive director, Alicia Gibb. Hi, I'm Alicia Gibb and I am so honored to be here. I'm the executive director of the open source hardware association. And some of you may recognize me. I've also been helping solder badges with little LEDs out at the BTU lab in open source stories booth. So if you haven't gotten a chance, please come out there. We've put some kits at your chairs. So some of you already have the kits that you need to solder together and you can come see us or take this home with you. But first, I'm going to tell you a little bit about how I got here. So I got my start in library and information science, where we were taught a strong understanding of freedom of information. That ported naturally to open source for me, which I learned about for the first time when I learned that you could right click on a web page and view the source. Yeah. So I was blown away. I thought this is freedom of information. I instantly traded my books for code and microcontrollers. And I found myself enmeshed in a world of hackers as I was one of the foundational members of NYC resistor, a hacker space in Brooklyn in 2008. I loved the motto, we learn, share and make things. I had found my community. I wrote my art history thesis on the Arduino micro controller. I started a job at an open source hardware company and I founded the open source hardware summit. All of this led to founding the open source hardware association in 2012. We like to call it Oshawa for short. And I'm proud to be here representing the nonprofit that brings open source to a new layer of our products. Together I'm hoping that we can create an open source future. But first, before we did anything, the open source hardware community had to create a definition. So we did what any good open source group does. We started an email list. Business owners and hobbyists agreed on these six attributes as what you needed to do to call your hardware open source and apply this gear logo. And over the years we realized that we needed to add some clarifications. So we came up with this checklist. One of the things on this checklist includes, are you emotionally prepared to be copied? We had to make this addition because people would email us saying, I open source my hardware and somebody copied me. Help. What are you going to do about it? And we would say congratulations. You successfully created open source hardware. But that wasn't the answer they wanted to hear. They were expecting something a little different. And I think this is happening because we have people coming from the product side who haven't yet been involved in an open source project or an open source community. But this is really exciting because this means that overall, we're reaching more people. And speaking of reaching more people, many of you have probably heard of or played with the Arduino micro controller. This is one of the most successful pieces of open source hardware. And although that open source hardware was started with ham radio, the Arduino now has given open source to many industries across the board. It was originally created for artists, designers and educators, but now has been ported to projects like the open curiosity project at NASA or humanitarian projects like safecast, which is an open source geiger counter that was used after the Fukushima disaster. The Arduino has been copied hundreds of times. And it's important to remember that Arduino was a derivative itself. And it reminds us that it's okay to be copied. We should use the potential of the whole community and build on each other's ideas. My favorite derivative is the purple circular one that has pedal looking things around the circumference. It's called the lily pad. And it's the first wearable micro controller. So the little pedals around the circumference are so that you can sew it into clothing with conductive threat. This is created by Leah Beakley, who is getting her PhD at CU Boulder. And lucky for Leah, there is an open hardware company right up the road to manufacture her goods. This is my favorite example because I just really doubt that the Arduino team would have ever considered making a micro controller that you could sew into clothing. Arduino's open source philosophies have led straight into classrooms, R&D labs, and hacker spaces. There's new ways of learning that have emerged as kids can now play with electronics and robots and hands on classrooms around the country. And R&D labs are making strides in new discoveries, such as this body suit that's enabled with a lily pad that helps people with paralysis learn to walk again. This is an example of, as Red Hat says, thinking the open source way. This is our present day reality in open source harbor. We have everything from open source tractors to open source fashion. Fashion's a really interesting industry to have open source in. Fashion can't be copyrighted or patented. So it's already in a way inherently open source. So when creators put the open source hardware logo on it, it's really trying to show the true intention of the company and how they want the users using that product. It's often said with open source that if we couldn't have patents, industries would fail. But what happens in an industry where you're not allowed to have patents or copyright, they innovate four times a year with a summer, fall, winter and spring collection. Now, I couldn't talk holistically about open source if I didn't mention the Internet of Things. And this here is the thing as an Internet of. The Internet of Things is the poster child between software hardware and data coming together. And with IoT, open source hardware will be important to security just as open source software has been to well, you know, everything. With hardware, we need to share the responsibility of security and the future of IoT is already enormous. So let's make that future open source together. There are of course other useful applications in open source hardware and IoT. For example, this Wi-Fi-enabled flamethrower. But you never know when a slightly silly project will be the next inspiration for why the Mars rover is able to land safely. I mentioned the BTU lab earlier, which is a lab that I direct at CU Boulder. And I have students and they're making all kinds of silly things every day from an analog Internet literally made out of series of tubes to an Amazon button that instead of sending you tied when you push it, it prints you a cat from the Internet. And what excites me most about that is the potential that these students have to transfer that knowledge. This is the open PCR. I used to believe people when they told me that open source hardware would never stand a chance in the medical industry. And then this came along. It copies your DNA. Hospitals spend tens of thousands of dollars on machines like these. But this one you can put it together yourself. It's $599 and you can buy it on Amazon. With more innovations like these with open source, we can hope to make the medical industry open source as well. Thanks to DIY bio and 3D prosthetics, the FDA is also taking note of open source hardware. I was fortunate enough to meet a representative from the FDA at the White House last summer when I went there to speak on open manufacturing. They told me that the FDA isn't really interested in stopping people from personalizing their own devices. They realize that this is going to happen. So instead they're trying to educate communities like the open source hardware community on their failure mode analysis and on the quality systems regulation to help everybody create better devices together. This is incredible that a government entity has taken note of open source hardware. And this brings me to suspending reality a little bit. So we've seen the amalgamation of hardware and software coming together, right? It's been happening for years. But when we talk about source and open source hardware, we have to suspend reality a little bit. This is what I call the atoms versus bits conundrum. With the source and hardware, you don't always get the product. Although 3D printers are making that easier. And with a little more research in 3D printing, I hope that we'll be able to print components or maybe we could even turn our 3D printers into desktop chip fabs. This would really push the IC industry further open source if people could create them at home. Currently, most ICs that we deal with in open source hardware are closed. So there's a layer of the source that's not able to be open. We also don't know where our raw materials come from. So far, the atomic layer isn't one that the open source community has termed important enough to be considered in our source. And perhaps that won't matter until we have interstellar space travel where Earth Copper is differed from Nimbus 3 Copper. One of the other biggest differences in hardware versus software is copyright versus patent. So our biggest ask to date at Ashwa has been for a certification program which we came out with last year. And one of the reasons that we came out with this is that we started to have Fortune 500 companies asking for something with a little bit more legal teeth in it. So the way that the law works with hardware versus software is copyright versus patent. And all of you know that it's pretty easy to license something under copyright. With hardware, it is very difficult to license something without a patent. And our community doesn't want to go get a patent just to license it openly. So Ashwa came up with a hack. We created this trademarked logo. And although it's couch and trademark, you can still apply it to your hardware board. And it adds some protections where it fits in nicely with some of what the Fortune 500 company lawyers were telling us that they needed. It also creates a database of open source hardware projects with links to their source. Next time you're working on an open hardware project, we really hope that you certify it. We want to gain your support for open source hardware. And we want to give you a little bit of support through the certification. The more we band together, acknowledge our overlaps, and develop in unison, the more the community becomes open source. If we dream of an open source world, that world includes physical products. We need to be thinking more holistically, but we need help from the FOSS community to do that. So next time you're playing with a piece of hardware, ask yourself, is there an open source alternative available? Thanks. Please welcome the principal investigator and director of the Open Agriculture Initiative at the MIT Media Lab, Caleb Harper. Hello. Oh my gosh, I'm so excited to sit in front of all of you and give you so much work to do. So get ready. All right, let's go forward. There we go. So if you don't know the MIT Media Lab, I thought I'd give you a little bit of a brief about it. I lead a group there. Inside of the lab, there are 30 labs. We share no content in common. What we share, which was mentioned previously, is suspended disbelief of anything. They call us the anti-disciplinary. MIT says we have no discipline. But inside, we chase after dreams. One of those dreams is Professor Hugh Hare's work. Hugh lost his legs when he was a young man. He's been building and rebuilding his own legs for the last 20 years. And when you talk to Hugh, you'll say, oh, this is great. Disabled people can walk again. And he says, no, this is human 2.0. I make myself taller on dates. I make myself shorter to ride on planes. I put picks in my feet to climb mountains. And so in addition to that, there's another group. If you remember that toy where you put your hand through one side, and it came out the other, they wanted to do teleportation. So they said, OK, we'll create a device where anywhere in the world you can manipulate an object. So what they created is called Inform. You can see it's using computer vision, replicating those hands inside of a dynamic platform so literally you can be anywhere in the world and play with the ball. So that brings me to my work. If I said the word food crisis to you, it's likely that even all these people in this room would be thinking something different. Not enough food. Not too much food. Algal blooms in oceans. Food security. GMO is a curse. GMO is the savior. There's not enough water. We're polluting our rainforest. We're cutting them down. The land of the farmer is being taken. Small shareholder farmer. I try to create a derivative in my work. How old do you think the average apple is in the United States grocery store? From the day it was picked till the day it got in your mouth? Two months, six months, 14 months. At 14 months, 90% of the antioxidants of that apple are gone. It's basically a little ball of sugar and cellulose fiber. So we're on the verge of a revolution in agriculture because our system is starting to fail. The first one changed society fundamentally for forever. We're no longer hunters and gatherers. We're now farmers. Second one, agricultural revolution, the base of technology, base societies. Third one, rapid urbanization created all of our cities. So what will the fourth one have? The fourth one will have a climate democracy. And what I mean by that is this map, the most beneficial climates in agriculture are in blue, the least in red. They move and they change and we're slave to climate. One of the big questions of my work is can we start being a designer of climate? Can we put Napa in India, Bordeaux in Africa? The second one, super serious as always, can we make wonka vision? So take that candy bar, process it, send it through the air and reconstitute it on the other side or in another way, in a world where Pokemon Go had more users than Twitter and Tinder combined in a week, can we not take data to describe physical objects that we eat, send them through the air instead of shipping them and reconstitute them with the same properties? And the last one, I went to Fukushima after the disaster. When I landed, it said the headline that day, Japanese agriculture has no money, no youth, no land and no future. But it isn't just Japan. In the United States, 2% of us are involved in agriculture. The average age of a farmer? 58. The next generation? Not standing there in line. Not seeing a future that they can participate in. Half of the continental population of Africa, under 18. 80% don't want to be farmers. They don't see a life that they can live, that they've seen their grandparents suffer through. So we've got to create a billion more farmers. So we need a movement. We've seen Coder Movement, obviously. Thank you, everyone. We've seen Maker Movement or in the middle or pretty far advanced. We've seen Network Movement. This is why Uber is now doing what it's doing and obviously Airbnb and all that stuff. We're up next for the bio movement. In a lab that never had anything to do with biology, the Media Lab, we now have six out of 30 labs doing biology. The convergence of life science of the digital world and bio is happening at a rate that I don't think anyone knows exactly where it's going to go. Movements need tools. So I've been developing tools for climate democracy. Inside of this little lab, this was five years ago. There's a lot of cool technology and I'll talk about it. But I think most interesting thing, 60 square feet in the Media Lab produced a harvest once a month. We took all those plants out and we started, we created a pick your own lettuce patch for nerds. In this lettuce patch, we had roboticists, data scientists, algorithms experts starting to see these bright, white roots, these deep green colors and get inspired to do something about it. So in that process, I used to take the plants out, bring them back into the lab if there was some left over because if you grew it, you're proud of it. And it would taste sweeter the next day. So I got mad at all of my students and I put up cameras and I thought they were doing things to mess with me. But it turns out I was a technologist falling backwards into plant physiology. A plant under stress creates biochemical change. It's defense mechanisms. So I thought if we could code climate, then we could code flavor and nutrition. So then we built this lab a couple of years ago now. Inside of this lab, there are 30 network sensing points per plant, things like CO2, O2, temperature, humidity, light. If you know about the genome, I'm talking about the phenome or the phenomena that if I had a digital twin, that physical twin and he worked out a little bit more and he ate differently, he might look different, he would certainly taste different. That's the exact same thing that's going on inside of this environment. So we've grown all kinds of things with all different technologies to reduce water consumption to increase speed of growth. We've used ancient and rare genetics like these tomatoes from Svalvoord. Never been eaten in 150 years. Bring them back to life. Search through them for what they have to give people rather than what they have to supply to fit a supply chain. Those environments are very big and what I needed is not bigger environments, I needed more instances. So we created something we call the personal food computer. We put that food computer out with a Unity-based game. That game had a digital environment. It was linked to a physical environment and it had sensors and actuators. The kids chose a recipe that was created by somebody else, actuated it in their food computer and then they get curious. How much CO2, how much humidity? Why does a plant need CO2 anyway? Crank down CO2 plant dyes, kid learns a lesson. In the meantime, they harvest the plant for physically and then digitally. That digital harvest creates a derivative recipe. They've now started mapping the phenome or the ability of that plant to express. I gotta go faster. All right, we've put it into schools. The craziest thing that happened is we had a teacher build the climate of the past using Farmer's Almanac data, using real-time data, build the climate of the present, and using predictive models from Watson, build the climate of the future. So it's a lot more interesting than the biology I took, which is why I became an architect. We're building this lab right now out at the old linear accelerator at MIT. We're just scaling up the work. We launched the version 2.0 food computer at the White House a few months ago. It's awesome, you'll see. Data. This hardware produces phenome data, and we do it non-invasively, so we're using things like computer vision. We're using mass spectrometers. We're using this brain box. This brain box all open source, all running on all the things you know. We then do invasive testing. We say, okay, terroir, what's terroir? We unpack that. We figure out what are all the minerals? We take the water and we sequence it, and we say, what's the root microbiome of this plant? We take the plant forward and we do gas chromatography and mass spec to say these things that you're looking at that seem super weird, these little compounds, that's flavor. That's a secondary metabolite that the plant has produced as a reaction to stress. So we're trying to figure all of that out. That amounts to about three and a half million data points per plant per grow. We call that the recipe. We put the recipe in, we have an interface for you to check it out, and it goes into the robot. Actually, part of our system is designed on Ross so it makes a whole lot of sense. That robot can then do things, create data that we do machine learning and artificial intelligence on. When you're talking about the vast number of variables and the vast number of expressions, this has never been mapped in human history. So we've started going through that. What you see on one side is kind of a multivariable analysis of all of that with a heat map. We say, how do we make it bigger? We get a trending heat map of three corollary data sets that no one ever knew before. We then take that forward, do visualizations of it. We even create models and run real-time weather data to predict where yield would be in the world. We did our first one about a month ago. We were 75% accurate based on historic data from the FAO and historic data from weather stations for the last 30 years. You might think I'm crazy and maybe this isn't coming anytime soon. It's already happening on the space station. Space program's been doing it for a long time, in fact. But it has landed on Earth. This is a factory in Japan. They call it Plant Factory. It's like the worst name you could ever call something. It does a million heads of lettuce 365 one week every day of the year. But you've maybe heard about the lettuce part of vertical farming or control environment ag, but maybe you haven't heard about the next one. Oh, if we can go back. Well, there we go, play that video. What do you think is growing in here? Looks kind of similar to my lab. Don't know. Little tiny plant. Ebola vaccine. So this is a DARPA project that's using tobacco, tobacco mosaic virus to produce an Ebola vaccine. This is one of the reasons we got ahead of Ebola and Sierra Leone. This plants give us everything. Pharmaceutical, natural derivatives, cosmetics, nutraceuticals all the way down to the things that you think about and the things that you eat. So this brings me to my last point and I'm already over time, so get stoked because this is about you. We put everything out, open source, GPL 2.0, creative commons on the hardware, even though we don't have a better option and Mozilla science data license. We put everything on Wiki. We created this community. The community, as you know, is raucous. They're throwing all their ideas in there, usually asking me for an answer. If you're watching, I have no answers. So join the community forum. Please come in, start learning. We've put this out in schools. We developed a climate creator from scratch, if you know scratch. So this is our user interface right now where you design climates across different things. Kids have been building this in what they call homebrew food computer clubs, if that doesn't make you a little bit curious. The last one we've deployed now with the UN in a Syrian refugee camp in Amman. We didn't tell them what to grow. They decided to grow things that they miss from home, things that they can't get anymore. It became a cultural object more than just a manufacturing object. So the community has grown in one year. We've been holding these hackathons inside of the Media Lab. This was 150 high school students that went home, created their own chapter of OpenAg. Without any money, with a very bad backend, with a community that's raucous, we are in 40 countries on six continents with builds. So we had to create a foundation. This is how we're working now. Everything goes out of MIT, open source, collected by the OpenAg Foundation as the commons, and then made available for commercialization. And you guys know a thing or two about that. This is the world today. Any country in a color is food insecure, meaning they do not produce enough food within their national boundary to feed their domestic population. Any color, red. With a purple overlay, these are countries that are not food secure that produce food for other countries. Mexico and us. China is the largest landholder in Brazil. The Middle East gets all of its food from Central Africa. Those strings that you see just barely with the dots, product of the Industrial Revolution, cars, planes, trains, automobiles, we ship our food a very long way. And if you don't know, when you harvest a plant, to when you eat the plant, is how much it has to give you back, just like the apple. This is the future. If you can see those little points. This is where we're growing food to create data and recipe shape, to email it to each other across the world, to get rid of shipping, to get rid of nutrition attenuation. And this future is already being built right now and I really need your help. Thank you. Innovative technology is really important to Barclays because we can't stand still. We exist because our customers need services from us. We've got to innovate and keep up with the times and be ahead of the times in order to secure that marketplace and that's what we're here for. We're just on the cusp of an architectural change towards containerized platform. We've got a vibrant, thriving tech industry. We have real need for innovation in the public service and we have sponsorship to pursue that innovation. El proyecto de modernización y automatización de aplicaciones en el gobierno del estado de Jalisco consistió en hacer un cambio de paradigma. Entonces buscamos un sentido de innovación abierta en el cual Red Hat nos ayuda a acceder a una comunidad, a una comunidad de colaboración y de co creación. We're delivering a production-ready platform for our customers. If you think of the level of collaboration and constant conversations and work that we've done together, it's great to have such a tight relationship and a partnership with Red Hat. The impact is going to be massive on business banking, wealth management and the personal banking areas thanks to Red Hat Technologies. Please welcome Red Hat vice president of customer experience and engagement, Marco Bill Peter. Good morning. Good morning, everybody. It's funny what Tim remembered about the Red Sox game. I felt like back home in Switzerland standing on a glacier. It was so cold. Now this half an hour here is really about our innovation awards. You heard throughout the whole week from Paul, from Jim about our five winners here and these awards recognize technology achievements of our customers and partners worldwide. As you last year saw, we had worldwide participation. We have it this year as well. And all these winners, they really demonstrate creative thinking, you know, determined problem solving, innovative use of our Red Hat solutions and execution, right? All these awards are real, right? This is proof points behind it. And all these categories, they combine. It's not just technology. It's technology and the culture. How can you do that, right? We're going through an evolution and a lot of these winners, all of these winners have shown these transformations. Now the categories are DevOps, application optimization, cloud infrastructure, enterprise transformation and the best use of open source way or the open source way. Based on what happened earlier this year at the Oscars, we want to be a bit more transparent about how we judge. I think this will help you to understand it better as well. We have a total of seven judges. Two, unfortunately, couldn't be here for our personal reasons. Five are here. And each category has one winner that judges selected during nomination process. So we get lots of nomination. We go through all these nominations. It's an amazing experience to read about all this innovation that's happening around the world. Five winners get selected for each category or one each category. And remember, today at the end of the keynote, one of these five winners will be announced as the 2017 Innovator of the Year. Now, let's get the other judges to join me on the stage, please. Now the award judges include a diverse group of talented professionals. Some are red-haters, as you probably recognize Chris Wright and Ashash. But then also we have a customer, the previous winner of the Innovation Award, Diepmar from Amadeus, and actually also experts from outside as in technical analysts or press as well. So we have Chris Rommels representing that. Now, many of these judges actually work throughout the journey of these customers or these partners in their innovation. So they have a lot of insights in how actually that journey happened. So what we want to do is a little panel here and kind of have a few questions on how they see it, how these winners actually went through their journey. All of these winners have obviously solutions from Red Hat. They're using innovative products from us. They've used our services and you know, at Red Hat we don't just sell technology in the license, we sell your subscription around open source, right? Remember that. The subscription includes obviously support, which I represent, but then also documentation, product security, the life cycle, that's all the value. And then Red Hat also provides, as you know, training, you had the opportunity to do certifications here, but then also the great consulting team that you've seen yesterday, a very innovative Swiss story, which I was really proud of. Now, let me sit down here and let's start here with Paul Cormier mentioned in his Tuesday keynote, right? DevOps is changing how enterprise develop and launch applications and services. Now, similar to the process in the open source communities, right? DevOps focuses on collaboration to achieve business goals using IT resources. Let me ask Aashesh, our expert here, how is the industry embracing DevOps? Thanks, Marco. So this is an extremely important topic that we see a lot of discussion in industry today. I think the industry struggled with a few things in the past, which is why we've seen the advent, the embrace of DevOps. From a development perspective, we've found 77% of projects are considered challenged or failed. About half of developers lack significant cloud development experience, but only 23% of developers are confident with the technology choices they've made, right? That's on development side, right? From an operations perspective, what we found are other challenges as well, right? We've found that the cost for a large-scale app that's been written, when it goes down, you know, it's very significant, right? The average number of diagnosed repair and issue is about 200 minutes or so. There's an average of 750 defects in a 50,000-line Java application. And, of course, when this does go down, it costs about $42,000 or so per hour. So I just rattled off a series of stats to give a sense of the magnitude of the challenge and then, obviously, the opportunity that arises for us to solve it. But these are just the technical hurdles I've talked about here. I think we could maybe ask someone like Dietmar what he thinks from an organizational perspective or behavioral change perspective that needs to be addressed here. Yeah, so I believe here we talk a lot about collaboration, so it's important to get the different teams together. I mean, the operational teams, the R&D teams, the development and business people coming together. So DevOps is really a tool to foster collaboration. And by this, it's a cultural change agent. It's really important that we get the teams together to have more productivity earlier discussions and knowledge sharing at the end. So in our case, like I can, there are many examples I can single out one that is currently running, a large project to revisit and re-engineer, to some degree, our e-commerce platform. That's a huge piece of software used by many airlines out there. And what we have been doing is exactly in this spirit, putting the different teams together, everyone from the very beginning on. And so it creates energy and it creates common knowledge and it creates pride. And at the end, it's all about culture, really. It's a tool to implement this collaborative culture. Thank you, Dietman. Thank you, Ashash. Let me ask you one question more specific to the Barclay success story that we heard, right? Their application platform as a service solution was the success of that was really the ability to shift to more innovative, more agile DevOps approach. How did Red Hat help here? And what can the audience learn from that, Ashash? Sure. So I personally spent a lot of time with the Barclays team and they've been on a remarkable journey over several years. But let's just talk about the macro perspective for a minute. The financial and service industry has faced a lot of regulatory pressure. And of course, there's market volatility. We all know that. Increasingly, we find new fintech disruptors that are entering the market. And as a result, organizations like Barclays want to become more agile than they've been in the past to develop new applications, take advantage of existing investments. And we've consistently seen that on the journey that Barclays has been on with Red Hat, right? We've a long history together, you know, with regard to their adoption of their enterprise Linux technologies, Aurel, our JBoss technologies. And building the APAS, the application platform as a service on Red Hat's open platform has been an actual extension of that. And we find that they were doing many more frequent releases for new services. And they were able to have much more support for bridging the old with the new, right? This is the balancing of the existing investment with the new microservices-based application that they were building. Again, an opportunity for collaboration between Dev and ops teams. One thing that's important to note is, you know, OpenShift and container technology is still relatively new with regard to wide-scale industry adoption. They're likely to be growing pains as we go on the journey. So I almost feel sometimes for customers around the problem, technology is obviously something that needs to be overcome, but could almost be, you know, the easier of the problems that they face. And as Dietmar alluded to, the real challenge is cultural, right? How do you shift from large drops of software that happened maybe on every six-month basis or quarterly basis to incremental releases? How do you go to embrace this culture of failing fast, being able to deliver continuously? Organizations like Barclays, and Barclays is a splendid example of this, are embracing DevOps, right, in the public cloud and thinking differently about technology and business infrastructure. And these teams that need to work together, right, they need to become familiar with technology that they're using, the new technology that they're adopting, but also being able to collaborate across boundaries. It's great what they achieved. Thank you. So Dietmar, with your last win, last year's win, right, is you using OpenShift container platform as well. What similarities do you see between Barclays' story and your story at Amadeus? So when I've read the Barclays' proposition, a lot of things reminded me to the journey we are going through. So yes, we go massively on OpenShifter, as you know. So the challenges to master the technology are very similar, and the feedbacks from the teams and the gains at the end are that we have faster releasing on the platform, and the teams are kind of freed from looking to the underlying technical stock because that's now managed by the platform itself. So they are focusing more on the releasing, on the business side of things, which is what we really want them to do. So all of this has come with challenges, but also with a great level of energy and an adoption that is strong, so it's good. And it's also worthwhile to mention that it was important, and it's still important for us to have a strong partner helping us, because on the technical side and on the implementation of DevOps, we have had many, many questions. So having Rhettat with us and other companies playing in this game is very important. Yeah, I think that's correct, right. Having a partnership and real collaboration between partners, it's not just a supplier relationship, it's good, yeah. Now, it's not just the financial sector where cultural shifts are happening, right, and increasingly necessary and pretty common, right. It potentially is in any industry, as you can tell, right. And as we just said, collaboration is one of the most important elements in the open source way. Now, it's very exciting to see large, previously a bit more isolated organization like the government of British Columbia taking advantage of DevOps collaboration in an open way. Now, let me go back to you, Dietman, right, that what has the Amadeus experience been with embracing the open source software, but then also the open source technology in the open source way? Be careful, I can talk for hours on this. So we have a long history in open source usage. So I mean, we use Linux, like I guess most of us here, for ages, so we are not completely new to this, but a few years back, I would say our relation to open source changed, where we got more active and we looked more actively into projects. And when we took the decision to go with OpenShift, we took it also, obviously, because it's an open source layer and underlying Kubernetes software is fully open. And we did actively with your teams to participate to the evolution of Kubernetes. So we could contribute to this environment, which creates on our side a very deep sense of ownership and knowledge of the platform, which is very important for critical systems when you have to understand what you're doing, if you have to react very fast to problems. And I think it's also a matter of really embracing the open source spirit. I mean, we profit a lot from the community. We get collective knowledge into our products. We have a lot of knowledge and I think we owe to some degree to the community to hand back and to shift contributions that we believe are of common interest to everyone. That's what a community really is. I mean, if in a community everyone is only consuming, you can't construct society or any positive thing around the community. So we try to take this seriously and that's what we think we have to do, really. That's admirable, really embracing the open source spirit and contributing back, engaging open source is great. Now, collaboration can come from many sources, right? And Ashash, I know you worked with the government of the British Columbia quite closely to build the developers exchange. You worked on their journey, right? I helped them on the journey to become more collaborative and partner and how they partner with the private sector to improve the services to their clients, right? Can you tell us a bit more about this story and why they were selected for the open source way? Sure, so I'm really glad to see British Columbia being recognized for the work they've been doing here for at least a couple of reasons, right? One is they've been extremely thoughtful about what they wanna do. It's about trying to empower developers, essentially individual citizens to be able to use technology for the common good. I mean, that's really great. And we've had them be an active participant in the OpenShift Commons, in which again, you know, speaks to the power of community and collaboration. And that's been really great to see. And also it's appropriate for them, given the theme of this year's conference, right? Which is celebrating the impact of the individual. I think the work that British Columbia is doing really is about trying to have each individual make a greater impact. So the open source way is really a buck using open source to create that culture, to support the collaboration, right? So we talk a lot about businesses having flexibility and agility to compete and to be able to rapidly develop IT initiatives and embrace DevOps. But I think the British Columbia developers exchange is up to a really good start. You know, we already heard about, you know, some of the things that are happening from the videos that we've seen earlier this week. What OpenShift really is doing and the technology platform that we provide is supporting that collaborative approach, right? Helping to reduce time between proposing new applications to actually developing, deploying them. That's extremely powerful, right? To amplify the impact of the individual. These projects highlight the power of the openness and collaboration that we've talked about. And you know, there's some really great examples, right? You know, one example that I personally liked a lot was the Ministry of Transportation Infrastructure developing the school bus inspection tracking service. I think we saw a quick picture of that earlier this week. The system was built and launched in just eight weeks. Absolutely remarkable, right? Because previously it might have taken a year. Again, you know, unlocking the power of the individuals who collaborated on that. Another project that showed the work that they did also with the private sector, right? So really expanding on the ecosystem was the highway camera project. Peter Watkins actually talked about this, right? He's the executive director over at BC DevExchange during the keynote yesterday. And he really talked about, you know, the opportunities that they had to be able to create an open 511 API for road events, right? Allowing departments to work with a local software firm, right? To expand, you know, others who can collaborate on this. To build an app that offers more information and really be able to have technology companies provide improved services for citizens. That truly is a great example of the open-source way and collaborating. Thank you, Ashash. I think having a government publishing open APIs is just so remarkable. It's awesome, yeah. Now, broad availability of open-source projects, you know, in the community, right? Means opportunity for governments to connect with innovation, with open innovation, and provide better services for citizens. Another similar government open-source story is here in the application optimization category with our, we recognize the government of the state of Jalisco in Mexico for using an agile approach to achieve superior performance in creating, maintaining, and deploying business applications. So you see we have Canada, we have Mexico. Now, let me ask Chris Wright. There's no wall in between. Chris Wright, let me ask Chris, why are the governments like Jalisco so keen to adopt an open-source first strategy for projects like application optimization? Well, there's a lot of benefits that we've already talked about here about collaboration, powering the individual, but I think there's a really important aspect that's just about the operational efficiency of running, whether it's a business or in this case, a government. So you bring this open-source innovation and technology, it's really enabling the government to be more efficient, to lower costs, and embrace agility. So just the same situation you'd see in an enterprise, and specifically at Jalisco, they've brought together some Red Hat technologies including Jboss, EAP, Infuse, and REL, and Rev to really cut their operational costs significantly. So for them, we've seen a 60% reduction in cost, and also at the same time, in operational costs, at the same time, really significantly cutting the hardware costs. So great cost efficiency, along with that, they're able to serve 1,000% more citizens. So going from 3,000 citizens per day to 30,000 citizens per day in terms of transactions between citizens and the government. And maybe not the most exciting kind of way to measure efficiency, but quick turnaround in things like traffic citations and tax collection. So that's really helping the government be more efficient. And what that means for the citizens is, that's money that's being well spent on the services that they're looking to provide as a government. Also, you see real performance enhancements, improvements for both the state side and citizens in terms of how they can interact with the government. Yeah, so the kind of funny innovation that I got to pay my fine quicker. That's right. Let's leave that aside now for now. But let me ask Chris Rommels here, right? How did transparency, collaboration, and citizen participation align with HALISCO's open source development model? And how can others learn from that? Sure, so I think one of the places to start is just that the state of HALISCO's position as a public entity, I mean, that just for one, puts a lot of pressure on them to ensure that when they change, they do so right and everything's done really well. Ultimately, the citizens are consumers, right? I mean, it's gonna be their customer they have to deal with and keep happy and keep their government working well. And as such, working with citizens that are ultimately consumers, their demands and expectations are also gonna evolve very rapidly. And so the state of HALISCO had to look for a way to set themselves up to both develop now and also set them up for the future to be able to develop just as fast and keep pace. And I think if you then also take a step back and just think to your point, when you're paying bills, there's a level of trust that requires, a level of transparency that people want, especially if you're gonna ask them to deviate from how they've interacted in the past. Certainly if you're sending off a check or working with a new platform, you wanna ensure that everything's gonna work out as you expect. And I think if you just take a step back and then think about what other people can learn from this example, I think the first and foremost is the fact that they recognize a pretty big need to change and just transform as an organization. And they also recognize that given their demands both to change now and also in the future, they thought it was important to use open solutions to ultimately take advantage of the innovation in the industry today, and also provide them flexibility for the future and avoid any lock and everything like that. And I think another thing that was very important that they did is they recognized up front that they wanted to make sure they did get it right and they picked the right mix of products. And also that when they made that change, their developers would be prepared to hit the ground running and be successful again, now and in the future. And to do that, I think one thing that paid benefits to them is they worked up front with the Red Hat Consulting and Training Team to do so. So ultimately, I think what caught my eye about this winner more than anything is the fact that there was a significant change undertaken, I mean just the sheer magnitude of the change, but more importantly, when you look at the results at the end, some of the statistics that Chris shared were really impressive. And I think ultimately you saw where they made a big change and they got really big results at the end. Yeah, it's great to see those stats, yeah. Thank you, Chris, yeah. Let's go back to Chris Wright, right? And what aspects of this strategy did you admire or stood out as the most impressive in terms of industry best practices? Well, I think a key tenant here is collaboration and the notion of transparency, collaboration and then citizenship engagement, which I think are really the tenants of what we're talking about here in terms of open source and bringing together ideas. One of the things that the Jalisco government is doing is really building a platform so that they can move ahead and not be left behind with technology changes and this kind of forward looking activity has earned them the title of Silicon Valley of Mexico, which I think is a really great way to look at it. They were trying to build themselves a core engine for innovation and that the traditional way of engaging with a supplier and getting proprietary solutions just isn't the answer today for how do you build yourself your innovation engine? And ultimately, there's further plans to build data centers, private cloud and really, they're giving themselves the platform to expand into the future. Yeah, thank you, Chris, yeah. Let's transition a little bit here and like you said, businesses really need the right tools to deploy managed IT elements, like private cloud including having the right software and the right management tools to do this, right? And technology like OpenStack can be a bit complex. I think we all agree on that, right? Ashash, what are the top reasons organizations are adopting private cloud solutions with OpenStack despite its complexity and how does Rackspace meet their needs? Right, well, it's a timely question, Marco, especially given OpenStack Summit is next week in Boston, sure many of you are planning to attend. I think the past challenges of deploying OpenStack has been about matching customer expectations with the maturity and where the technology has been. I think as technology has matured, customers are thinking less and less about just public cloud in a box, right? I think maybe that's where they first started, but increasingly more as a scale out elastic data center infrastructure that can reduce cost increase flexibility. So I think that's been really positive with regard to the adoption pattern that are happening around OpenStack. We're starting to see them. Rackspace, of course, has been an early leader in the OpenStack community, just like Red Hat, right? Have been contributing significantly. Organizations still need specialized IT resources to deploy and manage OpenStack. And for the organizations that don't necessarily have it or need assistance, Rackspace can certainly help and manage this for them. So they've created a nice business model around OpenStack to help several customers use it and get a lot of value from it. I think maybe one final point I want to make is that Rackspace has partnered pretty extensively with Red Hat and the OpenStack community. So again, in the spirit of collaboration that we've been talking about all morning, but that's really great to see. So collaborating now with Red Hat and end user adoption is extremely natural. Thank you, Ashash, for the context. Let's go, you know, Chris, if I may ask you, right? Is Red Hat has a strong partnership with Rackspace and it's just, as Ashash said, for a long time. And as Brian Thompson talked about in Tuesday's general session, right, we've worked together closely over the years to improve open source technology and provide those tools for the enterprise IT. What can you tell us about the latest Red Hat and Rackspace collaboration that is the foundation for Rackspace's private cloud solution? Well, Rackspace worked together with Red Hat to develop the Rackspace private cloud powered by Red Hat. And it's a Red Hat OpenStack platform-based solution combining other technologies like CEPH and certainly REL and Satellite, combining those technologies with Rackspace's amazing expertise in managing a cloud, complex cloud environment. And so this is a great combination of operational skills and technology really supporting the end customer's journey to the cloud. And not all customers have the internal operational skills to bring the cloud onto their premise. So working through a partnership with a supplier like Rackspace helps that customer build their journey to a platform for their innovation. So giving them the place to build their business differentiation. I think some interesting things that have come out of this collaboration and the solution that Rackspace has is enabling quick workflows. So things that may have taken an introduction of a new software version that may have taken upwards of 40, 45 days, bringing that down to something like three days. So dramatic improvement in how quickly you can update software. And also how do you create a production environment from scratch to fully functional? Certainly without agile infrastructure that could take months. Here we're talking about something including all of the different aspects like load balancing, network, multiple nodes, coming up in something on the order of seven, seven and a half minutes. So really rapid production environments that give you the ability to move quickly as you're building out your solutions. And I think the way to look at it is simplifying the private cloud and enabling all of that open source innovation without sort of sacrificing any of the stability, security, really key mission critical underlying infrastructure that you need for to run your enterprise. Yeah, it's great. Thank you, Chris. I love these stats and you can see this is why these innovation awards are real, right? It's not just a marketing effort. It's really like we look at these details and we analyze them, right? And so this collaboration is a good example to other customers aiming to adopt a private cloud solution looking for more integration with Red Hat. Chris, is it? Well, it's a real partnership between Rackspace and Red Hat. And I think the future of IT is so much about collaboration between vendors and customers, vendors and vendors together with customers. So this is really how we're building our next generation infrastructure. I love a quote from Dan Shepard saying, 50% of the Rackspace engineering team is Red Hat. So that is really just underscoring exactly the kind of collaboration that we're building together. Oh, sorry. And so together, actually Red Hat and Rackspace have built, contributed something about 27, 29% of the codebase upstream in the OpenStack community. And with that, bringing together our solution to the customers, you're seeing things like 99.99% API SLAs guaranteed from Rackspace. So this is the kind of enterprise infrastructure that comes out of this tight collaboration. Thank you, Chris. Now, let's transition again to the next area, right? And this week, we heard it a lot. Integration is obviously a big topic in IT. And it can be the integration of private cloud and public cloud resources and this whole open hybrid cloud. But also the traditional challenge of balancing investments in the old IT versus in innovation, right? I mean, how do you balance that, right? And so this is the enterprise transformation category, which focus on an organization that achieved and really showcase using the edge island open practices and technology to achieve that transformation. We've seen it over the years. And this year, the win of the last category is McCurry Banking Financial Services Group in Australia. You saw it, I think on Tuesday or yesterday, right? They built a much smarter digital banking experience in their personal online banking platform. You saw the apps yesterday in the movie, right? For their Australian retail consumers, right? They're continually evolving and improving their customer experience. So it's a good example. You know, Chris, let me ask Chris Rommels one more time. Can you share your thoughts on this story from Australia? Yeah, absolutely. So I think, again, one of the things that stood out to me was just the magnitude of the change that was undertaken and just the effort that they recognized they needed to start. They were in a situation where the bank hadn't invested for quite a while. So they were stuck with a slew of monolithic applications that they recognized they needed to update and start a process to do so. And also when they recognized that need to change, they also wanted to make sure that when they did change, they got started in a way that would ultimately support a more agile and DevOps culture. And from there, I think one of the important things they did is that when they were looking at different solutions, they found a partner in Red Hat that had both pass as well as container solutions. But again, just as in the state of Hylisco example, what one thing they did is that they recognized that open technology, again, would provide them not only the source of innovation they needed to move forward, but also would provide them flexibility in the future. And with that, they ultimately selected Red Hat OpenShift Container Platform, and that was as a public cloud implementation and data center run by AWS. And I think one of the things that's really important here is that they wanted to pick a solution but also just a partner. Again, just like we were talking about just a moment ago, they wanted to set up a model for transformation. So this was a case study in one part of the organization, but they wanted to be able to scale their success throughout the entire organization. And ultimately, they were able to do so when they selected Red Hat after, again, looking through what else was available to them. So just again, take a step back here and continue on the theme of statistics tell truths here. And one thing that really jumped out is that their developer productivity improved by over 50%. So once again, huge operational cost savings, but also just in terms of getting things done, their release time went from hours to just minutes. And so once again, this is about an organization recognizing a need to change. And in this case, a need to make some fast project progress to catch up. And once they made those big changes, the big investments, they were able to not only save on their operational side for them, but transform ultimately the end customer experience, which is really what drives long-term success. Thank you, thank you. Now, let me thank you for everybody for sharing the insights. We've learned the benefits of being a risk-taker within reason. That's why innovation award winners are here. And adopting new open-source technologies like OpenShift and other Red Hat solutions is a way to embrace innovation in a more agile, collaborative DevOps approach. And we've obviously with the help that Red Hat can provide with expert support and guidance. Now, this is asked for you, right? Hopefully, you get inspired. We always, when we get these studies, we get inspired and think it's like, wow, this is really cool what they did there and there, the public APIs and the government. This is really good to seeing. Get inspired, hopefully, and be the disruptor, right? And you can cost change, right? And if financial and government institution can do it, you can do it as well, right? And you can turn competition into collaboration, work together, right? Be the individual who starts the ripple of change and the innovation in your org. Now, the Red Hat Innovation Award celebrates and recognizes the organization that use open-source to solve business challenges. Out of these five winners, one is being voted from you, as the audience, here and online, to the innovator of the year. Now, let's go over here. There's only one envelope. There's only one envelope, right? So, 2017 Innovator of the Year is... Is this the real one? Rackspace. Congratulations, Brian. They're making pictures somewhere. Take this away. So, Be Bold. We want to see you up here next year or we want to see your story. Keep out for the nomination. This is opening next year. Talk to a Red Hat person if you want to be part of this. Submit your stories. We really want to see you. So, thank you for attending the morning keynote. We'll see you back in the afternoon and be the force with you.