 All right. So our first speaker is John Maddog Hall. John, I hope this picture is okay with you. So I first met John many years ago. I won't say how many. At a local lug meeting, he was invited out to kind of speak and he explained to us why he got the name Maddog. And after he was done talking, we all realized, yes, it was the reason why he was given the name Maddog. So I'm not going to talk anymore. I'm going to hand it over to John. John, do you want to do it again? All right, let's do it again. Just the first one, hello. All right. There we go. I am here to talk about the history of FOSS. I want to take you back in time. The year is 1964. A single transistor will cost you $1.50. And that's a simple transistor. A power transistor will cost you $2.50. A gallon of gasoline will cost you $0.25. And so by the time you have a seven transistor radio, you can fill up your entire car with gasoline and go even faster. So I had to have this because back in those days, it was the beginning of the hippie movement, tie-dye, you know, summer of law, just a little bit later. And I was a high school student studying electronics. But then in 1969, I went to university. And 1969 was a magical year because in New Jersey, at fellow laboratories, two guys started a little operating system that became known as UNIX. Ken Thompson had been working on a project, a large project called Maltics. It was supposed to be the be-all, end-all operating system for everything. But he was taken off of that and bought back to Bell Labs. He picked up a spare PDP-7 computer system from Digital Equipment Corporation. And he and Dennis Ritchie and a series of other people started working on this little operating system called UNIX. It was supposed to be the be-all, end-all thing for one person. A little while later, they moved it to a PDP-11. And this became one of the most used machines in the early days of UNIX. Now, why was this important? Because up until this point, people wrote operating systems that was tuned to a specific hardware and tuned to a specific purpose. And you bought a machine that did a specific type of job. UNIX ended up being a small system that was very portable across hardware. And this meant you could have exactly the same operating system when you had different pieces of hardware from different vendors. This was the first time that an operating system was taking advantage, or allowing you to save your training, to save your applications, to have it go across different pieces of hardware. Also in 1969, the beginning of the Internet, this is known as an imp. This is one of the endpoints of the ARPANET. You would have one of these in every endpoint you had, and then you connect your computer systems to them. And so from this was the very beginning of what we call the Internet and the World Wide Web today. Also in 1969, little recognized in any place except two people in Helsinki, Finland, a baby was born. That baby's name was Lina's tour vaults. That's how you say it, by the way. Lina's tour vaults. It's not Lina's tour vaults or Lina's tour vaults. But he gave up trying to convince people how to say it, so he doesn't care what you call it as long as you use it. Also in 1969, I was a university student and I became familiar with this organization called DECUS, the Digital Equipment Corporation User Society. Now as I mentioned before, back in those days you had a computer and if it had an operating system, sometimes they didn't. Sometimes when you wrote your application, you linked the device triples into your application and booted your application. It didn't have an operating system. It ran one program at a time. And there were very few computers of one architecture or one type. So when you wrote your program, you typically wrote it for a specific computer, maybe in a higher level language like Fortran or Koball. Notice I didn't say Fortran 4, Fortran 77, high performance Fortran, Fortran 99, or any of that because there was only going to be one language called Fortran. That and punching cards was all you needed. However, you also had commercial software because your mainframe computer might cost two and one half million U.S. dollars. That's when a million dollars was a lot of money. And since you're only running one program at a time on it, you want that program to be as efficient as humanly possible. And so if you could buy a compiler that would give you 10% better performance on your program, that's like you got back $250,000 of your investment of your computer. And so you would pay 100,000 U.S. dollars for this commercial compiler. And when it showed up at your facility, it came on a nice 12-inch, nine-track magnetic tape attached to an engineer who would spend the next week there getting that compiler to assemble and then compile itself on your computer system, and then you would run a series of tests to show the compiler was supposedly doing what it was supposed to do, and then the engineer would go away. But you would keep that tape and you had the source code for it because you had purchased that software and it belongs to you. There was no copyright on software back in those days. There was no patents that applied to software back in those days. You bought the software and you typically bought it under a contract. Contract law was what applied. However, there was also a place called Deacus. IBM had shared. Novel had brainstorm or something like that. And these were user groups because also in 1969, the concept of being a professional programmer really didn't exist. If you did programming this because you were an electrical engineer and you needed the computer to help you do your work, you were a civil engineer and you needed the computer to do your work, you were a chemical engineer, you were a mathematician, you were a physicist, you weren't a programmer who wrote programs for somebody else. In fact, I had a university professor tell me in 1973, John, you will never make it as a professional programmer. And I'm still trying to figure out if he was correct. But in any case, all these people took and wrote their software to help them do their job and I said, what am I going to do with it? Because selling software is hard work. If you're going to sell software to somebody, you have to write documentation. You have to have some way of fixing problems. You have to put it to different pieces of hardware. You have to do all these things and these people were not professional software writers. They were physicists, educators. And so they contributed their software to Deacus or Share or Mindstorm. And the people who use that equipment could then get a catalog, look up and say, ah, there's a text editor. And I can use that text editor on my hard copy terminal right there. And I could pay $5 for that text editor and get it on paper tape. And so you set away for that. But as a college student, $5 was still a lot of money because back in those days that $5 could buy you 10 pitchers of beer. And so you had this choice, you know, a text editor or 10 pitchers of beer. I think you can see what direction I normally went. But the great thing about it was that this was free software. Once you got that paper tape you could make as many copies of it as you wanted to. In fact, they encouraged you to do that. And so I went to the school store, I'd buy the paper tape, I'd make copies, and I would sell it to my roommates for $1 a copy. So after I had sold my 10 copies, I not only had my $5 back, but I had my 10 pitchers of beer. So I was having a living, making a living selling free software back in 1969. 1969 was also the last time I shaved. Well, we won't talk too much about that. Now, moving forward a little bit, I remember these guys in Bell Laboratories were making this operating system called UNIX. Well, by 1975, there was a whole series of people using UNIX. Not only the people in Bell Laboratories, but people at West Electric, there was the manufacturing arm of the telephone company, universities, and lots of other people were using this little operating system called UNIX because it was so flexible and ran across all these different pieces of hardware. And in 1975, people were still distributing UNIX in source code. And we would have these wonderful meetings, a lot like this, where people would get together and exchange ideas about how to make UNIX better. And people would give up and give a talk about UNIX and telling about what they had done. Except in 1975, this one company came in and gave a great talk about what they were doing with UNIX. It was fantastic, it was wonderful. Hey, I'd like to help you with that. Let's go down in the machine room, bring your tape, we'll exchange the software and stuff, and they said, I can't do that because my company is putting out a binary-only distribution of UNIX. And they don't allow me to give you the source code. Boo! Yes! Boo! Yes! But that was the way it was. And the next year at USNIX, there were a couple more companies that said, no, no, we're only putting out a binary-only distribution. Why? Because to see the source code of UNIX, you need to pay AT&T $160,000 for your first computer. And you had to tell them what the serial number of that computer was. How many of you know the serial number of your laptop right off the top of your head? Yeah, that's why I thought. And for the second computer, that was another $160,000. For the third computer, it was another $160,000. This is because it's a telephone company, and they didn't understand volume discounts. But for a binary-only copy, not only was it only $350, but you didn't have to tell them what the serial number of your computer was. This made it a lot easier for these companies to put out versions of UNIX that they can sell into the mass marketplace. But what it meant was that more and more at all these different UNIX conferences, people would not share the source code of what they were doing. And UNIX eventually became used to this, and there was no more booing and hissing. In 1983, there was a thing at MIT called Project Athena, and this was a movement by the schools because universities could get UNIX for $350 for a site license, the source code. Because universities were research universities that AT&T saw yesterday helping us develop this UNIX thing. I happened to be teaching at a small two-year technical college called Harper State Technical College. We were not a research university. And if I wanted to show my students the source code for UNIX, it would have cost me $160,000. And of course, my deed of instruction would just laugh at me for that. But at MIT, a research university, they were developing a version of UNIX that would go across lots of different workstations, and they developed this thing called the X-Windows system, which we use today. They also developed a security system that went across a network called Kerberos. Now, the reason I'm telling you about this is because in the next slide, we're going to be talking about 1984 and a certain gentleman at MIT by the name of Richard Stallman. Richard was a student at MIT and he liked looking at the source code for UNIX systems and he liked seeing how the source code was written and he liked being able to adapt his codes to use things like printers and stuff without having to pay a lot of money. And he was disturbed that these UNIX systems that had been open source code that he could see were now being closed. So he decided to start this project called Gnu, which stands for Gnu is not UNIX. And then later on, he started a foundation to create an entire operating system that would be free and open source. And he started with this program called Emacs, a text editor. And a lot of people say he could have stopped with Emacs because it was like an entire operating system in a text editor. But he went on and he did a compiler suite, he did a lot of other things, and he was gathering up all this software. Now, the interesting part some people might say is why didn't he start with the kernel? Well, by developing things like a text editor that was portable across different operating systems, he was showing people that you could have something useful that was the same interfaces going across these different systems. And he got people excited about working on that. Same thing with the compiler suite. He had a set of compilers that used exactly the same syntax and semantics in the compiler, no matter what operating system it was on. And this gave a level of programming capability that people were not used to. If he had started with the kernel in 1984, he could have finished that and we would have a very interesting 1984 type of kernel today, but nothing to run on it. So he went the opposite direction. So by 1990, oh, by 1991, most of this operating system, most of the software that could possibly go in this operating system was done, whether it came from Unix or whether it came from BSD, the Berkeley Software Distribution or whether it came from MIT or whether it came from a lot of different places, a lot of the software was done except for the kernel. And remember that kid who was born in 1969, Linus, because by this time, he was a university student at the University of Helsinki and he had just gotten a brand new 386 system which wouldn't do what he wanted it to. Now it came with an operating system on it. It came with this operating system called Windows. But Windows couldn't take advantage of the chip. Why not? What was new about the 386 architecture that had not been in Intel systems before? Wait a minute, somebody out there said it. Demand pays virtual memory. The 286 and the 186 and all the systems before could support swapping the style of memory but not demand page virtual memory. And Linus understood that there was an operating system that could do that but the operating system was called Unix and he couldn't afford any of the Unix systems that were there so he decided to write his own just for fun. Just a little project. It wasn't going to be as big and important like Minix or anything like that. And so he sent out a message to a lot of people and said hey I'm working on this, would you like to join me? And people answered back and said yes. Now originally he wanted to call the operating system Freaks. F-E-R-F-R-E-A-X but the person who was going to put the software up and then that for people to pull down said no, no, I'm not going to call it Freaks. We're going to call it Linux and the history comes out. Now by 1994 the kernel was to the point where there was a good enough kernel to be able to handle some problems and so version 1.0 of the kernel came out and a lot of people started making distributions. One of the first ones was a distribution called SLS, the soft landing systems. Another one was a fantastic distribution called Yggdrasil. Unfortunately they were a little bit ahead of their times. Those ones no longer exist. However Slackware came along rapidly and Slackware still exists today. Patrick Volkering, very excellent gentleman, is at the head of that distribution. And then other ones which we've heard of like Debian and Red Hat and SUSE, Connectiva and others came out. People say there's too many distributions. I don't find this is a problem. I could go back and forth between these different distributions but when I find what I like, I stay with it. So I don't care if there's 350 other distributions. I like this one. I stay with it. No problem. In 1994 I was working for Digital Equipment Corporation in the UNIX group and I heard about this person who had done something with software and one of the people in our user group wanted to bring this person to Deacus, remember Deacus? Still around, wanted to bring them to Deacus in New Orleans. Now in the United States there were two places that are called the Adult Disneyland. One is Las Vegas and the other is New Orleans. I love New Orleans. And I heard about this person and I said, okay we'll bring this person down to Deacus and they can show off their software. And we did. And I saw Linux for the first time. Now one of the things you can do in New Orleans is you go out on the Natchez. And I took Linus out on the Natchez and we're going along and I said, Linus, I've seen Linux now. I understand what the model is. It's really great. But you know it's only on Intel. It's only 32-bit. What would you think about taking it to a 64-bit system like Digital's Alpha, the world's fastest microcomputer? A risk architecture so you can get some of the intel-isms out of the kernel. Now what is an intel-ism? If you are a programmer and you're trying to do very, very efficient code, sometimes you take advantage of the architecture of the specific processor to do something. A little hack. And that's okay until the processor architecture changes underneath of you or you try and make the kernel portable to a different system. And then that little hack blows up in your face. And so what you would do is try and make the operating system separated into two parts, the least independent part that does all the things like scheduling, higher levels of memory management, things like that, and the lower part, which does the things that are specific to a specific architecture. And Lina said, yes, I'd love to do that, but I've been having problems getting an Alpha system from the digital office in Helsinki. And so I may have to do the PowerPC instead. That is a wrong answer. Don't do that. And so I went running back to my office at digital and I called up a friend of mine. Now you will be told that the way you get things done in a large corporation is that you write a product plan, you send it to your management, a business plan, they consider it, they look at it, stuff like that. Let me tell you, that's not how it's done. You call in favors. And I'd worked for digital for 16 years up to that point and people owed me a lot of favors. And so I called up this person named Jim Jackson and I said, Jim, I don't have time to tell you who this is or what they've done, but I need to have an Alpha system sent to Helsinki, Finland right away. What can you do for me? And this is a time where not even the engineers in digital had all the Alpha systems they needed. It's also a time where the system I was asking him to send was worth 30,000 U.S. dollars. And Jim sent it off with no more than that as justification. Now, the other thing you need to think about is that we started this port. In May of 1994, I met Linus, got in the system. He wanted to take time to think about what he was doing and also to bring out version 1.2 of the Kirtle because he wanted to stabilize version 1.0, fix all the bugs, handle all the problems, and then he would start thinking about this port to make Linux 64-bit and to make it portable because Linus didn't want to have a source code tree that only supported two architectures. He wanted it to support N architectures as many as he wanted to. And so he started to divide up the code in his mind that way. Now, you bring out a system like that and we started the actual port, January 1st, 1995 By November of 1995, the port was done and Red Hat had brought out an alpha distribution on CD. Nine months, approximately nine months. This was the fastest I had ever seen a port of this type done and done by people who were not working for the same company who were volunteers and a lot of them never saw each other face-to-face. Truly amazing. But now we had an operating system that basically had no applications for it. You say, what do you mean no applications? It's all those neat little commands of stuff in Linux and Unix. That's true. But no databases, no office packages, nothing like that. What do you do with something like that? Well, one of the first uses of Linux was to repurpose older hardware. You had gotten a brand new Intel system, you naturally had Windows on that, but you had the older system too. What are you going to do with that? Well, if you give it to somebody else, you have to buy another Microsoft license for that because you don't own the software. So you have to buy another copy and put that on the older equipment. That may cost you $400. But with Linux, you can just put it on for free and repurpose that machine to do something else. What could you use with it? You could use it as a router. You could use it as a small server. And what was happening at about the same time was this gentleman created this thing called the World Wide Web. And all of a sudden we had these people who had been using Spark systems with Solaris find out that they could use a cheap Intel PC with Linux to do the same thing, to create a shell account, to put a web server on it. And so Linux started to be the favorite of the ISP. And one more thing, because you had the source code if there was a bug in the system, if there was a virus attack, if there was something like that, you could fix it yourself. And this was very important if what you're selling are services to other people. There was a very famous worm that happened called the Morris Worm. And Digital Grip Incorporation finding out that the worm existed and understanding what the problem was took two weeks to generate and test the patch and distribute the patch to our customers. That was for the system that we still supported. An older system that we dropped support, it took us three months to develop the patch for that and we almost didn't do it. The free software community within four hours of understanding the problem had the source code patch up on the web. In 1995 there was another problem. Supercomputer companies like Cray and E.C.L. were going out of business because they would design a very expensive, very complex system and then they would sell five of them. Two of them typically to universities, another two to some of these organizations we dare not say their name. And then one would disappear someplace. And they were going out of business. The two people from NASA, Donald Becker and Thomas Sterling developed this concept called the Beowulf Supercomputer or high performance computing of taking inexpensive PCs dividing up the application and having them do amazing work. You could get 40 times the power, the computing power for the same amount of money or only have to pay one 40th what you would pay for a supercomputer to get your computing power you needed. That created another market for Linux. In 1998 Informix announced that they were going to port their database engine. In fact they not only announced it but released a code on the same day that was overshadowed by a company called Oracle who found out they were going to do this and announced that sometime in the future Oracle would port to Linux. And of course that took all the press away from Informix but over the next couple months the database companies all ported and this gave a vision of legitimacy to Linux. Then finally in the year 2000 almost overnight all the embedded system companies decided to use Linux. And Linux became the most used operating system in new embedded system designs. Why? Why did this happen? Because up until that point a lot of the embedded system companies developed their own operating system a lot of times they had to use their own compilers. But in the year 2000 something special happened. They all of a sudden realized these things now have to talk to each other on this magical thing called the internet. And this means you need to have a network stack. And that's a hard thing to do. And the other thing is you have to have an operating system that is stable and secure and typically multitasking maybe multi-user. And if you're going to create 100,000 kiosk you don't want to have to pay 100,000 royalties. And so they looked around and the operating system they chose was Linux. So this brings this up really to the end of my talk. The next person is going to talk about Linux of today. I didn't want to get too far into their talk. So thank you very much. Thank you very much John. Alright, so as John mentioned our next speaker is going to speak about the present of Free and Open Source software Jono Bacon. He knows a little bit about the Free and Open Source community. I think he wrote a book. Some people may have read it. No, Jono is saying no. No one bought it. Did your wife buy it? No, she didn't buy it either. I have a copy. That's right, you gave it to me. Alright, so I'm going to shut up now and welcome Jono onto the stage. Alright. How's everyone doing? So before we go on, I think it's important that we give one of the most inspirational people in the Free Software world a huge round of applause. I love this man. Okay, so I'm here to talk about the present. I think it's quite simple with one. So, I think we are living in an incredible time when it comes to Open Source and Free Software. We've just seen such a remarkable amount of growth in the last 10, 15 years. I got interested in this in 1998 when my brother told me that Windows was a Mickey Mouse operating system. Installed SlackR on my computer, left the login details on the screen and then moved out. If you want a hardcore introduction to the Linux, that's going to be it. What's interesting to me is that we've seen so many interesting examples of success. Not just in the Linux world, but in the Open Source and the Open Culture world as well. So Wikipedia, for example, was valued at tens of billions of dollars by the Smithsonian. We've got Red Hat, who I think have now got to be in a $2 billion Open Source company. The first billion-dollar Open Source company. Of course, Linux is powering devices in our pockets, in stock markets, in industrial systems and elsewhere. OpenStack completely disrupted the cloud and democratized it in a way that we didn't have a single provider who was dominating that because we know how that works in the software world. And then, of course, we've got millions of repos in GitHub where people are building software for a wide variety of purposes all of the time. So you don't have to look very far. You don't need me to teach you all how impressive Open Source is in the present. What's exciting to me is that we've not just got those meaningful projects, but we've got stupid projects as well, such as Hannah Montana Linux, which I think some people actually use. Gareth. Yeah. One of those 300 distros that Mad Dog was talking about. And then you've got, for example, did anyone hear about the hacker scripts? This guy basically worked somewhere and left his job, and his co-workers found a bunch of scripts that he used to automate his life. One was called Hangover Dotsher, which would periodically check if he was logged into the server, and if it wasn't at a certain time in the morning, it would automatically send his boss an email with a pre-defined excuse from a list. And he also wrote a script called Coffee Dotsher, which would basically connect to the coffee maker in the office, which no one knew you could connect to with Telnet, and it would brew a cup, wait 24 seconds, which was the exact time it took him to walk from his desk to the coffee maker to pick it up. So we get people, the Open Source spirit and mentality and methodology has not just been used for really remarkable projects, such as the ones a couple of slides back, but for cases like this as well. Now when I started out, I had a machine that looked a little bit like this. This is running DOS though. And what was exciting to me was that this essentially connected me as an 18-year-old living in the middle of England to an electronic world where I could play a role. And it was the combination of the internet and computing power and open tools that made that interesting. What is exciting about the present in my mind is that we've seen this remarkable growth in computing power. So we've seen the growth of computing curve, which means that in 2025 a $1,000 computer will be as powerful as a human brain, for example. And we can use this for data-intensive tasks. We've seen tremendous examples of this, such as Microsoft in the AI world and big data in various other cases. But we've also seen a remarkable growth of internet access as well. So now we're getting powerful computing mixed with ubiquitous internet access and open tools, and that opens up all kinds of interesting possibilities. What happened here, I think, is my slides aren't working. Cheap computing drones and 3D printing. What we're seeing here is we're seeing this birth of all kinds of interesting technology. So cheap computing, such as Arduino and Raspberry Pi's, we're seeing 3D printing, such as the MakerBots and the 3D systems printers. We've got drones, such as the 3D robotics solo. We've seen open source, this huge library of open source for building anything from wireless to games to anything else. Of course, the massive growth in the cloud. And there's always been traditionally a problem, I think, between connecting innovators to the consumers. People have been working and hacking on interesting problems for many years, but crossing that divide has been very difficult, and Crowdfund has essentially opened that up so the public can be your VC. And what's exciting to me is that all of these things are infused with openness. If you look at each of these different areas, people are doing things with open source projects. The majority of Kickstarter and Indiegogo campaigns I seem to see have got some kind of open source bent to it. And this has opened up a world where when I started out with that computer, I never had any of this technology available. So what we've got today, available for every single person in this room, is really inspiring. And this means that we see projects such as this. The 3D robotics solo, which is this drone up here, Linux powered, it's got two Linux computers in it. You can build custom hardware that will hang on the bottom of this drone. You can access it and get data from the drone. This thing is incredible. It's like a games console for the sky. And then you've got things like the Microsoft, which I'm a big fan of, which is open hardware, open source, open services, just a way in which we're able to, again, democratize artificial intelligence. So we're not just seeing really interesting open source projects. We're seeing all these interesting open hardware projects as well. And the reason why I think this is happening is because what we've seen in the last 10 years, and what we're seeing today, is that open source is where society innovates. This is where we're not just learning how to build interest in things, but this is where we learn how to work together around code, to work together around open documentation. How do we bring a group of people together to build interesting things in the most effective way possible? And open source has just become this fascinating laboratory for where we're exploring different ways of doing this. And it's like scale helped to iterate that every single year. But we can do better. So before I stop rambling about the present, I think there's some things in the present that are not perfect. It's not 100% rosy. I think there's two things that we can figure out moving forward. The first thing is figuring out how we can bring the worlds of atoms and bits and bytes together. So we've got hardware communities that do interesting things. We've got software communities. The openness in hardware and openness in software has opened up this world where we're going to be collaborating around hardware projects with 3D printing and firmware and open source and various other pieces. So this is a really exciting scope. It's kind of like the original map of how people work together in different ways in projects has become 3D. And we now got multiple layers in how people collaborate together around hardware as well as software. Another thing is figuring out how we build effective communities which is obviously something I'm somewhat passionate about. How we go from an idea through to implementation. I feel like we're doing some incredible work here across a wide variety of open source projects, but we haven't quite figured that out as well. And what this culminates to is that when I started out and I had that computer and the course of my career, the technology that's become available to me, when I think about people like this, which is my three-year-old little boy, and we think about what we'll open up for him in the future. It's going to be a pretty inspiring place. Thank you. All right, thanks, Jono. I'm going to predict that 2016 is going to be the year of Hannah Montana Linux. Mark my words. All right. So our final speaker in the Floss Reflections talk. You have one more of your son. Three of your son. There we go. All right. So our next speaker is Kayla Banks. So for those that don't know, myself and various other scale people, we've been doing this for 14 years. Kayla has been attending scale before she was born. None of us can claim that. So I'm going to welcome Kayla up to the stage. Kayla is going to talk to us about the future of free and open source software. Thank you, Garrett. So first I want to talk about me. They invited me here because well, I like to encourage kids to get into open source and I talk about open source for about four years now. But really since I'm representing the future they could have asked everybody in this room to represent open source because well, I like to explain it as my own personal experience. I have a lemon tree in my backyard and you know California soil is pretty bad and so well, what if one of those lemons want to just fall on the floor and grow their own lemon tree. I like to call that the present and that means the older people. They are the ones who will reach the soil for us. And I, the lemons are the ones who make new trees. And that's why I like to call everybody the future because everyone is involved in making new, better trees. I guess the clicker is not working so I guess I'll just talk. So first I want to talk about what I see in the open source. I agree with John. The present was a pretty awesome decade for open source. Everything was awesome and so you might be thinking well what can we improve on? Well, the main thing that we need improvement on is connection. Just think about it. We might have social networks that connect us to people but are we really connected? I mean, if anyone's watched The Future 2015 was supposed to be mind reading and it's actually not too far from it. I like to, I like to, I like to predict the future as the year of connectivity and one thing that makes this possible is a way of life I like to say is internet of things. Actually, my friend Jasmine's cruise is that John Cruise works for Samsung's company Tizen. Tizen is supposed to be an operating system that's not just operating on your computer. It's supposed to be on your phones, your TVs, your smartwatches, anything that has a device or it has a screen is probably going to be run on. I think internet of things that Tizen might be the future of open source. And so now that we talked about what the future is, let's talk about things we need to improve in the future. So the biggest thing I think that prevents kids and other people from joining open source is lack of support for gaming. That's mainly why I go on my Windows partition for gaming because when I put a bunch on my computer it was very, very hard to run Sims 3 and still have all the compatibility and support for all my mods and hacks. So yeah, you know as kids we like to play video games. So Linux this is what we're known for it's bad at it. Actually this is kind of a issue in my family since we're big time gamers. And so you can also check out my brother Hunter Banks who writes for FossForce magazine. He writes a little bit more about that issue too so you should check it out. And next I want to talk a little bit more broad than just floss reflections. If you look in the acronym floss you see that there's software well in the future I predict open source is going to be way more than software. There's a huge industry that I think open source can take over and that's hardware and I think we can start with 3D printing. Yeah, 3D printing already exists but I mean with 3D printing do you think about printing out a phone case or do you think about printing out a house it's possible and it's already happening in China actually we're way behind our game open source in the future of open source we are going to take away we open source community we're going to dominate 3D printing even if it's houses our dad actually has a friend named Jonah who takes over open source architecture yeah, open source architecture they make houses that are made from biofuels using blueprints that are all open source so that's just a little bit of what I think and going back to what I said first everyone in here is open source and so that means even a little grab at this morning Zoe if you have any ideas or anyone in this room that has ideas of what you can bring into open source don't be afraid to share oh and also if you want to learn a little bit more about the future we're having a talk the automated team on Saturday at 1.30, thank you alright, thank you Kayla so we have a few minutes before Brian Lunduk's talk for those of you who hadn't seen it was all over the internet so I imagine it's most of you the free and open source community had a big loss a couple weeks ago Ian Murdock passed away so I wanted to invite Jonah and John back on stage just to say a few words about Ian and kind of their memories of him I didn't know Ian Murdock very well I only met him a few times but he was the person who started the Debian operating system and I think that Debian is unique in a lot of ways because a lot of the different distributions of Linux or GNU Linux Fridge is around they started as a single person doing it where they started as a company doing it or but with Debian it was first the concept of what are we going to do why are we doing this and they formed a community of people with a structure to it that allowed Debian to grow Debian is not just a distribution it's in effect a distribution creator and so a lot of the distributions that we look at today such as Ubuntu, Knopix and others are built on top of the packages which are created by the Debian community of people they take this very very seriously they elect their project leaders they use encryption to sign their packages they have a very set goals to maintain quality of their systems and they have a series of different systems one of which is very stable long term support and then others which are less stable development systems so I think it was fantastic that Ian way back when they started the Debian system thought this far ahead and yes we have lost a very good guy who was very modest very intelligent and it was a shame that he died I wish he had been around a lot longer like Mad Dog I wouldn't profess to have known Ian hugely he was somebody who years back I got an email from him once with some feedback about some of the stuff that we were doing in Ubuntu eventually met him at a conference I think it was Linux Targ if I remember and I feel quite fortunate in the fact that throughout the course of my career I've got to meet most of my heroes in the Linux in the free software world and he was probably one of the first for me to meet him and being genuinely tingly about it because he was if it wasn't for him we wouldn't have a lot of what we have today it wasn't to Mad Dog's point Debian is not just software it's a way of life it's a methodology that has inspired so many other projects and it's always nerve wracking when you meet your heroes because you're not really sure what they're going to be like and it was amazing to me that he was more interested in me than me expressing interest in him he was genuinely a humble human being and from time to time I bump into him he would usually be hanging out the front of a conference having a cigarette or something and every single time he was just such a given person to the point whereby I don't think he really ever knew or acknowledged his level of accomplishment in the work that he did so you know we'd invite him to we invited him to Lug Radio Live which is a ludicrous event for a person with a statue of Ian Murdock but he came along he was happy to participate at every step and I think that's what makes his loss such a difficult thing to deal with but I think from the little bit that I did know him he wouldn't want us to here looking blue about it he'd want us all having fun and continuing free software and open source so it was a good time thank you