Attention, Northeast Park Hill residents. This is a community notification of a new sexually violent predator in your area. Please stay tuned to the following short program for more information. Hi, I'm Technician Ron Hackett with the Denver Police Department. The sex offender registration and compliance unit at DPD is responsible for the registration, monitoring, and tracking of all registered sex offenders and sexually violent predators who live in the city and county of Denver. Here's a brief history of sex offender legislation in Colorado. Our state laws trickle down from federal government mandates. In 1994, we had the Jacob Wetterling Act, which mandated that states would establish a sex offender list. Megan's law of 1996 said that the public would have access to those sex offender registration lists. The Pam Litchner Act of 1996 stated that some offenders might have to have lifetime registrations. In the Adam Walsh Act of 2006 unified sex offender laws across the country. In Colorado, the legislature has determined that sexually violent predators, by definition, pose a higher risk to the community at large and therefore mandated that upon their release from the Department of Corrections, the community must be notified. Sex offender notification in Colorado happens in two ways. The first is passive and ongoing through the sex offender registration process, which is a list maintained by local police departments. The second way is active via community notification for those offenders determined to be sexually violent predators by the courts or by the parole board. Most sex offenders in Colorado are supervised by the criminal justice system in our communities. Most sex offenders engage in crossover behavior, which means they may have been arrested for one type of crime, but be apt to commit another.  There is no typical sex offender, but all tend to be deceptive, manipulative, and secretive. 80 to 93 percent of sex offenses are committed by someone known to the victim. Sexual deviancy begins in mid to late adolescence. Sex offenses are not impulsive.  The community has a vested interest in helping offenders to be successfully managed in the community. Sex offenders have the same need for housing and employment as any other citizen. Any citizen who uses sex offender information to harass, threaten, or intimidate an offender will be subject to criminal prosecution. There are approximately 16,500 registered sex offenders in the state of Colorado. About 65 percent of convicted sex offenders are placed in the community on probation. The remainder are in the Department of Corrections or Community Corrections. Offenders may be caught for one type of offense, but be at a high risk to commit another type. Crime of conviction is only one indicator of risk.  The offender's residence must be verified quarterly by the Denver Police Department. The full sex offender registration list is available by calling the Denver Police Department Identification Bureau at<PHONE_NUMBER>. Convicted felons and those with multiple convictions are posted online at denvergov.org slash police.   Now, here's a look at the newest sexually violent predator living in Denver. Here's an overview of the registered sex offenders currently living in Denver. There are 2,390 total living within city limits. In Denver Police District 2, there are 378. Precinct 221 has 125 registered sex offenders. Of those, 99 have felony convictions and 26 have misdemeanor convictions. David Kevin Willis is a sexually violent predator currently living in Denver. He's 47 years old and was born on July 25th, 1975.  He's currently living at 5111 East 34th Avenue in the Northeast Park Hill neighborhood of Denver. Schools located within one mile of this offender include Steadman Elementary at 2940 Dexter Street, McAuliffe International School at 2540 Holly Street, Hallett Academy at 2950 Jasmine Street, Smith Elementary at 3590 Jasmine Street. Parks located within one mile of this offender include Colorado Boulevard Park, City of Nairobi Park, Skyland Park, City of Aksum Park, Ferguson Park, City Park Municipal Golf Course, Boyd Park, Fairfax Park. Recreation centers located within one mile of this offender include Hiawatha Davis Junior Rec Center at 3334 Holly Street. Bus routes located within one mile of this offender include Route 34 35th Avenue and Elm Street 35th Avenue and Forest Street 35th Avenue and Glencoe Street 35th Avenue and Dahlia Street 34th Avenue and Forest Street Dahlia Street and Bruce Randolph Avenue Route 43 Martin Luther King Boulevard and Elm Street Martin Luther King Boulevard and Fairfax Street.  He's currently on parole and registered with the Denver Police Department on April 24 2023 to 5111 East 34th Avenue in the Northeast Park Hill neighborhood of Denver.  David Kevin Willis has been determined a sexually violent predator after meeting the following criteria criteria one age 18 or older on the date of the offense or under 18 and tried as an adult. The offender was age 41 at the time of the offense criteria two. The crime must have been committed honor after July 1 1997 and convicted honor after July 1 1999.   The relationship to the victim was one of the following victim was a stranger to the offender or the offender established or promoted a relationship with the victim primarily for the purpose of sexual victimization. The female victim was not known to the offender criteria four positive results or the passing of a risk assessment instrument administered by probation parole staff and a qualified treatment evaluator positive results include an assessment for the presence of a mental abnormality a level of denial regarding the offense treatment appropriateness and motivation presence of sexual deviant interests. The offender was evaluated by the Denver District courts with positive results determining him to be a sexually violent predator.


celebrating beauty and curves, taught to seven African tribes with the most stunning and curvy women. Get ready for an enchanting journey across the African continent, as we unveil the secrets of its most alluring inhabitants. These tribes celebrate the beauty of curvaceous women, embracing their natural forms as symbols of fertility, strength and grace. Join us as we explore the top the 17 African tribes with the most beautiful and curvy women, revealing their unique customs and the captivating stories that define their perception of beauty. With the outmost respect, kindly note that our list cannot contain all the African tribes whose women are strikingly beautiful and sensually engrossing. Let us feast our eyes on some of Africa's most stunning and gracefully curvy women. Sitting census at the seventh spot is the Afar. Ethiopia's desert roses embark on a journey to the arid landscapes of Ethiopia, where the nomadic Afar people reside. Their curvaceous women who endure the harsh desert environment exude a unique beauty that is both captivating and resilient. Sixth spot is the ever gorgeous Zulu Queens, South Africa's sensual warriors. Explore the Zulu tribe, known for their fiercely beautiful and curvy women. The Zulu celebrate their women's strength and sensuality through traditional dances and rituals where they showcase their agility and confidence. Allegantly occupying the sixth spot is the Ashanti. Ghana's regal damsels. Discover the Ashanti tribe whose curvy women are revered for their regal beauty. Adorned in intricate gold jewelry and richly patterned Kent fabrics, Ashanti women exude a sense of royalty and grace that is truly mesmerizing. Fourth spot is the Twana. Botswana's elegant queens travel to the breathtaking landscapes of Botswana where the Twana people reside. Their curvy women renowned for their grace and poise carry themselves with dignity and confidence. Traditional Twana attire accentuates their natural beauty, adding a touch of sophistication to their presence. Number three is the Yoruba. Nigeria's vibrant goddesses. Journey to Nigeria where the Yoruba people celebrate the beauty of their curvaceous women. Inspired by their pantheon of goddesses, Yoruba women adorn themselves in vibrant fabrics and exquisite jewelry showcasing their stunning figures and radiant smiles. Proudly occupying the second spot is the Yuvimbundu and Gola's fascinating matriarchs. Discover the captivating world of the Yuvimbundu tribe known for its strong and shapely women who play vital roles in the society. As skilled farmers, traders and artisans, Yuvimbundu women embody beauty, power and resilience. Prestigiously occupying the number one spot is the Fulani. West Africa's graceful nomads venture into the vast expanses of West Africa where the Fulani people roam. Renowned for their tall, slender and curvaceous women, the Fulani epitomize grace and elegance. Their beauty rituals and adornments such as intricate hairstyles and ornate jewelry add to their allure. As we have journeyed across the African continent, we have witnessed the awe-inspiring beauty in curves of women from various tribes. This enchanting tour reminds us that beauty is diverse and it can be found in every corner of the world transcending borders and cultures.


