Okay, I think we can probably get started now. So thanks everybody for joining. This is the CNF working group. We meet every Monday at 1600 UTC. Talk about cloud native network functions. Before we dive into the agenda today, is there anything that anyone would like to add? Okay, hearing nothing, I think we can probably jump right in. So the first thing on the agenda today is the use case template that we'll put together. So I saw them on the call earlier. And I know there's still quite a few comments around this, but does anybody want to kind of talk through this? Or does anybody have comments or is there anything you'd like to say? Hope you can hear me. So maybe just as a way of intro for the people who didn't get active in the pull request, the template for the use case was supposed to be informative about the use case, practical use case that should serve as a basis for extracting or recognizing or discussing some best practices that we wanna finally end up with. And I try to put actually the template together in a way to serve this purpose of informing who are the actors or personas or roles in this use case. What do they want to achieve agnostic of technology? How would they expect the system to function? And then ultimately, what do they see as a challenger as a limit or as a suboptimal behavior of the cube native approach and to describe that. So this was a logic behind the template. Happy to tackle specific points if needed. Yeah, so actually have one question. So I see here that you put it in the like the CCDP folder. Now it's actually wondering if it would be better to put it in the use case folder. If we wanna say that's where like the templates are. So rather than, I think you put it under this one. I guess, I see where you did that because it's like the other templates in here. You're right, it was my omission actually. I overlooked when was creating a pull request. So I think I made another commit in a fork. I'm not sure I need to create additional merge request for that to end up in the main repo. So we could do it either by me correcting that and pushing another, creating another pull request or approving that and then I make a correction with additional pull request there. You don't wanna update the current one? I can update the current one as well. Thanks. I need to look that because I couldn't update anymore the branch because the merge request is active. So I would need to probably restart it. That's strange. You're saying you can't commit to your own, the use case template branch? Correct, but I'll look at that and we'll correct it. We'll reach out to you if I have some blocking points. You should be able to modify on your own side in your own and you may need to do a merge because I see that your branches, it might be behind master. Is it possible for me to just change it? Do you know? Not in the user, in the GitHub interface. You'll need to clone it and to do it. Okay. Then you would have to request a merge back to his and then a merge back to the other which is possible. I've done it, but it's... Yeah, good. I don't think the purpose is to get lost in the Git usage. Okay, yeah. The other thing I wanted to chat about just to hear like other people's opinions. So just because this also goes into like an issue that we have open right now, it's like this involved party section and there's kind of like a discussion whether this should be defined in this section or should it reference out to like a separate documentation? Yeah. And so the related issue in case people are interesting is issue number 54 of creating similar to how we have like a use case section and like a proposal section also creating like an actor section. And correct me if I'm wrong, but you said like people should go in here and define that like in the use case whereas some other people are asking like for it to be defined in a separate document. So I was really thinking about what would be the most or easiest and the most meaningful way for people who are writing the use cases to do that. So if we define it in a sense of foreign key and say here are the, you know, you need to hear in this template pick one or more of the roles that are defined in another document might be for some people who are writing that additional burden to look and say, okay, which persona, which actor is there. And if there is no actor that he wanted to do it, he will need to ask to extend that other document. So I settled down on leaving it a bit more freestyle because it's the information that we will extract later on in the best practices and we'll map it to real personas or actors there. But I'm also not very much fixed into whether it's like this or open. So the idea is for the chapter describing the parties. I think I wrongly used the word party. Didn't mean parties, but the different hats that people have or different personas to actually summarize who are the human participants in this use case and then what do they want? What are their needs? And then in the next stage which system components are involved in that use case and then how do they behave? So I felt it's maybe better to give it to the writer of the use case to describe and to think about with some examples but open for discussion. This is Watson, I'm seeing, it seems like people are using the phrase use case and user story almost interchangeably. And I'm wondering, and I've seen in here that we're saying that we're gonna have a requirement for use case, not a requirement for user story and it's wondering what people are thinking about that. Just as an aside, the user story has a lower barrier to entry in the use case. Like if we're gonna say people, if they're gonna submit a principle they need to point to something, the use case has a higher threshold. But yeah, I don't know if anyone else has seen that. Yeah, I was actually gonna bring that up later because we do kind of have like another issue open where we talked about like creating user stories and obviously this pull across is around the use case because that's how we usually define the issue. And I guess maybe that's an open discussion like would we prefer to have user stories or use cases? And yeah. Wait, can we end up with both? Those are two different things. Yeah, exactly. And it's not that they're equivalent in terms of should we use one or the other for this thing, it depends on which thing you're trying to do. Yeah, and it's important here because we're starting to say one of something's required. We're saying that use cases required, their use cases have more information in them than user stories normally. So if we're gonna go by like Ivor Jacobson's definition of use case. So yeah, we're making things on this, right? A use case is broader, but also more theoretical. How I reasoned about the use case, it is something that's very practical and that's kind of mind to mind that the best practice is out of it to trigger the discussion. So real life stories from different angles who are saying, hey, here is my situation. This is how I think it should work and then this should enable me if I move to the cloud native world and then cloud native network function. This is what I will face with or that I'm already facing with and what's the best practice or what's the user story? I would say that the use case could contain many user stories, but if you compare it to the movie, so use case is entire movie and user story is a scene in that movie. I think that's, I'm not sure that's true. If you look at the use case that I put in the other day, the other week, it's specifically use case because it says I need a tool to do a job. A user story would theoretically describe the job, but the problem with user stories is you don't really want somebody to be describing their situation as regards how they're gonna make money out of their customers, it gets complicated. So that BGP use case actually works quite well as a use case. I want BGP and it's reasonably self-evident why you might want BGP. A user story and there's one I've got in motion that I'm trying to, well, actually make look like a user story because it's got altogether too much in the way of opinion in it at the moment would basically say in this instance, it's gonna say, I want to install a CNF on my network. What's it gonna, what are people going to want to do in the process of doing that? And it involves dancing around developing teams who are gonna make the CNF and then hand it to ops teams that are gonna deploy the CNF because potentially with some hedges around it saying potentially those two teams are in or not in the same organization. So a user story is really about describing people's actions and the results they intend to achieve by those actions. But a use case here, as I used it before is really saying, here's a description of a tool that we want to be able to run. We're talking around the questions. So I think one of the questions was do we want to require one and which is it or both? We could say this is requirements and specifically for best practices. So when you're proposing a best practice, what is required? They are two different things. I don't think there's any disagreement on that. And then which if any of them are required? I would say either or both will serve because what you're looking for is justification that there is a problem to solve and being a best practice, this phone fundamentally has to solve a problem. So your suggestion, Anna's, you must have one or the other. Or a list, I mean, any of those, yes. Okay. So maybe I'll add that as a suggestion here. And if I look at the user stories, let's say my daily job, it's usually something very specific. As a network admin, I need whatever functionality X in order to do thing Y. So when I think of user story, it is very specific, very, very narrow focus, but also gives some very good scope for it. And the use case is more like, broader context of this whole thing. I think that's the problem with these terms is we're not 100% consistent how we define them because what you're calling a use case, I would call that are fine, I've been tainted by rally, I would call an epic, which is another form of user story with a broad scope. But the reason I'm distinguishing in my head, use case doesn't necessarily involve actors. It involves more about functionality. I am trying to do this thing and this tool would help me to do it. Or there is a thing I want to be able, doesn't necessarily have to involve people. So whatever words we use to categorize those, I think the important thing is requirements, documents are required to justify whatever we suggest you refer to use cases, user stories and any other things in this folder. And so I guess the question is, so what does that mean for this poor request? Or are people happy with it the way it is? Like taking into account our previous conversations or the things people like changed? Essentially, I think what is very much needed for us to have is a reference anchored in the real life. Anchored in the real life. This is really an essence that we need to bring out of either user story or use case or whatever. So that we can, when somebody proposes something, be able to discuss around it to understand why this story is like a real case. Is it a theoretical case? Is it a very broad case happening everywhere or very focused niche one? And then out of that derive understanding of what should be done in order to make things better in a cloud native sense. And this last piece is best practice actually, which I mentioned. So I could work this PR around the systems so that we eliminate people out of it. And if we wanted to, and then simply say how the system should behave and how the systems, what are the challenges with the systems when we talk about Qubenative approach. So this would give us that scope and we can keep the users in the user stories. But I felt the touching actors from systems, because actors always have expectation of the system, might give us too much breakdown. We'll potentially start dealing with, how do we categorize the things? Is it here or there? And so I would suggest that put it together into one kind of, yeah, I don't know how we would call it, merge of user story and use case. One of the reference documents or real life reference, whatever. So you were saying that the template should be an overall template for use cases or user stories and people can fill it out to their use case or user story, is that correct? More or less, I think it should have been looked at once again and maybe extended or more generalized. Maybe we could have options in the templates, like if you don't need this chapter, please skip and focus on the other one, something like that I have in mind. Yeah, so maybe with that framing, people want to kind of like look through this pull request again this week and see what like, yeah, if there's more things that should be added or like contextualized or things like that. Taylor, I see you're unmuting. I guess with the confusion on use cases and user story, my gut feel on it is that we should have two different templates. And ideally, not only a template, but if we can point to two examples that people go, yeah, that's a good user story. I understand why that's a user story. And then the same for the use case, then when someone is looking at the template, they can go over and look at real information, not just loremepsum, and it's filled out. My suspicion here is that while Vux stuff is useful at the moment, the answer is, before we commit it, we try and use it to see how well it's working, and then we can adapt it to what does actually work when we try and put real information in. Or alternatively, we just commit it and we say here is a work, for example, try this. It's not mandatory that you use this, but we recommend this as a starting point. It depends on what we're trying to do here. Are we trying to tell people they must comply with this template or are we trying to tell people that if they use something like this template, their job will be easier? I mean, ultimately, it boils down to what we want for the best practice proposal. And then the suggestion here is, don't bring any best practice if you cannot reference it into a real situation. Don't even think about it. Yeah, I guess. But I'm confused by that because this is a use case template, so not best practice template. I'm not saying that this is a... So if you propose a best practice, you need to reference it to something in the real life, be it the use case, be it the user story, be it whatever elaboration of the case. Just that best practice should not exist in isolation. Yeah, I certainly agree with that. I think we all do, actually. I think we have consensus. So I'm fine with that. But on this particular document, yes. So for best practices, we need context use cases. For use cases, we want a use case to be complete and this is a means of trying to get people to get it to be complete by having all of the information it's gonna need, not suddenly be wanting something that we forget later on. But if we attempt to write a few more use cases, I wonder whether we could do a better job of that because we'll see where it turns out they do need information and where it turns out they don't. And then you'd have rather than us basically arguing somewhat academically about what would be good and what would be bad, we could say, this is what would work best for us because now we've got a little bit practice, we've got a hands dirty. Actually, I had in mind to write one or two use cases, but I put that on hold until we discuss the template and not to write something and then according to template, then there is a lot of other ideas. So I can certainly proceed with that and maybe if somebody else would volunteer and proceed with the additional one, maybe following partially or fully the template and then exactly what you said, Jan, get the hands dirty and then simply say, okay, we had this struggle with this template or we couldn't fit this or that and then we adapt it. We can leave it as a pull request. I can bring additional commit with a concrete example. Yeah, sorry, I'll tell you. The template doesn't, or I'll say the update to the read me, doesn't say use of the template is required. It's not, we're not demanding that. So the template is to help people if you have no idea what you're doing, I guess, for building a use case or try to provide answers to questions. So I'm not opposed, I'll say, to moving forward on merging something. Just so if people want it, if they want to build a use case and they have a lot of content, they don't know how to format it and this helps them and that would be fine too. We can always go back. One thing that I would suggest is if we can link out to references for the standard definitions for use cases and user stories would probably be good, maybe at the top of, or somewhere in here, so that we're not, we don't have to come up with our own thing. These are old terms and there's probably a lot of templates. Yeah, I guess. So I was already putting the comments, plus one for committing now and perfecting later. I guess maybe my suggestion is it sounds like both looking in, like both have use cases that they are considering writing up. Maybe I propose try using this template and come back next week. And if you don't have any major issues, we say this is our first draft of the template and this is what we're going with for now, but obviously it's completely open to be perfecting later. We can always change things. This isn't just a static document that keeps on living. So I think maybe we, yeah, so we try it out if there's nothing wrong, then we say this is what we're using for now. And then as we find things we'd like to change, modify or update, we can do that in the future. So rather than getting stuck on is this template perfect? Being like this is our first step and then kind of moving from there. Yeah, I think I would go a step further than that. I would say if at any point in the week we think this template is good enough, if it hangs together in itself consistent, then if everybody's happy, we can get it in as well. There's no need for it to be perfect. It's sitting in review forever is not helping us. It just gives us somewhere to kind of needle, work and basically point out all the shortcomings of the document, that's not helping. So I think there's a, I don't know how many comments really do sort of point to strong need for change, but if we go through that, I think we could probably have this ready for certainly next week and possibly in the week. Now, does that sound like a reason? A main item to address side of this that there didn't seem to be a big disagreement was about the actors or personas or whatever I want to call them the rules and being able to break that out. Well, if we got nowhere else to put it right now, then why don't we put it in here and then break it out in a separate commit, which is a, you know, and then fine, the actor list will be maybe not have perfectly considered opinion, but again, if this is a place to start with the use case, that's fine. And then we can put more consideration into the actor list and then just refer it out when we put the actor list committing. That sounds good. Okay.  Well, I just, I haven't reviewed the document yet, but I just saw a few HTML entries. So you can remove those as well, like all the PR entries. Yeah, those ones. Oh, yeah. Like... Yeah, just for formatting. They're not visible in the, if you view file, go to view file in the three dots up. Yeah, they're not there. Three dots. Oh. No, still see three dots upper, right? Yeah, view file. Then it's actually breaking the lines. Go up, they were here. Oh, yeah. I think the writer of the use case will anyway remove the content. Okay. Yeah, I guess if there's any HTML stuff, I mean, yeah. If you go down, it's past the linting on merge requests or pull requests. So I wasn't too much upset, but thanks, Victor. Great. Then I guess this kind of discussion goes into the next one about like user stories. And I guess this issue is like, there should be user stories too. I guess my question was, do we want to close this? Do we want to have a separate thing? And it sounds like kind of from the previous discussion is that we see user stories as like a different way to justify a best practice. So we should have use cases and also user stories. So we should leave this issue open for right now. I'm just going to comment this on the issue too. So we have that too. And then this next issue too is also the issue for defining the actors and their roles. But as we said before, this is going to be in a later PR. So I don't know if somebody wants to volunteer to take that up. Feel free to raise your hand right now or otherwise we can wait. Is anybody interested in taking the first stab at defining the actors and moving forward with that? I think Taylor's got a proposal and I've had some thoughts on this. So if we take it together and we can have a proposal, we can put full request out. Okay. Sorry, Taylor, I'm volunteering you, who are you right now? I'm good, you're on that. Okay, I'm going to sign both of you on this year right now. Invoke if you want to review or talk with us about it, let us know. Okay, great. Then the next thing is, so this is after the comments and discussions last week around like the governance, we tried to define things a little bit more. So I think there's some confusion about what all the roles do and what they all mean. So we tried to like write something and obviously this is, I mean the governance is up to the groups. This isn't like how it, saying this is how it is. So this is, it would be great to have feedback on this. So one is, oops, wrong link. One is around defining the max representation. So saying that one company can't come in and kind of control the whole control the whole thing. And so what this is is one person from any company can hold a chair roll and also one third of the tech leads can be from one company at a time. And I think Taylor, where did you pull this from? Is this from Kubernetes? Yeah, I think that was the, I don't remember, it was a Kubernetes or TSE type of thing. Yes, this is pulled from another project. Taylor, do you mind if I, because Ian's comment was there's talking about members of committee, but we don't have members of the committee. So in this case, it refers to tech leads. Are you fine if I commit this? Yeah, absolutely. So we don't have a committee, actually. Yeah. So I think Ian, that should resolve your comments too. I need to give this a review properly. I think that, yeah, okay. Yeah, you're, I mean, I see no problem with your diffs. That's fine.  We've worked out what we're drawing people from, but maybe not what they do quite yet. And so that's fine. We're solving them as separate problems. I think it's good. I don't have any problems with this. So maybe I'll leave this open for one more week, just that. Well, if we don't hold it open on my account leave, let me just give a quick skim and see whether I like it. I guess we have four approvals right now. One, two, three, four. Give me one. You're about to get this. Okay, I guess then, I guess, yeah. If there's no more major disagreements, I think we can probably merge this too. So thanks, Victor, for merging that. So last chance. I think there's might still be inconsistency with the terms company and organization. Is there interchangeably? Company and this one is. So is it all company now? If that's the situation, then it's okay. Yes, it's all companies now. I don't see. Yeah, there's no organization left. We don't organization at all? No, we just say company. I think the other PR for the voting does say organization. Okay, so maybe. It seems like. Company slash organization. I gave a link to the, it's a Kubernetes steering committee. There's other ones too, but that was one of the main ones. Okay, yeah, you're right. Is it easiest just to change just the company slash organization? We're getting to the point that we're being paranoid here. If we actually start reading it, we hope and pray that these rules will never kick in. But if they do. If they do, then we interpret them the way we want to interpret them as well. So we've got a little bit of options. And there's no lawyers in this. Yeah, that's if it goes to that, we probably won't be on the call in. There's a committee again. We're definitely having a committee. That's very clear. Committee. Editing. Yeah. Entire company slash organization, companies, organizations. Yeah. Okay, let me. I'll refresh and commit this. Or do you already get it?  It's fine. And then, yeah. Thanks for pointing that out. And then also related to that is around the PR approval process, because I think there is, this wasn't defined anywhere. So this is, I started this as a discussion because I didn't want to start it as a pull request because I think this is like open of kind of defining what each of the roles do and kind of like what, I don't want to say power, but maybe responsibility that they have. And kind of the way that I thought about this was kind of right, though the lowest bar should be like the easiest. Oh, thanks for the comment. Yeah, we can, if you want to, you can go in and put slash people, but I think company slash organization is as far as I'll go today. But essentially, so right, the use cases is the lowest kind of like let's say bar with one tech lead and two community members. The charter updates is two chairs, one tech lead and three community members. The best practices is two tech leads and three community members. And kind of the idea here is showing that, like tech leads are really important for doing this because they're the ones actually like deep diving into this and neither the chairs nor the tech leads completely have like the final say, we want to have community input in everything that we do. So while it's important because they're helping kind of like, let's say organize or like lead the group, they're not, they don't have saying like, this is how it is and this is exactly how you do it, but it's also driven by the community too. So this first idea I'd like to hear like some thoughts on like these different roles and responsibilities. Can't tell if silence is good or bad. I'm not sure that those numbers necessarily work, but on the other hand, I mean, if we've got a group, then it seems like a quorum and then a majority would make more sense for charter updates, but you know, conceptually the idea that we deal with this in a separate document and we basically put thresholds in place seems perfectly logical. You know, this also feels like it's a little complex as well. It's hiring number has to. Yeah, if you go back to, again, my experience with the open stack, I know it's anathema around here, but I'll just give it as an example, then it would be good. Most pull requests would be approved by two core developers agreeing and that was maybe a little centralized, but it wasn't a terrible idea. Seems to me that there's not necessarily the use case and the best practice side of things. There's not necessarily any great value in having them differ. The charter updates, I think, is the one that needs to stand separate. And that would seem to be define a quorum and then define a majority. And to be perfectly honest, stick it on the tech leads because the community leaders, the community members are electing tech leads to represent them. Yeah, this is what I know. I think we should consider the option of just the veto power for stakeholders. So for in our case, service providers, the users and the ability for them to maybe have veto power on their best practice and some of the role for just that veto power and they don't have to vote for it, but they can say no, maybe a quorum. I would put, I guess, tying in with what Watson is saying, plus, I guess, both Ann and Frederick, y'all were talking about the complexity. The two things that I think are the most critical to care about with regard to getting approvals are the charter and the best practices. So charter, I think that one's probably easier to say we wanna be careful on what happens there and the chairs are supposed to help with that whoever's elected or that's one of their main things is trying to keep that moving forward. The best practice ties in with stuff. Ian, you've talked about and other people, the best practices eventually, if they're adopted, we say as a group, yes, we have consensus enough to say, this is a good breast practice. They're gonna go into RFPs and stuff. That's gonna affect companies and organizations that are developing and it's going to be part of what service providers with Watson is just mentioning. So there needs to be something about the best practice. I think it's important enough that we maybe differentiate that. Even if all the rest, like remove use cases, maybe the simple one under it is, we want some number of approvers before something goes forward. But the best practices I think is equally as important as the charter because of the impact on adoption. Yeah, I think my point though is there's a separation between the kind, the personal group that creates things and then there's a separation and then there's another group that is affected by those things that are created. So you could call those that second group stakeholders if you want, but that second group, there's certain limitations they should have on what someone's creating something. Maybe the direction maybe is probably not the best place for them to be, they can create something if they want but they shouldn't be saying, oh, don't create this kind of thing. But when it comes down to saying, oh, this is the best for everyone and you're the one consuming it, that affects you. And so that's where getting a stake, the veto power from. It can be abstracted away from this and put into government and things like that. Who is it that's affected by someone polluting the water but someone else is the person that does irrigation or does all these other things with the water, they're not necessarily experts at mining or managing water, but they do want to say, no, you can't do that in my neighborhood or my city or something. And do you think that city councils have enough knowledge about mining to make a decision like that? They have enough to veto it. They don't have enough to say, here's how you will mine or here's how you will, they don't know anything about innovation of mining but they can say, yeah, don't pollute my water. That's okay, but that's some kind of an external interface but I think they don't have enough knowledge to say like what kind of a drilling head you should use. Definitely, definitely you're right. And then we are talking about this kind of best practices also. Yeah, so having the stakeholder or in our, you know, in our example, the citizen but you could say the service provider or whatever, they aren't saying, go ahead and move around or go ahead and here are the very specific kinds and they don't have power over here the very specific kinds of drilling, for example you're saying, or very specific kinds of technology you're gonna use to solve the problem. But they can say that they wanna, oh, microservices that is something or microservices, no, that is not something that we want at a higher level. So it's more of a, and it's a veto power, it's no, it isn't yes. I mean, and they have veto power anyways, right? They can say, no, I don't wanna buy your stuff anyway. So it's not like, you know, this is getting information earlier. Yeah, that sounds like a minus two in the open-style world. So I guess it's perfect, okay. What is the, if you have a, some, I guess I'm thinking like in a justice or law where someone disagrees, it doesn't block but it's noted so that it's public notice that there was disagreement on something moving forward. I can't remember the term for that. A complaint box that no one reads. No, it's like a big controversial law and you talk about the dissent, so dissenting view. I'm just thinking of if, what you're saying. So the first is you're saying veto power and no, which means if a best practice proposal is put forward and you have, let's say, most of the community, the San Francisco community is like, yes, let's do it, but you have someone with veto power that says no, does that just block it and we don't adopt it or would we want to put the note that here's the problem that someone had with moving this forward. So it's a part of the proposal. Well, there's one individual saying no and there's a quorum. So I like that quorum. A lot more sense. If you had a, so you now have a role, so this SP, it could be that we're saying this is all going towards SPs as the end users for the product of the best practices. So applications and infrastructure, whatever is developed following set of best practices, the SPs are gonna consume that. And now we have a quorum of SP representatives that say, no, we don't want y'all to adopt that. We would prefer not to see it. That would make sense. So we don't have that role right now. We'd need to figure that out, but it makes sense to me what you're saying, Watson. This is about the PR practice, a PR going in. So I'm not sure what you're thinking. Do you have any thoughts on how that would tie in with this or that you could add into the discussion otherwise later on, Watson? So I just have one comment. This is the best practices. Go ahead. Oh, yeah. Just referring, this discussion is only focused on the voting part. Because I guess we're assuming that NEPR has to address all the comments and doesn't have any inter-issues or things like that. So we are considered those as part of the approval process or it's just, we're just assuming that those are going to be there. We should definitely wrap this down. So this is only for the approvers. This says approval process, what we should, it really could be the discussion is how many approvers do we need in the PR process before we approve a merge? Okay. So it's one item out of all the rest and all those other things are important. Yeah. This is a good conversation, but I'm going to push it to the GitHub discussion until next week. Cause it seems like we still have some more ideas. So I'd like to hear kind of other people put their thoughts in here. Cause I don't think we're going to come to a conclusion today. So it'd be great to have some more thoughts in there. Cause we only have five minutes left for today. I just wanted to get through kind of like the last couple of things on the agenda. One of them being the voting process. So there is some discussion here, but there hasn't been kind of anything since last week. I just wanted to check in if people had had time to look at this, if they had any more questions, things like that. Cause I think this is kind of like an important thing cause the elections are going to be coming up here. So just reminding people to look at this cause it would be great to kind of come to a conclusion and get it committed next week. Is there anything anyone would like to bring up about this PR right now? I mean, obviously feel free to on GitHub too. Okay. So four minutes left. I also wanted to bring to everybody's attention that the self-nomination period is currently open. And just as a reminder, in case you forgot, there's also a link to here to nominate yourself for either a co-chair or a tech lead position. Please send the information to the mailing list. We'll get it approved there. And so far we do have nominations for a co-chair from Jeffrey in the service provider co-chair from Ian for co-chair in the CNF developer co-chair position and also from book for the co-chair or tech lead. So he's nominating himself for both. That means we currently don't have anybody yet from the Kubernetes community who's self-nominated themselves and we only have one tech lead. So all the conversations we were having earlier about the PR approval process would be for not if we may have one tech lead because none of that cleared the bar. So I encourage people. If you're interested, please consider running. And I know I've talked to a couple of people who have who we're interested in running and just haven't submitted yet. So if you have any questions, please feel free to reach out to me or Taylor to chat about if it's you're interested in. Yeah, are there any questions about the self-nomination period? It does end next Monday. I'd like to propose extending that.  Okay. Trying to address some confusion. So extend both of them by at least one week and maybe extend the tech leads. We had more interest earlier and I'm trying to get some responses, especially on the Kubernetes community. There was discussions before the holidays and there's been some calls after. Maybe extend that one a week out so it's staggered. We have the chairs come in but then we could still have tech leads. And I know that there's some of the people have said they're talking internally. So I think there's the coordination internal to get back with us. I must admit I'm a bit confused about tech leads because I'm not sure I know what the tech domains are. And so every candidate kind of defines the domain and then proposes themselves as the leader. But can we try to somehow flesh out ideas for what are the tech domains that we're looking for leaders for? Yeah, so this is the part of the reason, Bill. I wanna extend tech leads further because of the confusion. The short would be we can have more than one. There's no limit on the number of tech leads. Although probably everybody shouldn't just go for it. The main idea is if there's an area that you think is that we need to, that's important to focus on for the CNF working group and you have time and a passion to go into it, then you can put yourself forward for it. We don't have to say a specific domain. You may say, I wanna help with use cases. So that could be general or you could say you wanna help with a maybe a best practice area like handling state in a cloud native way. You're like, I'm passionate about that because we're building applications that need to deal with state. So I wanna go into that and that could be a focus area. But we're also talking about nominations for both chairs and tech leads that are going a year, I believe is the same, isn't it, Bill? It's a year, but which means you may be focused on let's say cloud native state because that's an area that you care about now but three months from now, that may not be the focus but you probably have multiple things that are gonna be happening. So you need to be able to shift your focus and not just think I'm doing cloud native state for a year. You'll do it as long as it's something that's relevant. I don't wanna lock you into one, anyone into one specific small area as a tech lead. Yeah, I was more thinking about maybe trying to get more people involved and I'm trying to get some of my colleagues interested. So it would have helped me if there were already a few areas or domains listed as areas that we're looking for, like security, for example. Are we interested in somebody with that kind of expertise? Are we not? Absolutely. Yeah, I mean, actually maybe a good first place to start would actually be in the, oops, where, oh, where I can't find it, would be the different areas outlined here. Right, so those are based on categories trying to take a lot of the cloud native principles where I can amend the various categories and that's really what we're saying. So anything, if we go from cloud native principles and you start going down into an area, you can be at a higher level and save security. I wanna, I care about anything security. Well, that's gonna cover a lot of things where you could start getting down and go deployment issues with security. So it's whatever you want on that, but definitely the cloud native principles would be the first place. And I gave another link, fundamental concepts that I would say even a little bit higher than what this is, but targeting cloud native principles. So yeah, so we'll hopefully send out some information later this week to clarify what the different areas are. I mean, we'll also extend the nomination period for a week. So we are a bit over. So thanks everybody that could stay on the line. I appreciate it. Unless anybody has anything else, I think we can probably close for today. Okay, thanks everyone for joining. Thank you, bye. Thanks everybody. Thanks.


