 Well, good morning, and I'm pretty stoked to be in San Diego. Unfortunately, it's only for a few hours, but that's life. I like to talk today about open source. Jim did a great job this morning of describing how open source is just fundamentally changing the industry. I call it the innovation engine for the industry. And it's not just creating technology, but it's helping entire industries just transform and completely change how they operate, how they do business. And that's really amazing. Open source to me starts with a shared vision. You can't really collaborate on something if you don't know what you're working on together. Shared vision, I think, is key. Obviously, collaboration is a big part of what we do, so that's working together to achieve the shared vision. To me, a critical component in this is trust. As community members, we're people, we're humans. We're developing human trust relationships with each other. Trust comes with openness and transparency. I think it's a really fundamental part of what we do when we build a community. My favorite part of an open source community is the ability to just get stuff done, and I call it initiative. And what that means to me is showing up and doing something is valued. It doesn't matter where you come from. It doesn't matter your background, the contribution of code, documentation, bug reports, creating community meetups. All of these things are important parts of the community. And all that is required to do that is initiative and showing up. Another important part of a community to me is diversity. I think diversity has a couple of dimensions. One is the people, so make sure we have the broadest different kinds of ideas and mindsets represented. The other, from a more technical point of view, is the types of problems that we solve. So a great project, I think, that sustains itself over time, is capable of supporting a diverse set of workloads or different problems. I think another key hallmark for open source is the notion of incremental improvement. Whether it's fail fast and realize that that's not working or whether it's released early or released often, you hear more and more about it today in differing worlds. Whether it's DevOps and agile development or whether it's ways that whole organizations are thinking of operating themselves, not just building code. So I think that's a really important piece. It gets more to organic growth and evolution, some of what you saw earlier with the poet example. And I think this is a really key feature of open source development communities. So ultimately together, I think we're building a diverse community to write and maintain software to solve problems that users care about. Sounds pretty simple and well, we've done an amazing job of that. And so what you heard this morning was a bunch of examples of how the industry are changing, the industry is changing fundamentally. You look at a place like GitHub, which has something, they label themselves as having over 100 million Git repositories, over 40 million developers, and two plus million organizations. Those are staggering numbers. You look at some key large projects and the number of changes per day and the velocity of activity that happens within those projects. This is all staggering. And typically Jim talks about the billions of dollars of transactions that are supported through all of this open source development. So you get the sense of the real commercial impact. You didn't get a chance to hear that today, but one of the things that I think is important is realizing that part of winning is with great power comes great responsibility. We've done a lot and I think we have to make sure that we continue to evolve throughout all of this change and maintain some key features like that transparency and trust and incremental improvements on organic growth as these key tenants of how we operate together. So along the way, what's changed, I would say fundamentally, and I say this with intention to create a visceral response. It's the corporatization of open source. Now is that a positive or a negative? I don't know, maybe it's up for you to decide. The positive is all of that amazing industry impact that we're seeing. The negative I think is how do we onboard a whole new set of constituents, both contributors and users, into a world that we have really evolved over the past decades. Personally, I've been involved for about 20, 25 years. So this is a long time in coming. So we have a whole different set of dynamics. These are industry wide dynamics. There's a lot of money at stake which changes people's behaviors. And I think we should be able, one, to acknowledge that and two, really be mindful about how we carry forward to ensure that the core qualities of open source sort of withstand the test of success. I think success also, you see that kind of great responsibility. Understanding from a user point of view what a project delivers is important. And we just learned about another type of vulnerability with the issue with RubyGems. This kind of high profile security concerns is something that will continue to matter hugely to the industry. For impacting and changing the entire industries, we need to make sure we do that in a responsible way and help people who are trying to use our software to consume that safely. Another piece that I like to point out is there's a fundamental distinction between a project, an open source project, community based development effort, and a product, a commercial effort. Maybe fundamentally, one is about community creation. It's about the technology. It's about really evolving, bringing features on into a software platform and evolving that platform architecturally, soundly so that you can sustain it over time. Not necessarily creating a commercial relationship with the user. Certainly having relationships with users is important. On the product side, there's all these things about life cycle management and stability that's independent from the upstream life cycle. There might be integration around other products. And ultimately, clarity of when we're talking about a project and when we're talking about a product, I think will be really helpful for people who are trying to consume what we're building and understanding where it's in the bleeding edge and not yet mature and understanding where it's actually a commercially supported variant of an open source project. Another area that's related to this is certifications. And there's a bunch of different meanings for certifications. I think this is an example of blurring the lines between the commercial side of software activity and the community side of software activity. Protecting the trademark around a software project is really important because we have brand association with the quality of a project. Understanding when you're doing certification to conform with the trademark versus certification to say, this is a commercial activity. And I know in my role I get requests from customers to give me one of those and they're pointing out a certification stamp, which may or may not be relevant in the context of a commercial product. So I think that's a blurring of the lines between the community and the community development efforts and the commercial side of creating and selling supporting software. So to me, I think the challenge ahead is really keeping those core values, those core tenets of what open source is, thinking about how we create projects, sustain projects. When we work within foundations, understanding the difference between the marketing hype of hyping a project and the reality of what a project is capable of so that we're level setting with the industry, what's real and what's, I think we'd be doing ourselves a disservice to overly hype software projects before they're really ready and mature. And to me, this is the fundamental kind of interesting challenge that we have. I would call it open source 2.0 or next generation open source if I was in marketing and trying to give it a buzzword and a slogan. I suck at that, so I'll just say I think we're entering a new era of open source. It's not today, it's not as if it wasn't there yesterday, but we're moving into this new era of open source. And I actually have some concerns that if we don't pay attention to these things and work together as a broad community that we could lose sight of what's made us successful and transition into a new space where we lose those same core capabilities and maybe lose some of that amazing success. So I'd love to continue the conversation. Certainly there's Twitter and there's hallway tracks and if we get enough people who are interested in this type of discussion, we could carry it on and make it a more formalized discussion. And that's really what I wanted to share with you today. Thank you very much.