Lesson 6 Support and Resources When parents separate, figuring out what to do next can be challenging. This lesson will look at how family justice counselors can help you, the benefits of mediation, and how to work with the other parent to develop a parenting plan. Family Justice Counselors Family Justice Counselors, or FJCs, are mediators who work in family justice centers and justice access centers across the province. The help FJCs provide to parents is free, so there's no charge for the services you receive from them. Let's take a look at what you can expect. It's important to note that they are not social workers, lawyers, or clinical counselors. They don't give legal advice or take sides, but are there to help you and the other parent sort out parenting decisions and arrangements for your child, whether you are separating or have already separated. These decisions may include where the children will live and how much child support will be paid. Family Justice Counselors may also refer you to other people in the community that might be helpful to your situation. It's important to every FJC that you feel supported, so you are welcome to bring a family member or friend to your initial meeting. As a Family Justice Counselor, we're really here for the families to assist them in working through issues that come up after separation and divorce. We're impartial in what we do, and so what that means is that we're not going to be taking the side of either of the people involved and we're not going to be making decisions for them. We really want to empower the families that we are working with to come together and reach agreements that would fit their particular family. We work with a variety of people, so it could be parents, step-parents, grandparents, other family members and caregivers that are involved in taking care of children. How Mediation Can Help Mediation is a chance for both of you to have a different kind of conversation about important issues that affect your child. You've got to put your kids first because you're always the mum and dad and it's going to play out one way or the other and you can either be in control of it as a mum and dad or you can let someone else define it.  That's what their mum and I did. Twelve years later, I think we're seeing that there can be different ways of defining a family if you want to take that route or you can go the other way and you can have conflict and you can fight it out and you can achieve whatever you think you're going to achieve from there but there may be some collateral damage or debris that comes along the way and you have to be prepared for that as well. In my experience, I would say that those collaborative processes just it didn't make it easy, it didn't make it less painful but it was a kind of pain that was good pain that got us through to something that's been quite remarkable, quite beautiful something I wouldn't have even been able to imagine and if we had stayed stuck in thinking that we have to now hate each other be bad parents, do all the stuff that you sort of see in movies or things like that, I don't believe it's serving parents and most fundamentally I don't believe that that old story is serving our kids. You and the other parents still make the decisions but the FJC guides the conversation between you and keeps it focused on your child's needs which helps reduce the impact of the separation. So normally what I do is when parents have separated and they want to figure some things out so making parenting arrangements, deciding on maybe how often their child or children might go back and forth between their homes having an understanding about what kinds of decisions they'll continue to share maybe not share as they now parent from separate homes having an understanding about what their financial responsibilities are so when parents want to create a plan around that and they want to do it outside of the court process I'll try to help them figure out that plan. Mediation is a powerful tool for families to employ either along with the court process or before the court process. Using mediation lots of families never actually end up going to court as we understand separation is a very difficult process and it's a stressful time for everyone involved and so through mediation families have an opportunity to reach agreements and over time if they need to make changes to those agreements they can always use our services to do so and hopefully never ever have to go to court. The whole idea is that it empowers the people who are involved in the process. The mediator is not going to be making a decision we trust that the family members that are involved are the experts on what is best for their children and we want to bring that out and we want to allow them to come together and reach an agreement that saves time, that allows better communication between the family members and the role of family members is such that they will be connected for the rest of their lives because the kids are involved and so we want to build long-term relationships here. Mediation is going to help parents figure out how that communication can actually work with them. I mean I'll talk about different tools they could use and being able to communicate with each other and how to communicate when things get a little bit tricky and a little bit difficult. I'm there to help them have a conversation that's been proven difficult for them to have but ultimately they know their family best they know their children best and when they can make decisions on their own, solve their own problems it just allows them to move forward in a more positive way. It keeps the children away from the conflict. The children can move on with their relationship they can have an understanding that even though their parents might now live in different homes that doesn't change their relationship with each parent. What will mediation look like for you? Let's take a look at what you can expect. Usually what happens is that the first parent contacts our service or our center and an appointment is booked. I meet with that first parent. We talk about their circumstances, what they want help with we talk about their options at using mediation and I provide information. It's a really good opportunity for that parent to ask questions perhaps without the other person being there and then at the end of that appointment if I have permission from that person I'll contact or I'll reach out to the second parent and invite them in for a similar kind of appointment interview so that that person can also ask questions and me give information about the family law. Once we have met with each of the family members and the decision has been made to move towards mediation we would sign an agreement to mediate because confidentiality is a very important piece of mediation. We want to create a safe zone for the family members involved to be able to say what's important to them without having to worry about any of this information being used later in a court process. There are different ways for parties to mediate. Face-to-face mediation would be together in the same room. That's usually the most effective where you can really talk things out. In some situations you cannot be in the same room and in those situations you would do a shuttle mediation that's done over the phone. One person will be on the phone with the mediator then the combination will carry on with another phone call to the other person. There's also web-based mediation as well where people can be on a computer screen together with the mediator so that's sort of like being in the same room. When it's not possible or safe to mediate the family justice counselor can explain options for you and the other parent. So the times that mediation might not be appropriate is when there is cases of violence or excessive drug or alcohol use. In those cases I as a family justice counselor would most likely refer you to a lawyer to get some legal advice around that. The service that family justice counselors provides is free of charge. When people come in and perhaps English is not their first language our service has the ability to provide interpreters for them and they might have an interpreter at their separate or their individual meeting with me and of course then we can follow through with using an interpreter at their mediation. There is no cost for the services of an interpreter when working with an FJC.