Around Dodge City and in the territory on West, there's just one way to handle the killers of the spoilers, and that's with the U.S. Marshal and the smell of gun smoke. Gun smoke, starring William Conrad, the story of the violence that moved West with Young America, and the story of a man who moved with it. I'm that man, Matt Dillon, United States Marshal, the first man they look for and the last they want to meet. It's a chancey job, and it makes a man watchful, and a little lonely. This is Frank Knight speaking for the world's most honored watch, Laund Jean. When the West was being won, Laund Jean was there. Old records show sales of Laund Jean watches in the silver mining towns of Colorado and Nevada, the gold mining areas of California. A fine gold watch, preferably a Laund Jean, was one of the first luxuries purchased by a lucky prospector, for then as now the name Laund Jean identified the world's most honored watch. Laund Jean watches won their first World's Fair grand prize in 1878, won grand prizes in Paris, Brussels, Philadelphia, and at many other places. Right now, Laund Jean watches are winning comparable successes in the accuracy competitions in European national observatories. Today, you'll needn't make a gold strike to own a Laund Jean. Many beautiful models for ladies and gentlemen are priced as low as $75. Visit your authorized Laund Jean with no jeweler. He will be honored to serve you. Get back inside. Close the door. I don't know. Be quiet. I'm free. Open the door. Let him in. Open the door. Hey, let me hide. Will you let me hide? Don't let him get me. Your boy, mister. You hurt? No, you's trying to hide, Rourke. I'm going to shoot him, please. You shot a dying man. He wasn't dying long.  He was still dead.  Where's your daddy? Dad. Let the boy talk. Where's your daddy, I said? He's dead. Hmm. You two living here all alone? We ain't scared. Of course you ain't. Too bad I had to have it right in your kitchen, ma'am. Rourke has had that coming a long time. What are you going to do, mister? Well, just nothing, ma'am. Nothing at all if you'll let me. What do you mean? You just remember this was my affair. Mine and Rourke's. And now I'll walk right on out of here. Forget about it. As long as you do forget about it. Marshall's going to come after you. You're not happy.  I guess you're right, though. I guess he does talk a much too much. No, no, he don't talk. I don't. I'm glad to hear that.  Wouldn't it? He won't talk. I promise. That's good. Real good. And both of you just stand quiet till I get away from here. Won't be no trouble. What about him? I forgot my manners. Well, I guess I'd better get him out of here. Foxy, in the world are you doing it? Oh, Doc. What are you digging there? Is that a grave? Grave? Oh, my goodness. Doc, don't talk like that. This here is a garden. A what? A garden. It looks more like a buffalo wallow. Does Matt know that you're doing this right outside of his back door? No, he don't. I'm kind of surprising him. Besides, I ain't hurting nothing, Doc.  I can see that. Let me show you how my garden's going to be. Now, see, right here is where the beans is going. And here is the carrot. And yonder's pea. I don't see anything. Well, they ain't planted yet, but I got everything ready. All I need now is a seed. Now, where did this garden idea come from? You. Oh, what do you mean? Well, sure.  Scullery. Yeah, from not eating enough greens and sardines. Oh, yeah. Oh, that scurvy chest. Not scullery, Dillon. Well, whatever it is, I got to thinking on it and decided to do something about it so I don't get that disease of me. Oh, I know. Well, that's fine, yes. But as I remember it, that talk we had was months ago. That's right. It was. And I've been worrying about it to everything.  The trouble is I'm broke. Plum. I can't buy no seed. Oh, a seed? Well, let me see. Oh, no, no, no, and I don't look at me. Well, now, Doc, you'd like a plate of greens every now and then, wouldn't you? Well, sure I will, but not enough to pay for the seed. You might get scullery, Doc. That scurvy chest, and I won't get it. Wouldn't pay very much by them seeding for Mr. Dillon. It's just a few pennies is all, Doc. And then none of us would never have to worry. Well, not just to now. Suppose you did get those seeds. Now, you think everything that you planned is going to bloom like a sunflower? Well, my gracious. Doc, this ain't no problem. You just kind of push him a little seed in the ground and for you know it, you got that. Oh, oh, my. You're quite a farmer.  All right. All right, Justin. All right, here's some money. There.  Well, thank you, Doc. And from now on, you're half owner of this garden. You can have part of whatever I grow free. Oh, well, that's good enough, Justin. Pretty warm. It usually is in the sun. Must be near noon. Yeah, let me see. It's just about quarter to 12. Quarter to 12. My gracious, I'm going to be late. Late? Well, you're good. Or to meet Mr. Dillon at Del Monaco. Lunch, all right. What about our garden? I'll get to it, Doc. But after all, if Doc ain't had no green vegetables for all this time, it ain't going to hurt us none the way a little longer. I don't mind a man making money, Mr. Dillon, to buy jing I don't think he should be making it all off of me.  Why that, Zach Holden? Charging 15 cents for a meal like that. I swear that steak still had a piece of the hide on it. Oh, prices are going up, Chester. You just got to face it. But it's getting so, the man don't hardly have nothing left after feeding himself a little, and that's a fact. What's the honor, Mr. Dillon? There's a lady going into the office. Uh-huh. Reckon what she wants. And if she's like most women, we won't be long and finding out. Uh, you wanted to see me, ma'am? You're, you're the Marshal? Yes, and that's right, Matt Dillon. Uh, this is Chester Proudfoot. How you do, ma'am? How did you? Uh, I'm Cora Meadows, Marshal. My boy and I live out west of town, the peace.  Thank you. Uh, Mr. Dillon? Yeah, what, Chester? As long as you and Ms. Meadows is going to be talking for a spell, I believe I'll just go on back and see Zach Holden about charging that outlandish price for a meal. It's still sticking in my craw. All right, Chester, you do that. Excuse me, ma'am. Now, Ms. Meadows? Marshal, I don't rightly know what to do. Well, I suppose you just tell me what's the matter. Well, that's just it, Marshal. I'm afraid of what'll happen if I tell you not. I'm afraid of what'll happen if I don't. You need help? Yes, Marshal. I need help, all right. Uh-huh. Uh, just speak right out. Well, it's my boy. My boy, Tad, that he's missing. Oh.  Oh, wait a minute. Uh, what man are you talking about? The one that shot that fella out to my place yesterday. He shot him down just like it was an animal.  Yes, Marshal, I am. Well, I think you better go back to the beginning and tell me the whole story. Did he tell you where the man was drugged from, Mr. Dillon? Yeah, out the kitchen door, Chester. The track should be along here somewhere. Yeah, sure. Ah, over here, Chester. See there? Looks like heel marks. Yeah. Beating over them bushes. Yeah, they sure do. Come on. I've taken much time with him. What do you mean, good? It took the trouble to bury him. And when a man shoots you in the back, he's not going to worry about your funeral, Chester. I've seen him before, Mr. Dillon. He was at the long branch a lot playing cards. Yeah, it's a gambler by the name of Rourke. I guess the bury ends up to us. Yes, sir. I came as soon as I got your message, Doc. Is there something wrong? Yes, Matt, there is. Come to the other room. Huh? It's this youngster, Matt. I found him by the roof. Oh, what's the matter with him? He's been beaten. Cruely, brutally beaten. I don't even know if I could bring him out of it for a while, eh? Do you say who he is? No, and that's a funny thing, Matt. He hasn't talked at all. He's been conscious most of the day, but he won't say a word. I guess you can blame him. The way we did this was trying to scare him to death, even if it didn't quite kill him. Is it okay if I try to talk to him? Well, I guess you won't hurt him if you don't talk. You know who he is? Yeah, I think so. Hello, Tad. Tad, I'm Marshall Dillon.  I'm gonna help you. I'm gonna help you and help your mother. Now, you want me to catch the man who did this, don't you? I can do it if you'll help me.  Tad, look, the only way to be sure that you're safe is to bring this man in. There's not gonna answer that. No, I guess not. All right, Doc, let's leave him alone. I think you're gonna keep him here, Jack. Oh, expect to be up by tomorrow if he's quiet. The boy recovers many fasts. Uh, would he be well enough to stay in town with the kitty for a few days? Sure, man, I guess so, but if you know who he is, why don't you take him home? Well, I'll tell you later, Doc, but, uh, there are a couple of people I want to see first. Oh, Marshall, get you a drink. No, thanks, Sam. There's Kitty around. She's upstairs, Marshall. I'll have you down in a minute or two.  Thanks. Sure. You looking for me? Ah, yeah, I'd like to talk to you, Kitty. I'm coming down. All right. Come on over to a table and sit down. No, no, thanks, Kitty. I haven't got time. I would ask you to do a favor for me. Well, sure, ma'am. What is it? I want you to take care of a small boy for me for a couple of days. A boy? Yeah. What is he, a runaway? No, not exactly, but, uh, I'd like to have you keep him around the long branch for a day or two and give him the run of the place. It doesn't sound exactly like the best surroundings for a young boy, man. You're going to have to trust my judgment, Kitty. Will you do it for me? Well, sure. I guess so. If you want me to... I do want you to. I'll explain later. Yeah. Thanks, Kitty. Sure, ma'am. Tad, is it about Tad? Yes, it is, ma'am. I'm pretty sure we found him. Well, where is he? Is he all right? He's at Doc Adams' office. Doc? He's all right now, Miss Meadows, but, uh...  Beat him? I think the killer beat him to keep him quiet. And it worked because Tad won't talk to anybody. I'll go get him, Marshal. I'll fetch him home. Well, that's what I want to talk to you about, Miss Meadows. I'd like to keep the boy in town for a few days.  I'll go get him right now. Now, will you listen to me for a minute, Miss Meadows? You've got to understand that as long as this man is on the loose, neither you or Tad is going to be safe. Well, we're not going to get mixed up in that no more, Marshal. Me and Tad will stay right out here and never say a word more. Yeah, but if the killer gets worried about you, it won't matter where you are, especially if he knows that you've been to see me. I shouldn't have come. No, you did right to come, Miss Meadows. And if you let me keep Tad in town for a few days, maybe we can get this man.  You mean you want Tad to help you? Well, he won't know anything about it, ma'am. He'll be perfectly safe. Oh, no, Marshal. You've got no right. I'm not talking about rights, ma'am. I'm talking about...  I want him here at home. Now, you just let him recognize that gunman for us, and he'll be home safe and for good. He's been hurt bad enough already. He won't be hurt, ma'am. Now, Chester or I will be watching him every minute. And as soon as it's over, I'll bring him right home. Tad's a good boy. He never had a beating before. Well, I want to see that he doesn't ever have another one. One thing about playing poker that you might well learn right off. It ain't so much what you've got in your hand as what folks think you've got. Do you understand that? I think so, Mr. Proffler. Some folks just has a face for it, and that's a fact.  Give me one card, please. All right.  Now, that's good. That is good. You ain't letting on one bit. Now, I'll take one myself. Hey! It wasn't like this wouldn't happen in six months of Sundays.  Mr. Done comes back. Well, he ought to be here pretty soon. He went out to see your mother, Tad. He wanted her to know that you've been doing just fine these last few days. Oh, yes. I hope she's fine, too. I should like to go home. Hello, Kitty. Oh, hello, man. Mr. Done, you know what I just did? How's Laura? Oh, she's fine, Tad. She said to tell you not to worry about anything, and she sent you some clean clothes. Did she say when I could come home? I ought to be soon. Why don't you take those clothes on up to the room, honey? Oh, yes, sir.  Oh, thank you, Mr. Kitty. Mr. Done, do you know what happened just a minute ago? No. I was drawn to inside space. Oh, my God! What? What is it, boy? There he is. That's our man. Take the boy upstairs. Yes, sir, ma'am. Mission Marshall. A man walk in here for a drink. We've been waiting for you, Mr. The Boy, ain't I? Well, I don't know what you're talking about. I never saw that boy four in my life. You never expected to see him again, either. At least not alive. After that beating you gave him. Beat? Now, you listen, Marshall. You listen to me.  And so does his mother. She ain't here. She'll be here in good time. Marshall. You ain't taking me. You better look out, Mr. Because I'm not turning my back on you like Roark did. You got him, Mr. Newell? Yeah. Well, anybody can shoot a man, Shuster. That's that boy's mother what she did that took real courage. Come on, let's take Tad home. I think his mother's waited long enough.