The landscape of higher education is continually evolving, driven by advancement in technology, changes in societal needs and a growing understanding of effective teaching and learning methods. We had the pleasure of interacting with Dr. N. R. Alamelu, Principal Sri Ramakrishna Engineering College, Coimbatore, who shared with us the several ways in which teaching and learning processes at engineering colleges are developing. In engineering education, till a few years back, the pedagogy was a sort of a structured curriculum, the syllabi contents for the various courses as part of the curriculum and then assessment, grades, degrees, etc. Now we have moved away from that, which I could even call it a sort of a transformation where the curricula are not any more structured, there is lot of flexibility in the curriculum which is eventually a choice based learning outcome based curricula and syllabi, the students could register for the courses of their interest, of their choice, take up these courses. On the teaching learning process side, we have moved more towards student centric learning where we will have to prompt the students, motivate the students for lot of self-learning initiatives as well. Because whether it is a research or an industry problem solving, what is expected from the graduates is that they are ability to continuously learn. The technology is changing so fast that they cannot stop learning at any point of time, they will have to be learning continuously, they will have to be lifelong learners. If they will have to be lifelong learners, self-learning is part of the learning exercise. So in the teaching learning process, effectively the relationship between a teacher and a student is becoming that of a mentor in the students where the teachers will have to mentor the students to learn, create inquisitiveness, create the awareness to question, to experiment and to learn new things. Similarly in the assessment also, we are drifting away from the examination oriented mark-driven assessment, rather we are moving towards outcome-based assessment where the students will have to attempt a problem, find a solution for that, try something new on the hands-on experience, eventually more project-based learning, more outcome-based learning, activity-based learning. I think these are the changes which have been there for more than one and a half decades now, but being looked at more seriously, more effectively by all the stakeholders of the higher education system, may be during the last decade and about 5 or 6 years now. The innovation is not just the buzzword, it is certainly making a difference because how do we look at a problem, how do we look at a solution to the problem, it will have to be different. The present graduates, the aspiring engineers or any graduate for that matter cannot afford to think in a routine manner, they will have to be out of the box thinkers, they will have to be innovative and creative thinkers from the way they look at a problem, from the way they look at solutions to the problem. So innovation is becoming an integral part of problem solving, particularly with respect to engineering education. I very firmly believe that this is becoming more and more of an interdisciplinary approach. I very frequently mentioned that if we take an automotive for example, till a few years ago it was treated to be the domain of a mechanical engineer, but now I cannot say that anymore because there is more electronics, there is more computing, there is more protocol into any automotive which gets rolled out today. So the line between the different branches of study of engineering is becoming thinner and thinner, everybody should have a basic domain knowledge built on top of that, knowledge on digital technology, appreciation for the technology and application of those technology to the basic engineering domain from which they are choosing a problem to be solved. The innovation centres and the universities and colleges they basically motivate students to think differently, to try hands on whatever be the thoughts, may be quite a few times it could be some crazy thought. After attempting something the students may realize that this is not the way to go about, but still does not matter. They have attempted something which is different which would certainly motivate them to travel through that path more vigorously, more aggressively so that they are able to develop their thought process, the thinking process to think different towards a problem solving. I feel innovation centres should not only be part of an institution as an infrastructure, it should be part of learning, it should be part of assessment. I say that it should be part of assessment also because during the initial periods of take off unless the students are convinced that they will be assessed for this also they may not show interest. Once they are convinced about that probably it automatically becomes a routine process for them to be part of the innovation ecosystem as well. So once the students they get interested into something to be innovative I feel that they will have to start looking around what we call as empathy to may be a particular segment of a society or a particular sector of industry problem solving etc. They will have to look at a problem or they should look around identify a problem and then convert that into a technical problem statement and then try to solve that problem, develop a solution for that validate that. Once the concept is validated I think they will have to move towards how best it could be either converted into a product or it could be a full service solution so that it could be commercialized. A team of members who get into such new attempts of either a product or a service or a solution they will have to be motivated in an incubation center to become the founders of the startup for which the mentoring support system may be some initial seed funding. Once they mature once they graduate taking them towards venture capital or other funding process they will have to build over a period of time in an educational institution so that we are able to create job creators rather than the job seekers. The institutions who have innovation centers the institution who have incubation facilities would certainly be able to produce more students who think differently who are able to identify problems and find solutions. They will be able to generate huge job opportunities which in turn will contribute to the overall economic growth of the country a sort of a satisfaction that I do not do it for myself I do it for the community as well because of me about 10 families 10 individuals they prosper and if this grows multi-fold I think we should be able to meet with the expectations and the vision of the honorable prime minister of the country as well. It is quite evident from these insights that our educational institutions are gearing up to the challenge of Vickersat Bharatak 2047. We congratulate Sri Ramakrishna College of Engineering for developing an effective ecosystem for innovators and hope that their students will be contributing positively in solving the real world problems and play a role in making India a developed nation.


What's going on traders and investors Alex here and in today's video will be going over my setting in the new TWS chart because they did have a massive update recently and I actually started to use them and quite like them because they do remind me of trading view. So before getting the video a quick reminder that all the tools I personally use to trade and invest will be linked down in the description that includes broker scanner charts and newsfeed. So without further ado, let's get in the video. Alright, so we're going to go over these chart and talk about all the setting and how to customize them. If you haven't opened one already, the way to do this is just go to new and then you're going to go to chart and then you can go to advanced chart. And if you don't see the new chart coming out right away, what you're going to see is a big window on top that's going to ask you if you want to open the new chart. But because I'm already using them, they started to stop sending that message because I actually have them open. So we can see over here, I do have a bunch of indicator on this chart. And I have some settings that are probably different than the one that you have. So we'll break down really everything that is important to use them for either investing, swing trading, or even scalping day trading, you're going to have all the settings that you actually need. So over here, you're going to go first to the indicator. If you want to add some indicator, if you want to add like a trend line or anything is going to be on this side, where I like to start is actually customizing the look because you're going to be staring as these start for quite a while. And you want to make sure they're really set up the way you want.  So first of all, let's unclick and click some stuff. So this is pretty important. If you want the body to be full and colored, the borders, if you would like to change just the border of the candle, some people like to maybe make it like white. So I'll add a green color. I'll save it before changing anything. But if you want to put it this way, so you have an outline on your chart, this is how you would do it. I personally don't like to do this. And I like the way to be the same color. If you want to change it, the way you would do that is just change the color here. And you can see that these wake now are a different color. But if you want to keep it as simple as possible, leave them the color that they are, because the color is actually really nice. And I'm someone that's picky with that stuff. And I get annoyed pretty quickly when platforms don't let me or don't have a good layout in terms of visual, just because sometimes with the reflection of window or light, you can see and it's just quite annoying. So something that you can do this, we're going to leave it on a click on click also. But if you want to click these, what they are is you can see this $8. There's a line over here. I personally don't like to do this because I already see on the sideline that the price is over here. And this is for the high and the low of a range that you're looking at. I never found this useful because if you're looking at a different range, it's going to give you a different level. So it's always moving around. And I just don't feel like it's useful. So I definitely unclick this. Sorry for the interruption. But if you enjoy the video, don't forget to like and subscribe. We're trying to get to 20k this year. This year has been a big year. We passed 10k, but 20k is the new goal. So if you want to support the channel, don't forget to do that. Let's get back to the video next over here. What we have is we have the title bar, which is going to be right here. We have open, high, low close. If you want to see it, bar change value and also volume. If you want to see it on top, I personally don't like to have it there because if you're using an intraday chart, we're going to go to the intraday. You can see over here that it has the value of whatever you're on top of it, but also just in general, it's going to have the last value. So you can see this one is going to say open 803, high 803 and low 803. So it's going to show like the last candle, which is not really useful compared to your open, high, low close on a daily chart. So if you have a daily chart, I would recommend that you leave it. If you're looking at an intraday, I would recommend that you remove it. So we're going to go back to settings and then after that, this one was this one over here. So because this one is a daily chart, we're going to leave it, but otherwise I remove them and we're going to leave it with the volume. That's totally fine. So the rest normally, I don't need to see it because I have the watermark on my chart. So I know what I'm looking at. So I can remove at least the title to clear the space on top over here. Background, I leave it like this. This doesn't change anything. And after that, you're going to have scale. And this one over here, you can also put the symbol name over here if you want. I personally like to remove it and I just have symbol last price. This one is going to be important because it's your last price over here. And this I don't change high, low price. I don't really want to see it because it's the same thing as we saw before. It's going to tell you the top and the bottom of a range, like a bigger picture range, but it's going to move or it's always going to be different if you're not using the same time frame over and over again. So I just like to move it to have it like a better chart and a cleaner one. And also, this is quite important. It's no overlapping label. So if you have an horizontal line at 748, and then you have maybe something else at like 742, it's going to show you both. Otherwise, if it overlaps, you're not going to see both is you're only going to see one, which is not ideal. So you can remove them. And now countdown to bar close. This is really if you want to see on the intraday mainly, like how many minutes is there left to a candle stick? I personally don't do that. I never did use them, but I know a lot of people are going to look at how much time is there left for the end of the candle, which could be useful for some people. I just never got used to it. And I prefer to just keep it off. So we're going to go back to the daily when it comes to the setting, the plus button, I just don't want to see it. Sometimes it's going to be on plus something here at the bottom and scale mode a and l always invisible. This I just don't want to see it. It was some like you can see over here, like out of fit or logarithmic. I never need to see that's always invisible. So it's cleaner. There's also less data to calculate on your chart, scale placement. This has always been a auto. I never had any issue with that. And also the date, the format is going to be there. So let's jump into the section that's going to be more popular. And this one is going to be for the background and the colors. So as you can see, these looks pretty good. And I don't like to have the gradient. Some people like it. I like to go really solid. It's just much better. And I like to have the grid line a pretty light. So right now I think they're set almost too simple, like the standard size. Before you change anything, as I mentioned, just save the previous color that you have. So you don't get confused. So now you have your candlestick. You also have your grid line. So everything is set up. And I like to add the pan separator. This is going to be white. So this what you see is going to be at the bottom of the pan. There you see it's a different section. If it's not like this on your chart, I'll show you how to set it up just in a little bit. So crosshair, this is what you see there. Maybe this one actually, it's a better if it's just a bit lighter like this over here. I don't need to see it that dark. And the watermark, if it's not on click, you should probably click it. Because otherwise, it's hard to know which chart you're looking at. It just so much better when you can actually see the watermark, which is going to be right here. And something that's a little odd, you probably realize by now is that you don't see the buttons. They're quite the same color. Maybe it's my screen or anything like that, but it's not ideal. But what I did have, it took me a bit of time to really see that there was something there to click and unclick. When it comes to scale, this is going to be the white line that you see over here. I have it set at 14, but this is really going to be personal, depending on your screen resolution and what you're looking at. But I do like to have it white. And the line, I have it also white, but just a bit less drastic in term of color. So not that white, just to have like a good separation of where the border of this chart is. And also the text. So everything is better on the visual side. So the next thing is navigation on mouse, visible on mouse navigation, you can say always invisible, this not going to change anything. And pan always visible or invisible, it's not going to change anything, these little things. So you can leave it like that. And you have top 10% bottom 8% and right 10%. So normally the top and the bottom are the same. And right, I like to have it probably at a six like that. So just a bit more close to the border. So I can see more easily, you know, where these levels are on my chart, you're going to see the bigger difference when you're looking at the intraday chart is just a bit closer to the border. And I have to, I like to have a decent amount of space on top, because if I have a level that I'm looking at, I want to be able to see it. Same thing over here at the bottom. So now we're going to be jumping back in the final settings of this chart before going into the indicator, which is going to be an important part, because I do have some setting that really helped me have more indicator, but not be there on every single timeframe that I'm currently using. So we can see over here in the last section in the Canva, this is pretty much there. And over here, you're going to see applied default, but you don't want to click apply default yet. What I would suggest you to do is just the save button over here and save as a name or something like that. And it's going to remember at least your chart and what they're set up for. So you can put day trading, for example, all right, so this is going to be saved. And now, before going into the indicator, as I mentioned, if you want to see the intraday, you're going to have to click on this over here. So for example, there we're going to go into a 30 minute chart, you can see there is no intraday. If you want to see it, it's going to be over here. And now you have the intraday session, you can see it better with the volume over here that sometimes there is no volume. Sometimes there's a lot of volume. It's not perfect yet because I would really like to have at least the color for the pre market and the post market, but it's still much, much better than what they had before. And after using them for a while, you do get used for the pre market and the after hour just because it's trading so thin in the pre market and also there is no volume. And normally the big volume bar is going to be at the start of the day, as we can see over here, there was no volume and you can see your first candle in term of volume. So just a little something to get used to. But if you want to see the pre market data, it's with this button over here. So now let's jump into the indicator. So to add an indicator, quite simple, you choose the one you want. So I have a lot of moving average on this chart. I'll use a simple one, just like a moving average again. And you can see when I'm looking at the daily chart, I have a bunch of indicator, but when I'm looking at the intraday, if we remove the last one that I did have, I'm not going to see that many intraday. I only have one trend line or one, sorry, moving average.  And now you're going to see visibility. So if you don't want to see it on the intraday or anything like that, you remove this. For example, I have it with the 200 EMA. So over here, you can see if I go in visibility, all of these are definitely checked out. I only want to see it on the day, the week or the month. So you select the timeframe that you do want to see and also the one that you don't want to see. And then it's going to be like that. And when you go to your intraday, here we go. It's not going to be visible. So you're going to have less and less. Something I could definitely do different is just change a bit view up because it's almost the same color as these candlesticks. So if I put like a purple, it's going to be a bit cleaner to see versus the red on red.  So something that's important, if you don't see your volume in a separate pan, you can do over here move to existing pan above. So sometimes it's going to come in this specific way over here. If you want your volume to be in a separate pan, you say new pan below. And now it's going to be in a separate section, which is really, really useful. And it's not going to cluster all your chart. And now your scale is always going to be a better and have more space on top and also at the bottom. So this is much, much better. And when everything is done, pretty much just save and everything is going to be there. You can also save your indicator section over here. So save indicator template. So you can have a name. So let's put EMA daily, for example, you're going to do save.   So if you want to have multiple of these charts after you open them and you want to sync them, it's going to be right over here. You just need to group them. And just like that, you're going to be good to go. So I hope you enjoyed this video. This was a quick tutorial about the new chart, but I really do enjoy them because they're almost exactly the same as a trading view one without just having the colored pre market and post market. But when this comes out, I think it's going to be a big problem for trading view because all of the TWS user won't have any reason to use them. So thanks again. Peace.


