I'm Tomash and I'm product owner for Peket project and here we have Brian, the lead of the Centos project or like, actually Brian, can you introduce yourself? Sure. Yeah, my name is Brian Stinson. I'm the technical lead for the Centos stream team. We work in the community platform engineering group here at Red Hat. So Tomash, I think you're going to start us off with talking a little bit about containers and all that stuff and then we'll go back and forth. We'll have a few different interesting ways that you can consume Centos stream. Yeah. Okay, I'm going to share my screen and before I do that, so if you want to participate yourselves, Jen posted links to the content of the workshop and also to, like a two way how you can download your either PM images or container images and it would be great if you did it right now. For example, for me, it took me like five minutes to download the vagrant boxes. So if you want to participate, please download them now. Thank you, Jen. And I'm going to share my screen right now. And here you can see my terminal in the, to the, like, upper side, the I'll have my notes. And I hope that it's not too disrupting. And on the bottom side, that's where I'll be running my commands. So, one of the ways you can actually consume Centos stream is via container images. And I hope that I don't need to introduce what container images are, since we're in DevConf and this is a hot topic past five years, I would say. The container images for Centos stream I hosted at quay.io in the Centos namespace. You can see the link right over here. They're available in three architectures, the normal MD64, which is probably what your laptop has. And the additional ones are ARM64 and PowerPC64, a little MDN. And obviously I'm going to be using the one for Intel, because I don't have the other hardware. I have a Raspberry Pi, but it's still 32 bits, so. Okay, so let's, let's pull the image and I already did that. And so it will be very quick. Actually, if you're familiar with Podman, and this is something with Karl mentioned to me when we were preparing this workshop, there's a feature in Podman 3.0 called short names. So when you are in, when you are using Podman 3, you can actually just do full Centos stream 8, and it will work, it will figure out that the home for the Centos image is quay. So that's going to be even shorter. So now we have our image here, I have it on my laptop, and I can invoke it and try it out. So let's do that. I'm doing dash, dash, dash RM, so that it's just like a throwaway container that I don't want it to linger on my host and TI are so that we can actually run bash inside. And that's it. I'm running Centos stream right now on my federal laptop. And let's see if that's actually a reality. I'm going to scroll and look at what's inside, let's see, release, and you can see that this is in this, in this Centos stream 8. And for me, this is actually a really great way to try different like operating systems or versions, or I usually do this. So when I, when I want to see like what version of a package is in this certain like Centos stream or federated to. So for me this is super convenient way to do it. Also, it's a fresh environment. So if you need to like I know like test something or try something you can get fresh environment like this very easily and it's super productive for me. One thing you can do right now is you can install packages or you can just update it because like the images and the composites or like packages have different lives. So if I run the update there is possibility that there will be some updates. So you can do that if you want. You can see that metadata has been downloaded like the usual stuff. So one thing you could also notice is that I was using, okay, let's do this right now. I'm going to quit it. And one final thing I wanted to mention about container images and that is that I was using the stream 8 as like the tag of the image. And it's actually important to distinguish because you, I could have just done this, like without the eight, and I would still, it will still work. But since we'll have sent us to nine soon, like, I wouldn't know what exactly is inside so it's very good practice to actually, like, pick the actual version so that you are not surprised that suddenly there are different versions of things and your software breaks, like always into a specific version so that you know what's exactly inside. And that's actually how you can run center stream in containers. I'll hand it over to Brian.  Hopefully you can see that the, I think the next topic that we wanted to talk about is, what do you do if you have a sent us Linux 8 machine, but you want to try out sent us stream. I think one of the, one of the important goals that we had, you know, dealing with with all the things going on in the stream world right now was, we wanted to make it. We wanted to make it pretty simple to take an existing sent us Linux 8 machine and just migrated over to stream and start, you know, getting regular updates. And so, I think Jen posted in the chat there, a link to our GitHub, the, that's some of the materials that we're using for this workshop today. In that, in that folder there, you should find a vagrant sent us Linux upgrade. Directory, that's kind of vagrant file that will take you from it'll start you from a sent us Linux machine and then we can sort of walk through the steps here. Really, like I said, we wanted to make it as easy as possible. So right now it's, it's actually three steps. There's three commands to run to take a Linux machine upgraded to stream in the future. We're kind of moving around some of the packages and where they live in all of the different repos. We were hoping to get that down to just two steps at the end. So you can see here on the screen I've got my vagrant boxes up. So I just need to run in and SSH into it. So if you run into that, if you're doing this at on your workstation at home in that directory just hit vagrant up and you'll get to to this stage right here. So to talk a little bit about how this works. You know, every operating system has two different release packages. So there's one that specifies sent us Linux one that specifies sent us stream. And then there's a set of repositories that the basically tell your system, you know, which how to grab the content for each of those things. And that's what we're going to swap up here. In order to get access to some of these, these repo packages, we're going to run this command, we're going to sudo dnf install sent us release stream. And that's just the this is the step that we're, you know, trying to eliminate in the future we're trying to get some some things in place so you don't have to do this but this will get you access to the repos packages. And so if you do that, in the world of live demos where you know this always takes longer than you than it did when you practice, you should come up with, you know, just one package that gets added here downloaded. Yes, we accept the keys. And we're good. So even the in the GitHub as well the the second and third steps are there, we need to run a DNF swap. And what that's going to do is it's going to take the, like I said the repos package that points your system at CentOS Linux swaps it out for a repos package that points you at sent us stream content. So that is sudo DNF swap. And again, it's going to do a little bit of magic here to find all of those packages. And then it's going to tell us that we're, you know swapping these things out and doing a little bit of a work behind the scenes to get the right sent us release packages in place. So if you do that, basically what we did was just dropped a whole bunch of young repositories and you can look and see what we did in at see young dot repos dot D. That's where this stuff lives and you can see the listing here. Those are all repo files pointing directly at the sent us stream repositories. We haven't quite yet migrated because we just told our system where to look. So the migration is the final step here. So sudo DNF distro sync. And that does a couple of things. It does a lot of dependency solving and things to make sure that you have the right versions of the packages as they exist in all of those repos that we looked at. And if you look at this, once we actually grab the metadata and do the solving, there's a whole bunch of packages that it's going to download. And so it looks like we have, you know, eight new package, eight new packages 184 packages to upgrade. And then once he hit yes, it's going to download all those. And yeah, especially, especially while this stuff is running, like Tomas said in the chat, feel free to ask questions, post them in the chat and we'll we'll handle those, especially while we're looking at a little bit of install time here. Ask a question in the meantime. So you said that you're trying to trim it to just two commands. So I'm assuming you are eliminating the first one. That's right. That's right. So that first command. Basically what that does is it gets you access to both sent us Linux repos and sent us stream repos. It tells you where to get get those in both locations. We're trying to ship those repo files repo packages a little bit differently so that you don't need that that first step there. You know, if you're following along waiting for, for that to show up, we'll definitely be announcing that on the sent us develop mailing lists, updating our documentation and all that stuff whenever we're ready to drop that down to two steps instead of three. So while this is running actually will maybe come back to this. Because I think this may take a little bit, a little bit more time to run. I'm sure it's if you're following along at home it's still running on your system to what I want to talk a little bit about some of the other the other ways that you can consume sent us stream in various environments because you know we had talked about doing it in containers. We got a little peek right here at the vagrant boxes because that's you know we are publishing them for sent us Linux but I want to talk a little bit about some of the cloud properties that you might want to use sent us stream in and the first one we can talk a little bit here about AWS and there's a page out on the wiki. You can check it out it's wiki.santos.org slash cloud slash AWS and again all of these links are in our our GitHub repo there. This describes a little bit about you know all of the Amazon machine images that we produce as part of our build and deliver process and there's you know a lot of good documentation in here. If you've got your own EC2 namespace configured setup you've got you know all of your private connections and our private clouds and all that stuff. You can actually pull this this in we automatically keep this page up to date whenever we see new machine images into AWS. And so if you scroll down a little bit on that page you'll see again this is a whole bunch of stream eight images seated into each of the Amazon regions and so like let's you know if you do most of your work in US East one then you have a machine ID attached to that that will will be best to spin up in that in that zone. And even on you know down towards the towards the bottom of the list you can even see we have some Eric 64. If you want to use some of the fancy AWS hardware. So let's go back and check on our vagrant install looks like it's still running, which is fine. The other thing that we that we also like to show off a little bit is all of these artifacts that we work with you know whether we're seeing them into AWS. Or you know if you come up across you know another cloud that you know maybe we haven't put images in ourself. We don't have official images you know posted to to Google Compute Engine or you know any of those places, but you do have the ability to go out and look at our. Sorry, this is the wrong. We'll get to the right place here. So cloud that sent us.org is where you can go to see if you can get other images for other places. And we publish these on a on a regular basis. They do have a little bit of a different life cycle than you know some of the composers they don't get generated every day, but but they do come out fairly frequently. The under the eight stream directory, you can see some of the ones that we publish, and we've got images for air 64 power PC and x86 64. And so we're going to drill down into this directory a little bit. And you know, hint for what's coming again, you can see we've got vagrant boxes for a few different versions here. This is this one right here. The send us stream EC2 image is the one that we're going to take a look at here in just a minute about spinning that up, you know directly in in AWS. That's the one that gets translated into each of those am is for each of the regions. So then there's this generic cloud image. And that's pretty useful for a couple of different uses. I actually use it sometimes on my workstation when I want to bring up a VM really quick. It's also really useful if, you know, you have a fairly standard cloud provider, you can, you know, try uploading this image, do your thing with cloud in it and, you know, a lot of times at all. It'll just work in your, your cloud namespace there. So cloud.centos.org is a good is a really good place to go and check out if you want to end up getting some images to deploy in other places. So what we're waiting a little bit more before we move on to AWS. Is anyone following along at home anyone else have their, their vagrant setup migrated yet looks like we're just about finished. So Brian, in the meantime, we got several questions. Yeah, and the first ones from Steven Gallagher and he's asking for people who are not working for redhead how they can contribute new features to stream eight or stream nine. That's, yeah, that's a really good question. So, and I think we'll get, we'll get into some details here in just a minute. So we know for sure. And this is, you know, talking a little bit about build processes and, and how we get things done in the, in the project. We know sent us stream eight, you can think of it built, you know, sort of, we call it inside out. And what we mean by that is, if you know how sent us stream works in relation to rel, it's meant to be a development location that represents content that's coming in a, you know, upcoming minor release of redhead enterprise Linux. So stream eight, it's, it's consumable, you can see it, you know, here in the artifacts that you have really, this is not the contribution workflow that we're, we're stuck with. This is not the contribution workflow that we're doing that we're looking at long term, because really we get source code, build it, and then, you know, outcomes the, these different artifacts that we have. And I'll talk a little bit about the things that you can do. You know, here in just a few minutes we'll, we'll go over what you can, you know, some of the things you can do with your, your fancy sent us to me machine that you have either migrated to or, or upgraded from. But, again, to the, to the point there, the intention is for sent us stream nine, the, all the package sources, and even, you know, if the Thomas you can chime in here a little bit about source kit but those are going to be directly contributable by the public. So the intention is you'll have there will be a names facing get lab point at the sent us stream repose or the sent us stream get repositories, you can make merge requests against those. And the role maintainers consider them and, you know, make sure it's it's right for the next minor release of redhead enterprise Linux. But that's a big shift. You know, both in terms of the work that we have to do to get the workflow up and running but also making rel development happen out in the public. And so that's a, that's a big deal about what we're looking for. I personally can't wait for like when we open the gates with get lab and everyone will be able to contribute, especially when all these repose will be set like hooked up with CI, so that whatever you contribute to we will run all the tests on your contributions to make sure that they are not breaking like the rest of the distribution or that the change is actually working is going to be super awesome. Yeah, and I think that the key point there that you you mentioned to is, it is really nice to treat tests, just like we do other code, because that's a that's a really good contribution point to some. Did we have other questions in. Oh, yeah, we have a lot of work is very active with the questions. So, I'll have to read his question, because it's really complex. So, on this is asking sent a stream is assumed to be a real eight dot x right and are the builds revealed in the sentence info or are those real RPMs directly. Yeah, that's that's a really great question actually. So, those are they're built from the same sources, but they are built in different infrastructure so it's not.  It is a two different builds and that's going to continue. You know, over industry nine, there's two separate build systems to separate compose systems, you know, they're separate that way, they do consume the same sources. So, you know, whether it's, you know, well first and then set a stream eight, or if it's sent a stream nine into rel nine in the future workflows separate build systems separate workflows. We can look at at one of those here real quick. So, co g dot inbox that sent us to work. This is our build system for sent us stream eight. And you can go out and sort of follow along about, you know what's coming through and look at the logs and and things like that. The, the rel build system is completely, you know, inside red hat and so it's not really necessarily consumable but that's what you can look at to follow along with sent us to me. And another question from honza is, if there is a way to see usage of sent to stream eight in comparison to sent to slinnux eight. Yeah, so the that's a that's a tricky question, especially because of the way that we actually deliver sent us stream and even sent us Linux and you know some of the previous releases. We've got a pretty complex mirror network, which means that anyone can go out and, you know, sync the content, put it on their mirror, and then make it available to, you know, 10s hundreds. So it's really hard to actually gather that sort of data I know there's, there's a little bit of work that that happened in recent versions of DNF that the Fedora project is using to help with, you know, some of that count, count metadata. But, you know, up up until this point we really haven't, like we don't keep that much in terms of logs on the mirror network and you know where you're actually downloading the content from so. Yeah, it's, it's a little bit hard to guess about about things like that. So, yeah, so we just finished up our, our vagrant install, and you can see here from the set house release file we've got set up stream eight, and we're all migrated. So, that is a great place to be let's take a look at AWS. So I'm going to copy in a snippet here and the snippet is in the notes on our GitHub repository, and then we'll talk through what's going on here. Maybe not that one. Got the wrong paste in here. Yeah. So I've got the, the AWS command line tools. And, you know, we just looked over at cloud.centus.org and saw the machine images that we did. And we looked at, if you remember we looked at this page right here that describes the AMI IDs. And we pulled the right one for the region that I'm working in. And it's really as simple as this, we're telling the AWS command line tools to use this image, give me one of them, a T2.micro sized instance and then I've got some extra variables that are set here in my environment to, to give my subnet ID, and we want to tell it to give us a public IP address. Simple as that. So once we run that, we've got a pending machine here. And I'm going to give you a peek into my AWS console. Let's reset this back to, it'll always take just a few minutes to spin up. So it looks like we might have another question while we're watching this on the screen. So, yeah, I was trying to answer it in chat in the meantime. So, the fourth question is from Richard Allway, and he's asking at which point we are removing the branding of Red Hat in the import process for stream or centers. Yeah, again, so this is going to be sort of a tale of two different workflows. So you've got the Stream 8 workflow and the Stream 9 workflow, and they're going to be, you know, just a little bit different. I'll talk a little bit about what we're doing for the Stream 8 workflow right now. And again, like I said, you know, builds happen in RHEL, we get the sources for them and then build, you know, then after that we build and send us Stream 8. And when I say build there, what I basically mean is we take the sources and if it's not already de-branded, we have some stuff that some packages that have rules that, you know, give you the commit that landed, the source code that landed in Red Hat Enterprise Linux, but then we layer on another commit that you make it a little bit easier for us to strip out branding and stuff like that. So, you know, there are some packages that do need a little bit of extra attention. And right now, folks on my team are handling that as they come in. So we just have a list of packages. One, you know, one really important one is Anaconda. We always put a few different patches in that that spec file and then build it for send us Stream 8. For send us Stream 9. And again, this is a sort of a preview of coming workflows. We're trying to get as much of that conditionalized as possible. So you could you have flags that you know if you're building in a sent us environment or if you're building in the Red Hat Enterprise Linux environment and I think there's a lot of work to be done on that side just to make sure that the branding flows in the right direction. I think there's there's always going to be some content that is, you know, never truly matched one to one between Red Hat Enterprise Linux and sent us stream on a on a branding level because we have things like our trademarks and logos and, you know, the index page if you visit Apache and all that stuff that's going to continue to be maintained, you know, separately from from the counterparts in in rel. So, yeah, back to EC2 I sort of stalled for a little bit because this always takes a little bit longer than you expect for machines to show up and be available. But so I've got a public IP address here. And the instance is running. So let's run back over here. And I'll give it my AWS SSH key. And you can look at sent us release we have sent us stream eight running in AWS. And then of course you can do all kinds of magic things with your own workflows and, and all of that stuff there's plenty to do here but the main thing that we wanted to show is it's super easy to get something running in EC2. And of course, anytime you do something with Amazon, you always want to make sure that you go back and terminate your instances because your credit card bill will thank you at the end of the month. So moving on a little bit. So we did. Let's see we've done container images. We talked a lot about the cloud images we talked about. So just on vagrant just a little bit. I want to show, you know, another thing if you don't want to go through that, that whole migration process, you know, even though it's three steps right now I think we can make it a little bit easier. So we've actually published a vagrant box for send us streaming directly. And we looked at that in cloud dot send us.org you saw the artifacts for that. There's a directory in our GitHub. Under vagrant send us stream. And it's a really, really simple vagrant file that, you know, it's basically the output of vagrant in it if you're familiar with that. So if we look at the, at the vagrant file here. This is the important part. We're looking at the sent us stream eight box and then I gave it a version of the most recent one that we just published but so if you do vagrant up in this directory, it's going to pull I already have this pulled but it'll pull that image. It does a pull through to that that exact thing that we looked at on cloud dot send us.org. And then it'll start one for you. So while we're waiting for this. And talk a little bit and focus on, you know, another thing that Tomachman mentioned I think we've seen it in a whole bunch of other places. If you have interesting hardware. Maybe something that's not x86 64. You know, if you have one of those fancy power workstations on your desk. Come talk to me because, you know, I'd like to say hi and all that stuff, but you've got options for all of this stuff to because over here in cloud dot send us. I need to go to up. If you have one of those fancy power workstations you can download and install download and use the generic cloud image, just with livered from from this location to same thing for air 64 same and air 64 even has, you know, as we saw, some things that you can spin up in the Amazon web services and all that stuff so definitely something to call attention to including the container images and that was a lot of fun to to sort of match what we had in terms of container manifests and stuff in quay makes it really nice to just be able to pull that for something on your architecture. Is this generic image be actually used to import to different clouds like Azure or GCP. Exactly. Yeah, so some, we know that some clouds require different different configs. And so, like I know Azure is one of them because you know they want you to have like a management agent or something on top of what already exists in other places in the distribution. There's so it's kind of we basically need some experts for each individual cloud to tell us what you know what needs to be on the image but the generic cloud images are a great start to getting there because a lot of in a lot of places they'll just, you know, boot and run. So, let's go back here and check on our vagrant install. Yeah, so this is our sent us stream image that has booted. And so you can include this in any of your projects, a vagrant file like this in any of your projects if you're wanting to target sent us stream. That's available to you as a box in and this is here's the page on vagrant cloud you can see the the versions that we have and then some suggestions about how to get this on your system to we do have both virtual box and live for providers available for each of these. So the the question now kind of becomes you've got all these options right you've got containers you've got cloud images you can we didn't even really touch on the the traditional installs you know like download a dbd and put it on a on a system somewhere but that's that that's completely available to you to make sure that stuff is out on the on the mirror network where you would normally find these things. So you've got this sent us stream machine installed or you've got a container image running. What can you do with it. You can do a lot of things like you can put it on your laptop I'm actually running stream aid on my laptop right here. I've been you know my daily driver since we we started the project. You can run a home server on it. You know I've got my file server on it that has like, I don't know, maybe two or three containers for random services that I use. You can use it to start playing with containers. Like Tomas mentioned earlier, one of the nice things is you get one of the nice things about stream is you get features a little bit faster than you might expect for sent us Linux. And so podman 3.0 being delivered in sent us stream right now. That's, that's a pretty cool thing and you know I've been playing around with it, you know ever since it. Composes there. But the main thing is install it, run it, put your workloads on it. But the, you know, kind of an illusion to, to I think Steven's question from earlier, look forward to being able to contribute in a meaningful way. We're starting pretty soon. We're, you know, Tomas and I are working together on some of those workflows and what that means for sent us stream nine. This is going to be a really important place to, you know, collaborate with people that are working on rel in a way that gets you features that are useful to you. We can propose patches, hang out with us on the mailing list. But even right now, if you head over to bugzilla. We're treating because of the relationship there between sent us stream and rel. We're evaluating bugs against the sent us stream version you can see that here it's there's actually a version against red hat enterprise Linux eight called sent us stream. We're evaluating bugs that come in under this version as if they were rel bugs. That doesn't mean necessarily that, you know, if you're asking for, you know, something new or, you know, pretty big or something like that, like, it's entirely possible that the maintainers may say no. Meaning this isn't really a good candidate for the next minor release of red hat enterprise Linux, but it's a conversation that you can have, and it's a whole lot easier to have that conversation here in sent us stream than it ever was in any of the previous sent us distribution so you can think of sent us Linux if you found a bug at point release day. It could have been another six month cycle before you know you even get an answer on a bug because the send us Linux was so disconnected from where development was happening for rel. And that's why that's why stream sits where it is that's why it's important to participate here but also important to use it. So, I think those are the demos that we have. Do we have other questions or anything else coming up. I think we have one more guys from computer kid whoever that is asks, is there any good reasons to use sent to a stream over something like fedora on a laptop. Yeah, so the, and I think it all depends on your kind of your point of view and your workload. Yeah, I'm pretty used to running enterprise Linux. And, you know fedora is is one of those things where it's a, you know, it's moving pretty fast, it gets a lot of features and, and that's that's actually a really good thing. I always ended up running enterprise Linux on my laptops because I've ran them on my servers and I've just matched them up together.  So I come from the world of academics are ran a bunch of stuff for a mathematics department and you know we loved running enterprise Linux on the desktop and on our laptops because that matched with our the software workloads that we were running there too. So it's a, it's a personal preference to be honest. But, you know, send us stream is definitely usable in a workstation environment. So I can try a different answer. I mean, I would love to run center stream on my laptop but my use case usually is I want to have the latest software possible, like I want to have the latest container run time or libraries. So I often ended up running federal Rohit on my laptops. And right now I even have multiple machines with Rohit and it's just because that's what I want. But yeah, I love to stress what Brian said that it really depends what you want to achieve and if you want stability, definitely go for stream and if you want latest greatest federal or even federal Rohit might be the answer.


