So Greg we are here at open source leadership summit. Yes. What are you doing here? It's not a Linux, it's a 7-Open-Service. Yeah, it's Linux. 7-Linux is underneath all this stuff. To be fair, it is true. This is not, there's one other developer here, we're like, hey, a developer. But he's representing his company. I'm here to answer questions and talk about, actually how to talk about licensing for the kernel and SPDX and stuff like that. And then there's also a Linux Foundation board meeting later this week. So when you talk about licensing, what do you mean? So the kernel is GPL version 2, right? But the kernel source tree itself has like 10, 12 different licenses in it for different things based on what it is. We recently just, SPDX is a way to identify licenses in one single string, one single line. And ideally, you'd be able to just grab the whole kernel tree and know the license for everything. But it turns out it's more complex. There's six different variants of GPL v2 text we found out. So in doing this research, which GPL v2 do you care about? We have boilerplate text that is wrong in places. There's 700 different ways we save GPL v2 in the files of 25,000 files, right? 700 different ways. So part of the work is to go through and clean up all that. Recently, back in November or December, I turned out 11,000 of our files had no license text at all. So I did one commit to the kernel tree that touched 11,000 files and added the proper... So you have so much power? We talked about this in the kernel summit. We all got together and we're going to use the SPDX. Here's how we write it. And then after that, we're going through and cleaning up all this weird boilerplate and using just a simple, here's the line, here's what the text is. Because some files are dual licensed to the GPL v2 only or GPL v2 or anything else after that. So we just get the right list and we're cleaning it all up. So we're going to talk about licensing. Okay. I think you're working with Kate. So it's Kate and me and Philippe. Yes. Yeah. Well, I did a story about SPD a few months ago. It was a great year. Because people when they think about open source, they think it's open source. We don't have to worry about licensing or compliance, you know, but that's not the case. Right. It's really tricky. And how do you comply even with Apache and the BSD licenses require attribution? Exactly. So the really cool thing is the FSFE came out with a tool called reuse.  And so people that build products based on open source can use that tool to properly know how to handle what they're supposed to be doing, what their rules are, what they have to handle. I think the FSFE is totally different from FSFE in the US. Right. They are two different organizations. Yeah. Because I met Matthias and George who is also the founder. He's a very good friend. So we talked about the difference between two organizations. One is like Greenpeace, to beat everybody up and the other one is like more. I don't know. I've known both parties very well. I am a member of FSFE. Yeah. I do support what they do. So I work closely with them. And now I live in Europe. So it's easier to do that. It's even easier. And they're doing some incredible work there. They are. So like even just tools that we use, but then the whole public funds, public source. Yes, yes, yes. But I'm saying that word wrong. Yeah. But yeah, it's something like that. Yeah. That's a great, great initiative. And I know like the government of France has the rule that they have to release everything now. Right. But they produce all their data has to be even open, which is great. So the governments are changing and producing open source code and huge amounts now. And now since you have moved to France, and a lot of, you know, Colonel developers, you know, Leonardo and a lot of people, they are based in Europe. So how does change your working? I mean, you work for me. Yeah, it doesn't like I can live anywhere in the world. It doesn't matter. But there's three of us on the Colonel's security team that have to live in Paris. So we get together for lunch. You have to live in Paris? No, that we happen to all of them. So no, three of us are the 12 Colonel's security people on the team. We all live in Paris. So we get to the other for lunch once a month. Which is kind of funny. It's just really random. So do you talk about Colonel's stuff only or do you really enjoy French fries? We have good food. Good meat and stuff like that. So but no, we, but no, we talk Colonel's security stuff. We are all developers. But I think you're vegetarian, right? I wasn't telling the difference. Yeah, because you, yeah, I know. Yeah, when you can't read the language, you just have to accept sometimes what they give you. When you lived in Belgium because they speak French here, we were never able to order pizza over phone. Yeah. It was never there. So how is the experience living there versus here? Because I feel that there is much more awareness about open source and Linux, you know, all across the board. It is. I mean, so France specifically has the university I work with and Inria. Inria is a French government agency that computer science. And they've been a huge supporter of open source for the, they supported initial GCC development. There's a huge community of open source developers in there. They have the language OCaml, which is all open source. And that's a very French driven language, programming language that the research communities use as well as the finance community. So that's all open source. The universities teach on Linux. And there's a really, really, one reason I went to Paris was there's a really good group of researchers there that do systems development research on offering systems for that are applicable. So it's research that people can use. So Julia Lowell, who made Coconel, the tool that is fixed more kernel bugs than anybody else. And her team have done really good stuff. And they have graduate students and they do other research. And since you're there in France, are you also working with like any government organization or something like that to help them? I have contacts within different agencies in the French government that I have that do use Linux and I meet with them just because I've met these people and provide advice for them. One of them created a tool, a template for the office of the CIO of the French government that allows people to adopt an open source methodology for their company. And so we all created it with advice of lots of different governments. It was done in an open source way that to do group, a whole bunch of different people came together and wrote this template up. And you can take this template and it's been translated French, of course, and use that as a way to have, to control how open source is used. It like gives defaults of, hey, this is the licenses you should use and here's how you deal with community and here's the stuff. It's great template and it's all open. It's part of the to do group website now. So I was involved in that. Okay. So that was really good. Okay, now let's just switch gears from Paris and France to the real. I live there so I do know what it feels like. For the last one or two years, one of the things that has played Linux word has been security. Not just Linux word, but we saw the whole Intel before we go there. When we think about open source, we always think, oh, it's secure. The code is open. We have seen hard bleed and a lot of things happen. So what efforts does the Linux kernel community make? As Linus says, the software is part of, bug is part of software development process. So what steps are you taking to ensure that, okay, bugs will be there, but to detecting them early or to kind of mitigate them before they actually are released and they find the way in the system. Number one. So yeah, there's two things. There's one is a bug is a bug. We don't know if a bug is a security bug or not. There's a famous bug that I fixed. And then three years later, Red Hat realizes a security hole. But the other thing is the security, the kernel community realizes that we need to have mitigations. So hardening. We need to have hardening. So there's been a huge effort by Case Cook and others to take hardening features that have been traditionally outside the kernel and get them merged or adapt them for the kernel. So that when the bugs happen, because they will always happen, you can't do anything about it. It didn't hurt you. So like we have a simple one of, when you increment a number too much, it would overflow. So the reference count and you could leak memory that way. And now it won't stop. So things like that, we'll do things like that. Some stuff with protected memory and some other stuff. So that when the bug happens, the traditional old one was if you referenced zero as a pointer. Traditionally that used to be a security hole because you could access that. Many years ago we made it so we changed the way the kernel was laid out so that if that happened, it was just a bug and you couldn't do anything about it. It wouldn't hurt you. So in every kernel that gets released, Case Cook does a little summary of all the new hardening features that are there. That being said, you have to enable them to take advantage of it. Exactly. So I've seen, I've gone through and audited a whole bunch of Android phones recently. And some recent security bugs that we had like that would, if you had enabled the hardening features, wouldn't have even tripped it. There's a Bluetooth bug recently that it was a buffer overflow. If you enabled the buffer overflow checking and stuff that we have in the kernel, it wasn't mitigated so all your pixel phones were fine. They didn't even care about the bug. But other phones that just didn't turn that kernel configuration on were vulnerable. So it's part of getting into the kernel and letting people know that they need to enable the stuff. Yeah, that is the second part of the point was that even if you fix things, as you gave example of Red Hat, and we have seen and we also talked about earlier also that the system should be designed in a way that whatever changes or patches you're making, they should be actually applied. Yes, they should be applied and they should be used. So we release the stable kernels every week. I do a new stable kernel. Google announced that like one of the stable kernels 4.4, they wanted to support for six years. And they're doing that in a way because they want device manufacturers to take advantage of this. And then what I did is I went out and bought all the top of the line phones. They're based on the 4.4 kernel and see which one's actually updated. And so far only one company has actually updated their kernel. So the fact that we're releasing these kernels that are stable and update and have these bug fixes as well as so there's the carrot and the stick, they have security fixes and tons of bug fixes but they have some improvements. Like we sped up out of memory handling, we sped up a whole bunch of stuff. So you get benefits by taking these updates as well. These manufacturers haven't taken them yet. They're not updated. And so I'm working through the whole supply chain of trying to solve that problem because it's a tough problem. There's many different groups involved, the SOC, the manufacturer, the carrier. But the point is it has to push that kernel that we create out to people so they actually use it. But for the long term, you can't keep keeping up because there are so many bottlenecks as you gave exam. But why not? So today your Android phone gets a security update a month. That would be wonderful. Just update the kernel then. Yeah, but who's going to do that? Yeah, well, Google today already releases security updates once a month. But our Samsung, they... But then you got to push it. I mean, so there is a large ecosystem, right? So if you control the whole supply chain, it would be wonderful. But the way our ecosystem works, it doesn't... If we just keep these in consumer space, we talk about the server space where we have the CoreOS, which Red Hat has acquired. They came up with a model where it's atomic patches in the updates. There is a lot of... Yeah, that came from Android, actually. Yeah, that came from Android. But yes, yeah. They're constantly keeping up to date and update. And if you look even the enterprise issues, Red Hat and SUSE, even their big enterprise kernels do get updated all the time, too. But you just have to update them. Update them. But with modern systems, if you have lots of containers and pods and virtualizations, that makes it even easier because you're not relying on your 99... Your 9s of stability for your one machine. You can reboot this one and reboot this one and update it at the same time. And with that, it's actually made things better, easier to be secure than it used to be. Yeah, but now IoT devices are there, Google Home and Alexa. Yeah. I heard a story on verge that the author complained that, you know, I've only listened to music and there was an update on Alexa. They stopped my music and updated. I think it's a good thing that they stopped the music and updated because if you do a security patch, I won't mind, you know, my music getting stopped if the company is, you know, proactive and you know... Yeah, or do it at night or... I mean, there's... Except if you're doing a Tesla, you don't, you know, you certainly won't take over the system. Right, so like my TV, you know, it tells me, okay, I want to do this update. Is it okay to do it now or are we going to do it later tonight? It doesn't. It doesn't, yeah. And what about the hard bleed and, you know, Meltdown and Spectra? Meltdown and Spectra. It's a long day. Yeah. Seven interviews, so... Yeah, Meltdown and Spectra. First off, in the severity level of things, very minor. All you can do really with hard bleed... No, see, I did. Meltdown and Spectra is you can read data that you shouldn't be able to read from somebody else. You can't modify it, you can't change what they're doing, but you can get some information out of it. That being said, there's a really... Intel approached this problem that Google reported in a very different way. They approached it as a hardware bug because originally it was reported that, hey, the CPU is doing something really weird. So their hardware division was in charge of managing this. And then the software side got involved very late in the process. And then the way that Intel managed it, as everybody knows, was not really that good. To be fair, the Linux, by the time the leak happened a week early, Linux was fixed for Meltdown. We fixed it on time. Spectra was another issue. We got access to Spectra, that fixes and know about it about... We thought one week before we had to release, actually it was one day because it got earlier. Now the latest kernel versions are all fixed. So we fixed it all. The way Intel handled it was hard for the other source operating systems. The BSDs were not notified. Right. The OpenSlares was not notified. And that's that. And Intel is... I talked to them. I just had a phone call with them again today. They're reworking on how they approach security bugs and how they work with the community because they know they did it wrong. So that. So we do have a well-in-place process to do this. Security at kernel.org. You email us. Here's the bug. And we fix it. And we do this all the time. We do that. I fixed... We fixed security bugs that you could arguably say was more important like two weeks ago than what Meltdown Spectra was. Nobody noticed. We pushed it out. Everybody got it. Everything was happy. Just don't know about it. There's not... There's not advertising behind it, right? Right, right, right. That to be fair, Meltdown Spectra was a very unique thing that we fix bugs in hardware all the time. That's what a kernel does. But this just happened to be a piece of hardware that everybody has. Oh, yeah, yeah. And also it does... I mean, the mod... The bug was that it was an assumption that we thought the CPU worked this way. And it turns out it wasn't. So it kind of... Like the formal methods people are really interested because all of a sudden their model of what a CPU can and cannot do is wrong. So all their formal proofs for how things are supposed to work flew out the window because it turned out there's a side channel because they predict in the future and you can actually detect the prediction. So it was kind of a little side note that those people who formally approve programs are having to revisit everything. Doesn't it only need a new architecture? Or that's totally...  Yeah, Meltdown Spectra, that's probably easy. Spectra, it's just the way CPUs were designed that in order to go faster you have to look farther ahead in the future. And so in some rare cases when you can modify what you're testing so it's very simple. If this happens, then do that. So that do that was actually executed before the if happened. And so if you can control what that if is testing you can sometimes see what that is. So you're looking... And then if you're looking from the side you can see that. So in the kernel or what you're doing is you're crossing a security boundary. So me as a process I can see what another process is doing or me as a virtual machine I can see what another virtual machine is doing if I can control data out there. And you can. So there's been proof of executions of how to do this or your browser.  So the browsers are fixed for it now. The kernels fixed for almost all the big spectrum issues it's going to be a long tail of minor things where we just we're sweeping the whole kernel of all. Are this data that comes from the user or that the user can modify and do we need to protect from that? And we have tools that are testing for this thing in static analysis but the false positive rate is like hugely high so we have to dig through it by hand. But all the big issues for x86 and ARM are fixed. Other CPUs are more interesting. So when you talk about all this security I mean you're actually becoming like a security expert. Are there like I mean you have some big maintainers there so are there like some maintainer dedicated to doing this or it's like whether it's Linus or you or Andrew or whoever everybody's doing everything. So we have a security team, right? Our security so like the kernel security team is just a bunch of people who know the core of the kernel when we get a report we then drag in the domain ownership. So say there's a bug in the sound subsystem.  Sometimes on the security team we had some areas of the kernel that were always grabbing the same people so we made them just part of the security team to make it save that extra hop. So it turns out a lot of the core kernel people are on the security team we just fix the bug and everything's fine. But I mean all parts of the kernel have to be aware of these security issues because we are a trusted environment and you have to protect that. So these are just we have things in place the once we fix things we can put them in our static analysis rules and that way we never get it reintroduced. So we do things like that. But and then on the other side is like Case Cook and his work are adding hardening. So that's a other security type of thing and they're adding the features to do hardening and other bugs like that. Fix other things like that. As Linus said in the previous you know that we want the hackers to join us instead of attacking us. So how to kind of you know either encourage or incentivize people so that instead of kind of even if there are no such attacks or we have seen people are exploiting it how to encourage people to actually become part of the security community where they help the kernel community instead of. Well we always need help right. And so we have if you want to work on the kernel you can usually get a job doing that. On the flip side there's some companies that offer bounties for notifications of security bugs. I know Google does that. So we get a lot of reports from Google where someone's reported a bug to them and then we look and see and they think it's a security issue we fix it or not. So we get that a lot. So companies are willing to pay for that. Mm-hmm. So that there's other projects we have that so co-variety is a static analysis tool. For years they've been running on the kernel but no he's been fixing all the bugs he finds. So the common infrastructure initiative for Linus Foundation funded a kernel developer for a year to go through and just fix all those bugs. And he's doing an awesome job and he's got a job for you right. So to do all this kind of stuff and work through and fix all these bugs actually I need to get him to do some of the spectrophixes to think about it. So yeah so we have if you want a job to do this kind of work we have plenty of companies any company would love to hire you. I know some people who have started off fixing bugs and then can hire my companies just to do other development and things like that. Anything else you would like to talk about? Well I think about some you know I mean I can talk to you for hours. Yeah sure. We have a lot of questions. I don't know anything specifics. Yeah that's been consuming my life is getting all the updates to all the back ported kernels for that. But just yeah make sure you update your kernel. Take the update. Yeah if you make a device make sure it's always updateable. Right exactly yeah. So there's some interesting things with kernels wanting to be supported for a very long time because they're going into infrastructure. Like the Japan is putting them in streetlights. Yes you know. So that's a fun one. So making sure those kernels are stayed up to date and that we can test them properly in order to be able to push them out safely. I've been working on that. I'm talking a lot to chip manufacturers that way. Are you bored of this work? Are you? It's always something different. It's always something different right? And I still do the normal development and as far as review of the stuff that comes in. But no it's not important. I haven't got bored yet. It changes all the time. There's always new hardware. There's always new. I mean one really really neat thing about the Google thing with Spectre and Harplit is it opened up a whole new research into these type of side channel attacks. That was a brand new... It was a building on the prior art that the people have found but it was interesting in that it was hey there's something brand new here. But I said you know you're bored what I meant but you have been doing this for so long. I have. Yeah. And but the thing is that excitement is far from over. You know the new use cases are coming up. IoT is coming and so much is happening you know and everybody's using Linux for you know. Even Microsoft Azure is you know there's... Yeah Azure is ton of Linux. Yeah they're working with switches you know. It runs on Linux. So a lot of more work. But if you look at the core kernel community I mean I'm going back to the question that people keep asking is still the same people you know. You Linux and all those people. So how do you attract new people? Oh we have new people all the time. So every kernel release we have what? 150 to 200 new people every three months? Mm-hmm. That's a huge number right of people and we have what 2,500 people release. I don't remember the exact numbers. Mm-hmm. But so we still have a huge number of new people every year or every release are attracted and there's a side thing. So is when people ask we're getting older right new people. Is that a bad thing that people with experience and age are still working on a project because they still know what's going on? Mm-hmm. Or no I think that's really good. I mean look at the networking team they have been doing networking for 20 years right. That's a huge body of knowledge and we want those people. Now being said we have new people coming in to show their ideas or we need the help and we get new people in all the time. We have tons of work to do. We have tons of areas of the kernel that don't really have a maintainer. Um and we still have we always need the help so and we're still attracting them as long as we keep attracting new people.  What do I worry about? Uh-huh. We're about legal stuff unfortunately. What do you mean by that? Legal so we've had the copyright troll problem. Oh yes. So um which the latest thing just happened today in Germany that the um the current person who is doing that um withdrew his appeal. So he gave up. Honestly this one which was interesting. Um I helped out actually with that defense a little bit. And I put in uh it's not a friend of the court. I put in a little deposition saying here's how Linux is developed and things like that questions about that because what he was what he was proposing was not really the way Linux is developed. So there's legal threats that are um and trolls from outside our community are always my big threats right. What is um what that can hurt us and I always do joke Linux is so successful and is everywhere and so the only thing that can hurt Linux is Linux itself. Yeah I yeah you understand yeah. So what does make me worry is if we mess up if we if our development model crashes if we do something stupid and we push people away if we're not accepting still new developers if we our rate of change can go down it's fine our rate of change is so high but if we're doing stupid things that we're um driving people away from Linux because it's our fault and that's what I worry about and so every year at the kernel summit we re-evaluate what we do and we talk about our process and one of the things was like oh we need to do licensing in a better way because lawyers are reviewing this stuff this makes their life easier and they can make sure they're complying with our license easier great here's one thing that can help them out um new developers we look at that all the time um yeah so as long as we're still doing things well that's what we're doing and the external legal threats. Right I mean this could be off-record question I'll just ask based on your opinion then you said you know not to turn people away and you know uh sometime on uh mainly listen to Linux you know he has you know his own way of saying things but what people I'm not defending him or you know or but what people forget is that uh that treatment is reserved only for the high level maintainer you know the top maintainer that he trusts you know fully you know it's more like you're sitting in a boardroom with let's say Donald Trump you know and there are three advice the top advisor you know so there the language can be anyway it can be so I don't really know how much you want to comment on it or not but what I'm saying is that I see people misinterpreting because he I mean I've met him with the new people he like very friendly he explains things uh so do you want to comment on that or not so actually like this came up at lunch today with a group of people um it's um it's really hard to get Linux riled up so in the kernel development in the kernel community we have one rule and the one rule is we cannot break user space we made that guarantee over a decade ago called the Cambridge rule because we happen to be in Cambridge at the time um so Linus yells at you when you break that rule on purpose if you break that rule accidentally we're all human we fix it we move on or we break it and we can't figure out how to fix it we fix it and move on or we do something but Linus will yell at you when you're obstinate and you're saying I'm breaking this and I'm okay with breaking this and that's not okay um and it's a high it's a high bar to push him to yell at you I mean but some people are I mean developers are not the most um feedback friendly people that that feedback loop was not always there and email is a very tough medium in which to convey tone and expression something and sometimes you have to be very direct but if you are trying if I do something stupid and I break something and I know I'm breaking something and I'm insisting I'm allowing it to break Linus will yell at me for rightfully so and that's okay and it's always reported might say because fight I mean conflict is easy to report on and people are reading about it exactly it's more juice there it's juicy and like always said you should see emails for internal companies right I've been uh developers it's just totally separate I've been in meetings with some companies where people cry right some major companies used to have conflict as their major source of how they would resolve problems conflict with their way to resolve so I mean that and but so that's not a good thing at all but um I'm saying um what we do everything we do is in the open and tens of thousands of emails the problem is that's everything is an open so your frustration is also open so it's an open but and also I mean if I do something stupid or Mara does something stupid we know each other we exactly and it's friends so it's like I also used to term um you don't put a live microphone on a major league baseball or a major league football manager because he's yelling at his players right it's professional oh yes I know I messed up you're right because he told me that and I can take that for the what it's meant to be um yeah but we're doing in public right and it's not the little league you don't yell at the little league yeah I get it that way since we do have some extra time I want to because I talked to you earlier but that was not on the video format how did you start your Linux journey I've told you this before yeah but it was not on that's fine so I used Linux many many years ago I come from the embedded world so I used um Linux in a product we made where we were using sco Linux and running Oracle um Oracle came out on Linux uh we're like let's try and install it in a random wonderful so I'd use Linux for a while and then um I was working for a company um that we made barcode scanner and then um I was trying to test out my device with USB on all sorts of different operating systems um I accidentally made a barcode scanner that showed up as 102 key mouse so 102 key keyboard uh Linux didn't like that and Linux didn't have a working USB stack at the time so I was I saw this code I was like hey I can contribute and I fix some bugs and then it was fun and then um I've been messing around with a while and then my wife I was going away taking our daughter to visit a friend and she said hey why don't you write why don't you play with Linux this weekend and write that driver you've been talking about so I had this little weird USB to serial device USB to serial converter because I dealt with serial all the time and I wrote a driver for it and I submitted it and I wrote it and then um I learned from the Linux device drivers book which I ended up being a co-author on many years ago later um I submitted it and then instantly I swear within five minutes somebody wrote back oh this is wrong this is wrong this is wrong this is wrong this is wrong but I was happy I was happy I was like yes so I mean as a as somebody who is a programmer I know I'm always going to have to keep learning right then as you have to keep learning in order to get better and constant state of change you always have to keep learning and changing in order to adapt to the world so I was like yes I didn't know about s and p multiple processors what's locking and and what's this and oh yeah I guess that is totally wrong but that review process of I always like to code reviews and because you can get better and so I didn't take it you have to learn how to get rid of your ego and I can say I didn't have that ego and criticizing my code was great and I learned from that and I did better and I wrote that and that's fun and I had fun doing that and I wrote drivers and I wrote drivers for USB for a while and then I realized more people use the stuff I gave away for free the company I work for because the company I work for wasn't all that successful at the time and then I got a job doing Linux actually Linux security stuff so I started off in security oh okay and I helped write the first Linux security layer many years later but a hot plug and stuff like that so I've been involved in security for a long long time yeah so and how much influence do you have on your own kids are they all software developers or no my daughter's um no she has a degree in public health and she wants to be a doctor so she's applying to medical schools my son he knows how to program we learned the basics um he's now 13 but interesting thing is um you learned like learned the code and um code at the code academy you learn the basics and scratch and things like that and then after you can pass the basics there's no nothing to do exactly so it's like what do you and the same thing with the kernel you have these basic tasks but there's no intermediate tasks and finding a project on which somebody to work on it's hard because when there's minecraft you can build things and go away and that's a good distraction right I didn't have minecraft when I was learning how to program um so there's so many other distractions that I coming up with a solid program to make that hurdle to the intermediate stage is hard and I haven't I haven't figured out that problem so he learned the basics and that's good and that's everybody should learn the basics of programming just for whatever job you have what do you have what kind of hobbies do you have that kernel I used to um when I lived in the US I built a kayak wouldn't yeah yeah living in France I don't have a wooden kayak anymore so I really don't have any hobbies cooking travel we travel a lot more and see different parts of Europe it's fun right and what for the reason why you moved to France so I'd work with the university originally um in India they um did that I had gone over for a three month stay and um what's the family and we realized that and we wanted to move anyway and so we thought we'd try it a year and um because I can work anywhere because it doesn't matter and actually being in Europe worked out really well because I've done a lot of work with some German companies and things like that and going and visiting them is much easier right than flying across the pond and I've gotten to visit arm in Cambridge which is really easy and then we stayed a year and we renewed our visa we're going to stay longer yeah when you mentioned the German company you had been to Suze and Tumble Read was one of the project that you started and now it has taken a totally different shape where it's playing a very critical role in the whole Suze strategy yeah I'm really happy to see that so what do you think about it I love so I always I love that model that that continuing rolling update of model is a valid I always thought was a valid model for what a lot of people need it because you see people especially on doing the web stack and now containers are still that's the model you want to update that and you want to run the latest version of Ruby or latest version of PHP and um constantly update versus the old enterprise model where you backport things and you update on the two-year cycle and whatnot which works for some environments and the old traditional Unix model and the old traditional Windows model was that way I think the world changes faster and you want to do different things so I always like the rolling release that's my opinion I fully agree I have a rolling release so I mean our bodies are rolling really easy right yeah and also it's harder I've seen companies upgrade from major W and release this or to that and it's all this this harshness all the time we're like oh I have to figure all these changes in this happen versus if I have a change a week I can roll with that and I can figure it out and move on and then do it yeah it's much easier I think to do that and now with containers and Kubernetes and managing these things that makes it much easier to push out updates and keep things more up to date in a fashion that way I like that a lot better because I also use Arch Linux and but I prefer yeah Suze is a tumbleweed because what Richard Brown said that it's tested you know so that's kind of contrary to what rolling release is because they no you can always do a rolling release and test it yeah that's why he said you know it's well tested you know rolling release versus you know whatever code is coming just three out so I love it yeah no I mean it's always like I say you should always update your kernel to all your devices but test it always test it yeah because I test it in what we can test things for which are our tests are getting better and better Lenaro's doing actually an awesome job with testing stable releases on real hardware and putting a real load on them or just build and boot exactly so they're doing a great job with that so test for your environment and because you're always going to use it in a different way and then you can push it out but test and if you can't test then you have a problem no matter what if you if you if you update this year or three years later so five years later yeah so you need to build your systems in a way that you can test and and the kernel that's been an interesting thing is it's implicit that when we ever add new features like new system calls one that we add tests because we don't know if the feature you're adding is right or not so and like some of these backports when we're backporting these big security features backwards I'm kind of like pushing back and say how do you test this and they're like well we didn't test it but it built I'm like okay we need to actually test this to make sure that it did work and to validate that so it's test and validate and so we're updating LTP which is the old Linux test project for years was stagnant and it would have a bad reputation in that there's a lot of false positives in it so it was always is the test wrong or is the kernel wrong and most of the time it was a test a lot of people are now finally that's been revived and they're pushing patches to it and they're updating it for fix all the false positives and they're adding new features to it so they're going to test more and more of Linux and now it's running in Linaros testing and it's really good and Google's doing some testing in that area so we want to test all these updates because the kernel does move very fast so we want to make sure we are at least not breaking anything so that's added to our test infrastructure and the zero-day bot from Intel tests every commit that we make to the kernel and it's running all those tests on those as well they have a huge list of tests that they run on every tree that and everything that before it even gets salinus and it has to pass this before it gets there and testing is very, very good Well, we were talking about what are you running? Are you running Arch? Arch, you're a fellow Arch user I actually wrote Arch tutorial it's become so popular because people want to try it and because once I went to Arch it was just my heart for me to though my Plex server is almost always broken because I use Arch user repository or whatever you say it and but it's fun, you know Yeah, Arch is good I mean I've resisted really hard I don't want to be a developer yet another distro it's nice just to be a consumer of a distro that is always up to date I have had problems where Arch updated its compiler and the kernel wasn't I couldn't build things so I had to make sure the kernel could do that but that was fun Yeah That was my fault Because as a journalist and as a user also I like to stay on you know latest packages or whatever is there so it helps me I don't have to wait for a distribution to for two I don't understand why they have to wait when the project is open source your distribution is open source why can't you work in advance you know and you know test and do everything at the early stages Yeah, if you look at the Debian release model it's very old traditional release software release model and again it works so one interesting thing about Spectra and Meltdown I want to say Herpley was that the original Intel approached the enterprise distros and so Red Hat and Susan Knotical were all notified before the community and the problem with and then the problem with that was the majority of the world does not run those kernel Exactly So the majority of the world turns out runs Debian and it runs their own kernel from kernel.org So like all the cloud hosting providers and all that stuff like my cloud hosting provider runs just the kernel.org kernel and it's awesome So that was the big problem with Meltdown Spectra is the one third of the world's kernels were safe but the rest of the the community was not notified in time so we couldn't get stuff out to the other people so one thing that education wise is dealing with the old model of companies only dealing with other companies that's not necessarily true you have to talk to the community because the world runs on stock kernel.org stuff or Debian actually Debian is everywhere So that old model of the slow release for Debian does work and they're really good at backboarding stables to our patches and they go through a ton of work I don't like it because so that model but you can always run Debian waiting edge but it does work for a huge huge computing model and people are used to so it's fine and it's kept up to date and the Debian guys do wonderful security stuff so everything they're doing is kept up to date and it is rolling with the security effects but when you upgrade to a bigger release it's kind of hard then because of that yeah even I have not updated my Lenovo server to the latest because I was worried that something will break because I'm running couple of sites there with a lot of customizations so I didn't bother you know they still supported so when it will be out of that end of cycle then I'll update it so I wish I ran arsenic there so I run there arts there yeah I I mean I mean because now I'm like too busy with other things that I don't have time I will like at one point I'm like if I was running arsenic I'll just open SSH update it and done I don't have to worry about anything so you know the cattle versus the pet model so I think you have the same problem so my server instances are my pets because they're carefully too going off but if I had laptop disappears today it's the pet or it's cattle and I can back it up from from my server everything is on it nothing remains here either way everything is backed up everything's secure and if it's gone it's fine it breaks I move on to the next one and an hour of my actually less than an hour my new laptop's up and running fine so yeah so I need to make that so that my servers are treated that way and actually Kubernetes and the way you handle containers I've been starting to push some things to that and it makes that much easier so that model is much much powerful oh yeah I have a big build server for the my testing for the next kernel and it's now it's too I'm over using it it's so my builds are going slower because I'm doing so many builds so I think I need to just split it out and start using the cloud more and make it so what kind of machine are you using can you give us no I don't know it's some big it's in the it's in the data center okay so I bought me a big giant I got a big giant Xeon build server so do you go and sit inside just like science fiction movies sit in a big data no no no it's like when I do when I do a commit to the stable tree I how it commits and it pushes out and it fires off a test bill and I get a report from email depending on the load of it within less than five minutes but how secure is that server or data center who's it's just I'm building publicly available oh okay I'm just building it it's just a build you know what I mean and it's secure yeah how about Linus especially what kind of machine he uses he also uses the same yes I don't that's just my test builds make sure I didn't break anything so yeah I've committed everything to a public tree anyway okay so it's like I run test builds that make sure that I didn't break the build didn't break any warnings and things like that's all it is it's just a test load I just I could run it on I need to run on zillion cloud instances and go faster yeah so I run on my laptop mostly but I don't have any secrets right I got no secrets on my laptop I don't know yeah no I mean I mean I mean when you're doing open open you're doing open source the patches the changes that are coming to us are coming in public publicly yeah so with the exception of the tiny the tiny subset of security patches which only we only keep secret for a week anyway before we push them out so there's nothing is like secret there my wife's always saying the Russians are going to get into your laptop well it's fine it's like just there's a movie you know and we named K's laptop in the chain on the head it's all secured with that it's the next laptop no no we have we have two factor authentication so that when Linus and I push to our public repose that is two factor authentication so we do that it's so that's secure we encrypt our laptop drives and things like that so we have best practice actually so Constantine the systeminforerco.org has published a wonderful resource on how to do a secure Linux machine a developer machine and given it all to kernel developers it's public the systemin guide for how to do a secure systemin system because all the all the Linux foundation systemins have to do this and now he did a guide on how to do good GPG key handling okay and how to how to rotate them properly and secure them properly and what the good methods of care and feeding of your GPG key because we use GPG for when we do releases we sign them push them out that way so he's been publicly making that available to everybody and that's a really good resource what was this back back to the adopted after that one thing happened with the LKML the next archive was kind of compromised I think it happens so LKML.org is just a random website that gets an email archive of the kernel so that is nothing to do with our development our mail server is fine so that was just a think of it as a copy of all our public email it was just a mail server so um it's just a site you could search so we don't but there was something I because right now it's a long day I've forgotten there was something that was compromised then you guys had to rebuild everything or oh and kernel.org wrote down many many years ago yes yeah kernel.org got compromised many years ago so what is best practice about adopted after that oh yeah we have oh yeah so we have redesigned how kernel.org works amazingly and he gave a talk on a couple years ago with the kernel recipes conference in France on how kernel.org is designed and like when Linus does a I want to push a release so it's all publicly documented how we do everything and there used to be a Raspberry Pi involved in it too yeah but the Raspberry Pi did some of the the key signing because when we do the releases it would it would that because I was a secure little almost air gap system I was told that the Raspberry Pi is not in use anymore so I don't know what replaced that but it was something else but there's the steps that are involved with our two factor authentication system and when that and Konstantin comes from the Fedora community he was the system minister of Fedora and he's amazing and the other kernel.org systems are great so they built a system that is we documented how it all works and it's really really secure and like he says he wants to be able to make it if something happens to him or we need to pull we needed to revoke his access we can do it like that and it's still secure it's still here so we it's built and it's publicly it's public the design and implementation of all that is public as well so other people can be able to use it for their security. Anything else I think we covered a lot of topic today yeah it's fun talking it's fun talking to you all the time okay that was a wide range it was yeah which government from your your whole channel to your kids to friends to yes yeah from kernel to security to I enjoyed yeah we covered a lot thank you so much it was probably yeah I'm stuck it's always fun to talk to you let's go