Hi, guys. Good morning. I hope you're not too hungover. I wanted to talk to you today about what we sort of started talking about yesterday, which is dealing with the complexities of packaging all the tools that Google wants to ship in Google's Debian image. But in multiple versions of the Debian operating system, it turns out that there's lots of versionitis and other kinds of issues we're running into. And I'd like to go into a couple of examples. And hopefully, you guys can help me figure out what we need to do, either inside Google or between Google and Debian, to figure out how to deal with these sorts of problems going forward. Like I said yesterday, historically, when we built our images, we just de-boostrapped a file system image, and then just copied all of our files inside. And that was suboptimal for various reasons. You can't update packages and so forth, and you can't remove them. It's just less pleasurable and less smooth customer experience. We'd like to make that a lot better. We'd also like to get those things into the mainline Debian release tree, just like we were talking about yesterday, in order to maybe one day brand our Debian image as official. We've been making some progress on this, and so when we first announced and released our Debian images, we've been starting to convert some of our tools. And we've actually got some nice automation, almost complete, due to WeNugan. I've never really learned how to pronounce our last name very well, but basically, once we cut a new release of our tool and publish it to the outside world, it goes and does a whole bunch of things to build a Debian automatically and stick it into a repository that we use to build images. So exactly what software are we talking about? We're talking about the Google Cloud tools. We're talking about tools for compute, tools for storage, and tools for other products, BigQuery, and so forth, and so on. We're talking about various kinds of software that are used just specifically to make Google compute a functional product, the ability to create snapshots of your disk images, things that manage accounts, and manage IP addresses, and things that set up the host statement and other things like this. We also sometimes want to modify configuration files like SSH and SSHD. There are some issues around the cloud where, for instance, if you don't keep your network connection active, it sometimes will time out. And you'd like to keep SSH, keep alive, and stuff like this to keep the connections alive. But it's not clear exactly how to do that. So some of these are harder than others. So for instance, we found that packaging up our tools is, we don't know exactly how to do it right. Some of the things, and mostly it's due to dependencies we found, some things are easy, mostly because they're just simple files. They don't modify anything else. They have very few dependencies. It just needs Python, execute, or the Python runtime things just work. And then some things are questionable. It's unclear to me that if you wanted to modify the configuration files from another package with your package, how you might do that. That's fairly easy. What was that? A policy? Modifying the configuration file from one package to another is forbidden by the Debian policy. Good. So that solves that problem. Mike, too? On some package, you can include files from the directories. I mean, if you want to modify atc-sudo-us, you can include a file in atc-sudo-us.d, your file. Yeah, so if you're saying if the existing package has a .d directory, you can add files into the .d directory. And that means sometimes patches packages to support that because of this exact kind of use case. And I think we're using that for our syslog. I don't know if that's a patch or upstream. And we should probably switch our sudo-us for the account management to use that as well. Yes, I would agree. In general, we love that idea. And whenever we find it, we use it. But in some cases, like SSH, I don't think that's currently done. It's not supported by the tool. So maybe this is one of those things where we just figure out how to transition all the existing tools. We'll talk about that later. There's a section later. We should maybe come back to that. But those are good ideas. Let's see. So let's go into a couple of these examples of what makes things hard. I talked about them a little bit yesterday. I don't know if we're all of you here yesterday. Yesterday's main talk for Google Compute? Only a few of you. OK, good. So Google Compute, GCUtil, is a command line tool for Google Compute. It's a pretty simple program. It's just 100% Python Apache license code. It doesn't do or it doesn't need anything fancy. It uses several packages here. Google App Utils, Google API Python Client, HTTP Lib 2, IP Adder ISO 8601, and Python G Flags. These are its dependencies.  But we found that, in general, the Python versioning system wasn't doing a good enough job making sure that we got exactly the versions that we want of all the packages. And we were getting many support calls from people who had a system in which some module was a slightly different version because of some crazy dependency chain or something like this. And we eventually just switched over to a worldview in which we basically took the exact versions of all the dependencies that we need and we copied them into our source tree, into our package tree. And we import modules directly from there. Yes, go ahead. You know that it's not possible to do that in Debian, right? I don't know. So this is possible. It's possible. It's possible, but for a video. It might be on Cozier. It might be on Cozier. But in general, we found that it's the only way that we can ensure the stability of the product. Yeah, I mean, I can see both sides. Well, I mean, obviously, I'm wearing two hats, right. But I've mentioned that Debian typically avoids this, but at the same time, whatever, the solution should not, we need to figure out a solution other than having an unstable product. We need to find a solution that respects the reasons behind Debian's policies and also allows a useful experience, like a stable experience, for the customers and users. Is there anybody here who could talk to why the policy exists? I can see HTTP lib2, IP ID, HDR, ISO H6501. Oh, this is in Debian already. Yes, but so many of them have versions that we have not been able to qualify against. And maybe we just need to qualify against all the versions of all these things and all the versions of Debian, but again, that increases the testing matrix, and it's a large support cost. I mean, one of the questions I might have is, why would copying statically into a single package, what the issue would be? So there are many issues. One is code duplication, and the main issue with code duplication is security. When you have a bug in a package, Debian makes sure that that package gets updated. But if you have that package statically copied, then that bug is not fixed in your statical copy. And so you may have a security bug that is, Debian is not able to fix it because you have the copy. Unless they also fixed all the things that depended on it. In front, it's this case, GCU till depends on this and this and this. Your code is not even the Debian repository. So that's not possible. But for packages that help copies, and those copies are in the Debian repository, it means a lot of extra work for the people who are providing patches to also go and patch all the statical copies. So it's more work for security, mainly. So I feel like your best solution here is, if these libraries are in the archive, you should be able to, you should try and work with the version in the archive. Because if you were to make our Python HTTP lib2 a new version, then you'd break other things in the archive. And if you ship your own copy of it, well, then you're responsible for the security. That works as well. But it's now your problem. It's not integrating with it yet. There still is the challenge, though, that from Google's perspective, we need to make it work with Squeeze, and Weezy, and Jesse, and CentOS, and Red Hat, and SUSE, and so forth, and so on. So now we're talking a dozen different versions of all these packages that we have to qualify against and change code to support, right? Of course. Unless Debian wants to take over the responsibility, I guess, maybe, of when, if somebody wanted to create a package of these things, I don't know who. But maybe. Can you say the front desk for new maintainer? Say that again? Say the front desk for new maintainer. You can do that. He's suggesting that you join Debian. There you go. And fix it once. At the same time, the same argument about duplication of effort across different operating systems from Google's perspective also applies from Debian's perspective across different packages that have the same logic at the end, so the same logic has both sides. It's also, from a customer point of view, if I, as administrator of something, when everything uses the Debian packages, it means you have to test more. But it also means I, as user, only have the package once. When I have multiple copies of the package, I have to make sure all of them are secure. All of them fits my needs. If I have something special, I have to fix all of them. So if there is something that duplicates everything, I'm very reluctant to use it as user. Because if I have a big installation, it means much duplication for me. Sure, and I understand the issue. But with respect to this code duplication problem, it's quite conceivable. I could see, at least for some of these cases, the easiest solution for the program developers, which is not actually me, it's the other teams at Google who are building some of these tools, is maybe just to drop the dependency on the library and write a whole separate chunk of code that recreates what happens in that library just because they can control what's happening in that code. And if there's a security bug there, you're still screwed. You can't update that either, independent of this tool. It's, of course, easier for the developer to only have to test with one version. But for me as user, most things that are easier for the developer are things that make me not use the software. If you don't have a bug tracking and no possible way to report bugs, it also means it's easier for you because you don't have to keep up with bug reports. But for me as user, it's a sign that I don't want to use it. And it's the same way with duplication because it means there's multiple things doing the same functionality. And if there's anything special I need, and from bigger installation, there will always be something special. I have to keep up with all the little different versions. And if I am in a more complex setup, I have to verify all of them and keep the paper trail for all of them. And if I have to push a library once through change management, it's worth enough. If I have to do it for a dozen copies, I don't want to do that. But that's still assuming that this tool is using that library, right? If Google Compute tool one day decides that, well, I'm not going to validate against 12 versions of HTTP lib2, I'm just going to write my own. What's that? Well, for some of these, it actually is that much, right? So it's not so much a problem for GpnLtyl. It's more of an issue for the next tool. Just for the leaves that you mentioned here? Yeah, for this one, you're right. It's not that big of a deal. But for this one, some of these libraries change much more frequently. So Bodo and CRC Mod and PyOpen SSL, there are many more versions of these things floating around. And this team would be much more likely to not validate against 1,000 versions of each of these. Can I suggest we let Luciano speak? Sure. Oh, yes. In security team, there is a public file called embed copies, which is basically the database of packages that includes embed copies of other packages. So when we need to patch something in one package, we check in that embed copies. And we patch all those versions too. I mean, embed copies is a problem in Debian as a whole. And I don't see your solution that far, I must say. A lot of upstream developers made it daily. And it is a global problem in Debian. It is how it works. So there's other possibilities. Actually, the biggest thing I want to say is that you should make sure to get through the rest of your slides and bring up the rest of the issues. And this conversation needs to happen. It just maybe should extend beyond this session. Can I say one comment on that? Just on the Boto thing, obviously, we have the same thing. Boto ships in Debian. And right now, it's quite out of date, obviously, on stable. And that's something we're going to live with, I guess. And obviously, the other important point is it's important for these not just to be on our images on the cloud, but our customers are using this on their own installations, on their own hardware, to talk remotely to us. So I think we need to have a copy of all of this in main. It's all free software. So it's licensed compatible. And it's just going to be out of date, which means newer features won't be available by default. My suggestion would be that we have separate repositories where optionally, you could go and add that to your app sources file. We've got app sources, is it? It has a dot date. There is a dot date. So you could just pop a file in there. That's as simple as an echo from the existing bootstrap that we've all got. Yes, it's an extra hurdle, but customers who want to do that can actually copy and paste. Here's how you get the latest copy. So in a way that's relevant to quite a lot of the slide deck, does anybody know much about the PPA main type proposal that the SCP masters mentioned on the mailing list in May? I was hoping one of them would be here to talk about it. Do you know about it? Take a microphone. If you know about it. I know as much about it as you do. So there is a proposal to have PPAs in Debian, which is basically going to mean any Debian developer can create a private independent archive. It's laid on top of the main archive, but you can upload your packages to it and they don't interfere with packages and other PPAs. It's not a repository so that you can upload any random version of things which are already in the archive. If you want to make a back port, you're ready to do so. I think it's best to upload to backports.debian.org. Also, if you're going to be back porting all of these libraries to support your utility in a separate archive, you've got exactly the same problem as if you just dumped them on the machine. If it breaks something else that depends on that package, you've broken something. Yeah, you can break everything in them, like all the other stuff that's been qualified inside of Debian. Part of the issue here seems almost as if you need to have the ability to have multiple versions of packages on a system for different kinds of programs. And maybe balancing the needs of security fixes with different kinds of functional requirements for each of the pieces of software on the machine. I'm not sure. Wookie, you had something to say, I think. Yeah, I was just that Ganev said he was going to work on the PPA thing this week, next week. So actual some progress might occur. That's good. But any useful details? We should probably move on. There's one more person? One more, yeah. Well, if you have to maintain multiple versions of a single package, we already have a 30,000 package. If we have to maintain multiple versions of the same package, it will be a lot of work for us. And we will have to maintain and maintain version because usually upstream only maintain the latest version. So we try to package the latest version. If we have to maintain older version, it will be a lot of work for us. But for your package, I am pretty sure we can work to make them work in Libyan as they are. I am looking at BOTO. BOTO is 296, the latest version is 299. Do you need 299? I don't know. I don't think the version of BOTO is terribly out of date for us. I think it's pie. I think the main ones are CRC Mod and PyOvots SSL. We have a very in Libyan, a very healthy Libyan piton module team that can help you to package the dependencies that you are missing. And we can work to be able to package your tools without bundling the dependency. I'm pretty sure I can volunteer today to help you do that. OK, that'd be great. Yeah, the general problem outcome hopefully will be more collaboration to solve the problems within the existing model and maybe to extend the model where necessary. But so he's also thinking with regard to Jesse, with regard to Squeeze and Weezy, it may be a matter of putting things into the backboards repository to allow people who opt into that to use those where they know it can require some other. I mean, if maybe Google just subscribes the backboards and makes sure that all the versions are the same, but then that might break everything else, who knows. Well, OK, let's move on just a little bit to the next kind of issue that we have. And it's a fairly similar issue. So we're not actually going too far away from the last one. So here, this is, again, we kept coming back to this slide. Where are the version ideas happening for us, right? And in this particular case, it's PyOpen SSL and CRC Mod. And I'm possibly even socks the pie branch. I can't recall. And again, in Jesse, I believe all the versions that we need are there. But in Squeeze and Weezy, which are the released and stable versions of the operating system, the versions are just too old. The situation here in GSU-Till is a lot more complicated, because we can't even do the copying and the code kind of trick to solve the problem, right? Because the binary dependencies, we'd have to build a version for each version of the architecture that we care about, et cetera, et cetera. It's just a lot more complicated. And yeah, let's just move on from here, because I think we've talked about much of the issues around this already, I think. And let's come back, I guess, a little bit to the config file thing, which is another kind of problem that we have. I think we had some ideas about using .dfiles and stuff like this to solve this sort of problem. Yes, go on. Depending on how long-lived your cloud instances are going to be, one thing to consider is to use configuration management, by which I mean that you actually put your changes into central location, and then have some daemon running in the background that enforces these changes on the local system at all times, puppet, or whatever it is. There are small tools, not a whole infrastructure like puppet, although it might be interesting to just be able to actually take that and integrate it straight with your whole infrastructure and have all the nodes be centrally managed. But the benefit is that you will somehow, or at least the daemon users that I know, would prefer to have a very exact description of all the changes that you made compared to the default installation. So before you create a file that says, we changed, permit root login to no, and we changed this, and we changed that, put it in a form where this can actually be enforced. Yeah, I would agree. This is one of the problems with the approaches that I think in some ways Amazon is taking and Google is taking that the build image scripts, they change things, and you can't tell exactly what's been changed, and you can't revert it when it's after it's been changed. The thing that I like about using some of the .d files and stuff like this is that you can install a package that says, this is the Google secure lockdown config package, and I just install that. It applies the updates to all the files and all the right directories to create the policy that you want, and then you can remove the policy later, and you can list it and see that it's there. But again, not all programs support that, right? And do we go and change all those programs so that we can support it? So does Cloud have a mandate now that we have to go and change open SSH so that it supports .d files and stuff like this I don't think it does? So I have two quick things. One very short. Obviously, we don't have any passwords by default, so the SSH locking down isn't particularly important until people create accounts. It's not just the locking down on the SSH. There are several other things that at least Google cares about doing, so network. The other thing is, as an AWS user, I'm not interested in any of Amazon's images. At my company, we use the images Ubuntu publish because we know exactly what they are that got everything we need. And we customize them beyond that ourselves. We don't need any utilities on them. We just need an Ubuntu machine. Yeah, a lot of customers that come to Google, though, want something that works sort of smoothly out of the box. What's very smoothly out of the box for us, but. Yes, but Ubuntu doesn't exist on Google compute at the moment. We don't have a problem with Debian, either. Yeah, so while your company might not care about using tools that talk to the other Google systems, most of our customers need that. He actually meant smoothly integrating with the rest of the cloud platform. Can I go back to what Martin was saying about enforcing policy? So what we're doing here is we're talking about policy when the machine initially boots. After it's initially booted from an AWS point of view, it's your machine. And if you want to go and enable root SSH and you want to go and enable password login, we don't want to enforce that policy from Amazon. We want you to have whatever policy you want, because you could be running that behind private networks, which are not internet-accessible in any way, shape, or form. It's yours to do. So that, I don't know if we need to, I agree, Puppet and Sheffa are brilliant orchestration utilities. I don't agree with that, but. But as soon as it's yours, it's yours to change whatever you want. But I think Open SSH and SSH access, I think that one of the things I raised yesterday that I think is quite useful is what do we feel about having, we're going to install Open SSH into cloud images and that is your way of accessing it. What do we think about having fail to ban or deny hosts installed also alongside SSH so that it's going to lock you out if you do misauthenticate a couple of times? No one? A different IP address. Here you go. I think that all of these suggestions, like including fail to ban and so on, they're great. I mean, I can imagine that there are some people who would really like to have the carefree package and just install an image and know that this is already tightened. But on the other hand, if at some point, if this is a short lift instance, then I don't think we need to have this discussion, right? But if this is an instance that is supposed to live for the next three years or survive a couple of Debian releases, then you, at some point in time, you need to know what changes have been made. And if you make changes and I make changes, I try to keep them in some sort of log file so that later on I know what, when I screwed up, and we need to merge those log files. And all I'm saying is perhaps the abstraction of putting it into something that can be used to enforce policy. I agree that it actually does, right? If you say permit root login equals no in puppet that runs locally and I make the change back to yes and then it gets overwritten half an hour later, that's probably a problem. That's a communication issue though in many ways. But before we have a redundant file that is your log file which I tried to merge with my log file of all the changes we've made to the system and potentially I'll grab a number of the year now, 85% of all the cloud instances are ideally going to be centrally managed with some system like that. Maybe the best approach would be to just enable, at least give the plugs, you know, provide the interfaces for this sort of management from the start. I just wanted to get back to this .d configuration files. You mentioned that you don't want to update all packages to support it. I have heard of a package, I think it's named .d which actually allows you to use the .d folder for configuration and it will then, when the program actually tries to read it, it will concatenate all of them together. So it allows you to support it, even as a program itself does not. This is like a named pipe kind of program. I think it's called .d. I like also to point out that over multiple clouds we need to have consistency, meaning that if you disable root loading in on the Google Cloud on what we want to call the official Debian image, then the behavior has to be the same on AWS or the image that we provide for OpenStack or whatever. So I would be against anything that would be cloud provider specific. I would love that we have only one single image that would work for all of them and that the behavior stays the same as much as possible. Yeah, I would generally agree. I don't know if there are going to be differences amongst what cloud providers really want. So one of the things that I sort of feel I hear is that there's maybe a need for a general configuration mechanism and a policy expression engine of some sort that sort of like a check config kind of thing where you basically register with some place that I want SSH to take over, take this flag and these flags and these flags and then keep track of that history and then make modifications to that via some mechanism, right? That's sort of what I hear people saying, right? I don't want to necessarily install a package that locks down the system. I want to install a policy and make that combine with the existing policy in some way to create a new policy and then have the ability to add another one, yes. I think that's what Martin is saying. I think what Tomah is saying is that it should be done at least for the official images that are the default that are promoted generally not for any local customizations. It should be done in a sort of debbing consensus way with an eye toward the cloud context. Yeah, but if we had this policy in a way that was easy to understand and represent, then it's not as concerned. It's not as, yeah, what I'm saying is that if such a policy were easy to understand for the customer, I don't know that it would matter if it was so much the same as it was just the same structure, that they can look at the policy and they say, oh, that's the environment I am. I'll flip this switch if that's what I want. So you were asking whether you thought the cloud had kind of the right to dictate config mechanisms. I just say that all the embedded people have exactly the same problem, right? That you need to do some customization, you know? And I'm not, and we've done it by installing crappy packages that overwrite files. That's what people mostly do and it's pretty crummy when you come to update stuff. So the Freedombox people have this problem in a big way as well, because they want to make something totally idiot-proof and maybe make a web interface to all the config. And we don't really have a good mechanism for that. So I think there is a good argument for better config update mechanisms, but you know, probably we should try and use something that already exists. So the open-work project has a really interesting config mechanism which integrates well with the open WRT. So, but it's really different from what everybody else does. So it's difficult to use in a Debian context. That's one way of turning all your config into bits which you can then easily just play in a web interface and change that way. But you know, presumably this is what Puppet and Chef and things already do. And maybe we should just use those. And we already have Debian Conf. I don't know what happens when you try and use both of those together and everything breaks. But yeah, this is not a problem unique to the cloud, right? There is, if we had better ways of applying policy and all our installer stuff, you know, the FAI has mechanism for all this as well. I don't know how that applies. Ask somebody if you need to ask Phil Hans or someone who actually knows. I think it's more of a problem for cloud because we have to show it to users and give it to them as their default image, right? And we expect them to change the configuration more than I think in the embedded space. But I totally agree, otherwise. What is cloud config? There was just an imaginary package name that is like, what is the right configuration for cloud? If cloud configuration, it should be different from the basic hosted configuration for Debian, like the center host, the CD version of Debian. Maybe you get it by installing cloud config. But after listening to you, I'm not sure that's the right idea anymore. Maybe we need something stronger, right? You need something that's not just install package. You want something that merges policies in a sane way and keeps historical logs and things like this, right? So you can roll back and roll forward and so forth and so on, right? I think that's what I feel I might want now. One of the things that comes out of this discussion is that ideally, the Debian system should be parameterized completely, right? Ideally, all of the things that you might ever want to change are somewhere parameters. And in some ways it is. We have DevCon. It's not a configuration mechanism, it's a cache. But there's a whole lot of infrastructure behind it requiring the packages in their post-ins file to reconfigure themselves according to choices that the administrator makes or that can be preceded or automatically introduced into the system. So theoretically, that is exactly what you need. However, it's been, I don't know, 12 years that I've been trying to permit root login in SSHD to be parameterized. And for some reason, it has not happened. What are the obstacles there? Is it just SSHD has to be changed? I didn't write the patch. It's all my fault. Okay, so, okay, I'll talk with you later. The point is more that you're not ever going to make it, to find all the parameters and then to convince all the package maintainers to put them in. And then you're also unleashing a whole can of worms because suddenly all the DevCon translators have to start working on the stuff that you've just prepared for them, right? So potentially that's not going to happen, at least not fast. And I don't think you wanna be discussing this for the next 10 years. So another, and since we can't convince Debian to include Ruby, which is required for Puppet and Chef into the base distribution, at least I will object. Maybe there's something much simpler that we need. And in essence, I really like the idea of the .d directories and especially, maybe we can find a way to use that paradigm to make changes. And I imagine there's this tool, August or maybe there's a Clint brought a tool called Deets which is a locally running tool. It doesn't do any network configuration. It just pulls your configuration out of Git and then applies changes locally. And if you can just make it so that, if that, I think that tool is very open to influence. It was a good idea, but I don't think he took it anywhere near 1.0. I imagine that you'd have a Deets.d directory in ETC or in SRV or wherever and then you just drop your policy files in there. And they actually get enacted. And they will make the change to SSH. To the SSH file, just updated by, exactly, and then restart the service or something like that. Now you still have the problem that this is enforced. If I go to ETC SSH.d config and make the change back and then it reverts 30 minutes later, then obviously that is somewhat of a policy violation. But this can be solved potentially with comments or it's a communication issue, as I said earlier. So with any of these tools, that whatever, whether it's .d or Deets or something that doesn't have d in its name, we should, nothing you can do. Okay, there's nothing I can do. We should make it, so we only want to enforce it by default, like with Amazon at the launch, right? And then maybe the user may want to have a way to reapply the policy, but we don't want to automatically override their choices. So remove the crum d. Right, so I think the idea would be to maybe do it once at boot possibly and allow them to rerun the tool that applies it if they want, like not a daemon type thing. So what's that? No, I mean we've got a fun alley side, that's about it. I like the idea about the Deets-like thing, the Deets-like policy thing, because it at least puts all the policy in one spot. I don't love the .d directory ideas as much because you end up in a place in which if I install a package that throws some files in there and you install a file that changes something and in some other way, right? I have to go and look through the evaluation of all these .d files, right? And I have to figure out what the heck this guy turned it on, this guy turned it off, I have to know the evaluation order and hopefully that's the same in each program that evaluates that .d directory. But that's a dash dash test invocation on the Deets tool, for instance. I mean that just shows you exactly what is being done and you could say dash dash what changes and then give it a file name and it tells you the order of policies that are being applied to it. But like modifying SSH itself to take an SSHD directory and then he installs a package and I install a package and you install a package that I don't love, right? Yeah, I think I'd just say that I think we're a little bit fatalistic about using Debcomf. I mean for some of these things that is the right mechanism and we should just use it. But not everything, I don't think it solves the whole problem but it probably solves parts of it where actually a lot of people want to change that particular thing and we should just put it in. And that would actually address the goal of keeping the system as close to real Debian as possible. On the one hand that's a benefit, it makes it very Debian-y. On the other hand, it means it's not like anything else people are used to. So if you're puppet people, Debcomf's really annoying, but that's kind of it both ways. How does this mechanism, so I'm actually not very familiar with that mechanism. What does it look like? Debcomf? Yeah. Essentially it's a protocol that makes questions up here and either get asked to the administrator or fetched from the pre-seed file and then suddenly you have a parameter equals value type system and now when the packages are expected to look at this thing? When the package configures itself and runs the post in script, then it is supposed to merge what it finds on disk with what is in Debcomf giving precedence to the thing that is on disk. I see. So Debcomf is only a cache, it's not the Windows registry. Okay. And the point is that it's easy for it to be, the question part is translated and appears by, could be in a terminal or in GTK boxes or whatever. So there's various front end mechanisms depending on what's appropriate for the situation as well as pre-configuring and translations which is why it's quite nifty. When they say translations they actually mean human language. This is not always clear in the technical context. Gotcha. Yeah, so the package is the one that manages its own Debcomf questions and it's done by the package infrastructure for the package. Obviously it's relatively heavy weight in terms of affecting each package and you have to put the variables in. So, it's a bit of a slow process than just having ETC Keeper or some other magic that just does whatever we want to do to our ETC directory. It's a slightly different thing. This is automatable at the installer level for example. The concept of getting something like Deets into Debian proper is long ways off, probably. Very feasible for Jesse and backboards. Okay, good. Any other quick questions? Comments? I don't know what you mean with Debian proper. It is in Debian. I mean official mainline Debian official release whatever you might call it. It is. It's just not in the base system so it will not get installed by default. I see, I see. So you just have to add it as a package. It's in there. It depends on Lua, which may be a showstopper, but no, that was supposed to be a completely objective statement simply because it has dependencies and then that makes it difficult to get into the base package. But I think that Clint, who's pretty well known and knows Debian very well. This is a very Debian specific approach. This is not at all like what Puppet is trying to do to be like the solution to everything. But I think he's no longer maintaining it or no longer adding stuff to it. So it would basically someone would have to look at it and shake over. Which I think it's probably worthwhile to check it out. Oh, dang. Ooh. Just relaying something from IOC. Petter reminds us that there are levels of debcon questions that will never show up. Hidden questions for things where you want to automate or we want to precede something, but you would never really want to ask a user for it. I think we're about out of time. So I just want to thank you guys for chatting. I'd love to talk with some of you more about Deets and Virginitis and stuff like this and how we might deal with it. I mean, really it's Virginitis either and for the like in the operating system or in the person who's writing the software. Right, you have to deal with it somewhere. I wanted to just let you guys know that this week we actually are building new Debian Google Compute images. I meant to say it yesterday, but I forgot. Jimmy and I are probably going to be doing that Thursday around noon. And if anybody here wants to like help, you can actually have you guys like run the commands and install it and send it to test and all that stuff if you want. Yeah, it doesn't require being a Googler. You know, any DD, it doesn't even have to be Gmail account, just any Google account. We can, you can sort of see how Build Debian Cloud works. You can run it on your local laptop. You know, the account is only needed to upload to add the image. It's a really neat thing to get involved in. Thanks. Thank you. Thank you. Thanks.