So it's really exciting today to be at Holly Allen Entry in Surrey. Today is really about making an announcement to help the students, the students here in British Columbia. School districts around the province have done an amazing job this year, around 25 million dollars worth of administrative savings. We work very effectively and efficiently and we are already low in our administrative levels. So to be able to have those dollars back to us, to be able to address the learning needs of our students is very important for us. Today's announcement is about returning that 25 million dollars back to school districts back to students so parents in British Columbia will know that their students are getting the programs and the opportunities for the provinces willing to help support.


We live in one of the greatest startups in the world, right? It's very difficult for Asians to go and to say things that they feel that sometimes even on their chest, right? Maybe in your in your circle have called you the Gordon Ramsay of the venture capital world. Interestingly enough, there's not a lot of Asians in VC, but there actually are a lot of Asian founders, right? Every VC knows that if you invest in a company, it's going to take six, seven years to get at minimally to get out of that investment. So that's a marriage to me, guys. It's not it's not a hookup.


What's going on, everyone? Sam here with late in sports cards, ripping three boxes of 22 top-scrone black baseball for Akeem D. It's good luck, Akeem. Let's see what we got in here for you, buddy. A gold, it looks like, to start off. Matt Chapman, Brandon Crawford, green atomic, Mookie Betts to 99, 97 out of 99 for the Dodgers. Got gold rookie of Joe Ryan, eight out of 50 on the gold, again, gold rookie auto for the twins. Nice one there. We got an orange coming up. Yeah, I know, Nemesis, that was a rough game. That was a really rough game for Caleb Williams, dude. Gold, Xander, it's 30 out of 50 for the Red Sox. Like, what more can you ask from your quarterback, you know? We got orange of Casey Meiss, two out of 25 for the Tigers, nice one there. Another nice low-numbered auto for you, buddy. True orange on that as well. There you go, Akeem. Yeah, Greg, we got a good amount. We're not gonna get to like 15 orders tonight. There's gonna have, we're just gonna have to go tomorrow. Tomorrow, Wednesday, Thursday, whenever we get to them, basically. We had a couple days off, so we're a little backed up on personals. We got a lot of orders today, too. So we'll slowly but surely catch back up again. We'll take two or three days. We'll be good to go. Arnaud, Vladimir Guerrero Jr. There's Aaron Ashby to 199. And we've got green. Cabrion Hayes, 75 out of 99 for the Pirates. On to the auto. I'll do it for your break there, Akeem. Thanks again for your order and your support, my friend. Get those right out to you, buddy.


