Lukas Nussbaum, the current Debian project leader will deliver the bits from the Debian project leader now. Enjoy. That is your... Is that... Yeah, okay. Thank you. Okay. So, to start, I wanted to start from the sides of Debian that people encounter, and usually when people meet Debian for the first time, it's about the technical project. So we are a project building a very successful distribution with a real impact of the world. That's really great because when you can go basically anywhere on earth and meet people using Debian or using Debian derivatives, we know about Debian, and if you try to wear Debian t-shirts every day and you will see that many people recognize Debian, that's really cool. I guess. Yeah, maybe you're in space, too, that's true. But it's harder to meet people in space. But then there's also the philosophical and political project about promoting and defending free software. And what's really cool about Debian is that we do that, but we really check about technical parts. It works like a feedback cycle between the technical part and the philosophical part.   And Debian is really, well, building this community is a key outcome of Debian. And I really think that this place is a fantastic place to have a successful Debian that will help build the Debian community. So I try to find a symbol better than a group photo to describe that international community of contributors. And I came up with power plugs because I think that really shows the diversity of Debian. So the question I get asked quite often as a project leader is, how is Debian doing? And I think that most of the project is working fine. I decided to single out one team because usually it's a team that gets a lot of blame. It's an FTP master's team. And actually, probably most of you know that new processing had some small issues during the last few weeks. But if you look at the data, at the art data, there are seven members of FTP masters that were doing new processing since the beginning of July. I don't know if we probably, that might be one of the most active team in terms of active Debian developers. Seven looks like huge, probably the Debian team might have more, but still. And since the beginning of August, they processed 284 packages, like 11 days, versus only 73 uploads in the queue, new uploads in the queue. So we released with the, finally. It's quite obvious that this cycle was a bit painful compared to the previous cycles. If you look at the length of the cycle, we are a bit above our recent previous cycles. And the freeze was quite long. So we started the development of Jesse with the usual bump of RC bugs. And Jesse will be a quite challenging cycle. We really need to work on returning to shorter freeze because long freeze are really not healthy for the project. And we have some difficult decisions to take. First one about init systems. And also I think that during this cycle, well, at the beginning of this cycle, there are many architectures where the status is not completely clean. Probably we need to have quite difficult discussions about some architectures. So I think that we should be really careful in making these decisions the Debian way, that is make sure that we take the best technical decisions. But once the decision will be taken, I think we really need to stand behind that decision as a project. And we should not let ourselves be divided by the decision. So Debian is almost 20 years old, but actually that's an age where most people stop growing. But Debian is still changing quite a lot. If you went to sleep in 2005 and wake up now, probably, the Debian project will look very different. I don't know if you know that movie about someone getting into coma and then waking up after the Berlin Wall was broken down, but it would be fun to have someone waking up now after eight years. So first, team maintenance, most, well, a majority of packages in Debian are maintained by teams now. Since about 2012, so the red line is packages maintained by teams, the green line is package not maintained, and the others are one, two, three, etc. So team maintenance is really the new way to maintain stuff in Debian, but then we have a problem. We have teams that get MIA. We used to have developers that go MIA. Now we have teams that go MIA. And actually, we are not quite good at detecting that. When I did the survey about new contributors, one of them had a nice story, well, not so nice actually, they created a team with only one DD to maintain a set of packages. And then the DD went MIA. And the team was still active, but with no one to talk to to upload the packages. So it's kind of a lonely island in the middle of Debian. And we are really stuck at detecting that currently. We need to work on that. Something else is the use of VCSEs that's related to teams actually to maintain packages in Debian. So the green line there is Git. The red line there is No VCSEs. And the blue line is SVN. So Git is clearly taking over. All of those solutions, well, DAX is increasing, I'm not sure why, well, probably some teams that ask a team maybe, but Git is really the new standard to maintain packages. Which way, well, we have several ways to maintain packages using Git. Each team tends to develop its own workflow with its own procedures. And that really sucks, because as a project we really need to standardize on a single way to maintain packages and not have the project divided into smaller projects with each its own way to maintain packages. So there's really some work to do in that area about it would be fantastic if some teams use Debian Conf to come together and decide on a standard way to maintain Git packages using Git. And then there's also packaging helpers. So the blue line is DH, the red line is 3DH developer, and the green line is CDBS. Because that graph is always quite funny because DH was originally advertised as a CDBS killer and actually it's not really killing CDBS, more like killing a developer. But still, that raises a question. What do we do about our former way to maintain packages? We are quite slow in general at deprecating the previous standard way to maintain packages. Usually DH knows the new standard, but packages are only slowly becoming migrating to DH. Oh by the way, if you were wondering, those kind of staircase, steps there and there, those are the freezes. So you can see that things slow, slow down during freezes and then start up again, which is expected. So Debian is almost 20 years old, so first I thought that a clarification was needed as computer geeks, it's in decimal. And when you see that, you can ask yourself another question, which is what should we do before reaching 20 in X. Actually I'm turning 20 in X this year, so that's something I gave some thought. Or maybe, oops, oh, okay. That's the problem with making less than changes to presentations, it's okay. Or maybe what should we do before, well, during the next few years, what are the big challenges? So first, if you look at the global picture around Debian, we have upstream projects, we have users, and Debian is in the middle. We get software from upstream projects and we turn them into packages that distribute to users. Second, we get feedback and bugs and sometimes patches from users. And we forward them to upstream projects, or we sometimes forward them to upstream projects possibly with adding patches. But that's not the only thing, we also have Debian derivatives for which we have the same schema. And some of them also have their own derivatives. And so that's really the picture of how it should be, with Debian really at the center of the free software ecosystem. But some of those streams don't work so well in some cases. So one can ask whether we are always a good downstream for upstream and a good upstream for our derivatives. And I think there's room for improvement. In some cases, the relationship we have with downstreams or upstreams is really good. But in some cases, we can do better in that area and really reinforce the position of Debian in the center of the ecosystem. So there are simple things you can do. First, contact your upstreams. When you start maintaining something, it's really important that you talk to your upstream if you have an upstream. So talk to them, ask them to review your plans. If you plan to package a new upstream version, it's good to send them an email beforehand so that they can comment on whether you should do that or just wait for the next release or something like that. Provide them with feedback and bug reports. We have something that's not very well known. It's patchschwacker.debian.org that extract patches from Debian packages so that upstream can easily integrate them. Ask them to subscribe to the packages on the BTS. So I know of a few packages, for example, coreutils, where the upstream maintainers are actually replying to bugs in the Debian bug tracking system. And that's just great because users report bugs in Debian, the upstream maintainer comments on the bug directly in the BTS. It's the perfect way to work. Not all upstreams want to work that way, but when they get to work that way, it's just fantastic. Look at your downstreams, our downstreams are bugs and patches. And there's a panel tomorrow at Debian about derivatives, it would be a good idea. We had a large audience attending. But more generally, I think that we need to keep in mind that Debian is also about improving free software as a whole and we should not work, well, we should work on improving Debian, but we should really keep the global picture of improving free software and improving the world generally. And for that, we need to be a good player and collaborate with all entities. So then the ecosystem around us is changing. Everybody is talking about cloud, which is a nice buzzword, but not only a buzzword. And it brings virtualization and elasticity of infrastructure and software. And our model where you install a system once and then you upgrade it for 10 years using several Debian release, it becomes less relevant with that ecosystem because you just start up a new virtual machine, you don't need to upgrade Debian that often anymore. And that raises many challenges for Debian. First, the cloud, as pointed by many people, is taking freedom away from users. So we need to work towards preserving that freedom and we have several ways to do that. For example, we can package software so that users can deploy their own private cloud. So we are doing that. There are some improvements there. These are really, really hard software stacks, usually split in many different packages with custom configuration of services. And well, more manpower on that part would be really nice. Then we also should work on packaging PaaStacks and SaaS stacks, standardizing platform, development platform, deployment platform. And having the standard platform in Debian is really important. So for SaaS, actually we run into the usual problem of web applications packaging. That's not something we are particularly strong at. And it's increasingly important. But then on a more technical level, the world is using Perpetual Chef everywhere or is trying to use Perpetual Chef everywhere. And one can wonder what's the role of Debian packages, package managers, and of configuration using DebConf in that world. And we might need to evaluate what we do and maybe adapt a bit so that we can better integrate with those tools. And for public clouds, that's also the question of official Debian images. What does it mean to provide Debian on a public cloud such as Google's or Amazon's clouds? So if you look at this year's DebConf schedule, there are eight cloud-related sessions at DebConf. And I hope that we can address or work on all those topics. So probably something that will raise some discussions. I think we should look into meeting all our users' needs. So we have Debian testing, which is the first and the best rolling distribution. And I think we should really acknowledge that and advertise testing as such, as the rolling distributions. So testing is already widely used. During the last few days, I made some stats from Debian Mirror. And actually, if you look at the HTTP logs from that mirror, you see that... So what I did was take the log, grab for people fetching the packages file, and then look at which IP fetches which packages file. And 42% of the users of that mirror fetched the squeeze packages file, 60% the withy one, 12% the testing one, and 11% the unstable one. So it's not, well, clearly there are more users, well, there are two possibilities. Either we have very few users and many developers, or we have quite a lot of users using testing and or unstable. If you look at the popularity contest submitter, so this doesn't add up to 100 because one specific IP can fetch several packages file. If you look at popularity contest submitters, so looking at the version of the popularity contest package that is used to submit the results, we have about 10% of people using testing or unstable. So and actually that share, so that's the blue share there. It varies quite a lot during cycles and at the end of the withy cycle, just before the release, it was a lot more people using testing or unstable. So that's not something new. We have people, lots of people using testing and unstable. But there are also many other good reasons to go into the direction of the rolling release. First it makes us provide more recent software to users. So for the free software community in general, it means that we build a shorter feedback loop between upstream projects and the user. User can use recent software, report bug on recent software because usually when you are an upstream developer, you don't really care about bugs in software you developed two years ago. Probably the bug was found in the meantime. The more people we have using recent software, the more bugs are fixed and the more in general free software is improved. It gets us more testers of the next table release. So usually what happens, well, it's quite useful from a release management point of view to detect bugs earlier. It gives us more time to fix bugs. And actually, if you look at Christian stats about bug reporting rate, the Ubuntu bug reporting rate is much higher than Debian which is a bit roaring. Of course, if you are, I don't know, ice with a maintainer, you don't really care about receiving more bugs. Probably you have enough and it's pretty well covered. But if you maintain quite obscure Ruby library, it could help to have two times more users because probably if you have only 100 users worldwide, not all of them will report bugs. It could be helpful to increase that number of users. Something else that it makes us attract different users. So if you look at people using Arc Linux, for example, most of them are quite young, enthusiastic Linux users. And attracting more of these kind of users to Debian means that in the end, some of them will turn into Debian contributors. And having the image of the old and boring distribution, which is not completely true, but some of it doesn't really help us recruit new people. It's better to be, well, we can stay with the old and boring aspect, but it's better to have the other side of being young and really active. And also, I think that actually it's low-hanging food because there's no need to change anything. It's mainly about PR, about communication, communicating to the public that testing is usable as a rolling distribution and, well, just use it and stuff like that. So I think everything is there, just need to advertise it. Of course, the big challenge with that is to coexist with the stable release and to not arm the stable release. We really need to work on, well, we should be really careful about not decreasing the quality and the workforce that goes into our stable release. So about manpower, the challenge for the next few years as usual is to, as it was for the next, for the past 20 years probably, is to recruit new contributors. So everybody complains about manpower, this is a regular complaint and I think it's a justified complaint. There are many areas in Debian where we could use a lot more manpower. As a DPL, I often have to poke people about why it's something not working as expected. And, well, of course, it's easy to blame the lack of manpower but sometimes when you don't have, well, sometimes just boys don't do that and you can't do anything besides that. So I made a survey of new contributors, you might have read the report on the Debian project last week. What it shows is that it's really hard to contribute to Debian. As a project, we tend to build very efficient processes and tools so we like to be, to optimize stuff for ourselves but as a result, those processes and tools are often quite complex and difficult to learn for newcomers. And, well, that's a trade-off, well, we tend to be selfish about our processes and tools and, well, it's hard to change but keeping that in mind when designing processes and tools would be, still, already be a good thing. We have very high quality requirements. The attention to detail we put into our packages, it's just incredible. Of course, that's something that contributes greatly to the success of Debian but, still, for new contributors, it might be a bit surprising. We have a misalignment between our contributors' goals and our goals. What we want, really, is people who just join our teams and fix all the teams' bugs and upgrade our packages to the new version. That would be fantastic. Well, I miss people come with an idea of what they want to do inside Debian and, usually, it's package this thing I use that, well, maybe nobody else uses but that's something that is important to the new contributor. And, well, we need to find the middle ground between what the new contributor wants and what we want. And, also, one thing that the survey showed that it's very hard to get sponsored outside of the team. So, if you want to package something and there's a team where it fits, it's fine. You will probably find someone willing to sponsor your software. If it doesn't fit in a team and you don't know, you don't have a friend or colleague with a Debian developer and we will do the sponsoring for you, then it's really, really hard. So, you can all help change that. I think it's a really collective responsibility to change that. First, subscribe to Debian Mentors and do some sponsoring on Debian Mentors. If all of us do one sponsor on Debian Mentors per month, I think the problem is solved, basically. Problem is, if you look at the Debian Mentors archives, last month, I think there was like four or five different DDs doing reviews and sponsoring. So we cannot point to something where only four or five different DDs are active. And something that is, well, deep in the culture of Debian is that you cannot make mistakes. And you're not allowed to make mistakes. And I think that for sponsoring, it's really hard because you are asked to review something and you cannot read all the F-stream code or you cannot audit all the F-stream code looking for possible bugs. At some point, you take the risk to make the upload. And sometimes it's true that mistakes will happen. And I think we need to be better at accepting mistakes. It's okay to not know everything. It's okay to not be perfect right from the start. But it's better to be vocal about things you don't know and things where you are unsure than to just hide it under the carpet and hope that nobody will notice. And actually, even reviewing packages is something quite hard because, well, if you miss something, everybody will see it. But I think that's okay. We should really increase the culture of this being okay. One of the, someone mentioned that one of the people doing reviews on Debian mentors, there's a lot of reviews but never sponsors. So I'm not sure if it's because they feel that they are going to make a mistake by uploading something that, by missing something in the reviews. But that's really sad. I mean, we need to, it's okay if you make mistakes from time to time. It's software, you can probably revert it somehow. It's really hard to break Debian badly by sponsoring something. So there's some work to do on infrastructure around sponsoring. Mentors at Debian.net got rewritten two years ago, I think. Well, the current version got the work started two years ago using a summer of code project, I think. And it really helps, but there's more to do. For example, in many cases, the review is just, oh, you forgot that LinkedIn error. If we had automated LinkedIn checks of packages uploaded to mentors, probably the user, the prospective contributor will notice and there's, well, this limits the need for reviews. So I think that, well, Nicolas Dandrimon mentioned that work is underway there, I think it's Paul Tagliamonti who's working on that. So something else is related to the misalignment between contributors' goals and our goals. We need to be better at advertising tasks that are suitable for new contributors. So if we don't want new contributors to package, well, another image viewer, we need to provide them with ideas of things they could do. So we have WNPP Alert. Who in the room is running WNPP Alert on a regular basis? One person, congratulations. So we need a way to make it easier to discover opportunities of contributions. There are lots of opportunities for contributions, actually. If you run WNPP Alert, you probably find two or three packages that you rely on that are often, and if you find someone to adopt it, I mean, it solves your problem for those packages. We need to design better and simpler processes and tools and document them. But for example, everything related to using IOS, using Git, using SVN to maintain packages, this is quite poorly documented currently. So something that's really, really, as was mentioned, that's something really useful is everything related to peer mentoring and internship projects. New contributors really liked human contact of having someone to ask questions to. That's something that I don't know exactly how we can improve that yet, but that's something, well, Andrea still has some ideas, there's a session about that, about peer mentoring. But yeah, we need to work on that. But well, in general, basically what we need to do is help Debian become a more welcoming project where people can start contributing more easily, because currently it's really, really hard. So if you look at the schedule, there are seven events related to that. So the good news is that people care about this. We just need to make progress on that. And then before I conclude my talk, I want to talk a bit about Debian governance. So I just learned a new job. My vision of the new job is that many DPL tasks are quite short tasks, where if you do them with low latency, as soon as you receive it, it's done, it's much better. So for example, everything related to money handling, email redirection to the right people, poking people about something, everything related to legal, there are some constraints about how long you take to answer. And all those tasks are quite hard to delegate or to share, because there's a hard coordination override. If you want to share them with a team, it doesn't really work, because you will spend a lot of time coordinating with the rest of the team and it doesn't really make sense, so you can do it yourself. But there are also lots of tasks that can be delegated either totally or partially. Even writing a delegation, for example, that's something that takes some time, because you need to contact the team, figure out who they would like to see added to the team. Then you wait two weeks because nobody noticed your mail and pipping them again. That's quite time consuming. And actually, there's only the final act of sending the delegation email that can only be done by the DPL currently. Everything else can be prepared by someone else. And that kind of thing would be really useful. So, Zach started the DPL Helpers Initiative in order to try to distribute those tasks to a team and to teach more people what DPL tasks are about. So, my view for that is that it could be a kind of government for the Debian project. It is you have someone that is mainly responsible in doing that kind of short tasks, but then you have a group of people each with their own area of interest doing specific things. For example, we could have someone specializing in all legal stuff, in all new contributors related stuff. And these are areas that are quite easy to define and quite easy to delegate. We delegate in the informal sense of the way. This doesn't really need to be something official for most of the tasks. So, the problem with DPL Helpers is that it's not very active. We had only two participants at the last meeting. So, I feel a bit trapped as a DPL because I was hoping to rely on this to share the load. Actually, there's not so many people willing to share the load with me. But I wonder whether this could be the basis for a more sustainable governance model for Debian. Some things that could work and that would allow someone not from French academia or not self-employed to be the DPL. Because we're running out of people from French academia. So, there's a both about that. We might mention things going on currently, active tasks. But I also would like to spend a lot of time discussing this and how we can move forward and make it possible to move away from French academia. Okay, so that's the end of my talk. So, thank you for coming to Debian. Enjoy Debian. I hope it will be a very successful Debian. I'm quite sure it will be. Please use Debian to come and talk to me in person. So, that's my leader email which is archived and my arsenic name if you want to ping me and then we can meet somewhere. So, that's a kind of reminder of what I talked about in my talk so that you don't need to ask questions about only the last points or only about rolling. Thank you. About the rolling distribution thing, the testing and rolling distribution, I see a potential problem that has already been discussed and I already raised it in IRCs. When the freeze comes, would it be, this rolling distribution, would it be freeze? I mean, would it be intermittently rolling? Would it be handled differently or there might be two overlapping testing distributions at the time? How might that be handled? Well, I think that with that freeze duration, it's probably a big problem. Well, with that freeze duration, I think that we can live with everything being frozen for three months. Almost four months. So, I think that everybody wants shorter freeze. That would be useful for rolling distribution. So, let's just aim for shorter freeze and let's not try to do something more complex that might hurt stable releases. At least for now, maybe in five years from now, we'll figure out something that makes everybody happy. But what we do currently, I think, is fine. I don't think three months is an acceptable freeze interval. I really don't. I mean, we've had this conversation at the last several web comps, and I think a really good target duration for a freeze is two or three weeks. If we can't run a process that allows us to return unstable to being unstable in much less than a month, then I think it really negatively impacts the ability of lots of things in the project to keep rolling. Those stair steps that show up in many of our plots are just, you know, very frustrating. Yeah, but it also depends on what you call freeze, actually. Well, our definition of freeze, if we change the definition of freeze, we can have shorter freeze. Short of total freeze, for example. But I mean, there are things to explore in that area, like making sure that key packages don't get upgraded to new upstream versions just before the freeze. Yes, yes. Obviously, this is all part of what it takes to make something like that happen. I'm certainly not advocating a return to the very, very old process of let's just grab a snapshot of unstable on a particular day and call it a release. But there has to be something in between because when we end up in a situation where for many, many months we're not changing, you know, tool chains and core libraries and so forth, it's very, very easy for people to lose focus, you know, for their attention to move elsewhere. And then I think it's very hard for us to get it back. I clearly remember the talk of Anthony Towns in 2001. It's his first depth prompt when he introduced pool system where testing was introduced. And somebody else and me raised immediately their hand. What will happen with packages who are in testing and have a release critical bug? Will they removed again? And the decision was no. But I think there is some tendency now to remove these packages, at least leave packages, which have released critical bugs. And I think this is quite a good thing. Yeah. I think that we should go further in that direction. That is, well, we tend to treat all packages as equal, which is nice because our users rely on all of our packages. But some of them are still more important than others. And if we had a way to easily detect which are the bugs that really need to be fixed before the release and which are the ones that, well, we could just remove the package if it doesn't work. Okay, some users will suffer, of course, but it doesn't block the release. It would be a good way. But maybe we should just go further than removing packages during the freeze, but also remove packages now. I mean, if something is clearly unsuitable for the next release, we could just remove it from testing now. And if it gets fixed, it can get back. We have at least, well, almost two years to get back in testing. So get it back in shape. But, well, almost, well, we have very few release team members present at the conf, which is a bit difficult to discuss that. And that's the main responsibility to decide that. Of course, I need to talk with the project, but it's very hard to decide about that. So, Luca, you make two proposals. One is to make testing more a rolling release, and the other is to remove more things from it. How do you reconcile those two? I'm quite sure we can find technical solutions to that. And there are already technical solutions such that people just install packages from unstable from time to time. And for the users that we are targeting anyway, it's not really a problem if from time to time they need to take specific. Actually, if the package is not in testing and you have unstable in your source.list, it just works. But I don't think our main problem are leaf packages are there. I mean, you can always say, like, if there's a bug in a library, then let's remove it. So if there's a bug in LibRuby, let's remove Ruby and all its packages. I mean, leaf packages are not our problem. To remove leaf packages is easy. And we do that. Question is what if there's a bug in Ice Weasel? Yeah, but I think bugs in Ruby, but maybe I'm a bit biased about that. But Antonio can eat you if it's just next to you. But I think bugs in Ruby are probably the kind of bugs that should be fixed. Because, well, we need to draw the line somewhere, of course. But Ruby is probably on the let's fix it side of the line. I'm not sure that, I don't know. Well, some obscure Ruby library, like Ruby FitPaster, I'm the upstream for that. Nobody cares if it's getting removed. Well, some people will care. So I'd like to propose a radical answer to that question, which is that we should be prepared to revert something like Ruby to the previous upstream version if it fixes release critical regressions. And obviously that should be done with some care, but it might need to be done as an NMU. So we need to develop some collective understanding of when that might be appropriate and how to manage the fallout. But if we're able to do that, then we'll be in a much better position to fix bugs that are somehow intractable just by undoing the problematic upload effectively. But I think this is already happening kind of during the free. Sometimes it happens that we just revert something to the previous version because it's a new version to these problems. Often it's because the maintainer decided to update and it was not really a good idea, but we already have that possibility and use it from time to time. I'm not sure it really helps fixing, it would help fix that many additional bugs to develop that better. One thing that is related is the kind of having a feature branch for packages and having a way to revert specific changes. Currently we only have one development branch. We could have a feature branch where every package, every new version of a package leaves or sets of packages leave and have them merge into unstable or testing something like that. That's a lot of technical development. Okay, I think time is over. If you want to discuss this further, you have to use the hallway track. Thank you.


