Hello, Naglian, Tom. Right, a few notes from the starting. Right, afternoon all. I've just shared the meeting notes link. Okay, hopefully you can all see. So, yeah, first item to note is that the events on the 17, the calls on the 17 and the 24th will be cancelled because of KubeCon and recovering from that. Also, worth noting that for those of us who have a clock change savings time change next week, the call will be moving back an hour to its more usual time. I think probably we've spent a lot of time on the last couple of weeks going through the events. The one that I think is worth spending the time on is the informal buzz of the feather session. So, there is an issue in GitHub that was raised. Excuse me. There's also a discussions forum. And there's also a form which people can fill out if they are interested in attending and whether they've got a, you know, an item for discussion or not. I haven't seen the latest numbers, but I understand there's a few people have signed up, which is nice. I don't know if Taylor or Lucina, you've got an up-to-date view of how many people have signed up for the informal session. Good morning. Yeah, it looks like 12 people have responded so far. So, feel free to share the form with your community, especially those who will be attending in person. Yeah, absolutely. Thank you. So, I don't know whether either you or Taylor want to add any more about whether there's any further input you want to help organize that with just in case you're sharing the form and the details of it. I didn't understand the question other than the form, the organizing part. What was that? So, is there anything else you think we need to run through today on this call in terms of shaping it, organizing it, or anything else? Or is it just a case of us sharing the form within our communities? Well, I do think we should organize it. I don't know if to organize it some more. I don't know if that needs to happen on this call. I don't know. I think the two things I was thinking were making sure that if we're going to have something like a birds of a feather that we have that we can start putting together like what is the any topics or whatever. I mean, normally what my experience with birds of feather is people can come up to like a whiteboard and just write in a few minutes or whatever. Short talks. But if we have material together that people say they want to talk and we can start putting it, then that'll, I think, get other people ready. So what do we want to do for anything like that? And then the other part is the working session. If we're going to have things that we actually want to try to actively work together on. If we're going to have something like a bird of a feather over there, then having one or a few, you know, two or three, I probably wouldn't choose too many, but things that we'd like to work on and maybe have that together. Like for instance, the best practices. I don't, I don't think we should say any best practice, every best practice. But if we say, here's a few that we're interested in. We can always adjust these things when we're there. But if we have some content ready, whether that's one of the ones that have already been put forward or something else, then if we have content that's, you know, 20% or 50% done, it's better than zero in my mind. If we want to work on the glossary terms, then picking, you know, a couple of terms that we are interested in and starting that so that there's actually some content. People are in my mind more likely to contribute if, if there's something there and it gives them an idea. So I would say organizing the working session and the birds of a feather would probably be it. Okay, I think that makes sense. I agree. If we've got a couple of open pool requests, or, or Google Docs or whatever, you know, however we want to structure the work, but that's been started because I agree, people will find it easier to get up to speed with ideas and so on. So when you mentioned the, you mentioned the glossary, and there's a couple of, couple of issues we've already been relating to that. I mean, we could, we could just create either Google Docs or a discussion item in GitHub that starts to collect the glossary items that we want to define. I know there's some discussions already to kind of collect or do in this issue. As far as today or just work before we get there as promotion and just a general preparation, we have the, for the gathering. So we have the form. I've, we have the, our planning doc ourselves, which is more for internal Google Doc. In fact, is this your screen, Tom? Yes. Okay. Can you bring up that document? It might be easier just to look at what we've done and what's left. Do you mean you could part of the Google Docs one? The Google Doc, the planning for the gathering. Yeah. Yeah. Probably should just name this planning and doc, but they, yeah, so there's all that section there. The rest was content to let us know what we're doing draft content, I guess. So we've, we have the form. We're planning to do that with some places. So if there's more places we'd like to share. What's not on here, but we should probably add. Lucina, I think you were, you've already started some stuff for Twitter and we're planning on continuing that. Marketing it. Yes, I can. Continue promoting the gathering when I promote. Yeah. All right. So then get up. We have a discussion form. Can you click on some of those and bring them up? Tom should be clickable even though it's direct. Oh, look at that.  Number one and number two. Potential areas for, you know, talking. If someone wanted, and I'm not saying anything here. Do you see any responses? So no responses. But, you know, we can have people do discussions here. If wanted, we have a. The issue for this. So there's an issue for the event. Has anyone added anything else on the issue? No. I mean, if you had some, some interest in doing something specific in the event, or if you think some colleagues might be, we could get them. Okay. Go ahead. Yeah, I was just confirming. Yeah. So, so on that point, and Thomas graph has already signed up by the form. But based on a disc, one of the isolated colleagues Joshua. Someone was named and introduced me to him and Liz Rice and suggested they come along if they can. Okay. So, I don't know where we all where we'd like to put everything I was trying to provide some different places. I don't know. Until we decided and not, you know, hold off until it's a week till. But whether. I think whether. Of course, the form helps us gather some of it in one place, but then publicizing. So. We can add stuff into this issue or put it in that discussion. As we're going forward. I think we could. We need somewhere that's like a, here's the public agenda document. So that can be. There's, there's many choices there. The other place where it's published is in GitHub under. There's a new events folder. Is that on there. Maybe that's not. That didn't get added to the Google Doc list. I guess it didn't. Put it in there. Okay. Okay. So this events folder is new. You know, right now. There's no, here's a CNCF. All telecom. Top level, I guess it. Well, it's just CNCF. There's not like a CNCF taco. And at one point we put some stuff under the telecom user group. And, and it kind of seems like the CNF working group is. That place. There's, there's nothing at a top level though. So, beyond that, so figured for now. Putting events that are related to. The working group and. Maybe the certification test suite. Even. Telco days mentioned here, but we could always put stuff here. But in any case, this is it for the community gathering. And we could use this as here is the. This actually is the document that we. Do PRs to to add the. Agenda. So of course, having the location designated somewhere. Or everywhere is going to be good. But as we put together stuff, we could publish it here. And then point people. Like, what is the easiest to market? So if Lucina is going to be saying, Hey, here, go here. Come to the event. The form right now is great. Come sign up if you want to go. But where do we tell people to go read for updates? We're not going to be updating the form over and over. So where do we tell them? So this can be a, if we want. For the actual event live when we're there. We can of course do work in individual. Places where we have stuff like the, the glossary. Right now it's just an issue, I think, but some of the best practices actually have Google docs. So we can just work on the drafts for those. But in addition, we have. You know, how do we do live notes or shared notes or whatever? We do have a draft. Ether pad. We haven't shared it yet because I think that those are just public and I'm kind of afraid that we may end up seeing like a bunch of spam in it. If we just post it a link to it. But this kind of. Gives an idea of what I was thinking and I don't know Tom and Nikolai and. Lucina, anybody, Akash, if y'all have some thoughts on this, then we can adjust, but this is kind of how I was seeing. The agenda and how we're going forward potentially. And. And. I, this is totally just more of a draft right now. If we have the birds of a feather topics and, and then working session, then. You know, we can add stuff in here, share this and then put more. But do y'all have some feedback or thoughts on, on what we could do. I think in terms of this, the agenda, I, I like the idea of having the. The kind of the quick lightning talks to start with, and then a working session. And, and as we said earlier, to bring some already started. And. Work for the working session. In terms of capturing what's happening on the day, I think he had as good as anything else to use. You know, it makes it easy to catch what's going on. And I agree. But having a single place that we can point people to, like to get her article. And. It's a, it's an easier way of, you know, making sure everyone's got the right information. Can you lock face. But it adds. Probably. I mean, I don't really care before, but. If we. Link this from other places, like the. Events get have. Document. So that people can see here's, here's all the content that we talked about. And the live. Or the notes. And all that. It'd be nice. Just. If it in. A read on. Awesome. Yeah, it looks like you can create a read only. Specific URLs read only. Rather than. The link for the document. Did it randomize it? Looks like it. We. It's the same result of each time. So it's probably some. Some hash, but. You'd have to really care about getting. Well, maybe we. We post the random one. The read only. We could put that right into the. Different places that we want to share. Yeah. What happened now. And then anyone that's saying. They're interested. We can give them access sooner. And then. Share it directly whenever we're there at the event. Yeah. I didn't, I didn't know where to put the. Cillium ABF for Delco workloads. So I just put it like a topic discussion at the top. But it could be a five minute thing. That's what we're talking about. I was leaving it. The idea of. An open longer discussion. So the fight, the birds of a feather. Hopefully we can. Just keep those short. And not let. You know, one of them turn into. 20 minutes or an hour. From five minutes on the, on the other hand, it would be okay. I think to have. Here's a larger, longer discussion. You know, it's kind of thinking. The multi network. Okay. Were you there? I don't remember. And ended up talking about the. Potential adding a new Kubernetes object that. Had the. Information about declaring. You know, multiple interfaces. Not as a, I think it would be like a super. I don't know. I don't know. I don't know. I don't know. I don't know what it said or a. Of what. Maltis. So compatible with Maltis and other things, but. Yeah. Generic. The whole multi network group. So they. Kind of. They had some specific agenda items that went to work through. And. Questions and separate for, but they also had kind of. Open discussions around. Use cases and other things that were important. I think. So they didn't have a birds feather, but they had kind of working working session time and. Open just topic discussion. So. Okay. I think leaving some time for that. So that if we want to dig into something or someone has a. A use case and. They want to talk about. A problem space and practices or whatever. But technology is coming forward and we want to explore how it. Fits. But what were you thinking or whoever put it forward for this. This flexibility of seeing that plugins. So that was the discussion I've been having with. With us. So obviously. Certainly we buy. Our communities platform from a vendor. And whilst. C&I plugins are using a standardized C&I. There is a, there is a series of kind of validation and certification steps. But we would want to go through. Before introducing a. C&I that isn't kind of bundled with the product. Into the stack. Because it's another. It's another thing. C&F and that has to. Check. Yeah. Their application works with. So it's more about. Just a. I don't think I've really got an opening statement. I. You know, maybe. Maybe I need to have a little chat with. The. I've been talking to and see who's going to come and. Kind of how they want to frame the discussion is. I'm more. Suggested it on their behalf. Rather than. I think in terms of the ordering, I wonder whether the shorter. Kind of lightning talks should go before. The longer discussion. Set items. Just so we don't. Kind of potentially run out of time for them to. Happen. All right, I agree. Can you just move that down. And maybe we rename it to call it. Open discussion ideas or some, some other name. Can you get that read only late. Link and then add it to the. To do list in our planning document. And then post it to different places wherever is appropriate. What else do we want to do? I probably think a much else. Am I. In terms of the logistics of location. Is that being dealt with or is that something to deal with still. Still needs to happen. Lucina has looked at some alternative options. Like co-working spaces. I don't know. I don't know. I don't know. I don't know. I don't know. A bowling. A bowling place. Other other ideas. So if, if it turned out that we don't want to be at the RAI. Nothing set yet. So. Okay. Do you. Or do you need. Help. Or. Only want to. Sort of assist with getting that sorted or. Go back. There's a section just for the logistics. Or is it a checkbook section? I think it was that. Yeah. The ideas for where to go. Lucina, do you have any feedback? I know that all of the co-located events. For Kubecon will be held. On Tuesday. The 18th and some of them are. We have a meeting room available. I know they are. Morning, half the afternoon for our full day. I think if we wanted to try to find a space that are. The conference. Center. We could do it. On the fly. Or. We could ask the events team if they have a meeting room available. I know they are. We have a meeting room available. So that. They may or may not be able to help us. Get a, an official room at RAI. RAI. In the past, there's been talk about. You could use the lunch room. Or informal meetings. And then of course there's the hallway. I've only been to that conference for one time. I can't recall the exact layout to say meet us in the. Corner. I think we're going to have a meeting room available. So. I'm going to go back to the last meeting spot. Yes, across the street is a co-working space slash. Coffee shop. Okay. Talkie. I haven't emailed them yet. To see what their meeting room. Opacities. And now we have. Well responses of folks who are interested in attending. So that group, the group of map size. Should be easy to accommodate for. If you want to have a room. That's a little bit longer. A walk away. And there's a hotel and now, and how. Hotel. There's no vacancy for rooms at this time as it was an official. You come. Then you block. But we may be able to use the conference room. If it's not already booked at that time. And then the bowling alley. The six minute walk. I know there is going to be a. The big about being fired bowling party hosted by our mo. At that. At that bowling alley later on in the week. So they may already have. Some more requests for, for meeting. So it's up to. Would they. Ask the same team. If they. Have time to help accommodate that. Which. If we have a small group under 25. Then that seems like a good option. We have a target of. Attendees we're trying to meet. Or would we be okay with a smaller group of. 15 to 20. I think it'd be nice to get more, but I still think it'd be worthwhile meeting. With. It's hard to know where the people are going to. You know, respond to the form. Later. If that's all. It's hard to know whether people are going to, you know, respond to the form later on, or not respond to the form and turn up anyway. Etc. I'm not really sure how history tells us. I expect that. There will be some number that show up without ever communicating. And. If it's more than the group that. Shows up to. These calls, then I think we should do it. If we have the opportunity to talk to anyone new, good. And if we. Make progress in the working session also good. So. Yep. As long as we have it. A space that's. Known and easy enough to get to them. We may have people that. For whatever reason, didn't know about it. That are at telco day and go, yeah, I want to go to that and show up. We may double whatever the number is. And. I'm would like to get. General. I don't know if this would be a good place for NSM. To come and. Talk. We had had some. Talking to Ed and stuff in the past. The thought of having. A working. A working session. I don't know if this would be a good place for NSM. To come and. Talk. We had some. Talking to Ed and stuff in the past. The thought of having. A working session. With like some best practices and some use cases that were interested in the past. But nothing has really happened for a while. So maybe they'd be good. And then if there's any other projects like, hey, we shouldn't. We've had a lot of work from litmus, but is there another CNC a project. For the five minutes birds of a feather. For a. Working session where we're writing about use cases and putting content in. I feel like there's. This should be a, here's a time where we're really trying to encourage and move forward on. Collaboration between different parties. Have you been working in the. What's the NSM folks? No, no, not recently. All right. I can reach out to. Some people. Any ideas for. Like. Here's a CNC of project that we should really have. We should really be talking to. Is that a fun talking using any CNC of projects or caring about any interested that we should try to get to come chat with us. The ones I'm aware of are. Silver. In terms of things we interact with directly. Obviously we've. Not directly. Silver and camera. Not quite sure. That would fit camera. Want to. Reach out to because that's telco API. So. In terms of. Yeah, no. I don't know. The only ones I'm aware of are. Silver. In terms of things we interact with directly. Obviously we've given that is and. But not. Not directly. Silver and camera. Not quite sure. to reach out to, because that's telco API stuff. So there was a GSMA announcement at Congress about some API initiative, which is being delivered by the camera project within CNCF. So that could be relevant. Thanks that that's been brought up on some prior calls as far as what are the different projects How is anyone working together? Do you know anyone working on that, Tom, that we could invite? So I know I've worked with Peter before and Nathan. I know there are some other I doubt any of them are going to Amsterdam. Right. Yeah, there's a bunch of people there, but I don't think any of them will be going. I can reach out to Peter and maybe we email the mailing list. I'll reach out to Peter and Nathan first. All right. They can share it within the community if they think it makes sense. Yeah. Okay. Sounds like there are some plans. Let's see how we get on for next week's meeting. Is there anything else you want us to talk about today? Are any of the best practices something that we want to try to publish before the event and any of them? Ventress. If you just look at the, probably have issues that we could work on before them. Um, well, so, so I think the glossary one is, is, and it's not a best practice, but that could be a good one. I had started. On one of them. Within Google docs. Which one it was. I think it might have been. Yeah, this one. Okay. So we could, I could, you know, flesh this out a little bit more and then, you know, have that as a starting point perhaps. And I think you had started one as well. I tried to add one for every issue. Select the readiness was the one that you put in there. Right below. And of course we have the related. So I have a doctor for each of us, they're related, but it was just to keep them separate. Yep. Go ahead and click on that. I don't know if that'd be there. So I, I think Victor had started it this way in a different document. So I've just been cloning him and starting, but it's just the. Mark down copied in and then fill in the sections.  Playing that when you copy it back, but. You're basically doing that. The sections. And if you scroll down so that. Any in black is kind of the ready. The red is here. This is just copied over. We need to change it. So these have no motivation. It looks like that the static. External. Resources that you had. Was pretty close. It seemed like it had a lot of the content.  The code in this document was italics was. Copied from somewhere else and. Okay, okay. Non italics was ready. All right. Well. I mean, so that part is not done, but I think the references and readiness. Unless it was a liveness. You scroll down. Okay, so there's a proposal kind of started the proposal. Yeah. That's minimal. Notes. Added some more notes. Yeah. That's it. What was that? I wonder why we put that someone must have. I thought that was related though. Yeah, it's not red. So. There was something. Said. About the. Development side. And. I think it might be in the liveness, but. Victor was talking about the different. Attributes that you can use for these checks like a liveness and readiness where. The. How often you check and other things. And. That's probably something that we need to ensure it's on both of them. Yeah. Increase CPU usage as a result of, yeah, this is, this is it. So that seems like it's related. Need to check which ones are actually the same in them. But we're going to have some related content there. I think that quote. From that cloud native documents, probably a good reference also. And just keeping. These are both of them. Please. Okay. So perhaps. So we've got a meeting next week. And then. There's a meeting. The week after. Just thinking about when we should make a decision about which. Because obviously these will get worked on over the next couple of weeks. We could then make a decision about which ones we take to the working session. Based on. Which has more to go. And that's just got me thinking that actually. April the 10th. I don't know what it's like in the US, but that's Eastern Monday. And that's a public holiday in the UK. So. I won't be around. I don't know. All right, April the 10th. I don't know if there's a public holiday elsewhere. But either way, that means that my, my last meeting that I'll be attending before. Is next week. So either next week or a week after, perhaps we make a decision about. Which of those Google docs we take for the working session. Based on how much work has been done in them. It's unsensible. Yeah, it looks like it's just a holiday. That's just a, I mean, I'm just looking at one of those calendar places. Easter Monday. Worldwide. So we could. Do we want to just say. Not will cancel the town. Because it's a, it's a public holiday in UK. Germany, Ireland, Italy, and Spain. I have that in my outlook already. So I suspect some of the European countries as well. Yeah. Let's just go ahead and put. Canceling. April 10th. Easter Monday or whatever. Thanks everyone. Thank you. Speak to you next week. Cheers. Cheers.


