 that has seen some great support. Did I get a hand on that? I'm going to be able to kind of leave you with some work done and then we're going to move on. Really? Do you have a case of support? Really? Do you think there are times when this will become almost all of our work and it's going to drive right into a free spot? Kind of just giving you some background. So it's kind of a strange event that has a problem with the community of the industry. We work together and it's been a long time here. I would agree with you about that. I thought it was probably going to be, you know, just a totally new year around the day. Cooler than the start of that kind of thing. We thought it was going to be a serious work. I feel like it's going to be something that's going to actually be a good push-up in those years. But really, even though we do have this kind of support, it really does drive us. I have to give you a little bit of advice. You basically have an energy use, you know, for years to come. There's a lot of people who follow that. I think we're focused on all the stuff that I'm trying to give you about how do you construct and build as opposed to the structure? What's the overall problem that you're going to solve? What is the impact that you might solve? What services do you want to resolve? So the kind of view I have on the problem is you want to ideally have where it enables you to do more actions about what you want to get done, not get bogged down in part of the visual construct that the school can still build. Now, many of our, some of our, especially maybe because it's not, because they do that, because there's a lot of interesting stuff that looks back to that. But the first thing that, I mean, I know that what I think was told was that it's got a lot of problems. There's a meeting before the team and the team strategy and everything, et cetera. So this is very interesting. And you've heard of artificial components, and would you actually, especially the students and all that? That's not good. We've talked to them, we've just been written on a board. It seems to be very interesting. And then when you look at the stagnation, particularly with the visual, you have had a robot, and you wanted to have a robot in the pack. So rather than it seems to be a program, it's a robot on who's chosen a move, you know, stuff, stuff, really to say, why don't you use a robot's goal and then have a computer automatically generate a plan to achieve the goal. So that's how we compare on a table. When a student is learning something and step up that three seconds, it looks like they might have a very similar view. They can look at a school that's looking or they're looking at some of the more workflow system and they saw that, you know, it's easier to distinguish that they can step in terms of little, in any way, in terms of planning. So why don't we describe the goal of this? So I believe that affects you the right approach by the right planning and what the students feel in the lives of the students. Now, it also exists in the lives of the students and the objective is to achieve the goal. Really, this question is what if the student with the goal is and the student with the more professionalism with the goal is to kind of put the more versatile goal. Does it bother you to ask me on the way because I think it's hard for us to make the system more easier. On a daily basis, what do you say about both the hospital vision and the buildings of the hospital and how they're able to survive? So they use the day-to-day population so when I was a student we worked on a system that worked with the students of Iowa and they're not on a distributed table to the floor that's giving them direct support for the whole bunch of families. I think that also largely when we know what's been happening when I was a student in the United States started to apply at least a certain amount of the data that started to be taken by the Mar-Man program was something that some know is starting to realize that it's giving a daily stress that's giving them much better tools that are much better on a daily basis. So I'll think back to some of the revenue that was certain part of the data so when you look more in detail about what's being associated with this and how it's not going to be I thought a lot of stories about where the nationality in the state-based system was in the hybrid system which was a combination of the current, the whole state and the state of the United States and also how much control it works in but the data that is shared with states is certainly that the data that was being used on consideration that is something that is happening in the public in that whole situation I'm doing the project as opposed to the public in the United States but there's many things that are going up states when it's going up states so there's many things that are going to be there's going to be a sense of what people are thinking on what's going to happen for everybody so there's just a little model of use to see in a way this is a specific state where when you weigh it down what are the states that want to use for example here are the nodes that want, here are the servers here are the points that are running on the nodes this is going to be a different type of state where you can talk about what's going to happen where there's different cloud services on the nodes on the security services on the security services you can deal with that basically as an asset there's also a way to look at how it's going to survive as you are there's going to be a lot of stability in that state there's going to be a lot of stability in that state and looking at how those states could help and these ideas here are the better ones you can take out and describe all these points that can be and then which servers are running on which one is going to be on which one is going to be on which one is going to be on which one is going to be on taken down, do you think people are very, very responsible for that? But if they need technology, if they need to be used, do you want to use that? In all of the cloud world, if you just pick up resources, and you pick up money, so if you start with the cost of taking it to the cloud, if you still need to do that, then you put a lot of things to turn it down in order to make that part of the business there. So that's that effort. I think very, very important things to really want to add. And one of the problems with speed, and this is kind of really considerable, is that it's very, very effective. Now, for the notice itself, if you want to be able, but if you look at the larger consideration problem where if you really, really speed up resources, and a lot of these resources are being put by the hour or by the state in general, it's really important to understand that obviously from an audience that got asked who we are, there is a lot of things to worry about. They need to say that we have the convenience system and it's the sole system that controls the network space. And by process or by middle of the year, a service guy will end there and change the switch. The opportunity to manage the system needs to stay an hour away from using that thing so it's for many people. So that's what's going on where it exists by creating a new way to have an action system, it's the sole system that controls the teams and we assume that those resources will get back to the same place. Obviously the emergency is not fixed on service. So it was very interesting to go to that quick end of the project and chat. It's kind of totally different here in that way that's how it works. He said that this is a description that this is my golden space and we want to treat it and we use what we refer to as a full-on system. Rather than what's in my service body and we have a system which is kind of with very good records and controls that we respect and we respect and we respect and we respect and we respect and we respect and we respect and we use things that have no effect on the state. So we use a system called kind of a way to do the system thingy where you get an understanding of the system piece because the algorithm doesn't know about there and the system is building the system on. So it's a way to do that because that's the case with a lot of user problems that having something full of what's in the system and what's in my script that has something to do with that. But some of this may be a better way to do this than if you use one foot. So yeah, what's still made from a similar location control is really something that the service body man and the students can use. And I was only at this time with AI and I had the same AI that turned to me usually. It's not a whole space. Now to give you the set of actions and to give you the set of actions and wave you together and speed and goal. You just need to study goals and things that you want to get to. You know, the latest one I'll talk about is the way AI started to evolve is really that that's a very specific motion of goals that on the previous one was intended. It's not just going to make the system operate the system but one who's yet there so what they ought to do is first talk about not just goals in the end. They can talk about goals, walls, walls, plans to achieve. So they have the most richer kind of simple motion goals that can talk about things that can happen in screens that hold while planning to achieve as well as doing the same thing. So that's not important with the scheme of goals. First picture of the city is not so it's sort of a racist kind of location that we are told. Then you have the next iteration where they are assuming a grand issue of the city. It's just not a goal that's really the last thing that we're about to want to start to do with all those. It's just going to be asking who's really on it. There's one more somebody who would like to ask that question. I'll say that on the time of death though, there's a few emissions but there's also 30 trade-offs between the emissions and the emissions of Europe. So it's going to be asking my goals what do you want to do if you want to say here's a bunch of criteria for this. There's not really an average emissions in my scheme. There's trade-off, trade-off, security, security, building, and so on. So that's another area that's going to depend on the emissions of the whole city. If you look at the whole people, not the citizens, don't think the whole people look at a lot of service until this service is one of the services that you're going to get. And that's the way you're going to do it. So also, if you think there's a big problem at all in how you're going to do it, you also think that that's the way you're going to do it. So I'm going to talk a little bit more about how you're going to do that and how you're going to instead of stress. But most of you may not be found out just because you're doing gas through the gas stress on services, doing the breast services, or whatever you're putting out there, so it's really the ground out of that story. Because you're doing that and the way you translate it from the plan to the two priorities and purposes that you play is the goal of a high level of language and not the sphere of stress. You can do it more in how to read and how to stress. You can do it more in terms of how you're going to do it in terms of how you're going to do it. So the way I'm going to do it in terms of how you're going to do it is when you're doing one of that basically, you're going to get off the main thing or the main thing is you're going to find an option about keeping it down and that's what I'm going to do. So we're going to do that when you're just doing the most accurate feeling, simple to stress and other tasks. So sometimes it's going to be the solution for the single thing that you're actually doing but the other thing is you know what you're doing just going step by step and just the first thing is you do what you need to do and another problem is what do you mean by order and what you're doing is wrong. So the main thing for this is better is that if you want to do this and you want to do this you need to start doing the work to fit. If not, sometimes you want to rest in the row to get the content that's not usable. So if you're trying to restore a single multiple stages by setting and lowering your damage to the proper size and keeping your damage to the correct So it doesn't really matter what you're doing, it's probably going to take some time but it needs to be done. The first thing you need to do is waiting up to the end of the day you decide how to do an operation to keep it stress-free and how do I do it in the state to be a way to monitor that. The first thing you need to do is that you have a consideration of losing your stages and what's happening is you need to change the part of the distributor to restore an ego that says the preference part of the state to keep your damage on one's business. So if you're worried that those things won't fit, that's a very new way of changing the story because it's still the ground about everything that's being done in the economy. In terms of some approach that people are running out of money in the economy, the state will let it restore the reason that it's in the state. Now, if you really look at that character in the state that you're doing it about you're reloading out and you're reloading first, it's not even about the consideration of the state but the memory state. So if you really want to model a state that somehow it's going to say when I'm changing this, how can you that represents a new manner of state when I'm changing it? So the way this is, I think that's kind of where we're going around, here is the might of care of the relationship between the consideration part and the service that they impact and then when we make a decision to configure it we start from not moving on the service. Now I feel it's very, very dangerous. So if you got this idea that if you're going to configure it, you're rather understanding the configuration part of it, it might have a different type of changes to a reload that might have impact on you to be able to construct. So there's a potential to foster a kind of contingency in the new set of components out there. So I gave this point because I'm doing it on the use of the previous package. If you learn that there are some amazing requirements that there are so that you can create it. So the way you can say, I don't think there's a requirement on the service, but I want to show about that. So by the way, this was the first time that we've looked at that, even when we laid out this, the main kind of tool is for example, if you walk down and you have a few recommendations to submit and you would be split out or you would be struggling a lot. Now, the way to describe why they're not really struggling is because you get all of the points that are there. And you don't say, okay, here to be considered, here to be all of the points that you see, there's no path you're struggling for it. The way you want to see that now is basically it's under pre-thought success. You may not even be struggling to know what it is for, but you just really have a much better relationship between these people for which you were struggling, these people for which you were struggling. The going draw, when you think of the people, when you think of the community, you wonder if they follow the plan. They just have a general mode of action. And maybe it's people, it's people, it's people, it's people, it's people, it's people, it's people, it's people are there. You get also constant positions,なんか And then when you reduce the attention of the story, I think it was part of their focus, not about the time to talk about it. But when you see people who perceive this system, they're very good at it, and kind of heard it, heard it naturally, and they see it as an action that the other person can make. So that's not the kind of loss, it's the kind of thinking difference. And then another type of action is where the story is not just giving information about the loss right there, but just covering the losses and not believing in that. They run a couple of these policies, but in the end, I think that it's much better to know what's going on. But when you look at the right now, you see an escape. The only thing that you see is an escape. Eventually, there's no way of thinking that it would happen. They're not asking what's been happening while it's being conceived. Now, in the end, it's really not a good idea to do that. We're going out of the kitchen, we have a road out there, and we're going to have a marriage step and do that. So in some times, what do you think is called a non-proliferation of our societies in terms of that very good focus now? We're going to do that very good. We're going to do that very good. So the answer is really to see it as part of the case, rather than being a city in terms of the urgent role of black loss, you don't know what God's going to solve it. I mean, there's a need to try really to see that. There's been a way of solving the problem that, I mean, the urgent change is an extension out of the period. I'll put it one simple way. We're going to talk to somebody that's been conceived as that and screaming once in a while. We're going to talk about new rules that are kind of solved but one technique that we're doing here is rather than keeping the timing generated on this, we're allowing you to inspect the plan and look at it. Because if you said that, you're going to say, if you like the fact that we need to inspect the next few multiple times that I told you. So we still want to have a more focused focus. So if they do that work for me they may not work. But if they're just going to be actually looking at the timing that they can use to try to solve it. Now they're just trying to go full state but then there's some clues for if there's an actual plan to achieve it. And if there's not a plan to say that that would be needed all or if there's an agreement. And there are ways that we can run that slightly by discriminating where we're using it. Most of it. So we're just waiting to start on the goal for the scheme to do that. So that doesn't matter. You have to start with this down and now we've got something else. You have to avoid that you're out of the system at first. So the scheme, I just want to scheme along the lines. We need a kind of scheme to end that problem. So we're going to have to be kind of curator of the scheme. So we're going to start a scheme plan and that's going to be the end of the problem for as many states as we want. Let's make sure that the law starts on a specific area to do this. Because you know the stages. No one has to deal with different kinds of systems because it's another scheme that we've got. I don't know if I can tell you, but right now I think it's been out there. Because you know that it's a very simple step. Pretty much anybody needs to go to the limits, to the staff. So to live in poverty whether it's the reason why it's good for the very simple things that we need to do, whether it's to see the doctor, whether it's doing anything else that we need to do, we need to step. And that's the problem that we have to be heard for as many as possible. So they some of the terms that are not really clear is this is called viewable growth where rather than feeding around and modifying still has to be out of place and we're going to be placed. But clearly that that can work because not only is it not out of place, but obviously you're actually talking about feeding whether you have all that out of place and feeding. So you have to sort of sort of feed slowly on the mind stuff that's separated from the statehood. So that seems to be a system of feeding out and about. So we have to sort of sort of look at the statehood out of the statehood where we're not going to be placed. So either it's turning itself in if you're interested in what we're doing on the laptop or if you're not still have a situation around it that we need to give where we're in the place where we should be. So if people who look at it are very involved not that I've got a clue or anything that wants to fill out the money but it wants to get in the lab where it wants to know where it needs to end. And not only does it need to give where it needs to end so it's not just as much as we're getting in the family where we've got a stack of networks and stuff like that. But at least we can use what we need to understand. We're not going to be placed in the lab. Well, it's just a theory. How do we understand that if you're going to be in a government doing what you're asked to do or something building probably those who are in the police here do want to handle the area so that when you want to be in an early life so that you'll support want to handle the area. There are systems where that happens to scale. It's a scheme. It's a very fast system but it's not a big problem. There's another way where things can be more important in the environment so that one of those is worse than something. And another scheme is that you have a consideration file that has all the time that you're set. And when you want to be clear about that that's a very focused on those. So we're going to do the work that has to be serious for that. We're going to have the same one with that scheme. The scheme is the scheme that has to go on and work it. So we're going to have the same scheme that has to go on and work and work it out. So we're going to have the same scheme that has to go on and work it out. And we're going to have to do the work that has to go on and work it out. That's a good scheme for the environment. So there's a whole host of examples that have been around for a long time, and I think they've been using that kind of link-off in the backfield as well, but they've faced especially a lot of challenges in mathematics or other things, and we wonder a lot about the focus on today's monocle, which is a challenge. A challenge, though. When you're using a linear unit monocle, it's not in the services, but there's no way to kind of do the service together. It's just something that's truly monocle. It's having to stem that out for you. So on the service, you're able to write an optional code that leaves the cloud that has triggers, and then it turns it into a form of operation, and then it's really tapping on. So the least that's still leading to this, which is the service function, I think it's an actual service system. So you're getting a lot of time to work on the one thing that has to do with the complex of areas, and not just do everything you've got. Service functions, somehow they have to handle that. So we need to be able to speed to make this work and know that it's going to serve it. So the only problem I'll talk about is that each case matters, or if you have another problem, then it's going to want to work. And then there's another problem here. How do they do these kinds of things? How do they do this? But what do we really want to do with this? That's the problem. You have to go through and look at all the parameters that are kind of tied to the set environment and the development. So how do these kind of services, to be honest, we really want to know if it's going to be in a good place and that I'll get into the service. And then there are two series of services that we've got. So those of us having parameters that's known by person, they don't need to be in the service. They just want to know. They just want to know about the parameters. So there are three series of personal services that we've got. This case is very, very, very personal. When it's like networking services, there's not a number of these problems. But then there's actually what we need to have a service that's an effective base for this kind of service problem. I think there are problems. How do these services come up, whether it's the service one, whether it's those and that. So there's a communication problem. Fairly specific to all that service. So we need to know internal services and how to use it. But the way the service is used now, it's called a user method. So it's a very, very, very personal. It's up to you, it's up to you. You can just hit it to order up on your time. And then you're going to use the one series and you can talk to the one series. For some things, you have some information, but now there's really just not too much information. And then as you go, we're probably going to use that one. We're going to share it today. We're going to be using it on the stage. I wonder if we're providing it or not. It's kind of what we were trying to do. And then just, I think the answer is to use the term orchestration. It's depending on who talks to you and what the background is. When you talk to them, it's going to be an interesting kind of business. So each part of the business of orchestration is really important to talk to. Now, it really means that the orchestration is possible. It's really like a business. It's basically about how we understand what we're talking about. I think what we're doing is we're going to set up a kind of acting peer-to-peer and we're going to talk about one of those great albums, orchestration that's really about depending on how you put it. Basically, it's kind of kind of what we're talking about. So, one of the factors that I'm going to go on is how we're doing it. Let's go with that. We're going to start with a third and there's been a lot of huge schedules. The two jobs that I was going to talk about especially when I was a child basically, and they got started in there. It's kind of dead-down what we're going to talk about. We're going to run for the virtualized as well. It's a kind of good-act scale that I'm going to do. It's going to be like a long-term service. It's going to be a regular regular service. So, there's a lot of kind of things to talk about. There's a lot of kind of things to talk about and stick to it. There's a lot of things to talk about or what we've got to do. I think I mentioned that I'm going to start with a new memory and the process of your own real work has to be kind of a good-act. And essentially, you call it the good-act. It's more of a part of the life of the system so it's a very kind of purpose-filled and a scale for the PC and that sort of matches the system in the department. It's a tough and a tough and a really more community approach. I don't think it's this kind of argument or something. I think it's the kind of things that are used in the system, which is just an example. And so, we're 2015, we're kind of getting into the state, and Dr. is kind of reading about what the plan is and learning from what the system knows, as well as matters. So, are we arguing? Will we do that? That's part of the question. We're not arguing. But you're not going to hear about that. You already know about it. You already know about it. So, you can know those issues that are very important. But how do you think this is going to be? You already said that we're not arguing. You are arguing. So, we're following out a lot. But hey, if you can think of another one, you can see, as I understand, things are really important to other players. I can solve any of them. Do you agree? So, you see, the two ways of perspective depends on what you say, if you're still there, I just don't think you're there. So, that kind of gives you an insight into ways that are really important to other players. So, you understand it. You just consider what ideas are very important. And then, you turn it off to our panel. Which kind of name are those these vendors? Which is the part that makes you act in other parts of the state of the city? Instead of wondering about the system, So, I'm just trying to get a little bit of information on the steps and stages to see if all of you are going to have two days or two months right now, if you're going to be in a working community you're going to have to do about three days. So, we're about a hour, and then we will pull back and we're going to do this, or four or another. We have one more talk. It's kind of just a little bit for you to all know. Kind of talk a little bit about the way that you know what you're doing. So, it's probably going to be like, just sign up for the lab. We're going to have two days and then three. And then, basically, we're going to do it. We're going to have a lab with all of the others. You want to do your working lab on it. And then, you're going to have to do that. You're going to have to come back. All you need to do in the sense that you're going to do the lab and all of the other things that you need to do is you're going to go back to your program and do the other things that you want to do. So, yeah, we're going to have to do things that you need to come up with. So, we're going to do this. Just install this. Yeah. You hear that from the beginning? This is the beginning of that. The recording problem, what do you do? The topic, the topic personates me. I'm talking about spectral, which is a workable base registration later on soon. It's going by if you're interested. Yeah, yeah, sure. Yeah, no, no, let's just do that. Yeah, that's in the combination. And I remember, I think you were here at 12, at the skill 12. Oh, yeah. And I remember you both, and you were demonstrating the open skill. Yeah. I still remember that. I connected the dots. Yes. So it's very interesting topic and you definitely can't see that very integrally because people always ask me what is the clarity for a subversive approach, and I have my own answers being mostly focused on that work-blown interaction. Yeah, I think you're saying, you know, I think the hybrid emigrant approach and constant stuff like that is what it is for. I think there's room for the involvement, where the tools are going to work. They're getting better and better. Yeah. What's the point that you come in and talk to me? What's the point that you don't really want to talk to me? Do you seem to go through this kind of state-building problem? At this, at not at the beginning of the state-based problems. You know, I came, the thing I clearly remember is when I began to talk about the network type of infrastructure and the need to discover the inventory and the relations and how you actually discover the state, there was something in between because I've settled myself. Oh, sorry about that. Once you have the recording, I'll just go with the recording, maybe we'll hang around and chat about the topic. You compensate me for coming back. No, it's okay, great. All right, I'm going to meet you by the way. Oh, yeah, too. I do. Yeah, it's kind of... Do you have a very connected problem? That's another fashion of mine, actually. Proposed talk for... Now we'll move. We actually... We were in Palo Alto University, so we got acquired by Breakgate, and they moved us to the main quarter. Which is where? That's... To 27 and 1st Street. Oh, okay, okay. That's not a problem. Not a problem. But yeah, the server list is not a thing, so I'm actually... We're running a... A site project. With Biofine, and we found a really interesting application to the server list, which is in genomic applications. Okay. What makes that interesting is extremely elastic loads. You know, because without the scale, they may run for a normal hardware for a week. And of course, there are five machines for a day and a month, but then sometimes there is no one, and there are some time, you know, it's 80 people. So, this is the extremely spiked workflow to run, and another part is the... Bringing on code there is the only way to solve the problem, because most of the elements of the computational pipeline are written by different developers who are actually scientific developers. And working with these guys is like, you don't try to code like that, do you? You do. So, embedding on at least two out of, say, hundred steps to work on the same machine as them. You know what I mean? So, you're getting them to rewrite their stuff? No, we pack them into containers. Okay, I got that. And then, you know, this is why the server list is you pack them into containers, they are batch jobs. So, the functions... Yeah, yeah, that's it. The functions, the package, when them out and do them, and we actually... If I begin to build the type of the framework around the server list, that's coming out really interesting, I don't see that as a framework, it is more of a problem to solve that. I presented that recently on Docher with Apalada. But, you know, the server list is... There's a long way of saying, I'm totally fascinated with the server list right now, but it takes time which we build. Well, what we're going to do is... You're doing a level there, right? So, the fission stuff that you're doing around with fission, that's where we're spinning off. Fission? Yeah, that's the thing where they take Kubernetes and where the GUI's... The GUI's... It just looks like any function of service where the GUI's... I think that's what you're saying, they spin up on the thermal containers so the energy in the environment can spin it up on the thermal containers. Right, right. Fission is a framework for... It's open source project in 5.9 for companies here. That's, I think, the project for companies here. Oh, plus from 9, I know it's 4. Okay, yeah. Yeah, actually, I actually worked pretty close with Fondor Fondor, I didn't know that they're here. So, fission is there, some real framework. Let's do that, yeah. Kubernetes has this job concept that we use and I was building this stuff on Swarm and Swarm didn't have the job, so we had to actually build that. But the interesting thing is I looked at OpenWISC Oh, yeah. I looked at it carefully quite a lot and the reason is, again, we were doing this text from a similar way because when you begin to look at what OpenWISC actually does, there are the triggers, there are the rules, here are the events and I'm like, look, what? It's just... You compare that in our market, the market is one-to-one. Maybe there is just so many different ways of skinning the cat. But, you know, I think it's time to use that because of maturity, because it's kind of two years, more probably much bigger than this. And, of course, the biofragments. That's a familiar tool, but I think it has all the details, it has the workflow. And for some of the serverless architectures, the interesting thing I see is they have, you know, turning the sheet to answer on how do the the shoulders stick together. Have you seen the Amazon step functions? Have you looked at that? Did it come out? Oh, no, it didn't. You had a problem there in talking about this, it sounded like a configuration problem, but it's more, it's just like if you have a function and then have to give results, but the workflow problem, if you have a workflow, if you do a task and you have parameters, you have to make that. That's right, that's right. So, on Amazon, about a month ago, had something called step functions which facilitates, as you describe it, something like client-based machines, facilities. Oh, that's interesting. Yeah, yeah, and so you don't have to have anything, I think it's... I'll need to check it out. Yeah, and I don't think there's queues, so I think the thing that does the job, you don't have to put a queue in between so you could have a lambda, you know, it's like, you know, data flow function program and so on. And what we did at Stepstorm at some point, we had the concept rules and rules, you know, like something triggers and then you connect that to an action, and then the action completion being a trigger by itself, you can change these things very interestingly, and we've just a bunch of rules, but we keep the wall pretty soon with that. Yeah, and the wall is that type of thing, well, technically, it's the right way to do an implementation plane, that's probably all you need. At the operation plane, this is a nightmare. Oh, yeah. So we built queue, we built the deployment pipeline to build Stepstorm itself, to follow these things and look at that, and they thought, no one can possibly understand that, like, if it breaks, we'll never find it. It won't break So with all of undridden stuff, it is very, again, it's intrinsically difficult to reason about this system. Yeah, that's the point around, when I was in AI, I mean, they had, you know, rule-based systems, how the rule-based system is the interaction between the rules, so, yeah, you have all these rules, you have cycles and stuff like that. Yeah. I think, to me, I think the approach, ultimately, is, you know, I might back on point around very kind of transactional, direct sort of system, but what you do is you have a description that is kind of, is very, you know, you know, it's going to do a very kind of predictable description like that, but you can compile it. Yeah. So if you get the description, you hate it, so you kind of know, well, I guess it goes long if you hard to do it well, but it's, you know, it's like, Carol, you know, when I wrote big Carol programming, it was such a scare, it was like, you know, this one works for this one, how you do this one. So I think there's some things that kind of a code generation are a little bit more sure. Right. Right. And even, you know, G2K is, I remember for like, for years ago, like what I remember there is, it was similar to what you're talking today about the hybrid approach, where you have the goal, but then there is a, like how you achieve this goal. And another thing is, you know, basically, you're doing some pre-runs or doing some, you know. We didn't do that. I mean, there's a bit, there's a bit of data between doing pre-runs. And I remember the chef got on the Adam and the chef, he was always, it was a real killer poster. He said, he gave you a false positive. There's a lot of times, you're usually supposed to install a path that you start to service. You know, you can't do a... Yeah, yeah, yeah, yeah. Yeah, so... In configuration management, you're right. In the, in the goal-based system, which generates work for, please probably, you know, I didn't think about that. It's just the impression from the chalk, but if you say the hybrid approach, main flight, generating the execution plan based on the goal, and then, like, there is something, like, I really want to hear more about how it might be when you have the hybrid systems who use the goals and the kind of work flows that we go through. So we did, we think you can't work on stuff. So what we do is you, if you don't give the work flow, you generate it, and you give the work flow if you want to, which should be feasible. And the more leaving, and then there's then you could actually, it kind of sees it for you sort of the work flow and you could tweak it for a lot of times together. And it only generates action steps, steps to make change, and then we'll put it in, like, smoke test and things like that, look at better concurrency. Because it's very hard to automatically plan that, you know, has, you know, something similar to be by hand that is much more efficient. And extra steps and other things. But how do you then, like, ensure a reason about the fact that the manually created plan achieves the declared goal? Well, I think the only way to do it is actually by, um, like, catching. So, you know, it's kind of something that you're able to catch. It's kind of more empty. Please also, too, you don't care if any of the pieces can kind of be... I mean, I didn't catch it the higher level. So how about the cluster? You know, I want to make sure there's a lot of pieces of it. You could have nukedayers, slaves, but I won't test it as a real assistant. You know, it's not an accessibility system, but you could have a response on it and think that that would be awesome. So, really, really, there's audience systems you think that they would default on, I'm not saying I've had it out past, but the systems succeed. It looks like the plan to succeed is if the services are enough. Uh-huh. Uh-huh. Uh-huh. It's like, I've heard stories from the silent buyers and the person who orders doesn't have any ever closed or doesn't get it out and things like that. Uh-huh. And then you declare and to test themselves. Do you kind of think you prefer to do them in the workflow type or the script type or the ways that they kind of bolt them to the end of the execution end? You know, so we have a notion on this kind of the eye to make things gather information and to test the answers. So it's it's it's not even the most separation. It is more the traditional so the action just like in configuration management and the typical pattern is check it but it's there makes it so and check it but it's there. And the same here is just at the higher level. We can't automatically generate so while we first started on automated some of the information persons had that would get used to generate a lot of missed attendance so a lot of times when you write these things now they're always right to work with the other thing is the other thing more is what we're doing is that the workflow as we do is it's we're doing something that's equivalent to the vantage of the program so we don't have methods in the same object you don't have to specifically pass attributes so what we do is where we pass stuff is we have the third description that says what attributes are and we pre-see them but when you want actions that they have results they just set it on that object and then we pick it up where we don't have to have a syntax where we work well we say the minutiae actually it's kind of the most focused thing right now so we first we're working with people in our last country so we're kind of focused on let's do this let's do a system of a service building so rather than provisioning and thinking about the base and the nodes it's a overall system that we support is a lot of times I want to think about an affecting environment or another environment and what I bind to is so when we're doing support with one surface last year I want to set it up and I want to set up teams that are restricted teams so we we need deploy teams which one of the things requires deployment of the environment deployment of the system deployment I mean everything you're deploying you know VPC your deployment is about to come here so that's the thing we're even focusing on is deploy through the backbone contact so when we're doing like to the madness or something like that we want you provision of a separate layer for the separate the the the the the old school kids how do you do it right now I saw that like I just took a look right now I saw that you started working on that Yeah so when you start to say you've been kind of working on this for a while kind of alter the ones with the product companies Yes So right now you guys are kind of finding the cutouts we decided to just go on so we decided to Right now, we have a really commodity product and we've been working on for about four years. So what we're trying to do right now is get the minimum traction for angel companies right now. So what we're trying to do, we took a set of technology and then we got there, and we discussed things that we thought would come with it. It's just the two of us that got a good amount of traction, so we think that if we could get some minimal traction, and we could get some good reference, people don't have to pay for it. We could go to the venture guys and get a call. So we decided we're trying to step with the venture so we didn't have to go to the venture. So it's going to be tough. I mean, we just went through that. The venture product right now is very uneasy for the whole developed space. And for smaller tools, to put it this way, each daughter cannot figure out how to make money. What are our chances? If you're mine, I'd be like, I was thinking recently, some friends approached me. We actually, we had to, we were forced to sell. And we started about the same time that you guys started. We started about the same time. We got the venture money. And then we couldn't raise another round. And we sold. But we're happy that we did. Because we actually wanted to go for it. There was a lot of traction. There are diffusers, preference accounts, like everything's good. And the problem is there is no good business model for the tools like that. You know, shortly people don't pay for the tools, but the worst part is you see figure that out. Okay. Yeah, what are you trying to, I mean, that's what we have to work on. I'm looking at the China, I mean, I think we're at the stage right now where, we're kind of being dysfunctional. So first get the traction. You always have a fall back. You get the soldier in your car. You just want to get the, I love to talk to them when they get closer. So, you know, it's kind of different. Swimming by, let's kind of, if you were in Palo Alto, you know, give me a call. We'll grab a coffee. And I'll introduce you to a couple of guys. Please, you know, there are a couple of folks in the VC community who know the space and the very, you know, the least thing they can do for you is to, you know, just give you the first hint of what do they think where the space is. Because at some point you had a couple of, you know, friends, I mean, who they've developed and didn't know anyone when they started, but developed at some point and we just have the guy where we come to him and like, what do you really think? You know, this place is so cloudy right now. Fun and tender. That I cannot figure out this and I really know this place. Actually, he still is the guy who had used the test lag and MegaCloud was one of his methods and he was falling open and he said look, the dust hasn't settled in all the developed schools and it is very risky at this point and if I cannot understand this thing, I think that's the first to shine away from the, well, so it's very easy. You know, if you wonder if the VC community, they have a VC manager and a VC manager and they're getting more and more involved and we're kind of using them but yeah, we haven't had to worry before business and so, you know, it's still pretty good but it's amazing that you guys are running by the consultancy and staying on top of all recent things and the state orchestration, your spot on what's your name again? Thank you. Yeah, it's more than enough there. All right, we're talking to you again. Yeah. All the best. Thank you very much. It's been a while and it's not being too interesting to just be here but yeah, no, again, they're all very important. All right. Check, check, one, two. Yeah. Test one, two. Yeah. Yeah, the plane was laid and the cone thought you were in Kansas City when we called it Hoover. Yeah, I can't see. There you go. Oh, thank you. This is my first time here. So today, we're on our community track so there will be time for after, I don't know, the pocket for like three years is community and I'm very, very accountable to any member and you can't she's going to give a talk called to contribute to your own destiny and without further ado your Zamburgrenner. One of the main topics of our conversation was this light that makes me who are we? I already introduced myself and Carl. I'm the system administrator at Microsoft AI. I also do a lot of interaction with other things. We all kind of wear a lot of hats. Yeah, it's not going I don't know. Here we go. We got the mic working. So it's actually without fear to contribute sometimes if you went to do something but you stop because this particular community, I think probably how many of you guys are focused on software I'm in the hardware space now so I just I kind of like want to see who's in that space too. When I first started in the open source community my biggest fear and it felt like I was having to leap to hall buildings was that open and collaborative participation. It was kind of scary knowing that everything that I said would live in perpetuity and somewhere people are writing down my quotes the people aren't in here it was kind of getting involved with it and realizing that not because I googled it I experienced it so it was a little scary getting involved with these groups I recognize some of your faces but I'll go over some just to let you know who who the strange started with the news letter and became the editor-in-chief at around issue 176 or so I jumped in for my own personal journey laid on a drop and the 80s were up to go from a decorated combat and so to go and drop somebody into into somewhere this blue-gray combination and so Linnick was very his work that we see today the thing that maybe some of you don't know and sits on their board around all this my husband was a number back then but that's how and he always wanted to be part of it it seemed like every time my husband got out of town and I had to pull out my or I had to pull out my windows to use Linnick's I was so frustrated with the collaborative part of I don't think y'all want to hear anymore this is moved over to Canonical and so Drepid CD they were going to play it they had to apologize for being late he gives me that laptop and he says I have to how to install it I was up and running I had my blog set up and I was talking about my experience with this new thing that I was experienced called a boon 2 now I wasn't a very good writer or blogger at that time that's why you don't see the link to the early blogs but it was like my adventures in a bun 2 part 1 my adventures in a bun 2 part 2 part 3 part 57 finally there's a community member and I was tweeting it and it was Zonker, Joe Brockmire he sends me this tweet that says could you be a little bit more original with your titles so this was a public conversation well what do you mean can you title it so I know what you're talking about besides a bun 2 so I got coaching from all different places sometimes coaching comes in the form that's a little bit raw a little bit more raw than we like it you know again it's this open collaboration right and so I didn't get offended because I'm sure somebody else was blogging who was writing just as boring of titles as I was and somebody needed to say oh wait a minute let me not use that word your stuff is boring and you need to you know spruce it up a bit and so I got coaching from everybody and anybody because they knew I was new sometimes that's a good thing for you ladies who have ever had a baby how many times did people give you unsolicited advice about your pregnancy or how to raise your kid or you know that's kind of what it was like and I was just yeah okay great but that's what started it sometimes all it takes is one action each of you sitting in the audience today you don't know what your one action with somebody else is going to be that's going to motivate them to go on to write books to go on to lead communities to go on to coach people to go on to design new ways and new community models and so you just don't know or you don't know who that one person is going to be to you who's going to light that little bit of a spark that's going to get you to be that person and so don't be afraid to jump in the Olympic size pool my very first like big event all by myself was Oscon so the very first community leadership summit I go helped John with that and then there's Oscon I had no idea what I was getting into it was like the Olympic size pool of just like open and I loved it I drowned a little bit had to tread some water but eventually I breathed but think about where you started think about what that one moment in time was that got you started some of you would say I don't remember but I think if you think hard enough and remember what that was what hooked you some of you're going to say well I had to learn it for work others will say well I was trying to find a more inexpensive way you know to to do something some of you will say I had a scratch I had a itch I needed to scratch it so I figured out how to do that all of those are good answers but there was that one thing that got you involved in open source for me it was watching my husband and all the cool stuff he did but I didn't want to go through all the frustration so I just waited a little while that's the one with that either so I always tell people if you're afraid to make a decision you always fear the decision you make so just think about that for a second if you're always standing there and you're like I don't know what to do I don't know which way to go somebody tell me what I should do once you make that decision you're going to wonder did you make the right decision you're always going to wonder don't let this thing called fear paralyzes everybody at some point in time it's paralyzed me at different points in time but the minute you know the minute you let it then you just you're sitting out you're sitting on the sidelines you're not participating and getting the most out of it so in these communities that we have don't be afraid just to walk in don't wait for somebody to invite you to the party this is open so no matter what what project what community you want to be involved with if you're excited about it just go do it don't stand on the sideline and say gosh should I wait for somebody to send me an invite man if I was waiting for an invite I'd still be waiting you know I would have done half the stuff I've been doing because I would have been sitting in the corner going I'm going to be polite until somebody asks me don't be polite there's time and place for being polite but not always like walk into a room and say hi to people you know nothing wrong with that say I want to learn from you I did I walked up to all kinds of people like CEOs to companies when I was in this world going you're doing something I want to do you're here I'm here you got 10 minutes can you mentor me for 10 minutes and some of the coolest friends I have today are the people I just barged into interrupted their conversations or said hey I want you to mentor me now some said no I don't know why but some said no but others were like yeah I can't do it today but here's my number here's my here's my email like let's get in touch and let's you know talk about this so every year I pick a different mentor somebody that's going to get me out of my comfort zone that's so their personality is so far removed from mine maybe there's some of this introverted and I'm extremely extroverted so we're opposite ends or maybe somebody is the suit and tie type and they're always like really proper which is again miles from me and I'll ask them to be my mentor because I want to learn from them there's always somebody who is going to be smarter than you there's always going to be somebody who knows more than you and people who don't realize that are those technically arrogant people that you don't want to be around anyway so don't worry about being afraid to do something just go do it so this isn't the clearest graphic but it's one of my favorites that I've created over the years and so this is how it started so when you think about a community and you think about all the things that you want to do you know in a community it's like trying to carry all the sheep because you want to do it all like once you get into a community and you want to be part of it it's like oh I want to be part of that well I tried this I didn't just my first year and a half in I didn't just like get into the Ubuntu and the false communities you're going to see everything that I did in a couple more slides and you're going to go like failure so why do I like community why do I absolutely love communities not just open source communities but just communities in general so I was in Nashville the other week I was talking to this new artist and I'm like your website looks like every other new artist in Nashville it's first name, last name, music at gmail.com first name, last name, music Twitter first name, last name, whatever everybody was this cookie cutter mold and I said let me tell you about open communities let me tell you about open source let me tell you how we do things on this side of the street and he went wow I said now how would you feel about doing your music that way so he says to me you know I've got gigs until Monday I can't really talk to you until Monday but what's your email address so he emails me and he said I want to know more about this so I'm going back to Nashville in two weeks all because I wasn't afraid to walk up to here's this person on stage they take a break I like their music I want to see them do more than what they even thought they could do so I go tell them what they're doing wrong I wouldn't suggest that all the time but I was kind of nice about it and I had bourbon in my hand too so I was trying to be here but you know you kind of know your audience right you got to know your audience and who you're talking to and so had I been afraid to go and approach that I might not now have the opportunity to have a consulting gig you know so I'm all about building a community around this guy's music because isn't that what it is really when you follow an artist it's a community of people who like that particular artist it's a community of people who are like-minded isn't that what we all are today we're a like-minded community we might have different nuances but aren't we all about the open and transparent collaboration with one another in order to advance an ecosystem and drive the adoption of the open principles and philosophies whether it's around software, whether it's around hardware whether it's around law, education you know it keeps going right all of these principles and philosophies that we love so dearly can be applied to every part of life like my boss often tells me you just put everything out there really is there any part of your life that you don't talk about no because I feel like that if I'm talking about how much I love the conversation I tell you what everybody in here has a story and I've got hundreds of interviews out there because I love interviewing people I love seeing how people got to where they are today because everybody sitting in this room has a very unique story and if you were willing and brave enough to tell your story you could motivate and inspire someone else to do just what you're doing or maybe do it just a little different have a derivative of what you're doing and so we have these communities around everything think about it people who like I don't know like a particular model of car there's a whole community around that people talk about that people who like particular people who like California so people who like particular strands of marijuana they all get together I tell you I had a group of people they wanted to open speaking of openness they had this vape pen for THC and they wanted to open the plans of course my board said no that's too far removed from the data center we can't really do that under our foundation so I found them another foundation but the thing is it's all about the conversation right had they not had the conversation with me I couldn't have connected them with someone else so it's all about building the community commenting on things the collaboration the contribution what people don't realize sometimes is that thought leadership that you provide that conversation that you have that comment that you give that bug that you file that's all contributing and anybody who tells you that it's not ignore them because your time is important your time your ability your ability to learn your ability to share your ability to tell people what you know what you don't know that is all collaboration that's all contribution and so if you like I started out telling people how come this doesn't work or how come like some of the first like I didn't know that these were me being a user reporting back to the developers and I had developers going Amber why would you think it was supposed to work that way I'm like well because I didn't write it I don't know what it's supposed to do because I have experience with all this other software and stuff that I use I figured it was going to do the same thing and your stuff is broken and I learned how to nicely tell people their stuff was broken I wasn't so nice in the beginning but they taught me but it's all about the conversation the community the commenting the collaboration the contribution piece of it are what keep me involved with people I love it and to be involved in a project you have to love those things too and every one of us I don't care if you can't write code you have something valuable to give to each of these projects don't let anybody tell you that you don't because you do because when's the last time you saw somebody who was really good at writing code could write a grant proposal could get you the funding that you needed could talk to the people that write the checks in such a way that they want to write the checks for your organization you got to have somebody that understands the technology enough to speak translated to somebody else's language so it doesn't matter if you don't write the code somebody's got to be the one doing the documentation somebody's got to be the one explaining it to the world because sometimes even the people that write the documentation you don't want them standing up here either if you want people who are going to engage everybody get them interested make them walk out of the room and say I want to know more I want to get involved or they say I am so confused I have to go to the website so you either confuse the heck out of them or they got to go to the website and look or you excite them so much that they don't even know what you're talking about but they want to be involved I left one talk one time and had this guy come up to me and go he goes I don't know anything about this but you're so excited about it how do I get involved I am like this is awesome so I mean it's when you see somebody so excited and they believe in something so much that makes other people want to get excited too I mean we all see some stuff and we go no not really but this is really cool everything that we do remove the code from it remove the distribution from it remove all of that it boils down to you are connecting with people who think the same way you do are excited about the same things you are why not just go up and talk to them why not say hi to them why not go how did you get here everybody has a story and sometimes that story is what brings everybody out and you get really cool ideas because sometimes maybe somebody over here is working on something that somebody else over here is working on something similar they are both having problems but if nobody talks to one another and connects the dots they are going to stay siloed off and chances are they are going to have two independent projects that won't be as effective or efficient as it could be if somebody had just connected the dots and brought them together and that takes a conversation that takes people in a community that takes people collaborating commenting on what is going on and eventually contributing it because it does no good it does no good for somebody to apply the principles and philosophies of open source and then just keep it to themselves I told a I told a I can't tell the name but I told this company a couple weeks ago that their open source project might as well be proprietary because when you hold it hostage and you don't let people see the code but you say it is open source I have to call BS on that and I did and I think that I don't think there is anything wrong when making money I don't think there is anything wrong when making money on open source projects but be careful what you call it be sincere in what you call it and so I think that if I hadn't been around the community and been around through the history of it and seeing what was happening I wouldn't have the confidence to do those kind of things but you learn nobody is born with this information there is not a single person in here that was born with the knowledge of how to write code or understand the Linux distribution or understand what open and transparent collaboration is we all learned we all learned from one another so just like we had to learn we learned and so we need to be the ones to teach them we need to be the ones to teach them not to be afraid to go out and do great things and the open source community sets everybody up believe it or not to go forth and do great things if you just extend yourself just a little bit get out of your comfort zone you will be surprised what will happen so these open source communities aren't ladders but I don't want someone telling me you got to go do step one you got to do step two, you got to do step three and then when you complete all the steps then you can come over here and do this stuff most open source companies are like a lattice you just pick a point and you move around anywhere you want to go you know you start at one point then you go somewhere else and go oh maybe I don't like that maybe I'll go try this over here there is nothing wrong with that you know I don't know about you but if I have to somebody tells me that in order to be part of a community then I have to jump through these hoops and I have to go do all this stuff before I can even like see the playbook or figure out where the wiki pages are or you know see who I can talk to I don't want to do that I want to go explore I want to see where I want to be I want to see all the projects that are there and then I want to make my decision and so if you think about it two people can start at the same point and end up in complete opposites on the same project which is cool and that's one of the things that I really like about all these communities that you see here today that you all represent today if you think about how your community is it's not a ladder anybody in here think their community is a ladder approach oh thank goodness the ladder approach is much more friendlier it's much more you know inclusive you know it's not this exclusive thing where they give you this prescription that you have to do and if you don't make it if you don't do all of that and follow it to the exact T then you can't be part of the cool kids club I think everyone in here is part of the cool kids club and that's because we get to choose where we want to go you choose your own destiny when you're an open source you get to decide every day which page you want to turn I'm telling my age now but you know you get to decide where you want to go in this nobody gets to tell you where you have to where your hobbies have to be or even at work nobody's going to tell you how to write the code to make something do something they're going to say go make this work and it's up to you to do that if somebody is sitting over your shoulder just hand them the keyboard that's just me I might have lost a job or two here you take the keyboard but think about what type of organization you want to be part of and then if your organization isn't like that help your organization become that I know you've seen this I kind of modified it a little bit because my comfort zone was way down there on a drop zone on the ground and I decided that I'd be up there get out of my comfort zone so I started skydiving and it's actually the coolest thing in the world but to me that's where the magic happens you talk about getting way far out of your comfort zone jumping out of a plane at about 14,000 15,000 feet that's a at first it's a little bit out of your comfort zone but that's kind of like joining an open source community for the first time too because it's so open and transparent for everybody you might as well be jumping out of a plane that sinking feeling oh my goodness what if my boss sees my typos on the mailing list what if my new boss that I'm interviewing sees my old code they don't care they care about who you are in that moment don't borrow trouble you can actually go back and show them the other stuff and go look how much I've improved you're getting the improved me ask a marketing person they will help you out all day long on how to spend that story but this is just to illustrate you have to get out of your comfort zone you can't just sit in the corner and watch the world go by you can't be afraid to get out of your comfort zone if I was afraid to get out of my comfort zone I would have never you know been in the air like that I would have never been in open source communities writing books and all that kind of stuff so let's talk about individual success when you think about it it's you know the endurance the hard work the dreams, the enthusiasm, your faith depending on if you're a faithful person your goals it's hard work, it's tenacity it's hope, it's courage, right it's a lot of effort think about all the personal successes that you've had all of those things were there all the things you see in the white boxes you probably experienced every one of those but you probably also had fears you had to overcome obstacles you had pain, you had doubt there were failures, there were limitations you made mistakes it was difficult at times but at the end of it all and all that mixture you had individual success but if you were afraid to get out there and do that if you were afraid to go through the pain to work through the doubt if you're afraid to overcome the fears right? so you can't let fear stop you you've got to power through it I can't I was talking to someone a couple weeks ago and I said you're so smart and you're so talented amazing talented engineer electrical engineer and he was like yeah but what if the project fails so what? so what? if it fails we're going to tell the world about it if somebody's not going to join in and going to fix this I said do you think Edison got the light bulb right the first time? nope so you know everybody has this moment of doubt but we power through it right? and so what is leadership? so I love leading things I absolutely I love it but what that means is you've got a coach you've got to be the example and you've got to teach people and you've got to share a vision I don't always know that I inspire people but I try to every day even if it's just inspiring myself to do more things but I hope I inspire others mentor people and build a team around everything that's what the leadership success looks like leaders do those things and I've been fortunate enough to be a leader in the community in many communities and so take away if you're good at those things lead nobody has to ignite you with the leadership position and say oh you're in charge and by the way if you have to tell people you're in charge I hate to break it to you you're not in charge how many of you guys have seen people that walk or you have seen people that walk around going I'm in charge but really it's the manager around the corner because they're the one that has a clue it's not the guy standing up front telling everybody they're in charge so people will listen to them it's the ones that people will listen to without having to be told to listen to don't be afraid to be that back leader don't be afraid to in a lot of communities there's this person that the community votes in or somehow they get voted in but they're really not a good leader they might be a good boss but if you are good at these things just do those things you don't have to have somebody give you permission to go mentor somebody or coach somebody or build a good team or help inspire people or share a vision like don't wait on somebody to tell you to do that just go do it and so there's three things here there's like the art of community the official bunty book and how many of you guys have seen the draft copy the open source way I don't even think it ever got finished so each of these has a unique thing that I learned from them but I think the one that stands out the most and maybe if you google the open source way the book Karsten Wade introduced that to me those of you who know Karsten but there's a section in here that talks about failing and it says when you fail take notes you know and share those notes and so if you can find that online it never was completed but it's actually a really good read if you get a chance to do that those are three books that I would say like if you're not interested in new bunty of course don't read a bunty book but art of community and the open source way there's a whole website now that's the open source way but that's sort of what started it and kicked it all off so I think that's around 2009 if you can find it but take notes just because you fail who cares just dust yourself off keep going I would always tell people what I failed at sometimes I got laughed at sometimes people were like oh well that shouldn't have happened and then we would work through it and figure out why it broke so talk about epic failures so if I'd let this failure right here keep me out of the sky I wouldn't be skydiving today I went through a tree line and I broke my hand but I broke my hand on a Sunday on Tuesday I had surgery the pins put in on Wednesday I was on a plane and on Thursday I gave a talk at a DCD event so had I let that stop me one from skydiving and two kept me at home I wouldn't have given a talk and then from that talk went on to do other things so it's okay to have epic failures it's you know metaphorically we break bones sometimes right we might break our computers we might accidentally erase very important code we might accidentally introduce a bug we might whatever but just brush it off go fix it keep going so remember when I told you I did a lot more that first year than just get involved in a community so those are some of the things I did the local leadership series I was a bunch of member I was a bunch of member I think six months after I joined and then within nine months I was on the community council so and then I was working with the US teams I was doing a bunch of weekly news I was I helped organize the first one of these Ubu Khans I was I led the a bunch of women project for a while as the North Carolina local team I went to UDS Dallas I was helping with full circle magazine so that's some of the things I was doing that first year here's a few more so I was going to Linux I was writing for you in Ubuntu I was doing false events I was doing book reviews I had my personal blog I was blogging on and then I was again doing a bunch of user magazine so but that's not all I did that first like twelve to eighteen months I also did behind the fence I did video interviews but all I did all the video interviews from I think for four years I did all of them so they're all online but I did a bunch of women series meet the platform team I did people personalities and planners now would I tell anybody to do all of that in one year no I was just a little fanatical about it I was so excited again I wanted everything talk about an epic failure what that did was set me up for a huge case of burnout that I totally ignored don't ignore that don't take on so much that you just wear yourself down because I did and it was like it was a very sad moment I don't know any of you all have experienced burnout but that was an epic failure while I was successful at all of these things and doing these things and getting excited it took a personal toll on me and I had to step away for a while to get healthy again so pay attention to what people are telling you pay attention when people are telling you it's a marathon not a sprint you know I didn't listen like whatever matter of fact I have a whole talk about this piece of it that's called a volunteer vertigo and high-tech hangovers all about burnout and how to avoid it it's like don't do everything that I did don't take on so much like make sure you're always finding that work-life balance you know there's times like our year will be it'll ebb and flow right like there will be times we'll have crunch time we're busy and we're busy and we're busy but always balance that out somewhere down the line with you know some quiet time some some you time you know go digitally dark for a couple days all those kind of things but what I'm here to tell you is just because you don't write code doesn't mean you can't be successful that's in a year at the end of the year that's a lot of stuff that I was doing I didn't know the first thing about any of that when I started I just started talking to people I just started identifying gaps and going I bet I could learn how to do that I bet I could learn how to do that any of you can identify gaps learn how to do it no fear don't let fear paralyze you if I'd let fear paralyze me I wouldn't have done any of those things I wouldn't have hundreds of video interviews out there you know with really cool people in the community so again just some this is just some of the stuff you know like technical reviewer the bunty book you know helped architect the lanara community architect of the bunty community I mean not the bunty community OCP community of hundreds of interviews out there the thing is though like had I not been involved with all of this other stuff throughout the years my OCP community wouldn't be this incredible cool model that we have we have a completely different model than any other foundation out there and here's one those of you have been around for a while you'll probably recognize where I got the things that I didn't want my community to have I didn't want my community to have a benevolent dictator I didn't want my community to be this consensus community where everybody had to agree or you couldn't go forward I didn't want the community I didn't want there to be anybody be able to buy leadership positions and I didn't want any one company to ever take over my community because when that happens it gets a little misguided right like it's if people have deep pockets imagine the organization have deep pockets and they can throw money at everything but they're not going to put the time in they're not going to put the skin in the game to do the right thing or people who can put tons of people on something to advance their agenda but maybe their agenda isn't really good for the overall ecosystem you have to have that balance and so over the years I watched as projects succeeded and failed and where the frustration points were and so I wanted to make sure that that our community we took all of that into account and so we've done now on that side now would have never been able to do this had I not started so long ago and gotten involved with all these other things and talked to people to figure out how they did everything and so now we have this model that's merit based so anybody could come and join our mailing list anybody could come and see the specs and designs you don't have to be a member to see any of that you don't have to be a member to come to any of our events all of that is open to the public now if you want to contribute something or if you want the benefits of membership you've got to you've got to you've got to be a member but more merit that you have the less money you pay so in our community we have community silver, gold and platinum platinum being our highest tier that's the least amount of money somebody has to write a check for because it requires the most amount of merit so the more hours and the more IP you have the less money that you have to pay so that came from the experience of being around everybody you know in all these projects over the years and so don't discount the failures don't discount the difficulties don't discount the things that didn't work out that you've experienced because that's all layering to other great things that you can go and do and now we have this amazing hardware community where we've written licenses now so we have a hardware license that was based on the merits of the Apache license and we have a hardware license that's based on the merit of GPLV2 so we've written those to help you know to help drive the open hardware piece of it we now have folks like Microsoft and Rackspace who are putting their designs in GitHub to do collaboration with hardware designs just like you do with software and putting it out early but none of that would have been possible had I not learned from all of you all of the projects that are here and so it's interesting to you know see what you can learn and then go apply it in a different way you know and if I listen to everybody who said we've never done it that way before we still wouldn't be doing it this way you know and so don't there's time and place for everything and so don't be afraid to say you know what I think we should do this a different way you know don't be afraid to look at something and go we've done this long enough let's try this other way and sometimes you might have to go and try it on your own but think about um what is it flash mobs right the first person to do something yeah alright they're doing it right if the second person doesn't do it the whole thing fails right so it's very important to be the second person don't worry if you're standing out here by yourself you know with a proof of concept if it's good that second person will fall in line that second person falls in line the third the fourth the fifth will fall in line too but none of that would happen if you're over here in the corner too afraid to you know to speak your mind or do what you're passionate about so make sure that you're leading by example make sure that when you're you know when you might be afraid to do something take a deep breath try it anyway what's the worst somebody's going to tell you nope we're not going to do that it's always no if you don't ask I don't mind being told no um I'll argue with people but I don't mind them telling me no um but I won't know the answer if I don't ask I won't know the answer if I'm too afraid to ask the question or if I'm too afraid to go and introduce myself to someone or you know so don't be afraid I see these events and every year I see people walking around I see them sitting by themselves and I'll walk up and say hi and they look at me like I have a horn growing out of my head sometimes I bring a horn with me just so I can say I'm a unicorn they really think I'm crazy when I do that but the point is like there's so many brilliant people here and we miss the opportunity to learn from one another because we're too afraid to say hi even or we're too afraid to acknowledge the hello what's the worst thing that's going to happen you have a ten minute conversation and you say no I'm not interested ten minutes we waste more than that just driving to work every day see what time it's here a few minutes so what I want you to take away from this talk today don't wait for permission get involved with a project or projects you're interested in don't wait for somebody to invite you seek out the experts and what you're interested in there'll always be somebody who is more knowledgeable than you go find them don't be afraid to fail so many people are afraid to they have great ideas but they're so afraid that they're going to fail they never start it makes me so sad like it's so sad don't be that person don't be afraid to fail and don't let your perceived lack of technical skills keep you from getting involved when somebody cares that's not what I need you to do I need you to go fix my wiki page I need you to go moderate this mailing list can you set up this meeting for me there are people who like to do those things all you gotta do is talk to somebody I have this rule that I think it's three or four questions when somebody's new to a community I want to know what they do in real life because that's going to tell me a lot about their skills I want to know what they're interested in what they want to do and then I want to know like have they been involved in a project before not an open source project any project right? have they volunteered before and those three things will tell me where I can start having the conversation like I said sometimes that person who writes grants for a living whoa they're going to be able to help you with a whole bunch of documentation because they like it or they wouldn't be getting paid for it because you can't stay involved in grant writing and not like it and enjoy what you're doing life is too short I once, you know this was a long time ago I had this very lucrative paycheck I hated it I absolutely hated it made me sick like getting ulcers, getting migraines you know what I had to decide life is too short for me to do that I want to do something fun and this is fun and so enjoy what you're doing if you're in a project and every time you think about you know looking at the mailing list or you think about getting an IRC meeting or even like you know online meeting and it just makes you sick to be part of it why are you part of it? go find another project that appreciates you how many of how many Linux distributions and loans are are there hundreds if one project doesn't you go find one that does do what you enjoy don't let people bully your own or discount you because everybody in here has worth and has value and can bring thought leadership to a project so we have a few minutes thanks for listening I hope I didn't bore everybody to death and I'll take your questions or as a friend of mine says take the bullets as they come any questions I'll come down there because I don't like being up there anyway yes so you mentioned that I don't want to take the mic you mentioned that you failed and that you you are kind of proud of that what's your most embarrassing failure how far back do you want me to go I think for me I didn't really have like huge embarrassing moments in the open source community I think there was a time that like it was embarrassing to sit there and here you are with a whole foundations team or you're with the team that writes a boom 2 and they're looking at you and you're the lone ranger sitting there it doesn't work and they're like yes it does I'm like no it doesn't and you feel so small until finally somebody says what are you doing and when you walk them through it they realize they weren't following their own instructions I was following their instructions and their instructions were wrong but that's difficult it feels like a firing squad to stand in front of these amazing people and here you are the one that doesn't write the code going your stuff is broken and they're telling you no you know and that's you know I was a little afraid that I would die but I did it anyway and I learned from it and they learned from it and I had this one time like how many of you guys y'all are going to laugh but how many of you guys remember when a boom 2 had Gweber anybody remember that so the developer for that I didn't know who he was but we were at this release part and he walks up to me and he goes why? I'm the developer now let me just go over here but what he told me he goes no wait I want you to reinstall it and I want you to file some bugs because I like bugs I don't know what's broken if somebody doesn't file a bug and so he was the one that had me excited about filing bugs because for the longest time this is one of those moments where fear got the best of me and I was afraid to file a bug because I was afraid I was going to upset the developers okay that was a little silly now looking back on it but it's intimidating when you know here you are this person that doesn't really know what they're trying to do but you know that something's not right and I was afraid I was going to make them upset because most of them were my husband's peers and so there was that dynamic that was going on and then I realized he was like we all want you to file the bugs because we can't fix it if we don't know it's broken and so I was a little intimidated for a while now if it's broken I'm going to tell somebody but you know you just have to overcome those fears and that was a very hard fear to overcome that piece of it and I was for about three or four months I was sort of paralyzed I didn't want to file anything I didn't want to say anything negative but then I got over it to me and so sometimes you might have to mentor and coach somebody else through that difficult moment through that moment that they're afraid to do something you know but listen to them and let them tell you and then if they're really good at it or you think they have great potential help them through it and don't be afraid to sit down and have that honest conversation with them now my most embarrassing failure in life was probably in eighth grade I played basketball you know how you switch sides so I scored the winning team of the winning points for the opposing team didn't think anything about it whatever my teammates tease me at the end of the year you know when they give out the MVP awards and all that that team because they went on to the state championship came and awarded me their MVP trophy in front of my entire school yeah I was a little embarrassed on that one so and there's still people today that tease me about that but you know it's one of those things right you learn early on that you know making mistakes are okay and that you get through them and you hold your head high and there's not a single I mean let me know is there anybody in this room that had made a mistake we all make mistakes we'll make mistakes in all of our projects no yeah just squatting yourself there it's too hot in here was that it any other questions I mean I'll answer whatever if I can but yes let me read the microphone so everybody can hear the question I know it was just a quick question you had a long list of projects there so I was kind of wondering how you discovered all of them really because I really not quite sure where to find all those kind of things oh this is awesome so that's a great question so I absolutely love wiki pages I'm one of those weird people that have a love-hate relationship with wikis maybe that's the first wiki markup is the closest thing to code I'll ever get to I say that and then watch next year I'll be doing some project that's always the way it works about the time I say oh I'm never gonna do that I find myself doing it but I love wikis and I love I just love doing that and so and searching through wikis because wikis can be like the youtube that spiral like you click on this video and then it takes you to this video and then it goes here well wikis are the same way and so I would get like on the bun 2 wiki and I would just start clicking around seeing what was there fixin stuff if it was like the grammar was all wrong or whatever I'd just go fix it or if it was an ugly page I'd go find out whose page it was and I'd go hey can I smush this up for you because I'm weird like that but I'd also do that on the fedora wiki and then I got to meet people like in the communities and I would just go hey what do you need me to do like what can I do pick me pick me but you know I would go do those kind of things and so what I would suggest is whatever project you're interested in go check out their wikis first go find like all the pages you know put search words in see what comes up and you know click on all the links and just you know just surf the wiki pages I know it's weird nobody's ever told you to surf wiki pages before but seriously just go through the wiki pages or the mailing list and see what the archives say look at the you know whatever the titles are you know and see what whatever those threads are about and if there's something interesting go click on it and then see who who wrote it and then go contact them or you know is uh what was that project that Ashish did was it Hatch was that it is it still maintained so Hatch is one of these uh sites where if people can say they need volunteers and they need help and you can put in like your skills and see what it matches you with so is Ashish here do you know if he's here yeah so well I'll see I don't know if he's here sometimes he comes here but he's he does that and so there's all these little things that will match people up with their with these projects and then the other thing to do is while you're here if you see somebody's name badge that says community manager on it hello I'm so so here's my skills I can't say everybody loves that but what I can say is they'll appreciate the fact that you're enthusiastic about it so just I used to keep a list of like I had this list of questions that I had about stuff when I first got started like what about this and how is this done and who's in charge of this and I just have it around and I'd have a list of names of people I wanted to meet and I was kind of like stalking some people like you do rock stars but that's just because I wanted information right and so I would go find them at events I'd warn them but I would go find them and just go talk to them so just go ask like whatever projects you're interested in whatever things you're interested in go find somebody who's on that project go approach them talk to them if they're not the ones that you know are in charge of whatever you're wanting to do chances are they'll point you in the right right direction just go talk to people and go like I said go search the wiki pages and go look at the mailing list because all open source projects pretty much have those things right they got a real-time chat whether it's IRC or Slack or whatever people are using today I'm not even going to go through the whole list because I will be here all day and then you know just and they have wiki pages and they have a website and they have mailing lists and so you know go go look through those yes sir so I'm in education and we have such a tough time recruiting women into technology in general so just as a woman what advice would you give to help us be able to recruit more women to get more women involved that's a good question and I often say because I fight this battle even in my own organization so those who have seen the line in block chart for open compute we only have two women you know I try to recruit people all the time but I think part of it is making sure that you link up with organizations who have a database of great women speakers and great women you know because usually those speakers have wonderful resumes around open source and around the technology background and have done wonderful things and if you have a card after we finish up let me let me get it and I'll actually send you some of those links where there's women and women often and Jill I'll let you correct me if I'm wrong but we'll register on places they know are reliable and you know that the people that come to that website searching for women speakers are sincerely interested in their knowledge not you know not how they look or how funny they are or whatever it's all about what their technology knowledge is and what their area of expertise is and so there's some sites you know are very much very reliable and very safe if you will to register as a speaker and get really good gigs out of it do you have any yeah the Linux they've got some good pointers as well and so you know those type of groups have great resources too and can point you in good you know in a good direction I think though sometimes people please interrupt me if I'm wrong I think sometimes people try too hard you know I always like it when there's a great lineup of women but sometimes even we fall short did I say that out loud we you know sometimes we aren't the just because we're estrogen laden doesn't mean you know we're the ones that should be getting up there speaking and I say the same for guys too because you know it's this guy and he's well known sometimes he shouldn't be up there speaking either I think you just have to know your audience who you're wanting them to speak to what what is the takeaway message you want people to get and then find somebody who can address that message whether it's you know a guy or gal like it doesn't you know to me it doesn't matter I think if you find the best person for the job but I don't think I think where we fall short and we get it wrong sometimes we don't even try like we just eliminate people based on their gender there's there's women's group that just eliminate all guys and there's guys groups that just eliminate all women I think it's like nukes to knife fights like you just don't do that you you look for the best person for the job and when we're sincere about that we get amazing people but when we lean too far one way or lean too far the other it just all goes to heck in a handbasket so any other questions you're gonna make me walk all the way back there hold on do I want to give a book away is it my book is this edition nine okay I didn't help write this one but I I led the way right so what question am I gonna ask to give this book away let me ponder this for just a moment actually because normally when I'm gonna give something away I know about it in advance this is terrible huh what so how many people okay I know what I'm gonna do how many people is this their fifth year coming to scale sixth seventh eighth ninth I'm gonna be lying to me too I don't know but I'm gonna trust your integrity 10th 10th 11th you may have to give me some more books 11 11 going once I think you don't want anybody longer than 11 years have you consecutively came to all of them okay yeah anybody else go to the first one oh we got two people you went to the first one you got a question oh first year you've come well I think since you sir went to the first one and what did you say 50 people how many people are here now how many people come to this thing now I know right I think you are the lucky recipient we don't often get at these and I'm gonna tell you how rare this is we don't often get people who aren't organizers that are at these events who have been coming to these events since the very beginning so I think it's time for me to turn the mic over and I want to say thank you and if you guys have any questions you want to talk about afterwards just find me I'm gonna be here until Sunday so just find me thank you so so you might say I want a job it's free but every time it executes if you move to say ten to five ten and a half hours of S3 you're gonna charge it again so the bill is gonna be in the right amount of money there are S3 correct one of those more than the last one so not terrible it's just kind of a consideration to talk about for being I've seen a lot of people that have been to it for a while you know how this all holds it's pretty amazing what you say except for me I'm not sure what actually it is because please try to ask me at least the other issue that I talked about was the social change I kind of talked about all this stuff when it comes to bills so what are the issues with that which I imagine will go away at some service level on how I will apply before you get this so not knowing exactly how it will affect the work under the cover but assuming it's based on the schedule what you think is the function of the process so if you create a function that's never existed before first of all you have to take the code and find the use of this container if you do that you're doing it like in the root of execution the container that it's running on needs to exist so they have hundreds of thousands of machines and the function doesn't exist today but when it does exist it has to run on node number 7 so from this answer the first thing you're going to have is you might invoke it and you might take I think they claim hundreds of years in the next few people depending on your volume of execution and obviously volume of this right now in other zones it's big like a lot of coverage which doesn't have shock waves depending on what's going on you might invoke the function I think it might not run but I don't know it might run in many people reported of course it was in many or two cases but they basically say that's my perspective I don't think there's no such thing as a key it's easy to look at what's going on in Q and some kind of jump set in key for now or today or at least that's true but one side is not at all there are a lot of jobs that you don't care they should run today or should run as early as possible when you start talking about that and all the workers over just like a buddy this worker does not have over memory which you might have a lot of people are really adopting it for back end mobile services so you're a mobile developer why do you need service at a time when you're feeling like how do you guys make your acting call up with rest services and make those rest services on the point of finding a way to run the function and not an engine that you don't have to scale with but if someone pushes on a button in their app and you expect that result to come back because if you see it you wouldn't see a key to zero on the call seconds you wouldn't want it to be not too much longer based on the amount of service that you're able to serve that's going to be a significant difference or you might have to actually do it internally to your company between physicians or your company to your customer you have to give them a response note for an A and then you're going to need to do that you can actually use the question again you can use links to other services on that so that's it again there are some people So people, again, have to act in sort of view of a post-deployment of it. So it'll say, okay, I have a straight and sectional audience with a point-of-lander function. And then I have a fake piece of data or a fake object that it writes immediately afterwards. And you'll remember that the time it gets into production, like, fake calls there is that it'll basically be live and it'll take millions or hundreds of thousands or thousands of seconds. So what goes on there is, again, you know, when they're pure, but you can't keep up with the passion, once it's attached, it can get into most of the process. And if attached, again, if they don't give you control of the ex, the passion will expire. So if you execute a land function a thousand times in a lot of times and you don't execute it for a week, and you execute it one time every two months, you're going to get a post-deployment. If they have some sort of cleaner service that says, like, you know, whether or not they're talking about a second hour or a day or whatever, they have some ballistic devices that prove they're not probably these things. But all of those clear out all of their intentions. These things that are going to be bad for us in the future. It's not just my help, it's everyone in these things. Here it is. And yes, do you need a simple function? All right, do you need a few functions? Step function helps you a little bit. There's a couple of frameworks. If you already know the developer, do you need to play stuff? Do you need to play products? The biggest one is the Interactive Office for Service. That was about my name. And as you know that yourself, from that know that, if you think of it like there's so much available, you don't need to go to the official web app space. You kind of need to use the web app. You need to use the site. You're like, okay, I know now. I'm not supposed to call it in the project. I'm going to be in town. You've got a space to find it for you. So it's pretty cool. Functions helps a little bit. But you have different routes about it. Instantly... So I think it's all for us. Any further comments? No, that was the name. They said it was going to be in May. They never called it before. Okay, let's go into it. So the Amazon is like, it's not being in full搜 technology. So who do you like the most in the space? But there was a little project that was directed at the moment that I talked about at the service office in New York. It's changed since they announced it. But they basically answered the challenge. So when they were in their way, she made this kind of version of the project and it goes out. You can imagine that it's a mess. Herbal, it's a function. It's another function. You're going forward in versioning, right? If you have up to 42 functions, something that's long, whether you want to go back or go forward, it's not a big family. So again, they're kind of used to this. I think it came back because there's so many people around me because I think about people's kind of experience. So I've gone way long enough. Actually, it's been a long time. I don't have much content because frankly, there isn't much content. These guys are new, but newish. And a lot of the same, like I decided to say something to talk about twice again. I don't have much to talk about because really, they're not really interested in that. For these last two years, we have actually served this. We've actually run it ourselves on service. And the second most popular way to take it, the second best, is from Microsoft. So they call it the AirTrip Project Functions. That's their answer. They have a very similar, they just have a SIM card, a SIM card, a SIM card, a SIM card, a SIM card, a SIM card, a SIM card, a SIM card, a SIM card. I haven't had an office one much. I've been using this for a while now. So I'm going to go back to this. When you're used to searching in case of COVID, these other ones, but in general, why it's important to just know as a daily writer The other thing is each name, especially coming from my top page, I don't know how to get into it, but please, if you really are a better player, if you're a critical player, they, if you really want to use that service, they actually push different types of services into the patient. That's all serving today for me and this one. I'm going to go with that one. Amazon is kind of the focus. How are you going to get into it? I think you even have some code that's built in where you can actually look up what they thought it was going to be. So if you're managing the windows and the package is in there, you can trigger functions that accept the system. It's kind of a cool effect. Literally, you don't have to get it to scroll down or whatever. It's kind of similar issues. So again, I'm not going to do that if you don't want to do that. I'm not going to do that. So again, at the end of the day, the truck was very similar. They had, they can accept the traffic, some of the services, general service, some of the, IOT service, which is actually really good for the patient. It's quite good. For the customer, it's one of the ones that I have. So the problem is, waiting for the service is over. Not really, but it should sink. If you're converting this one back over, sometimes it's going to sink. And this is what happens when you do it because it's very open as a TV of a TV. So what they've introduced appears to be adding to them, that's one of the main things that I thought was right now. If it's crossed, and the piece that you do comes up with it is like that, or really, so you're building to the definition of, and I think it's a crossing function and it ties to this crossing that's going to come in. And until they So, the color agent that's related to the system is going to wrap this reservoir up to the system like that. And then as soon as I re-wrap that, it's not the writing that I have, it's the color that I have in the function. So when you think about having an app that exists today that's, it can map, again it's a funnel that's going to be the first app to be provided with, the first app that knows. And when you map that, you can basically have it fully controlled. So what I think that you might not have, such as this 20 kHz open hardware, is the media functions. I know I'm not going to make sure that they're the ones that you can still work with. But it's not taking those steps as a part. So anyways, this seems like a very, very approachable game. You can kind of call this game a business one, but it seems like they're going to do that as a business one. So a lot of people like this function by function. If you're having a stable system already, okay, I'm going to write this one graph, it's one function. If you're going to write it, it's still being drafted. You can house that as a proxy. It's still going to be the further function of the room. So it seems like it's still going through a really big group session of patches or whatever. It's a family room, so it's going to go back to the app. Maybe it's also going to be testing on the room. Again, a lot of what we talk about today is, let's start from where we're coming from, and then we'll look at these things, considerations we're going to have. So that's a big point. The rest of the app is a kind of function to see. And very importantly, all of our understanding of this is, you know, one goal is to do a single file function, or this one is a kind of system. If you have to do, and you have to add your functions, and you have to design the window functions, Google has to do the function. The thing is, so it's kind of like, as you say, it's a new dish, you know what I'm saying? But it's not, it's still not really there. I think it was busy, it was so much fun. So it's kind of like, I think you can actually appreciate it. It's a close-out for a little while, and you can expect more from people. So it's a really good thing. If you didn't follow the documentation like that, there's also a lot of other stuff. It doesn't look stuck to that perspective, but it's very neat and very, really good. Essentially, the next thing is not. It's not treated, but it's treated like a Google file of what sort of triggers. They have their peer-reviewed services, and some of the services that they're doing. So, again, it's kind of a cell phone, something like that, but I think a lot of that's been changed in the past. Those peer-reviewed services are much more interactive. So I understand what they're doing, but I don't understand what they're doing. I imagine they have to review at least not something, or they can also review it, or they probably have shops that every issue is not. I don't see a lot of shops and triggers, and they only have places where they can review their products. So probably if you go through some of the peer-reviewed services, for execution time to remember, there's a whole few ways. So I kind of understand that the core of your game is serverless. Those are the true serverless places. There's a couple other ones in space that offer those solutions, right? So apparently serverless means serverless. That's why people are so granular to this one today, whether it's crime-space-based centers where you're ranging all these types of things. So the heart of those solutions. So the one that's been around kind of has a biggest influence in the fact that it's not even a project. So it's called open-to-visit. Here, on the other hand, it's basically, I guess we say that you don't need it, so there's actually a combination, which is great. But what I understand has come out of this out-of-perspective means. The community is already just going on this ownership and the companies are doing more. So I already developed a new project that is, it came out as an out-of-perspective. So I think from a computer perspective, there's probably even the technical way of developing it. And I'm not interested in the project, but I'm interested in the experience. It's due to some sort of kind of way of course, the out-of-perspective means. So it's realistic, and you can consider the way it was done. Of course, depending on perspective, you can develop a service, right? It's just an option that you're working on. It's there on people that you're working with. So someone I was working with is just within a company. I think some of them are in the company, but they also go out and work with them. So, again, it's actually pretty much the same stuff. And now, so what you've written is a written project. It's based for many of the states so to speak, so to say. So primarily what they've written is this kind of code. And next, we've written many types of data across the set of costs, kind of the element that works with other sort of data. They've pulled that on the front end, so it's kind of the part of the context that's at the point. It's very push to be able to read the system. So when someone says, I'm open to this function, it allows you to imagine that it's a controller, a controller such from the way that you hear. I assume that, I don't know. But you can actually hear what it says as it shows you this model. So, in the end, when it comes to this, what it is, it'll be the primary function if you are having some container kind of similar types of models. So what they do is they'll have a few machines to make sure that you can hold and then start the value and then control what's going on. So, and then we have too much detail that their solution is a little bit more very good, yet end-dating solutions of all kinds of easy way to think about the kind of EPI and thinking about the rest of the data. The cloud providers will come on at the end of the day to kind of approximate some sort of rest of the rest of the data. You're always going to have a DSL, you know, you're kind of defining the job and say, I have this function. So in Amazon, in Amazon, we get a dashboard that I think there's some sort of this kind of work-like thing, but most of the other requirements are the kind of similar issues that you have. You have some sort of file that you face kind of issues in DSL, including the jsonar model. So, the kind of picture that I'm going to talk about is how to disconverge nothing that is still all over the service. Even with this, it is kind of that. Do it yourself as opposed to the language which you have become. If the interface is not that it is. Single-functioning project typically is going to depend on the language. So, it's going to depend on the language and the process. So, again, there's a lot more that is a project, so there's a lot more content there. If you could do a real bit of some good getting started stuff. Mostly, I think, you could do similar problems that you want to interact with. It's kind of that. So, I think there's a lot of contribution at the end of itself. And very similar to this, there's one called Fission. So, Fission is newer. It doesn't have the traction awareness that you know people use the style of papers. So, again, there's a lot of contribution that you can create. So, Fission is a very different thing. It's a very different thing. But it's a very different thing. So, Fission is a very different thing. So, Fission is a very different thing. So, Fission is a very different thing. Fission is a very different thing. So, Fission is a very different thing. So Fission So, again, it's very simple, and I'm going to start with a fun little function, I'm going to go to context, I've got the first two inputs, context is kind of complicated, and that can be pretty much everything. I think it might be some mediators, but I think it's a problem. And then the callback, based on your... ... ... ... Hello? I found the switch, it's on the bottom. Look, I found the switch. Should I use this one? ... ... ... ... ... ... ... ... Thank you. The good news is I have an hour for this talk, and it's not an hour long anyway. So, starting 10 minutes late, you just had some nice little chats in there. So I'm here to talk to you about 10 years of Zubuntu. How many people here have heard of Zubuntu? Yay! How many are using it? Alright, not as yay. I'm just kidding. So this presentation is sort of in two parts. I'm going to talk a little bit about the history of the Zubuntu project, which is a very opinionated history, as all histories are. So I'm sure some of the early project members will watch this later and be like, that's not how it was at all. But I did talk to some early project members in preparation for this talk, because I only got involved in 2010 or so. And then I'm going to talk to some of the things that we've done as a project to make the project successful within the Zubuntu community and open source at large, because Zubuntu is one of the larger flavors in the Zubuntu world, and it's one of the oldest. So just to sort of introduce myself, if I haven't said hello to any of some of you yet, I'm one of the authors of the official Zubuntu book. I started working on the 8th edition. We also got the 9th edition that came out in July, and I've got a couple copies here to give away after my talk. One of my co-authors is giving a talk in the next room. They put us at the same time. I think he's giving away a book too. So I've been working on the Zubuntu book with Matthew Helmke and Jose Antonio Ray for several years. I also spent six years on the Zubuntu community council. That's one of the two governing bodies of the Zubuntu project, so I've been doing Zubuntu stuff for quite some time. In the Zubuntu project I'm technically the marketing lead. I don't actually know anything about marketing. I'm a systems engineer by trade. I mostly recently worked on OpenStack. I now work on Mezos. I don't actually do any soft, skilly things, but I know how to use Twitter, so it's a small team, and they're like, alright, you're the marketing lead. And I was the website lead formerly, and again, I'm a back-end person, so that was because I helped them do the migration from Drupal WordPress, not because I can do website art, because I don't. Like, I paid someone to make my website. So first of all, just sort of going through the history of Zubuntu. I like this slide because it sort of has your little logos through the ages. So the first one, there's the original logo that the Zubuntu project had. It is the XFCE mouse inside of a different colored Ubuntu logo. The next one is in the middle. That one was, I think we used that logo for about two years. We're taking the XFCE mouse again, and now it's jumping into a circle. And the one we've used for the past several years is this little mouse in a circle. And that's the one we have on all of our T-shirts and all the other goodies that I'll show you later. So Zubuntu came about in 16.06, but that depends on how you count. We called 2016 our 10th year, but the Zubuntu desktop package actually came out the year before with the 5.10 release, but we didn't spin up any ISOs. So we called 2016 our anniversary year because 16.06 was the actual release where we had a Zubuntu ISO and we released alongside KDE, and I think it was Edubuntu, or Kubuntu and Edubuntu. And this is what the desktop looked like back then, ten years ago, almost eleven. It's not so bad, but you can see it has some room for improvement. I started using the Zubuntu desktop specifically as a user with the 6.10 release, so pretty soon after the first official release I started using it. I'd been using Linux for about five years prior to this. I'd been using, I started with Red Hat, and then I went to Gen2, and I was using Debian a lot, so at this time I was using Debian. So this is my blog post from 2006 when I said I finally got rid of Debian testing on my primary desktop, and I'm switching over to full-on Zubuntu. I had been using Xfce just sort of installed on top of Ubuntu server, but I was like no, I'm going to make the switch for real, I'm going to use Zubuntu and see how that goes. With the 10.10 release I joined as a contributor to the project. So this is sort of when I became aware of what was going on in the project. But to step back a little bit into history, of course it started with 6.06. Within two years the project had a bit of a crisis there was no clear definition of what the project was supposed to be doing as far as what default applications were supposed to be shipping, how true to Xfce they were supposed to be, was this going to be a plain old desktop that just was like vanilla Xfce, or were we going to be adding custom icons and custom themes and other things. And the package question was really hard because we were wondering what should we ship as default applications. Should we follow GNOME and ship a bunch of GNOME stuff, or should we divert from that? And it actually caused some serious problems in the project. We'll talk about how those were resolved. But some contributors left and we had a really rough time around 2008 because people did not want to contribute if it wasn't going in the direction they wanted. But the project as a whole did not have any sort of mission statement or any strategy to say exactly what they are. So everyone came to the project with their own ideas and when their ideas were not satisfied by the collective they left. And that was one for anyone involved. But thankfully I came after that. So in 1010 I accidentally got involved as happens often. I was on the Ubuntu Community Council and the Ubuntu project was using Drupal and it was a really old version of Drupal hosted by Canonical. And they've been hosting the website the entire age, like the length of the project. So that was nice that they were hosting it but the Drupal was old. Hardly anyone had logins to it and it was just a big mess. So they're like, hey Liz you use Ubuntu and you're on the community council which means you have power to do things. And I'm like ha ha ha but actually we really get some things moving. And we decided in the course of that instead of just upgrading Drupal like two or three versions, was Drupal actually serving the project anymore? And should we switch to something else? So we spent about a year working with Canonical and switching over to WordPress because it was easier to use and would fit the needs of the project better and Canonical could more easily support it so they would be updating it often which was great. So that's how I got involved. I was helping them with the website and then I got them converted over to WordPress and then everyone disappeared and I'm like, well I'm not going to maintain this and they're like, I guess you are. So I became sort of the maintainer of the website and then I was working with someone else who eventually he's now the website lead who actually can make things pretty and have a lot of work with PHP which I do not do by choice. So that was 2010. And today this is our pretty desktop now. We've got a designer who works with us and he makes pretty desktops every time. So this was the release that came out in November and the project is in a pretty good spot. Like any open source project we always need more contributors. There's never enough people testing our ISOs so there are always bugs when we release. There are never enough developers to fix the bugs and this is an ongoing problem because everyone in the Zubuntu project is a volunteer. No one's paid to work on Zubuntu. Aside from what we get from obviously Ubuntu is our base and people are paid to work on that but everything that is Zubuntu is all a bunch of volunteers. So we do have struggles to make sure we have enough people contributing. So if you want to contribute, grab me later and I'll give you some pointers. But the team's actually pretty solid. We have some really long term contributors. We have new contributors coming into the project at a pretty healthy rate. We're still only about 12 people total and since I'm not a developer I run dev.zubuntu.org which is our development site but I don't really do any development. So there are people like me who don't really do development on Zubuntu. There's like half of us are developers, half not so much because it got the website person and the QA person. So that's today. Things are really good and that's why I wanted to give this talk because I'm really proud of the Zubuntu project and it's the place I'm spending more and more of my time in the Zubuntu community these days. So to step back a bit, are people familiar with flavors in Ubuntu? So to quickly explain, Zubuntu is a flavor. It is not a spin off. It's not a derivative. And what we mean by that is that every single package that is shipped with Zubuntu is in the Ubuntu repositories. You don't need to add a different repository to get Zubuntu. You don't necessarily have to download a different image to get Zubuntu. With the net boot image it's one of the ones you can select. If you install server you can just install Zubuntu with the Zubuntu desktop package which again is just part of the Zubuntu repositories. So all of the development of Zubuntu is done within the framework of the Zubuntu project. The packages are uploaded through the same framework all the Ubuntu developers use. Releases are very tightly integrated with the Ubuntu release which is something people tend to be surprised about. There are lots and lots of flavors now. There's Kubuntu and Ubuntu Budgie and Ubuntu I think there's like eight or ten of them. And if one of those is not ready, Ubuntu won't release. So all these projects come together and sit in the release channel on release day and re-spin images and make sure everyone's happy. And that's always a really funny day for me because I'm not one of them. But if you see sometimes Ubuntu is a little bit delayed in the release it could just be because all these moving parts have to come together and it's really astonishing that all these communities can come together and build this together. But we are using all of the same release mechanisms. We're using all of the same tooling and all of the same process to get our packages in. So if you want to contribute as a developer making packages to Ubuntu, you have to go to the Ubuntu, what are they, the technical membership board and get upload package rights for Ubuntu in order to contribute to the Ubuntu patch set. So it's all very tightly integrated and Ubuntu developers work very tightly with the Ubuntu developers. I like to say Ubuntu is also part of Debian because we've got some of the packages that Ubuntu uses are actually packaged inside of the Debian distribution and then automatically synced over each release. So I'll talk about that a little bit more in a minute about how we participate there. But this means that all the work that is put into Debian to support a lot of the packages that ship with the Ubuntu distribution, all that work is directly consumed by the Ubuntu project. So that's one of our upstreams is Debian. Of course XFCE, the desktop environment that Zubuntu and it's why it's an X in the Zubuntu there is for XFCE. So that's the, that's what makes it it. So we spend a lot of time in development wise in XFCE as well as an upstream. And like every single Linux distribution, we're also part of this broader community of open source projects. We ship with LibreOffice, we ship with Mozilla, Firefox, and all these other pieces of software that come by default in the distribution. And of course we didn't write those. We pulled them in from other communities. So we here and there have to be involved with those communities and we find bugs and file them upstream and such. So speaking specifically of our upstream I mentioned XFCE of course. Our contributors in Zubuntu, a couple of them actually contribute to XFCE directly. They're more developers in the XFCE project. So when we have problems in Zubuntu we can directly impact getting those fixed upstream and that's been really valuable because Zubuntu is probably the biggest XFCE distribution out there right now and has been for quite some time. The numbers kind of go, come and go and it's hard to exactly measure it. But looking like over time people try a new XFCE distribution and they come back to Zubuntu because it's safe and good. At least we like to think so. So when there's problems with XFCE or things like Thunar which is the file manager there have been some issues with that lately. But instead of just bugging upstream we have developers who are actively working on that who also work on Zubuntu. I briefly mentioned the Debian packages but we actually have someone on our team who works directly with the Debian guys and he is one of the Debian guys. Thankfully that's not me anymore because I don't like making Debian packages but we have someone on our team who works with them and helps them update the packages because sometimes we need a newer version of some component of XFCE that's not yet in Debian. So we help them too. And again this is all on a volunteer basis across the board. One of the really cool things we also have is the Shimmer project and I'll pop out of this presentation for a second here. The Shimmer project was started in 2009 and this was an attempt from the Zubuntu project largely to start creating themes that were not strictly tied to Zubuntu but would end up being the default Zubuntu theme. They didn't want to have this design group inside of the Zubuntu project. They're like we want to make XFCE themes that everyone can use. We don't want the stigma of them being attached to a particular distribution because if Zubuntu is using them then Debian doesn't want to use them. No, it's going to be a separate project. So a bunch of the folks went off, created a Shimmer project and their goal is to make a really good UI that does all of the art things like make colors that match and workflows that make sense in the UI. So they've got a GitHub repository and these are the guys. They are all actually male so they are guys who are working on this. These folks are also Zubuntu developers these days. So that is the Shimmer project. How do I not lose my place when I bring this slide back? Yay! Okay. So Shimmer project is another upstream and again we've got a lot of cross-collaboration there. So sort of speaking to... The reason I go through all that is because working with upstream has been really important to our project because if we don't have impact on the upstream, we're sort of beholden to whatever they're giving us. There's plenty of Linux distributions that work that way where they get what they get and they use it that way. But I think one of the reasons that people stick with Zubuntu is because we have so much impact on the upstream and we can make change where we need it. But another thing we've done is we've really stepped up our game with community engagement in the past few years. My marketing thing... I don't know how to do any of this really but I've sort of learned along the way. One of the things we did was that I joked that I know how to use Twitter. So I created the atZubuntu handle on Twitter and that was fine and we started updating it. But we realized that there were other Zubuntu communities out there. You've got Facebook and Google Plus and LinkedIn and I don't even know all these things. I was like Facebook. I went out and I was like hey I'm going to look and see if Zubuntu communities already exist on these platforms. So I went out and I found a few on Facebook. That's where I started. Some of them have really solid moderators who I would feel confident making official their Facebook page. Some of them not so much. Some of them had people posting screenshots of desktops that were not... Let's just say the desktop backgrounds weren't always awesome. I was like that kind of needs to be moderated if we're going to call this an official Zubuntu thing. I started talking to some of the moderators and some of the people who were running these. I found one that I really liked on Facebook. I'm like listen, I don't want to do Facebook but you're doing an awesome job there. So let's make your Facebook page the official Facebook page of Zubuntu. This was awesome for two reasons. One, they were so happy. They were going to make my page official. That's so exciting. I feel so honored. I'm like yeah and you get to still do the work. Then I didn't have to do the works and then we had a Facebook page run by this really legit guy and I didn't have to do any of the work and he was all happy that we recognized his work. We did ask that one person on the Zubuntu team officially be added as an admin just in case the person gets hit by a bus. They lose the page or lose access somehow. We do ask that they add one of us as a backup but they're always happy to do that. So we did that on Facebook. We did that on LinkedIn and we did that on Google Plus and it's worked out really well. We have really eager community members on each one of those platforms who actually knows how to use the platform who are helping us run our social media accounts. So they're excited to be brought into the project. I'm excited to have these official channels run by really solid people who were already committed to something. So that's one of the things I'm really proud about community-wise because I totally did this to make sure I didn't have more work and it turned out everyone was really happy about it. Something else we've been playing around with is just giveaways to sort of engage the community. One of the first things we did was after we had our new mouse head logo is we printed up a bunch of stickers and I went on Twitter and I was like hey do you want some stickers? Just give me your mailing address. And it turns out to send random women on the internet their mailing address. They were happy to send me their mailing address and I sent them stickers and it was all kinds of fun. Now people got really excited and I started seeing these stickers in the wild and it was so exciting because I'd go to a conference and I'd be like that's the Zubuntu sticker that I had printed because they'd give them to their friends. I'd send them like 12 stickers and they just sort of decim- what's the word? It got distributed somehow, yes. That was really fun and it was really inspiring to contributors to Zubuntu because again we're a really tiny team and we don't have a lot of resources but seeing that people are actually using it, actually like the AV guy here, he's like I use Zubuntu and I'm like yay. But seeing the sticker on a laptop and having people say they use it is really inspiring to our really small group of contributors and that's one of the reasons we volunteer and it's one of the reasons we do the work we do. So having that reinforced through these kinds of giveaways and then people responding to us is great. Which brings us to the next thing is sort of we do these contests and blog posts. We started out with this Zubuntu at blog post series. We reached out to organizations that we knew were using Zubuntu and we asked them to tell their story. We'd do it sort of interview style where they would, we'd send them a bunch of questions and then we put in our blog and say you know this computer recycling place was using us or this school or this company and we started putting them on the blog and that was also inspiring to contributors because again they're not just working in a vacuum. There are people taking the Zubuntu, the work they're doing on Zubuntu and actually making real things out of it. Last year for our 10th anniversary we did a love Zubuntu campaign where we had a love Zubuntu hashtag and then asked people also to send in stories about how they were using Zubuntu and these were much simpler and much more informal than the blog posts we were doing. And that was a lot of fun because we started using the hashtag on Twitter. People started sending us their stories. Some of them were silly and funny and some of them were really actually impactful. And then we selected two grand prize winners and then three other winners. I don't know how we came on that number. We just wanted to give prizes to lots of people. And what we did for that was we worked with Unix stickers which I'll show you the link in a moment. They sent a T-shirt and some stickers to each of the grand prize winners and stickers to each of the finalists. And then at home I printed out our artwork lead guy made little certificates and then I printed them out on my laser printer and then I signed them and then I sent them out to everyone. And people loved that. Because when you write with a pen, I don't know, it just made them feel really special. And I sent a little note along like thank you for your story and whatever. And again that brought us in user stories which was exciting to our contributors who always want to see these things done. We also decided I did that initial run of stickers. I went to moo.com and just did customize stickers. And that was fun. But it was expensive and it was me just giving away stickers. So when we started getting approached by companies who wanted to sell some of our stuff, they wanted to use the Zubuntu logo and sell stuff. And we're like, alright that's better than Liz being the distribution method. So I can show you here. I don't remember who approached us first but I'll just say this one first. So hello tux. They now create Zubuntu polo shirts, women's t-shirts, and then a sweatshirt like these hoodie type things. One has a hood and one is just like a zipper sweatshirt. They also sell a flash drive for 35 dollars. But they don't have a huge scale. So it's going to be expensive. But this was great because that was no longer a distribution point. And also they made really high quality products. And whenever we need a prize for a competition or we want to reward one of our community members, we can just reach out to these folks and say, hey, can you ship off a polo shirt to one of our contributors who's been doing really great work? And since we're letting them use the logo, Canonical technically owns the trademarks and stuff but they let us use it and this I think works out somehow. And so they'll send us free stuff. Plus users were like, I want a t-shirt. I want a polo shirt. I want stickers. And we're like, okay, this is how you can get them. And then Unix stickers.com is similar. We tried not to overlap any of the offerings between the two vendors because they just offer different things. So Unix stickers have tons of different awesome Zubuntu stickers. They even have these sticker bundles and pins. And they have these great t-shirts. I don't think I brought it with me this time but it's one of my favorite products, the blue Zubuntu t-shirt. So again, just like the social media, instead of us going out and trying to create these things that our community wants, we reached out to existing people in the market who were more expert at this. And again, for Unix stickers, they were the ones who did our love Zubuntu campaign. They sent stickers and t-shirts to our winners. Coming back to that little story I told about a little crisis in the Zubuntu community in the beginning. I was talking to Cody Somerville who was an early contributor to the Zubuntu project and one of the leaders at some point. So in preparation for this talk, we had a nice long chat. And I was like, so listen, tell me about this little kerfuffle that happened in the project. And he said it boiled down to the question of what is Zubuntu. So as I said, people were arguing about what kind of applications to bring in and other things. So there was a community meeting and then they created a mission statement that everyone could sort of agree upon. Now I used to have really mixed feelings about mission statements. I thought they were silly and bureaucratic. But since working with a non-profit and seeing ones in projects like the Zubuntu project I've finally found some real value in these. They get everyone on the same page in a very simple way. This could be made simpler. But in short, we want to make sure that our community and our contributors know that we are community developed. Again, we're a bunch of volunteers. We don't have a company telling us what decisions to make in the project. It's really driven by us. And we're always going to be a Buntu based as codified inside of our, you know, these essentially founding documents. We did have an April Fool's joke one year where we said we're switching to Debian and they didn't tell me about it. And then they did the joke and I was the social media person and I'm like, what have you done? Because that was almost news. Anyway, so we're not switching to Debian. We're a Buntu based. And we want a system that combines elegance and ease of use. We want something that's easy to use and looks nice and people are comfortable using it. We also want it to be relatively light. So we don't want to ship really heavy applications. We don't want to... We were like an alternative to GNOME for a long time. Now we're an alternative to Unity. We're not as light as something like Buntu, which uses LXDE, but we are pretty relatively light compared to Unity and KDE. And we wanted to be stable and really configurable. I used Enlightenment before I used XFCE and you had to edit XML files to change things in Enlightenment. And that was really unpleasant. So when I switched to XFCE I learned I could move my bars around wherever and I could do everything and I never had to touch XML ever again. So that was very configurable and nice because it was easy. And we want it to look polished and pretty. So we have a guy who works just to make desktops and work on the themes and again the shimmer project. We want it to look nice. In addition to the mission statement, we also have a strategy document, which again I'm seeing all this bureaucratic stuff pop up suddenly. Why do we need a strategy document for an open source project? But as I've been involved in the community in the past six years, I found that it's one of the things I'm most proud of about the project. So Cody, when he was working as Zubuntu lead and trying to sort out issues with the community, he created the first iteration of it in 2009. And since then we have iterated on it as a community. So the Zubuntu team weighs in on it if we want to change something in the document. We'll have a couple meetings about it. We'll talk about it and then we'll vote on whatever change we want to make. And so it has changed quite a bit since Cody originally created this thing nine years ago. And when I was talking to him the other day, he was really surprised by this because he's no longer involved. He's moved on to things. He was actually my boss at Hewlett Packard Enterprise for a while, which was really weird because we worked on Zubuntu together before. And then we were working in real life jobs together. Anyway, so Cody and I go way back. He hasn't been involved in Zubuntu for years. So he was really surprised when I told him that it had become this living document that we're still basing the project off of. And so I just wanted to take a few minutes to sort of go through what we have in our strategy document because I think it's something that can be really valuable to other projects. So it's not, oops, it's not short. So I'm just going to scroll through this real quick. Like it's this, here's my scrolly. It's a pretty hefty document. But we decided we need something pretty long. So we give you the about the document, tell you the mission statement. We talk about the target audience for the project. So what kind of people are going to be targeted as far as the audience of Zubuntu. And again, this sort of reflects the mission statement. We also define some areas of focus. So these four areas of focus are what we consider every time we make a change to Zubuntu that is somehow major and going to be impacting the distribution as a whole. So the first one is usability. This does not mean accessibility, unfortunately, because we don't have the resources to submit to that, both upstream and XFC in Zubuntu. But we do want it to be easy to use for the standard user who we had identified. We also want performance to be pretty good because we know a lot of people are using Zubuntu on older machines. We wanted it to be ready to use. So when people install Zubuntu, they have the tools they need to get going. Ready to use has been a really important one for us recently because we were shipping Zubuntu with Abbey Word and Numeric. These are the Office Suite pieces from GNOME. And we kept hearing from so many people that they're like, listen, performance-wise, these are fine options because they're pretty lightweight as far as Office Suite go. But I can't use them and the first thing I do is install LibreOffice. We were hearing this for about three years. And every release we talk about it, we're like, are we going to switch to LibreOffice? And we're like, no, it's a monstrosity. We're not shipping with that. And so there came a point in the project where we're evaluating, we're going through the strategy document to make decisions, and we're like, listen, we have to make a decision between performance and ready to use. And honestly, our community, because they were speaking out to and saying, listen, this is not how we use Zubuntu. So we made a bit of a compromise. We did switch to LibreOffice, but we only ship a certain number of components. I think we only ship the writer and the spreadsheet. So it's pretty similar to what we ship before, and it is heavier weight because it's LibreOffice rather than the GNOME components. But it made our community much, much happier. So that sort of thing is what we have to consider with ready to use. And then as far as community goes, we want to be hearing and listening to feedback. And that's where social media became really important for us because normal users are not going to come on IRC. They're often not even going to come on a mailing list, but they'll tweet at you. Oh, they'll tweet at you. And go on Google Plus. Like, can you use the bug reporting tool? They're like, no, that's what Google Plus is for. As far as the community goes, we also decided to put our sort of governing documents into this. So we had a Zubuntu project lead for many years. But again, as a volunteer-run project, we decided at some point, well, we wanted to have a new leader and no one wanted to be the leader. So we said, how about we have three leaders? And then four people said, we'll be on that. And we picked out the four of them. We picked three of them. And the fourth one was so relieved. So we decided to make a Zubuntu council. So previously, if you looked at this strategy document a year ago at what it said project lead, but again, we changed our mind on this and we now have a three-person council. And this is kind of just bureaucratic of how we defined membership, what they do. We also have a Zubuntu team, which is the one I mentioned that has like 10 or 12 people on it that are core and can make decisions. So that includes the marketing lead, the website lead, the QA lead and all the other people. And what we say to stay a member of this team, you have to be active, you have to actually care and be invested in the project. And we also have some things like here and there, all of the leaders in the project have to run meetings from time to time. We have a rotation of who's running the meeting. So it's not just the project leader all the time who's doing the meeting. The QA lead sometimes does it. I sometimes does it. I does it. Sometimes I do it. Sometimes I make the website guy do it for me. But we all sort of share these duties and we all also like agree that the quality of Zubuntu is on all of our shoulders. So it's not just the QA person's responsibility that this is a good release. We are all supposed to be testing the ISOs as members of this team. And I haven't done that lately. So I'm a bad member. We also sort of talk a little bit about our users. In development we also do some of the key sections of how we do development of the software. We talk about the fact that we need to have community driven meetings. We need to have, we're using these specific tools. So we're using mailing lists and IRC channels because there sometimes comes up people come along and be like, I want to use Slack. And we're like, we're not using Slack. And it would have to be a real discussion because we're like, listen, we made these decisions and we talked about them together and we put them into the strategy document for a reason. If you want to have this discussion that's great. But it has to be a real discussion and you can't just start a Slack channel without talking to us because maybe someday we'll adopt your Slack channel. But it's not going to be an official part of the project and you actually have a process to go through to work with us. We have a tiny section about dispute resolution. This does not explain how to resolve disputes. That's like, there are whole books written on it. One of the reasons we included this is we wanted to make sure that it was important, communicate that it's important to us. We really like having consensus and we don't like it when people are arguing because that's sad and we want to make sure we get to a good resolution. So we've adopted the code of conduct just like the rest of the Ubuntu project. And we can go to the Ubuntu community council if the team is having an issue. But we wanted to just write that down to make sure people knew. And then there's more development stuff like how often we do releases, how long these releases are supported for because flavors can diverge from what Ubuntu itself does. So when Ubuntu LTS lasts five years, Ubuntu LTS lasts three years because, again, lots of volunteers. We don't have time to support a release for five years. Some people will keep using it after a few years because Ubuntu is still upgrading the kernel and they're still updating the libraries. It'll be fine. But your XFCE packages are really old. If they're okay with that. And then, you know, boring stuff about core components and package selection stuff. So that is our strategy guide. Hopefully I didn't bore you to tears. But I wanted to go through it because I'm really proud of it. And I think it's been central to the success of the Ubuntu project. And I think more projects should have them because I joined open source projects that really have no direction. And I see the conflict arise in these projects that doesn't really need to be there. Like if you all just had stated goals and would agree upon things, like as a baseline, a lot of the issues and conflicts that happen as far as technical decisions and things wouldn't really manifest. We do still have, you know, personality conflicts and issues that come up with regard to default applications. And people get really passionate about this stuff. But we have a baseline to go back to and say, hey, we have a process for this. So this is a summary of that just in case I couldn't bring up the website here during the talk. And I'm just going to conclude by saying this is also a lot of fun. So these are a few pictures. The big one is at the final UDS that happened, the Ubuntu developer summit that was in Copenhagen. Very sad. But I got to meet Micah there and my friend, GNOME, were all contributors to Zubuntu. And that was the first time any of the Zubuntu contributors had really gotten together. And then we went out touristing in Copenhagen. And then that's when he came to see me in San Francisco because Zubuntu participated in the Google Code in about a year and a half ago. And they sent a bunch of mentors and mentees to San Francisco. And I'm like, I live in San Francisco. You should come see me. So we went out and did San Francisco things. We went to have some chocolate ice cream and did a lot of walking. And did we ride on a cable car? I think we must have. I always take people on a cable car because I like the cable car. Anyway, so we've gotten to meet lots of really awesome people and work with really great people. And the project is largely distributed between Europe and the United States. We've got some contributors here and there elsewhere. But it's really exciting to be able to come to conferences and meet up with our colleagues on the project. And it's been rewarding in a different way than just seeing people use Zubuntu. The project ends up being really tight-knit. We have an off-topic channel where we talk about board games and cats and beer and all the fun stuff. So there's definitely a lot of fun to be had on the project as well. And I think that's also part of what makes it a success. We're all really invested in this project. And we care about each other, which is nice. So, let's see. We've got about 15 minutes for questions, if anyone has any. So the question is about the strategy document. There's a section in that which says not to use heavy libraries. So I think... So one of the things we've done to determine that was we look at dependencies. So not just a single library, like the size of that library, because that doesn't tell you a whole lot, but how many dependencies it pulls in. So the typical use case is someone wants us to ship K3B. That's like an ISO burning and a disburning tool that comes with KDE. It's awesome. But if you install that on Zubuntu, it pulls down like half the Ubuntu repository. So by saying we don't want heavy libraries, we don't want heavy dependencies, and we don't want libraries that are really big and going to bring in a whole ton of stuff. Because it bloats our default ISO. And it also means if we're running any KDE services on Zubuntu, it makes it from boot up. You're already using more resources. I think that's pretty much where we were going with the heavy libraries thing. Where did the mouse come from? I think there's something about that on the XFCE website, but I'm not entirely sure. I love the mouse too. I'm a big fan of it. Yeah, it is super cute. I love the mouse. But I think there's some lore in XFCE somewhere, but I don't know it. And we just adopted it because we're like the distribution that runs XFCE. So any other questions? Michael? How do users get involved? So you can go to Zubuntu.org and there's like a contribute page or like a join. Let's find out. Let's see. So Zubuntu.org, the community, you can contact. Uh-oh, this might be hard. Get Zubuntu. Oh, here's development. Here's get involved. Okay. We probably shouldn't put that on the development tag because if people don't want to develop, so. All right. So we talked about development and then we talked about other ways to contribute. So you can develop. That's great. But if you want to do artwork, develop documentation, marketing, QA, we have all these links to places, quality assurance. Yay, these links work. Okay. So anyway, go to Zubuntu.org and go under development. And now I'm going to chat with our website guy about why we put that under development instead of something like the community. So once you're contributing, can the Zubuntu Council grant membership? No, they can't. Would they like to? I don't know. I'll ask them. You can get a Zubuntu membership. So a Zubuntu membership is how you get like your ad and you get a bunch of these like perks in the community and perks from some vendors and stuff. Sustained and big, I forget what the wording was, but big contributions to Ubuntu, but Zubuntu does count. So then you go in front of a membership board or you go to like the Kubuntu Council. They actually do have the ability to grant membership. And then you show off your contributions to say like, I did all these great things. And they're like, great, you're now an Ubuntu member. But the Zubuntu Council hasn't really taken that on as a thing just because they're new and small and maybe they'll want to. Because the Ubuntu contributions do count. I think there was a question up here first, did you? Okay, go ahead Nathan. Next 10 years. What does the X come from? I don't know. I don't know anything about X of C. It turns out. What do you go from X11? I will get to that. Next 10 years. I don't know. I mean, one of the things that Zubuntu has sort of pride itself on is not leading the pack. Like I'll show you here. This is the bigger menu. And you'll see in the top there, it's got a place where you can type in something. So if I wanted to launch GIMP, it just types it in. But people hate that. They wanted the menu here where they can click on things. Thankfully, whisker allows you to do that. So if you want to go into graphics and figure out what kinds of things are, oh, good, that's nice. You can actually still search the menu. This menu is like the mother of compromise. It's not just a searchable unity dash. And it's not, it is something you can still navigate. But when we introduced this, people were so angry because they don't want to do the searchy thing. They want to click through. And they didn't understand how to use it at first. But we did this way after unity. And so we had half the community being like, I hate change. We're like, you can just put the old one back. We just changed the default. And then the other half being like, I want to just search for my applications. It's more natural. We're like, now you say it's more natural. Now that everyone else is doing it, even Windows does like a searchable start menu and stuff now. So we don't really want to go into the pack. So I think we kind of just the next 10 years, we're just going to continue listening to what our community wants and sort of staying a few releases behind the greatest innovative thing. But that's kind of what our users want. It's what I want. I don't want to eat. This is my desktop. I have work to do. Just don't mess with it. It's fine. Right. So moving on from X11, this has been a big topic in Ubuntu itself and in the KDE communities. We're going to do MIR, we're going to do Wayland. We've tried to stay out of that giant controversy mess. We're like, if it's good enough for Ubuntu, it'll probably be good enough for us. But we also like playing around with things. I mean, our group is made up of a bunch of geeks and we like playing with things. So I think it was before the LTS. I think it was like 1510 release. Canonical was really trying to push MIR. They were like, we're going to get MIR out. It's going to be in the LTS. To be clear, MIR and Wayland are like the next evolution of X11. And they're somewhat competing. Canonical's working on MIR and everyone else is supposed to be working on Wayland. It's kind of unclear. These are kind of the next iteration. So Canonical really wanted to push MIR. They were putting out testing ISOs and we're like, let's make one of our own. So our community went out. One of the people on our team, he made a Ubuntu ISO with MIR and we put it all over social media and people were so excited. A bunch of people started testing it out because they were like, I can finally try MIR in a really simple way. So we collected all this data about how it didn't work. And our work in the Ubuntu project, we were told later, actually impacted the fact that Canonical didn't end up shipping it with the LTS. Because they hadn't really done what we had done. They reached out to the community and they wanted people to do tests. But for some reason we were just much more successful at getting people to respond. I think because we made it super simple. It was just download this ISO and put it on a USB stick and go to town. And I think we had tapped a part of our community that we hadn't really reached out to before with trying something experimental. Because we hadn't done that very much. So as far as where we go with X11, I don't know but we've been playing around and we're willing to go either way. Again, we'll just follow the pack where it goes. How much do we do it lead to what? So the strategy guide and how that led to the G music browser being kicked. I sort of tuned out at that conversation. I use N player on the command line. I don't really know. But it was definitely a huge part of it. We had someone go out and evaluate all the popular players that were out there. And then we did slap it against the strategy document and say, listen, what do our users want? What are our goals here? I don't remember the specifics of how that was decided because I was like, I never use any of those anyway. My MP3s aren't even tagged. So every time I load them up in one of these things, it's just a giant mess. So the question is, Zubuntu and XFZ, he's really based around GTK. Whether it's on GTK3, I think they've mostly finished that transition. It was halfway between for quite some time. Yeah, there was a lot of breakage between 2 and 3. It took us a long time. And I'm pretty sure we're all the way there now. I haven't looked closely. It took a while though. It took several releases for us to make the switch. And our themes broke along the way. It was a big mess. I think we'll stay with GTK in the long run. Probably. I think that's where we're going to be headed. Michael. I think in addition to being somewhat light, it's not the lightest thing we can use. Alex D is written against, I think they're using QT or something. Yeah. There are lighter things out there you can use. Because the maturity of it was also a big thing. We don't want just fast, we want mature and simple to use. It gives us all the hooks that we need to get into things, and it's also pretty quick. It works well enough for us. I think it will continue to do so. The other thing is, as a small team, even if we found another framework that was so super awesome, I don't think we'd have the people power to switch over to it, honestly. Adding on I3. Probably not just because resource-wise. Unless someone came along and was willing to like, I'm going to own this and bring it into the project and do this thing, we may consider it then, but yeah. Just probably not as a default for us. Alright, so any final questions? Oh, I have to give away my books. That's exciting. Alright, I want to see who tweeted about my talk. Did anyone tweet about my talk? Who I don't know. So these are books about Ubuntu, and I'm really excited about the 9th edition of this book because we added a new chapter on devices and conversions and stuff, so it's actually a whole new book with the 9th edition. Is there anyone here who doesn't use Ubuntu yet? A new person? Got a few new contributing people here. Let's see. Okay, Michael tweeted about it, but you already have the book or you've had a few copies. Alright, well I saw a couple hands go out, so I'm just going to come around and give away some books. But that's it really. Thank you for coming. Thank you. Thank you. Thank you. I'm not a fan of Google, I'm also not a fan of Google. I'm disappointed. They've been a really awesome job. I think though, they've been doing so much, they're kind of fortunate to know that Ubuntu is so interesting. They're 90% close to it. But it's been helpful for like a year or so. So it's kind of how you get on the block with Google. So it's anything that you really need to do. It's kind of a weird thing to do, so I think, you know, about 15 months of checking them all out about the reaction based on anything, whether they were babies, whether they were things that were close to the corner. Everywhere else, it's a huge issue that we have to deal with. So I think this checking of blocks, quite a good one, I think it's awesome stuff. So we don't know. It's kind of, when you talk about features and predictions, people like us and we don't know anything about that. So let's look at it before we come to a given area. It's kind of, we've got an engagement on those data, that there's no pricing, no appearance, like on this, there's no special features. There's a specific stuff from a girl that I expected to know because people have got a tax for girls on any of those languages. So I thought that was a good one, which I know is a good stuff. So anyway, we're going to look out for this. Other than that, there's no one I should talk about. You'll have to function level. So I just agreed that I should watch for it. And they have their own services and they'll try to reach you at the point of the end. So I think a couple of things that I would like to know is taking trigger from a product and store changes your function and takes that from the user. It uses the original 2000 year, and it has a caption on it. So it's a lot of information. So that's probably the problem. Again, not so much if you're not a developer, but you are a user, or you are a company that you use in the product. It's functionally using today, but what's there? It's like a one-to-one decision. So we've kind of done it with other products, which is the true service. Now we're going to talk about that. There's still a server list for someone, right? There's some developers that can not handle it, unfortunately. So we have a lot of users who are using this. I don't know if it's a user in the service, or if it's just like a one-to-one client, but they can handle it. So I don't know if it's a user in the service, or if it's just like a one-to-one client. But again, you won't find others. There are some very open-wish that's been around around all the ethos. Traction is one of the most important projects we've ever done. It's kind of running both in the market and in the developer relations. So service solutions, kind of a question. Again, a project. What's the reason behind the project? People familiar with other kinds of projects that come with the foundation of our foundation project. We have incubation and top-down projects. So I explain it up because it's currently an incubation which is a cool project. In fact, this incubation, all that means is, maybe I was talking about business, it's not really a program. It's like a foundation that puts the students back and calls incubation. It pretty much means that, hey, we've got trainings from our foundation project. It's actually comparable to the community that stands on its own. One company and one person can go away and do a lot of business-critic projects at any one time. I mean, it's obviously part of the center of use, but it's awesome. You've got to get a good job. There's a bug. It's a little bit of a problem, but anyway, a couple of reasons, even though it's not that kind of camp, there are tons of issues with it. And most of the issues are right now. I think that's really the only reason it is... They don't have a partner group, but they don't want 80% to 100% to be paid for an active project. And so MNZ uses its interest because it will hurt. So I think that would be a good thing. And I think this is like the L.I. center, okay? Yeah. Steril is what we have just been on for a couple of years. So in the developer, Steril is what there are a lot of people that everybody's talking about. It's Steril is for you, but it's for you as a craft. You've got a few billion of ideas in terms of how to deal with it. But it's not in here. It's in here. You've got this, someone in the board, whether it's you or the board, but it's kind of joining the piece a little bit. It's just kind of a big thing. So the plan that you can go to a lot of detail on the future of how it works and how it leads to the development of what is the most function-based and programming. We've already kind of started to add not only not on one project, but on the other project. This is based on how we deal with it. This is what it's all about. So this is kind of like our methodology. There's schools in which there's a language like this and I think that's what it is. So how are we going to deal with this? They have been a cool project that has been as I remember, but I don't actually think like color, but it is a think all of the colors of the colors of the sky. It's kind of a new product for the rest of the communication within the kind of cluster. But that's kind of like the range of the operation. NGNACs, they basically say if you're in some NGNAC that you're very specific to creation, you don't always have to do that. There's a web application, a router, kind of a caster and all the rest of it. It's just kind of like that stuff. So they're like, hey, we can do this same thing. You can do a cool proxy drive for the NGNAC depending on the controller that is triggered in the console and reading and writing speech and maybe the touch. They don't have a writing show in this company. It's similar to what it's created to with a circle up there. And that is just because they're in the message of the product. The product is pretty awesome to talk about these pieces. The nice thing about this between the touch console and the other console, probably for our very own NGNAC but NGNAC's console, all these pieces and then the ability to do is when the invocation comes in you push it into the top and the extension comes in the cube. Whereas a lot of people who just talked to the SQ would have more users that would be sure they would have a system to process specific data loads from the creation process. They're just using it in a way to see how this creates the level of quality and the level of console. The console is a doctor who knows what the system is. You know, in a hospital they have these filters that are written on the nose and much like how we've heard that maybe it's taking a few minutes to do a call. There, that's a little bit of a bargain that the revenue doctor can make to make the rest of the product but hey, we need to take this test that the job has been defined to run this container with this function and it makes sure it's not that it will be cashed from the machine that I'm going to be using to perform the cash. So, the main focus of the update and I don't know how many of you just wonder if it wraps it around or if it passes back to the console or it passes back to the controller or back to the response. So again, this is kind of what we're going to do again. You know, who do you know that people are talking to at this? Do you have anything to talk about? We don't have another term to ask where you want to go. These two in particular they're all like human-style and they catch calls with certain things to do to make the rest of the product. So, it's very kind of a game to do. Kind of a syncing on how to go again. They're kind of sexually serviced. All these things that you don't want to know, you know, again, this needs to be talked about. But, at least you have to be I've already mentioned that it's because you're looking in not only in Amazon or Google or any other it doesn't make a pretty big assumption that the product service is talked to as exclusive to the company. That being said, because there's no such product service for the customer, I don't know all about my head but I think you hear the hardest language, I think it's very, very important. So, people are very important because they're so much provided with this product. It's something pushing the slide. I think it's also a first slide as we're talking about that. I don't know how it is but you know, it is still is. So, two things that we're talking about is that you know, there's one machine thing that I found that we had that was solely for the customer. And while I'm not talking about the customer, it creates itself as an accumulation with the customer appreciation for the customer service. Based on that accumulation of the customer service, it's simply for us to run this product. So, that is the most important thing to do with the customer. I'm going to give you a talk about this. So, when you set up a vision, you mentioned it's pretty simple like a couple lines of execution for a layer of vision hacks on top of Q&A. One is on layer, the other one is something I'm curious about. Part of the environment is the Q&A method. You write your Q&A method plus the Q&A method to your product and you then say vision is one of the most important things for this person. So, now we're going to be dealing with if you could say Q&A method. So, again, trivial is something I hope you know. Everyone pretty much works on this. And, again, it's as simple as it gets when you can, when you think about how much it's supposed to be. Obviously, this is going to be a long one of these functions, probably a part of the function by the way, but I think it's kind of a very small vector so that is it. Questions whether this was talking to you or you were interested in answering any questions? So, how many or are there these on this talk? I have a question. The Google Container Service that Kink runs on Kubernetes. Yes. So, the Kubernetes is really going to be a little bit more accessible. So, if you could run Kubernetes natively in Google you can run it with Microsoft as the object Kubernetes itself in case you think it should be. Amazon has this guest which is its own thing. I don't know for sure and I don't have an expert but the solution is probably with the one vector just one or the other just go out and run it. It's just everything is really cool all the way to Kubernetes. If you're going to be in a shop it's going to be a service and one of the ways that it's going to be. So, you can you can you can start with Kink or Kink. Oh, no. You have to personally you run so if you have like Kink a lot of time this day you just as a business friend you have to learn how to get the security snacks. So, for us it's kind of like we have people like in a live environment it's actually just push by many people as much as we can. We scan our documents and we have a lot of time. Then it's going to be there just about 40 minutes. If you're in Google you can do that for a while you might have 40 minutes from your time to work as far as I know you don't have to be in any discussion. That makes you do thing else to try to do some malware You don't have to go there So, it's quite taking just like a few years. And so, if I change management perspective, if you want to, if you're getting a ton of requests, oh shit, I need to scale up. I need to scale up. I need to scale up. I need to change this. And the next tier up is true service, which Lambda, Azure function includes a lot of functions. You have to, like, Apex that you don't build a scale really, you don't build changes that you did. And one thing you say, this function is apparently just recorded. So, if you get a flood and you want information in theory, it's taken care of for you. At least that's what they're saying. I've never gotten zero-to-one, it's gotten faster than I think it is. But supposedly, they keep it all up, and it's not too late either. So, kind of, if you want to start to scale up, say, if you have a full DIY, if you work with a stack, rolling it on a question, you can change service. You don't have to do the base stack, you don't have to change management. You can go above that to true service from the first part of it. Now, someone can run it. You don't want to ship it. If you're like any other shop, you can kind of run it with sort of stack. So, anyways, they have two big finishes with that. They'll spin it up for you, and I'm not going to run my management. I don't think you can handle the money and you can run it in self-management. Imagine a global service solution that you have on your phone. So, again, it's like, if you squint, at least we can talk down to the developer, it's all sort of this long, it's the same interface, and it's all very much the same. If you're a network engineer, if you're a store shop, if you're an ops driver, all the firm, you're looking at them from different points. Depending on where you're being prepared. And I think they're going to change management in that field. We have a lot of the lowest level, and we still have some of the top-level, you know, top-level being pure serverless ops drivers. You get the same thing I mentioned earlier that talks about, I don't know much about the service, but if you're a fan of it, you're going to run it for you. Yeah, that's correct. Yes, you can do that a little bit less. And then, so again, there's always this kind of lock-in. If you do not want to say, who made this? Who deals with work? It's totally talked about in 15, 200 years. And that might work for a lot of workflows. The biggest one in one workflow is, there's a lot of that in one platform, the shape is like clearly locked in here, but in the beginning, you kind of have this inverse one deal, instead of the one that is the inverse one deal, you just want to be able to understand that people are kind of into it. Do you over-publicize it? Is that what you're going to do? I don't know. So there's always possibilities. Yeah, thanks everybody. And if anybody, all of the mail messengers are sent out, so you've left something to tell you about an hour and a half, so open up the emails. Oh, okay. So if somebody hasn't gotten an email, or maybe an email, send it to the LAZ about when they do... Just come up here, can you, or just come up here and you can just. Or do you know. We're just even busy (?) We'll leave a link from the ration you're up here using Lounge between one hundred people will be running until the day Okay, so originally, since you can imagine, so they at least, okay, thank you. The PCT and the standalone. So, I guess we actually, you know, you have to kind of go on there. It's never, I don't know what you're going to do. But you don't have to say anything. You're a certain thing. Okay. So I say, it's like finding a little bit of a, or 80 on 0.0.0.0.0. So I go 0.0.0. Which? Mbinski at qnet.com. Okay. No worries right now. I'll put it in for you right now. All right. Okay. Yeah, yeah, that's actually, yeah. I just installed, is that a PC there? Or is it a scale PC? What is that? What is that Fire Ember box? What is this? Sure. You got some paper? Here? You have any paper? Or what? Paper? One second. Potentially a question. This is what camera, the video, okay, very cool. So it's basic, it's a computer. At the end of the day, with running a stream capture app. You know what, wait, we can do this, we can do this. We have paper, we bring that, we bring paper just, you know, it's amazing what analog will do. Yeah. Sorry. No, no, no, no, no. You're up here, you've been here all day, doing great work. Thank you. I was probably was. I'm sure, like as soon as you gave me the URL, I said, let me do this while I'm listening. Let me look here for somebody to be up and see how you did. Yeah. At qnet.com. I don't think I'm going to make sure this is mvnsky.com. Correct. Okay. It'll just get an email within about just spin everything up to 15 minutes. All right. Is the lab just something like, are you going to talk us through it? Or should I just hang, I can do this anywhere from within range, right? I saw that, yes. So we don't tell you much I'll tell you what, I installed get Docker during one of the second iterations, one of his talks. That's the first time I've touched Docker. I ran the NGDX, right? With the local host fucking won't run. I can't find shit. So I look at it. So I said, well, Docker help, right? Engine image container. So I start playing around with those permutations and finally I say, okay, so there's a container with there's NGDX running or I can't remember what it was called. But it turns out there was a port command to show me which port it was running on and then it showed that this action out local host somehow didn't install it in zero, quite dupal zero. So you put quite dupal zero in your browser on a Mac, running you something Docker, blah, blah, blah, and it pops up the NGDX. So it's just a little, you know, I have to put that up on stack overflow now. The one guy said, I want to install this dude, I said, Jesus Christ, it's okay, let me do it Yeah. So yeah, when you were telling me all those things, I'm sort of like, I've taken notes but I'm still kind of grasping with the vocabulary and notions right now. I think fire hose and that's the way to do it. And then eventually eventually you do that eventually you retain more. Your confusion factor goes down in your retention. I always learn more by just hands-on learning. Oh yeah. You guys gave a lot of good kind of seminal points and pointers and websites and notions and vocabulary that I can group of and look for and start to tie together myself short. I went for PhD in leading I mean the only way to learn stuff is to go to the universities and get to universities like that. I was in the 70s so I totally I remember living at UCLA's biomedical library until the Folklok midnight because they had the card cattle. Hey, Jesus Christ, you had to go up and pull this journal and some bastard would raise it out the article. It's like, oh shit, you have to go to the reference librarian and check it out. You only got two hours so you can get the Xerox machine, five cents for paid. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Well, this is a better venue. You speak closer to LAX, I mean, I mean, there was a there was a Carl's Jr. down the way. We're coming through. Oh, okay. And so that was we didn't have to deal with 101. Yeah. This is great. Yeah. Yeah. I grew up there. So I know I were just down the street from Kaiser for a long time. Was this area, my wife grew up in Westwood but she was saying that she grew up in the 50s that this area had pretty bad air pollution is much better now. Oh, yeah, I mean, because I guess the San Diego mountains were just trapped the for a minute was the same way. I played football in track in high school and we had with smaller things. There were times when you could stand here in the valley you wouldn't see the mountains. You could not see the mountains. It was just this everything was a spray. Okay. So let me make sure. Yes. I'm sorry. Michael. Yeah. Yes. Michael. Yeah. Yeah. Okay. So just so you know, I think it's kind of the I think, I think the Russian spelling is I think the Russian spelling is I think the Russian spelling is I think the Russian spelling is I think the Russian spelling is I think the Russian spelling is Ok. Mine's horseshock. They're aside the curtain. Do you need any email? All right. But I think they're evolving to like the direction. Yeah, I mean, I guess, well, you know, we were, I came from a company that, is still in the process of making lead from physical to virtual. Although they've been virtual for, they've had a lot of virtual stuff and now they're trying to do some sort of heterogeneous cloud. You know, it's funny, we're in a small company, it's not private, or yeah, I don't know if it's private or not, what would they do, there's, it's, you wanna talk about the incestuous rats and the stuff of fucking conflicts. I mean, I remember sitting through these classes about all the, you know, reporting conflicts and stuff, or at a time like some of the people would have like 88 zero of their relatives. I mean, okay, so the Trump administration has got to be on public counsel, and this is 80% of what they're doing, what the hell is this stuff? And it's like, they're just, it's, there's so many new, just things you can, the politics are like 80% of the job is 20% of the work, so. We're talking about private companies, I mean, we've got private companies that were, no, private companies finance by somebody who has a very big wallet, and there's no incentive to see it, because you can keep on. Especially if you're a friend, especially if the guy with the big wallet's your friend. So, you know, you're gone after your child or something, but, yeah, you can kind of, you can kind of exploit that a little bit too, you know what I'm saying? But what I like is, I would just start an environment that you can afford to use real asset tests to set. Oh, yeah, yeah, like, we're gonna have to, we have to make, we have to, let's say you have to make this demvow in six months, or you're dead, you're dead. Yeah, I worked that, I did that in the Air Force too, for like, in Kalaki, I worked both sides of the country. That was my, that's where I worked, I worked at the Muckay Ice Center, and I'm now working on it. Where? We were on Sand Hill Road, you know, we weren't even studying it in the Sand Hill Road, I was like, I need you to come to the mall, or we're working on a big project with the Navy and the Economists. Okay. And, I mean, we just got very, I only went to the lowest level of clearance, so we had no idea, you know, they would, what you were doing. You know, we have no context with our stuff that's working, but it's kind of using artificial intelligence to supplement the kind of control, you know, the base control. Oh, yeah, yeah, yeah. On the submarines. Oh, I did ASW, yeah, I did the submarine warfare, I did that in Burbank with the P3s, and the Vikings, and you know, the Sonoboys, and we had actually, I did some AI work and list with detection algorithms on some bollocks. Oh, okay, back in the, oh yeah, I'm expensive as, I mean, it's like, crazy expensive, crazy expensive, yeah. But, yeah, I had, I went all the way up to the top with the clearance stuff, I'm glad, I'm glad to be out, that's, you know, just the whole, well, one of the last things I worked on was a gunship, AC-130 gunship, and I don't know if you've seen, there's a YouTube video about how this is just cross the fluxes group of guys who may or may not be calling carrying rifles, and so fuckin' what if they are, I mean, you know, I have an AK-472 that I go down with a gun range and shoot, and it's like, I just target practice, but, I mean, it's, you remember what they call cognitive dissonance? Yeah, sure, sure, right? Right, right, I mean, you know, you're, you're, you're, you're, you know, God, God, corn, country, and all this stuff, and you know, you're, you know, you're, whatever, religious health, indoctrination you've had, or whatever morality you have, and then you're working on these systems to kill you. Yeah, I mean, it's, it's, it's a constant conflict, I mean. I mean, when I was taking a job, I was thinking about, you know, what are you doing, too, but it's, I mean, it's, yeah, it's hard, I mean, it's hard, I mean, it's an engineer, you know, you go, you go, you go, you go. Exactly, you worry, exactly, it was, it was fun and cool to work on this stuff, and I worked on TARDY and weapon systems, displaying control, a lot of flight test stuff. It was, from an engineering standpoint, is good, I mean, I worked, I also was a medical researcher, so I started out, you know, in Reagan here, from medical research, and then after Reagan, it was like three, the NIH and NSF were like a 30% of the pre-regions spent on spending, he just, he clustered, fuck, the whole science thing. I mean, I guess God got even with him, because he got Alzheimer's, and he said, well, can't we just turn it back on? He's like, no, dickhead, this is not a fucking bowel. It's okay, it's like you've just destroyed a pipeline and a generation of scientists. You're going to have to rent it. You think that's gonna happen again? Oh my God, I can't imagine how bad it's going to be. I mean, okay, my Machiavellian fear is that, and I don't know, this is conspiratorial, where does this logically go, but you look at the Koch brothers, and you look at the, you know, they fund, they fund, think tanks, they fund, they buy politicians, and they fund advocacy groups, okay? So they have this really all-encompassing, multi-pronged attack. Yeah, yeah, yeah. And I mean, and the 9.5%, I mean, I'm not an economist, so I don't know how to really cook, you know what I mean, both sides can say, it's hard for me to believe that 1% of the population has 99% of the world, you know what I'm saying? But I mean, I mean, it maybe it is, but let's just say that it is, okay? If you look at the Trump, if you look at, if you kind of, so let's just say those are kind of like quasi-bactuals, like a point of reference to start a conversation. If you get rid of healthcare, so to speak, if you get rid of education, and you militarize the police force, and you military, and you diss the communication like these do, you create like a pro-deterian that is replaceable, get to 50, 60, dot, fucking dot. We don't need you anymore, you are spec, you are news, you are next, right? Because you're gonna reproduce, and you're not gonna question this, you're not gonna have the intellectual tools to say these five disparate dots, you won't be able to connect them, you won't even think. I've been talking with the United States. That's really the story. The DNA to not, I have a lot of friends who are Russians. It was really interesting to quite ask him, I'm like, yes, what do you think about food? And he could be a very, very important person, but that's not all for us, our reference point is stop. You're still a pro-deterian, you're still a pro-deterian. So, I mean, there's no cynical, it's like, I think it's in our DNA. Oh yeah, right, Russians have a really, really cynical. Oh, but they're humans, but they're humans. Yeah, it's a, Tolstoy, right, okay, I mean, they got it, nah. Well, okay, just wrap your mind around, we need to treat 3,000 people in one hit. It's not a good fucking deal, it's really not. I mean, compared to what the- I think her, as a portion of you- Well, if you just take, just take, I was saying it's a talking point, okay. Your goal is militarization and repression and surveillance. Isn't that perfect? I mean, now you and I can do it, anybody, if you go to Al DeZero, if you listen to Radio Havana, if you, God, I mean, who knows what, right? Do you think there's somebody, I mean, I don't know if he saw the news today, but Jeff Stesson is confused as well. Did he finally get, well, he's- Well, did he, you know, he heard her- He did, he did, oh, I think he did. So I think the Republicans are giving Trump a little leeway, but it's good they're not making it too far. Well, I think he's gonna be like a bad dog yet. He's on a long leash, but people are saying that Stesson can be analysis. Eventually, it's gonna be, even if they don't care about America and or the Republican Party, and it comes down to, this is God calling country right now. At the end of the day, they're gonna save their own hands. Yeah, well, and two, it's the most benefit of trade, and it's creating a barrack, so, you know, I think it's one of the most, I'm disappointing both parties in trying to understand trade, and it's a really complex issue about, you know, and I do believe that it has to be a fair trade, but I think there's no, there is a global economy, you have to compete with it. Well, my view is that you have to compete with it, and you just raise the safety net to provide for people. It can be more, too. Well, but I think the thing is is you and I can not compete with Mobile in Bangalore, okay? You and I are not gonna look for $5 today. 14 ounces, not 14 ounces, that's all, we're not. Yeah, I mean, and just like they say, well, you know, these Mexicans are taking all the jobs, you and I would not be able to, because we're old enough. Oh, you know, I've something to tell you. You know, to the fixed boundaries. Well, we're not, so we have my team, our engineering team in Sierra Able, and not because we were looking for Sierra Able, we try to find people, so we're trying to find people in the Bay Area with the skill sets we need. Being a startup, you couldn't take more than like two, more than a month of training stuff, I mean, we can, I mean, right by Stanford, just Berkeley, and so the stuff we needed, well, in this case, we needed to do the puppet, and some just very more pragmatic skills, and they, I just want to kick my son's big knees on the grass, they're way, they're way behind the technology. Oh yeah, oh right, so I remember, I actually think it was here, it was in Carney Mell, who knew Chef Puppet, and I was going, oh, they taught that at Carnegie Mellon's, and no, I didn't learn it on my own, so. You know, I think that they come, there's a big, there's a big need for skills, and I think there's, I was at Cisco for a while, and I would love to hire in the Bay Area, but people didn't have the skills, and really, those guys, I'm sorry, they weren't good at skills in the near future. They have more applied skills. Okay, interesting. Yeah, they were very applied, they were, yeah, so I think what I'm finding is that a lot of jobs are very specific skills, they're very, you know, it's a hot tech, but right now I get, I mean, if you know, Amazon, you know, Docker, you know, serverless, there's a lot of jobs there, the thing, it changes pretty fast. Oh yeah, it's, yeah, VMware was a couple of years ago, right? Yeah, it was, yeah. So yeah, interesting. Oh, yeah, I'll take you up there on the stage. I couldn't find it, I had no, this is like a rare point, I'm a coffee addict, I have no coffee today, and I try to go over to that, I remember when I saw that photo. It was close, I know, I was so, I know, I was like, so, you fuckers, you're an expert, how do you keep your franchise open? Let me double check it here. I'll tell you, if you had said it was true, so you should get an email. It could be your stamp holder, but I didn't remember your email. Yeah, I know, it's interesting. Of course it's gonna be a couple of that lab, and so maybe we'll just set up, could any of you, what's the theory of that? I wanna know what's right now for the time you're in. If you've missed it, let me know. Yeah, that's it, but we'll figure it out. You know, we'll just get a look by Geeta, and figure out what we have to do tomorrow. You know, it's like, I don't know, we'll figure out what we have to do. Yeah, can it all set up? Yeah, but let me figure it out. The only problem is, so there's been a number of different views as well. You will face that. But yeah, that's been at work. So I couldn't really message it, but the IEB users created two different IEBs in the same name, so that what always happens is we send a message that's got background, email, that was still on it, and I knew it was gonna be managed, and I had a million of people that was down to consider it. And I couldn't do the program, it was just stupid to say I didn't know what it was. The server couldn't start it, so the ports couldn't use it. But the way I got it, the arbitrage there allowed me to start, so we got it. We sent a message to us. So it both came to the press every time I kept again a little bit of a problem as the IEB user used on the platform. Created it, and eventually I found it. It's like a couple of different ways of working. Like I said, we'll just let you know what the goal really is there. Okay. Good. The direction to do the document, how do I resolve it? No, I think it's a bit more, to give you more examples, and we could just follow up with you. It's not really, you can't like it, it's a good amount of time, if you want to buy it. How much money do you have? There's a, there's a lot of, like I said, a couple of months. Yeah, do you have a lot of money that you could possibly pull through time? Yeah, they sent me a box with a bunch of shirts. I should probably ask that for more. I set them out at every meetup, and literally every single one is wrapped. T-shirts I tried to reserve for people that are speaking, or that have done something. The stickers, I lay them out all over the place. T-shirts and blue ocean is like, on the precipice, like going one hour. Yeah, some of the stuff goes with it. Not in a big suit. Check this out. Check. Infinity power. So, I'll touch it. Oh. Let me get a video encoder. Okay. That is custom. Damn. Oh man. It's a clearly 3D printed piece here. No, no, I know, I was just looking. I like the chase. How's your day work? I'm actually not gonna connect to the presentation. I'm going to quote you forever now. In, no one in this room hates Jenkins more than me. From your talk earlier. But I do do a lot of characters. All of you, you have to agree that we just update. Did anybody notice that box? Yeah. Switched up. Do you agree? Follow along. Are you getting ready for this? That's right. I got him. I did. I said it was the last one. No, me neither. There you go. That's right. Follow along. I'll make one last follow along. They knew what they were doing. They knew what they were doing. Yeah. Yeah. I don't know. But that's why they're not here. Follow along? All of it? All of it? All of it? All of it? Don't. There's a brewery. There is not a brewery but there's a case here. Right over by here. That's where they're all at. So that's where you have to compare yourselves. I can't see the green wall so if I find out, I'll just fly through the right way. I know, but it needs to change the red balls to check north. It does look different. Well it basically is check north. No, no. Check north darn around. Yeah, see what they did, they hacked up the KVM and managed to switch for it. Yeah, so much. Yeah, it happened. Oh, yeah. He just recently called you guys. Yeah, yeah. We got Wolfgang and Casey, you guys. Oh, yeah. Yeah. Yeah. No, I mean, the hotel is registered in that foundation. Test. All right. Ready? All right. We showed up. I really appreciate it. This is actually the first jam that we did this year, 2017. We are doing a couple announcements. So one of the things I wanted to do with the jam this year and something that we did last year, I thought it went really well. But one of the things that I'm trying to do this year and if anybody would be interested in participating or volunteering is I want to do more advanced topics in our user group. So not to say that we haven't done great topics, but I am, as always, looking for speakers and people that are interested in presenting or have unique use cases or doing something special with Jenkins. So if that's you, please come talk to me. We are doing another meetup this month, actually, at UCI. And I really like the idea of doing one at UCI because we get to interact with people on different levels, everything from students to professionals. So this is probably the only one we do in Orange County. So if you're close to Orange County, come check us out. Come on, bro. Zots, yes. That's this guy. So we can flash his graduation picture here in a minute. We started my talk of highly effective Jenkins users. This is a community talk, so I am not the only person to have given this talk. But all of the information in it is pertinent to Jenkins users. So I will get started. I'm not going to rush through, but I want to get to Tyler's talk personally because I want to see what he has to say about all the new things that are happening in Jenkins. So it's also a little bit weird. I typically like to stand up when I'm giving a presentation, but my computer is a little bit low. So I'll try to make the best of it. So we will get started. Oh, look at that. Yeah, maybe we'll just turn a little snitch off right now. And my screen is too small. Any connection forever. Hopefully that doesn't happen again. Do this. So I think we're good. All right. So this talk is talking about large scale Jenkins instances. Obviously, I think the number that I heard today was the J1,200 plugins. Yeah, so quite a bit of plugins. And to real world or is a practical talk. So these are things that you could actually employ in the workplace. With that said, obviously, different people are going to have different variations and your mileage may vary. So most of the talk is for people that, you know, as opposed to you're playing with Jenkins, these are Jenkins instances that are in large scale production environments. So have it one. Make it stable and restoreable. That's a big deal. So being able to, so like one of the things that we do is our master is essentially a folder. And we use Docker to do our upgrades and all that stuff. So being able to replicate your master is a big deal. I recommend people that are using Jenkins in the workplace. Definitely use LTS or you'll be upgrading all the time, which is not bad per se. But if you're managing Jenkins, you don't want to upgrade every day. Reach LTS line is updated about three times. Obviously you're avoiding bleeding edge and LTS goes through testing and acceptance testing and probably regression testing. And I seem to have a pretty good, I mean, we upgrade, I think from 19 to 32 and it was flawless. I don't think anybody noticed anything. So Jenkins has been LTS for about eight months. I believe 323.3 was yesterday. Yesterday. So if you are not using LTS or if you're on Jenkins one, there's a lot of big improvements and you will be happy that you did that. This is a big one. Obviously people with 1200 plugins, there's probably a plugin for all of your use cases and everything that you want to do. I have to be careful with this one because I'm lazy and I like, hey, we'll install a plugin. So yeah, I started trying to curve myself of I want to install plugins that are going to be the most useful as people are moving to things like Jenkins file. I think that we see a lot less need per se for plugins doing all of the lifting for you. So be conservative. Make sure you're when you're upgrading them, you're not just blindly going in there and hey, there's like 12 upgrades here. Let's just do them all. Make sure you're smart about the way you're doing. Anyway, there's so many tools that integrate with Jenkins and you should be using all of them.