 I'm going to bring a colleague and a researcher that I've been working with from Bitersia up on stage. Here he comes, Daniel. And we're going to talk a little bit first today about some research we've been doing about how you guys are all connected to each other. So, Daniel, welcome. Thank you. All right. Hello, everyone. How are you? So, we always talk about collaboration and action. This is a slide that I usually do. And this time, we are here in Spain, and Daniel, who is co-authoring some papers, and hopefully a book with me on this topic soon, is based in Madrid. So I figured we'd do something a little different this time and bring him up, and we talk a little bit about this. Because at Red Hat, we always talk about how open source is the source of everything, and we work on, as a company, millions of projects. This is a little out of date because it's 2018, but Great Hub has 96 million plus repositories, and there's millions and millions and billions and billions of developers working there. But it's really about the connections that we make and the diversity of the communities that we work in that helps to create this wonderful, innovative world that is Kubernetes and the CNCF and OCI and all of the other Apache and Eclipse projects. So we wanted to take a look at how all of that was connected to each other. Because as we know, OKD, and if you didn't get the socks yet, and if you have no idea what that is on the socks, that is the OKD Panda. And we renamed, if you didn't realize this, OpenShift used to be called OpenShift Origin. We renamed it to OKD, and the joke really is that it's OK, Diane. That's what you've got. This is all you've got. So they gave up trying to find a name, and they just surrendered to OKD. But it is really a function of Kubernetes plus all of the other projects that we work amongst. We talk about collaborating with the upstream, all the upstream projects that we pull into OpenShift to make it into the container platform, into dedicated, into online, and now into Azure, and to lots of other people who are hosting OpenShift as well, are pulling in different integrations. And we collaborate across lots of different streams with our folks who are deploying it. They add value on top of it. There's a number of the other co-located events today that are partners of ours from TwistLock to Aqua Security. Lots of people are adding on top of OpenShift. And then we deliver it as a product with lots of other stuff, and we get it certified. So we do all of this goodness and stuff. And that has, as a good community manager would want, driven lots of contribution actually into OKD, though there's, I think now there are about 80 plus organizations that have made some contribution, the font gets really smaller. And this is, you're seeing probably for the first time, the Batergia dashboard that we use to track all of the things that go on inside and behind the scenes. So this is great, but really the future isn't about contributing to OKD. Most of the contributions that OpenShifters and Red Hatters do now are directly into Kubernetes or Prometheus or into the other projects. There's tons of Red Hatters, and this changes all the time, so I have given up trying to keep it up to date. There's lots of Kubernetes contributions being done out there. And it's, there's lots of projects, and this probably has, I think since last week, has a few more things that have been added into it. And up in the top corner, you're going to hear today about the operator framework, which is now adoring, and this is 29 items. I think it's up to 37 operators, or 39 I didn't look this morning. But people are building operators, which again, extends what Kubernetes can do and the automation and the management of services on Kubernetes. So the complexity of understanding how all of these projects are interrelated becomes kind of crazy. And if you are someone who is doing community development and your company tasks you with networking and creating a peer-to-peer network with everyone, it's quite difficult to know who everybody is. So we have done something I think a little unique for in community development is we started to apply some of that wonderful data science tooling that you all get to use for sales and marketing and everything else to community development. So we've taken a bit of a data-driven approach to working on all the data that we've collected, and I'll let you talk a little bit about where all that data is coming from, Daniel. So why don't you? Yeah, thank you. So well, the tooling is, of course, 100% open source. It's part of the chaos project. Well, you can go and look for this. So this is in Grumar Lab. You have the URL there. This is kind of the architecture. So you have the usual retrieval part at the very beginning on the left of the slide where you have the usual data sources. So you can go for GitLab or GitHub or Atlassian Stack. You retrieve everything. You store everything. And then there is some magic around identities, which is kind of a headache, as you can see. So you have to improve and polish the data and affiliations and all of this information. And then it happens, and then you have a curated database for, let's say, the CNCF ecosystem, the OpenCIF ecosystem. And you can aggregate all of this data and look where developers are working in which companies where they are coming from, areas of the code. And then you can have a really full understanding of what the community is doing, right? So, well, this is Victorian analytics, let's say, at the very end, what you saw before, which is this chart, is one of the things you can produce. So yes, a really quick introduction. So each of the dots are developers. And then you see at the very center kind of small blue rectangles. So those are the projects. So we have Kubernetes. We have Fluent. We have Envoy, OpenTracing, and some others. There is a relationship between the dot and the blue rectangle, if that developer has been working at that project. Then you can see that there are some other cases where, yeah, this pointer, where basically we have developers working in both communities. So we have relationships between developers working on Kubernetes and developers working in OpenCIF. So all of these people are working in both communities. And of course, we have other developers working in more than one community. So all of this mess between here in the middle, this is developers working in several of them. So who are they? What are they producing? So who's who in the community, right? What can we understand from all of this? So this is the consistent that we all have here. So we call this the amorphous jellyfish. So we're going to drill down a little bit on this. Because I think this is interesting just as you start to see. And we didn't pick any individuals to dive into. But go ahead, and we'll just talk a little bit more about this. Yeah, we took one example here, the Jaeger example. So how many of you know what Jaeger is? All right, and you're using it. So this was a project that was donated to CNCF by Uber and had a number of Red Hatters who are working on it. And so that's sort of what you're seeing is the interrelationship between people who are working on Jaeger and people who are working in Kubernetes. So that little network in the middle are the none. Those are you. Those are people in this room or in other rooms who are here at the conference. And you can actually click on them and get their name and understand who they are and see what other projects they're working on. And then we have this concept. We've been discussing about connectors, right? And mavens. And so who are those important people? Yeah, so if anybody read Malcolm Gladwell's The Tipping Point, sometimes people love it. Sometimes people hate that book. But he has concepts of personas that we all know of mavens and connectors and that. So these people are, some of them are the project leads. Some of them are surprising. They're not people you would expect. And it's quite an interesting dynamic to do. And having this tool as someone who does community development is so wonderful, because if I need to find someone who is working on the Yeager project, who knows Kubernetes and who maybe knows Kafka, I can look and see and tease out where that person is. So indeed, if we look, let's say, a bit more in detail, so who are those three people working in Jaguar and in Opensiv? So we have those names. So these are, let's say, the connectors, the important people that are kind of helping to drive the community, to build community. And so if you look, Jesse is a red-hatter. Greg Swift was at Rackspace. He actually got the OpenShift Community Award at the last, or two gatherings ago. We gave him that. He's now at LogDNA. And Julius, I forget where he's from, but they're the people who have the larger, the circle, the bigger number of contributions that they've made in the diagram. So it's just. Yeah. So. So we wanted to start teasing out some of this and looking at it, not just at an individual level, but sort of at a company level. Like, so where else is Uber? We just are using them as an example on this one. Where else are they showing up in this ecosystem? So they show up, obviously. Yuri here shows up in Jager Open Tracing. Surprisingly, Uber's doing a lot of work in operators and M3DB is their mega database that they've been working on. Then they've also done, I think, a little bit of work a long time ago in OpenStack. But that didn't show up in the history yet. So yeah, this is. So we have a live demo that they can show you, this data, basically. So this is Uber, Rackspace, in this case, because we were discussing about Greg and Red Hat. So of course, the big stars we have are Red Haters. But then it happens that we have some other people and some other companies. So for instance, well, this OK. Yeah, come on. So we have Red Hat, Uber, and Rackspace. These are, let's say, the legend of colors we have. If we go for this, it happens that, of course, we have Uber and Rackspace, as we mentioned, before working in some other projects. So we have Uber people interrelated with Red Hat, interrelated with Rackspace developers. So let's say we don't know people participating in Jagger, probably we can reach them through several people within either Red Hat or Uber or some other companies. And indeed, we can do things like, well, let's filter this. And then let's try to understand fully where Uber is working. So we can filter here. We can save the information. And then we have developers, Uber developers working open tracing Jagger here. And then the bigger the dot, as you said, is the more contributions by this developer were produced for that repository. And this data set, we haven't put in the data for all of the CNCF projects yet, but that's something we're working on as well as a number of other projects. And we will be adding in all the operator repos as well. So it's just going to get more complicated and more interesting. But also being a Canadian, I have to say this, one hockey metaphor is it also allows us to see where the hockey puck is going. So there's some famous Canadian person hockey player who once said you should never watch the hockey where it is. You have to look ahead to see where it's going. And so this has allowed me to see like migration from open stack, people from open stack who are moving over and starting to work on Kubernetes. So you can start to see historically that the movement of actual contributors and people working on projects through this community. And you start to really get a sense of how much cross community collaboration is really happening here. And it's pretty important to the health and well-being of the whole ecosystem. Yeah. So M3DB, we just recently did a Santa Clara OpenShift Commons gathering. And two folks were also at the KubeCon event in Seattle on stage talking about their wonderful operator that they've done to make this run on Kubernetes really nicely. And then we're working with them slowly to get that into the operator hub so that it runs anywhere. So this has been quite an interesting phenomenon to watch how this is all very fluid. And then the other thing that we've been doing is working pretty closely with a lot of our people who are using OpenShift. Is there anyone from Amadeus in the room today? So I'm not outing anybody here. OK, good. So we picked on them because they've been long time and very vocal OpenShift supporters and contributors to the origin and then into OKD. And done a lot of work in lots of different spaces from RDO and OpenStack to Kubernetes to OKD and to OCP on Azure, as well as recently we had them at another event. And they were working on Kafka. And they came in and get a wonderful presentation, which is on our YouTube channel, on what they're doing with Kafka now and doing contributions to that. So you start and keep repeating myself, but you start to see the real interconnectedness of all of these projects. Then we have the question, how does this community look like with Amadeus? So for this, of course, we produce another specific chart where, again, we have most of the people coming from Red Hat. If we compare Red Hat and Amadeus, it makes sense. Then we have these two BX stars here. This should be OpenShift. So this is Kubernetes. Then we have some developers working in the two communities. Then we have some Amadeus people, which are these purple developers around. So this is an interesting way of looking at all of these data. And this one, we were discussing right before this. Hey, can we have this Uber, Amadeus, and Red Hat? So the three of them together. So we understand the ecosystem of the three companies. So this is the ecosystem of the three companies where we have, again, the big player, which is Red Hat in this case, with OpenShift and Kubernetes on the top. Then we have, so the legend is Uber is the green ones, Amadeus is the purple. So we have some Amadeus developers, and then we have some Uber developers around OpenTracing and Jaguar. And if we go to the next. Did you do the IBM? Then there's another little interesting thing that's happening here, which I think maybe is a good one to talk about last here, because it's coming up soon, is the intersection of where all the IBMers are working and where all the Red Haters are working as we walk through this next variation of what IBM and Red Hat are going to be doing together. So you'll start to see, and it makes it easy for me and for everyone else to see, where we're going to all be working together as we merge our two companies. In this case, so we have Red Hat mainly driving OpenShift, and then we have IBM and Red Hat working together in Kubernetes and OpenTracing and Jaguar and some other companies. So cool. All right. Let's go back to the slides. I think that might be my. So we had. I think that was it. You mean the. There's one more slide. Did we have? I don't know. Hit that slide. OK. So you want to go? Go to the next slide. Oh, that slides, right? Yeah. OK, let me go down here. Yeah, so yeah. All right. So really, I know that's all interesting to me, and I hope that was interesting to you, just to really maybe get some visualization on how you are all connected to each other in some way. And as we improve the data set and bring in the additional repos and mailing lists and information that Bittersia allows us to do, we'll be sharing that information as well publicly at lots of other venues too. So that's really the key here is there's a couple of takeaways I think. At the beginning, I mentioned that OpenShift Commons is an organizational-based community. And that we ask you all to use your GitHub or your corporate names. One thing that was interesting to tease out of all of this data is that there really is no anonymity out there. So if you think you're being anonymous using your Gmail address with GitHub, it's not there. I mean, it's so easy to figure out who people are and their affiliations these days. But it's also interesting because there still are a number of independent developers working on these projects too. So that's been quite fun to find them and to realize that there's a lot of traditional open source contributions still going on, not just through corporate-funded development. So there's lots of great information here. We'll share it out in lots of other papers hopefully in the future with Daniel. And if you're interested in joining the Commons and finding your peers, the room is here for you today. We really ask that you network amongst each other, meet some new people here. There are just a little over 200, I think, people today I haven't gotten the count in this room. And then a little over 100 in the other room that are working on those operators. So we'll all be in here today for the whole day. Yes, the whole day. And lunch and everything else will be served in here. So this day is about you and getting you up to speed on what's coming in OpenShift and Kubernetes and this whole wonderful ecosystem that we're all working with. So thank you, Daniel, for helping me with all this research. And we look forward to publishing some papers that you can give us feedback on soon. So thank you. Enjoy your day. All right.