How are you doing? I'm good. How are you doing? Like it's been a week. It's yeah. And I mean, like the rush is starting now or it's really, really starting for Cuban. So it's been a week. It's been a week. It's been like, it's been rushy, but also slow. Definitely on the CNCF side. People are, People are moving slow. Yeah. I think we might as well meet because it's not like anything in the election counts is going to change in the next hour. And why I know that people love. Compulsively hitting refresh. It's not actually helping anything. That is, that is my favorite pastime. Actually, it is. I've been spending a lot of time hitting refresh. See, whereas I scheduled a whole bunch of things that I had to do for work and at home this week. In order to force myself to only check the results like once every three or four hours. No, I rearranged my whole schedule so that I could stay up all night and watch the results come in because they're not in a time zone that's friendly to me. But. After Brexit, like you look at the polls and I went to bed and I was like, Oh, you know, it's going to get remain. That's what all the polls say.  And I woke up the next morning and I was just like, What? And then after that, I was like, I'm not, I'm not doing that again for anything important. Like, I don't want to. I don't know. It doesn't help anything. My constantly refreshing, but. And staying up all night, but. The. Yeah. So anyway. And besides which, given what I need to work on for this sig this week. Given what's going on in the US this week, it's kind of nice to be writing governance documents where I don't, I don't have any projects dropping in right now. Given what's going on in the US this week, it's kind of nice to be writing governance documents where I can actually recommend practices. Deep, deep cut. Yeah. Amazing. So yeah. Okay. So we don't have any projects dropping in right now. It's actually been kind of nice. We've had projects dropping in on several of our meetings. Yeah. And I hope that continues. So. So we had mentioned, we had mentioned this. Why don't we just. Do it. Or should we do the, should we do the, hey, we're meeting. We're meeting stuff. Yeah, let's do that really. Hello, hello, everyone. Today is November 5th. This is a meeting. This is a meeting that will be recorded and available on the internet later. So please be mindful of what you say and do. Please be sure to adhere to the CNCF code of conduct. And in general, just be awesome people. Okay, done. Thanks. So, so yeah, we were, we were, we were, we were, we were, we were, we were, we were, we were, we were, we were the, the homeless street and the homeless street. So, so yeah. We were, we had mentioned, kind of in passing. Uh, what, if we just made the, so our every other meeting was going to be kind of like the office hours, but if we just call that maintainer circle and kept it moving, sounds kind of defeated. Let's talk through that. Yeah, my bad. I've been absent because I've been doing amazing things for Kubernetes at Apple, which is awesome. And yeah, we've got amazing things going on. And you're going to dish? Yeah, Elena will talk. Yeah, Elena will talk a lot about it at KubeCon. So that we've also been getting ready for that. So we've got a ton of people speaking as well. So yeah, no, good things, good things for the sustainability of the project for sure. Anyway, so that means that I've been absent. However, I definitely am back now and I'm ready to finish out the out the year with the community, which means I would love to kick things back up with with everything that I have do, which is a, maintain our circle, be the recruiting playbook, and then see the the community management requirement for graduation. So those are the things that I'm like really gung-ho about right now. But if there's been further developments with maintain our circle without me, like let's talk about it and collaborate and see how we've grown and whatnot. I mean, I don't necessarily think it needs to be some one-size-fits-all thing.  Yeah, no, we're actually nothing has happened yet. Yeah, I think I think everyone's been generally busy. So yeah, we can circle back to what you wanted. Okay. Yeah, I was like I was envisioning break rooms and small discussions kind of like what we do here now with individual groups, but a lot of different maintainers from different groups, which then the conversation would get a little wild. So I was mean, I was envisioning breakout rooms and discussions and things like that from way back in the day, way in the beginning of this year. But yeah, I know I do. I have some awesome amazing people queued up to for topics. But I know that this group really wanted the inclusive language topic to go first. So yeah, so what we actually I think maybe there's a few meetings back what we had landed on was we kept coming back to like burnout and just talking about like maintainer sustainability. So we were thinking maybe we do that as the first topic. The contributor. No, the inclusive naming initiative is planned to have its first community meeting at cubecon. So it's going to be that Thursday morning, depending on your time zone. So we can come to that if people are interested as a first step just to like show, show out in force. And then and then kind of take the topic into contributor strategy as we need to it doesn't need to be the first topic. Okay. All right, so I will continue to work on getting us some presenters for a burnout topic. And then I'll line up and schedule the rest of the speakers by weekly based off of the are off weeks. If that's cool with everybody. And then I'll work with Amy to start to get communications together. I don't think yeah, I don't see her on the line right now. But yeah, and I'll work with Amy to start getting communications together around that, meaning talking about and introducing the fact that maintainer circle will be biweekly. And how you sign up and get cool. Yeah, should we have like a running form to drop topics into or somewhere? Yeah, I just I just been using GitHub issues. So that's where they all are now. I mean, I can definitely organize that in a better way or we could put an issue template together all years. I mean, this is you're looking at the bottom of the foundation of the of the thing. Anything can be changed at this point. So you know, as as it stands at 1038 am Pacific time, we are collecting issues in GitHub issue or I'm sorry, collecting topic ideas in GitHub issues. But yeah, totally down for a more cohesive approach if you have suggestions. I mean, I think that's fine. Okay, just, you know, just allowing people to drop in and say what they want to say. Yeah, so are we looking at this time slot or the time slot that Amy has for Project Sync? The last was this meeting this time. And then Amy said she was keeping up Project Sync for Project Sync. Okay. That's the other time on like Thursday mornings or something, right? Tuesday mornings, I think. Tuesday. Tuesdays? Yeah. I'm totally okay with whatever just point somebody point me to a time that we can lock in that would work best. I think it's I think it's fine to keep this time and just alternate for now. It's like it. The I mean, the upside is that it's already in the calendar, right? So Yeah, though, if we want to do maintainer circle stuff bi-weekly, then do we want to basically have this on the calendar every week? And every other week, it's going to be maintainer circle. And then the succeeding week, it's going to be half an hour of actual SIG stuff. Yeah. And how we want to do things. I was thinking we were going to do an hour and a half for maintainer circle. Okay. Well, I mean, whatever. I'm just saying, I'm saying, if we're using this time slot, right? And you want to have maintainer circle every two weeks, yeah, then we should move this time slot to weekly so that on alternate weeks, we can have coordination meetings. Yeah. I'm okay with that. Sure. Okay. Do we have anything else to maintainer circle? Nope. None of this. None of this time. So next thing on our agenda is prep for our mini micro paperwork workshop. The we've done. Dawn, Carolyn, and I have done the recording. Now, there's two other things. One is to potentially get more materials for projects prepared to whatever we can get put together in the next two weeks. And then the other thing is, of course, to get project leaders to show up at it. I already plugged the session in the TOC meeting on Tuesday, but that meeting was extremely lightly attended. So I don't know that necessarily anybody that will have actually gotten the word out. Beyond that, I think we can all sort of individually socialize it. We're going to ask Amy to send something out to the projects. Yeah. Yeah, I think that would really help if we could kind of get the word out for like, especially like sandbox projects and let them know that we're here to help. When's the next project sync with Amy? Because that would be a perfect plug, because I think that they have to check in there, right? No. No, they only show up at project sync if they need something. Oh, okay. Well, I mean, that still could be a good check-in point for us. Yeah. Okay. And so that'll only work if there's a project sync next week. So check the calendar. Any other ideas for, because I mean, one of the other things is, one of the groups we want to reach that's rather amorphous is leaders of projects who are thinking of applying for sandbox. And there's no concrete way to reach those people because they're not seeing the projects yet. We could lurk on the TSE proposals, I guess. Yeah, and it's funny you hit up some stuff in CNCF Slack. Yeah. Okay. So for preparing other stuff, what I have planned to get ready before KubeCon is number one, I'm currently working on three templates for three different forms of project governance for the templates repo. Looking over CNCF projects, the three most common forms of governance are sort of simple maintainer, council maintainers. Composite projects, and that's where the project has a bunch of sub-projects, and then the technical leader of each sub-project is a member of some kind of council, and then steering committee elections. And so I'm writing generic template documents for each of those forms for the templates directory. It's extremely difficult to write completely generic governance documents because you pretty quickly get into a decision tree of if you do this and if you do that. So I'm going to get those done probably tomorrow. And then I'll ask people to review them. I'd like to have them available for the micro paperwork sessions. So if we can look at getting them in on a sort of MVP basis, rather than this is the perfect template for this kind of governance, because for one thing, I don't think the perfect template for type of governance X is actually achievable. The other thing is, I have a document I wrote for another publication, which is just sort of a list of all the different kinds of paperwork that a project will commonly want to have. I've been cutting and piecing that to fit in with the CNCF requirements and the structures we have for the rest of our documentation. And I'm going to try to get that finished for the paperwork session so that even for types of paperwork where we don't have a full advisory document or a template, we at least have a paragraph saying, hey, you're probably going to want this. Anybody else working? Yeah. So some of the governance documents that are in the resources guide are actually really beautiful. And I was wondering if we could adopt some of those. So some of the there's like there's like re there's like governance checklists. And some of them are really beautiful. Like I can bring up them now like like sustain like sustain OSS they have a governance checklist. And they're really like thoughtful and like they would be great for like a workshop. I don't know if y'all thought about that kind of style. And like there's one one of them that's linked as well is like a work there's like a governance workshop. And it's the curriculum of the governance workshop. That looks like it could be sort of a plug and play to like what we've already done and stuff. Hold on. Let me I'm going to get some of the links out. Yeah, I had the governance checklist in LinkedIn, the template for the this the KubeCon workshop itself. We're actually focusing on the requirements checklist. The and that's actually led to something else I put further down on the agenda. But so we are focusing on a checklist. It's the CNCF requirements checklist for for different levels of maturation. And then what we focus on in detail is going to depend on who shows up the we have what was it with 12 minutes of video and the 12 minutes of video sort of focuses on that checklist and the general requirements. And then the rest of it's going to be Q&A. So yeah, that's cool. If you have if you have other stuff that should be included in a template, then please link me that and if it's not already in the resources document, obviously it should go in the resources document. I just dropped it in the chat. Not the chat, sorry. In the notes, Paris dropped it in the chat. I like how this asks you quite like it prompts them to think about it and ask in a question way. So it's just like, let's talk about your decision making model. Like how do you want to make decisions? I don't know. That's why I saw that and I like I thought that was wonderful. Yeah. Yeah, that's really well done. Yeah, I love this really like this. Yeah. So I was like, we should just like, you could almost not adapt it, but pretty much adapt it but plug and play with some of the stuff that like all the work that's on like some of the stuff that's already been going on, you know what I mean? To like make it hours, if you will, but from a general a general sense. I don't see a license on this. Is this CC? I think let me, yeah, it's in their repo. Let's look at their repo. What was that? Yeah, their website says that the contents on the site is CC by SA. I mean, I was planning on just referring to the website though, because that whole thing is actually helpful and I don't see any particular reason to copy it. Yeah, it's only if we want to add some CNCF specific stuff to it. Yeah, I feel like I can work at least all the CNCF. Yeah, all the CNCF specific stuff I have so far. I can work into the templates. Honestly, most of the CNCF stuff does is it limits some of the decisions you need to make, right? Like you don't need to come up with a whole structure for managing your IP because the CNCF does that, right? You just need to designate who's allowed to tell the CNCF what to do. And you don't have to decide which COC to have. Those are two things.  So yeah, we could have our own decision tree based on this one.  That would be really cool to see kind of a visual as well. That was probably not helpful, but I mean... Yeah, I mean like the side-by-side of like seeing like answers to those questions and whether or not you have to deal with them would be awesome. I think a few of us have done proposals for projects to the CNCF at this point and... words. There are words. I didn't know what I was doing. This is a short version of it. And there's quite a bit of digging that you have to do to kind of like put the pieces together in the right way. There is a template now, right? There's a template for proposals, an expectation of doing a PR, but it's still hard, I would say. Okay. Anyway, I'll get those templates done in time for GoopCon. Don't know that I would get something like a decision tree based on the Sustain OSS material done in time. Anything you do will be wonderful, Josh. Yeah, so the... I do have to say one of the dismaying things is I said, okay, well, first, what I'm going to do for copying text is I'm just going to look through the governance documents that we have for all of our established projects and pull out common elements. And the thing is, even when the workflows are more or less the same, the wording is completely different. It's going to be interesting. So, okay. Oh, so my other question is, is anybody else going to have time to prepare anything either in the way of advisory documents or templates that we don't have finished at this point? Can I ask a lazy question to the chair? When's KeepCon again? It's two weeks away. All right, hold on. Yeah, yeah, it's at the 17th. Yeah. Yeah, hold on. 17th.  Just a week and change away. I can't believe it. So I do have time for some doc review, but as we get into the middle of next week, it's... If you give me specific tasks. You have rather more duties around KeepCon, Stephen. Most of the stuff that I'm doing for KeepCon is already done because we have to do everything in advance. Fair. This is not true for you. Okay. Oh, hey, Charles. I'm to do some reviews. I don't know that I have time to do any new stuff. I am still sort of on the hook to do... I'm currently scared, Charles, away. I'm still on the hook to do the charter, and if I get time, I will try to do that next week, but I'm not convinced I'm going to have time to do it. Okay. Cool. I would say at this point, some of our only focuses should be whatever we've got to get out of the door for KeepCon and then pick it back up when we're done. Yeah. Do you want to give me a task? What do you need to do? Yeah. One of the things I was going to ask, Carolyn, you were working on a contributor ladder template. Is that likely to be done in time for KeepCon? No, not really. Because I was working out with somebody else, Karen, and so we still have more to go on that, and I don't really want to try to show something through in time for KeepCon. Do you want to give... What if we give some of the resources and say that a template's coming? It's almost like a look at these that we endorse and then a template that we're working on is coming. Yeah. We can try to figure that out next week, I think. Try to pick something we endorse. They're pretty all over the place, to be honest. Well, I know that's one. If we give a list of five to eight and we say here's some that we think are good for those community groups and not necessarily like... Oh, okay. Yeah, yeah. No, if we don't have to pick just one, yeah. Yeah, yeah, yeah, yeah. Karen's already identified some, so we can do that. And those are on the resources guide that we have in the GitHub repo, too. So if we want to just review that, too, Josh, you could pretty much use anything that's on there. Yeah. If you have to fill in gaps, meaning like and say more templates coming, TBT kind of thing. I think that's fine. Yeah. Yeah. Just seeing what materials we can get together before the session, other than the resources which we already have. And also, obviously, this would be a call for, hey, if there's stuff we haven't added to that resources list yet, we should. Come on down, you know. Yep. So just so that we will have stuff because if people ask a particular question, they want to say, hey, do you have an example of... We've been working on our... No, we've been right. We've been working on our piece of paperwork we need on our DCO. Do you have an example of that? Cool. I don't even know what it does. That's nice. Some CICD things, I think, right? I kind of lost track of where we are on the agenda. But I just wanted to let people know that you have a PR open that needs someone to review it in Paris. Yay, link me. I'm like, yeah. Stuff. I'm like my first stuff. Yeah. Sorry, I'm muting. Yeah. This takes the good first issue labeling stuff that I did for community, Kubernetes community a couple of years ago and refreshes it because we have more ideas now and kind of made it not specific to Kubernetes. So that's what this is. Sweet. Yeah. And I actually like this better than the Kubernetes one, by the way. And I will absolutely say that on the recording. Thanks. We can ship it back into Kubernetes. Yeah, I know. At that time, we need to re-ship it back in. We need to figure out how to do that. I'm happy to submit a PR to do that. I was super sad that the file got copied around and get and lost all my attributes. Oh my gosh, girl. I have folders in there. That was me the other day looking at all these whole directories of content that are now owned by somebody else. I was just like, all your hard work is yeah.  But if I was like, you know, and you want to like link to your work, like now I have to like go into my get history because like now it looks like Bob did all my work. Yeah. Yeah. Lovely. So it's just like, anyway, we can totally stop offline about that together because I also agree that that is like, so. Yeah. I don't know. So that's what that is. So if anyone wants to look at it, I really want Paris to look at it because I think you helped to review the first one. So. And I did not help review the next 80 iterations because I think it might have the spirit, the essence of that document. I think the coolest part is like coming back to something after you like, Caroline, I had no idea you did the lay down the first doc for that. But like coming back to it later and seeing how it's evolved or like, oh, people are touching it. They're doing stuff. They like it. You're using I love that somebody else has decided to edit that and keep it going and keep it fresh. So yeah, I'm I'm excited about that. I like donating things and having people care about them enough to work on them too. It may or may not look like that meme that's Spider-Man meme though at this point where they're looking at each other because that's kind of how the doc reads now that a couple of our Kubernetes docs read like that where they're like, no, you know, you and then you're like, which one though? Which one? So it's funny that like our governance docs do that. And of all the docs that you want, like a very specific idea of like what to look at first and what to do. It would be the governance docs. And the only I'm not saying we're not going to say anyway. It's being worked on though, right? Yeah, so awkward silence. Yeah. Okay. So one of the things I actually wanted to bring up just because it came up. So this came up when we were creating the content for the session is is that there are sort of multiple places you can look in the CNCF for what's required of projects at each level. And these multiple locations are not synced up. Yeah. I mean, like this started with what you need to become a sandbox project and what's on the document in GitHub. And what's on the form are different lists. And what's in the head of the TOC members are nine individually different lists. So I had to talk with, you know, I initially filed the PR assuming this had just been an omission from the form. And Liz was like, well, wait, no, that's not right. And so now we have a much bigger to do item of, hey, we need to actually have somewhere a canonical source of what the complete requirements are for projects at each level. And then that source should become the source of data for all other places where this is listed. So in the TOC meeting, did you say anything about like a site and any any other rallies rallies around that? No, thumbs up that that was they liked the idea. It was an issue that was a wait, that was in the previous month's meeting. Yeah. And then but any anything else as far as like resources or like any any folks to like help us out. Because like the thing is a thing about the CNCF site, right, is it's not totally open source or is it now? Or because I don't know, it's like a it's like a wordpress that a wordpress theme or something. I don't I don't remember. But yeah, there was like some, yeah, no, yeah, yeah, not be going, you know, this would effectively be a completely separate site. Yeah, that would be just Netlify. Yeah, when we're going to subdomain on Netlify and yeah, yeah, like the contributors theme. Yeah, the only new contributor website theme. Yeah. Yeah. Well, then let's do it. Yeah, then we can just let's we can advertise for it. Like I can we can start like getting on the horn. Maybe like put like a blog post out on those kind of like a proposal of what we want to do and see if anybody wants to help. What if someone who loves making websites and just start something and then that's what we point people to when we start talking it up. So we're not trying to like jump start the titanic here. That's wrong ship. But you know what I mean? Do it. Yeah, do it. Who's who's going to stand it up? Is Carolyn? Is that you? Was that you? Yeah, well, because I love making websites. Oh, my God. It's amazing to do it usually. I was like, I can't tell if that was sarcasm. If we want to keep the existing theme and look of like the contributors, I forget the name of the site. You know what I mean? We're made like the community site essentially and we published everything as a website. We want to just take that theme and use it then I can start putting content in there and organizing it. We can just iterate on it. Yeah, we just make it. Yeah, we also go ahead for sure. So we also have the team to leverage if we need to. Celeste and Nate who is new, but also working on websites like they've been working on the DEX website as well. And there is a website template already. So. Yeah, I didn't know that I would see. I didn't think that we had anybody that wanted to the stand the dang thing up. So that's why I was like, hold up. All right, let's get somebody to stand it up. So all right, Carolyn's like, all right, I dig it. Yeah, that's what they finally called it. Yeah, we can just take that or yeah, take their site and take all the content out and make a new one. Did you save the template stuff on or should I take it from this? Yeah, hold on a second. So Kubernetes probably has their own, but there is a CNCF template project for. Yeah, we have our own. We have a Doxy one. But yeah, it's in Kubernetes SIGs slash contributor dash site if you want to fork that. Okay. Yeah, I've seen this one. Perfect. Stand it up. Yeah. It gives me something to do when it's like eight o'clock at night and I want to do shoot. You should have said that earlier. I would have been in your DMs. No, I'm kidding. I know. Hold on. Oh, God. Hold on. Hold on, Carolyn. I'm about to home into your DMs so quick after this call. So this is a bit like the, so we had a working group naming leads call just to like catch up because the meeting is monthly and we just ended the call with screaming. Like the last part of the call was just like, should we just, you know, scream? You know, for a meeting that we all wanted to cancel and thought we had nothing to talk about. We're getting stuff done. I like it here. Carolyn, here's another one. Perfect. Thanks. And that one is already templatified if you want to use it. I know the, I know the Kubernetes one probably a lot more time was spent on it though. So well, you know, I can, I'm, this is what I do is I just steal existing websites and Frankenstein them into anyone. So it's like, good. My, my space. And I'm down with that. That's why I tell people all the time. I'm like, why are we reinventing the wheel here? Yeah. Like I, I say that every day at least once. I'm like, why? So I love it. Yeah, we did. So like for the naming stuff, we did a panel to talk, to start talking about the inclusive naming initiative and everyone on the panel was basically, I was like, I'm an engineer. I don't want to do things twice. Like, can we just lay down a framework that works for everyone and try to adopt it everywhere? And they're like, yeah, we don't want to do these twice. That's why we form this thing. I have to keep up with you because we actually have an internal group at Red Hat naming group at Red Hat now. Yes.  We're already connected with them. So we've got, we've got Red Hat, IBM, Cisco, VMware, Kubernetes naming and working on standard spot is so it's going to be a big, big old party. So at this point, I'm still just looking for and replacing master, slave and whitelist, blacklist. So anybody pulled out or anything else? That is, that is the point that I feel like everyone is at agreeing to. So with Kubernetes specifically and probably a lot of other places, it's basically people, you have like, you have a set of people who are interested in making changes or and maybe new contributors come by and they're like, yes, let's make this change. I saw this issue was open and I started searching where in place, replacing everything and you're like, oh, hold on, hold on, don't do that yet. Cause you just changed an API and we have an API deprecation policy, yada, yada, yada, right? So yes, that one too. So trying to figure out like the people who were ready to run, but giving them a framework to run with. So we landed the docs for basically like recommendation or workflow and a template and a language evaluation framework to give people kind of like a starting path. And then I think Aaron landed the first thing using that workflow or rather we have to review it, but it's, it's master to control plane, right? And then we're going to layer on top of that one. Like QBADM has some work and flight as well already, and they've started making changes on the website. So, you know, it's going, it's going all right. I think the, what's cool about the language evaluation framework or you start to look at orders of concern, right? They're, you know, so our first order concerns are like language that is very clearly causing harm, right? In some way, shape or form and eliminating it, biasing towards eliminating it as opposed to carry on a thousand year discussion about it, right? And then as you go down the orders of concern, it kind of goes into well, is the language ambiguous, right? Would we be better served by making this less ambiguous, right? So, so yeah, the, I think we're starting to move into like we've identified a few things that are clearly like we don't want these. And then, you know, the next piece is like, okay, we'll lay down the recommendations for them, execute on that, hand it off to the code owners or the content owners. And the next piece for us is that, you know, finding people who are interested in doing the work now that some of it is better defined. And then also starting to think about those second and third order concerns that, you know, that are maybe a little bit more ambiguous, right? So, yeah, because I, well, the, I just find it interesting that a lot of people have had all these naming groups and that sort of thing. And we're still currently only targeting the same four words. Yeah. That we identified early on.  Oh, for sure. For sure. I mean, my, my personal and within our community, my, my, my personal thing I'd like to get rid of is, yes, pets versus cattle, but the, which does have a religious defensiveness angle to it. But yes, yes. And also because it's trivial, right? It's not, nobody uses that in an API. So it's not like we're needing to have a deprecation process. We can just replace the phrase. The, the Petset discussion is good. There's an super old one from Kubernetes. Oh, yes. Well, no, that was, it's like, it's like, it's like, why is this still Petset? And I'm like, because we forgot to rename it. We always, we always had it on the roadmap that we was going to get a long term name that was not going to be Petset. And then we didn't. Priority long term. That's how a lot of these things come around. Yes. Yes. It was like, oops, this is going to be 1.0 soon. We kind of need to rename it. Then like Minions was another one too, right? Oh, yes. Yeah. Yeah. The, so I kind of just want to, I need to start coming to your meetings to just listen, because this honestly, I already, I feel like I learned a lot and I just, I'm just listening to like a podcast. Oh, so actually the next naming meeting is this Monday, or this coming Monday. If you see like a Phantom Paris with no video, that's just Paris is podcasting. Spooky Paris. Yeah. And then we have to figure out like how to schedule these, the larger initiative calls, because that should be fun. All right. So we want to do projects needing assistance. Well, we don't want anybody to be online. I actually hadn't realized, if I'd realized that Charles was on the line, I would have asked him to speak up earlier. Yeah, he's not paying attention. I was not paying attention to who was dialed in. He said a words. He said some words. Yeah. He just said I'd be go. I mean, he's going to be mostly involved in the Contributive Growth Working Group. Yeah. Yeah. I'm just great. I love that.   And we're like, we have that. We have that. Come on down. So it's nice to know that some of the ideas that are kind of generated from this group are having impact already, right? That's good. The, okay. Is there anything else? How are y'all doing?  I'm like, Oh, right. We just switched to daylight savings. We just switched off daylight savings time on like Sunday. That was less than a week ago. How is that less than a week ago? It was like a kick in the teeth on top of everything else. I was up the whole time and I was like, what just happened? It was like looking at your phone and then you're looking at the microwave and you're like, wait, when? Yes. Oh, is that today? The, um, so, yeah. The, um, I mean, actually, I, I generally kind of like the week after switch back to standard time because I have all these early morning meetings. And so that's like one week where it's a little bit easier for me to get up for those early morning meetings. Assuming those meetings are set in US time. If you're set on European time, it doesn't help me.  Sounds like we're finished. No, we're not. No. Stay forever. Tonight's, well, tonight's bonfire night in the UK. So it's Guy Fox Day. But there's no fireworks because we're locked down. So I've, but apparently like all of my neighbors are doing fireworks. They've been watching them out the window. Oh, so you need to tell me you're not going to set off any room and candles just like open, you know, open the window. Come on. Go through the neighbors window. I live, I live in a block of flats. I think these are people with like nice jars who are setting off fireworks, but there's loads of them. So I'm going to go on insurance company calls us tomorrow from watching the video. Hi. We just wanted to speak to you about a, a claim that was made. Nice seeing you to pleasure everyone. Stay, try to stay sane. See you soon. Do some refreshing. All right, later.