Good morning cyber traders Happy Tuesday everybody Second of July lesson two days to the big day of fourth of July has everybody doing good to see you all All right. Good morning to you too mark Chuck Lawrence Lewis Dave and All right, everyone all the cyber traders So it looks like a typical what I kind of predicted what was gonna happen as of last week And I'm gonna say it again tomorrow and by the way, just give everyone a heads up tomorrow is a half day in the market market close at one o'clock and then Then what we have and then we have Friday is actually a full day Just give everyone a little heads up regarding about the market But before we start going through the watch list and see what happened yesterday Just remember today's we moved our live trading class with me where we do where we do our open house every week That is today at 12 o'clock and then we're gonna move traders talk from took from Tuesday Which is today to tomorrow? So we'll see you all that and you know that is a very great event with with Josh where we kind of open for live questions and answers and That's a very important thing. We know That you guys learn a lot just by coming in that event but regarding Regarding about everyone from Canada. Leta said fireworks here last night Canada day Well, we always love our Canadians love you. Thank you very much all my Canadian friends out there hopefully enjoy Canada day and You know low fireworks to myself. I'll try not to blow off any fingers, but actually New York It's illegal now. I miss those days, but uh, I'll go somewhere and I'll go watch it Yep, don't miss out traders talk definitely event. That's good. We're gonna move that to Wednesday. All right in the meantime guys Let's talk about what happened yesterday There were a couple of stocks that didn't move move pretty nicely. First of all run was pretty awesome Run had that really big spike right at the gate where we're from 1880 all the way to $20 I had a couple of nasty shakes right there, but that was probably one of the best stocks Had a huge huge 140,000 iceberg order on that stock right there a huge order and we use the level four to see that and A lot of you guys were watching it when it had that all-time high and it held there So I just wanted to kind of bring that up even though, you know, it did really well the iceberg order was really really big micron Typing the wrong window micron also oops It's my time frame here Also did pretty well too out of the gate You could see that had a nice push going into it the open but then all of a sudden boom everything tanked and It's same thing with COTY Another one tanked that one. I mean, I don't know if it was on your shortlist, but that was pretty awesome It just came down like a ton of bricks great pick yesterday and then the the BR FS Was pretty steady nice little level one stock had a pretty decent afternoon trade now with all these news that came out yesterday listen, we all know about Why the market kind of moved a lot it was actually up pretty big and then backed off Regarding about the the talks in China with President Trump and stuff like that But but even that I'm telling you they just just gets to show you that There really is not a lot of people out there trading today a lot of people are on vacation and You know, they get ready you're between the Canada day here in North America and then have them for to July Falling on a Thursday I told you this week was not going to be like last week and guess what that is okay Because you want to know when to trade we're not to trade and this sometimes is opportunities You'll get something a little bit easier to trade so there are some stocks just got to be very very selective now How we're gonna trade tomorrow. Well, that's what I'm gonna tell you tomorrow So we'll have breaking news on that and I'll tell you a little bit how to do that So you make sure you guys come to work because guess what I'm gonna be here So I expect you guys to be here. You have to be here, you know Listen as good times as bad times and you know, you just got to see how to trade those markets Because there's always great opportunities out there not that you're gonna have, you know great trading You know a whole great list like we have but listen, we only need one to make a day's pay now regarding about what's moving this morning what we saw That was moving a M R and let's start off with that one right there I am already gapped up pretty nicely a lot of you remember the stock we traded it last year We're from $2 all the way to about 22. You have a nice little pop right there. She's breaking lower lows and The she doesn't have the greatest iceberg orders out there Now see too much on level 30 level four But we know the stock does move it did trade a million shares and pre-market ready. That is a lot. Okay EROS is the one that some of you guys been trading so far this morning EROS you could see that stock right there got destroyed and I don't know why I'm looking at a Thing like that. All right. So eros you could see that stock right there was eight dollars down to a buck fifty She just gapped up a little bit.  Look at all those orders 1.2 million shares Not I mean, it's funny when you look at level three verse on the AMR and verse this one the EROS He'll have a lot. You have a lot thousand shares and thousand shares There's what we need and that's gonna give a sense of a game plan The RBZ is the other one. We were trading in this morning. That one did pretty well Yeah, look right here. So that one came out of nowhere I think just popped right around 830 ran from 420 to 450 another stock that got Decimated $80 stock beginning of the year went all the way down to about three bucks We remember some listen this stock if you remember go back to your journals This stock's got a great great short squeeze. We saw the stock go from 10 to 40, you know That's about a you know back in April Lash, and then it did it again. It ran from like three to 2050 so we know the stock moves But the most important thing The most important thing is what we teach you in class how to keep a good journal Go back and now's the time to go teach yourself a lesson and say, okay If you were a student back here in April, how did I do with the RBZ? What happened? What can I remind myself not to do? So I so I could fix that problem and capitalize it because if this if this stock goes from 3 to 30 I don't want to lose that opportunity again Okay, so make sure you did your journals properly the way you taught in class and go check it out Because I tell you this all the time we always say this in class. You are going to trade this stock again Okay, maybe not tomorrow. Maybe not next week probably next year, but they always Somehow come out with some news and make big moves to go back and review that And that's about it guys is not a lot going on regarding about the markets That's what I found in pre-market so far, but we all know that when a market opens up There's always been some new ones just come out of the gate out of the blues You see these things come out of some foxholes or something like that like wait how that cut won't come from but um But the tip of the day I wanted everybody know remember Sometimes you feel like you're chasing a stock right just go out there buy one share buy one share Just get into the position remember if you don't trade and you get those butterflies out You'll never be aggressive. Listen. It's okay to chase a stock. Just do it one share. Don't do with a thousand All right, and then as you get used to it you got to get you got to get your mind in that Trading mode if you're not in that trading mode You're never gonna do any trades because you got a trade to make money right and remember you got to lose To learn losing is a good thing. You know why you lost you won't do that again. All right. Anything. I'm missing guys I did not call out fellow traders vibrators Wayne says the globes the GLBS is worth watching at 250. Yeah, you can see it right there It's got it's got some decent volume another stock that you guys should remember was another short squeeze that we traded it back In March this one from three to nine another one of our two three hundred percent winners, you know So that one's doing pretty well Action Ken says actions equals success. That's right And if you don't if you don't have the action, you know, I don't have many times you have to say it You guys got to hit the button. Don't be a deer in the headlights. Okay, you know Some people don't like hearing this but it's it's you know Sometimes it's kind of true when you do your journals, but they do say it takes a thousand trades before you start Before you start knowing how to trade sounds like a lot, right? So if you do it one share Doesn't cause you that's money and ticket charges Do it on a thousand shares you could survive it of course you're fortunate You got to go out there and you got to trade to learn Tiger's worth watching over six Grant says yeah, I can see that nice call right there Grant Definitely looks like something pretty interesting and you know, what's got great iceberg orders out there You could see there's a big 10,000 share buyers sitting there at 580 They're probably way too often wait off until then. All right guys. Listen, don't forget So we got going on today if you logged in late Today we have open house live trading with Fausto and talk about high-frequency trading So go out there tell your friends about it share tweet it, you know You know, it's always slow at 12 o'clock where times we take off so come and join us and You know, so that has some fun and then we move traders talk to tomorrow at 11 o'clock You she knows on Tuesday due to you know We had to move a couple of classes around because obviously Thursday markets closed and that so but remember tomorrow more close at 1 o'clock But it is open all day on Friday guys. Good luck today. See you back at 12 See you for the afternoon meeting and If I don't see it enjoy the 4th of July weekend. Good luck everyone. Happy trading


