 So, Mr. Chris Devon, I thank you so much for taking the time for this interview. Sure. I'd like to know first about what you're doing in Google, and then we're going to ask you some questions about what you covered in the presentation today. Sure. Well, I run Google's open source programs, as well as a couple of other jobs that I have at the company, which means I'm tasked with everything from ensuring license compliance with open source software licenses, as well as making it easy for Googlers to interact with the outside world at a technical level with these open source projects. So, we do that a lot of ways through releasing code, through helping out different projects that matter to us, and that kind of thing. All right. So, first off, I'd like to know about the open source study that you came up with, and you covered it in your speech today. Sure. And the major findings that you came up with, and why do you think they're relevant? OK. Well, first of all, it's funny. That study was done almost 10 years ago by MIT Sloan School of Management, and the Boston Consulting Group. OK. Crème Lacané, who's now at Harvard Business School, did it. We helped him with that, helping interact with the people who are on the source forge at the time, because I worked for the company that ran source forge back then. Anyway, so we really wanted to get an idea of why people did open source software development. So we just asked them, like, what motivates you? And we gave them a lot of choices. And what overwhelmingly came to the top was that people wanted to become better computer scientists. They wanted to become better at their jobs. They wanted to build skills. And many of them also identified, a third of them actually, identified with the ideas that we were all in this together, and that we should all be helping each other out by releasing code so that we can make all of our lives better. So it was pretty awesome to learn that. 44% was curiosity, more than skills improvement. What do you say about that? Well, I mean, I think people get into computer science and get into computers in IT because computers are interesting, because you can make them do things. And you can see if you can make it repeatable and sometimes profitable. It's pretty neat. OK, a major part of your presentation was pictures about Google 11 years ago. Sure. Why did you choose to? Well, it was 11 and 10 and 9 and 8 years ago. So I showed those to show people that we've been using Linux from the start, that Linux was a conscious choice, and also unconscious at the same time, and that it was natural for us to use Linux in open source. And why would we want to stand in the way of that as a group? So how does Google use open source? Well, we use it any time you go to Google, you're using a Linux machine. That's where all the software runs on top of is on top of the Linux kernel. The software that we build is built using open source tools like GCC and Python. And then we combine open source software libraries, OpenSL, Zlib, you name it. And we mix them together with our code to create Google. So open source is part of the entire process of software development at Google. OK, so the final question we'd like to know more about the summer of code. What is it, and what about the student participation in it, and what are the major interesting maybe outcomes that came up? So the summer of code is probably something I'm most proud of that my group works on. We started this six years ago, and we wanted to come up with a way of giving back to the open source world that has given us so much software to use. And one thing that I personally had noticed over the years is that I hadn't been seeing a lot of new open source developers showing up at the same conferences that I would go to or in the same forums that I would go to. And so I thought, well, why is that? Why aren't there more students taking part in open source? Or am I just being myopic? And so we looked into it and we decided we would try to incentivize students to do this over the summer as opposed to getting another job. And so we teamed up with a variety of open source projects, Nome Foundation, Apache Software Foundation, Python Software Foundation, and people like that. And we said, what if we gave you students? What would you do with them? And they're like, oh, well, that would be great. We could have them do some stuff. And from that came the summer of code. And the way the summer of code works is actually pretty simple. A student will apply to a project, not to Google, but to a project, saying, I want to do this thing. And here's why I'm the person to do it in this time period. And if they're accepted, and only about one in six applications are accepted, it's about 1,000 students each year. If they're accepted, though, they get paid $500. And then when they make it to the midterm, which is about a month and a half later, if their mentor thinks they're doing a good job, they get paid another $2,250. And then at the final, again, if the mentor thinks they've done a good job, they get an additional $2,250. And so multiply that by 1,000 students. There you go. And they create, on average, about 3,000 lines of code each for an open source project. And it's pretty exciting. So do you think money was the incentive for students to participate or their willingness to probably prove their skills? What do you think? Why was the amount of participation that impressive? Well, you know, we joke that they do it for the t-shirt. But I think the money helps them have the freedom to take on this kind of unusual sort of internship, right? So we sort of see the money as just helping students out and helping them sort of get over that sort of hump. And then I think the real service that we bring them is introducing them to the people in the open source world and giving them a structure in which they can thrive. So it's pretty exciting. So you gave us some stats about the level of participation in different countries. Can you briefly mention them? Sure, yeah. So there's a couple things. We have an 81% pass-fail rate. So that means we're failing 19% of the students. And what failing means in the program is you don't get paid. So you can fail at the midterm. You can fail at the end. This is about half and half. And so yeah. And then this year, we had 105 countries represented in the application pool in about, I think, it was 98 actual countries that took part. And then, yeah, so over the six years, we've, I guess, handled about 1,800 students and maybe a little less than that because we started smaller. And then we've probably released about 18 million lines of code. OK. That's pretty good. That's quite impressive. It's pretty amazing. Now, we've all been pretty surprised at how successful it is. Any next steps about that program? Well, yeah. So we just opened up applications for organizations to take part in what we call the high school version of it called Google Codem. And what that is is students, again, all over the world, can take part. And what they do is they do much smaller tasks. And they're both coding and documentation, website main and system administration tasks for these projects. So they come up with much smaller things for them to do. And we set high school students off on it instead of college students, so under 18s. And then, because summer of code is 18 or over only. And because of that, we're able to get to a much younger demographic. And that people who maybe haven't even heard of open source before, but they want to do something exciting for their son with their winter break. So it's pretty interesting. And so that's going to launch pretty soon. OK. Now, we wish you the best of luck. Thank you. Thanks for this interview. Well, thanks for having me. Thank you very much.