So in this short video, I'm going to show you how you can edit Wikipedia in the live space So I'm going to navigate first of all to the article. I want to edit on global health and You can see that it's edited Quite often So what we want to do is when we're going into edit a page. We need to be logged in. So I'll log in With my username and password I'm going to click on edit to start editing the page because if I click edit source this shows you the source code which is a bit More tricky for me, but you can use the magic pen here as well to switch to visual editing Which is this edit button as well. So you've got two ways of accessing the visual editors drop down menus But because this is in the live space of Wikipedia anyone else can edit it at the same time And what we don't want is for there to be any edit conflicts Because you can't have two people Saving the page at the same time and having two different versions of the page So one person would always lose out their edits and we don't want that at all So what I'm going to do is I'm going to put a little template on The page to make sure that other Wikipedia users can see that I'm editing it at the moment So that they won't edit it at the same time. So it's insert template And the template I'm going to use is called in use Two separate words in use. I'm going to select it and Insert it. I'll show you that one more time I'm clicking edit to go in the page And then I'm clicking insert template and typing in use And clicking on the first one there And insert what that does is that adds a little box to the top of the page That says this page is going and undergoing a major edit for a short period of time And to help avoid edit conflicts, please do not edit this page while this message is displayed But Importantly, no one will be able to see this until you've finished the save So why I'm going to go up here to publish changes the blue button And it says publish, but really it just means saving the page So I'm adding the in use template because we always it's always a two-step save process on Wikipedia and I'm just describing the change with a short edit summary and clicking publish and Now that box that will appear and other Wikipedia editors will see that it's undergoing a change and You can see why edit summaries are important by clicking on the view history there. You can see my Username and a date and time stamp and a little edit summary Make it a very clear what change was made when and by whom and these are all permanent links Importantly, so if I go back to the page again Now no one should bother me while I'm making these changes and I can go to the section. I'm interested in and add some content and Make sure that I'm adding citations and then importantly when I'm finished I will click to describe the change added new section on Whatever I'm writing about and then click blue but but publish changes button again to complete the save and That's it. That's how you would Edit a page in the live area