Welcome to the Endnotes, where I put all the fun facts I can't fit into the main videos. Today, an extra bit of information from my video about the potato. And if you haven't seen that yet, click on the card. According to one story, probably apocryphal, the potato first made it to Britain when Sir Francis Drake bartered for potatoes in Chile on his circumnavigation of the globe from 1577 to 1580, bringing them the long way around across the Pacific and around Africa back to England. But it's unlikely they would have lasted such a long journey. Alternatively, he might have picked them up later in an act of potato piracy when he sacked Cartagena in 1586. Another story is that the potato was brought to England by Sir Walter Raleigh from the Caribbean in 1588 or from the settlement at Roanoke Island, though potatoes weren't grown there at the time, or that Raleigh got them from Drake. In any case, the story goes that Raleigh had the gardener at his Irish estate plant them, but when his cook served the toxic berries at dinner, he had them all pulled up and disposed of. But his poor Irish tenants rescued the sustaining tubers from the trash. A more likely route from Spain to Ireland was in the ship's stores of Basque fishermen, who on their way home from fishing the Grand Banks off Newfoundland would stop off in Ireland to dry their catch. In any case, the potato certainly became a crucial staple crop of Ireland. This of course led to a boom in the Irish population, but therefore great poverty with growing population and no employment. The failure of English plans for grain farming in Ireland had led instead to commercial beef grazing, which made English landowners wealthy but left little for the Irish people. And when the potato blight hit Ireland in 1845, a great famine ensued, and the country was further depopulated by a great diaspora of the Irish around the world, many of whom would go on to work in the factories. As always, you can hear even more etymology and history, as well as interviews with a wide range of fascinating people on the Endless Knot podcast, available on all the major podcast platforms, as well as on our other YouTube channel. Thanks for watching!