This is stock number 11454Z. We are here at Summit Automotive in Fond du Lac, Wisconsin. You're new and use sports car headquarters. Today we are checking out this exceptionally clean 2013 Chevy Corvette 1LT 60th anniversary. This vehicle has the 6.2 liter LS3 V8 motor. All of our vehicles go through 130 point inspection, get a fresh oil and filter change, all the fluids get checked and tapped off per the state of Wisconsin inspection process before being made available to our customers. Cyber gray metallic is the color we shoot all of our videos in 1080p, 60 frames per second, so if you have HD capabilities on your computer, tablet, or smartphone device, I highly recommend turning them on right now because it is definitely your best way to check out the quality and condition of the car before seeing it in person. And if you'd like to check out all the photos on this car in the upper right hand part of your screen is a link to our website. Click that and check us out there to see all the photos. This one comes with the chromed Corvette rims. In the front they are 18 inch rims and it has Goodyear Eagle F1, 245, 40 ZR18 tires on here. These tires have a good amount of tread left. I'd say probably 60 to 70%, maybe even a little bit more. No scuffs or scrapes on that front rim. Driver's side fender is in excellent shape. It does have the HID headlamps, factory fog lights, and the front bumper is in excellent condition. I didn't see any major scuffs or scrapes on it. The hood is in really nice condition as well. And the passenger side front fender, no major scuffs or scrapes on there. Passenger side front rim, nice condition. And as you go down this side of the car, take note of how clean the body is, how reflective and mirror-like that paint is. We take these HD videos so if you are far away or even if you're close by, just cannot make the trip down, but you're still interested in purchasing the vehicle. You can see the car, hear the car, and have confidence in the vehicle you're looking at before you even get here. So when you do get here, there's absolutely no surprises and that is why we offer the Summit Auto FastPass option in the upper right-hand part of your screen. Link to our website where you can apply for financing. Get pre-approved. See a payment quote. Even appraise the trade all from the comfort of your own home. So when you do get here, all you have to do is drive the car, love it, or get it shipped right to your door and you'll know exactly what to expect because you've watched the video and you've looked at the pictures. Back room and tire, same condition as the fronts and the rear quarter is in nice shape as well. Coming around to the back of the vehicle, all looks really good back here. Some very nice clean chrome tipped exhaust. You get the dual exhaust with the quad tips and it's got a little splash guard there as well to kind of hide the mufflers. The rear glass looks good as does the hatch and on the driver's side just as clean as that passenger's side and for full disclosure this back rim is in really nice condition as well.  There are no rips or tears on those seats. The bolsters all look really good. Power driver seat, factory floor mats, power windows, power locks, power mirrors. You get the 60th anniversary plaque right there. Hop inside just to stop the beeping here. Leather wrap steering wheel, audio controls on the right. 10,000 and three miles are on this car. Instrument cluster is very nice and clean. Steering wheel is an excellent condition. You get the AM, FM and Sirius XM radio capabilities on here. Dual climate control. This one does have the six speed manual transmission. You do get an outside temperature display there. Keyless entry right here. We do have two sets of key fobs or two key fobs for this vehicle. Passenger side floor mat and seat are in excellent condition. This vehicle smells very clean. I don't think it's ever been smoked in. The hard top piece, headliner is in nice shape. And you do get on-star capabilities in the mirror with a compass display as well. We'll take a look at the trunk. You have to have the ignition off. Check that out and then we'll start it up and check out under the hood. Back storage area is very nice and clean. No rips or tears on that carpeting. Very nice back here. You can see the shocks are doing a nice job holding up the rear hatch. And we'll start it up and take a look under the hood. No check engine lights or anything like that. All looks good. Notice you do get the 60th logo on the tach and speedometer. We'll also check out those lights in the front. I would personally like to thank you for checking out the video today and hopefully from this HD video you'll have been able to tell just how clean this car is all the way around. Under the hood we have the 6.2 liter VA LS3 motor 430 horsepower. Engine bay is very clean. Once again our vehicles go through 130 point inspection. Get a fresh oil and filter change and all the fluids checked and topped off. You can see those shocks are doing a nice job holding the hood up. Here's the emission sticker. Take a look at those headlamps and fog lamps there. And we'll do one more final walk around on the car here with all the lights on. And once again I'd personally like to thank you for checking out the video. I would highly recommend this car from a quality and condition standpoint. It is in really nice condition. Really clean. I didn't see any scuffs or scrapes on it anywhere. Very nice car. And to see more pictures of this car or one of our other 450 new news cars, trucks, SCVs, minivans, Wranglers, Corvettes, Camaros, Mustangs, GT500s, Challengers, Chargers. You name it we got it. Go to our website right there www.summitauto.com full pictures and descriptions of every single vehicle from two locations all at summitauto.com and if you like to check out more HD videos you can go to youtube.com slash summit auto remember to like subscribe and share on this video and all the videos that you see there. In fact in a second you will see a link to subscribe to our youtube channel on your left. A link to more Chevy Corvette videos like this one on your right if you have not been to our website on the bottom link to our website click that check us out and we're super excited to be offering this extremely clean 2013 Chevy Corvette 1LT in cyber gray metallic. Thanks again for checking out the video.