TfNN, Deadline News Update. Hi everyone, on this fourth day of May, we've gone May on Friday, so the new month you can see the candle, the green candle, we're having an inside bar so far, we've just barely begun. And all I need to see sometime in May doesn't matter when, something doesn't have to be closed, it just needs to be a pop above, 24,764.77, going to .78, starts a new leg A to the upside. That's quite a distance from where we are, 23,520 down 203, went to a lower load today, we went to 23,602, the recovery hour was 24,660 on the 29th, you can see this is arch formation, really a sideways picture that we're looking at here. The key level to hold over the next three days is 22,941, closing below that essentially says quite a bit more time to come in the dating, we'd be charged with just guarantee that you're going to make a peak beam this week, the S&P, this is the S&P 500, index down nine at 2821, made a high on the 29th of 2954,86, trading now at 2821, had a low today of 2797, you can see this uptrend lying here, needs to hold it, it is below the nine, but just above the 14-period moving average, so there's only an indication of a cell signal, it starts to close underneath that, close anywhere from 2818 down, and you're going to start to get a cell signal, maybe even an immediate cell mode, but in the meantime back at the ranch, the queues have been really good, they're up at $1.34, the ended X100, 2204 was the high on the 30th, three days ago, the low today just hit the 14-period exponential moving average of 21112, and it bounced exactly, that's right on the number, that's good. So what we're all looking at right here is that they are probably the high tech stocks holding very well, the IWM that's a small cap down $0.95 and 12419 kind of took all that energy to the upside out with the last three days action, and if you look at gold, starting gold over the weekend, I still see this in a trading band holding very well, high level consolidation after a really great move from the 1450 area in gold up into the 780s, and now what we're looking at is 1714, it's consolidating, hey look at this, the dollar has made the H pattern to an M pattern, nice strong move to the up 41 cents, and crude oil, all right, now crude oil is, oh I missed it, I'll get it as we are going to close.