Celebrate good times, come on. Celebrate good times, come on. There's nothing. Jalsa. That means celebration. What does it mean?  I did not know where that was going. Is that what it translates to? Yeah, celebration. Yeah, that's right. Yeah. Jalsa? Yeah, that's, yeah. Why? Remember it, the title comes up. As a certain, no spoilers yet, but remember it, yeah. And it comes up at a particular time. Yeah, we'll talk about it. Oh, yeah. Interesting. Oh, yeah. Anyways. You saw the title, you know what we're doing. Yeah. We're doing a movie review. Subscribe, hit it, choose, follow Twitter and Instagram. But we're doing a movie review, everybody. And it's of the new film that just came out on Amazon Jalsa. 22 film, directed. Suresh Trevini. Suresh Trevini, written by him as well. As well. And then some other folks contributed to dialogue and story. It looks like Prajwal Chandra Jashkar. Forgive mispronunciation, please. Abbas Dalal Hussein Dalal. And then starring Vicky. Sorry. Sorry. He just saw the first movie. Yeah, sorry. I assumed it was Vidya, but it wasn't. Vidya and Shafali Shah are the two main leads in this, as well as the other sporting cast. But those are the two that we know. They're not our dofus, I wish they were. Not yet. But anyways, it still be, since it just came out, it's on Amazon. We're gonna do a little non-spoiler review and then we'll get into spoils just because, you know, if you haven't seen it yet, I wanna give you the option to go watch it. But it's on Amazon, it's about two hours. So if you don't wanna hear anything, you can just go watch that, come back. If not, we're gonna do a little non-spoiler and then we'll get into spoils. Rick, your initial thoughts, please. Well, this is our 21st of the year, our 142nd Hindi and our 228th all-time. A very entertaining, well-crafted, consistently captivating story about how good and innocent people are routinely crushed by the powerful and how those in power can easily cover up their crushings at the expense of more innocent people being crushed. There's a moment we'll refer to in the spoiler section. Yet, even in the midst of horrific realities, good people can still choose to do the right thing and still be good people. It, for me, lived up to the trailer excitement I had. Yeah, yeah. I enjoyed it as well. It's not a perfect film, but it's definitely an engaging film that, if you watched a trailer and you were engaged in the trailer, it's basically the film in terms of- It does a very solid job of letting you know what you're getting into. Yeah, and it keeps you entertained. You're gonna get two great performances from Shafali Shah and Vidya, who, shouldn't surprise you, kind of knew what's gonna happen already. And so I think it was a really, they did a really good, and it's not like a new story either, in terms of somebody does something. That aspect agreed. That aspect. That aspect. But there is, in the spoiler section, we're gonna get into, and this doesn't ruin anything. When you watch this, you can watch it and walk away being entertained and see the main story and not realize that there is a very subversive undercurrent happening at the same time that's quite intelligent and very impressive to me. Yeah, so overall, no one spoilers, I think the acting is great. I think the writing did a really good job at keeping you engaged. In the middle, I think, it didn't really falter, but I think they probably could have cut it up a little bit and made it even more tighter to get to the point a little faster. But I liked the writing. I thought the dialogue was good. I thought some of the twists and turns and all the underlined messaging was really, really nice. It was really good. We'll get into the spoilers, yeah. And Casting Bay, a couple of casting choices that I absolutely love. Is that how you cast it? Yeah, Casting Bay cast it. And I saw it in the credits.  First is to the man, Shikrant Yadav, that we saw in Kila, who plays More, the police officer. Oh, yes. Yep. Also, Kashish Rizwan, who plays Alia, was, I mean, we'll get into this in the spoilers, but I thought what she got with her screen time and she's, she's just getting started. You know, the first? Yep, just getting started, did a, I thought she did a great job. And then, the really cool thing is, there is a primary character in this that you'll see. I don't remember if he was in the trailer or not, but Vidya's son in this, his name is... Aiyua, Aiyua. Yeah, he plays Surya Kasibatlan, forgive me if I mispronounced your name, but he plays a character in this who's a boy with cerebral palsy. Yeah. And the actor does have cerebral palsy, so beautiful addition of inclusive casting of a character who, it plays a part in the story, but that's not the primary thing. You didn't have to, this could have been written without that. And I love that they just said, I don't know if they did this, but it seems like they just said, this little guy can act, let's put him in it, and the character's gonna have cerebral palsy. I don't think it was, it just happens to happen, which I really love. It's not really integral to the story. Does it have to be there? He was just a normal son who happened to have cerebral palsy. Sure. I thought it was a really good casting job of him as well. I think it's funny. The way I end to be sometimes, obviously, I know, second build. Second, and then all the way down. All the way down, he's so falling top, like, yeah. Exactly. I end to be as hilarious. But anyways, I think it's definitely a film that is worth your time in terms of, if you're like, I wanna watch an entertaining kind of different thriller that might have like a similar storyline that you've seen before, but it's gonna keep you engaged the entire time with some great performances from leads, and a intriguing ending that I think some people might like and other people might not. Yeah. And some good editing choices with the direction and leave something up for conversation as well. Absolutely. So, yeah. Should we spoil? Yeah, yeah, let's go into spoilers. Yeah, let's go into spoilers. I don't watch it, go watch it, come back, and they're just gonna get into spoilers. Yeah. So, spoiling time. Yeah. You spoiled a little. Okay. So, yeah, let's get into it. I thought, let's talk about the two leads that we normally start off with. And if you don't know why we do that, we're both actors. That's our favorite part. That's our favorite part of that. Storytelling is watching the actors act, and wanting to act with the actors in it. That's usually why we start with acting. But Shafali Shah just continues to show me why she's one of my favorite actors, one of the strongest actors, I think, in India. Agreed. In general, she has something behind her eyes. And I think that's, it's something that you can't teach. Nope. Obviously she has a talent there, and I'm sure, I don't know if she's done training as well, I'm sure she has. But there's a certain quality about certain actors. That quality of something's going on behind, without them saying anything. Yes. And she has it. Absolutely does. And like easily. And her character was so complex, because once again, we're in spoilers, like you don't know what, because at normal, the whole time you're like, oh, this is grieving mother. Right. It was from a different cast of the person she's working for. Yes. Very submissive most of the time. She has a great job at that relationship. Yep. But you could tell she's like, she has this fierceness behind her.  Yeah. She really. I literally. Is she really gonna do this? I literally, because I didn't see that coming.   Yeah. I thought, is she really gonna do this? Yeah, and it was, it's really good in the writing because when, it's hard to say, you understand why she like, if she would have done that, it would have gone through. You'd like, you wouldn't understand it because obviously you should never do that to a child, then obviously you say it.  You want to teach her a lesson. Bob, I'm gonna leave. As revenge.  Which was beautiful. I thought that was great writing and editing that that was done in the midst of her actually saying her testimony and what she did as she's doing it. Yeah. And so I really enjoyed that part. But yeah, her, and then I guess we'll just, well, I got one thing about, I'll let you know. If you're an actor and you're learning about acting, especially, pay really close attention. If you see this, I hope you paid really close attention to the fact that this role that Shafali played, both actresses, these roles required extremely talented and experienced actors to portray these roles because these kinds of roles for lesser trained and lesser available actors would be really easy to indicate and show grief and try to be what you think they should be in the moment rather than just be. And there's a stillness level and this is the pinnacle of stillness. The two actors who are the pinnacle of stillness, and obviously Daniel Lewis is in that category too, but even more so we talk about Irfan all the time. And Shafali has that quality of being able to be on screen doing absolutely nothing but thinking and you're mesmerized. And you know what she's thinking, or you don't know what she's thinking. Yeah, and you care.  She's a great actor or somebody you can just sit in a chair and put a camera on them for an hour and you don't wanna stop watching them think. And she's a great listener. When she was talking to Vidya in that scene in the kitchen when she accuses her of having, right? The jar drop, she says, you left the stove on. The shock and the hurt of why are you attacking me? She doesn't understand and she was just trying to, and she obviously knew her dynamic width. This was a Ross, but also somebody she thought was like, kind of a friend in the family because she's like helping out with my kid. Now you're lashing out at me for no reason, but yeah, I agree. She was just, she's 100% and they're just listening. Great listener. And it's one of the things you want as an actor. You almost want it to be like, I don't know what they're gonna say. That's what you wanna make it look like. I just wish there was, I wish there had been more screen time with the two of them together. Cause watching them together is just watching two heavy weights go at it. But yeah, I do agree. Cause she didn't have a lot of, a ton of dialogue for somebody who's basically the lead in the film, right? I guess she would technically be supporting, right? Yeah, I think in this video would be the lead and she would get the supporting. But yeah, she doesn't have a ton of dialogue and it's mostly just kind of reactive. Finding out her daughter got hit by a car to basically all the aftermath of that and then everything else. She had probably more dialogue with the kid than she did with the video. She did. And that's one of the things I'd love to have known on set if she even had this conversation. But I know that I would, if I was portraying a character like that, one of the things I'd wonder from the writer and the director and would probably even question it on set, like when she's there toward the end and she's just cooked for them and she's about to take the boy to the beach. How, you know, it'd be like, so where am I right now? Am I really, do you want me to be vacant? Do you want me to, do you want the distraughtness? I know I can't give too much of that away to the grandma. Where would you like me to be? Because I can give you what I wanna do and the director may say, just show me what you've got with it right now. And then the director may say, you know, whatever little adjustments are gonna be made to that. But that's again, why you need somebody who my guess is she just brought what she did and they were like, okay, cut, print, moving on. Yeah, you gotta do a question at that point. In Vidya as well, I thought she did a phenomenal job. Yes, she did. Very different performance. She was playing a person, a big time journalist in India. Somebody of, obviously, I don't know, I mean, I know of some journalists in India, but the more personalities I know are like big time journalists on CNN, Fox News, or something like that. She's playing somebody like that, essentially. Well, she was about true, so probably not on Fox. Sorry, a little dig there. But yeah, I thought she did a really good job and I thought she had some really good scenes with everyone. But the fact that this whole story revolved around her and something that I think a lot of people face of this internal guilt. Yes. It's actually the main thing to film, and there's a bunch of things the film's about, but I think the main thing is internal guilt and what that does to a person of trying to hold something in that they probably could have gotten away with, but they're gonna have to internalize this for the rest of their life and can you do that? Right. This was really the more complex role. This was a more difficult role in terms of the complexity, not in terms of the overall work, because Shafali's character, like I said, requires you to be a substantial actor. The same thing for hers. And the reason her had the more complexity was because of all of the different nuances she had to deal with. She had to deal with the immediacy of the grief, but she also had to deal with covering up, anxiety attacks, who do I tell, who do I not tell, I'm covering it up, now I'm mad, now I'm diverting my anger over here when I shouldn't be. She had a lot of stuff that she had to deal with that's really hard as an actor because so much of that is internalized with the character in the story. And the last thing you wanna do as an actor is think about, okay, how can I get my internalization to be seen? That's the last thing you wanna do, but that's the end goal. We need to see that. And the only way a good actor does that is Vidya did her homework and she had believable panic attacks and I really believe she, and again, shout out to just the way it was shot. Even though I knew it was coming, it still shocked me when she got hit by the car. Yeah, it was a really good stunt work, CGI worked all together, whatever it was, I was still like, I still jumped when she got hit by the car, both times. Both times. I knew they were coming. And then her beautiful choice, hard to look at of her laying in the gutter, face down, half up, and doing a good job by the actor, by the way, and VFX and makeup. I wanna give this shout out to her. She did right at the very beginning and I knew it was gonna be her. So we're starting at the very beginning of the film and Alia, the actress who plays Alia is Kashi Rizwan. She has that moment with him and she starts to cry and I went, wow, you're emotionally available. That's beautiful. Damn it, I think you're the one who's about to get hit by a car. And then sure enough, but she did have to be there. And I'm very excited about that young actor. I think she's really good. I think she did a great job with the little time she had. And makeup did a great job. Yeah, that shot of her on the ground was intense. Intense, as was. It could look bad. Bad. And if you're not terrible.  Brain damage. So it's easy to make that look like it's not real. Yep, because I mean. You can't really prepare for that. With makeup and with the actor not doing it right. And that worked as did makeup, did a great job of showing us the progression from where she was laying in the street after the immediacy of the hit. But then when you see her afterwards, she's pretty much unrecognizable because of the swelling that would happen in the head. And I thought makeup did a great job. Yeah, really good job by all involved. The overall writing of this, I thought it was really, really nice for not only dialogue, but story. Just like I said, I think the main story that I would take away is from the internal guilt that you have to deal with and how that personifies itself, I guess, outward or with lashing out or anxiety attacks or whatever. And also there's so many other things the fact that she was trying the story and then there's so many other stories that other people were trying to cover up. Yeah, they didn't even know it was her, but they were covering up their own problem with this exact same event that happened from the boyfriend to the police officer. Correct. So they can't, like there's so much going on here and all the corruption that ensues, right? And that was the other story. So you do have the main story, which is of the guilt and the stuff, right? But what I think, and it's a wink and it's a tip of the cap to the director and the writers and the whole team because that's the primary thing and everybody could see that and walk away and not know what the film to me is really about. I think what the film is really about and it's why we saw the title when we did. That was pretty early towards the end. It was almost at the end of the film and that's on purpose. I'm sure it is. I'd love to talk to any of them about it because what she gets stuck in is this celebration moment of the win of this political guy who if you remember, he's the one who's responsible for the paying of the money to the cop because he doesn't want anything bad going on in his jurisdiction so he can win his election. And what this really points to when you take it from that pinnacle of power with the politician and then the cops and then a media person all the way down to this sweet little villager woman who's the servant. It's about the fact that, and there's a reason it's called what it's called and it's the reason that she got stuck in that moment of that celebration and that's what I said in my paragraph and why I phrased it the way I did of that the powerful crush the non-powerful and get away with it and the non-powerful have a choice to try and lash out or remain good people and that's why I love the way they filmed the final shot because I had no idea I thought she did it. I thought she let him die. Yeah, I didn't, I was obviously between the two. I was like, one, I just, I was like, even though I get it, like as a mom, even though also as a mom, would you do that to another kid that you basically also raised as well? Right. And so I was like, I was like, I don't know if this actually happened but also they made it think like it did. They did that and they did a beautiful job because if you notice in the shot, so she's out there on that long extension into the water and you see the boat floating.  Yeah and what it, what it reminds me of a lot of people take this out of context you'll hear as a justification for revenge an eye for an eye. And that was, I'm gonna pontificate a little bit but here from my pastoral ministry years that text was never used to justify revenge. That text was specifically given to encourage me moderation because what would happen would be it should be an eye for an eye not you get to take a life for an eye because that's what was happening at that time when that scripture was given is like someone lost an eye, okay well we're gonna go kill him and his family and it was temper that back that is not justice you're not looking for justice that way and that's what I felt this was about it was like the objective isn't an eye for an eye which goes back to what I said about it's a hard decision to choose good when you've been crushed unjustly and that's really a redemptive thread that happens in the film which is I think that's what's reason to celebrate that's reason to Jalsa is the fact that this woman who has every reason to become embittered and just lash out and say I'm done even her squatting and doing the sweeping of this woman who with all of her power and everything else has been able to cover up the murder of my almost murder of her child yeah I liked the moment at the end where there was nothing said and it was the director of choice used many times in the film to silence the dialogue or just silence the film of like when she was yelling at her son and you couldn't hear what she was but you can kind of assume what she was saying it's almost more powerful sometimes to not know you just know she's saying something she probably should never say to her son that she was gonna regret you saw it on his face yeah and so I thought it was a nice directorial choice and he did it many times he also did it I think when she was stuck as well which is also good on Vidya she basically, that's not an easy thing to do because she was in the car for a good couple of minutes that's what, yeah and so the director basically said I try to get out try to get out try to get out you need to go see your son because she might be murdering your son the way you basically almost murdered her kid and the camera was probably just on her I was like okay do it that's difficult very difficult great choice because as an actor one she has to do it believably and she has to live in the moment but she also has to know I have to stay in this framework as well so I know I actually can't get out even though my character actually wants to get out and you have to justify the fact that I can't get out so what do you do with that if what's happening around you literally is like okay I know I can just open up the store and get out but I have to make it look like I can't it's hard it's acting it's acting that's what separates the good ones from the bad ones exactly and then also towards the end when she was walking along the beach as well and assuming that she lost her son and walking and then just sitting down next to Shafali I thought she did a marvelous job I did too and one of the things I mean I don't know if you noticed this but I wanted to say I put it in my notes I am so happy to see that the censor board has been able to get there smoking is injurious to your health warnings on the OTT platforms I am so happy that's happened man it was so long I didn't get to see it and thought it would always stay that way but boy am I happy you know it'll stop people anyways overall I think it's a really worthwhile film to see I think it's an entertaining film and you'll see some good acting as well from the film yeah and I thought the score behind it as well it was really subtle at times and it also brought the emotion of certain moments at other times and so I thought the composer Guarav Chatterjee and the cinematographer sorry we didn't chat him about it yeah Sarabh Goswami I thought the cinematographer in the film was actually good yeah good choice I think it was lens choices that you guys used it may have been post-production but I think it was lenses that they chose for the discordant sense of panic attack that she got into they did several things they did those I forgot what it's called technically but when you do the the background and foregrounds separate the foreground stays and the background leaves but the foreground looks like it's moving with the blur around the edges and they did stuff like that especially the blur around the edges to enhance that sense of you being in her panic attacks I thought those were well done but let us know what you thought about this film down in the comments below and what should be the next Shafali Shah and Vidya film that we should I know Vidya has no one killed Jessica that we haven't seen a lot of people talk about that one and then Shafali I'm sure she has a ton that we have I just I'm looking forward to when's telecrime to telecrime season 2 yeah you know the first thing we saw her I think it was Satya man probably so and Vidya was Kahani was it Kahani? I think so oh no Shafali did we see juice before or after oh Satya I can't remember I can't remember but that might be before I know we jumped up and down yeah with her in that film yeah oh yeah she does have a new series out that uh yeah I've heard about it human human human um anyways if you've seen that please let us know how it is if not what should be the next film that we should watch down below