Hello and welcome to the session. In this session, we will discuss how a linear equation in one variable can have one solution, no solution or infinitely many solutions. Now, by solution, we mean that value of the variable from which the left hand side of the equation and the right hand side of the equation are equal. Now, linear equation in one variable x can be of the type Ax plus B is equal to D or Ax plus B is equal to Cx plus D. So, for solution we see those values of variable x for which left hand side is equal to right hand side of the equation. Now, let us see linear equation in one variable with only one solution or we can say linear equation in one variable with unique solution. Now, consider the equation 3 y plus 7 is equal to 16. Now, let us solve this equation. So, this implies 3 y is equal to 16 minus 7 and further this implies 3 y is equal to 16 minus 7 is 9 and this implies y is equal to 9 upon 3 which is equal to 3. Now, let this be equation number 1. Now, here the only value of y that makes the equation number 1 true is y is equal to 3. It means for y is equal to 3 left hand side will be equal to right hand side of this equation. Now, let us verify this for this. We will put y is equal to 3 in equation 1 and here we will get 3 into 3 plus 7 is equal to 16 which implies 9 plus 7 is equal to 16 and further this implies 16 is equal to so left hand side is equal to right hand side it means y is equal to 3 satisfies equation 1. Now, if we put any other value of variable y then left hand side will not be equal to right hand side of this equation. Now, let us put y is equal to 1 in equation 1. Now, here we have 3 into 1 plus 7 is equal to 16 which implies 3 plus 7 is equal to 16 and this means 10 is equal to 16 which is not true because 10 is not equal to 16. So, putting y is equal to 1 in equation 1 left hand side is not equal to right hand side. Similarly, if we put any other value of variable y except 3 then it will not satisfy equation 1. So, the given equation has only one solution that is y is equal to 3. So, this is the linear equation in one variable with only one solution. Now, let us discuss linear equation in one variable with infinitely many solutions. Now, here consider the equation 4 x plus 20 is equal to 4 into x plus 5 the whole. Now, here left hand side is equal to 4 x plus 20 and right hand side is equal to 4 into x plus 5 the whole which is equal to 4 into x plus 4 into 5 which is 20. So, right hand side is also equal to 4 x plus 20. So, these two expressions are equivalent. Now, simplifying the given equation we get 4 x plus 20 is equal to, now here using the distributive property this will be 4 into x that is 4 x plus 4 into 5 that is 20. Now, subtracting 4 x from both sides we get 20 is equal to 20 which is true. So, 4 x plus 20 is equal to 4 into x plus 5 the whole is true for all real values whatever may be the value of x the two expressions remain equivalent. The given equation many solutions. Hence, if we put any value of x then will be equal to right hand side of this equation. Now, let us verify this for this let us put x is equal to 3 and 5 in this equation. Now, for x is equal to 3 left hand side will be equal to 4 x plus 20 which is equal to into 3 plus 20 which is equal to 12 plus 20 and this is equal to 30 and right hand side which is equal to 4 into x plus 5 the whole will be equal to 4 into 3 plus 5 the whole and this is equal to 4 into 3 plus 5 is 8 and 4 into 8 is 32. So, 32 is equal to 32 which means left hand side is equal to right hand side. So, x is equal to 3 as the solution of the given equation. Now, for x is equal to 5 left hand side which is equal to 4 x plus 20 will be equal to 4 into 5 plus 20 and this is equal to 20 plus 20 which is equal to 40 right hand side which is equal to 4 into x plus 5 the whole will be equal to 4 into 5 plus 5 the whole and this is equal to 4 into 5 plus 5 which is 10 and 4 into 10 is 40. T is equal to which means left hand side is equal to right hand side. So, x is equal to 5 is the solution of the given equation. We can put any real value of x in this equation and that will be the solution of this equation. This is a linear equation in one variable with infinite many solutions and now let us discuss linear equation in one variable with no solution. Now, where an equation has no solution equation. Now, when every value of x left hand side is not equal to right hand side then the equation is inconsistent that is it has no solution. Now, this condition ends when two expressions are not equivalent. Now, let us consider an equation that is 5x minus 2 is equal to 5 into x plus 1 the whole here. First of all, let us simplify this equation. Now, this implies 5x minus 2 is equal to now using the distributed property this is equal to 5x plus 5 into 1 which is 5 now subtracting 5x from both sides we get minus 2 is equal to 5 which is not minus 2 is not equal to 5. So, here left hand side is not equal to right hand side it means these two expressions are not equivalent. Therefore, the given equation is not true any real value. So, the given equation has no solution. This is the linear equation in one variable with no solution. So, in this session we have learnt about linear equation in one variable with one solution no solution or if I write you many solutions and this completes our session hope you all have enjoyed this session.