Now we have standalone bootloader that is able to launch a target application. The next thing we need to do is to make this bootloader trustworthy. There are two conditions for secure boot code to work properly. The first condition is to ensure the unique boot entry. That means the MCU boot mechanism has to make sure that the secure boot code is always executed after reset. The second condition is the immutability condition, which means the secure boot code and the public key that it will use for the authentication of the application cannot change in any way. If those two conditions are fulfilled, then you can trust the secure boot code you have. Then next we will see how to secure the boot entry on STM32. The secure bootloader relies on the first code to be executed after boot. On STM32, this is mandatory to set up the option byte so that boot from Flash is selected. On some STM32 families, this requires RDP level 2 to be activated. On more recent STM32 series, some other security mechanisms can also ensure the booting from internal user Flash with only RDP level 1. Here is the general principle of STM32 boot. All STM32 are able to boot from at least three different regions. User Flash, system bootloader and internalized RAM. And the selection can be done with option byte and possibly with boot 0 pin as well. As STM32F series, RDP level 2 can ensure that the MCU always boot from internal user Flash. The only exception is F1 because on F1 only RDP level 1 is supported so a secure boot cannot be guaranteed on F1. F7 introduces also the boot address 0 and 1. Those option bytes can also be set both to the same user Flash address. And this will improve the boot entry robustness using RDP 2. This is the general boot principle of STM32F series. So in case RDP level 2 is not set, then the boot 0 pin level will first decide whether the system will boot from internal Flash or not. In case it is low level, then the system will boot from user Flash. Otherwise the boot 1 pin level will further determine whether the system will boot from internal RAM or the system will loader. But in case RDP level 2 is set, then the booting from user Flash will be forced. On F7 series, there are two more option bytes introduced. Then the boot pin will decide whether to use the address coming from boot address 0 or boot from 1 option byte. Both address could be programmed to point to the internal RAM or system boot loader or internal Flash. But when RDP level 2 is set, it's not possible to boot from RAM anymore. So those address could only be programmed to boot from user Flash or the boot loader. But in such case, only very limited features will be provided from the system boot loader. So in such case, we should enforce both address to point to the user Flash address. But the low power series L1 is the same as F family. On L0 and L4, there is additional software configuration option introduced in the option byte. So on L0, it is input select option byte and on L4, there is the in software boot option byte. And associated with this selection, there is an additional input 0 option byte instead of boot 0 pin. For L5, we will detail it further later on. So here is the boot principle of L0 and L4 series. When RDP is not set to level 2, then depending on the configuration of the boot pin selection, the next decision is made by either the boot 0 pin or the boot 0 configuration. Both could lead to boot from internal user Flash or could be further determined by unboot 1 option bit to boot from either system boot loader or SRAM. But when RDP is set to level 2, the system will always boot from internal user Flash only. As same as 32L5, as described in MOOC part 2, it provides more configuration options for securing the boot entry. The configuration depends on TZEN option bit setting. When TZEN equals to 0, the boot options are a mix of between L4 and F7 using in software boot 0 and boot address 0 and 1. When TZEN equals to 1, then the boot option enable only two possible targets. One is the secure boot address 0, the other one is the secure system boot loader, which is also known as RSS. On L5, there is also one additional boot log option. This will bypass the boot 0 configuration. First, let's take a look at the boot principle when TZEN is 0. So similar to L4, there is the unboot and software boot 0 configuration bit to determine whether to look at the configuration from boot 0 pin or boot 0 option. And both could be configured to use the boot address coming from boot address 0 and boot address 1 option byte. Both option bytes could be configured to point to the internal user Flash address or to the system boot loader or internal SRAM. But when RDP is set to level 2, then the boot will be forced to the address from user Flash. Then let's take a look at the case when TZEN is enabled on L5. When boot log is not yet activated, again, this unsoftware boot 0 option bit will decide whether to take the configuration coming from the boot 0 pin or the boot 0 option. And both could lead to the booting from RSS directly or to use the address coming from the secure boot address option byte. And this option byte could be programmed with an address coming from the user Flash or RSS or internal SRAM. But an address in SRAM is only allowed when RDP is set to level 0. As long as RDP is higher than level 0, then valid address in the secure boot address option bytes can only be an address from user Flash or RSS. There's no more chance to boot from SRAM in that case. And that is the same when boot log is activated. Boot log will bypass any configuration from the other boot options or boot pins. The boot mechanism of SM32WB is the same as L4, so I will not repeat the same here. The boot mechanism on SM32GFamily is similar to L0, so there is also the unboot select bit which can force the configuration coming from software. But GFamily also introduced the boot log option, which will bypass all the other boot settings in option byte or boot pin and force the boot from user Flash, regardless of the RDP level. And the boot log can only be deactivated when RDP stays in level 0 or with a RDP regression from level 1 to level 0. That means activation of boot log plus RDP 1 makes the boot from Flash immutable. It is almost the same as RDP level 2. The debug port will automatically be disabled after reset in such kind of configuration. Of course, RDP level 2 can still force the boot from Flash. So on G0Z4, similar to L5, there is the boot log option. When this option is not activated, the rest mechanism is similar to L0. So there will be the option to select boot pin or boot 0 option bit, whether to select the user Flash to boot or to boot from system bootloader or RAM depending on the configuration in boot 1 option bit. But when boot log is selected, is activated, then the only possible boot source is the user Flash. That is the same when RDP is set to level 2. Similar to F7, SM32 H7 family also has two boot addresses defined in boot address 0 and boot address 1 option bytes. And both could be configured to boot from user Flash, system bootloader or RAM. Selection of the two addresses is done by a boot pin. On some of the H7, which has the additional security features, there is also an additional secure bootloader area embedded. This is also known as RSS, root secure service. When security is activated on those devices, boot is forced to RSS instead of normal system bootloader. When security bit is activated, a secure user memory area can also be defined. RSS will always jump to an address within the secure user memory as long as the secure user memory is defined. Here is the boot principle of H7 series. As long as security is activated, the system will always boot from RSS. And in such case, if secure user memory is also defined, then the RSS will always jump to the secure user memory address in the user Flash. If there is no secure user memory defined or if security is not activated on H7, then the boot pin will determine whether to use the boot address coming from boot address 0 or boot address 1 option bytes. And both could be configured to point to an address from internal user Flash or system bootloader or SRAM. But in case RDP level 2 is set, then the boot address will be forced to user Flash. We have talked a lot about how to make sure the unique boot entry on SDM32. Now let's take a look at how to ensure the immutability on SDM32. The first step for immutability is the use of write protection mechanism. This mechanism always apply on a per flash sector basis and WRP mechanism can be activated by option bytes. However, option byte can be modified if RDP is not in level 2. So RDP level 2 is also required to make sure option byte will not change. On some recent chips, including secure user memory, the immutability can also be ensured as long as RDP level 1 is activated. SDM32 G0, G4, H7 and L5 have the ability to define a secure user memory. When running code inside secure memory, it is possible to erase flash inside this secure memory area. But when running code outside secure memory, the flash erase is not possible anymore. That means, for example, if we put the secure boot code inside the secure user memory area, after jumping to the application, the application will not be able to make any modification of the bootloader code area anymore. In case there is still the concern of any possible modification happen within the secure boot code inside the secure user memory area, then the WRP can still be applied inside the secure memory area. In that case, to get the immutability, it is the same as the other SDM32, WRP plus RDP level 2. Summary of the secure boot protection. In order to trust the secure boot code that we have, there are two conditions to be met. First, we need to ensure the single boot entry on SDM32 that could be achieved by the mechanism of RDP level 2, boot log and secure memory on H7 for instance. And the second is to ensure immutability. That can be achieved by RDP level 2 plus WRP and partially with RDP 1 and secure memory. The association of single boot entry and immutability makes the secure boot as if it was ROM code. This is what we call root of trust. We trust that the code excluding off the reset is always the same. Secure boot protection variations. Depending on the environment constraints, it is not always necessary to have the maximum protection. RDP level 2 for instance. But in that case, a detailed analysis has to be done to understand the weakness of a setup. For instance on SDM32 H7, using secure memory plus RDP 1 plus WRP inside the secure memory can be enough as long as code inside this area is not able to change this configuration. Such setup could be useful to still have the ability to change option byte if this is necessary. Now let's have a hands on of the boot loader immutability. The goal of this hands on is to show the different steps to add immutability protection to the simple boot loader, build the binary of both boot loader and application and program to the board, run the device and run a test from application of the immutability of the boot loader. Thank you for watching.