I got a chance to try Indomie's new potato chips, the Chetado They're sold online and in stores at various locations. Check the links down below. Enjoy this video Yo, what's going on everybody? Welcome to a special Indomie episode of Fung Ro's food right now I'm here in Sydney, Australia with AB. What's going on y'all and local Aussie Tan A few years ago me and David made a video called five ways to eat Indomie I think he likes me some Indomie I see goreng I can't be the best I am cremes I ever had Right now we are outside of a spot that specializes in cooking delicious Indomie me goreng dishes So I grew up eating me goreng It's really popular here in Sydney, but I had no idea there was a cafe based around it We are also going to be trying the all-new Indomie potato chip Chetado me goreng We've got the Indomie me goreng and we got the brand new potato chips right here. Let's go All right, everybody the food is flying out here. We got cold cutlery right now This is gonna be a whole Indomie meal because we're eating flavored potato chips with the me goreng flavored noodles Indomie is started from Indonesia, but it's kind of like popular like everywhere That's very good. I like it, but um We're gonna try the Chetado Indomie me goreng flavor first, okay Let me show you this chip right here I like how big the chips are you know sometimes when they deliver it the chips break down like these chips kind of stay solid God does taste like me goreng Indomie is pretty popular here, right? But time to try out these wraps and these other specialty dishes that they have here This is a me goreng wrap. It actually has noodles inside with fried chicken as well. This one is something else I would never would have thought of putting it on that wrap. Yo, AB, Tan Actually, you guys are cousins. I will try this vegetarian one Which I know that you know people top off Indomie with a lot of things, but I actually never thought about avocado Nice crispy chicken right here Yo, the sambal mata the chili sauce you got dude, I got avocado I got tomato and I even got some of the chips on the side for the crunch Avocado the cucumber and the tomatoes actually is balancing out You know some of the saltiness and the spiciness you get from the me goreng It's delicious. The Indomie is soft and you get the crunch from the chip. Mmm. You know that these are some thick chips I'm gonna enjoy them They're good But the wrap actually might be the easiest way to eat Indomie on the cold. Yeah, I gotta put this on the chip So I'm crunching that bite I love the freshness that comes with that. Yeah, more sauce. Yes. This is sambal mata All right, you guys are dipping it dip the chip man Going in for seconds ma'am. I need more of that sauce This is more tomato base, this is just straight up red onion base We have the campfire. I see melted cheese smoky melted cheese spicy beef some hash This is like a soda fries like to the next No, the chip can help It's a strong chip. I got a nice full bite right here. You see the spicy beef. I need a french fry on there, too Hey All right, so I've been it up on this. Yeah, we have some white rice. We have some me goreng in there Yeah, some chicken skewer and the fried chicken that they do so well here Nice, crisp on the outside of the skin Yeah, you look the saute flavor. Tell me why we had to go get the big bowl of Sambal mata just because it was so good. I Think it's just really compliment the noodles. Yeah guys. I just put the saute chicken with the mata on a chip Yo, okay, so we're talking about eggs on you know me Yeah, so I had to order the classic the egg just to dip the chips When the egg Everything you want in that bite you get the egg you get the spiciness and you get the flavor of the me goreng on a crispy chip The egg kind of helps tone down the spiciness. We're gonna make a dip that they actually don't serve here So we have your base for guacamole Smash the avocado you need a tomato cuz it brings out Acid let's do some of these And then some of these pickled vegetables right here. Throw those in oh Yeah, yo, I think that pretty much closes out our indomie me goreng feast from chip to noodle back to chip This new chitado flavor, which is the me goreng flavor. It's gonna be hitting stores You know pretty soon worldwide judging by how popular indomie me goreng is yeah I can see these chips being pretty popular too man It's bring back so many memories of just eating it and then now just having a different Scale different level where they add more flavoring and then the sauce brings a different experience to an old classic I grew up eating me goreng and eating the chips is exactly like eating the noodles but in a potato way I definitely think chitado is my new chip to do All right big shout out to a B big shout out to Tom big shout out to Kosuka Big shout out to endo food for providing us the chitado chips man And that is like a new thing that I've never had before so in the comments below Let me know what other foods you would mix the chitado me goreng flavor chips into all right everybody Thanks for watching and until next time we out