I remind members, by way of preemption, that if the amendment in the name of Kevin Stewart is agreed to, the amendment in the name of Jackie Baillie will fall. The question is that amendment 6523.3 in the name of Kevin Stewart, which seeks to amend motion 6523 in the name of Craig Hoy, on national care service viability, be agreed. Members should cast their votes now. The vote is now closed. Thank you. The result of the vote on amendment 6523.3 in the name of Kevin Stewart is yes, 62, no, 49. There were no abstentions. The amendment is therefore agreed. The next question is that motion 6523 in the name of Craig Hoy, as amended on national care service viability, be agreed. Are we all agreed? Yes. Are we all agreed? Yes. We are not agreed, and therefore we will move to a vote, and members should cast their votes now. The vote is now closed. Point of order, Shirley-Anne Somerville. My app appears to have frozen, so I would have voted yes. Point of order. Perhaps deal with Ms Somerville's point. I thank Shirley-Anne Somerville for her point of order, and the record will be corrected. Point of order, Mary Gougeon. I had exactly the same problem as Shirley-Anne Somerville on my page when it connect. I would have voted yes. Thank you, Ms Gougeon, and your vote will be recorded. My vote was recorded. I would have voted yes. I understand, Mr Stewart, that your vote was indeed recorded. I call Stephanie Callaghan, who is online, for a point of order. Thank you, Presiding Officer. I had voted no and tried to change it to yes, but my screen froze, so I should have voted yes. Thank you, Ms Callaghan, but you can't actually change your vote in those circumstances. The result of the vote in motion 6523 in the name of Craig Hoy, as amended, is yes 61, no 50. There were no abstentions, and the motion as amended is therefore agreed. The next question is that amendment 6520.2, in the name of Jenny Gilruth, which seeks to amend motion 6520 in the name of Graham Simpson, on essential road improvements, be agreed. Are we all agreed? Yes. The Parliament is not agreed, and therefore we will move to a vote, and members should cast their votes now. The vote is now closed. Thank you. The result of the vote on amendment 6520.2, in the name of Jenny Gilruth, is yes 62, no 47. There were two abstentions, and the amendment is therefore agreed. The next question is that amendment 6520.1, in the name of Neil Bibby, which seeks to amend motion 6520 in the name of Graham Simpson, on essential road improvements, be agreed. Are we all agreed? Yes. The Parliament is not agreed, and therefore we will move to a vote, and members should cast their votes now. The vote is now closed. The result of the vote on amendment 6520.1, in the name of Neil Bibby, is yes 49, no 61. There were no abstentions, and the amendment is therefore not agreed. The next question is that motion 6520, in the name of Graham Simpson, as amended, on essential road improvements, be agreed. Are we all agreed? Yes. The Parliament is not agreed, and therefore we will move to a vote, and members should cast their votes now. The vote is now closed. I do not know what is happening with the app this afternoon, but I would have voted yes. The result of the vote on motion 6520, in the name of Graham Simpson, as amended, is yes 82, no 28. There were no abstentions, and the motion, as amended, is therefore agreed. I propose to ask a single question on two parliamentary bureau motions. Does any member object? The final question is that motions 6564, on approval of an SSI, and 6565, on designation of lead committee, be agreed. Are we all agreed? We are all agreed, and the motions are therefore agreed to. That concludes decision time, and we will now move on to members' business, and therefore I would ask those members who are leaving the chamber to do so quietly and quickly.