All right, here we go.  Yeah, that's great Hello, Bailey, my name is a Margaret. I'm just after a pick up order if that's possible today at all Pick up please if possible. Yeah, I'll um yep So I might haven't had dominoes for a while But I might get the barbecue chicken and I'll get the one on thick crust. Thanks Yeah, yeah, that's the one thank you and then look I'll get I'll get a couple of meat lovers obviously classic everyone loves bloody meat lovers and What sort of is this some sort of um some sort of meal deal we can do here like if you order heaps of pizzas is there some sort of meal deal that we could do or is it just sort of You know too big an order for that Okay, let's do that. Let's let's take in a garlic bread and a bottle of coke and another couple of peace orders coming through Do you guys have the pepperoni at all for the pepperoni on the thin there on the thin crust? Okay, great, so there's a couple more. What have I got written here? And the oh yes there can I also get a vegetarian pizza. Do you guys have the vegetarian pizza? Right, what have we got there can you read that order back to me? So how many garlic friends have we got so far Oh, we have one guy for in the balls. Listen. Look, we'll add another couple of garlic breads to it And maybe another two another two bottles of coca-cola And the wings do you guys have any chicken wings at all we have a chicken wings We got either a father of seven of those. Yeah, then a nine to nine. Yeah. No, look, it's lovely supporting small business Um, look can we cancel that? Oh It's so hard to redo it It's so hard to get that scream right.


Vinny! I knew you'd come over here. I knew you'd come here. Good bird! I know it's dark guys but if you think someone to watch TV comes over to hang with me. Such a good little bird.


Hi everyone. Welcome to my talk. My name is Felix Schuster and today I'm going to talk about scalable competition computing on Kubernetes with Mabel Run. A few words about myself. I'm the CEO and co-founder of Azure Systems and we are a startup building open source software for competition computing and one of the tools that we build is Mabel Run and Mabel Run is the extension to your existing service mesh that makes your deployment a confidential deployment. So what does this mean? A couple of things. So first this means that all your data remains encrypted all the time even at runtime during processing. Next it means that you can cryptographically verify the integrity, the topology and functionality of your deployment and you get protection against very strong attackers like malicious cloud admins, malicious Kubernetes admins or even physical attackers like like data center insiders. So this sounds pretty cool right and it allows you to a couple of things. So it enables you to retrofit your existing Kubernetes deployments with top-notch security and it allows you to essentially keep the cloud provider out of your trusted computing base and use the cloud with more confidence and move more workloads to the cloud and it allows you to build exciting new applications that provably preserve the privacy of your data sources. Yeah so this possibly sounds too good to be true and so how do we do this? Obviously there is no such thing as magic so we rely on a new technology called confidential computing and in the nutshell confidential computing is all about running sensitive workloads in so-called secure enclaves and these enclaves are available on many recent server CPUs for example from Intel and these enclaves have three defining properties. So they can run arbitrary software in strong isolation and no other system component like the operating system, the hypervisor, other apps or even other hardware components can look inside the enclave or interfere with an enclave. The second important security feature is runtime encryption so everything that is stored or is running inside an enclave remains encrypted in main memory even at runtime and the final property is verifiability so you can get a certificate from your CPU that says okay hi I am a genuine Intel CPU and I'm running this piece of code in my secure enclave and this is a very strong property and we use this to build entry and verifiability for your whole cluster. So confidential computing hardware is widely available and you can get it in your favorite clouds and we for now with Malrun only support Azure but we are working on bringing it to other clouds and other hardware members. Okay so let's dig into the details so how do we create a confidential deployment? Essentially there are two steps first one you need to build confidential containers and that is fairly easy so if your app is entirely written in go then you can just use our open source go framework to just take your app and package it for an enclave. So that's done so the the last and final step is to securely mesh your services inside your your deployment at runtime and this is what Malrun takes care of and this requires a couple of steps. So first we really want to have container to to container attestation so one container running inside an enclave needs to make sure that the other container it's talking to is also running inside an enclave that's very important because otherwise it could have mock-up enclaves that could just steal secrets. Next we want to have deployment to client attestation so we want clients of our deployment to be able to verify the overall integrity and functionality of the deployment. Next we we need MTLS to not terminate inside sidecar proxies but directly inside a secure enclave because otherwise it could be intercepted by attackers and we need enclave-based secrets management so we can't rely on Kubernetes for secrets management because in our case Kubernetes is running outside enclaves so it is not part of our trusted computing base and the attackers we consider can just access the Kubernetes secret store and finally we also take care of of code updates in a secure way and from a 10,000 feet point of view this is what the workflow looks like when you install Mabura. So you start with an empty Kubernetes deployment and you do as normal you install your favorite service mesh for example Linkerd and the next thing you do is you install Mabura using the Mabura CLI and then you do a very important step and that is you define in in the file called manifest you define in JSON all the confidential computing specific aspects of your deployment and the final step is you install your app as normal and if you packaged your app with with ego then your containers will automatically contact the Mabura coordinator over secure and mutually attested TLS connections and Mabura will make sure that these containers adhere to the manifest and only if they if they do if they comply with the manifest Mabura will issue TLS credentials to these containers and will also send over the the other secrets and the next the client can come the client can establish a secure connection to you to your deployment and this connection also terminates directly inside a secure enclave so it's really end to end secure and what the client also can do is the client can get an attestation statement from the Mabura coordinator and by ex ex exon mining that statement the client can convince themself that this cluster or this deployment at tears to what is specified in this manifest and this is a very powerful feature okay so there's one app we like to use for demo purposes and it's emoji voto it's the default demo from the link of the service mesh and if you want to run this in Mabura and super simple you just package the three services using using ego you don't need to change a single line of code and you define the manifest the manifest in this case is only 130 30 lines of of jason and then you're good to go and you can just use marble run and let it take care of the rest okay and here's here's the the manifest for the emoji voto demo and the first section we define all the enclaves that are allowed to run in our deployment in this case we have here three enclaves and they are defined by by the by the by the signatures fingerprint and down here we define the the parameters for the enclaves in this case most environment variables but this could also be files for example and further down we define the secrets that live inside this deployment in this case we just have one secret which is a web search and these secrets get automatically injected into the right enclaves and marble run takes care of that right this was my quick introduction to marble run i hope you find this interesting to summarize what marble run does is it turns your existing deployment into a confidential deployment and this is super exciting because this keeps all your data encrypted at all the times even during processing and it allows you to verify the integrity and functionality of your deployment even better it protects against very strong attackers like malicious kubernetes admins malicious cloud admins or malicious datacentro workers and it enables cool new applications that preserve the privacy of your data sources next steps um check on marble run.sh for code further examples and if you have any questions feel free to to join the discord and you can find me on twitter at flxflx and yeah let's keep in touch let me know what you think and goodbye


Moving away from housing now to education, where the minister, Professor Tahir Mahman, says, libraries are the custodians of knowledge and information, and hence the need to develop effectiveness of promoting reading culture among the youth. Professor Mahman stated these in Undo Town, Undo State, are the commissioning of a modern academic library built and donated by the National Coordinator of the Progressive Change Agency Initiative, Dr. Shun Bosedi Osamai. Also a staff of ADIME Federal University of Education, Undo Town. The minister who was represented by the Deputy Vice Chancellor of Academics, Federal University of Technology of Kura Futa, Professor Tahir Mahman, noted that in the last couple of years, the reading culture has been on the decline, especially in Nigeria and Africa in general. The acting Deputy Vice Chancellor ADIME Federal University of Education, Undo, Dr. Samuel Akin today and the donor, Dr. Shun Osamai, also highlighted the importance of libraries as motivators of students to cultivate reading habits. I am glad to be the Deputy Vice Chancellor of ADIME Federal University of Education, Undo State, to host the immediate utilization of these enemies. May I encourage the university and its community members to take advantage of the library's resources, participate in this program, and support its continued growth and sustainability. I want to congratulate the university again for having this first of its kind, not coming from the government, but from an individual. There's no job satisfaction. Most staffs are not happy with what is happening in the educational sector. And the truth of the matter is government alone cannot do it. If we leave the educational sector alone in the hands of government, then we are not serious about developing the educational sector. If truly we want development for the sector, it is the duty of every one of us to identify whatever things we can do within the system and find their way to do it. This Osam donation is the first of its kind by a savvy staff in the School of Languages and we would be happy to be a member of the University of Education. For this remarkable note, let me say that I am short of words of my presentation to the dole, Dr. Sherwin. Without missing words, this is a very well-taught