Oh, yeah, Laina Sleeping I guess I don't know no no idea I tried to bait him in saying we're doing a one-piece watch party. He didn't he didn't take I was like, what are we? What are we starting on? Just seems like a bait. Oh, yeah, no way. She got butter in that sock, bro. Oh She's actually like going at it. What you don't have to kill him.  Oh, was that a nightmare? Or maybe he just knows how long does rain or have left left a year like a year The last time that's the last thing he remembers is their voices like calling out for him That's the first time that's the first time we've checked in on yeah, I know since the attack, right? Yeah, dang Who is the deceiver Willie, I don't know I couldn't tell you yet. What's their plan here running away?  Yeah, no, it wasn't a nightmare.  Oh Shoot, this is nice those dogs. There's dogs. I saw horses the dogs were on the left. They look so Why does she look like Aaron, did you see that shot? I think they're supposed to be dualities. Yeah She looks a lot like Aaron there. Yeah Why does it sound like a Skyrim quest And I know what you're thinking no Willie and I did not realize right away that these are in fact Sasha's parents We do later on in the video, but I wanted to put this disclaimer here now. Yes We do have our two IQ moments sometimes Ben and Mia I She is so happy on the left.   Yeah I See the animation difference between season one and now is weird Mika Kind of ironic that Mika says oh Mika's slang of a Titan kind of changed her worldview See a different Aaron. Oh That was dark. Oh, that means she's starting to lose faith in Aaron. I think You See Alaina had Did not like that shot of a horse I don't like this feel violated. Oh, why is horse about to eat her bro? Of all the horses I've been around in my life. I don't think they usually do that do they I think would be like just like missing a chunk. I guess it's just to show how lucky she is it's like Over exaggerated it's not it's not the devil's doing it's the horse It's kind of like It's like let's just hang out till Marley comes over war happens Stop I saw a comment Just fantasy stop Well, they were raised in a practically military fashion so they've killed people All orphans Maybe a gavel you'll be able to fit in that way since they're all orphans Oh She probably even knows these people Yeah, wait what yeah, she just said they came from Marley. Yeah, they know She's like you had a very loud conversation at the river and she didn't care Gabby, what are you doing with that?   Don't have an answer for that So Gabby oh Did she not listen to anything she just said Wait, that's the girl that Sasha saved Oh my god If she was alive and Gabby killed her oh my god Where marlion works is that nicolo does he work at a restaurant? Yeah Dang dude. I want to go back. Is that is there an end credit? Oh my god He she said I want to be more like her. Is there an end credit scene? There is What they didn't oh say staged it like Also, they know Oh no Oh, they know dude Aren't they all gonna be like wait, but why would Zeke swap sides Doshi Very ironic Scouts fought side by side with trainers the whole time The world versus paradise they got to prepare The most Oh my god They're all saying they have to go now The world Dang Okay, but the thing is I still feel like Zeke is a wild card. I he's not with But also I ended that last episode with you know the whole wine thing It didn't even touch on that this episode. It didn't even remotely like go to that that you know I don't think it's gonna touch on that again. I think it was just like no no no It definitely will because it showed me It was a special wine bottle and Nicola made a big deal about it and then it showed them pouring wine at the campfire It was 100% alluding to something happening with that 100% Oh, well, yeah alluding. Yeah, not like not they weren't like actually tied together like that. I think they were I still think they were in a way. I don't think that was the wine I feel like this it was do you think this end credit scene like it's setting up like So I feel like if there is a part two to season four I feel like the end of this season will be marley's surprise attack and whether it fails or succeeds Maybe season four part two or the movie or whatever they do will be like the global alliance's attack I feel like that makes sense. I think that the end of this is gonna show zeke's true Uh intentions. Yeah, because and uh, I did I always forget her name Who's the girl with the but the bob cut yelena starts with that? Oh, yeah Yelena whoever is on the island right now. That's marley and it's gonna show their their true plan with zeke That's that's there are a lot of marley ins on the island It's it's kind of like an uncomfortable amount because like it's just like there's a marley that works That works at that restaurant and yeah, but I still don't know where annie comes in Yeah, I forgot about that I think they literally had that scene of arman talking to her to be like, hey by the way Don't forget. Don't forget She exists. Yeah, it's been a few seasons, but jeez here. That's the wild card, dude The true wild card. I want to see the parents at the beginning. Are they actually sasha's wait Are those sasha's parents because sasha's parents adopted her remember they did didn't they are we dumb? We're supposed to realize that oh my god. That was them. Oh my god. We're dumb.  They did adopt her So oh my gosh, and then that's that's very wholesome.  We're so dumb Yeah, I guess they don't they don't really say her last name like that's really wholesome that they started adopting other orphan Dude, wait, they showed sasha's parents like not that long ago because they had the funeral scene. Yeah. Oh my god Hey, at least we didn't learn it from the comments.    What's what's the girl's name the orphan?  Yeah, I get it.  It's so frustrating Oh, we're so dumb. Well, I I realized it after she said it. I was like, oh, so wait, that was definitely her parents back there, right? Yeah, but I just but I think it was supposed to be like as soon as you see them.