Here's a little bit. I wrestled a lot in Greco growing up throughout the country of Asia and high school. So we're going to get a little throw that I really like to kick. Not only in Greco, but also I've hit it a lot in college. We've focused on all school freestyle. Alright, so we're going to be working off this under over position. Now it's really important for my partner to work with me. This movement isn't going to work if I'm not getting the correct feel. First of all, I want to make sure my partner has his hips out. He's really steaming up into me. I'm never going to hit this move. I want to get his out a little bit from me in this position. What we're going to do is I'm going to pummel with him a little bit. It's very common in wrestling to see him fighting here, fighting here, fighting after a couple. He gets that feeling that, hey, we're pummeling. Now on this next one, I'm going to let him start to pummel. What I'm trying to do, I'll do it a little bit slower for you guys. I like to hit this from both sides, honestly. So I'll switch sides this time. We're pummeling. What we're doing is we're sitting our hands in here, fighting in, in the reverse side. Now after a couple of those, I'm acting like I'm fighting in. Right as he starts to fight in, his elbow goes over. Boom, fish in. Right here. Fish in right here, and then this on swinging over top. Basically, I don't have a big step on this, if the step at all. Are we right here?


The Ukrainian army brings the end of Russian T-90 tanks. Since the beginning of the Russian invasion, the Ukrainian military has destroyed 3,734 tanks of the Russian army. Alexander Kovalenko, a Ukrainian military political observer, noted that there were more than 100 T-90 tanks among them. In Ukraine, the destruction of 62 T-90 tanks was documented. According to general reporting, more than 100 T-90 tanks were destroyed in Ukraine. In Ukraine, one third of all T-90 tanks were destroyed, he said in Telegram. Kovalenko recalled that at the beginning of the full-scale invasion of Ukraine, the Russian Federation had about 300 T-90 tanks in the units and in storage. Those T-90M pro-Riv tanks that are now rolling off the assembly line are mostly modernized, removed from storage. At this rate, Russia will soon not have a T-90 at all, the expert summed up. As of May 9, 2023, according to the general staff of the Armed Forces of Ukraine, 3,734 Russian tanks, 7,258 armored vehicles, 308 aircraft, 294 helicopters, 307 air defense systems and hundreds of other enemy equipment were destroyed in Ukraine. In addition, military expert Alexander Kovalenko, based on Oryk's data, compared the losses of Russians in various wars. Thus in Ukraine, the invaders lost 1,937 tanks in Georgia, 3 in the First Chechen War, 192 and in the Second Chechen War, 23.