Sure. We should wait five seconds for the D-Led chair. I know, right? Right. I'm just gonna chair. I'm gonna like the chair. You'd be like Jamal Williams from Wine's Rock, Paper, Scissors. I mean, we could do that. What was your childhood game of choice with that? Was it Rock, Paper, Scissors? Yeah, it was Rock, Paper, Scissors. Yep. If I'm going against my wife, I always go with Scissors like four times in a row and I still beat her. I mean, Rock personally, whatever. You beat me every time, of course. So, when you look back at Sunday, how much do you expect to see something similar to what Tampa did in the first half where they basically were angling kicks away from Cordell? Well, we expect that every week. With a dynamic returner like Cordell, you're expecting that teams don't want to lose a game based on the best player of the ball. So, it's a benefit for us to have two guys that can handle the ball back there, other guys like Keith and Avery to go back there and catch the ball, field it, and at least give us decent field position or the offense has the ball the next play. So, that's critical for us. And we expect that every single week and those are situations that we work. Question there because I don't think we see it that much, but y'all did it in the second half. Could you just move Cordell around to kind of make it a little more difficult on teams to figure out where he is? Is that something that would ever happen in a kick-off return game? Oh, yeah. We actually did it after the first kick-off return. We did it after the first one, and we were messing around just to, you know, we're playing chess with them, just seeing what they want to do. And Cordell, he's a very selfless individual and it's all about us getting our offense in the best field position and being productive on that special teams play. So, the one that we were talking about in the second half, you know, that ended up working out in our favor where, you know, Avery was the deep returner and, you know, you can see on the film, C.P. goes and blocks the backside, too, to kind of free up things and let Avery do what he can with the football. Oh, for sure. You only get better with reps and those live game reps are very valuable for us as a special teams unit, especially as a returner because there's always, especially having a C.P. back there, there's always going to be a dynamic or a different situation that we're working to get a lot of calmness to that return unit when he has the ball in his hands. Going back to one of the corner, what do you need to see from Cam or from Delcey really to say, okay, I want this person this week or for the rest of you? What do you need to get from that? The overall thing, Mike, I would say is consistency. Consistency is critical, you know, day in and day out. It's very limited special teams reps. We said it before, like in one of the other times where we talked, we were guaranteed a kickoff and a kickoff return. So we might punt one time in the game. We might punt eight times. Hopefully we don't punt as many times, but if we have one punt in the game, we better win that rep. And it starts with our protection, goes down to our punter, being able to execute his technique and then our gunners and our coverage making plays on the football. So consistency is critical for that position, as it is for all positions on special teams. I'm not going to pretend to understand, you know, punting a mocha is going to be a good punter but beyond exactly obvious, what was Ken struggling with and where were things going wrong? For him, it's just his basic fundamentals. You know, one, just making sure he's doing his job and being consistent with his proper technique. And those are conversations that we have. You know, people could get as a, you know, a team or a player, you can get fixated on the actual results rather than focusing on the process. So that's where we're spending all of our time, each and every day, each and every week is the process because the results will come. And he's continuing to get better. So, you know, we're just going to keep working. It's a great challenge this week, going against New York. And, you know, right now, we're still in the evaluation process when it comes to that position. Before you had the practical flexibility, it was almost like you would have to work out somebody and then you have to make a choice. Correct. What is this week up for you and what are you trying to evaluate during this week? As you look at, I mean, Justin, I'm sorry, Justin has been around the block and you have Ken, what is, like what are you looking for to make that decision maybe Saturday about who your partner is going to be? You know, having that flexibility, having 16 on the practice squad is great for our organization and for our team because it allows us to bring, you know, older players in too, not just limited to the younger players, to be able to always evaluate our roster. And we're always looking to, you know, continue to grow with the roster because our roster is going to change from week one to week 17. So when it comes to a guy like Dustin and Cam, which is continual growth in that position, you know, confidence, you know, and then also the biggest thing too is the consistency with their technique because that's everything boils down to is they're being able to handle their technique at any given time, whether we punt two times in the first quarter or we punt two times in the fourth quarter and we're up two scores and they're putting pressure on us. So that overall consistency and, you know, working on their technique day in and day out and being and growing with that technique. So we have all the confidence in the two guys that we have here and we'll see how it goes. On the street who would like this opportunity, why Dustin and what, what have you seen from his tape and in the limited time here, why he was the guy that you wanted to bring in?  Obviously, as a holder and as a punter, he has a track record of being successful and that helps with our special team. So, and then he's, he's had a consistent career. He's always been playing at a high level, playing for a very good special teams unit when he was in Kansas City. I'm going to talk earlier about the versatility of CP. I just want to ask your assessment in these first couple of weeks of Richie Grant and Jaylen Popkins, how they've been working on teams.  He brings a lot of versatility when it comes to that position and, you know, making, you know, all four phases, whether it's blocking in space, covering in space, being able to move him in different positions, and that was something, you know, an evaluation process going into the draft. We knew, just particularly for us on special teams, that he could be a player for us. And, you know, it's great working with Richie because he really focuses on each and every day competing at a high level and he wants to be the best at his position on each phase.  He's experienced a lot of different things in his career. It was what you've been exposed to and how you grow to it. That's what I believe in when you talk about experience and for having an elite player like Dustin, a punter like Dustin, to have him in the building that's done it for a long time and he's had success at it. He's played in Super Bowl, he's been a pro bowler and he's been through the ups and downs to be able to provide that type of knowledge and experience to Cam is invaluable, especially for a person that's played that position and Dustin's been great for the room. How many punters? We looked at a handful, number-wise, we looked at a handful and, you know, Dustin was... he was the guy we thought would fit well with our organization right now. They don't know... they just see the punting like they were going back in. Yes, sir. How much input do you have and how many punters do you watch before you bring that in that situation? Do you always have a short list or maybe it's kicker or punters or snappers? I wouldn't say a short list, but that work, you know, any given year, that list is always evolving and particularly now, you know, with having 16 on the practice squad and having that flexibility to having a specialist here because, you know, COVID protocols and being able to maybe, you know, eventually get to elevate someone will always have a short list and that list is always changing day in and day out based on availability. So that list could go from two people one week, it could go to eight people the next week. So it's constantly always changing when it comes to evaluating, but as an organization at every position we're always looking at evaluating and making the most out of our roster. So the whole earlier Friday up on Fridays and then the least on Monday things the last couple weeks, is that strategy in case something happens to young women because of COVID or something like that? What goes into why that has been happening? You know, that's more of a question for George Smith and Terry, but again, it just, when it comes to the roster just making the most out of our roster day in and day out so we can operate at a high level. Yes, yes he is. Does that make any difference for you guys or for the other? You know, at times it makes a difference for opponents, no different like going against in college football every, you know, you go against a team like, you know, Georgia Tech back when they're running the wing T or Air Force, that kind of changes the variable for that week for that particular week the rotation changes on the football a difference from a right foot upon our left foot upon her for us and special teams it doesn't really matter, you know, being able just to get the ball where it needs to get to with the proper hangtime and direction that help, you know compliment our coverage units and our protection units. Talking about the coverage, do the gunners need to understand something different, right versus left?  Well, it's more so a returner when we talk about direction for the gunners, they need to know the direction of the punt because we talk about because often myself we talk about not putting as much miles on our tires if we're playing gunner together and we got to release to the right all right, but he punched the ball left now we're putting more miles on our tires just to get from point A to point B rather than being efficient so we could be effective at the point of attack. Talk about return specialists and how they should fit into that conversation.  I mean your impact player and you're changing the game in that aspect and you're creating offense in the special teams game and you're putting points on the board I think you should always be considered in that aspect just as a ball player. You think Devin Hedgers is a homoplayer? Eventually I think I mean for sure I mean he's affected the game in so many ways when it comes to being a return specialist and the way special teams coordinators and coverage units prepare for a guy like him I mean he changed the game and if you're in a position where you can change the game in that aspect I do consider you a Hall of Famer. Thank you guys.