Hi, it's Bridget. Welcome to Above Life channel. The purpose here is to inspire your spirit and to fill you up with hope. This video is part of a series of videos. I've done channeling Freddie Mercury in the afterlife. Now this video, I'm going to talk with Freddie about how he feels after the Oscars. Now I know you'll probably be like, what? If you're watching this video other than in February or March 2019, you might be like, why are you asking Freddie Mercury about the Oscars? How does he feel about that? Because Bohemian Rhapsody was nominated for Best Picture and Rami Malik, who played Freddie Mercury in that movie, won the Oscar for Best Actor. And so I thought it would be appropriate to connect with Freddie this morning, the morning after the Oscars and find out how the afterlife looks at this stuff. So let's have a chat with him. Again, this is part, this was originally part of the four videos, four days of channeling videos with Freddie Mercury in the afterlife, which you've already gotten five videos and now this will make it six. So I hope you enjoy the extra videos that I've shared with you. All right. And to find the additional videos, they are all on the Freddie Mercury playlist here at Above Life channel. Check out the playlists and you will find it. All right, so let's chat with Freddie, shall we? Okay. All right, so how are you feeling? How are you doing today? He's like he says, I'm always good. You know, I'm always good. It's kind of funny to ask a afterlife spirit that because they're not there. Of course, they're great because they're just spirit. They don't have to deal with the human stuff, right? But I want to talk to you about the human stuff, Freddie. We've got to talk about that. And to let you guys know too, I'm recording this video after I've already actually, I did an audio this morning with Freddie Mercury too. So we've already connected. So all right, so we already have the pleasantries done, right? Okay, so let's talk about the movie Bohemian Rhapsody. It was up for Best Picture. It did not win. But the band Queen, your band, opened up for them. So let's talk about that. Let's start with the opening. They opened up. They did. We will rock you and we are the champions. How do you feel about that? He says, he's like drinking tea, just so you guys know. And I actually made tea for myself too. So I have to have a little bit too. All right. So how do you feel about that?  He's like, they don't have time. They don't have time. You're right. That's true. There's like a time restriction there. He says, it's not a rock concert. It's a performance. Okay. I kind of wanted the rock concert though. I'm sure a lot of people watching did too, but it kind of got us in the mood, you know, to have some fun, you know, and to be at the Oscars. And it was an exciting year this year in Hollywood.  Well, for one, would you have performed? If you were invited to perform, would you perform? He says, oh, I don't know. He says, I don't know. He says, I don't know. Okay, so why is that? Why is there a feeling of not uncertainty about that? Not sure if you would actually have performed or not. If you were still here with us in human form, and if Queen was invited to perform because there was this movie about, you know, the biopic about the band, would you have performed? He says, I don't know. It's the energy that's coming forward. And I feel like it's because so he's giving me information sensory. So I'm sensing and feeling the energy and then I'm sharing it with you. So I'm sensing energy is giving me energy information through energy through the Claricentian channel, the heart channel. And then I'm translating that into words for you guys just so you know, that's how this is working right now. All right. So what's the not uncertainty about? He says, I don't think it would have been that big of a deal. Quite honestly, had I still been around? I don't know that it would be something people would want. I suppose they would. But it would be different. You know, he said it would be different. At least for me, it would be different. Well, how so?  And the band is, you know, in their 60s and things. And I can't imagine. He says, no, it's not about that. It's not about the age. It's not about age and aging rocker. That's not what he said. He says, you know, that things change over time. The music changes. The performance has changed. He says, it wouldn't be the queen that everyone wanted that they saw in the in the movie. You know, the rockers, he says, the rockers. Well, they did a pretty dang good job. You know, your former bandmate's Roger and Brian did awesome. He says, yeah, he says, yeah. Well, he says, would I sing and perform if I was still alive? Yes. He says, yes, but it will be different. It will be different. It's a different way of, he said, it's a different state of reinventing yourself. It's different.  He says, your body can't handle. He says, your body can't handle all that roughness. For one thing, he says, but the adrenaline, though, he says, the rush of the crowd just carries you through all that. He says, the stamina and things like in the performances, the rush of the crowd and that adrenaline energy just carries you right through all the performance. But he says, but that would be tiresome after a time. I would want to do other things, you know.  He said something softer, maybe. But he says, I don't really think it would be as big of a deal, he says. Or I don't know that. Even if Queen was still here, or you were still here and part of Queen and Queen was still the band together and you were this lead singer. He says, it doesn't really feel like there's like an uncertainty about that. And I think it's probably because did you ever get the sense that you wouldn't have a full life? Like that you wouldn't grow old? He says, oh, that's rather morbid. He says, and he's smoking. He says, that's rather morbid. But I'm glad you ask, he says. But I'm glad you ask. He says, not really, not really. You don't really think of those things. I suppose when your friends and those around you are having families and going through those sorts of family experiences, you see time as something that's passing. But you don't really realize it until it affects you and you get tired. And you don't really want to go out and be wild and explore and have new crazy experiences and stuff. I don't know the right words you guys to say, but it's like he's talking about like, wild is the best way to describe it. Like not needing to have this constant, chaotic energy. And he says, I just, I didn't have that anymore. It was about, he said, it was a good eight or 10 years, eight years. He said, right about 10 years before his death, he shows me that he started to realize that things needed to change and that he maybe could think about he started noticing he was different. And so is that due to age? Because you were 45 when you died, so I'm in 35. That's still really, that's still pretty darn young and happening for even for a rock star. I mean, if you look at the types like, you know, Elton John, who I know you were friends with, and who else, Beatles, Paul McCartney, I mean, they're, you know, out rocking it and stuff. He says, yeah, but he says, you know, he says, different things, I would definitely do different things. But then he shows me like eight years before his death, about then that's when he really, he says, I really knew things were changing, things would be different for me. I didn't, I couldn't quite understand or put my finger on it, or maybe I didn't want to think about it. But I thought about, you know, like aging, growing old, kind of a thing. What would I do when I couldn't do music anymore?  They refer to that in the movie, but that it was a concern of his, was his voice. Like that was the, his reason for living is his voice. He's very connected to it. So there wasn't so much a fear of dying as there was a fear of not being able to sing. So that was, that's accurate.  You know, I can still write songs and play music, but it's not the same as performing. Yeah, would you write songs for others? He said, I did. I did. What do you mean by that? He wrote, it looks like he wrote pieces of songs to leave behind or pieces of like words that he left behind that could have been made into music for other people. So whether that be, you know, Brian or Roger or whoever, it feels like there was some of that. I can't quite see you writing songs for other people necessarily, but unless you did, I don't know what he did. I'm kind of confused by that. He may have been asked to or approached to or coordinated or collaborated with somebody else to write songs that looks even outside of Queen. Like that looks like something that may have happened. I'm not sure because we're in this state of asking him to think about the future. All right, so that's the opening of the of the Oscars. Now, what about the lead actor, Rami Malek? Let's talk about Rami. In one of the previous channeling videos that we did, you mentioned it was actually the channeling video called Freddie Mercury being human channel. And you mentioned that you didn't haunt Freddie, but you guided him. You gave him support. Can you talk about that a little bit? And how do you feel about him portraying you and about him getting all these awards because it wasn't just the Oscars. He won lots of different awards for his for his portrayal of Freddie Mercury. It says, oh, I think he did a good job. You know, it's hard to be someone you're not. You know, it's hard to to pretend to be someone else. I suppose he says, although in a way performing is a bit like acting, you bring out the the parts of you that the audience needs or that that they expect. So in a way, I suppose it's natural for many. Rami Rami is a decent person. He definitely has integrity and he's making me feel like Freddie is making me feel like there's trust there, like he trusted him. And he said, he certainly talked to me a lot. He said, he certainly asked for my input and my guidance. Well, did you respond? So he talked to you and he asked for your input of guidance. He says a lot, oh a lot. And you were, did you respond? And how did you respond? Well, I made him feel like me. I made him feel the way that I would feel. I shared with him what you would consider energy, Bridget, but I shared with him. And in that way, I suppose I inspired, motivated whatever word you would like to use. And in his performance. So did you agree with the way he portrayed you? And he says, well, he did as much as he was allowed to do. Yes. Flamboyant is a word that comes forward. I don't want to like that word, but like being really, you know, expressive and that kind of a thing. He says he was only able to do what he was allowed to do. And he says, but I think he says, I will give him, I will give him a lot of credit. He said that takes a lot of courage to do what he did and to even dare to become me, to become someone that you're not sure how the people who are still alive, the family and the friends and, you know, queen, the members of the band, they were lovely to him, they were lovely, lovely to him, very supportive, quite supportive. I want people, I would like people to know that. He says, but to stretch yourself so much into a place where you're actually comfortable being not in your own skin, and he's referring to the costuming, not in your own skin. Rami mentions that, I think, I think he's talked about that before, about the, not risque, but the really interesting costumes.  He says, well, he says, but he had a good time. He says he had a good time. And it feels to me like he learned a lot to Freddie, that he learned a lot from expanding and getting into the character and getting out of his normal life roles. And that's what actor's jobs are, and how good they are at that, how good they are at becoming someone else, morphing into someone else, is what gives them the accolades and the recognition, like with the Oscars, you know, it's the Academy, so it's the Hollywood that gives it to him, and that's, you know, that recognition must feel really good. He says, you know, the awards don't matter as much as, he says, the people that come to support you. He says, it doesn't, the awards just, you know, they catch, he says they catch dust on the shelf. And what really matters is that people want to hear your music or want to see your movie. Well, that's exactly what they did, Freddie, because it was Bohemian Rhapsody. It was all about you and your band, you know. He says, you know, he says, I know there's a lot that wasn't covered or wasn't said or shared or, you know, put on display in the cinema, he says, on the big screen, he says, but nobody needs that. That's not that kind of in-your-face kind of flagrant display. He says, nobody needed that. He says, so he's speaking to the people or the fans who kind of criticized the movie to say, oh, it didn't show enough about Freddie Mercury's private life and his wild parties and his crazy ways and only made inferences of things and his lifestyle and such. But he is saying that that doesn't need to be, why does that need to be something that is in your face and the focus when the focus, he says, you know, he's making me feel like, he's not saying it out loud, I feel it. He's making me feel like the focus of your life, of his life was music and making music and bringing that to the people who wanted the music and who loved it and who enjoyed it and the creative process of making it. So this whole cycle, he says of the creating and the sharing and the receiving and the energy of it and all that, he says that was the whole point and he says of my life, he says that was the point of my life, not all this other stuff. Was it a part of life? Yes, that's what human life is about, a lot of different things. But does that need to be like plastered on the big screen so that everybody can focus on that and forget about the whole purpose of his life? No. So he is quite alright with the way things were depicted, just so you guys know. It wasn't like too tamed for him necessarily or he doesn't have like a judgment about that. So I just wanted to share that with you guys. I think it's important because I know some of the viewers will appreciate that. All right, Freddie, is there anything else? Do you want to see a, can we see a Queen 2 movie or something? He says no, no, I think. I think we've about done it now, he says. Is there anything you'd like to or you'd like to say to your bandmates, to Roger or Brian or John or, yeah, let's start with them instead of mentioning the new front singers. They did right by me. I would just, he says gratitude, like I feel this incredible amount of gratitude. He says they did right by me and he says we were a family and there was a lot of love. He said there's a lot of love, there's so much love there. He said there still is, so much love there for all of them, everyone, everyone of them. And they feel that. He says they know that, they know me, they feel me, they know me. What do you think about Adam Lambert? He's the new singer. I think I talked about this in another video but it's been a while.  So we kind of touched on this topic before. He says, he's bringing me back to like Rami Malik becoming him for the movie, same thing for Adam Lambert. He doesn't, he wouldn't expect, he's saying, he wouldn't expect him to be, he says I don't expect him to be me. He can't be me. There's only one, Freddie Mercury, only one, he says. He can't be me. What do you think of his voice? Oh, it's quite nice. He says it's nice. It's beautiful. It's beautiful. Beautiful, he says. Is there anything else there? It kind of feels like to me, Freddie, it's a job for him. You know, I don't know if it's like this. I mean, I know it's a really big deal, but I don't know if he feels, maybe he doesn't feel worthy of it. I don't know, but it doesn't seem, he doesn't really feel cohesive with it, you know, with the band and such. It's kind of like how when Journey, Journey when Steve Perry left, it took a long time to get somebody in there that just really fit, you know, better than some of the temporary people did. And I don't, I couldn't think of anyone else that could fit, you know, fell those shoes. He says, yeah, he says, you know, you can't expect people to be just be exactly the same. There's just not, he says, there's not that. It doesn't work like that. You know, it doesn't work like that. So he doesn't channel you. Adam Lambert doesn't channel you. He says, no, no, no. Afraid not, he doesn't know. He says, okay. He says, but it's not like that. So it's okay. It's all right. He says, as a peer kind of a thing, it's like there's a respect there, but there's not a, he doesn't have any judgments again about it either way. You know, he says it's up to the band. It's up to the band what they do, what works for them, what feels best for them. It's really up to the band. And technically, he's good. And he's got what it takes technically is what he says. But the relationship piece and stuff, you know, he says that takes years to build that, you know. Although I'm going to say you say that, but Rami did it very quickly with the band. He says, yeah, it's a little different, isn't it? Maybe because he asked for your help. And he kind of just looks up and smiles. That's it. All right, this is Bridget. You have been listening and watching here at Above Life Channel, a conversation with Freddie Mercury in the afterlife. We're talking about the Oscars from 2019 and some of his responses to that. Again, this particular channel wasn't a word for word verbatim channel where I'm listening and I hear the words and I share it with you. The way that I work very comfortably with Freddie Mercury in the afterlife and many of my other afterlife guests, it's through the heart, through sensing and feeling the information and then sharing it with you, translating energy and feeling of the message and the information into words. And that's really, quite frankly, how most of you are intuitive is that way. And so you've seen kind of both because of course I'm clairvoyant, so I see him, so I describe what he's doing, his gestures, his mannerisms, how his emotions are and such on his face, so to speak. Look, how he's being represented. But also there are some specific words that also come in as well. So there's a little bit of the clairaudience, but most of it's clarsentient, feeling, sensing information, energy, and translating that into a spoken word, but then also the clairvoyance, which is the site as well. So I think it probably helps you guys to understand or know that. All right. So what did you think? Did you watch the Oscars? What did you think of the band performing? They opened the show. What did you think of the Queen performance? And also what did you think? How did you feel about Rami Malek winning, winning the Best Actor award? How did you feel about that? Big heart emojis on that one or, hmm, yeah, I think it was good or it was okay, that kind of thing. It's okay to be honest in the comments. Just don't be mean. Don't be rude. All right. This is Bridget. Thanks so much for watching. Be sure to give a like, a thumbs up, and share it with others you think would be inspired or interested in this particular video channeling session. Thanks for watching.