This is stock number 20T75A we are here at Summit Automotive in Fond du Lac, Wisconsin your new and used Ram and light duty truck headquarters today we are checking out this super clean 2016 Ram 1500 crew cab 5 foot 7 inch short box this truck has the 5.7 liter V8 Hemi motor it has been fully safety and inspected by our service shop has a fresh oil and filter change all the fluids have been checked and topped off and this truck is 100% ready to go maximum steel metallic is the color we shoot all of our videos in 1080p 60 frames per second so if you have HD capabilities on your computer tablet or smartphone device I highly recommend turning them on right now because it's definitely your best way to ensure the quality and condition of the vehicle before seeing it in person you want to check out all the photos on this truck in the upper right hand part of the screen is a link right to our website click that and check us out there comes with the 20 inch paint alloy rims with the chrome covers and it has Goodyear Wrangler trail runner AT 27560R 20 tires these tires have a lot of tread left I'd say probably about 70 to 80 percent of the tread left on those tires driver's side front fenders in excellent shape headlight lenses are nice and clear the front bumper is in nice condition I didn't see any major dents or dings on that it has the front bumper parking sensors factory fog lights chrome trimmed grille that's in really nice shape passenger side front fender I didn't see any dents or dings on that paint is very shiny and gloss like and a passenger side rim no scuffs or scrapes on there as you go down this side of the vehicle you can see just how clean the body is how reflective and mirror like that paint is we take these HD videos so if you are far away or even if you're close by and just cannot make the trip down but you're still interested in purchasing the vehicle you can see the vehicle hear the vehicle and have confidence in what you're looking at before you even get here so when you do get here there's absolutely no surprises that's why we offer the summit auto fast pass option in the upper right hand part of the screen a link right to our website where you can apply for financing get pre-approved see a payment quote even appraise a trade off from the comfort of your own home so when you get here all you got to do is drive the truck and love it and you'll be all set to go look how clean that frame and underbody is very very nice condition on this truck it's probably because it has the plastic wheel well liners keeps your frame and underbody looking good those back tires have just as much tread as the front tires and this back rim is in excellent shape as well no scuffs or scrapes passenger side box looks like it's in really great condition and as we come around to the back of the vehicle rear bumpers in really nice shape no denser dings and that does have the dual rear exhaust backup parking sensors full towing package which includes a receiver hitch four pin and seven pin wiring that tailgate is in excellent shape as well has a locking tailgate backup camera and it does come with an access soft tonneau cover I wouldn't say that the tonneau cover is in perfect condition but it's in pretty nice shape I didn't see any major rips or tears on it and it does come with a bed rug and that's in pretty nice shape as well tailgate shuts nice and solidly and as you go down this side of the truck just as clean as that passenger side box look like looks like it's in really nice shape and this back rim is in excellent condition as well down the rest of the side of the vehicle no denser dings on the doors looks really good has the heated power mirrors with the built-in directional signals inside the bighorn package gives you the great cloth interior there are no rips there are no tears on the seats they're in nice shape power driver's seat with lumbar we do have factory floor mats throughout auto headlamps audio controls on the back of the steering wheel power windows power locks power mirrors and these mirrors power fold in I was like showing both sides so you can see that both sides are working nicely which they are and as we hop inside the truck you can see that this one has 46,646 miles you get these seven inch lcd display gets the digital speedometer outside temp compass and range to empty and time you can change all those corners to do whatever you want leather wrap steering wheel is in excellent shape this is a heated steering wheel bluetooth and information center controls on the left cruise controls and gear selector on the right this one comes with the 8.43c radio so what's cool about this radio is it doesn't have nav but if you wanted to add navigation to this radio you could for $595 see your sales professional for more details AM FM and Sirius XM radio capabilities this is also where your backup camera shows up and you got your heated seats heated steering wheel buttons and you can do the backup camera without actually being in reverse here's your eight speed automatic transmission with the turn dial shifter push button four wheel drive including four wheel drive auto and low and you got your heated seats heated steering wheel buttons down here stability control toe hall and you can turn those front and rear parking sensors off now if you don't like doing your climate control up on the screen which you can do you do get dual climate control by the way you can do the down here so it's more tactile buttons if you got gloves on or just don't like using the radio these buttons work pretty good and you got a volume and two knob down here as well for the radio has the 115 volt 150 watt plug-in as well as a usb plug-in right there passenger side floor mat and seat are in excellent shape this one does have the 4020 40 split bunch seating in the front here so it is a six passenger and that headliner is in really nice shape didn't see any rips or tears on that map lights power sign rear window and you get your home link buttons for your garage door security systems and lane systems you also get the 911 and assist buttons in the rear view mirror those are features of the vehicle that you never have to pay a subscription for by the way it smells very clean inside this truck i don't think it's ever been smoked in the back seats are just as clean as the front seats no rips or tears back here it does have the latch child safety system for all your child car seat needs back seats are in nice shape does have that power sliding rear window you get that center council there these seats fold up and there is a load floor load floor goes down like so you can put that down nice and flat if you got pets you can put both sides down they got a nice flat place lay if you got muddy boots or tools can set them on here and you're not going to wreck your nice seats also if you're hunter you got a nice flat area for a shotgun so it's not going to be rolling around on the hump there storage underneath the seats as well and you get in-floor storage on each side two so with removable bins for easy clean so you can put ice and drinks in there it's like you got too many coolers wherever you go doors all look really good and it does come with child safety locks lower kick plates look great and we'll take a quick look under the hood i would personally like to thank you for checking out the video today and hopefully from this hd video you'll been able to tell just how clean this truck is all the way around inside now under the hood we have the legendary 5.7 liter v8 hemimotor enjabes very clean runs very smooth this truck has been fully safe eat and inspected by our service shop has a fresh oil and filter change all the fluids have been checked and topped off the truck has been gone through mechanically 100% and is 100% ready to go to see more pictures of this truck or one of other 450 new and used cars trucks suv's minivans wranglers half tons to quarter tons one tons you name it we got to go to our website www.summitauto.com full pictures and descriptions of every single vehicle from two locations all at summitauto.com and if you'd like to check out more hd videos you can go to youtube.com slash summit auto remember to like subscribe and share on this video and all the videos that you see there in fact in a second you will see link to subscribe to our youtube channel on your left a link to more ram 1500 truck videos like this one on your right if you have not been to our website on the bottom link to this vehicle on our website click those checks out and we really look forward to helping you with this super clean 2016 ram 1500 crew cab five foot seven inch short box big horn with the 5.7 liter hemi thanks again