hurt ourselves with turnovers again, we got to have complimentary football when it comes to that and with the turnovers and it just wasn't a smooth game. We got to play better. The offense line has got to play better. I think we did a good job running the ball. I know there's several things in the run game I could have done better today on my combinations and stuff and so it's tough. They played a great game. Their offense played really well and hats off to them. For me it's a long grueling season and so it's another week for an opportunity for me to get my body healthier. I think every single week that I've played and been able to play with my leg I think things have gotten better and better and it's showing and so if I could just continue to take this week as a professional and keep growing not only physically but mentally like you said but I got to see my kids man I miss them so bad so I'm really excited to see them. Yeah we have five games left and I thought the guys from an offensive standpoint I don't know defense. I have no idea. I can tell you if it's one high or two high before a game what front they're in but I don't know defense like that but all the guys on offense I thought played really hard today. Guys were finishing downfield, our running backs ran really hard. Any time you have success running the ball the receivers are downfield blocking. Guys were really giving it their all and so I'm proud of them. We just got to score more points. We had to score more points and not hurt ourselves so this is a good week to come back and gather ourselves like Vrave said mentally and physically and move forward and take a step forward and not a step back. Is there a certain point perhaps where the injury has become too much and might you have reached that point? I don't know. I mean we've dropped two in a row so our record that's a huge bummer on our record and how we've lost that one seed or whatever but you know Vrave has done such a great job as a head coach of putting guys in. I mean injuries happen. There's nothing we can do about it. I don't know if there was a way to stop injuries every single team in the NFL would do it. How many we've had this year is just a super you know super unfortunate but Vrable every single week harps on the team keys puts guys in there. Our coaches do a great job of you know if we have our whole starting offensive line putting more in the offensive line we have our whole receive record putting more in them and plugging and playing guys and teaching them the game plan to where they know what's going on and then go play fast and aggressive. I think you know I think Vrable and this whole entire coaching staff deserves a lot of credit for that. Yeah. The thing with the running game it's a week to week thing you know different defenses bring different challenges and you know we were able to open up some holes and those guys have their own unique skill set when they came out and they ran hard. I'm really proud of them and the way they came and I was impressed with them today and hopefully we'll continue to move that forward but you know we got to we got to make sure protect the ball at all costs especially as an offense that's our duty. He has that on the long run where it was knocked out right on the sidelines I was five yards away from that ball you know if I finish a little bit harder on maybe I can be the one hit it out of out of bounds and not have the DB fall on it so it takes all of us you know you never want fumbles but if I go a little bit harder maybe I can you know knock that off the sideline and we just continue moving forward and so like I said it takes all eleven of us to run the ball throw the ball and we got to be a whole lot better yeah we knew we knew we had to do I mean we we knew we you know anytime you go on an away game you got to have a strong chin and a big heart and you had to pack a run game and I think we did those things and you know I think the effort was outstanding from everybody on the offense and we just got to keep those drives going I mean we are crushing it from the 20 to the 20 but we got to finish those drives and and you know the one on fourth down with with the pass that was intercepted I mean it's fourth down you know you got to rip that thing in there and you know it's not he just throw it out of bounds live to die another live to play another down ten now you know he's got to try to force something it is what is that that situation in the game so but yeah we got to protect the ball