Stevenson falls on Messiah tonight, 3-0 Glenn Clark with head coach Tati Korba. Coach, obviously you were up against a really tough competition tonight, one of the best teams in the country. Knowing that, and knowing you still clearly wanted to get a result anyway, what did you make of your team's effort tonight? A great effort. We had a pretty specific game plan that we had to put in place, not much time between games. So not a ton of time to work on it, two days really. And I think our biggest concern was them kind of staying committed to that plan, staying disciplined, more mentally kind of checked in and disciplined than anything. And I thought they did a great job kind of sticking to the game plan and following through on the things that we asked them to do. You had some chances to equalize there in the second half, and who knows what happens from there. But is that sort of what you're reflecting on, that you look back on that and say, you say you're going to have that chance in the second half to equalize against Masiah, you've got to be pretty happy about that. Yeah, I mean, I think for sure it could have been 1-1. And I think that it was a great game I think for our very young squad to see that while Masiah is the defending national champions, one of the best in the country, it's a team that when we play them the right way, and maybe low-press and then look to break out, it's something that we can bottom line as we want to play them again. So that's kind of the goal. You've got to work to that opportunity the next couple of weeks. At the end of the match, a fifth save for Keegan, so she finishes with five, and she's now tied with Tiffany all time for the most saves in Stephenson history. Correct me if I'm wrong. You had one year with Tiffany, correct, at the end of her career? Yeah. Since they're standing together at the moment, in what ways are the two similar, obviously, the two greatest goalies in Stephenson history? Yeah, I think just that competitive mindset, I think first and foremost, and I know Tiff had a great career, and I know that she worked hard to improve every single year and really didn't rest, and Keegan has absolutely done the same thing and continues to find the things that she needs to improve and work to make them better. And she's just been kind of the anchor for us for so long and has been five years, I've been here five years with Keegan, so I have to get her on staff maybe, find a way to keep her around. But yeah, we're looking forward to her breaking that record. I think it's very well deserved. We'll have to tune in for that on Saturday, obviously, but then what do you need to do? Obviously, as you point out, wanting to get another shot at them, you've got to keep getting points. You need three points to make sure you put yourself in that position. What's going to have to happen on Saturday against Alvernay to bounce back and get three? Yeah, you know, our next three games, we feel like they're all must-win games. And, you know, I think we need to feel like our backs are up against the wall, and if we want to stay in control of things, you know, and not be dependent on other results, then we need to come away with, you know, three wins over the next three games. We'll see you on Saturday. Coach, I appreciate you taking the time. Thank you. She's Tati Korba. Go Mustangsports.com.


It's of course talking about your mama begin. I'm a brick. We got a this is called Roger Sir Recording what read this? this Jivane mega recording this is the video of Roger Sir recording in Hungary for the song from the movie mega This song is a special composition for Roger Sir as it is a dedication to his wife Jiva who had Passed away a few years before the song released. It's still widely believed He never recovered completely from his wife's passing as she was his pillar of strength.  There's no recovery. We do not recover from the other one dying No, it's like it's like even if you're coming from a loss of a child It's not even if you get remarried. No, don't recover from losing the love of your life It's like he recovered from the loss of his limb. Well, yeah, he's surviving life that way, but the limb didn't come back Yeah, yeah, I know that but yeah, so a lot of it since we like to see him do it live In a live session in his process Recording a song awesome. So that's cool. Um, maybe he can become our toast There's Sweden, is that what they said Holland Holland, okay. What is the temple temple? Like somebody many many times. Yeah, especially Whether it was recording or just choral instruction with a choir We're rehearsing for a musical but would you we're working with the music director? No serious, but music He wants it darker Hey, what's going on in there? What's a push? Why are you not getting it That's so much you need no, no, no, it's came in the take you just play Yeah, I can seriously can sit and watch in a studio like that for hours on end Yeah, it's so interesting because obviously Anytime you have a gene they have it in there and everything that's already it's already done Up here and then they get frustrated when you can't yes They can they can't articulate to you exactly. They're just like, okay No, that's not right. Okay. Yeah, that's why I really Some of the best engineers are really really patient people because the The one creating it and who's doing the arranging and the composing They want something and sometimes you you miss that and I've I've found that arrangers are I mean Engineers and producers tend to be some of the most patient people like think about when we did our stuff with Steven bowler he folk he functioned as our engineer and they are And there'd be times where you want to nail it and you're not getting it like oh, I'm so sorry And he's just no we're good. However many takes we have to go. We'll go. We're typically pretty Pretty flexible too, and they also have to be able to set aside Their particular thing because you know, they're hearing things as well But if you're not giving roger sir what he wants you got to find what he wants Yeah, not what you want. It's like the director of a film. Exactly the director of this music Yeah, he is the boss This is his vision. Yep. He ends. So you have to No, same thing same thing singing because he may have changed things since they were given their vocal So they've had they may have had a reversal that morning before he walked in and they just saw the piece They may have not they may have just looked at it and started singing And since he wrote it, he may have had some changes He wanted like making sure that you can't really notate in the music for vocals How dark you want the sound to be so you have to tell them what you want with the oh sound You don't want it to be a big ah you want it to be an oh sound And he may have changed like the breathing pattern He told them I don't want you to breathe for the entire four bars And musically it may have said breathe after each bar And so you just make the adjustment and fill it that in the music to breathe Yeah, it'll it'll give you breathing notation for for a singing part It'll tell you if you should when you should break and how many breath How many beats you should rest before you come back in again It'll also not always but it'll give you dynamics as far as if you should increase being loud If you should hit it louder, if you should be soft when you come back on it That's typically all in a notation. Yeah. Yeah, it's always fun to watch them work I enjoy that.  So let us know if there's more of this other artists like our Dost, hey of Ramon as well That you know, that's always gonna happen. All right. Yeah, you know anybody we interview they become our Dost Just automatically because of you can thank podcast for that. He's the one who Let us know down below