How's everyone doing today? Okay, so today I'm going to talk about how tech has been changing in government. Okay, so how often do you interact with government? When I say government, I mean your government. It could be local, it could be state, it could be federal in one year. So for folks who do it twice a year, raise your hands. Okay, got a couple. For folks who do it once a year, doing something with government. Okay, got a couple, couple more. And zero. Okay, a few who are zero. Do you guys file taxes? So in the past, I'm missing my notes. In the past 12 months this is on average how many people have signed into federal government websites. I ask the taxes question because most folks are only interacting with government to do their taxes. However, there are, at the time of the creation of the slide, there were for the U.S. federal government 161,495 people at one point on U.S. government websites with 1.4 billion users for every 90 days. There's three of you in this room right now. I'm just kidding. You can find this information on analytics.usa.gov. And you can dig into where people are, how people are using government websites on the federal level. So things are happening. A lot of things are happening on the state, on the local, on the national and international governments. There is, on the local level, a lot of the initiatives include Code for America, which was spoken about at PyCon. There's the creation of CIO and CDO positions, CIO being Chief Innovation Officer, not Information Officer, and Chief Data Officer positions at various cities like Detroit, LA, New York. So why am I talking to you today? Because I'm on a mission. I get really, really excited about this. I'm on a mission to get folks involved in public service and to understand this area better. Passionate public servants are the cornerstone of government. If you are not excited to be a part of helping out your government and the things that you can do by the end of this talk, at least you will know two things. One, how Django is used in government, and two, some of the resources that you can find coming out of government in the open source world. So let's talk about government. So who am I? So I've done a lot of stuff in the Django and Python community. But since I'm here in my official capacity today, I will talk about my professional self a little bit more. I'm a former journalist. That's how I came to Django. I worked at the Washington Post where Adrian Halavati worked and inherited some of his code when it was pre-1.0. And I started in journalism because of the civic mission, the idea of empowering people, and empowering citizens to be able to make decisions. And currently I work at 18F, which I'll talk about later, which is a part of the federal government. To me, it's the same mission. It's the ability to empower people to make good decisions and to be able to offer them and get them the services that they need. But 18F is just one part of the story. But first of all, who are you? Oh, that doesn't seem to be showing up well. Okay. Well, this is a map of DjangoCon attendees. Oh, there we go. I did that on purpose. The DjangoCon organizers were nice enough to let me use this from their invites because I wanted to know who I was talking to. And while my talk is mostly what's happening on the public sector in the U.S. federal government, it's important to know that this movement's happening all across the world. Every government entity has one thing in common, how to best serve their people. Governments around the world are exchanging ideas. Each sovereignty is also made of a unique set of beliefs to say that my cultural beliefs in the U.S. are different from other cultural beliefs in other countries and also regionally. Some things translate from culture to culture while others do not. Varying views on privacy, for example, and trust. What do you trust your government to do? What do you trust your government not to do? Varying structures of operation within the government has had an effect on the approaches that various governments and entities have taken. Centralized government offices versus independent government offices. So through the U.S. example, I hope you learned something today on the impact that you can make on your country, on your municipality, and to make it a better place for the people who are like you. In all, even in the private sector, we still have this mission. How do we best serve the people? The people being our customers. And as I said, this is happening all around the world.  You will see a huge amount of countries located internationally. I can't talk about every one of them today, so I will highlight one. It's kind of considered the leader in the international realm, which is gov.uk. They launched in February 2012, and they're sort of considered one of the leading examples in government digital services. So I'm going to rewind a little bit and start telling you what's happening on the federal side of the U.S. So the Library of Congress. The Library of Congress was before the launch of gov.uk. And specifically, Jango's used in the Library of Congress's repository development center, including Jango, Python, Solar, Golang, Redis. Projects include one of them is called Chronicling America, which you can easily Google. It's an old newspaper archive. That's a project that I had worked on after leaving journalism. Another project that uses Jango is eDeposit, electronic deposit. It is the electronic intake of content into the Library of Congress. Before this point in time, people would literally walk up to the Library of Congress with hard drives or mail-in hard drives. And still to this day, some folks are doing that depending on the content, depending on the size of the content. But this was the foundation to allow people to fire electronically for copyright and then get it classified in the Library of Congress. And then next is the World Digital Library. The World Digital Library has the Library of Congress. Some of you might know one of the major developers on this, which is Chris Adams. He's a longtime member of the Python and Jango community. And he seems to contribute under the radar to a lot of things, but yet I couldn't find one specific thing that was like his wheelhouse. But he's actually been a mentor of mine. He's super awesome. Another one that has been a leader has been the Consumer Financial Protection Bureau. If you've never heard of this, you should know about it. They're great. They were created on July 21, 2011 as a legislative response to the financial crisis of 2007, 2008, and the subsequent Great Recession. They handle consumer protection in the financial sector. Jurisdictions include banks, credit union security firms, payday lenders, mortgage service operations, and foreclosed relief debt collectors, etc. While the Library of Congress's Repository Development Center existed before CFPB, CFPB was an interesting use case because it was a greenfield project. It was an agency where an agency didn't exist before, which doesn't happen very often. And so they were able to really push the bar forward on what's happening in government. This is a great app. It's built in Jango. You can find it on CFPB's GitHub repo, owning a home API. Basically, you can look up unbiased interest rates for your geographical area. I have to say, while I was making these slides, I went and I had some links from CFPB and I went back. And when I saw this, I immediately sent it to like three friends who are trying to buy a house right now, including my mom who's trying to refinance. And I thought it was fabulous. So it's not necessarily you're getting your interest rates from a private entity where you don't know what's happening in the background with respect to advertising dollars. So it can give you a good baseline for what your expectations should be. Another project is eRegulations. Eregs make, this project makes regulations easier to read and digest and easier to navigate. The title matches the section of the URL updates as well. So you can send direct URLs to a specific section of the regulation, which, as you can imagine, is CFPB comes out and is trying to regulate some of the financial markets or some of the things that are happening and protect consumers. This is a great way for people to share information. And so you can see how like the title updates. Honestly, this is eye candy. I was really excited about the slide moving. Yeah. So President Obama said, we must harness new ideas and technology to remake government. This was on January 21st, 2013. As part of this, he launched the Presidential Innovation Fellows, which was where I went after the Library of Congress. It was established in 2012. The photo above is the first round of fellows. And the purpose of the Presidential Innovation Fellows is to bring innovation economy into government. This is the reference to some of the private sector stuff, by pairing talented diverse technologists and innovators with top civil servants and change makers within the federal government to tackle some of our nation's biggest challenges. So some of the projects that have been worked on are the Blue Button Initiative. I was really excited when I saw this from my doctor. You can now download your own health records and share them electronically. That's through the Blue Button Initiative. It increases accessibility to electronic health records. The Green Button Connect reduces waste and shrinks bills by providing consumers information on what their power usage is and where it's coming from. Notalone.gov is actually a very interesting case. Notalone.gov was a White House initiative built in less than 30 days. And it was to improve the transparency and information sharing of sexual assault prevention and enforcement data for students in schools. And as you'll know, I skipped over GOQ because that was my project. So during my fellowship, I worked on a project called GOQ, which is an open source disaster. Well, it's an open source mapping tool where you can do mapping workflows. But it was used in this context and created in this context for disaster response and recovery. It crowdsources geotag photos to coordinate response. The original idea came to increase the speed of damage assessments. When Hurricane Sandy hit, it took, it takes multiple effort from multiple folks and multiple jurisdictions to be able to assess the amount of damage on a house. At the same time, people are sleeping on cots and don't have a home. But they needed people to physically go to the house using imagery from public, from social media and using imagery from the Civil Air Patrol who does flyovers. After disaster, we could start to identify properties that were in such decrepit condition that we can then issue money to be able to get people on their feet faster and back to their life. This project also led the National Geospatial Intelligence Agency to join GitHub, which is really exciting because it paved the way for intelligent community entities to be able to post-repost publicly. So, this is really exciting to me. The changing landscape is saving lives and saving money. And Django is behind a lot of the work that's happening. On August 17, 2015, which was just a couple days ago, the President signed an executive order which made the Presidential Innovation Fellows a permanent entity within the government. Now, 18F, which is where I work. 18F came after the Presidential Innovation Fellows. 18F was launched on March 14, 2014. It's a digital consultancy for the U.S. government inside the U.S. government. What does that mean? We are a sub-component of an agency called the General Services Administration. And as such, we work with other agencies and help empower them with digital services. Currently, we're working with more than a dozen agencies to help them deliver on their missions in user-centered, agile, open, and a data-driven way. We ship code, practices, and culture, so code. We are open by default. You can find all of our code here. And there are so many repos that it's hard to find repos. So if you are looking for something specific, please let me know or I will answer the question afterwards. But one of the great things about being open by default, basically, you can see I'm working on a project. If you were to go to my GitHub history, I published it a couple of days ago. And it's a really dirty prototype for a data API using Django. So yeah, people are not scared about sort of throwing things out there. If anything is not public, there needs to be a reason why. And then it's published that it's specifically not public. So one of the coolest projects in my opinion is an open FEC. FEC data was hard to ... FEC is the Federal Election Commission, and they handle federal financial data for elections. And having this API allows the American people to better understand what's going on with elections and how they work by browsing reports, document data, individual donations who's donating to whom, granular spending data. It was launched actually in July 2015. It was not built in Django, but it was built in Flask. So who here has a fourth grader? I'm really excited about this. Fourth graders. Yes. Oh, but you don't live in the US, do you? Oh, that's kind of ... I'm sorry. I was excited about it until that. Well, Every Kid in the Park was launched in September 2015. This was built in Django. So it just launched. It was really exciting. Every Kid in the Park gives US fourth graders free access to all federal lands and water, including national parks, forests, wildlife refuges, and marine sanctuaries for a full year. These and friends can go for free as well. So I need to find a fourth grader. If you have a fourth grader, if we can talk afterwards. So it's at everykidinapark.gov. These are some students from Samuel W. Tucker Elementary School, which received Every Kid in the Park pass. And as I said, it was built in Django. One interesting thing about this project was the special thought to be put into the audience. The audience being fourth graders. So the text was written for fourth graders. Fourth graders are too young to be on Facebook. So things like linking off to Facebook wasn't an option. It was really vetted and thoughtfully made to make sure that it was audience-appropriate to get kids involved in the national parks. So I said, code, here's practices. Some examples of practices are 18F guides. The link was a little bit long, so I created a bit.ly link, bit.ly 18F guides. Including there, you can find various guides on various topics. The one I'm most excited about is accessibility. We have sort of working groups. And I was one of the members of the accessibility working group, the idea of making websites accessible to everyone. Analytics, agile practices, APIs. Some of them you might not need, but there are some great resources in there that you can refer to. Automated testing cookbook, automated testing playbook, content design methods, fun end group lists, which is how we sort of spin up group lists, which is sort of how we spin up sort of working groups to get things like this done, which aren't direct projects like Every Kid in the Park. And then how we handle open source. And if you would like to make suggestions or updates, you can with a pull request or submit a ticket and we can address that for you. So practices, teaching agile using Legos. This is really exciting if I haven't said that enough. So while the guides are open-ended, we also do formal teachings as part of the work we do. For example, 18F consultant Zach Cohen led a workshop to teach the importance of agile methodologies to folks who weren't used to practicing agile methodologies. The story he gave to folks was, as an office worker, I want a laptop stand, so I have more desk space. And the task was to build a laptop stand out of Legos. It teaches, it taught these people to communicate early, communicate often, and communicate continuously. So you have a laptop stand that's built as opposed to a whole desk. Culture, another, because it's hard to, the link's a little bit long. I made a bit late link, 18F, COC for code of conduct example. This is, very exciting. We actually have a code of conduct. From my knowledge, this is the first code of conduct. Not just legal requirements, but first code of conduct within the federal government. It was inspired by 10 different multiple code of conducts and legal requirements. From bridge foundry, open hatch, the Python community, PyLadies, AIDA initiative, and more. If you have any opinions or suggestions, please feel free to submit. We want people to participate. And last but not least, the United States Digital Services. It was founded a little bit after 18F. It was founded on August 11th, 2014. And it is a part of the White House's Office of Management and Budget. The mission is to improve and simplify digital experience that people and businesses have with their government. So one of the things that they're working on is improving services for Americans, veterans. USDS stood up a team at the VA and to create a simple and easy to navigate VA website. Also, to improve the benefits claims experience for veterans. USDS is working towards a more efficient and effective VA that delivers for America's veterans. And as some of you might know, Alex Gaynor, he was recruited for this effort. So Alex Gaynor is now living in DC, he moved. And is working at the Veterans Administration. And interestingly enough, I didn't know this when he was hired. And we had a meet and greet for the new team at the Veterans Administration and Root Beer Floats. And I turn around and Alex Gaynor is standing there. And I was like, what are you doing here? You live in DC now? And he goes, hi, I'm part of the new team. So that's how I found it, Alex was in DC. And I'm really excited that he joined the government. Another thing that has been created is the USDS Playbook, which is found at playbook.co.gov. This creates a set of plays for CIOs, more on the business side, to be able to understand things that need to happen in a very high level way. Things like default by open, understand what the people need, understand the whole experience from start to finish, make things simple and intuitive, build the service using agile and iterative practices, bring in experienced teams, choose a modern technology stack, deploy in a flexible hosting environment, automate testing and deployments, manage security and privacy through reusable processes, use data to drive decisions. A lot of these are things that we take, that some of us might take for granted. As yeah, of course, these are things that you're supposed to do. But this sort of gives, these plays give CIOs in government, a guiding force by which to make decisions that follow modern technology stacks and methodologies. And sometimes it takes a village. This is really exciting. This was a partnership between 18F and USDS. And what, I'm gonna get all government now. White House OMB memorandum M1513. A policy to require secure connections across federal websites and web services was signed in June 2015. What is that? Creating, making HTTP only standard in the federal government. And pushing, making sure all federal agencies move in that way. Why is this exciting? Because people like you helped make this possible and to create this policy to say that this should be a thing that we do. And so therefore making the recommendations to make it an official thing with policy makers. So this image is an image of the 18F team. In a very accurate map of the United States, we run out of room. So we talked about 18F and USDS, the VA, CFPB. Our folks in a lot of these agencies are remote teams spread across the country. Folks who've joined us from the Python community include Christine from LA, one of the founders of PyLadies. Kathleen Devlin from Dayton who runs PyOhio and Julia Elman in Raleigh. Which is very close to Austin in our very accurate map. Known for PyLadies and Girl Development. And then of course a couple of the presidential innovation fellows have joined. Also folks active in non-Python communities such as Sarah Allen, who's the founder of Railsbridge, she's located in San Francisco. And we come from folks who've joined come from a wide variety of backgrounds. This is an image of the backgrounds from the 2014 presidential innovation fellows. Having a folks from a wide variety of backgrounds is important. We talk about diversity and diversity at work in many different ways. And why is this important? Because we are representing a large constituency of folks for the people by the people. This applies to everyone in every sector, whatever people you are serving. You cannot truly advocate for the users of your systems that you create if you do not represent the users. Our audience is America and everyone in America. Now last night, I don't know 1 a.m. or so, I got a video in my email box from Todd Park for you guys, very exciting. He basically created on an iPhone. And he asked me what time my talk was. And I was like, well, it's 9 a.m. Central. And I said, you know, if it doesn't work out, that's okay. But this guy stayed up making this video for you guys on his iPhone. And he is technical advisor to the White House and the former second CTO of the United States. Now, this is where it gets tricky. If you're watching this video, I'm going to suggest a list of my good friends, Jackie DeSiebel, a personal hero of mine, who talked about the short movement to build homelessness among our nation's veterans, helping to secure the future of our students, helping to improve disaster recovery response across the country, and much, much, much more. It's a movement powered by amazing people like Jack, deeply gifted, developer, designers, data scientists, and product managers, with tremendous skills and hearts the size of each other. And it's a movement that needs you. If you're a skilled developer or inside digital services, please consider serving our country, be one of the growing number of families we introduce, as a presidential innovation program, or by doing a tour of duty as a member of ATF, or at the U.S. Digital Service. Our country needs you. Together, we the people can build a better government for the American people. Thanks so much for your consideration and take the best of care. So yeah, so I've told you a lot about the work that's been happening. I told you, you can find work that's happening outside the U.S. Like I said, there's a lot of coordination between, there's a lot of coordination between various countries. We've, I've personally chatted with folks who work on the UK side. There's folks in Indonesia. There's folks in Australia that we've coordinated with. But it's not just at the federal level. It's also at the local level, your local community. And empowering the local citizens to be able to make decisions. So if you're interested more in local stuff, I encourage you to go back to the Picon Talk by Catherine Bracey to learn a little bit more about efforts like Code for America. But yeah, there's a lot of work to do on all levels. So I hope that after you leave today, you will start to get involved. If not, obviously not everyone can just pick up and leave their job. At least not as a side effort, because we need, we need help. We need lots and lots of help. There's lots of work to do. There are over, there are about 100 federal agencies. And I just told you about a handful. This is not to say there aren't efforts happening at other agencies. But this is not to say that there aren't efforts happening at other agencies. But there's just a lot of work in every corner. And whatever your interest is in the local or federal government, please come and talk to me. And I will tell you about various opportunities, whether you're interested in financial, whether you're interested in data. For example, census, whether you're interested in helping veterans or cultural institutions, either in your country or in ours. Thank you. Thank you, Jackie, for an excellent talk. We do have time for questions. I'm going to kick off with one myself. There's clearly lots of things that AT&F could be involved with. Do you reach out to agencies? Or do you wait for them to come to you for help? Yes. So it's definitely a combination. We have something called a project intake meeting, where we discuss sort of some of the emails that have come in and we review them. AT&F is run off of agreements with other agencies, which are called interagency agreements. And within those agreements, we write in stuff like agile, we write in stuff like open source by default and have a 30 day exit clause. So if the relationship doesn't work out, we have a way to exercise it. But we've never had a situation where we had to exercise it. We've always been sort of able to get through things together. Hi. Seeing your GOQ project was thrilling to me. I'd just like to say that I'm from New York. And seeing a lot of the tech community's response to Sandy was pretty vapid. Let's hack the storm. And a lot of things came out of that that didn't end up helping people. So it was a real thrill to see what you did. And thank you for that. My question is, how did you do qualitative analysis on the photos? So to say these photos were taken and so there's more damage here than there is over here? Sure. So while I was working on that project specifically, we hadn't got up to that point in the process. So I can't really speak to it. However, if you want to see me afterwards, I can provide you contact information to the folks that are currently working on it. Or you can file a GitHub ticket in their repo since it's open. And I can point you to that. And they can answer your question. OK, thank you. Hi, Jackie. I'm Carol. You know that. Where the corner where Cara was in San Diego just at the very bottom. And I'm wondering, I found out about the 18F guides from Julia back in February. And they are outstanding. I highly, highly recommend everybody take a look at it. I'm kind of thinking off the cuff at the moment. But now that we have Pilates remote, maybe it would be nice to do a series on the guides that relate like a specific guide like accessibility with a topic on actual development. Like asynchronous teams and remote work? Yeah, well. Specific or? Yeah, or like San Diego, we have a lot of veterans that come back. And we have at the FabLab grants for reentry. I wonder if there's a way beyond just Code for America to engage people within those communities that the projects serve to actually contribute. Sure. I think the closest thing I have seen to that is the local offices of Code for America, which is like Code for DC, Code for San Francisco, Code for Los Angeles, and then internationally, Code for All. And when you go to those, so Code for America itself has the fellowship program. It's a more structured program. When you go to the local ones, you walk in and you say, I'm going to work on this project. Who wants to help me? And you can use that as your umbrella to reach out to people. So is that the same or different than Code for America? I believe it's under the umbrella of Code for America. For example, Code for America has a summit every year. And all the brigade captains from the cities go to the summit as default. So it's like one big happy family. Got it. Thank you. Yeah, no problem. So if there are any more questions, let's thank Jackie again for a great talk. Thank you.