Why learning grammar is essential? Some may conclude that the correct usage of English grammar only matters to teachers and have no real relevance in day-to-day life. We have to conclude that this is incorrect, because grammar disregarding the country or the language is the infrastructure of communication. For instance in the simplest of examples, when a message is delivered with the correct usage of grammar, it is much more understandable and precise to comprehend the intent and meaning of that message. Knowing proper grammar uses key. To have a beneficial and enjoyable time communicating, the learner must know the proper usage of the grammar of that language they seek to use. It is essential in the free world to have the ability to express oneself, but this does not come easy for everyone or every topic. Therefore the importance of mastering a language for this very purpose, towards progression in civilization, become evident and necessary. A great deal of conflict one faces in their life seems to include an error or deficiency within the communication. It shows again that the mastery of language is also a mastering of communication, for one's benefit and for the benefit of those whom we interact with. Grammar in writing. Now writing properly is even more paramount. The proper use of grammar is essential in the professional world in conflict resolution. Writing that is poorly punctuated and consists of errors, are laborious to read and can become impossible to comprehend. In linguistics, grammar is the arranged structural order which influences the configuration of clauses, phrases, and words in any given language. It is the methodical study and description of a language, and it aids us to understand how words and their component segments combine to fashion sentences. Grammar to cultivate habits. Grammar rules can aid learners to cultivate the habit of thinking reasonably and distinctly. Without the proper use of grammar and its structures, precise communication is impossible. Proper usage of grammar keeps one from being unintelligible while conveying thoughts and ideas. Proper usage of grammar organizes the mind towards the skill of expressing ideas with little to no difficulty. This results in the ability to speak, read and write fluently. Someone who has poor usage of grammar can make a negative impression. As intelligent sentient beings, we can cultivate this mastery of fluency and these are marks of progress. Further writing and speaking correctly gives an appearance of credibility that may also foster comfort from those you are communicating with. Improving grammar at its best. It is unfortunate that although amid the development of social networking and technology, many have become incapable of using proper grammar in day-to-day communication. Some of the ways we can improve grammar are by consciously listening to others who use the English language well. Often, films and television shows are written in proper grammar. Lastly to cultivate a mastery of language, one must read a lot. It not only improves grammar, but it also improves vocabulary. The knowledge attained from this can indeed transfer into one's writing as well. Do you want to teach English abroad? Take a TEFL course.