What's happening on my YouTube peeps? Thanks for tuning back into the channel right here with me Kyle the rust belt mechanic and Guests here is captain run. What's up? We've got a couple of questions that we're gonna be answering for you guys today one of the biggest ones that we've received question-wise on the channel is Keeping track of your flat rate hours. I know I kind of introduced it on one of my other videos on how we keep Track of our flat rate hours on Google documents, so I employed the help of captain run to do some Hands-on training for you guys showing how that you guys can set up your Google documents Google sheets to be able to track all your flat rate hours Plus a nice introduction for captain and Ron's channel that you guys definitely need to go check out check out this one So here's how you go about setting up your flat rate form and spreadsheet to keep track your flat rate hours If you don't have a gmail account What you can do is you can go sign up for one for free Even if you don't even decide to use the email address get one It's always good to have a backup email in case you need it But that will also give you access to Google Drive Google Drive is just cloud-based storage that allows you to store pictures videos Documents whatever it is you guys might need You get 15 gigs for free, so you can actually say whatever you want It's always good to have some sort of backup for some of your more important documents So you're gonna have plenty of room up there to throw whatever you need up there and also keep track of your flat rate hours So you guys can already see I've got my Gmail, excuse me my Google Drive already up and going Ignore all these files because obviously you're not gonna have files like this. This is my personal drive, so You can see I have my upcoming turtle tattoos here JRC.  This is what you guys can explore these options later But getting to the meat and potatoes of this we're just gonna go straight to it So you're gonna go down to more and you're gonna go to Google Forms It's gonna give you a little arrow here to where you can pick from a blank form or from a template We're just gonna pick blank form because we want to make it what we want to make it So clicking on that brings up another page. So what we're gonna do is we're gonna title this form as flat rate hours and Congratulations, you're done with your first step. So the first thing you want to do is you want to keep track of Dates, so we're gonna put in here. Just type in date When you do so it automatically recognizes that you're wanting to keep track of a date so it automatically configures it for month day and year What you're gonna want to do also is there's a little button right here that says required You're gonna want to make sure you toggle that on and all your questions that you're gonna do You want to make sure they're toggled on because you don't want to submit a Form without having all the information in there That just protects you from giving a form with incomplete information and then your backtrack and trying to figure out what it is So wherever you see this required toggle make sure you turn it on. So we've got our first Question of our form done so we're gonna hit the little plus arrow which says add question And we're gonna drop down to number two second one is going to be your Your order number so we're gonna type in order Oops, oh our DER order Number and we can leave that as a short text answer because that's just gonna be a number So we don't really care about any other formatting for that There's different things you can pick from but what we really want is just short answer So again click your required and click your question Third thing you're gonna do is gonna be what car you were working on so we can put in Say year Model and customer So the way I have mine set up and the way Kyle has his setup is that we'll put in what you're the vehicle is What model the vehicle is and typically the last name of the customer again? We're gonna keep that as short answer because we're just gonna put in some small short text hit that required button and hit add question Fourth question you're gonna do is gonna be work performed work performed Now this one didn't automatically generate what kind of we want it gave us a multiple choice We're not gonna use multiple choice because there's always gonna be some sort of variant in the work that you're gonna do So again go back up and pick short answer So we have a short answer box hit that required button and hit the next question and last but not last but not least flat rate Hours and it please Disregard my bad typing So flat rate hours again another short text answer It's giving us some variables here, but we're just gonna ignore those don't add anything don't change anything down there just hit that required button and That's pretty much it now. You do have the option to put in some other Some other forms or not forms you're some other Choices here if you want to do more so like for example, you do have the option with the multiple choice button Say you want to do a flat rate form for multiple people Say you have you and three other people who want to be able to use this form have one spreadsheet But you guys want to be able to designate which which jobs are yours You have the option to make radio buttons in a multiple choice for your own tech name or tech ID number Which you could then sort in the spreadsheet later on down the road But nine times out of ten most people are just going to be using this for their own personal use So again, it's an option, but not one that's really necessarily needed So once we get this required button done We look up here in the corner and it says all changes saved in Drive it automatically updates for you So you don't have to worry about continuously hitting save. It'll do it for you Go ahead and title this if you just click up here where it said untitled form It'll automatically pull whatever you name this to that So we've already got that changed You can make us click the star if you want to make sure it's a favorite file that way you can find it easier But again, not really necessary.  This is preview Click on that it's gonna open up another tab and here's your form. So Now you have that form and what you're gonna do is you're gonna come up here Depending on what browser you're using You can bookmark this you can favorite it. You can put a link on your desktop So if you were to let's see if I can do this. So if I pull my window down So if I click on this little lock icon right here Click and drag out to my desktop It will actually leave me an icon out here. So if I double click this icon, it will open up this page We have saved right here So going back to full screen We're gonna go back to our original Tab where we were making all of our changes and we're gonna click on responses We don't have any responses yet because we haven't filled out that form But there's one key icon on here that we need and that's little little green icon right here This is open spreadsheet. So if you hold over it says excuse me create spreadsheets So if we click on that, it's gonna give us a window that says what do we want to do? We're just gonna create a new or a spreadsheet leave it named flat rate hours responses and we're gonna hit create So it's gonna take a few seconds link it to the spreadsheet and now we have a spreadsheet with time stamp which means when that input or when that form was filled out the date of What we put in for date order number you're making model work performed and flat rate hours So if we come back over to our form and let's say we do how we did a job today, which is 01 13 2019 Order number was order. I don't know three four three six five five. Why not? What we worked on and we worked on a 2013 I don't know charger and it was for Richardson Why not work performed? Yeah, we did a oil change rotate and I don't know wiper blades and Then whatever your flat rate hours for that the perfect sense for example for us a Oil changes is four tenths a rotate is four tenths and wiper blades will be two tenths. So that's four eight nine ten So that's one full hour of work Once you get all your stuff put in you hit submit and it says hey Your response has been recorded and you can just leave this window up so that next time we need to put in a job You just hit submit other response and it takes you right back to that page Or if you close it out, you've got your handy little link up here. You can go right back into it So Once we have that done we can go over to our spreadsheet and as you can see we have all the information we just put in So one other thing that I like doing as well is up here in let's say g1 or h1. It doesn't really matter This being Excel Essentially you can type in formulas to calculate whatever you want So I like to calculate my I like to keep a running total of my hours So I'm gonna show you a formula you can put in you may have to modify it from week to week But you shouldn't really have to do too much So it is equals sum sum Open parentheses and then you can take your mouse and you can just drag what Cells you want it to do Hit enter And now it puts a one because that's all the hours we have in here So if I come back over here and do a 1 13 2019 order number Whatever year 19 charger blob work performed uh tune up Flight rate hours we got three hours to that tune up. Why not? So put in that one and we're gonna put in one more oh one Oops 13 2019 order number whatever that was a I don't know 15 compass and Say the name is grigger. Why not? And we did another lof rotate and uh battery and we got paid for a 1.3 hours for that. Why not? So once we get a running total of stuff going It'll keep all that information for us right here But as you can see in this cell here It's totaling up all your hours for you So that way you don't have to go through and add it all up yourself It will do the work for you and then at the end of the week when you guys get your time slips all your flagged hours You guys can look through and be like yep that hour right there Matches up with what my total is if it doesn't then you can go back through and start looking at what your hours are See where your discrepancies are um Once you're done with checking all your hours for the previous week Clearing all these out. It's just as simple as selecting. Whoops don't that Um selecting what you want to get rid of so the way I usually do it is I'll click over here I'll hold shift and I will pick another cell And then just hit the delete key and they're gone um You may have to right click and just say delete rows Because a lot of times what will happen is when you do another submission it will actually put it in down here So then you have to delete all these blank rows up here It'll take a little get you getting used to but it's not too terribly bad It'll take you about 30 seconds once you get the hang of it So that in a nutshell is how you guys go about setting up your flat rate time um Form and spreadsheet if you guys have any questions about it You can let rust belt know or you can get ahold of me at my on my channel And I'll be happy to answer any questions that you guys might have Um towards this spreadsheet. So I'm going to kick it back over to rust belt and we'll see in a few Well, what do we tell you guys that really is not that hard of a process to keep track of these things Captain ron's really good at what he does and helping to explain that to you was something that he really wanted to do And it's a nice intro and lead into his channel So make sure you go and check out captain ron's channel I will put a link above and down in the description below for you guys to check that out Captain ron, what kind of things are you going to be doing on your channel? my channel is pretty much going to be a Kind of an intro to a technician channel um with me being in school and me not having a whole lot of um You know automotive background to start with um, I thought it would be a good for I know kyle's had a lot of people asking You know, hey, I'm a guy who's wanting to get into the field of doing Automotive work. What you know, what do I need? What can I do all this other stuff? So I'm going to put out a series starting off of just general Basic automotive stuff had to do oil change properly how to do tire rotation properly um, those might go together, but uh, just other things like how to actually You know dismount and mount rims all that other stuff. Um, I'm also going to be doing a updated toolbox tour of my toolbox So those of you have been asking for those stay tuned for that. We'll have that coming soon Awesome. Thanks captain ron. Like I said, go check him out We appreciate everything you guys have been doing for the channel Make sure you stay up to date hit that subscribe button hit the bell notification So you get notified when I come out with new awesome content for you guys to enjoy I appreciate it guys. Thanks and you guys stay awesome


The 49ers just took it too, the Raiders, and they didn't do it with Garoppolo. They didn't do it with Bethard. They did it with Nick Mullins. This was a clinic put on by a kid in his first NFL action. Yeah, Nick Mullins, who on a short week with no practice time, and he found out pretty much today that he was going to be making his first NFL start. And all they had done coming into this game was walkthrough. So there was very little work within the game plan and what he was going to be asked to do in this game. And a guy who obviously knew the offense, they talk about that being one of his real strengths is his ability to digest the offense and go out and execute. And he's a tough guy, and he played flawlessly, really. And I think Kyle Shanahan did an outstanding job of getting him going early in this ball game. But what a night for Nick Mullins. And I don't know.  We do know what they are, and it's not very good. He's going to get tested. Nick Mullins will, but I'm excited about watching him and seeing if this can maybe continue for him. Yeah, it was fun to watch here in Santa Clara as the 49ers with Nick Mullins at quarterback took apart the Oakland Raiders.