So, thank you, everybody, for coming. Brief introduction. I'm outside of working in the conference. I work for Continuum Analytics. I'm a bouquet card developer and also just solutions architect and tech lead at Continuum. This is my Twitter handle. My email. Or you can also use Fabio.plier at Continuum.io. Continuum.io. A brief summary for this talk. So, usually I try to fight the boring of me speaking with some nice images. This time I'll try to do it with some nice plots. Before we start, some road map. I start with reductions and then I will basically go through what's in the recent release of bouquet. And then I will have a couple of extras of the bouquet ecosystem and briefly talk about what's next now. So, first, show me some hands. I'd like to know more about yourself. Who here uses bouquet? That's quite a good number. Who here never heard about bouquet? That's a good number as well. And that's good. Hopefully I'll show something good for you. Who here uses JavaScript for plotting or charting stuff? And who here uses B3? Sorry. So, here are some quick numbers before telling more about bouquet. Basically, when I started and when I joined the project, I think those numbers were really smaller. Bouquet had grown a lot recently and this is really cool. And we had a lot more community engagement. Bouquet is an open source project and it will say that it's part of the PyData ecosystem and it's under the known focus. And so, what is really amazing is to see those numbers really growing every month. We have a nice, good amount of stars, forks. Of course, this is not... We don't have 27 downloads a month on PyP. We have 5,000. And now we also have a chat on Gitter. So, I invite you to use it if you have questions or doubts or anything. Aside of that, we have the main list and all that stuff. So, what is bouquet? Bouquet is a visualization library made for Python and with data science in mind. So, trying to get rid of all the problems that a data scientist have when they try to plot the results, which is beneficial anyway for any Python user or any user because actually bouquet is not only a Python library. We have also bindings for Scala, Lua, Julia and NR in JavaScript. So, to get more about the project, you can go to the website and to have more information about it. It's going to be complicated. Okay, we have... You arrive at the gallery. And most of these are made by the core developers. Those are all basically bouquet plots made with bouquet. And many of these are... Some of these are actually user contributions. This one actually... Specifically, I'm very happy. This is full implementation made by an external contributor. And it's really cool. Look at this. It's all Python, no JavaScript written. So, back to the presentation. We recently just released a bouquet O12 version. Let me change this. Okay, a bit better. So, and you can get more information here at the main site. Documentation is really hard. Probably as hard as writing a visualization library like this. It's really complex as a library. And trying to document everything in a proper way is hard. Somebody do our best. And I really invite everyone that goes to the documentation maybe for the first time or whatever to post issues regarding what they found hard and how we can improve. And basically, we walk through all the main topics of bouquet and how to get through those things. So, I encourage you to do this. Here's the bouquet O12 release post. And basically, all objects you see here are bouquet plots. And they are interactive as well. So they can actually change things here. And there are different ways of doing this and how it works. And we'll be showing this during the demo. Hopefully the Wi-Fi is not so bad. And those things are connected. A few of these are connected to a server. The sliders are just JavaScript callbacks. But let's see in the moment. Cool. So what's that? Cool. So what are the new things? I said this talk as intermediate because to have a good understanding you probably is better to have an idea of what's bouquet and have used it. But I think it's beneficial for everyone. They should understand and see the benefits even if they never see it. Bouquet comes with a bouquet server, which is an object, a tornado server that lets you write Python and say, okay, every time my plot is updated or the user clicks on something or there's an event on the client side or in the server side, both sides can be synchronized. So we used to have another server and it has changed since around October or November. This new server is extremely more performant. It's all WebSocket based. There are no more REST calls. It's based on tornado and WebSockets, as I said. And it keeps basically all the objects and models synchronized between the server and the other side. So just to understand how a bouquet server app looks like, let's take a look at this. Now we're... Oh, well. Those are actually bouquet server apps running on that page and being embedded. But here you can see a few examples. So, for instance, this movies app is a bouquet server and it's connecting to a data store and I can actually change stuff. Every time I change this slider, a callback is triggered on the Python side. A pandas data frame is being keyworded and the returns are sending back to the server. As you can see, it's quite fast and it's quite reactive. And actually it's based on our example, which is actually slower than this. A shiny example, sorry. Let me see. Show off another example. For instance, this other one showed a histogram with showing off some of the bouquet server features. So we can select those areas. There's a Python callback that we compute in the histograms and they are sending back to the server. I can actually select multiple areas and I can actually also define the way those selections are triggering the Python callbacks. So it can be either every time a movement happens or in the end of the movement event. So let's see. Let me... Bouquet server now runs with the bouquet command. Basically to run on your computer, you just need to type bouquet serve and the app or the app script or the app there. You define your bouquet app. And it's quite simple to just run that. It accepts a lot of commands to deal with security and filtering. So if you need to serve behind an nginx server or you just need to serve under some ports or like use HTTPS connections and those kind of stuff. So this is what more or less a bouquet server app is the code for. More or less the same thing as a trivial bouquet standalone dynamic plot. There's a lot of code here but basically what is needed is you need to basically import per doc which is the only piece for the server. You need to import to create your figure which is the plot. Say all the things like how do you want to make it look add some glyphs or some elements to the plot. Here we define a pint of callback and basically we put a button and say every time someone clicks the button call this callback and then we add everything to the root of this car doc and that's it. Basically bouquet apps could be as simple as a Python script just a main dot py file and we write everything there or if we have some more complicated or complex requirements we can have a package or a directory with one file for the main file then a YAML file for a DIM how we want to make everything look and feel static for serving static files directly from bouquet server a server life cycle so you can actually define callbacks triggered in specific moments when the service is being spawned or things are shutting down and then we also have a template directory with an index file that it can replace the bouquet server main HTML template that used to be quite painful in the past that's a huge improvement actually well before jumping to the bouquet command I'd like to show you a couple of examples so let's so let me put it here so everybody can see so to serve a bouquet app I just go let's say bouquet serve let's do this this one is a bouquet server app that basically has oh I forgot to say I tell to show basically it has a periodic callback being called every I can't remember but it is redoing for Fourier harmonics for the whole circle and there's a lot going on the back and it's quite fluid as well another example that is quite nice as let's see this case I'm serving a bouquet app that is the directory and all I need to give the directory name this is an OHLC plot basically recomputing all the statistics and all the simulation every I think it's three or one minute a second and as I change the sliders the model is changing its behavior and as you can see it's quite fluid and the rate is fast enough to keep the rate between the Python side and the JavaScript side and it can be really anything you need we are doing simulations with NumPy and optimizing with Numba but you could connect to your data source or do whatever kind of crazy stuff you need cool okay let's move ahead here so bouquet command we also have two other we just saw before the bouquet command it also has different options the main most important ones are HTML basically it can just if your app doesn't have callbacks but it's just like client side callbacks or just some interactions with widgets you can use bouquet HTML or any HTML file that you can actually send by email or serve anywhere contains on the interactions that you need and bouquet JSON basically saves a serialized JSON file that you can then take and use elsewhere to create bouquet plots all the information I try to put the related links under every slide okay client side callbacks basically bouquet lets you also write JavaScript if you want so let's say you don't want to have a server you want to have some interactions and like in this case this case I have a notebook and I don't need a bouquet server I want to just have some sort of this dynamic plot and every time I move the slider I want this to move basically I would like to write JavaScript to do this and bouquet lets you it provides a custom JS widget that lets you write either a coffee script or JavaScript and define the code and it gives you access to the lower level data source so in this case this plot have one type of scatter and then it's connected to one data source you can say on this data source slide the objects or do any computation or anything in this case it's just replacing the source with every year as it changed so those JavaScript callbacks they extend the capability we are working this is because we are working on basically doing canned JavaScript callbacks for the things that most people want to do but we had a dream also to say what if we could write Python and make it work on the browser and it's not a dream anymore so with this new release you can actually write Python functions that we kindly translate to JavaScript for you and they work on the browser so like this case I have a bokeh plot, a simple curve that I have sliders and I want to tweak with the curve using the sliders so to use Python you just need to define your plot stuff and define a callback and define what kind of objects it need in this case the source which is the data source of this plot and a window object the window object is actually JavaScript but so basically you get the data from the source you tweak with your parameters you basically read the slider values and in this case we use the JavaScript function to recompute the numbers and then basically we get this object as a callback and we pass to the slider for every slider so every slider here we will be calling a JavaScript function that was written in Python and if you don't believe me well this is what's happening on the first page but let's show it locally that should work no, this is a similar thing slider maybe it's elsewhere maybe it's just slider and that's that in the O11 release it just supported Python 3 yeah but now it also supports Python 2.7 because sorry no, this actually is it just creates an HTML file slider and that's what it's serving there's no active callbacks or anything actually you can just get that and send to a client and the customer intro we actually you can actually write notebooks with those kind of things and use bokeh serve bokeh HTML to convert this notebook to an HTML file and just send the HTML file to someone it will convert the notebook to a bokeh HTML standalone file because it only grabs the cells that were created with bokeh anything that is notebook centric yes, anything that is notebook centric or that relies on your local data would not work but any real anything that is not related to your environment should work then you're fine cool we also now support jupiter notebook callbacks so it used to be quite hard because jupiter have their own web sockets that connects to jupiter web sockets we have our web sockets stuff right now we release the push notebooks callback that you can actually use to do the same thing and use ipython notebooks widgets to connect to a plot and recompuse okay another big problem with bokeh was that honestly it didn't look so well especially the widgets they used to suck a lot but they are super cool and better now and also it used to have really a lot of limitations with laying out stuff so it was really hard to do a lot in the way every user wanted so this one is a quick comparison about how things look now you can see the old one here and the new one here there are a few tweaks and changes in this case but the main things are that hbox and vbox which used to be the old boxes they are gone now we have roll columns approach we also have a widget box which basically makes easier to build rows and columns and it's quite simple now to lay out stuff and lay out stuff in a way that axes are aligned and you can define where to put the title and legend title and legend are can be put out of the plot itself so bokeh used to always need the widget inside the canvas area you can actually now put it outside this is an example of layout, column layout it's fairly easy you just need to say okay layout, column and then tell what to put in the column same for the row and same for grid plot we basically use array lists to define what goes and we compute everything we actually have a responsive flag that you can use to make things responsive and there are a few options like for the sizing mode stretch other options some layout examples I already showed you custom extensions so a lot of times bokeh do not contain everything like if you want to have a slider that looks differently or if you want to have a different kind of plot or different kind of tool you can actually bokeh now provides a mechanism to extend our models sort of a plugin system so you can actually create your own bokeh model either on the python side only or python and javascript side we try to make it less complicated it's possible so if you need to make changes to the javascript side you can actually define that on the python line class and you define a specific new attribute so how extending python classes work you basically actually let me show let me use this to help me so to extend bokeh on the python side it's quite simple you just iterate from the model you want to add everything you need for your custom model if you need to extend on the javascript side it's a bit more complicated you need to basically you have two options write your javascript file and then use it or you can actually just define your implementation in the model itself and I can show you here and that's all that basically you define your python class and you define this special under implementation attribute to define the javascript so the result of this in this case is for instance if I want to use hipster old school range I can just define all these things it works it injects all the javascript and the html into the page and replace the custom slider one so but you can also extend more things like if you what if bokeh doesn't support 3D and we want to have a 3D model now you can do it and you can so for instance bokeh show surface 3D you can actually have use whatever javascript library you want to integrate with bokeh and have the bokeh managing the higher level things and having your lower level javascript API doing the other stuff for instance it's using these javas that consumes a bokeh data source and plots the 3D dynamically on the page annotations bokeh now have real notations so you can actually use stuff to annotate your code we have arrows like this case and not that complicated you just import what you need as a layout in this case an arrow with open head and I give the coordinates you can actually tie that to data sources this is a box annotation here to highlight a specific area and yeah the way you use it is more or less the same you have labels like in this case with different aspects and we can tie it to different models we have we have much better geosupport now we actually support a geodeason data source that you can use to drop points on the screen we still have Google Maps support but Google just changed their terms of using APIs and basically you need to have your own key to use it but basically they didn't say anything and changed from one day to the other all tests failed so it was not nice but it's an extra step for the users and we are trying to check what we can do to make it just work geosupport we have good support for tile renders so if you have any service that you want to use we provide support for that to consume marketer projections new typescript and javascript API so typescript and javascript APIs pairs down the plotting API, the models API and a brief charts API which is not like bokeh core charts API it's just a handy thing to create like bars and pies on the javascript side like in this case JS transforms we have new JS transforms which means if you have a data column a column of data in the Python side and you want to basically create new data from that plot objects from the same column with some transformation we support this we now support jitter and interpolation so if you have just a number of dots and you want to interpolate in different ways you just specify the kind of interpolation you want we have now better WebGL support and it's actually quite fast just show quickly an example just show a quick example here of it now supports all the glyphs basically in this case we have WebGL not supported, not activated and if I zoom in you can see this time when things are gray it's basically recomputing everything and this is how it's recomputing to render everything this is how it's rendering with WebGL both examples have 10,000 points we have examples with 1 or 2 or 300 points and WebGL performs quite well but now there's a whole ecosystem growing around bokeh as well I want to mention two projects that are quite cool the first one is hollow views and basically hollow views let you have annotated data it's basically notebook centric and lets you have annotated data and it pre-builds it creates a new grammar to let you do specific complicated stuff with your annotated data so let's say I want to slice my big chunk of data in different layers in different dimensions and I want to have a slider to basically go through different steps and different layers of that cube of data it lets you do that quite fast those lines create this plot here and as you can see it's quite nice to read and quite lean in terms of code this other one project I would say it's fairly cool basically data share is part of the bokeh family and it lets you plot massive number of data on the browser this example here is taking the New York pick up and drop off data set it's a 12 million data set a few gigabytes I think it's 10 gigabytes of data and it basically just works well let me show you hopefully we still have time okay I should have that somewhere I still have questions though so you want to have questions or you want to see this cool so very briefly one problem with big data is that if you have points, points tend to overlap so in this case I have 12 million points I'm just plotting 1000 here you can barely see what's happening in this case 10,000 it's over plotting because you don't really understand anything anymore you can tweak with the data let's just have 10% alpha and 10% reduce the size of the dots but you don't understand stuff yet same here you try to improve and you can actually see the problem is that data is not linearly distributed so you have to have transforms and try to compute better data but the best thing you can this is actually changing in using logarithm transform this one is actually changing in using an equalized histogram so basically data shader lets you specify all those transforms and have a nice set of transform operations before it gets stuff to do okay so basically every time you have data in a screen you only see the points you would see so if I can zoom in it will basically go in and out and recompute stuff if I didn't break anything let's reload that oh this is the one on the browser this is being served on the network not locally if I still have time I'll show you otherwise just grab me later do you have time or no no okay I think 2 minutes is maybe fine thank you happy to answer questions on the conference aren't you