We've been talking last week introducing a little bit of things that have a rate of change. Okay, we talked about maybe income, a cable bill, a phone bill. We did the lab about doubling, the little story of the grain of rice. Were you surprised when you started deciding and answering the questions about the grain of rice? Of course, surprised that I had given you the answers, Joshua. But were you surprised about how quickly, what was the girl's name in the story, Ronnie? How quickly Ronnie was able to feed many, many families, I mean one grain of rice, once you get a handful and then two handfuls and a bucket full and two bucket fulls and quickly she was able to feed a lot of people just by that doubling. So, and that was an example of exponential rate of change. But together we're going to work on writing a few examples of functions. Okay, do you remember the term function from your algebra classes? Yeah. The pencil thing? You know, like the pencil test. Y'all know what I'm saying. I know what you're saying. Well, I want everyone to know. Do you remember the vertical line test? Is that what you're talking about, the vertical line test? If it touches two times or more. Okay, so the, we haven't used the word function. We've just been talking about representing using a graph. The rules, the algebra rules for function and Katie is right. Let's take this idea of doubling from Ronnie's rice, one grain of rice story. Katie has remembered this rule about the pencil test or the vertical line test. Who has seen that before? Who has a vertical line through the graph? And it crosses no more than one time than it can be, than it is a function. Do you remember hearing that from algebra class? Raise your hand if you remember that vertical line test or something about that. Okay. Now there certainly are graphs that don't pass this vertical line test or aren't a function. But the whole point of the vertical line test is this. For any input, okay, so here's, this is, this is maybe our graph of the one grain of rice. Okay. For any input, there can't be more than one output. Remember that, what we were putting in, we did this. F1 of x equals two to the x for one grain of rice. The doubling function. Okay. Or doubling the pennies that you make. All right. This is what I input. And in our story, it was about inputting in what day we're on. So if I input the day that Ronnie is collecting her rice from Rajah, the output, there's only one output related with that. Okay. So on day three, Ronnie could not collect eight grains of rice and a hundred grains of rice. There's only one output associated with the input value. Okay. We talked about our cupcake factory. All right. And we had something like this. An example of a linear rate of growth. This is our profits, for instance. And it was looking pretty good at that time. Okay. So if I were, if we were going to gather together in our meeting and talk about profit for June. Okay. And everybody brought in and we had our marketing people, you know, do our number crunching so we could see what our profits were for June. We couldn't have, you know, for that report for June, we can't say, well, our profits for this month were 500,000 and 750,000. There's only one output associated with that input. I might look at different days. I might say, what about June 18? Okay. There was a profit of 450,000, but June 19, maybe not 450,000, but 30,000. Okay. And then June 19, there was a profit of 70,000. So on different days there might be, but I would be using different inputs. Okay. Think about the temperature and temperature as a function of time of day. All right. So I look up to my back deck and I look at the thermometer to see how warm it is at that moment. At that moment in time, 3 o'clock p.m., okay, it cannot be 65 degrees and 70 degrees on my back deck at that moment. Okay. That's the whole point of that vertical line or pencil test. That's the whole point of it. When I input, if I'm looking at something that is a function, the output value or the function value or the y value, the f of x value, always the same thing, cannot be two different values for that one input. And that's what the vertical line test means. Okay. So we haven't really used the word function, but you've probably heard it before. What we're talking about, we are writing functions because we use the calculators, your CAS system, do that the other day. But that is what we're doing. We're writing functions to represent a picture of a particular rate of change here. And the old linear function with a negative rate of change. So let's take a look at what folks are doing here. Got a couple of people with a negative rate of change. If everyone at your table has a function, choose one to think about what might this represent? What story might go along with your linear function that you have input? What is it that shows the rate of change for a linear function? Anybody at the table? What is the rate of change for a linear function? What is it that shows how this thing is changing according to time? What? This is where it is aligned. Okay. The linear function should show a line. There you go. It's the slope. The slope is what shows the rate of change for a linear function. Okay. So if we want to show a negative rate of change. So look at Ashley's there. She has a linear function with a negative rate of change. Okay. Let's see what folks have here. Okay. We have lots of examples of negative rates of change of linear functions. Let's take a look at who has a story that goes along with their linear function. Who has made up a story that this might represent so we could show yours. That's okay. Okay. Okay. So something that might be a negative rate of change, Barbara said from her table, might be temperature from summer to winter. Okay. We're experiencing the temperature change right now. The temperature is decreasing and that's a negative rate of change. Now it might not be, you know, we would have to collect some data to determine if that was a negative rate of change. Depending on where you lived in the world, that rate of change might be more dramatic or even living in a different hemisphere, that rate of change might be a positive rate of change. That's kind of, certainly from summer to winter, a negative rate of change. Okay. Does somebody have a story that goes along with their function? Let's take a look at this one. Does somebody want to fess up to this one? Okay. That's what you get for missing on Friday. So talk about, I mean, Wednesday. We all missed Friday. Yeah. I mean, isn't it? Is it linear? Is the rate of change negative? Oh, no, because I'm picking on him. I picked his and he wasn't here. So what is it with a line, with a linear function, what is it that helps us know that represents that rate of change? What piece of that formula? Okay. This negative sign right here that Joe has helps me know that that is a decreasing function. Okay. A decreasing, now, so the negative tells me it's, the line will be decreasing. What's what word goes with, what word goes with the rate of change for that line? Ashley said slope. Okay. Slope is rate of change. All right. So this is a negative slope for a line. The slope or the rate of change is that coefficient of X. You've seen it before in your algebra classes. Okay. Slope intercept form. Find the slope between these two points. So what we're doing now is instead of just finding slopes or graphs for no particular reason, we're going to try to examine these functions in context of something. Like a cell phone bill or like the doubling example, the grains of rice. Okay. If you want a negative rate of change, okay, the slope for a line should be negative. Okay. Now what other number do we have here? Okay. And how does that, what does that have to do with this particular, it is a positive, it's a positive 7 and that, Joe, can I get you to change your window so we could see the top of that? Click okay and let's see what your graph looks like. There we go. We have a better, now, customizing that window, he's given us a better idea of his function. Okay. And again, so the slope, there's the negative rate of change. The slope is the coefficient of X for a linear function. That's always the rate of change, the slope, okay, coefficient of X. And then I gave away, you remember that the word Y intercept from algebra and the Y intercept for a linear function, well for any function, it's some initial value at the very beginning. If we were to input zero right here for X, if we were to input zero, whatever the slope is, doesn't matter, time zero is going to be zero. And then I'm going to add to that the Y intercept. That's why that constant term is always for any function, the Y intercept, because when I input zero for X, it knocks out any X terms. Okay, the initial value. And we're going to talk more about initial values as we move forward with rate of change. What might be, were you going to say something? What might be a good story to go with Joe's linear function? What might this represent? Just be creative. Stock, if this is an example of stock, buying stock, how much did Joe purchase the stock for? When he bought in at day zero, he bought it for $7. Or $700 or $7,000, whatever the scale is, we'll just use as is. Now, how's Joe doing? How's his investment coming along here? Decreasing at a half a percent. Okay, let's be careful. It is decreasing. And it went away. It's decreasing. Why do you say half a percent? Well, it's got to be decreased on some measurement. What is the measurement? Well, I said point by point, 50 cent. 50 cent, which is half a dollar. Okay, so be careful about throwing out percent there. Okay, we want tempting to say percent because we see a decimal. But this, we've defined, just making up our story here, that this graph is in terms of dollars. Okay, this axis is about dollars. I'm glad it does. 50 cents. He's actually losing a lot more. So this vertical axis is dollars. And let's say, what are we going to call this axis? That is time. What do you want to call it? Change is pretty regular. We're making this up as we go. We can say whatever we want. It could be a daily change, weekly, monthly, yearly. You're the stockholder, Joe. So what do you want the time to represent to be? Well, if it's going down a decade, it would be crazy. A decade? It won't be civilized. Yeah, let's say it's maybe weeks. Okay, I would like to say decades, but in reality, that's not how we measure stock. So let's interpret Joe's graph here. He has bought in to this stock at week zero. And how much did he buy it for? Seven dollars. What's happening every week? Very nice, Calvin. So we put it all together, and that's the rate of change. That's the rate of change for this story. Joe, sadly, is losing 50 cents every week because we defined the time to be weak. Now, Joe extended his graph so that he could see when it crosses the x-axis. Why is that important in this story? Actually, he's not really gaining, because the value of what he's bought in is losing. So this is the graph of the value of this stock in our cupcake business. Okay, so he bought in at seven dollars a share. When will his stock be valueless? When will it be worth nothing? Zero. Okay, so Justin and Calvin are pointing here. 18, 17, 16, 15, 14. So just reading the graph, we can see his stock is going to be worth nothing, sorry. In only 14 weeks. Just from reading the graph, another way we could figure that is to say, when will this, when will his, when will this function be worth nothing? Okay, and he used the term before x-intercept. That's where the graph crosses the x-axis. When will this function be worth nothing? Okay, how about you scribble down and just make sure, use some old equation-solving tools to find out when will this function be worth nothing? See if you can solve this equation for x. See if we don't get an algebra solution of, did you say 14 days? 14 days. Okay, solve this equation for zero. When you use some algebra, did you confirm that that particular will be worth zero at 14 days? So we use that algebra to confirm what the graph says. Okay, let's look. Do we, what about, can you find a graph that we're looking at here that has a y-intercept of zero? Whose graph has a y-intercept of zero? No one on the top, yeah. Which one, Cronella? Five, six, one on the top, six went to the right. So one, two, three, four, five, six. Okay, who's this one? Who wants to confess to this one? A y-intercept of zero, is it a negative rate of change? Decreasing rate of change, look at that, a negative 2x, sometimes you can see that bar. Negative 2x, and where does it cross the y-axis? Zero. Right at zero. Okay, so this particular function starts at zero and then goes downhill from there. So any others have a y-intercept of zero? What about this one? I want to ask about this one. Does anybody, anybody have a concern? It's positive. Why what? Why is it positive? Oh, I don't know. It's not red, Katie. So that one, oh, and it's also not, it is also not positive. Anymore. Anymore. Okay, very nice. Oh, look at this one. This one is a slow death here. What is the rate of change? What's the rate of change for this one? 0.06. Maybe you can't say, I think it's 5.05. So that was, it is decreasing, but at a much slower rate than the one we looked at with Joseph. Okay.