Yeah, it's all squared up in it Yeah Now all the padstones are in Yeah There's no rush for that Once the joists are on we can do all the beamfilling. They can put them in and then when We run that side in the back that side and then we run the front in last and then we'll put the wrinkles on when we're doing some Right soldier bricks, let's get this set up full-foot level tea clamps Fantastic things. These are too tight and pull the brick work over That's when you set this thing Second one, it's gonna have to be dead tight That's just to guide the bottom of your soldiers Line for the top So we've got Corn box over there, and then our fixed brick. It's our line set up Got We vent there, so put one in here And got one there, so put one against there Got one there, so put one in there So I've got eight soldiers one in there one one two three four One two three four. I think it's eight Yeah, eight have big joints, so one there One in the middle One there With our little red ones Facing, one thing we have to do is We've got to take a bit off the back there Just so it's fit, just so we don't trap in the Tea clamp in this side Six twenty five So the soldiers are six ten Actually six thirty there So we've got a We've got a Gain twenty mil Big old, big old joints on this Not giving, not giving Starting it On camera We're getting the first friggin Vent Keep checking Still got twenty mil to make up There you go again Yeah I'm talking to the camera Say hi, I'm trying to film with this chest mount Can't straight up, you're building it and Making sure you get evenly Your angles right Half a turn, well a quarter of a turn Really magic then, tea clamps BT tea clamps Just cut off Cut through the bottom, there's Just drinks, cut off the excess Which is actually a bit wet at the moment It's in the shallow is it There you go, sit from up here but When it's when the house is finished And you're looking from below You'll always see that It's cacody done, tidied up properly Done a few of them as old backs then Soldiers done Features in BT clamp and fixed brick Right, let's go and get the front finished


Hi everybody, welcome to our channel. I want to make a quick video today on TRP's Temporary Resident Permit. I don't think I've done a video on this or maybe I've mentioned it in passing in other videos. Temporary Resident Permit is an application for foreign nationals who are inadmissible or who may be inadmissible to Canada or that are in Canada without any status. There's different ways to apply for a TRP. You can apply for a TRP if you're in Canada. You can apply if you're outside of Canada. You can apply for a standalone TRP or you can apply for a TRP within an application. For example, with the Humanitarian Compassionate Application, with the Spousal Sponsorship, with a Criminal Rehabilitation Application, with a Temporary Resident Visitor Visa. Online on the IRCC website there are some information about TRP's and there are information in manuals and guidelines and regulations. However, I would say that TRP's an application that an experienced lawyer will know exactly when to apply and why. You could apply on your own and there are clients who do, but what I'm trying to say is that there's a lot of scenarios where one would not know that you can apply for a TRP. For example, if you have somebody who has received a bar, a misrepresentation bar from IRCC and they're barred from entering Canada for five years or for applying. Now, there is a possibility, you can always apply a TRP, it doesn't mean it's going to be approved. The TRP is based on the discretion of the officers, the officer who's going to decide whether it will be issued or not. But there is a possibility of applying for one if there's really strong, compelling circumstances, for example, minor children involved, the person has to stay in Canada or has to come to Canada. There are some chances that it could be issued. Now, when it comes to misrepresentation, it's very, very, very difficult to get a TRP issued, but it's not impossible. Same thing for, well, same thing for, for example, criminality. If somebody has a DUI, for example, from Sweden and they want to come and visit Canada, but they are not yet eligible for rehabilitation, it's going to take, for example, two more years, but they want to come and visit or there's a wedding they want to come to. Now, somebody from Sweden doesn't need a visitor to come to Canada, they can just get on the plane, they can get on the plane, they need to apply just for an ETA, which is automatic. But given the criminality and given that the person is inadmissible, then that person needs to apply for a TRP because if the officer at the border asks questions, and even with the ETA there, I believe there is a question about criminality, you could be questioned at the border upon entry to Canada, you could be the night entry, you could get an exclusion order, you could be sent back, so creates a lot of problems. But if you want to enter correctly, properly, their legal route, then you have to and can apply for a temporary resident visa at the Embassy responsible for your country of citizenship. So it's a form, it's photos, there's a $200 fee, you have to include documentation about your circumstances. So if it's about misrepresentation, what happened, why, why do you think you deserve to come to Canada at TRP? If it's criminality, all of the documentation with respect to the criminality, why do you want to come to Canada, who do you want to visit, why is this a compelling situation? Processing time with respect to TRPs, that's a little bit tough because it's not really online, there's no posted times, it really depends on the country, the situation, the story, but it could take a very long time. It could easily take six months, it could take 12 months, it can even take longer. It's kind of like a mysterious application that is sent into kind of like a black hole and then nobody really knows what happens until something happens and we have to follow up and there's ways to get information. So this is what I meant earlier by saying that it's kind of an application that an experienced lawyer would be able to propose. It's not always the right thing to do, it really depends and at the end of the day it's an exceptional category for exceptional circumstances. So if you are in this type of situation and you think that you may not be able to come to Canada and maybe a TRP would work, you've done your research but you're not sure, we recommend to consult with an immigration lawyer to see if a temporary resident permit is suitable for you or perhaps you're filing an application and you're inadmissible and you're going to request an exception, you're going to request the officer's discretion but sometimes adding a request for a TRP in your letter, adding the $200 fee, the TRP form, specifically indicating that you're making that request can make a difference and can make the officer not refuse your application or refuse your underlying application but issue to you that special permit, the temporary resident permit. If you have any questions about this, you can contact our office. Thank you.


A definition of the amateur. The amateur is young and dumb. He's innocent, he's good-hearted, he's well-intentioned. The amateur is brave, he's inventive and resourceful, he's willing to take a chance. Like Luke Skywalker, the amateur harbors noble aspirations, he has dreams, he seeks liberation and enlightenment, and he's willing, he hopes, to pay the price. The amateur is not evil or crazy, he's not deluded, he's not demented. The amateur is trying to learn. The amateur is you and me. What exactly is an amateur? How does an amateur view himself and the world? What qualities characterize the amateur? Fear is the primary color of the amateur's interior world. Fear of failure, fear of success, fear of looking foolish, fear of underachieving and fear of overachieving, fear of poverty, fear of loneliness, fear of death. But mostly, what we all fear as amateurs is being excluded from the tribe, i.e. the gang, the posse, mother and father, family, nation, race, religion.  The amateur is terrified that if the tribe should discover who he really is, he will be kicked out into the cold to die. The professional, by the way, is just as terrified as the amateur. In fact, the professional may be more terrified because she is more acutely conscious of herself and of her interior universe. The difference lies in the way the professional acts in the face of fear. The amateur identifies with his own ego. He believes he is himself. That's why he's terrified. The amateur is a narcissist. He views the world hierarchically. He continuously rates himself in relation to others, becoming self-inflated if his fortunes rise and desperately anxious if his star should fall. The amateur sees himself as the hero not only of his own movie but of the movies of others. He insists in his own mind, if nowhere else, that others share this view. The amateur competes with others and believes that he cannot rise unless a competitor falls. If he had the power, the amateur would eat the world, even knowing that to do so would mean his own extinction. Though the amateur's identity is seated in his own ego, that ego is so weak that it cannot define itself based on its own self-evaluation. The amateur allows his worth and identity to be defined by others. The amateur craves third-party validation. The amateur is tyrannized by his imagined conception of what is expected of him.  Paradoxically, the amateur's self-inflation prevents him from acting. He takes himself and the consequences of his actions so seriously that he paralyzes himself. The amateur fears above all else becoming and being seen and judged as himself. Becoming himself means being different from others and thus possibly violating the expectations of the tribe without whose acceptance and approval he believes he cannot survive. By these means, the amateur remains inauthentic. He remains someone other than who he really is. The amateur has a long list of fears. Near the top are two—solitude and silence. The amateur fears solitude and silence because she needs to avoid at all costs the voice inside her head that would point her toward her calling and her destiny. So she seeks distraction. The amateur prizes shallowness and shuns depth. The culture of Twitter and Facebook is paradise for the amateur. There was a popular bumper sticker a few years ago—too much ain't enough.  The amateur, the addict, and the obsessive all want what they want now. The corollary is that when they get it, it doesn't work.  Because the amateur is so powerfully identified with herself, she finds it extremely difficult to view the world through the eyes of others. The amateur is often unkind or insensitive to others, but she saves her most exquisite cruelty for herself. The amateur's fear eclipses her compassion for others and for herself. In his heart, the amateur knows he's hiding. He knows he was meant for better things. He knows he has turned away from his higher nature. If the amateur had empathy for himself, he could look in the mirror and not hate what he sees. Achieving this compassion is the first powerful step toward moving from being an amateur to being a pro. The amateur believes that, before she can act, she must receive permission from some omnipotent other, a lover or spouse, a parent, a boss, a figure of authority. The amateur sits on a stool, like Lana Turner at Schwab's, waiting to be discovered. The amateur and the addict focus exclusively on the product and the payoff. Their concern is what's in it for them and how soon and how cheaply they can get it. Consumer culture is designed to exploit the amateur. If you don't believe me, watch 10 minutes of TV or scroll through any magazine or online shopping site. My beef with American culture is that almost every aspect, including the deliberations of the legislature and the judiciary, has been debased to pander to the culture of amateurism. The promise that our products and politicians proffer is the promise one might make to an infant or an addict. I will get you what you want and it will cost you nothing. Because the amateur owns nothing of spirit in the present, she either looks forward to a hopeful future or backward to an idyllic past. But the past evoked by the amateur's make-believe. It never existed. It's a highlight reel that she edited together from events that almost took place or should have occurred. In a way, the amateur's reimagined past is worse when it's true, because then it's really gone. The payoff of living in the past or the future is you never have to do your work in the present. Two Hollywood producers were talking. I've got good news, said one, and I've got bad news. Give me the good news. Remember that mansion we were trying to rent for the big party scene, but we couldn't get because it cost $50,000 for the night? Well, I just talked to the guy and he'll give it to us for $10,000. What's the bad news? He wants $100 up front. The sure sign of an amateur is that he has a million plans and they all start tomorrow. Have you ever followed a guru or a mentor? I have. I've given my power away to lovers and spouses. I've sat by the phone. I've waited for permission. I've turned in work and awaited trembling the judgment of others. I've given away my power subtly with a glance that was perceptible to no one, and I've given away overtly and shamelessly for all the world to see. Exile, failure, and banishment can be good things sometimes because they force us to act from our own center and not from someone else's. I applaud your story of how you hit bottom because at the bottom there's no one there but yourself. The force that can save the amateur is awareness, particularly self-awareness. But the amateur understands, however dimly, that if she truly achieved this knowledge, she would be compelled to act upon it. To act upon this self-awareness would mean defining herself, i.e. differentiating herself from the tribe, and thus making herself vulnerable to rejection, expulsion, and all the other fears that self-definition elicits. Fear of self-definition is what keeps an amateur an amateur and what keeps an addict an addict. The amateur dreads becoming who she really is because she fears that this new person will be judged by others as different. The tribe will declare us weird or queer or crazy. The tribe will reject us.  There is no tribe.  Each individual is so caught up in his own bullshit that he doesn't have two seconds to worry about yours or mine or to reject or diminish us because of it.  There is no tribe and there never was. Our lives are entirely up to us.