Obesity is associated with low-grade inflammation, triggered in adipose tissue, which may occur due to an excessive SFA from the diet that can be recognized by toll-like receptor 4. This condition is involved in the development of components of the metabolic syndrome associated with obesity, especially insulin resistance. This article was authored by Fabian Valentini Frances Quetti, Andre Ferreira Nascimento, Igor Otavio Minitel, and others.


God's beauty is all around us and my goal as an artist is to capture and interpret that beauty on canvas and to take you the viewer along with me on this painting journey. And welcome to Painting Journeys. My name is Kitty Lynn Klisch and we'll be journeying across the canvas today. I'm going to take you to a new location but first of all I want to talk about the painting where we were on our last episode. Last episode we were in the foothills of the Grand Teton. And if you remember the painting from the last show it was a little different. I think I had the cabin up a little higher and not quite as much color. You know I went in in my home studio and I did a little rearranging with the composition. I wasn't real happy with the cabin where it was. I wanted to bring it down here and then of course I wanted to echo all this marvelous light that we're seeing up here. I wanted to echo it down there. It makes it just pop in that corner right there. So this is the lost cabin in the foothills of the Teton's in Wyoming. And so now today we're going to go north, travel north, and we're going to go into Yellowstone. And I remember as a kid when I was growing up in school we learned a lot about Yellowstone Park and Old Faithful. And I was fascinated with Old Faithful. I always wanted to go there. Well I finally made it and it wasn't quite exactly what I thought it would be like but it was enchanting. It really was. So I'm going to start painting and then I'll tell you more about the journey as I'm painting. Thank you. First of all though I better get some colors mixed up here. I want to dive right into that luscious sky. Get all those darks in before I put the lights on. We've got some really strong value changes in this. You have you know like a really dark value going through here and sort of a medium value here and this is sort of a medium to a darker value. And then of course this is very light. It's almost like a four-value photograph that I'm working from. And of course we don't want it to look like a photograph. We want it to look like a painting but I want to dive into that sky. It's just oh it's so fascinating to me. I don't know if the camera picks it up or not but there's actually pinks and purples in these clouds back here and the camera may not be able to pick it up but I'll bet you my brush does. So here we go. I'm just working with my regular palette that I usually work with. I think I've even eliminated a few colors today. I added one new one. I added brown matter. I was dinking around in my home studio and I used picked up a little bit of brown matter and used it. I wanted to try it and I really liked it. And so I put a little bit on the palette today. We'll see if we can use it anywhere in there. I'm making a nice grade blue. This is what takes the time is mixing the paints. I wonder can you hear the knife scratching against the palette? I can. I put out two globs of white. I thought I'd be on the safe side today instead of having all my white and one pile on my palette. I put out two globs because I thought well I want to keep one cleaner. Okay now that looks a little too blue according to what I'm seeing here. I'm going to add just a wee bit of green to that. Warm up that blue so that it's not so cold. And then of course the green being the complement of the violet and the clouds. That will make it even more dramatic and beautiful. Here we go. Let's see here. Oh yeah. I think we nailed it kiddo. All right here we go. And then we'll put some more darks. We need to mix up a few more darks here. I want to have a lot of colors to prepare and ready to just dip into. So bear with me while I go through this process. I had always always wanted to travel to Yellowstone. When we finally got there we were actually on a trip from here in Wisconsin where I live all the way to the west coast to Washington state. And as a special treat we stopped at Yellowstone on the way and it was really the park. I don't know if you have been there. I know many of you have but those of you that haven't the park is very diverse. As you go through the park you'll you'll hit areas that are almost barren and it's quite large. I think the park covers goes into three different states. I think it's Idaho and Wyoming and another state. I'm not sure. I can't think right now. But anyway it it's very large and you have your mountains and of course they're very wooded and then you have these areas that are like plains that are flat and sage-like almost like like you would think more desert-like more like high desert. The wildlife was was quite abundant. We did get to see the big elk and I'm gonna scrape that down. I don't like where that's going so we'll just scrape that off and we'll put a little bit of pink in there a little bit of violet. This is what we want. Now we can start coming down with the dark. This as it comes down has to be quite a bit darker right in here so that we can see the the smoke from the volcano. It's listening to something on I think it was PBS the other day about volcanoes. It said that believe it or not that the biggest volcano we have in the United States is old faithful and they don't really know when it's really ever going to to really go off. That's really something it's kind of in a way it's kind of a little scary. Let's get some blue in here. We have some blue in here and there's a little blue in there. This is a little darker down in here. It was very when we saw the volcano when we saw old faithful can't say rub but blow I guess you'd call it. I had always been under the impression that it was like clockwork you know I don't know where I heard that but I was in the impression that every you know hour or every so many minutes that it went off like clockwork. Well that's not the way it is. They put a sign up and there's all these chairs that are sitting around quite a ways away and you it'll tell you like you know the next time it's going to blow it will be like at 5 20 or something that's what time it happened to be when we were there and we waited for oh I guess almost until 6 o'clock and then and it was getting quite dark in the sky I think there was a storm coming it finally went and it starts out with little little bubbles little tiny bubbles that kind of pop up it's like something boiling on the stove pot of rice boiling on the stove and it just pops and pops and pretty soon it gets larger and larger and the steam starts to roll out and it I think right now in this photograph that I have of it I think it's at it's about as high it goes up what do they say that well the the the I believe the the steam itself actually goes up to about 50 feet or further it's not a good place to be too close to as we as we traveled to the park through the park we saw a lot of other areas that were really I thought were prettier than where old faithful was located you know where the the lakes and I think my favorite area was the Yellowstone Grand Canyon or the Grand Canyon of Yellowstone I thought that was really beautiful it's just like the Yellowstone or it's just like the Grand Canyon in Arizona it's just a beautiful beautiful deep deep canyon with a large waterfalls and smaller waterfalls and all these vantage points to see these places I'm leaving this clean because I want that for my for my white smoke or steam I guess it's really steam not smoke one of this really light back here so that you can see the distance under here I'll come back and do a little futzing with that later right now I'm just trying to lay in them the colors that I see there's this beautiful turquoise in the sky that I'm having a little trouble getting but I'll get it I'll just keep working it until I do right in here there it is we've got some clouds there this appears to me to be need to be a little bit lighter once again I'm working with these bristle brushes I don't know kids I'm still not sold on them they are just so scratchy this is a lot of white in here I think I'll go ahead and get the dark on and for right now I'm just going to mix up a really dark value I'm not going to worry about any detail we'll wait for the detail till we get closer to the you know till we get the whole canvas covered so right now we're I'm just going to put this really dark dark green sort of I'm making a black sort of a green to put in that those trees back there and I'm going to push that up in order to have more of a feeling of forest and trees you know a lot of times the brush stroke will will actually define the subject matter better than anything else you just paint it with the brush stroke going the right way at least that's what I like to do see if I really don't have to fuss with this much it already looks like trees and stuff and then this over here and that's far away so we'll let that edge be real soft and I soften up those edges in the background just by taking and dragging the the sky over the edge and that's that softens it and makes it go back into the distance it's not really that close and then I can always come back in and if I want to and refine it just a little bit more but that looks a little better a little further away I really like soft edges and paint and paintings soft to go with the you know you have the hard edges and then you also have to have the soft edges so anyway what's really interesting in this in this waiting for old faithful to blow is the different people that are sitting there I happen to be sitting near a group that were wagering on when it was going to happen and I guess this one person was quite adept at telling just when it was going to they they could tell by the amount of steam or bubbles or whatever I didn't want to do that see that's a nice thing about painting in oil you don't want to do it you don't like it just take it off I see that little bit of stuff over there I'll go back and darken that a little bit but okay now this is coming down here and then I'm gonna go to a different brush and I'm going to paint the this ground area that I see I see this light edge and then this needs to be kind of softened into that it's kind of a light edge there is coming and it comes up in here and then it goes down this is this is almost like a shale it's sandy rocky I don't know quite how to express it it's I'm not it's not the most attractive stuff in the world let me just tell you that but we'll see what we can do with paint to make it look attractive because like I said but it isn't really about making this a look like the photograph it's this is supposed to be our our impression of this right now that light sort of rocky the only thing I can think of the only word I can think of is shale seems greater than that kitty let's see here I'm working very hard trying to get the the right colors in here for you but that is going across there now here is a little darker this is a little darker and it's coming up here and kind of coming down that's even darker yet this is where it's kind of sits in the land sort of comes together and all different points here that's another thing that makes this kind of an interesting thing to paint because you have all these directions going different different ways and it helps to make it a little more more interesting here this is a little darker right in here okay and then yeah this is darker coming down here and then over in here we have a little bit of that brownish coming down and we have the white shale over here that's quite white coming in to here on the bottom you have almost just has a little tiny bit of a pinkish look in here where those where it's first starting to come up see now this right here we go okay this is fun isn't it yeah brings back some really good memories memories of relaxed times you know you just kind of get all caught up rushing through life and you forget what vacation is like to just amble along and see the different things marvel and their beauty dream about being back in your studio so that you can paint them and nice vacations are nice traveling is nice traveling on canvas is nice like I do all right here we've got all these little patches of lights and I want to just kind of get that filled in sandy colors you can already tell that this is gonna be much much brighter than what the photograph is but that's okay that's what paints for and there's some little darks in here and get a beautiful green color when you mix your paint gray with the yellow ochre I want some red in here and then this down in here I'm seeing a little alizarin crimson I'm probably gonna knock all this down a little bit but just for now I just want to have it have it on there then I can tone it down and do what I want to do I see a little group of green things in there this looks a little green in here there's a little green right in right in here and there's more light and some orange I think I started to tell you about those painted I think I can't remember if it was that called the paint pots or just what but it was this real strange surreal area that was cordoned off and you and you walked around it you couldn't go into it and was all these pools of the and they were bubbling you know just like like I was saying like the rice kind of simmering and bubbling up and popping and they were doing this and but they were different colors it was was very interesting very I don't know it's kind of like if you couldn't imagine feeling like you're on another planet that's the way it was it was just so different the people you know most most of the people that were walking around it you could tell that they were really quite awestruck at this natural phenomenon that they were seeing I heard on the news not too long ago that there was a really serious fire in Yellowstone and I truly hope it didn't do too much damage because we have a lot of fires now going on in the in the West like that that's that's pretty I think at least I think it's pretty it's colorful like that bring this down a little bit more I think we need I know you're waiting for me to get to the actual steam huh that great big bundle of steam let's see here that's lighter back there you want this it to stay lighter and go take the green and oh no it's a little more violet there we go yeah that's what we wanted okay I think I'm going to darken if I go to my lightest lights I think I'm going to darken this area over here on the bottom there we go and then there you can see just a little touch of that and in there and I'm going to take a paper towel soften that down a little bit so that it it doesn't pick up too much of the green and now I'm going to start coming in here and get back with that blue brush first of all I think I'll take I think I'll work this a little bit and soften it a little just kind of soften and move with the with the clouds it just seems to help make it a little softer and and I don't have my big brush with me today but there that looks a little better I often do this you know because this guy is the furthest thing back and so it should be a little softer I think you know when you're thinking about distance atmosphere things like that you consider all of that and yeah this guy should be back further and it should be softened a little bit we don't want to make it look like it's really too stormy there we go now we've got some nice things going in here I think yeah mm-hmm okay and we do have a little a little bit of the blue up above right up in here in this little corner right up in here and it's coming up there I see we're going to have some areas of blue coming through in here there's going to be an area right in here and then this is going to be coming around this right here it is going to be coming across over here right there that's all going to be white white and this is going to have some blue coming around down in here I'm trying to sort of come in from the outside in to create my my steam I think I need you know your eye bounces around I think I need this to be just not that white kitty I need this to be just a little bit lighter back here and the on the skyline just a little bit lighter there and then we'll kind of soften that in we'll have that same light over here and up in here this big brush and come down a little bit just keep that nice and soft okay and then over here I'm really seeing a lot of of clouds back there and they're warm they're a nice warm white where this is kind of cool this is much warmer up here so I'll take some white and warm it up a tiny bit of yellow ochre that works pretty well there we go you can really see that that sun is is hitting those clouds back there so now we'll just have to pray that we don't make green when we put these yellow clouds on well I think I'll take the safest road here and wipe some of this out okay now let's see here now these are just kind of going across I'm seeing a lot of green here I hope that's not look like there are clouds in the background we do have a little bit of blue right in there right in here there's a little touch of blue and there's a little touch right up in there this is a little darker in here and there's a little dark right down in there now this is a violet over here here sort of violet color and that's from the steam and it's a little violet on the edge right in here also as it's coming up here this is this one's coming down here like this the blue right here blue violet you see here it's my next biggest brush I guess I'm just gonna have to clean this one and stay with it try to wipe it all the paint off of it that I can it's just turning into a bit of a challenge today but that's okay we're up to it aren't we just hang in there we'll make something happen here I'm kind of like the way this is sort of coming down and around sorry I'm so quiet I I told they forgot forgot you were with me I was so engrossed in this my gosh you know it's just that the process of painting of journeying across your canvas and you've got all these choices to make and and beautiful things to to see and bring out that you forget you forget you're not by yourself you forget to talk you forget to think sometimes I even forget to breathe when I'm painting I love it so much down here now this works down here isn't it exciting you know you just to see this this tremendous thing that's been around for who knows how many thousands maybe millions of years and you're here you are in this TV studio capturing it on canvas it's like a miracle kind of it's wild and free dangerous but beautiful and I want to try there was like little bubbles coming up that kept coming up and popping and I want to try to show you those you know to show you that that feeling of of those little things I don't see them in the photograph but I know they were there I saw them I was there I saw them and see light things going this is this is lighter coming up right here we have some light coming onto this too and the warmest part of it the very warmest part is getting so excited now because it's coming together it's wild it's wild and it's rough and I know it's rough but I can see it happening now we need light right in here I love to paint with thick juicy paint this is that this is what is called impasto thick juicy paint just let that paint build up on there and let it describe that the movement and the thickness of the paint describe the surface of what you're seeing this is warmer right along this edge right in here I do want to take the another brush and bring back some of the blues in here and we have a little bit of the green that's right in here showing has to be a little darker there and then that we may have to wait because if I touch that now maybe if I do it with my paper towel touch it and knock it down a little bit you see you can paint with your fingers with paper towels with brushes knives spatulas whatever you want to paint with there that knock that down to show that that is behind and we'll put a little more on top of it there to kind of there now that that shows that that is that mountain coming from behind and I just I want this to just right in here I wanted to just really come down looks kind of van Gogh-ish doesn't it yeah that's okay that's alright I like it I hope you like it too I hope after sitting here and sitting there and watching me try to make this come to pass here I I we traveled across this canvas I I hope you do like it I think I like it pretty good I think I'll go back in here and maybe make a little more of the green right in here and a little more of the light that seems to be there again that's that rocky it's sort of stuff that I was telling you about you know the the terrain just keeps changing from enormous rocks and cliffs and waterfalls to mountains to rivers and streams beautiful I saw the most beautiful elk of course I only saw him from the back I have this great picture of this elk coming in from the back of him as he's walking away right in the middle of this stream it's just what an experience it was I hope if you haven't been there that someday you'll get to go I really do a little green down here a little bit right in here maybe some up in here right there I think I should do something here to show more where the where this is here I think this needs to be a little crisper there right here there we go that helps need those we need those little signposts that lead the eye into where the the important part is a little more white right in there and let me see here I see a dark green coming right here and then the last thing I want to do here is darken up the bottom of this and make it look it's coming out of that and I think even though I don't see it in the photograph it might help if I come with a little bit of dark right underneath to kind of show that that is coming out of there I think that helps a little bit I think this needs to be just a little darker right in here for the background there I truly hope that you've enjoyed our little journey through Yellowstone and to see Old Faithful at its finest as it is blowing and I hope that you'll join us for our next show when I think I think we'll continue west and go to Sedona Sedona Arizona that's a really beautiful place to the red rocks of Sedona I think you'll like that so you have to be sure and catch us next time as we go to Sedona Arizona and of course you'll want to see whatever little things I come up with to change and make this painting here a little bit you know more refined and that I'll do in the studio I want some light right in here okay my cameraman is telling me I have one minute one minute where's our time gone where has it gone I don't know but I sure have enjoyed being with you today I and I hope that you enjoyed our painting journey to Old Faithful in Yellowstone Park once again my name is Kitty Lynn Klisch you've been watching painting journeys be sure and catch us next time bye bye till then