 Thank you very much. I'm very honoured to be presenting here. I'm not sure. I think I have been to all of the Libra Office conferences. Maybe I'm this one. I'm not sure. One of the things that I found really encouraging and really heartening is how much this community has grown from when it started basically as a spin-off and it's essentially moved to take centre stage and it's actually made the work that everyone has done here has actually made a great deal of difference to people's everyday computing experience. And I don't know whether you all realise that because I have worked on free software for a long time, so open source, back when it was free software rather than open source. So hang on a second, that should probably mention who I am. I'm actually just an engineer in Google's open source programmes office. That's a very old photo. As you can see by the fact that I'm probably about £200 larger in that photo. So Google's open source programmes office. What do we do? We're actually a small tax write-off for Google probably who live on the side of Google research and we do a lot of the work around reaching out to communities. We do license compliance both inbound and outbound. We release code. We encourage engineers within Google to release code. We've done the summer of code programme. I'm going to talk a little bit more about these things later. We do API licensing, protocols and specification releases and we also fund very specific open source projects such as my own project, SAMBA, Git, Gerrits, the Go projects, a boatload of other things. So yes, I'm the co-creator of SAMBA. Anyone here not heard of SAMBA just want to make sure. Well, you never know. I'm talking to an open source audience but I often talk to less friendly audiences. So I do a boatload of different things. I think I'm running off the wrong presentation here. Never mind. I'm doing no many more. I'm pretty sure I deleted that last night but there you go. So there could be more mistakes in here than I am. Hang on a second. No, I'm running the right one. Yes, there we go. I occasionally interview people and do things for the Google block. Probably doing something like that after this conference. So yes, that's kind of my credentials and I love coming to these conferences because even though Google doesn't actually ship a LibreOffice or an open office produced product, the standards that are produced around LibreOffice and open office, they're really, really important to Google. So, as I was saying, this project has made a great deal of difference in people's everyday lives. The one I know most intimately, obviously, is my brother who was a very unhappy Microsoft and Word user and was dealing with the daily transit tribulations. And the one thing that stopped him moving over to using the Linux desktop was Microsoft Word Compatibility and I'm delighted to say that the recent LibreOffice have just solved most of those problems for me. It's not perfect, it's not 100%, but it's good enough so that most users in everyday use, they can deal with DocX and the proprietary document formats and LibreOffice just works for them. And you know what, I think everyone ought to give yourselves a round of applause for that because that really is a phenomenal achievement and now I've sort of given you my credentials. I can say the reason I recognise this is because essentially I've seen this happen before. Many of you are old enough but many of you are not. To remember the old days of Linux when the idea of running Linux or Free Software on a desktop was just a dream, our goal at that point was to try and make some inroads into the service space. And many people have told me that SAMBA, my own project which interoperates with Windows, was one of the major drivers, obviously Apache 2, to enable Free Software servers to come in and display proprietary software. And LibreOffice is essentially doing the same thing on the desktop. It's the desktop, you know, the desktop, the word processing presentation, et cetera, calculations weeks. They are the things that are preventing people from trying out Free Software on desktops in offices and LibreOffice is actually doing the same thing for the desktop that SAMBA did and Apache did for the servers. Now unfortunately we have to make sure it's not a period victory in that we take over the desktop just in time for the desktop to become completely, not only irrelevant. So moving to mobile is obviously something that we care very much about at Google. And I would really encourage, and one of the reasons we like to help the Rockaway Foundation is to try and get LibreOffice working really well on mobile platforms because more and more I fly around the world a lot and I very rarely, I only see old people like me using laptops, many more on airplanes, everyone else is using tablets. So that's really where we need to go. So I'm going to skip through this section mostly because this is a generic Google open source programmes office slide that has to cope with people who really don't know much about open source and are trying to introduce them to the topic and why they should care. So I'm kind of going to skip through this about licence use. Hooray, go GPL. So here's something interesting. How many people here, and this is probably a very biased sample, how many people here actually get paid for writing their free software? Full. Okay, full time job? Yeah. That's amazing. I know this is a LibreOffice developers conference but still there would have been a time when I would have asked that question. That made three people's hands would have gone up. So the idea that people get paid as a full time job for writing software that they give away, I mean, you know, I was one of the very early lucky people to get paid full time for writing software and giving it away. And this is becoming a career. It's great. If any of you guys want to switch tracks, by the way, I could place about ten Samberg unions in Silicon Valley startups tomorrow. If any of you guys want to start programming and, you know, start going backwards and programming and see again and work on Samberg, I'm your man. Come see me later. So again, yeah, this is really the result. And I like to point this out usually not to developers but to sort of management types and people running companies when I get to present this in those environments. And what they're used to is they used to sort of thinking, well, you know, professional software isn't professional unless you're buying it from SAP or Oracle or even Google or whatever. This open source stuff, it's just amateurs. And it really isn't. It is becoming enterprise, well, it has become and already is enterprise-level software. And do any of you guys get to go to any of the Linux Foundation events? Has anyone been? Anyone? A few. If you've been to those, they're run by a guy who runs a Linux Foundation called Jim Zelman, who is the world's best used car salesman. The world's best salesperson. He goes up there and gives these amazing presentations. He goes to sort of thinking, I want to give you my money, Jim. He's marvelous at it, much better than me. But one of the things he's selling, and he points out his job is so easy, he's selling sort of free enterprise-level software. And most of the companies that are creating software-based products, which, to say, these days, if everybody realises what they're getting, essentially for free, or they have to put engineering resources in to maintain it and understand it, but the quality of the code that they're getting is phenomenal. So, for instance, how many people here knew that, has anyone here heard of Tesla? The Volvo of Silicon Valley. It's essentially all Tesla cars, their entire entertainment system, they're all Linux-based. So people are building amazing things on top of the software that essentially all of us are writing. Which is pretty good, it's keeping his image up. So, Google and open source. Where does Google fit into this? Well, Google started out as this pile of Lego bricks, basically, in Stanford University, and as they say, it grew and grew, and these are basically just sort of data centre build-out slides, and grew, and grew, and, you know, I can't show you a picture of the latest data centres because, as any Larry Niven reader knows, you can't take pictures in hyperspace. So, I've gone to those where the Google data centres really live these days. But if you step back and think, what is Google? So, what is it? Yes, a big company. But what actually does it consist of? It's kind of in-house hardware, line hardware, and everything is built on top of a basis of free software. Everything is built on that. One of the meaner things I do when I go visit private free companies is I'm talking to them, and I'm sure you know who they are, and they do all their own software, that's what they sell, and I chat to them, and I say, oh, you have to write all your own software, doesn't that take you very long time? Wow, and that must take years and years to put together. We just kind of pull things off the net, and a lot of other functionalities are only there. So, Google uses a tremendous amount of open-source free software. We have a separate repository, and he is going a little bit into the nuts and bolts of how the open-source program's office structures things. So, we have a third-party repository where everything that is in Google written goes into, and then we have a standardised mechanism of labelling, licensing, classifying things that go in there. Unlike most companies where you have to go through 12 levels of legal review to be able to look or import an open-source software project, in Google you kind of pull it in, you make sure that the licensing is correct, you make sure that everything has been pulled in in a pristine pull from the repository, and you check it in, and you're done. Now, obviously we have some sophisticated tools to make sure that when you build a product out of those pieces, all the licences are able to match so that you don't ship. You don't combine, say, GPLV3 with something incompatible from embarrassingly enough GPLV2 only. So you don't have a mismatched set of licences that break, et cetera, but it's incredibly easy to import and use free and open-source software in Google, and that's why there's so much of it in use. And then, of course, we actually create a lot of it and push it out the door. I'm going to talk a little bit about that later, but there are just... I've lost count, you would have to have automated scanning tools to count how much free and open-source software we have inside of Google and how it's used, and obviously all these layers of licence compliance around there to make sure that we don't scroll, because people love to see Google. We really try not to mess up. Unfortunately, one of the really tedious parts of my job that isn't automated is that sometimes somebody has to go in and physically look at the stuff and say, no, this group, you need to change this, the automated tools, and so, as one other process to bear, of being a Google open-source programme for these engineers, is you have to do licences review, but it's only about 5% of my time. So, you know, why do we do this? So, it's funny, I was horribly jet-lined last night and was up between 2am and 5am, and I'm watching the documentary on the making of 2000 more, and it hasn't been more, God knows why, because YouTube is available, you know. And essentially, it really comes down to this, although you never know, this could become a nightmare scenario sooner than you think. If you build your company, you build your software on top of other people's, on top of proprietary software, it doesn't matter who it's from, you know, if it's software that you can't modify and you can't control, somebody can always say to you, I'm sorry, I'm not going to let you do that. This is one of the reasons why personally I hate DRM so much. So, a lot of it is really around control and ownership. By having all that software that we are able to modify, we can fix bugs that we run into and that would prevent us from running the business before we don't have to ask anyone, we don't have to seek permission to fix any of these issues. And of course, the idea is to get those fixes back out into the community as quickly as possible, because sort of hoarding these things is a dumb idea. Now, admittedly, some of the fixes that people do, they might not be ones that you want to be given back, but that's another matter, witness the Android Linux kernel issues. But what it gives Google and what it gives anyone who's willing to invest in understanding and maintaining the software is complete flexibility and complete freedom. And you know, it's, like I like to say, it's really all Richard Storman's arguments for why free software is a great thing, including especially the freedom, but you know, people are scared of when you say freedom, they think you're some kind of communist or whatever, which is worse in the US than it is in Europe. So, you know, but we're not Google, but you don't have to be Google to really take advantage of all the things that are out there. And this is one that I often pitch to local governments and councils and cities, is essentially you can use the availability of this resource to build up your local talents. Silicon Valley is a very weird place. I've lived there for over 20 years now, and I know what I'm talking about. It's a very strange place for the very strange people, and it's a great place to be, but it's not the only place that innovation and creativity and software can come from. And having the software available to everybody means that, you know, giving enough people sat together, you can build your own business, you can build your own industry around the software that is available for free. So, you know, don't just become a user of someone else's proprietary, someone else's proprietary software. If you're that, you know, you're essentially, it's the difference between owning your own house and renting it. Using someone else's software, you're always paying rent, and you always will be. If you invest in your own people, if you invest in your own engineers to build and maintain the software yourself, then you have a pool of talent that you can use to build some pretty amazing things. I'm not going too bad about that. You've got a lot of it out. So, what are the specifics? Which I've already gone through in patching and code release. So, Google's very interesting, having, again, worked in many companies where you had to go through several layers of management permission in order to release a patch to an open source project. Google has one layer of management in the area, and it's what, there's just three people on it now. There's Chris, Daniel, Max, two of whom are lawyers, and essentially you mail them your patches for a week or two until they decide that you're not insane. And then they say, don't worry, stop bothering us patch directly. And they encourage people to patch from their Google addresses, obviously. So, it's an incredibly lightweight process to push things back out into the community. And that's one of the things about Google that I really love. I know I shouldn't come off as too much of it, but my company is a wonderful cheerleader. But there are some things that we do really well, and coding out extraneous processes is one of them. I have another story around that I will tell you about standards later on, I was blown away by it, but it's one of the reasons it's a really fun place to look at. So yeah, patching outwards is extremely easy. We just have to make sure we filter out the crazy people, and everyone has crazy people, you know, so even Google. So, then there are large-pushet releases. I'm going to say less about those. So there's Chrome, Chromium, Chrome desktops, the browser in the Chromium OS, mainly because they are so big now that they're essentially their own divisions in the company. They might ask us advice occasionally. And of course, the real heavyweight in this area is Android. We have someone who works in our office who works with the Android team on releasing, but pretty much they do their own thing, because they're an entire division in the company now. They don't want to have to ask the 50-person open source programme office for permission to do anything. So those guys generally release on their own schedules and release their own things, but we do get involved in some of the other things like Webim, Webim, Webim, Webim. I can never pronounce that. The video codec stuff, trying to solve the problem of free video codecs on the internet, getting away from the evil that is software patterns. And there are actually a boatload of different projects that get released, sort of fairly major code releases that come out of Google. So I've talked about inbound and that's most of the outbound stuff. And then of course there's someone's code. How many people have participated in someone's code? Anyone? Yay! Give me some round of applause. We love you guys. This is a slightly out of date slide, so I'm going to skip over it. So for the people who don't know, the goal is to get computing science students working on projects through a rigorous application process run by Google. I've said about that better. Projects apply, students apply, we match up students with projects and essentially pay them to write code and try and become members of the open source community. It's a great project. The biggest headache in this. Can anyone guess what the biggest headache is in this project? Anyone? Hey, the local. Exactly! Dealing with the 200 or 300 different tax authorities, laws, et cetera. So the actual coding bit and helping the mentors that's great, that's the fun part. And then there's like seven months of grinding work, dealing with all the local tax authorities, making sure that you pay people, you know. Yeah, that's kind of grim. So we actually run another program for high school students. Oh, which I didn't mention here. So we run a thing called Google coding, which is much more fun because we don't pay them any money. So that's actually much more fun for the open source program I've used to run because all we do is we give them a grand trip to Google and let them spend a week going around San Francisco and touring the Google campus. You know, and I have to go and give talks to them. It's interesting, I actually asked them a Google interview question in the talk I gave, which is kind of fun, which proves you should never write network services in C, but catch me offline after this, if you want to know a little more about that. So then we give away money. So everybody loves someone who gives away money. So we're members of the Linux Foundation, Grome Document Foundation free software, software freedom from servancy, which I'm on board of, Apache, we give money away to the SAMBA team, and many, many more. So it's sort of encouraging open source projects, open source foundations, and open source science and data releases. So we actually do a lot of work around that. Then we have a standards organisation which is affiliated with, but has its own vice president, and a vice president called Vint Cerf, who you may have heard of, and he runs our standards organisation. So this is one of those times when it's wonderful working for Google. The UK government was holding a consultation about what document format to standardise on for their all government communications, and of course the two possibilities were ODF and OOXML. And I was kind of dimly aware of this, and then because I have regular everyday coding work, all kinds of other things to do, licence compliance, completely forgot about it, until Michael called me up, Michael means to call me up, and he essentially said, oh, by the way Jeremy, the deadline's tomorrow. Can you get Google to submit something? I was thinking, oh, great. Yes, he wants me to get an official statement from Google sent to the UK government on their standards blog, and he's giving me a date to do it. And we did it. I was just the errand boy, and I had very little to do with it. I basically, I pinned Vint, who is immediately online, because I don't think he ever leaves me today. Maybe he lives there, I don't know. So I pinned Vint and said, do we want to do this? And he said, yes, this sounds great. Can you write me up a quote? So I wrote up a quote, and he was like, well, OK, we need to get legal review, but we got legal review in less than an hour, which if anyone has ever worked for a large company, you will know how unusual that is. And then the only other thing I had to do was I had to check with the Google Docs people to make sure that they weren't going to do something crazy, or we were going to get in their way, and in fact it turned out that the Google Docs guys were like, oh, that's great. We didn't know people really cared about that, but this is something that has basically told us that we need to improve our ODF support. So, yes. Oh, yes, question. Let's make it a moment to include ODF and ODT files in the Google search format. Search is a different department. Sorry. The comment was, now it's time to, now you've done that for the doc team, now you need to get it done for search. You remember how I said Android and Chrome were these big monoliths off to the side? Search is like Mount Everest. That would be nice if I ever find out anyone who works in search. Who works far enough at the top in search that I can effect any change there, I will be sure to do so. But yes, that's one of the downsides to working to a large corporation. Search is the biggest bit. But as I say, Google is built on internet standards. And so, promoting standards, promoting open standards, free to implement royalty-free, patent-free standards is massively important. Unfortunately, I have to use that crappy logo. The original logo for this was Eric Schmidt with the Shagovara, in the Shagovara piece with the little Baraeon, which I thought was great. There's a data liberation front, which is a gorilla organisation within Google that is designed to make sure that you can get your data out of any Google property as easy as you can get it in. So, we don't want to build any realtor hotels. So these guys basically run around and when anyone is trying to build something new, they go to them and say, okay, that's very nice. You've built this wonderful interface of importing stuff. Now what happens if people want to leave? That's great that happened. So that's kind of a very useful bunch of guys. And they do that in their spare time. That's run out of Shagovara, I think. Okay, so because I skipped a little bit, that's not too bad. We have a 10-minute coffee break before the next keynote. Are there any questions? And the person that they were supposed to be taking photos did. So, it sucks to be you who's supposed to come down and take filters on me. Anyway, he's going to do that now. Thank you. I hope. Yeah, any questions? Yeah. Do you follow the sound? Actually, less than I would like. So one of the things that has happened with Sam, and I'm going to get into Sam apologise here, one of the things that has happened with Sam over the years is that as best practices in open source development have changed, so have we. One of the things that that means now is that no code goes into Samber without two engineer review and without regression tests built into test whatever future goes in. So this is how we're going to collapse under our own weight of 20-year-olds like a C code. And because... So I love the code, and I probably get to code maybe one, one and a half days a week now, because the rest of the time most of my Samber work is reviewing other people's patches. And that kind of sucks in terms of doing new and interesting things. But as somebody pointed out and said, you get paid more than the other guys. If somebody is going to do this work, it better be you. So especially what I try and do is whenever someone posts a new patch, a new contributor, a new vendor or whatever, posts something on the Samber list, I try and shepherd them through getting that code into Samber. So I code less than I'd like, especially now I have an eight-year-old this text of one of my weekends, but very, very occasionally I will sort of disappear and just write something new just for the fun of it, but it's not as much fun as... I don't get to do it as much as I'd like to do it. But I try and have a bigger impact when I make changes. Yes, another question. Can you change to a dual of checking for the patches? Uh-huh. So it's not only sufficient to have an email that you need a VGP way to do it. Sorry. To the repository. Yes. I think this is a clever idea. I think they use some UBP with that. Oh yes, we don't know the things. So what is the way for Google, and should this maybe be done by the Document Foundation also? So I think it is an excellent idea. So the comment is that the Linux Foundation now have two engineer review, PTP sign-offs for all the submissions. Should the Document Foundation do the same? Yes. Yeah, there's some interesting ideas being kicked around and telling me about that that I can't talk about right now. But yes, that would be a very good thing. And if we can work out how to help people do that, we certainly will. Samba, even though we have Git tree, so the theoretically distributed, anything that goes into the main repository, theoretically it could be spoofed because we don't PTP sign submissions. But we have pretty rigorous code review. No one's tried, at least on the Samba side of things, nobody to our knowledge has tried to introduce security problems. We're good enough for doing that on our own. We don't need help with that. Yeah, saying that someone has introduced a lot of them himself. Yes, that did come up about a year ago and essentially the Document Foundation and the LibreOffice code base and committer base might be big enough that you need that. We're still relatively small. That's why I say, if I can get 10 more Samba rendunias, I can find you all jobs. So we still have about 10 to 15 people. At least for us at Samba, that might be a little wheelie. I would like to do it. If we can make it... You know what developers like. We've done it this way forever. I like doing it this way. I don't want to change that. I don't want to change as we have done to get the code quality. So that's a bridge that we will cross when we have to. Any other questions? Can you make a move to your left? Oh, sure. Shall I go back and pretend to be in the middle of the talk? Let me put a slide on so at least I'll look. So one of the bad things about working in Google is that when you take photos you can't have any of you in them because then I would have to get legal review and a sign-off that you would give me your permission to appear on the Google blog. I can't be bothered doing that. So at least on the Google blog it will be a conference with just me in it. Sorry about that because I know I can give them my permission. Yes, question. I'd just like to say thank you for Harris. The code reviews that you guys are doing. So that's actually run. So I have Git. On the left-hand side of my office I have Git, Wireshark, and one other, and on the other side of my office I have Gary. So it's great, whenever I have a Git problem I just go straight round to Junior and kick him and say, what's going on with my repository? Which is pretty good tech support. So that's kind of handy. The bad news is because they share a wall with me when I'm screening obscenities down the phone to a Samba interpreter they can hear me. Yes, Gary is very nice. We actually evaluated it for Samba but we couldn't agree because we are such a happy, uncontentious friendly open source community. The great thing about Samba is that we all, at least we all hate each other more than we hate all the other committers. It makes us so friendly. Yes, Gary is very nice. If you have any questions, comments, Sean is very happy to take your email. I was doing that when we were trying it out for Samba I would be around there every day complaining about the web UI because web UI sucks. Yes, any other questions? Just a comment. Just tying in with this PGP and signing thing. I would like to remind everyone on the key signing party which is a great event taking place tomorrow at 5. Oh yes, thank you. One other comment. I use Thunderbird with any mail and it works with Gmail. There's no excuse to not PGP encrypted and signing all of your emails all the time. I actually have mine set up so that it encrypts by default so I have to explicitly click no, I want to send this unencrypted. It's a pain in the ass because of course most people I'm sending to I have to click that but it reminds me that that needs to get fixed. If you really want to make our lives better put some money into an e-mail suck list. Well, so Google has announced that they're doing a webmail based PGP email and I think they're probably putting resources there. Did you see the announcement? They're actually doing a JavaScript based PGP. The key management will be the problem. Key management is always the problem. But crypto stuff is hard. I like the slide of this background and I also like what you said about the very quick process during the documentation. What would it take to possibly overnight to join the FTC from Google side? Um... It would require me to get attention from Google Docs to e-mail me about it and because we used to be on it I was one about to sit on these endless tedious conference calls that were at 6am my time and I think I just gave up. Because that's with a little bit more friendly now. Oh thank gosh for that. The truly 6am California time is perfect for everyone in Europe. Yes, please e-mail me offline. What are we going to do about joining the OEFTC? Any other questions or shall we get some coffee? All right, coffee break in here. Thank you very much. A short break and then we will go on with another keynote. Just pick some coffee or something to drink and come back please. Thanks.