Everybody, my name is Rick Harding, also known as Hopalong Harding, as you may note, as I wheelie around the conference room here. I can stand as my doctor's gonna yell at me till I get my ACL fixed, cause I shredded it. Showing my bike, my son had a wheelie.  All right, so, you have an API now what? It's time to work on some clients. I apologize, now I'm gonna ask you to do a bunch of work, but I'm gonna justify it. I promise, it'll totally be worth it. So why should you listen to me at all? I spent a bunch of years, five or six or so, working on an open source, delicious clone web app thing, and got me into Python, and built a community, and wrote APIs on clients and phone apps, and did Google Summer of Code, which was excellent. If you ever get a chance to participate, go do that. I've also worked at Canonical, the people folks behind me, a bunch of stuff on their Juju product for the last few years, but I'm coming up on six years there this November, so I've been around a few blocks, I've done a few things. I'm a father to this awesome little guy who I was trying to show how to do a wheelie, and I should never try to teach him to do anything ever again. On this bike, I like to mountain bike, I like to camp and RV and everything, and I like to do photography and travel, and so that's me. Great, no, who wants to go next? No, sorry, that'll take a little bit. So why an API? Why do we do APIs to begin with, right? And I always, for me, I've kind of over time transitioned into kind of a very product manager-y view of things. I care a lot about community adoption. I mean, why do we write code? We want people to use it, right? We want to do useful stuff, and especially open source code, we just want, we love when that someone comes along and goes, your tool solved my problem, you're amazing, and then we go, yeah. And then we go tell our significant other. They said I'm amazing, and then she said, yeah, wash the dishes, you know. So, but the thing about APIs is they're there to do things like provide robots to go and do things while you're sleeping. They're there to provide features of things, you know, you don't have a button on your website for it yet, but the API lets people go and get their work done. APIs, I love APIs, I could talk about how to do them and what they should do and how they should look and feel, and APIs are just an amazing thing.  You go from being a tool with an API to an actual platform, people are building their own products on and there's something really special about that. So I love APIs, so that's great. So what do I mean by client? So APIs are great. How many folks here have written an API, provide a service that has an API on it? All right, how many of you all have written tools to use an API by someone else? Okay, now how many of you actually make raw calls to the API or how many, so raw calls, no library? You didn't pip install Bodo, you didn't go download the Stripe API client or whatever, you just make raw, exactly, right? The numbers there were about, I don't know, five or six to one, right? And the point about clients is a client is basically a library written in a specific language provided to users of that language to embed in their own tools. So example would be, I'm gonna talk a lot about Bodo. Bodo is a Python library that AWS funds a developer to work on so that if you do any work in your code against AWS, you have this lovely Python package library that handles all the fugly XML that I don't ever, ever wanna see. Cause it's written very Java-ish with very complicated, like to do the raw queries to AWS, I want to just quit and go become another job that I will probably install. Anyway, so I'll let it go. So it's un-good. So I work on this project, Juju. We learned some of the lessons I'm gonna go through here. Very, very hard. So we have Juju's a tool for doing operations at scale and cloud and bare metal and such and a very, you know, modeling your operations really well. And then it's got an API. We stand up a server and it's got an API. It's a web socket driven API. You issue commands across the web socket and it's very nice cause it's real time. You've got an open connection and all that. But because of that, it's not a simple just post this to this URL and you get back some, you know, JSON response. So, you know, we have this API and that's great. But you know what we found? Most people actually did it first. They grabbed our CLI and they write shell scripts around it. So one thing you may not realize is you've got an API, that's great. But people actually start out on the smallest, simplest thing they can do, which oftentimes is just a shell script that for loops through and does stuff. So I want you to think about not just, well, I have this API served by a server, but look at this as in any way a user can leverage your product or tool. They're all APIs of a sort, right? And so in our case, our CLI is, you know, we spend a lot of work from juju1 to juju2 to revamp the CLI and make it much more usable to care about it as an entry point. But it's interesting because we wanted people to go, hey, you can script this against the API and they would go, yeah, well, how do I do that with the CLI? And we're like, oh, well, no, you don't do that. That's not made for that. So it's very important to have the API because they were falling back to the easiest thing they could do. So in juju, you deploy software, okay? jujuDeploy is a command and it's one of my favorite ones because the CLI actually has a baked in go, juju is written in go, the backend services and the front end CLI client. So it has a baked in go client library for the API. And when you do jujuDeploy my SQL, the client actually does a look up to an API that says, okay, tell me, what is my SQL? The user's asking for this. And it's kind of like DNS. It resolves my SQL to an actual charm store, like identifier URL path in the API, sends that back to the client. The user never sees it because it's big and ugly and we don't want them to have to type it. It then sends it to the server and the server goes, okay, I know exactly I have a URI for this thing and I can now go and it runs an API call to add the charm into the database. Then it runs another API command to deploy a unit on this cloud that you specified. So jujuDeploy kicks off dozens of things that happen from fetching resources to bringing up cloud instances to configuring things and triggering scripts and hooks and all that. But the user just goes, I tried to deploy and it didn't do what I wanted to do or whatever. And you're like, well, okay, that's complicated story. So this is one of the things I really want to emphasize. Oftentimes when people first think of clients for the API, they print out all the API commands and they start to write a client that has a function for every one of them. And that is not a good user experience. I would like to encourage everyone to never ever do that. That's evil.  Like don't make your API a map of database calls to your database, because that's not helpful at all, right? Put some thought into what your product's actually offering and how it works. So oftentimes people go, hey, I've got an API. Great, the community will come forth and they will write clients and all their languages and they will provide for us and we will be awesome and amazing and be everywhere. So we did that in Juju. We're like, the community will go forth and the community did a great job except that they did many clients. And so we ended up with this kind of chart. Which client do you use when? Well, are you on Python two or Python three? Are you using Twisted? We have a library from a community person that did that but it doesn't work on Juju two, you know? Or it doesn't work on Juju one or Juju two. And so because we didn't own the client experience we left it to the community. We then had people come up to our mailing list and our IRC channels going, hey, I'm trying to script this with Juju to which we replied, so tell me a little bit about your environment. What are you trying to do? We can recommend like, I feel like a personal shopper.  Are you going to a fancy dress or is this a casual thing? You know, like which one's right for you? And so this really led to some issues and really what it needed to be is we needed to take more ownership of that. The other side of this is we've had this API but people haven't gone in and adopted it and really used it for things we wanted them to do. We often tell a really good story of how you can use Juju and our tooling and our charms for a really thorough CI CD experience where you can match the application code to the operation code and test it together. And if you have new application code you can do testing and it's all scriptable through the API but it was a lot of work and we really didn't find people were doing it. They would do things the old fashioned way, manually testing and all that and we were frustrated. We've provided you the tools to do this. Why don't you do it? And what we weren't hearing but we should have heard was because it's still hard. So I compare it to packaging. Long ago in my open source days I worked with, there was a developer that wrote a tool for a bunch who called Nome Do. It was like a quick silver launcher thingy for Nome. And I loved it. I've been looking for it coming from a Mac to Linux. I used it up but you had to build it yourself. And as part of my, I want to learn how to do packaging so I packaged it into a PPA and suddenly we had rather than like five of us hacking on this project and working on it, literal tenfold increase of users like week after week after week. And this is like one of my first insights that the ease of getting something to your users is you can't overestimate it. The adoption will come up so much more if you provide a client that works smoothly with your current version in a way that does good things your users will come. So this all comes down to really owning your product. I always love how Git is this tool but GitHub's kind of become the product in a sense. As you know that there are pull requests is this term that everyone uses now use pull request everywhere for everything. It wasn't actually even anything really in Git there was no such thing as a pull request until they added this Git request pull command which came out in 2014 which if you know Git goes back further than that and it's not even pull request, right? But we all talk about pull request because the definition of what is the vocabulary there has been defined by like GitHub. In Juju 2 we spent a lot of time going through and we wrote down and all of our on our product you create a vocabulary. What does it mean to speak the language of cloud computing or container computing or in data science or whatnot. There's a vocabulary you have to learn to participate in that community.  You know you've got is it four wheel drive or not? Is it rear does it you know does that locking rear diff or front diff and all these vocabulary things you have to learn to participate in automobiles or whatnot. So we broke down what are all the verbs and nouns that are used in using Juju and that appear to the user that they need to understand how do we limit them and focus them and as we build out our product, our API, our clients we make sure we're very consistent that the language is the same. The API call is not get charm and then the you know the client says deploy app right because those two things would be different. You know we don't want to have that difference between your product. So thus was born an official Juju client. We sat down and wrote and we have it it's in PyPI now you can go get it. This is official it's you know version two one of the things that was really important to us was this is for Python community so it needs to use the Python standard best practices. We have data to use async IO. You know we don't use twisted and stuff in it and I go back to the Bodo was a really interesting example because this guy in the community cared a lot and wrote this client and AWS came along and realized clients are important to the people that use our product. When someone uses a client they're not actually they don't care what the API looks like. They never see it right. All they care about is the client experience and that's whether or not the user thinks your product successful or not is gonna be based on the client they use. Is it easy to use this in my code or is it hard? And that client maybe you know covering over five different API calls that had to be made in complicated ways in the background but they won't care if they don't have to deal with it and see it because they did a good client. So I really love how AWS they actually hired up the folks doing the best clients in a lot of the languages and put them on a tools team because AWS cared about providing a consistent up to date experience in those clients to their users. So when you do these clients you have to take in and kind of pull in the values of those languages. If you're doing something in Go it needs to be very lightweight. It needs to be easy to incorporate from their methods pulling straight from GitHub with a packaging tool that they use and care about if you're doing something in Ruby or JavaScript it needs to be very modern JavaScript ECMA 6 compatible using promises or all the latest things that that community expects. And by owning the client you get to enforce best practices. You get a good benefit. You get to make sure that when they use the client logging is set up properly that resources get cleaned up on failure conditions that it's doing things like reusing connections and not abusing your API by spawning thousands of connections because they did something silly. And you get to send useful product data. You know what version is the client making the API request? We often go through and look at how well people are keeping up to date with the latest clients. How many people are using old stuff? So the client automatically sticks extra metadata in the API calls that then we can use to collect useful information about how are they using it? Are they using it from one set of computers or on this cloud and not that cloud and all that kind of stuff. It's a great opportunity to really again not just own the product experience but then benefit from that use. Some more examples. You're not limited to mapping exactly the API to the end user and the client. You can completely mask over warts. You know man, if we change that in the API we have to version it and release a new version then get everyone to adopt it or we can update the client and have it do a little magic foo and kind of smooth over that little wart in our API and the users actually get the better experience. And especially encourage folks in the world of microservices and all that is to have a single client. Notice that there's one BOTO API client for AWS. There's not one for S3, one for EC2, one for whatever. You can develop things in a very microservice easy to update and manage and scale world but still provide the end user. We are a single company with a single product with a single way to interact and use us and users will enjoy it. So it sounds like a lot of work and it is. I promised you I was gonna convince you that it's good though. But there are things that you can do. Use your own client but don't do it like we did. Our command line has an embedded go client. How many people can go and use that embedded go client? No one because our CLI is embedded into it. You have to get the CLI and we would cheat. The CLI had then, it had access to internal code because it imports a bunch of stuff. It wasn't a separate product. So use your own client but make sure it is distinct. Treat it like an external dependency in all your use. So you do a CLI, use your client. You build a web UI. We have a juju GUI that uses a JavaScript. We didn't do this well or we kept a separate JavaScript client and treat it as an external dependency. And then use it for your own internal scripting.  Script using your own client. And you'll find that you could actually get a lot of client use, written testing, adoption and ease a lot of your burdens internally without feeling like you're paying someone to go write these clients independently as their own kind of products. You kind of get the little two for one snack there a little bit. But you have to go through a little bit of self control to do this. So with that, I'd like to just kind of show that it's not just me, I'm not crazy. AmongoDB, you can see they've got the list of clients for different languages. This is from Sentry, which is a tool they want you to send your logging and stuff information to. They provide clients in a bunch of different ways. There's Stripe has clients they provide in Ruby and JavaScript and such, as well as AWS with their clients themselves. So I really encourage you to kind of own your product, focus the community. They don't spend time writing the clients or if they do write a client for a language you can't focus on, you can at least direct them and guide them based on the clients you've already provided. We've established best practices, how things should work. The community has to do less work of reinventing their own wheel. So you can really focus on them. And then where you go from here, just go out, provide the best product you can to your users, think about things and go through the little bit of extra work to keep these clients external to your own tools. And I think you'll find that you're off in a much better place to get adoption, drive usage and get really good feedback on your APIs. So I just wanna say thank you. I particularly wanna call out thank you, Pi Ohio for 10 years of awesome stuff. I've been coming here since the very first one Catherine did at the library. I've spoken at a bunch of them now. And I just love, I've met a bunch of people that this was their first one or their second one and stuff. So I think I just wanna call it. They're doing some awesome stuff here. So support Pi Ohio. Any questions or anything? I'm the guy trying not to run over your foot in the wheelchair as I try to stay off my knee and prepare for future wheelies. But otherwise, thank you very much. I do have a few minutes. Any questions, I guess? I wanna make sure I don't run out of time. Question in the back. So that's an interesting one. So, oh sorry, yeah. So do I distinguish between a client and an SDK? And yeah, so I mentally this and I should look at a formal definition somewhere. When I think of SDKs, I think of like baked in editing tools that tend to come down. Like you think of like the Android SDK or whatnot. You get a suite of stuff to stick with. Whereas a client is merely a library. So I think that's where I would limit it. If it's just a library I can import into my code and whatever I wanna do, that's just a client library, right? It goes off and does some work for me and whatnot. But an SDK feels like it needs to be a bit more than that. It needs to have more tooling for bootstrapping, shell projects that are started off or things like that. I would consider those more SDKs to do more than just provide an interface to an API. So, again, because we're doing, okay, what is my opinion on versioning the client versus the library? And this can be contentious, people believe different things. My firm belief is we're all following semantic versioning, right? So if I have one dot and two dot, right, and I write something in two dot, it should pretty much work in two dot, even two dot, two dot three. There may be new features available, but I should be able to use a two dot one library against two dot three on the old stuff and it should just work, right? Otherwise, I broke compatibility, major compatibility, and I should go to three. So my thing is that as long as the client library and the API version match in the major version, I don't care about the rest of it, right? The rest of it's all for change logs, figure it out, bug reports, targeting milestones or whatever. But you do have to, if you break something, just be honest and rev that version. I will say one of the biggest things I can ever say is if you do anything, if you do any API stuff, start with version right off the bat, no matter what, and try to do everything in your power to make it so that you can rev the version, because I have seen so much technical debt accrued based on going, well, if we did the right thing, we'd have to rev the version, which would have all this fallout, therefore, we're not gonna do that. Instead, we're gonna do something really hacky that no one wants to do, that we're gonna have to maintain for a decade. That stuff makes me cringe. So I even encourage, when you first start doing APIs, intentionally find ways to rev the API early and often so that you've established a practice. How do we do it? How do we announce it? How do we provide a client that talks across these versions? You want your client to come down and basically maybe you have to put it in compatibility mode, or even better, you have to, normally in a client library, you have to say, here's where the API endpoint is to be able to have the client detect what version it is based on what URL you give it. So if you have a suite of microservices, you could have ricksjuju.com slash two major version number or something, right? So that from there I can see then all the different microservices and they each have their own individual URL segment. So your URL may actually be four parts, right? The root domain, a version for the major thing, a subcomponent or a microservice component and then its version that it's currently sitting at as deployed currently. And then the actual rest of the getting work done part of the API string, you know, such that you've got malability in there to update things as you need to. Can I compare my client and plugins? Plugins, I always define plugins as things that adapt behavior to a tool like you can optionally put it in and put it out. A client implements an API, it should do it fully and completely to where users can do whatever they can do with the API so I don't really compare them as the same thing. All right, thank you very much everybody.