Hey, this is Brett and this 2014 Ford Mustang GT Premium Convertible is stock number 14015Z. I am here at Summit Automotive in Fond du Lac, Wisconsin, your new and used sports car headquarters. This 2014 Ford Mustang GT Premium Convertible has the 5-liter Coyote V8 engine, but it's 420 horsepower. This one's paired up with the 6-speed manual transmission. This car has been fully safe to and inspected by our service shop. It has a fresh oil and filter change. All the fluids have been checked and topped off and it is 100% ready to go. I'm going to go all the way around in this video. Inside, start it up. Take a look under the hood. Take a look inside the trunk, just giving the most accurate representation that I can of the vehicle. Black clear coat is the color. I shoot all my videos in 4K. If you like the video, you can subscribe to the YouTube channel, click the bell notifications and you'll get updates on the videos I do each and every day, as well as having access to one of the largest catalogs of vehicle and specifically sports car walk-arounds on YouTube. This one comes with the 19-inch silver painted alloy wheels. Really nice condition on these wheels. Pirelli P0 Nero tires. These are 25545R19s. I would say that they have probably about 60-70% of the tread left in the front here. Very good amount of tread. You get some nice red caliper covers on there. Front fenders in really nice condition. Didn't see any major dents or dings on there. The front bumper is in fantastic condition. Didn't see any major dents or scuffs on there. Looks really good. This one does come with the HID headlamps, the LED running lights, the LED fog lamps. I'm going to turn all those on at the end of the video so you can see just how nice and bright they are. The hood's in pretty nice condition. I didn't see any major dents on there. Paint is very glossy. Passengers side front fender is in fantastic condition as well. And the passengers side front wheel, no major scuffs or scrapes on there. As you go down this side of this 2014 Ford Mustang GT Premium convertible, take note of how clean that body is, how reflective and mirror-like that paint is. Take these HD videos so if you're far away or even if you're close by, you just cannot make the trip down. But you're still interested in purchasing the vehicle. You can see the car, hear the car, and have confidence in what you're looking at before you even get here. So when you get here there's no surprises. You can make a smart and informed buying decision from wherever you're at or just make the decision to come take a look at the vehicle. If this video helps you do either of those, let your salesman know that you saw the video that it was helpful in that breadth sense. You're very clean down that side. Back wheel is in excellent shape as well. Four-wheel disc brakes, of course, on this car. Back tires have a really good amount of tread left on them as well. And the frame and underbody is in really nice condition for a 2014. Looks really good. Coming around to the back of the vehicle, you get the Roush exhaust. This thing sounds really good. I can't wait to start it up and show you just how nice it sounds. You get these sequential LED tail lamps. The back plastic here, this applique is in really nice condition. Sometimes these can delaminate. It looks really good. You get the GT logo there. Declared spoiler. This one does have a backup camera, which is pretty sweet, which my GT500 had. Inside the trunk is very nice and clean. And this one comes with a spare tire.  And that shuts nice and solidly. Coming around to the driver's side, just as clean as that passenger side. No major dense dings on that rear quarter. For full disclosure, this back wheel is in fantastic condition. The wheel wells all look really good. Didn't see any corrosion on them. Does have the capitalist fuel fill, which is a really nice feature. Never get gas on your hands again. And down the rest of the side of the car, the door looks really good. Didn't see any dents or dings on there. Has the power mirrors with blind spot mirrors in them.  Very, very good looking interior. One of my favorite interiors for the Mustangs. This does have a heated front seat on the driver's side. Comes with some nice factory Mustang formats. Auto headlamps, these tilt steering wheel. You get the leather bolsters on the doors. Power windows, locks and mirrors.  They look really good. Smells very clean inside this car. I don't think it's ever been smoked in. And you get latch child safety system back there. If you want to try and put a car seat back there, that is up to you. We'll hop inside, check out the miles, the radio and everything this car has to offer. And then we'll put the top down and start it up and take a look under the hood. And see this one has 22,496 miles on it. Instrument cluster is very nice and clean. You get the leather wrapped steering wheel. No rips or tears on there. Bluetooth and audio controls on the right. Cruise controls and information center controls on the left. And you do get that brick red leather on there as well. Of course, the Mustang logo in the center there. This one comes with AM, FM and Sirius XM radio capabilities. It does have a CD player down here. Your climate controls sink for your Bluetooth cell phone. Your nice six speed manual transmission with the silver ball shifter. You get ambient lighting in here, which is pretty sweet. And the passenger side format and seat are in excellent condition as well. The inside of the soft top looks really good. And once again, smells very clean inside this car. You do get home link buttons for your garage door security systems and lighting systems, map lights, soft top control and auto dimming mirror. To get these soft tops down, you just have two latches, one right there and then one on the driver's side. And then you just press this button and it'll go all by itself. And then it'll stop right where it needs to. Once it's done, it'll just stop. You can see that's working nicely. See it just stops. All right, let's start it up. Listen to that exhaust. Take a look under the hood and check out all those HID lights in the front. It starts right up. No check engine lights or anything like that. That Roush exhaust sounds so good on this 5 liter. It's really amazing. And the car looks really good with the top down. Looks really good with the top up. Really a nice ride. I would personally like to thank you for checking out the video today. And hopefully from this HD video, you've been able to verify the quality condition options and of course, cleanliness of this car all the way around inside. Now you've got all those LED headlights or HID headlamps, LED fog lamps and LED running lights and under the hood. Like I said, we have the 5 liter V8 Coyote engine. 420 horsepower engine base. Very clean, runs very smooth. You get the strut tower brace on there as well. Once again, this car has been fully safety and inspected by our service shop has a fresh oil and filter change. All the fluids have been checked and topped off. And this car is 100% ready to go. There's the emission sticker. And I would highly recommend this car from a quality and condition standpoint. Considering the age of miles on it, this thing's in great condition. And I think whoever's going to get it's going to really, really like it and enjoy it for all the reasons that you'd enjoy a convertible musting. And to see more pictures of this car or one of our other 550 new and used cars, trucks, SUVs, minivans, Wranglers, half tons, recorded tons, one tons, Mustangs, Camaros, Challenges, Chargers, Corvettes, 5 liters, GT Premiums, GT 500s. You name it, we've got to go to the website right there, summitauto.com, full pictures and descriptions of every single vehicle all at summitauto.com. And if you'd like to check out more HD videos, you can go to youtube.com slash summitauto. Click the bell notifications, get updates on the videos I do each and every day as well as having access to one of the largest catalogs of vehicle and sports car walk-arounds on YouTube. In fact, in a second you will see a link to subscribe to my YouTube channel on the upper left. A link to all the Mustang videos I've done in the upper right. A link to this vehicle on our website on the lower left. And a link to one of our latest YouTube videos on the lower right. Click those checks out. We're super excited to help you with this Ultra Clean 2014 Ford Mustang GT Premium convertible in black clear coat. Thanks again for checking out the video. Remember to like, subscribe and share on the YouTube channel. I really appreciate it. Thanks again.