one-third I think. Okay, we will short introduce FOSM. The video that you've just seen was some impressions of speakers of how they perceive FOSM and everything. But so if we do a query on the domain, which is of course what matters. So FOSM stands for the free and open source software European developers meeting. And this year we will have more than 300 talks by more than 280 speakers, which will be amazing and a new record. Now what makes FOSM special but are many things, but one of the things is that it's entirely organized by volunteers. So all the people you see running around in yellow t-shirts, they've been working at it for months, weeks, and nobody's paid to do this. Yeah, all for free software of course. Now FOSM was created ten years ago. So the first edition was three and four February in 2000. So today we're 2010. And let me quickly check who was here also during the first edition. Can you can you raise your hand? One, two, three. Yeah. All right. Now let's go back to that first year. Thanks to modern technology, we can easily go back. And so the archive, the way it has a copy of February 5th. So let's check it out. And it is a beautiful web page, especially notice the logo. It is a high definition of a beastie, penguin, gnue animal. So it started and we were called Osdem those days. And let me point to a nice little detail here on this page. So apparently the first edition by singing the free software song all together. Okay, let's go. So in 2002, thank you for your back machine. This is how our website looked like. I think it's very 2002, especially notice the beautiful bear. It could have been posted on, what was it? Well, it's beautiful anyway. Okay. So 2003, we wisely changed to more modern. This is what it looked like in 2004. We didn't have a lot of inspiration. Kind of stick to it. Or maybe if I use a failover. Right. So in 2004, same website again. Then 2005. And then actually, well, it's hard to read. But the web server crashed and we lost our data. Great. So we thought it was a good start for a new website. And so in 2007, new website, new data. And then it changed again in 2008. And, well, that's the same theme that we're still using. So 2009. And this year, it's 2010. This is where we at. Now, what if we never changed our name? What if we would be called Osdem today? Well, luckily the way back machine also allows you to visit parallel universes and everything. And so if we would be called Osdem, right. Okay. Is she maybe sitting here somewhere or no? No. Okay. Well, that was a kind of interesting history of Fossism, the websites, but they're also probably the things you came for tracks and talks. As you probably know, for two thirds of everyone, we have different types of lectures. The first of all, six main tracks. These main tracks are held in the two biggest rooms. This one and one on the other side. These are the six main track lectures. And there are also three keynotes, two keynotes this morning. And one keynotes on Sunday evening about kernel hacking and kernel drivers, et cetera. We also have more than 20 developer rooms. Those are really, really technical lectures. Most of them, at least 30 plus lightning talks. That's 15 minutes timed with timer. So if the speaker tries to go one second longer, the microphone shuts down and the timer just buzz. So it's a little, if you give a lightning talk, be aware of that.  While working around in the H building, this building in the AW, the other building outside, there are also many stands. Be there, we'll talk with people. That's why you are here and not following the conference using video streaming or something. This map is also in the information brochure. You can get at the info desk. The info desk should be here in this building. We are currently in the Jansson. Something interesting to know is that on Sunday afternoon, we will have two fuzzdom buses driving you from this place there where Strum ridden to the Brussels south train station. Approximately every 25 minutes, a bus of 150 people can drive to the train station. So it drives up to eight o'clock, I think. So don't hesitate to stay a little longer if you can and enjoy the talks. But let's take our way back machine again and look at this lecture in 2001. Who can recognize the room? Yeah, one. You were there? You were really following that lecture? So you know the speaker? Richard Stallman, indeed. And you probably also recognize his halo? It's not a disk. It's a halo, but it was a disk in a previous life, of course. Everyone knows that. Richard was one of the very well-known speakers who was at our first fuzzum conference. And we really thank him for that. And, well, the room still hasn't changed, of course. That's the ULB. But we also thank the ULB because we can get almost all the rooms for almost nothing. So without them, we couldn't organize this conference for free. And, yeah. So this is again, yeah, the picture of this auditorium almost full. Of course, more people are coming to see Richard's than myself.  Okay, we have more than talks, people. There's also more activities where you can participate in actively and stuff. There's like key signing. Well, you'd have to be registered on the beforehand. But if you see a long queue of people standing in front of each other reading... That's probably the key signing party so you know where to go. Buffroom. So you can find a list in the AW building. It's marked in the brochure also where exactly on one door of one room where you can schedule birds of a feather meeting for 15 minutes or 30 minutes, maximum 45 minutes each for a project or for a meeting for whatever with a group of people that you want to have a meeting with. There's a hacker rooms. There's two. There's one in the main corridor over here, in the middle of the main corridor up the stairs where you came from probably. And one in the AW building. There are certifications, exams for LPI, BSD, Type 03. So quite a few other things than just booths, death rooms, talks to listen to. So this is a beautiful picture of the key signing in the last year I think. So it will be on Sunday in case you registered and this is what it tends to look like a long queue of a lot of people. There is a room scheduled for the key signing. I know that there will be more than 130 people I think. So the plan is to fit them inside if possible. If it's too difficult then a fail-back of outside will be done again. But the good thing though, this year it's not as cold as last year. Maybe, who has a network device right here? Probably almost everyone with those smartphones. You know from the history that in the past, well, we didn't like to talk about the network subject. So it's a nice weather outside. Fortunately in 2008 there was a change. We bought some WRT devices, some 3-com access points and had a quite stable network. But the whole network was segmented in different micro-nets. Last year Cisco proposed to help. Around Sunday the network was stable because it's still quite a serious job. And around the top moments we had 700 simultaneous users, which is also quite a lot. But this year we thought, well, we can do better of course. Better means 800 meters of fiber, 1 gigabit internet uplink inside around almost two kilometers of fiber. We have 18,000 public IPv4 addresses. So every device that is on the network gets a public IPv4. Be careful if you have an iPhone that is not patched. But that's your own fault then. And 18,000 plus IPv4. Did someone say there is a shortage? I read last, no, two weeks ago there is only 10% left. I think we have 1% of that 10% for the conference. But we also have IPv6. You will notice on the splash page that FOSDEM logo on the, I'm not sure about URL, but the FOSDEM wireless splash page, there's a logo blinking if you are using IPv6. I didn't count the number of IPv6 addresses, but we surely have enough. The SSIDs of course FOSDEM. And right now, and even one or two hours ago, the network was stable and working. There are also some nice statistics you can see online about the usage of the network. So that's really a good point though. But yesterday we weren't very happy honestly. We laid those 800 meters of fiber and while testing it, it didn't work of course. What else? You're organizing conference with an internet uplink of one gigabit and don't have a backup. Well, your backup is 10 megabit half theplex. Is that an option for 3,600 people? No, not really. So out of six strains, we had one strain working. Those who know how fiber works know that you need two strains. So fortunately again, those ULB ICT staff were there and they helped us resupply the cable yesterday evening. So that's finally worked. You might also have noticed we had quite a panic moment when yesterday we realized we had only 5 gigahertz antennas. But fortunately the Cisco guys went back to their office at 1 a.m. and found a box of 102.4 gigahertz antennas. So everything is really fine. We are starting to panic because everything is fine. There must be something that isn't working. So what's the most important thing for a hacker's brain to function? I ask you. It's food, of course. Food, which is why we start every Fosnum event with taking care of the food in fluid form, of course. So we started out very small. We were a few more the next year. A bit more the next year. And, well, yeah. Okay. But enough about this beer event. Let's talk about actual food. Food. Food. Food. Okay. Right. We also have it in other forms. Not so fluid. There's two bars. There's one in addition to the two last years, one bar underneath the auditorium over here. There is one up here. There's burgers and fries in the main street. You walked in through presumably over here. We've also doubled the capacity of those. And so you shouldn't have to starve.  You should be able to function, I think. Right. Money. Money. We need shitloads of money. I said before the conference wouldn't be organisable for free because there are a lot of costs, not only security people, security staff, hardware insurance, transportation of speakers, hotels of speakers, et cetera, et cetera, et cetera. So we usually thank our sponsors. Thank you. A good thing, though, sponsors don't have anything to say about the programme. We refuse sponsorship if they tend to say we want to give a lecture. Eventually, you will notice that some sponsors are giving lectures. But usually it's more, hi, would you like to give a lecture at FOSM? Yeah, sure. Nice. Hey, do you want us to sponsor you? How much money do you have? That's the way how it goes. Of course, the usual sponsors come back at us and ask us, yeah, same deal as last year. We say, yeah, thank you. Okay. Done. So, yeah, again, thank you to all the sponsors. But without the sponsors, we still don't have enough money. So we still, for more than 30 per cent, need the donations to thank you for all the donations we give things in return. Here's a simple table. There are some draws, and the more money you give, the more chance you get to win things. The donations draw, the presents will be given on Sunday during the donation talk. That is scheduled just before the last lecture of Greg about Colonel Drivers. Okay. On to the last point. The mythical FOSDEM dance. Who has seen the FOSDEM dance before? Yeah, yeah, that's okay. And is there somebody who knows the history of the FOSDEM dance? Nobody? Maybe too shy? Okay. Let's take a look at the beginning of the FOSDEM dance, which was in 2006. So we have two of the original organisers here on the picture. Raphael and Damien. And so it all started out with them. Back in the days when an opening stock was done without slides or anything like that, and you just went on stage and told the story. And so the story that they were telling was that Damien was running late for something. Of course. I mean, there's plenty of things to run late for here at FOSDEM. And he was explaining why he was late. And he said, yeah, I was doing things and over there and stuff. And then I had to run. And I had to run. And I had to run. And well, that's basically how the FOSDEM dance originated. So this was in 2001. Now, because this dance was so beautiful in 2007, we did it again in a bit larger numbers. 2008 again, even larger numbers. And then last year, in 2009. Now, this year, it's 2010. So the question is, what will we do this year? Should we do the FOSDEM dance again? Yeah. Okay. Yeah. But of course, it is our 10th anniversary, right? So we should celebrate actually, that is our 10th anniversary, right? No, that's for the French speaking. That's not an option. No, what we had in mind is that we would just do the FOSDEM dance altogether. Or we could of course also sing the free software song. No? So I propose that we will all do it here together.  And then we're going to ask everybody to come here on the stage all together so that we can celebrate our 10th anniversary by doing the FOSDEM dance together. Okay, but first a little demonstration. Do know that we will probably enter the Guinness Book of Records of a conference with the most dancing people. Right. This is serious. No humor, please. Okay. So maybe some more of the stuff for the demonstration. Maybe I can play the air hostess that is in the airplane explaining how to put the safety jacket on, etc. Yes. You just put yourself open your two legs approximately at a similar distance. Take your two arms next to you. Left your right leg. And then do like you're walking or running. That's it. So it's not really difficult, honestly. So now just close that laptop for who has a laptop open and come over here. Yeah. Just to be clear, there's no way to walk outside of this room without coming here. Yes. All the doors should be closing right now. Okay. Come on. Come on. Come on, people. So we're going to take pictures. So don't worry. There's no excuses. Come on, guys. Just come on. Come on the stage. Come in front, please. For the 10th edition. Let's dance. Come on, guys. You guys are already sitting in the right position to those who are sitting behind. We do not forget you. I just confirmation that the doors are closed. So please stand up. You won't be able to properly say that you were at FOSDEM 2010 and less you were at that stage doing the FOSDEM dance with everybody. So get up and join us. Come on. Join us. It's normal that the stage is too small. Some of the rooms are too. So just get a little bit closer. We can all fit. Is this not a conference where people like to talk and meet each other? This is a way to meet each other while dancing. There's still room in here, people. Don't be shy, really. Don't be. The camera is still running, by the way. So this will be all on video.FOSDEM.org and on the common video sites like YouTube. Come on, guys. Just don't be shy. Don't be shy. Okay. That seems quite a number of people. We do understand that some geeks are rather shy, but even in such a crowd, nobody will recognize you. All right. Some more people deciding. Are some people still interested? Come join us. Okay. So Tios, I think we're just packing up. Keep a safe distance.  Okay, so now just spread your legs. Not too far away, of course. Equal distance. Equal distance. Put your arms at your sides. Lift the right leg up. I see many people with their hands in their pockets. Yeah, hands out of the pockets on the side, please. You have to use your arms. Lift the right leg up. Up that right leg up, up, up, up. I should see only one foot everywhere here. Okay, and run. Yeah. Thank you. Use applause for this crowd. Thank you. And enjoy the conference. All right. Thank you, everybody. Fosem has officially started. There is a first lecture coming up in a few minutes. It's about open source in large companies.


Did you know that there are more than twice as many cell phones as people on the planet? There are 7.7 billion people in the world compared with the more than 15 billion cell phones on the planet. It is also interesting to know that of the 15 billion cell phones on the planet, believe it or not, only 4.5 billion people have access to working toilets. And now you know.


Hello, my name is Paul Bredner. I'm the technology evangelist at Instacluster, and this talk is building zero code streaming data pipelines using open source technologies. So it's a lightning talk. It's an update from the talk I gave last year, and it involves two folks. The technologies include Kafka Connect, which is common elastic search and Kibana, which I talked about last year, and the second pipeline PostgreSQL and Supercept. Previously, I talked about building a Kafka Connect pipeline. This is a photo I took in Berlin at Apache Con a few years ago. I wondered at the time whether or perhaps it transferred water or beer. In fact, what I'm going to talk about is a water data source. The source data is the NOAA title data, which comes from a REST API and gives you access to hundreds of title data sensors around the world. The first pipeline consists of the NOAA REST API with data fed into the REST source connector, then Kafka, then the elastic search sync connector, and finally elastic search and Kibana. There's an overview of the architecture. This is an example of one of the visualizations in Kibana, just showing the data as sort of like a graph. You can see things like the lunar day and the title range. What can go wrong? Well, I left the system running for a few days and discovered that some of the connectors were failing, and it turned out that sometimes there were JSON error messages, and sometimes there were even non-JSON errors being fed into the system as well, and the connectors did not cope very well. So what I needed was improved error handling, and I discovered the Apache Camel Kafka Connectors project, which has a very large collection of open source Kafka connectors with robust error handling. So what's new? This is the second path. It's basically a different pipeline with new syncs added, the PostgreSQL sync connector, feeding data into PostgreSQL and then visualization using Apache SuperSet. Some of the challenges around this pipeline were finding open source PostgreSQL sync connectors that work with schema-less JSON data and which can insert that data into JSON-B table columns, and then finally configuring Apache SuperSet to read the JSON-B data and visualize it. SuperSet has lots of visualization options. Here's just one of many examples using a scatterplot. The size and color show the C-level trends and explain perhaps where you should and shouldn't buy property in the near future. I also investigate scalability, how well do both systems scale, and in the conclusions, which you can see in my blogs with the URL there, you'll see more details about the scalability and cost comparison between these two pipelines, a more detailed evaluation of Kafka Connect and a comparison of Elasticsearch versus PostgreSQL and Kibana versus Apache SuperSet. This is part of a 10-part pipeline blog series, and it's got all the details and more. Finally, there's a new service that we're offering at the moment for our cadence for workflows and a new series that I've started called Spinning Your Workflows and Drones with Cadence, which looks at an example drone delivery service. Well, thank you very much. I hope you enjoyed that lightning talk. Please check us out at the website. We have a free trial for two weeks. You can try any of these technologies and more, and I hope you enjoy the rest of the conference. Thank you for listening.


Iran was not far behind. It was at par with the western world. Women could step out without a wheel. Even meet men at public places. Absolutely amazing to see that when she speaks about on par with the western world, she shows you women in skirts. Then she proceeds to tell you that it was common for men and women to mingle in public, as if that's a good thing. Yet again, why is it better to wear skirts and mingle with men? Why that is? Because it is on par with the western world. Understood?


Well, welcome to the White House. I told some people the other day that Nancy and I managed to be very happy here in spite of having a hundred MXs in the basement.  But I'm delighted that all of you were able to be here today for briefings on many of the initiatives that we're undertaking. Of course, it also leaves me in a position of not knowing whether I'm plowing the same ground with whatever I say here. But I'll be brief. They've seen to that with the scheduling. I'm also pleased to tell you that if you haven't been told already that today we're transmitting to the Congress our revised federalism initiative which incorporates four major mega block grants to state and local governments. These legislative proposals represent a continuation and expansion of our efforts to return authority, responsibility and revenue resources to state and local governments. You know, Bernie Baruch once said something of the effect that people who believed that they could lean on government would find that when you lean on government, government begins to lean very heavily on you. And in the two decades between 1960 and 1980, we saw ever accelerating encroachment by the federal government on state and local prerogatives. Narrow and restrictive federal grant and aid programs grew from less than 50 to more than 500, pervading such federal, such obvious local concerns as rat control, troll and sewer extension. The cost of these programs exploded from around $7 billion in 1960 to $95 billion in 1981. And the federal government had too much control. The programs lacked flexibility. The regulations were restrictive. Federal mandates were depleting state and local treasuries. Expenditures were being made for programs that weren't really needed in particular communities and localities. State and local officials began calling for a reordering of priorities and assorting out of responsibilities among various levels of government. Well, we're attempting to address those concerns. In 81, we were successful in consolidating 57 categorical grant programs into nine block grants. A regulatory relief effort directed in large part to removing regulatory manacles which bind state and local governments. This effort continued in 1982 with the enactment of the job training block grant and urban mass transit block grant. The legislative proposal that I'm sending to Congress today will contain four megablock grants and they are a federal state block grant, a federal local block grant, a transportation block grant and a rural housing block grant. It incorporates the input that we've received from state and local officials during the course of the last two years. It'll provide stable and certain funding sources for state and local governments by guaranteeing funding for the programs at levels enacted for fiscal year 1984. And it's not a vehicle for budgetary savings. It'll provide greater flexibility to state and local officials. It'll provide a pass through to local governments for programs which have historically gone to the states but where the states have passed through the funding to local governments. It provides special protections for revenue sharing and the entitlement portion of the community development block grant program. The program will be phased in to avoid dislocations on the state and local governments. And I don't know whether when George was talking to you up here, I'll go back a paragraph or two when I was talking about regulations. I think you know how much has been achieved under his leadership in the task force there to reduce the paperwork and the regulations that have been tying your hands so much and that effort will continue. There are still too many. Now, that in short is the package that we're sending up and I'm asking Congress to give the legislation its immediate attention. Working together, you and I can make government work more effectively for all Americans. I think one of the great things that probably came out of the traumatic experience of the Great Depression was with the best of intentions, the federal government moving in where they saw these great emergencies, then made what was supposed to be temporary medicine for the illness, permanent medicine, even after the patient got better. And the result was a drastic distortion of the historic relationship between state and local entities and the federal government. And we want to get back to what was the original purpose and the original idea of our separation of government levels in this country because I think they're unique in all the world and they were the greatest guarantee of individual freedom that this country has ever known. So we're going to keep at that and I thank you all for being here.