On this day, there's a lot of theatrics going down at Maria Montessori Charter Academy in Rockland. And enough makeup and fake blood to impress Gene Simmons. Corn syrup, dyed red. The multi-purpose room is now a dressing room, where the school's second through sixth graders are being made to look like victims of a fictional earthquake disaster. From here, they go back to their classrooms and wait. I got two black guys and bruising behind my ears. Wow, does that hurt? Sort of. These kids are getting into character while waiting for the alarm to sound. That's when their acting skills will be put to the test. That is a grody wound. I know. They're wonderful actors. Yeah? Yeah. How about you? You having fun with this? Yes, I love this. It's great. We look forward to it every year. It's really cool. This is the seventh year they've held their annual Team Community Emergency Response Team Mock Disaster Drill. Everyone has a role and a responsibility, including Incident Commander and Public Information Officer. We're dealing with parents who may be freaked out. Our overall job is to give the right amount of information and good information to keep everybody calm. In another classroom nearby, members of Team CERT are gathering their gear, reviewing their plans, and learning the disaster scenario they're about to face, a large earthquake that's damaged their school and the community. Fire crews and police are delayed due to down power lines, which are blocking access to the school. They're not allowed to go to the injured students, but it's something they've trained for. They learn to do scene size-up, assess the situation, they learn what safety equipment they need, they learn how to suppress fires, they learn triage first aid, all of these excellent skills, and then this is their chance to apply all those skills they've been studying the whole year. This is a earthquake drill. Right now, drop cover and hold on. Drop to the floor now. Let's go. Let's go. Team! Team! Let's go. Let's go. Let's go. Team! Let's go. Inside the first room, teen-cert members put their training into action, under the watchful eyes of Rockland firefighters. Team members assess each victim's injuries, red for the most severe, or yellow, or black. What does black mean? Dead. But time's ticking, life's at stake here. Hey guys, remember, 30 seconds. 30 seconds. Keep moving. The victims are moved as soon as possible. What was once the dressing room is now the triage area. Everybody has a role to play. PIO, who by the way, is a little too enthusiastic about removing this reporter from the incident scene. Are you throwing me out? Yes, I am, sir. Very kind. But I'm just doing my job. So am I. CERT is a program of the Federal Emergency Management Agency. It educates people about disaster preparedness for hazards that may impact their area and trains them in basic disaster response skills. Teen CERT members are usually high school kids. Here, there's seventh and eighth graders. And among the youngest participants in the country, whatever the age, these volunteers learn about and demonstrate the safety practices we at Cal OES advocate daily. One hour later, it's all done. The last thing I heard was they've cleared all of the living out of all the rooms that were hit. So they've cleared over 100 victims, about 125 victims right now. Success, which for most of these kids will carry on beyond the campus. They'll have that training, they'll have that confidence to be leaders in their schools and in their homes and in their communities.


Hi team speaking. Hello team. This is Jesse of Hong Kong electronics. Hi Jesse. How are you? Well, I'm a bit disappointed with your latest CDR shipment actually We received here this patch this morning and we're not very happy with it I'm really sorry to hear that. Would you mind telling me exactly what the problem is? Well a model a the quantity is wrong a model B the pattern is wrong a model C The CDs are simply not working and a model D. You've overcharged us. It's really terrible I'd like to know what you're going to do about it Well, it's certainly not our intention to dispatch the wrong goose to our customers or to make mistakes with prices Jesse I'm very sorry about this and I'll look into this matter immediately. I Hope you could fix it as soon as possible. I assure you that we will rectify the situation as quickly as we can I'll attend to the matter personally. Could you please fax me the details? Sure, by the way, when can I expect to hear from you? I'll get back to you by the end of the day


Hello. Welcome to the second flood warning public meeting. This is a progress since our first public meeting, which was held on the 23rd of March this year. And I want to welcome you all to this exciting project that we're doing in stormwater management to enhance our flood warning capabilities citywide. So my name is Ranjan Esmutaya. I'm a senior professional engineer with the Stormwater Division Transportation Public Works. And you all can see my email down there. It's my first name, dot last name at FortworthTexas.gov. And if you have any questions related to this project, please feel free to email me. So I'd like to acknowledge the funders for this project. This is a matched project. The match is being cost shared by the city and the Texas Water Development Board. And the Water Development Board is using the flood protection grant that the governor created in 2016 to fund these types of projects. So we appreciate the support provided by the Texas Water Development Board. And we also acknowledge the 60th anniversary of the formation of the Water Development Board. They've been doing great work since their formation to help with the water resources, the water supply problems that the state encounters. So I'd like to acknowledge the contributions made by several agencies to make this project a reality. There are departments within the city, the Office of Emergency Management, the Stormwater Transportation Department. There are several people that have contributed towards where we are right now. And externally, the National Weather Service has provided feedback and other agencies such as the USGS. The neighboring cities have also contributed towards hosting weather stations that we will talk about here in a little while. So I want to acknowledge some of the neighboring cities that have contributed towards the IRFs. I also want to thank you. Thank you for staying engaged and involved and providing feedback. So the purpose of the grant is to develop a citywide flood warning system that is reliable and relevant. We'll be using the existing network that we have. It's called the High Water Warning System. We'll make enhancements to that. And the focus on flood warning is to collect the data that's being collected at weather stations, at high water warning sites that monitor the water levels and provide that to the public and emergency responders. And the third and final purpose of the grant is to develop a flood response plan that identifies the major threats and the response to the flood threats that the city potentially faces. The grant is, as I mentioned earlier, a cost share and the city is providing the match in terms of procurement of the software, consulting services and through in-kind travel match as well as in-kind staff time. The water development board portion of this grant is being used to procure equipment for this grant project. So I'll go through the schedule in just a little while, but we have also requested a nine-month extension for this grant. It was ambitiously aimed at about a one-year project. We believe that we need another nine-month to comfortably complete this project. So here's what I had shown earlier. The first public meeting, you all had attended the March meeting. We were scheduled to have a meeting in June-July if everything was crunched down to one year. But as of now, we believe that we need a nine-month extension. So here we are in October-November. We had a second public meeting. And we have made good progress on the software. We got about halfway through on the equipment installation process. And we are about 60 to 70% of the way there on the flood response plan. So what's the new schedule going to look like? We anticipate finishing the installation of gauges around May-June timeframe of 2018. We'll begin the installation of that equipment, which will consist of weather gauges and the telemetry around January-February. The software itself has gone through a procurement process. We are in the process of writing a contract or inking the contract. We have negotiated the contract. We just need to get approval from the council for the software contract. And then that implementation will run through May-June timeframe. The flood response plan, as I mentioned, also has made relatively good progress. We got to refine the flood response plan developed to date. And then we'll run it through a tabletop exercise, receive public comment, receive external agency comments. And then we'll revise that flood response plan subject to the lessons learned. And then it'll be submitted to the war development board. The grantor, the war development board, requires a final report on this project. And we will generate that during the end of the project period. We anticipate holding our second public meeting once all these three main components of the project are complete. So here's our existing system that we plan on enhancing to create this flood warning system. The high water warning system is based off of alerting roadside drivers to high water on the streets at 52 hazardous slow water crossing sites. And the data that's generated through the alarms when the roads get overtopped is submitted to the first responders. So these are real time alarms that take place in real time as the water starts overtopping the streets. But you see on the map are the different faces that the high water warning system went through over the years. It began around 2006 and then got enhanced subsequent to that to the 52 current sites that are being monitored. The data itself is collected in these field sites and then transmitted to a receive station at Bernard Plaza. So here's a little bit more detail of that. The water levels are measured by pressure transducers. And then the data that's collected again in real time is transmitted from the field sites to the receive station at Bernard Plaza. My mouse is circling the internals of what the receive station looks like. So data comes into an antenna at the top of Bernard Plaza and then in the building there is a receive station that consists of receiver decoders that convert the data after it's gone through some radio frequency filtering through these cavity filters that get then decoded to data that's sent to a server, a flood warning software that's hosted on the server, processes the data which then gets cleaned up and is used to generate alarms as well as used to generate display of the data. I do want to talk about the rain gauge system. At these low water crossings there are rain gauges. There are about 39 rain gauges spread out throughout the city as part of this network. Eight of those rain gauges are on dedicated weather stations that measure not only rainfall but other things like air temperature, barometric pressure, humidity. So the protocol that's used to communicate from the field is called alert. This is a 1970s based technology that transmits whenever there is a trigger like if the tipping bucket tips over in those rain gauges that creates a trigger that's sent out from the field to the receive station at Bernard Plaza. So all sites that collect data report whenever there is a trigger event. Either the pressure transducers are measuring water levels and that water levels get transmitted in real time or the tipping buckets measure in real time. As well as other data that's collected on the sensors or the batteries that power the system, the solar panels. So there's a lot of data that's collected and sent from the field sites. Of course not on real time like the rainfall and the water levels but they are transmitted. There are close to, totally across the system, there are close to 7 to 800 different types of sensor data that's generated which includes the batteries, the solar panels and things like that in addition to the sensors that measure the water level and the weather. This alert protocol has no error correction so whatever data is collected is transmitted. There is no receiver to transmit a correction protocol employee to check whether the data is valid or not that's transmitted. And then during high rainfall events as you can imagine these tipping buckets and water level sensors get very busy and there's a high level of traffic, radio traffic generated when there is a rainfall event. And if you were to try to expand this network your data loss gets even worse. The good thing is this technology is outdated and there's more recent communication protocol. However there is a little bit of a compromise in terms of what you gain in terms of the security of the data transmission. And that is that the alert transmits very quickly whenever there's an event it transmits to the relay station or the receive station in Burnett Plaza and that transmission time might be in the millisecond range. However you do have this problem of the data collision. The server that's receiving the data can only deal with one transmission at a time even though it's within the millisecond range but if you have lots of transmission that just collide with each other that becomes a big problem. So that's one of the limitations of this alert system is the data collision is the biggest issue. So what does a flood warning system look like compared to this high water warning system? We will continue to use the high water warning system with its field sensors which is mainly big gear towards alerting the roadside drivers of floods at these low water crossing sites. So that will continue to run. But we'll be enhancing that system with additional rain gauges. We'll be improving the telemetry. We'll be improving the software. So the experience that the public gets from this improvements will be significantly more than what's currently available. And the data processing and things like that also will get enhanced through use of the alert 2 communication protocol. So here's the alert 2 communication protocol. It's an upgrade to the older alert protocol. It is designed for higher transmission rates and it uses GPS clock technology to keep up with the transmission and the receive time. So you don't get data loss because you got a time slot associated with the transmission. There is error correction in the protocol. So there is the transmission structure, the bit data that gets transmitted has error correction codes built into it so that the receiver can validate the data as it's being received. And the receive, actually the transmit message can be variable length instead of a fixed length as it is in alert. Now there is as I mentioned a compromise and that is that the alert 2 because it does a lot of error correction and uses the error correction methods. It does have a latency period of about one to one minute or so from the time that the data is collected. And then the alert 2 protocol is what they use in the system. They are in Harris County and during Hurricane Harvey it performed really well. Not much data loss. If there was any data loss it was very minimal. So as we transition from the current alert to the alert 2 protocol we'll be doing it in phases instead of pulling the switch immediately. The new weather stations that are being installed as part of the war development board grant effort will be placed on alert 2. And there will be alert 2 equipment at the receive site at Burner Plaza as well as we'll have a second receive site at the Bridge Street tower. So we'll have two receive sites just in case Burner Plaza goes down for whatever reason. And the new alert 2 will be put on a third frequency. We currently have four frequencies that we use. Two of those are actively used for alert. One of those two remaining two will be used for the alert 2. And then over the years over the coming years as we get more experience with alert 2 the alert protocol will get decommissioned. And then all the transmission sites the current high water warning system transmission sites will be put on alert 2. There will be some additional modifications made. Currently all the sensor sites transmit have radios and they transmit to Burner Plaza. So that creates a lot of communication overload during an event. We want to try to minimize that. And we're going to do that by having the master controllers that are located at these remote sites. Be the only ones communicating to Burner Plaza and then the localized communication between the field sensors will be handled by the master controller units. So I want to step back a little bit at this point and provide and I apologize as I move the mouse back and forth. I'm trying to make sure that you all can see this clearly. Okay, let me see if I can maximize this so I don't have to do that. Yeah, I don't have to do it. So the idea with this with the citywide is that we are going to be locating a various number of rain gauges. We think about 20 different new sites. We have about 39. Let's go around that up to 40. So it's the video talking about whole numbers. So total we'll have about 60 rain gauges spread out throughout the city. Some of them actually will be located outside the city limits. We are collaborating with neighboring cities to for them to host some of these rain gauge sites. So we have a good distribution of rain gauges. But that by itself is not going to provide a lot of information citywide. The city of is about three. The city of Fort Worth is 350 square miles. And obviously that's a large area. So the current density is about one gauge to about 10 square miles, which is not too bad really. But when you're dealing with real time, you do want to try to capture as much of that spatial variability as possible. So we are planning on tying in as it's right now. So this is not nothing new as it's right now. We're planning on using a hybrid approach by tying into the next rad radar measurements that are made by the National Weather Service. So the Weather Service does do this already. It's just that we'll have more rain gauges on the ground to help enhance that process. And try to minimize the problems associated with predicting rainfall from the next rad radar system. So the current next rad radar system has been updated to transmit in what's called dual polarization. So I'm highlighting a little antenna in the lower right corner here to show you the transmission, the cartoon transmission of a radar wave in the expand. And the National Weather Service has enhanced those radars to transmit in two different polarization states or different directions. One in the horizontal direction and then another wave in the vertical direction. So these two different types of polarization let you better characterize the type of rainfall or the types of cloud characteristics. The cloud as you can imagine consists of all three different phases of water. It's in liquid form, it's in solid form in crystals, ice crystals, as well as it's in the vapor form mainly below the clouds. And so we get to experience the liquid form as it falls down as it precipitates out of these clouds. And so these radar systems have to be sophisticated not to go too high. So you don't hit those crystal layers as well as not go too low. So that's where the tricky part is. Anyway, over the years the National Weather Service has gotten good about characterizing the rainfall using the radar system and the more recent radar systems since 2013-2014 timeframe have these dual polarization capabilities, which has provided enhancement in terms of characterizing the rainfall and other severe events. So the main point I want to make here is that while we will enhance the network of weather stations and rain gauging in Fort Worth, we will tie in to the radar system to provide a more comprehensive view citywide. Now that doesn't mean that we won't be using the radar only system as and when needed. So here's that next rat system I was talking to you about. This is one of the systems you see on TV weather stations. The picture on the upper right corner shows the radar station at the Sphinx airport. And on the bottom I've shown you the signatures that were being picked up during Hurricane Harvey. So it's actively used not only by the weather station but by a variety of other folk that provide the weather service information. Another system that is located in the Dallas-Fort Worth area is this Casa radar system. And whereas the next rat national weather service radar system sweeps across a much larger swath of the sky, the Casa radar system focuses on the lower elevations. So it doesn't have to scan as much and the return period on these Casa radar systems a lot faster in the minute range whereas the next rat system takes about five minutes, could take about five minutes. I have shown you the circles that are these different radars that are located in the Casa radar. One of these circles is a transmission radius from one of these radar sites. And there are eight of these radar systems and the more the overlap. So areas where you see a lot of overlap you're going to have a lot more confidence in the measurements than areas that have no overlap. As you can see out in the south as well as the southwest as well as in the northerly direction. And on the right side I have showed you an event from January which had severe tarnatic events and you can see all the red that's the high intensity rainfall events. Actually the white spots that you see there are areas where the tornado that had wrapped around it a lot of rainfall touch ground. So this radar system provides quite a bit of not only rainfall information but also wind information that enhances the forecast capabilities that can be used to warn people about extreme events. So we are fortunate that we live in an area that's covered by these two different radar systems. We'll work with the National Weather Service on the next rat and then we'll work with the Casa team. And I'd like to acknowledge at this point I forgot to acknowledge the Casa team when I gave you my thank yous but the Casa team which is based out of research teams at the University of Massachusetts, University of Colorado and UT Arlington. So for our part we are looking at trying to generate thresholds that could be used to program the radar systems to provide warning. And one way we are doing that is to look at the high water warning sites these 52 high water warning sites which have been engaged for water levels which have been engaged for rainfall and look at trends in the water levels and look at trends in the rainfall to see whether there are patterns that we can pick out that could be programmed into the radar measurements that are being monitored in real time. So what I've shown here is a graph of that and let me spend just a little bit of time going through this. So the dotted lines in blue or the dotted icons in blue is the water level measured at a low water crossing site. In this case it happens to be at the 28th Street and Labo Creek which is a flashy creek in the city. And this was an event from late November in 2015 and you can see there were two overtopping events. Anything over zero means it overtopped and on the time frame between 26th and 27th there was an overtopping and then immediately after the 27th midnight there was another overtopping. And that tends to be a lot more dangerous because it's in the dark and people can't see. So there were two of these events and then the red dots show the accumulated rainfall. So what we mean by accumulated means that this is a running tab. It's a total sum of the rainfall as it's being measured. It's not the individual measurements with time but the individual measurements that are summed up over time and that's why you see an increase of the rainfall. And what you want to notice is that the steepness of that cumulative rainfall tends to steepen up as we experience these flood events on the ground. So that's one way that we are using these measurements to inform the radar system. And currently we are working with the CASA team to look at 15 minute increments of rainfall and as the intensity within those 15 minute increments start peaking up we've identified to watersheds below those CASA radar footprints to issue alarms. And that's still in development but as we learn more and test it out we'll be in a state to make that more publicly available. I just wanted to give you an example of the way we are using the ground measurements to help inform the forecast. So this question came up at the first public meeting and that is that we are going to be using the rainfall measurements from both the ground measurements as well as from radar in either from the radar form or in a hybrid form to make the lead flood warning. We are not at this stage going to take that rainfall ingested into complex numerical hydrologic models and run those hydrologic models to make forecast. We're going to rely on making those warnings off of the rainfall at this time. Okay so I hope you have a good understanding of what we are trying to do and from here on out I'm going to be talking about what we have done to date on this project. So we've created a website for you all to access and the website is www.fortworthtexas.gov forward slash flood warning. We'll be placing updates this public meeting as well as the previous public meeting is recorded and posted on there. We have a executed contract with a consultant firm called DDI to help us with our project. We have resolved some of the data conflict problems that we were experiencing with our current high water warning system at the received site by squelching the noise at the transceiver site and then we have done some preliminary engineering structural engineering analysis of the second received site at the bridge street tower. So the second received site is going to be a failover system in case the primary received site at Burnett Plaza fails. And we've identified issues that need to be resolved to make the high water warning system a little bit more reliable in terms of the water level measurements as well as the weather gauging. And we have developed a strategy to locate the weather stations in and around Fort Worth. We have selected a software and we have a draft of the flood response plan in place that's being refined. So here's a picture of that bridge street tower. This is the second received site. It's about 250 feet tall and receive antenna will be located at the top and a cable coax cable will run from that bridge street tower to a building close by that will have the transceiver and the Digiport boxes that will take the data and transmit it to the server. It's pretty much like I showed you earlier for Burnett Plaza. So our strategy for locating the weather stations is to fill in the regional gaps. If you look at the region and I think the next map shows that region. So let me bring that up. No, it's not. So it's further down on the slide deck and you'll see what I mean by this. But the region in the south, southwest and the westerly regions have missing gaps in them. And those gaps will fill. So we have more weather data farther out and lots of the frontal systems come that way. So it's totally justified to locate weather stations out that way, that side. The telemetry itself, we can reach out to 30 miles. And then within flood prone watersheds, we'll locate the gauges in the upper one third of the watershed. The site selection themselves have to go through a vetting process. We need permissions from the landowner. The site has to be secure. There needs to be some fencing around, not necessarily around the weather station itself, but close by. So it serves as a deterrence. And the site needs good access so we can go and regularly maintain it. There needs to be a clearance, a 45 degree clearance above the weather station. So there's no obstruction that will prevent the rainfall measurements and other weather parametric measurements. And we plan on locating the rain gauge at all about 10 feet, not more than that. Here's the radiopath analysis that told us how far out we can go. So anything that's colored in blue all the way to red. So red means great reception. Blue is lower reception potential, but we can still receive it, receive the data. And we can go out actually all the way to Grandbury if needed. The actual expansion plan is going to go out through to about Creson, Godly, God and Joshua. So these are the cities we're talking to right now, Joshua, Godly, Creson and Wetherford, and then also Mansfield out here to locate the gauges out in this direction. So this is the Bernard Plaza strength of reception. And here's the strength of reception from Bridge Street, not as strong, but that's not a big concern because we don't expect this Bridge Street to be down or be actively used for extended period of time. It's just serving as a backup just in case the transmission to Bernard Plaza fails. So we feel comfortable with the Bridge Street tower reception. And let me add that in this picture what you see as those inverted triangles are the existing rain gauge and weather station sites. So we're going to significantly expand the footprint out west, southwest from where we are right now. Here's what the proposed weather station is going to look like. The components will be a multi-sensor that measures all these different types of parameters including rainfall. We'll have a supplementary tipping bucket rain gauge at some of these sites to validate the distrometer that's located in the multi-sensor unit. The transmission box will consist of the alert to controller units. And the concrete pad and pole is not going to exceed more than 10 feet. Here's the distribution of rain gauges and weather stations in the Metroplex as they relate to where we are. In the green lines are the major watersheds that drain the city of Fort Worth. And as you can see areas in the south-southwest there isn't a lot of areas that are gauged. And so that needs to be filled in so we can capture the rainfall patterns that are coming out from that direction. We have access to nearly all the other weather stations that are shown on there from our partners out east and from other directions. I wanted to go through, let me see if I can get that picture down so you can see it. I want to go through the strategy for locating gauges in watersheds. We are not going to have a lot of lead time because the floods when they hit a watershed can impact the outlet of the watershed within about 20 minutes. We don't have a lot of time. And locating the rain gauge on the low end of the watershed as it is right now with the high water warning system provides very limited lead time. So we want to try to go out to the edges of the watershed as much as possible. And that's what we plan on doing. So the plan is to locate these weather stations close to the edges of the watershed divides so that if and when these rain gauges by themselves get used to provide that lead forecast to some of these more flood prone watersheds, that will be on average about a 20 minute lead time. I do need to mention that the National Weather Service, the next rat based predictions can go out to about an hour. The numerical models that they use and provide the quantitative what's called the QPEs can go out to like 18 hours. But that's using numerical models and those radar signatures can get used in more sophisticated models to provide of course less lead time. The CASA radar also runs atmospheric models based off of the radar footprints and those can go out to about 15 minutes. The CASA radar footprints like 100 meters. So it's very much more precise than the next rat. Next rat footprints about a one mile by one mile area. So the idea here with this, with locating these gauges as well as with the radar system is try to provide as much lead time as possible. And the more we can ground correct those radar signatures and more we can locate these gauges at strategically located positions the more lead time we'd have. So the timing is everything in these flashy flood environments. So the remaining tasks on the gauging that will get us through this contract period is to finish installation of the receive equipment at the bridge street. We have done the structural analysis to locate the equipment on a tower like that. You've got to go through a structural analysis. Others they won't let you put anything on that. So that's been complete. And now we are in the process of procuring the equipment through bids to locate the receive equipment. We are working with neighboring cities to develop interlocal agreements. And I just received one today from Joshua. So thanks to the city of Joshua for working with us on locating a gauge on in your city. As well as we are working with the other neighboring cities I mentioned earlier. So we expect all of that the placement of the receive equipment interlocals and the bids to be done by end of this year. And then early part of next year we'll go through the bids select the contractors and then we'll be able to start installing soon after sometime in the January February timeframe. And then there was installations will take us through about June timeframe. So by the end of June we hope to have all the gauging equipment in place. And those will all be on alert too. I want to move on to the flood warning software. So we made significant progress on the software since our last public meeting. We had issued bids. We reviewed the proposals. The vendors provided demonstrations. We selected a software system. We began contract negotiations with the software vendor and we are in the process of approving the contract through mayor and council approval process. So we've gone through the selection and recommendation stages and we've selected and we recommend the contrails software from one rain incorporated. I want to just talk a little bit about the software system itself. The software is flexible enough to be hosted on a desktop environment as well as mobile units that you can carry on your cell phones. It has data collection capabilities across a variety of meteorological variables. It can ingest both the alert and alert to protocol. So we'll be able to keep up with what's going on in the high water warning system as well as the new enhanced system consisting of the dedicated weather stations. It processes the raw data that's collected by the transceiver unit and then it does a lot of QAQC checking so that you don't provide corrupted data to the emergency responders or the public. There's a lot of good visualization capabilities. It's got an alarm manager to send out those texts and real-time alarms to the emergency responders. And it can also be used to activate those flasher units. Now I do need to mention that those flasher units that you see out on those 52 low water crossing sites, they get triggered automatically. So it doesn't wait for the software at the central receive station on Bernard Plaza to tell it what to do. Whenever the high water warning is triggered, it responds immediately to that trigger event locally. That's the way it's currently right now and we don't plan on changing that. And the control software also has good reporting capabilities. There's a couple of screenshots from the Hurricane Harvey experience. So this is what some of the folk that were monitoring Hurricane Harvey at Harris County were seeing on their system. And we can highlight a table format and show you where some of the intense events are taking place. In this case, those reds are very high events that have exceeded historical standards. And in this case, it's actually exceeded the 500 year events. You can also depict points on a map and show the numerical value associated with those points. You can have a dashboard environment to check multiple variables. It's kind of like what you would see in your car as you're driving. It shows all those indicators in a dashboard fashion so you can quickly diagnose and identify problems. Here's an example of a screenshot from the alarm system. You can drop in a lot of equations to control those alarms in this software. And then ultimately, we'll make the data that's processed by the contrail software available to the public in a form similar to what you're seeing over here. This is an example from Harris Flood Control District that shows what it looked like during Hurricane Harvey. And you can see the tremendous amount of high water events that were recorded during Hurricane Harvey. So what are the remaining tasks for the software installation and deployment? So you can see it on your end. So as I mentioned, it'll go to council date November 14th. And then once the council approves it, we'll execute the contract and then the installation can begin. They'll migrate the data that's currently hosted in the current system into the contrail software. They'll integrate their components along with our components through an integration process. And that's a significant amount of effort, the integration.  And then staff will be trained on the use of software once lots of the issues have been ironed out. And then the data will get deployed for us to test out and then eventually made public sometime around a June timeframe. So that's the developments on the software. I'd like to move on to the flood response plan. So the flood response plan is a planning level document that will be undertaken as part of this project. That'll describe the city's flood responses depending on different types of threats, flood threats encountered, likely to be encountered by the city. And these flood threats range from flash flooding through to potential dam breaches to regional level flooding due to levee system issues and riverine flooding. So since we met in April, we've had a stakeholder meeting within the city to identify what that planning level document was going to look like. And based off of the meeting as well as gathering up a lot of the background material and let me just describe what that background material is. So this flood response plan is not going to create anything new in the sense that it's going to integrate and bring in together in one document all the different types of emergency action plans, the emergency management plans that are used in the city by external agencies such as the Corps of Engineers of Water District. We are not going to actually copy into this document all those document we'll just refer to those documents but it's going to integrate in one place the different types of flood responses associated with different threats in one place. So that's what was part of this background research was to gather lots of that material so that we could understand what the different types of emergency actions were. Obviously, when you respond to a dam breach, you're not going to respond the same way as you would do a flash flood and so on. So the effort led to creation of a conceptual framework, how to format that document. And the conceptual framework is using what's called the TDEM-10. This is an emergency planning frame format that the Texas Division of Emergency Management uses. So we will use that framework as much as relevant to host this flood response plan. And we have developed a early draft of that. We are in the process of finalizing the draft and I'm working with the consultants and the emergency management folk to finalize that draft. And then once that draft is complete, we will want to take a tabletop exercise. So this outlines what I just discussed. I did not talk about the preparedness and recovery but this flood response plan will also have mention of preparedness and recovery but the main focus is on response. So here's the TDEM format that will be used to write out this flood response plan. What I'd like to mainly highlight here are Section 4 called Situation and Assumption, which deal with stating the facts on the ground. And then concept of operations deals with the different efforts that are undertaken by the different types of threats. And so that will describe the resources available as well as the application of those resources. And then direction and control deals with how the level of flood threat gets escalated as the threat level gets worse and worse. The preparedness level part of the document will consist of these components that I've listed out here, primarily dealing with educational efforts to keep the public informed prior to severe events. There's a significant amount of inspections and monitoring, particularly with the regional dams. And then mention will be made of the high water warning system that's used to warn the drivers of flood that the hazardous crossings. So let me step through some of what I talked about in a little bit more detail. So the response itself is going to focus on the hazards caused by potential dam breaches of city dams and the regional dams. So there have been over the years emergency management plans already developed for these. So there's going to be, as I mentioned, nothing new in this document. It just integrates the existing emergency management plans that are already out there. The second type of flood hazard that will be discussed will be the flash flooding due to overflowing creeks as well as undersized storm drains. And the third type of flood threat that this document will deal with is the riverine flooding associated with the Trinity River. Here's a map showing you these dams. There are eight city-owned dams in the city as well as the regional dams, which are Eagle Mountain, Lake Worth, and then Lake Benbrook. The Eagle Mountain is managed and operated by the Terrain Regional Water District, Lake Benbrook, the Corps of Engineers, and the city of Fort Worth is responsible for Lake Worth. Here's the different types of flood hazards that have been identified. And the map on the left side shows you the mapping of the flood plains as well as the repetitive loss and flooding from areas that experience flooding due to undersized storm drains. And on the right side, I've showed you a typical type of map that's generated during a flood event showing you areas that experience overtopping as well as incidences associated with those flood events during a flash flood event. So the flood hazard that will be discussed will be the flood hazards due to the Trinity levees, and this map shows you the areas that are protected by the levees. So the first important component will be identification of the hazards. The second important component of this plan is identifying resources available to address each one of those threats, and that's what you see over here, the different types of resources that are available to identify, to work and address these types of threats for the flooding. And the early ones that dealt with the flash floods, in this case, these are the types of resources available for issues associated with the potential breach of the city dams. So the parks and storm water have different dams that they're responsible for monitoring and inspecting, and if there are issues associated with those, those will be immediately forwarded to the Office of Emergency Management and the Emergency Management Coordinator on duty at that time. And then the Emergency Management Coordinator will bring in the police and fire to provide notification to the homes and prepare and execute evacuation plans. There will be coordination with other agencies such as the Texas Department of Public Safety as part of this resource notification. So in terms of flash flood, the third important component is the application of resources to address different types of threats. In this case, I have laid out the main points of how the city applies the resources to deal with flash floods. So the flash floods themselves can range depending on level of severity from level four, which is the least severe to level one, which is the most severe. And the level of activity of the field personnel dictates a lot of the escalation. Not only that, but also the amount of rescues, the 911 calls and all of that is coordinated and assessed at the Office of Emergency Management. And so there's a lot of local level activities that get coordinated at a higher level by the Office of Emergency Management. In terms of monitor application of resources for city dams, as I mentioned earlier, there's monitoring that initiates the distress call to other levels within the city office. Levels of emergency management. Here's what it might look like for the regional dams. Again, the monitoring and observation is the point at which the notification and the escalations begin. And then the Corps of Engineers alerts relevant folk at the various levels of government ranging from state to federal levels and brings in the appropriate resources to address different levels of severity of the dam breach. So once there is a severe event, you also have to recover. And I have shown some of the main points of recovery. The debris is a significant part of recovery. So there are debris removal processes in place. The stormwater management division does flood forensics to understand what happened and characterizes the storm and the flooding extent. And then city forces get engaged to repair significant damage to infrastructure. And then if a presidential declaration is made, you also have to go through a cost recovery to recover the costs. So here are the remaining tasks. So we'll anticipate finishing the draft of the flood response plan by end of this year. It'll be put out for public comment. And then the plan will go through a tabletop exercise. It'll be updated based on the lessons learned from the tabletop exercise. And then that document will be submitted to the Water Development Board and Texas Division of Emergency Management. And then following their comments, the flood response plan will get finalized and go through an approval process with the Texas Division and the Texas Water Development Board. We anticipate completing all of this by June of next year. So I have reached the end of my presentation. And I wanted to summarize where we are right now. We have a good understanding of the current high water warning system, the issues associated with that high water warning system. We've resolved some of the communication problems by resolving the squelch noise issue at the transceiver, which has helped with the data collision problem. Of course, the data collision problem doesn't go away when you're using the alert, but we try to minimize that as much as possible with our current system. And then we have laid out good plans to expand our network and move on to the alert-to-based network. So we'll be working with a hybrid alert-to-alert-to network for a while and then eventually move on to a purely alert-to-based network. As soon as our bids for the equipment and installation are complete, we'll begin installing the dedicated weather station starting in January. The software installation should begin soon in November, and then it should lead all the way to a public website sometime in the June-July timeframe next year. We'll have a completed draft flood response plan by end of this year, which will go through those phases that I showed you just a little while ago, and it'll get sent to the appropriate state agencies for the approval. And then I plan on hosting a third public meeting in June-July timeframe in 2018, and we will have all the components as part of this Water Development Board grant by the extension period in September 2018. Thank you very much. And if you have any questions, I'd encourage you to send me email and please visit the website for updates and keep up with the CD calendar for the third and final public meeting. Thank you.


Hi everybody, it's Kevin Sheedy here, obviously we're the Estonian and the country game coming up, a powerful country festival and part of that is going around this reviewing lots of things that happen around our Victorian country and of course being up here at North Garfield and having with some of the burnt out land that you people have done a magnificent job are saving homes after well nearly two weeks of fires and they're still putting out fires.  After turning up a packet and I couldn't believe how tall all your career firefighters were, I should have done a lot of recruiting there for the mighty bombers but look to the many many career firefighters that assist the volunteers as well, sensational effort, very dangerous jobs, getting to sort of get to know your landscape and every fire is totally different and you never know when a lightning strike is going to start a fight. It's the harshness of living in Australia, like we could have that here in Victoria with bushfires and up in Queensland with floods. It's quite incredible where everybody does contribute but the more I've actually looked into our country, looked into the people that work in the CFA and around the CFA and the volunteers that support them, you know to be out here in the dangerous bushfires that have happened not only this year, also around you know over 10 years ago and Black Saturday and you know to me it's just incredible what you're doing. Well you know we've got an invitation opportunity there to have a lot of the volunteers come and march on the MCG, we're trying to get that sorted out. Great effort and great effort down there, everybody at Narno Guru, supporting, helping, cooking, feeding well over a thousand firefighters and volunteers, tremendous effort and congratulations to all of you.


Hello everybody, thank you for joining me today at this very dire time of the afternoon and on a Thursday, but let's get started. So the year is 2012. What were you doing back then? Perhaps you were studying something, perhaps you had a different job, maybe you switched career over the past 12 years, many things have probably changed. At least for me, I would have never expected that I would be in this stage sharing some thoughts with you. 12 years ago I was in Guatemala studying and I'm very sure everybody had very different stories going on back then. But one thing that united us all across different countries and cultures and different stuff was something definitive. The Mayan apocalypse is about to happen, right? This was everywhere all over the news and some people thought it was serious and there were some kind of weird things happening, but at the end we are still here so I guess it didn't happen. But the other thing that was more defining of our modern world is that memes hit mainstream and that really changed how we live today and we still have it. Maybe the apocalypse is over, but the memes are still here, they have evolved so many times and I was a student in computer science so one of the things that I saw back in that era all the time was this one, the classic, read the funny manual. I was studying computer science but every time I had a question people would be like sending me variations of these all the time and I think they would be canceled today, but yes this happened to me, it was my daily bread when I had questions I was trying to learn, but back then we had manuals of 50 pages so we could watch TV and we were supposed to read the entire manual so we could use the remote control, but what if I had to learn something really special or difficult like my sequel? Well there's a manual for that, it's just that it's 5000 pages plus and I'm supposed to read it all I know it all right, otherwise I'm going to get sent a meme. Twelve years from now things have changed quite a lot, right? Now this is not how we approach learning, learning in 2024 is different and how does it look like, how do we learn something new and new technology and new project and a new library and that's what we have documentation for, we have changed the word manual for something more comprehensive and that's what this talk is about, towards great documentation. What does great documentation even mean? That's something that we'll discover throughout this talk, but first let's talk about documentation in general, like what is documentation even in the first place, the dogs right, dogs are documentation and that's pretty clear, but there's more to it, the project's website is also, oh no, I changed my slide by mistake. Let me introduce myself first, that's why I was just so excited about the topic that I even forgot who I am, but I am Jorge La Fiesta, I am the author of the Linux Foundation introduction to backstage course and now I'm not working much with backstage, but I'm instead looking in a cooler place called Rutley, we do incident management and yes, now I have to look at the screen. I also studied digital communication at UCLA and Alborg University in Copenhagen and most importantly, I am a certified sommelier, which means that I drink wine and I know how to do it, which is what matters, in my opinion. Great, so now let's get back to the topic for real about what is great documentation and let's get to see what documentation is and this is dogs, right, dogs are fine, but then there's also the component of the website, which is a very defining aspect of documentation that we don't often consider, because when you hear about a new project on a podcast or somebody mentioned it to you on QCon, you probably heard dozens of things that you didn't know existed over the conversation you have with friends or people that you know here and you Google and then you find the website, how many times have you Google a new project, a new presser thing and then you're like, ooh, I have no idea what this does, so why is it useful at all to me? That's because the website is also a part of the documentation, it's very an entry point on even is it worth my time to keep digging into actually even reaching the dog section, so that's why the website is an important piece of this puzzle of how we even learn about new things. Next, we have the Rhythmie, because for open source projects it's not only about the website, you can also discover a new project through GitHub, you probably seen trending repositories and stuff like that and that's also why it's an entry point to get here. We also have the contributing file which is a form of documentation because if a person's project doesn't get contributions, it's even open source or it's just like a sponsored company thing that is just open, kind of. So that's an essential part and we need to be enabling contributors. Another thing that is part of it is the issues on GitHub, they are also a way of documenting what's going on and we also have meta documentation about how we even orchestrating this whole thing, because you've seen yourself the projects evolve fast, they really go really fast, especially when they become popular, so unless you have a way of curating how this is going to evolve, it's going to go crazy and go wild. However, it seems to me that there is some incoming communication. Let's see, I think it's coming from outer space or some kind of AI-generated text. Oh, it's not playing. But this hall talk is inspired by a tech audit that happened, it was sponsored by the CNCF on the backstage documentation. Backstage is a very complex project, it has hundreds of pages on documentation and they took the work of going through all of the docs and figuring out what works and what doesn't work, what is confusing, which is a very commendable task. I have never done it myself but I just used their analysis. So in this talk, the methodology is basically going through the findings that they have and trying to get patterns that you could apply into your projects or the projects that contribute to, and that's the idea. If you're interested in the output of this analysis, it took them months to get it done, it's in this one meta issue in which they collected all the different recommendations for oh, you need to restructure this whole page or you need to add this guide or you need to change this part in the sidebar, it's very practical information and it could be interesting to see how a transformation of a big project documentation can look like. So let's look into the backstage of the backstage tech audits. We have seen that they analyze documentation in three components. First is the project documentation, which is the docs part, then they also analyze the contributors documentation on the website. So let's look at first the project documentation. What does it take to make good project documentation? First you need to understand who needs this documentation because there's different people who want to use your project, your library, and you need to be able to cater for them. And one of the clear ones is new users, right? This is the whole purpose of having a project, somebody else is using your project. So you need to make sure you have documentation that's ready and available and optimized for someone who doesn't have a lot of context and is interested in your project and that is a specific nature on the docs that you have to write. Another set of group is experienced users. You cannot give experienced users this intro guide. They have different use cases. They need to find specific information. Therefore your documentation has to be structured also to take into account this user persona. And depending on the nature of the project, you also have user roles, which is essential. It can make things very easy to read or very hard if you don't recognize the right user roles. I'll give you a very practical example. In the backstage documentation right now, I'm very familiar with it. So for me, it's just that I always mean I never understood it completely, but I knew how to move around it. And I didn't know how to make it easy to read. And the reason why it's complicated and the reason why it's hard to follow or understand even what's going on is because different user roles are convoluted into the same pages. So that makes it very hard because the audit even identified four concrete personas in the case of backstage. Because backstage, I don't know, is anyone familiar with backstage? Can you raise your hand? Okay. So for context, backstage is a very complex framework. So it can be usually installed by someone in an organization. So developers can use it. So those are the end users. However, the end users need documentation because backstage has a lot of features. So the person who just wants to check out the catalog, which is one of the features, doesn't need to know how to install backstage. They just need to know how to navigate the catalog.  They require a lot more documentation. But it's specific to their needs. And backstage is optimized for inner sourcing, which means that it can be extended by other teams in the organization. So that's why there's this other persona that requires a specific documentation for developing tooling on top of their instance. That's not going to be useful for anyone else except for this group. And then finally, there's documentation for people who want to contribute to the framework, which is also very common when people open source logins or features, because it's not that easy. It's not like it's a special way of developing backstage when you do this. So it's just about identified what are the different personas and then you can organize the docs. So we'll see an example of somebody who does this really well and it's open telemetry. I don't know how familiar you are with this, but it's very different to use open telemetry as a dev because you need to put the tooling in it or as an operator because you need to use it in a different way. And they provide this way of straight up just, are you a dev or are you doing the upside? This is how you're going to get started. This is super useful because then people can get started rapidly without having to weave through the things that are not relevant to them and then they can find value fast, which is what we all have to do now that if we don't have a lot of time to read things that are not relevant to us. That's one way of like dividing user roles. Then there's also the example of Hermitius. They have like a really nice documentation and you can see that they have this part for new user content. It's a specific type of documentation that's going to be useful. If you're new to Hermitius or you just heard about it, you want to know, for example, how does it compare with other options in the market and how like the fundamentals and like introduction to the introduction kind of topics. So you know what it is about because it's not an easy thing to understand. And then there's also another part for new users, which is about practical stuff. How do you get value as a new user? Because that's what we need to optimize for new users. We don't need to tell them a story of how they found there or we funded these three years ago because they don't care. They want to get to see if this is going to be useful for them and how much effort it requires. So you need to get them started and make them be able to prove value of your tool as soon as possible. So you give them like this minimal viral path that they can follow with practical stuff and some conceptual content and then they should be ready to go. So that's for different personas on the documentation. But then there's also different types of... I just don't trust this pointer. Okay. Then there's also project documentation types because not all documentation is the same. There's conceptual documentation. There's step-by-step documentation there's like business value documentation on how to showcase like this works. So there's feature documentations. So at the end, the whole purpose of documentation is to enable someone to do something useful with our project. So that's what we need to ask ourselves. What are we enabling people for? As I was saying, one of the first things that we need to optimize for is that we can have people prove value because nowadays your project is probably not the only that exists. There's alternatives. So you want to be able to explain to people why they should choose yours. There's also documentation that's useful for explaining the foundation parts because that's going to be very interesting so people can do more and learn how to make it more intuitive for themselves how to build on top of your project. There's also like the showcase in the features which is the midi part because at the end nobody is using the project for fun. They want to solve the real things. They want to achieve goals. So this is also very interesting to showcase like in a very straightforward manner. So they don't have to weed through things. Then there's hands-on development which is tutorials, guides, and step-by-step kind of stuff, maybe even little laboratories or workshops that you may have set up. That's kind of another type of condition that is required at the end. Let's look at more examples from ethios documentation. So you can see that they have this clear path where they have conceptual content which is literally called concepts which is just very clear and easy way of communicating that this is where you'll find this kind of content. But they also have key features just on the same level of hierarchy. The sidebar is very important in documentation because that's the first thing that you can see. You cannot expect users to like go through all your nav unopening all the things until they find the right path. So you can it's useful to have like this is what you can use. This is how you can use Prometheus for alerting. This is how you can use it for this, for that, for that. And that just simplifies everybody's life. And then there's also step-by-step content which is going to be drilling into the specifics of this is how you set it up for X or for Y. And it provides this like, you know, tutorial style kind of content which is always appreciated by people getting started on as a reference as you implement. Then they also have a little bit of a mixback in best practices, which is perfectly fine. And that's also what we have here as well, just some best practices for documentation in general. We have, for example, the concept this is something that the CNCF Tech Talks audit also recommended, having very short pages, make them very concise. We often have the temptation of saying, oh, well, I can put these docs in this page because it kind of talks about the same thing. But then you're going to make it very hard for people to find this information and very hard for you to keep it updated because then maybe a part of the documentation changes, but the rest doesn't. So it becomes very messy when you have versioning. It's not very clear what changed. So make the pages in solar. It's better to have 10 different small pages than to have one super long page for many recent events, for SEO, for discoverability of the content. So that's something that it's often the temptation to be like, just drop it in that page, but it's better to make it separate. Another thing is include an API reference, which I guess is very common, but just in case, mentioning that if you have an API specification, just drop it in the documentation. Make it searchable. That's going to save so many lives because we don't have time it's very easy to miss things in the nav bar or just very specific terms may get lost. So just make it searchable is invaluable for users. And this is also important. Make plans early for versioning because your project will definitely evolve. The API that you have today will not be the APIs that we'll have in a year from now or two years from now. You're eventually going to rewrite the entire thing over the course of years. So you need to be able to have versioning early. You may not need to do it like right the first year, but you need to be able to plan at least how you're going to support this. And that may include choosing the right documentation framework or knowing what you can expect in that regard. And then similarly to that is plan for localization because when your project because very successful, which you will because you're following the best documentation practices, you're going to have people that want documentation in other languages. And this is also a very nice way of getting contributions. It's quite common that people in localized communities want to contribute content in their own language, which is very nice. It's a nice experience and it's good to have it enabled earlier. So we have covered some some tips on project documentation. Let's briefly review some stuff for contributors in the commutation, which include things like the rhythm includes the contributing file and issues. So one thing to have into account is to have all channels of communication clearly marked because sometimes you know you operate on this court, but then do you know it? Is it clear to everybody? Is it really marked on the repo on the website? Because otherwise it's unclear where do we communicate or do we communicate some through some other Slack channel or it's better to just be very explicit about where you expect the communications and which what purpose. Are you going to say that you're going to have this court for support? And I don't know, like GitHub issues for all that kind of stuff or the GitHub forum. There are so many ways of engaging nowadays that it's best to make very explicitly available to the users how to communicate with you about the project and how to communicate that they want to contribute. How do you support them? That should all be documented somehow. It's also very important to have a scheduled meetings because the project is it's okay if you want to do everything I think that's maybe the case for a lot of projects, but eventually the project will grow so complex that you will need to sync up with your organization sponsoring the project or with contributors or with adopters to figure out how are they using it and get feedback from the community. It's often unavoidable to have regular meetings and I think it's very healthy because then the people can hang out and you can see a face if you have cameras and understand how people are using your project which is ultimately what's going to inform how the project will evolve. So that kind of meetings is best to have them scheduled on a predictable pace and that space has to be also very feasible and explicit to people so they can know when to join and how to join and which are the channels. So all these communication channels are just integrated and easy to follow. Then we have a guide for new contributors which is also going to be unavoidable there's always going to be that's what we want right well just as we want new users we want new contributors and that's that documentation can be the people that are going to be contributing they are like more more savvy let's say or more invested in the project so we do not need to make them as tidy as the new user documentation but still it's useful to give them like which environments you need to set up and all of these nice things so they can contribute smoothly and then another thing that is interesting for the contribution is the pod projects governance because if you are going to commit time to contribute something to this project you want to know what to expect who's going to own it how is support for your efforts going to be received or are you going to create this PR and it's going to be abandoned completely who do you reach out out if you have problems that's or who's even going to maintain this after this are you expected to maintain this feature forever like what's the commitment that's something that has to be communicated explicitly also for the well-being of the maintainers because otherwise the assumption is oh I'm going to contribute this and the maintainers are going to have to take care of it forever which is happening in many projects and it's very burdensome for for maintainers it's better to set very clear expectations now for the website some tips and ideas this is something I could talk about for I don't know hours because it's my job to the websites I I work in marketing but on the good marketing people so one recommendation specifically for open source project is to keep the website on a single source which is often the case that you have you you're building the docs in a repo then you have like the landing pages in some other place and it becomes very difficult to maintain so one recommendation that a CNCF does is try as much as possible to have a single source where you can compile it could be as its own special repo for the website where you can compile the the docs reference when you can compile the the API and the marketing landing pages because that's going to make it easy for you to maintain and it's going to make it possible for people to contribute which a lot of the times you want people to contribute to your landing pages and your docs and if you have one single place where they do it it's easy to tell them hey you just go there and change it if there's an error or if there's something that they want to a page or other tutorial something it's going to be easier if they have one single way of doing it another thing is usability make sure even though like a minority of people we use it on a mobile device it's still some people who might use it and generally it's going to make it easy for you to so the documentation is available for different kind of screen sizes thankfully we have already this day and age a lot of libraries for documentation that already do this work for us but just not everybody has a lot of those just a check and there's something very critical that is often left behind or not even rely on an open source project is having some sort of social proof because just as you need to learn how to use it and show value you can develop trust if you can showcase hey all these companies are already using us maybe you should try it yeah like we are trustworthy of your time and this is something trivial relatively once you have a few adopters just like talk with them and say hey do you want to be showcased in this page and you can work on cases studies which is going to be super useful especially for champions that want to use your project in their organization they need some resources to to prove to their boss that this is not some crazy open source project that there is something solid that people are using it and then they can trust better that's going to be a worthy investment another thing to consider and it sounds way too marketing but it's very real you need to take into account the search engine optimization for your open source project website and that may mean using the right terms making sure the mark down in your pages is hierarchical and compliant because otherwise what's going to happen is that like the private source competitors are going to eat your pages and they're going to create a lot of pages so you everybody searching for your project will not even get to your website because they they know how to play it and even if you're the source of reference they know how to like dump you down the the list so it's better to be prepared just make a good work with your the way you use the language and your your html and that that can go a long way and and protect you from being forgotten even in your own search terms and also keeping track of analytics is also useful to see for example you can detect how documentation is performing a little bit and directly by saying if the drop rate in this tutorial is like five seconds maybe people are getting stuck maybe this like command is wrong and people are just leaving because the amount of people who will tell you that it's wrong it means like a hundred people tried it and they just abandoned it until somebody tells you hey this doesn't work so it's better to keep some eye a little bit to see what's performing what's performing where are people dropping out maybe this means that they don't understand what we're doing or maybe we have to rephrase how we talk about our project in the homepage it can be super useful and then last but definitely noticed is planning maintenance of the website and in general the documentation is good it's healthy to go through the website let's say once a year and say oh this message in this is not really what we do anymore we find out that people are using us in this way so let's change our hero image or or or or tagline yes now what is great documentation that's the question that we wanted to ask and just maybe short some short pointers project documentation a great project documentation achieve something and that is that it helps user according to their needs and it enables them to find what they need fast so that encapsulates pretty much the the way of segregating documentation by different roles making insular smaller pages make it searchable we all we do that so the documentation can be useful to people according to the need we reach whatever they need and they we have optimized the page for that and then the contributed documentation enables people to contribute in a predictable manner that means that if I put my time maybe on the weekend to create a PR I know what to expect I know that the maintainers may be going to take three weeks to review it but I I'm okay with that but they because they told me so I do it consciously and then I know what's going to happen who has to approve it like I it's predictable and I'm comfortable when I contribute when to this project and finally the website the website's at least the way I see the website is that it should prove that your time is worth it's worth it to give a shot to our project because it can solve this real problem for you and it's yeah we can show you you just give us like five or minutes go to the docs but just getting the confidence like getting people to trust you enough to give you like five minutes is very hard in today's internet so that's that's kind of the purpose of the website and it's also useful for champions and finally all the documentation the great documentation has everything connected which means that the docs tell the same story as the website at the contributing content at the auxiliary channels at the meetings there's this cohesiveness and people know where to go when they need something that's really what we want to achieve and finally the message as well is contribute to documentation you don't always have to contribute code code is great but a lot of time there's a deficit in documentation contribution like this was from yesterday's talk on the state of backstage for 2024 and they mentioned this issue that I showed in the beginning and it's up for grabs there's many tasks very very good tasks for beginners that can get you involved in a way of contributing to a very successful project the backstage was the project with the most commits contributed in last year so it showed you that it's an interesting project to start contributing if you want to and documentation is a great way to start and yeah that's that's all I have thank you for coming there's this qr for feedback which I would really appreciate so I can make a very talk and if there's anyone that has any question we have some time all right I'm Nate a technical writer with the cncf thank you so much for going through this process and doing this well first off thank you for working with us on this program this was a lot of fun working with you and I'm gonna hijack a little bit here if there's anybody who is a maintainer in the room and you would like to to go through this process with us you're welcome to open up a service desk ticket or reach out to me on slack mate w and the other thing I'd like to let folks know about is every I guess it's the last Wednesday of every month we have a a tech writers open office hours for anybody who's got any questions about technical documentations we bring tech writers in we have conversations we go through all the stuff that Jorge has been talking about and the way you can find that is in the cncf I'll make sure that we put up a piece of information with the zoom details and all that in the cncf tech docs channel in in slack so sorry for hijacking thank you so much Jorge this is absolutely thank you thank you so much for saying that I think everybody should know it yeah great yeah Nate is amazing to work with so if you have a cncf project you should definitely go for it or just a commentation as he said for the open office it's gonna be amazing I learned a lot right thank you have it uh after a minute


Dragon Ball Z, Budokai Tenkaichi 3. Maybe it's just me, you can let me know down below in the comments, but back in the day, this game was THE game. That's why it's such a shame that with all of the new Dragon Ball stuff we've gotten over the years, they've never made a Budokai Tenkaichi 4. Except they actually did. If by they, you mean a team of modders known as BT4. That's right, they've added all new stages, characters, transformations, and super moves. So of course, as soon as I found out this existed, I knew I had to play it on the channel, which is exactly what we are going to do right now. For the first video, you know we just gotta go around, look at what seems fun, starting with, of course, I've gotta check out the new characters. Wooo! Look at that already got it set up on the match I wanna see, Gojira? Let me go with Gojira vs Broly on the Glacier stage. Let me keep this as canon as possible. Although I don't know if the Glaciers look this good in the movie at this point, uh, of the film. Oh, minigames! Please, please! No! Ah, it wa- Yo, why'd it open up such a dramatic shot? It looked like Gojira was about to say there ain't enough room for two of us in these glaciers. Waaaaaah! Such a way with words. I'm ready to test out this new power of mine. That's what I'm saying, Gojira. Let's go- Hold on, you know what? Let's start it off with a move. Start us four! Yeah, I might have looked at the move list pretty good, I miss everything, nevermind Broly's built bad. Come here, Broly. He sa- He sa- Oh, look at the dodge! Now I'm attacking his flank. Uh, you know what? I'm gonna let him fall. Yeah, why not? Treat himself. Broly, I know you're not coming over here. Where did my- Did I really use my blue- How did I- Wildsense! Oh, that's how I did it. I used Wildsense.  No! Oh, he has Wildsense too! Alright. Block that, bitch! Oh- Bro, really, he said my people need me. Damn. Damn, Broly, please. I'm just trying to do my ultimate. Over here, Broly. Oh! Woo!  No, Broly, please. I'm sorry, I'm sorry, I'm sorry. Damn! Planet Crusher! Damn! Damn! Oh, come on. Yeah, it was a basic super-Kamehameha, but you know what? I'm proud of it.  He locked on. Hold on, you know what, Broly? If you're gonna do all that, let me show you the power of a- Oh, start us fall in my bed. Let me show you the power of a Super Saiyan. Oh, let's go. Look at that transformation. Now it's time, Broly. Now you really, you really should have thought about it. Yeah, yeah, you having second thoughts now, huh? Hold on, but I don't want to finish you in this form, so I'm just gonna let you do your thing. Go ahead, Broly, do what you gotta do. I'm not finishing you in this form, Bro. Easy, easy. Are you really throwing that at me? Ow, ow, ow, ow, ow, ow. Broly, how pathetic could you be, Bro?  Come here. Oh, and you made a big mistake getting this close to me. You made a big mistake. Oh! Oh no, please, mercy. Oh, damn, I gave him the five piece, though. Gigantic breath.  I hit him right in the sternum. Damn, this looks so good. I kinda broke my arms there on that animation, but that's fine. Oh my God, he's lucky I couldn't follow it up, but I do have the ultimate now. Broly, you better hope she lies in. Broly, Broly, where's she lie? Hey, you better call her. You better have her on your Faye Five, Broly. All right, we're being childish. We're being childish. We're being... One more time, Broly, one more time. I've had enough. He, like, got lost and locked on, like, five times. That man was fighting for his life. Hold on, Broly, let me show you how that match should have gone. Oh, minigames, I forgot. I have to risk my wrist health for this. Okay, nevermind. Okay, now that I'm in control of Broly, this is gonna be a different store. I even started Gojira in blue so he could have a chance. Gigantic charge, uh-oh. No, no, no, no, no, no, please, please. Oh, my win, come here. Yeah, yeah. Oh, my God, Broly is just hitting this man like a grown man. Where you going? Oh, my God. Six, almost 7,000 damage for that. I'll take that. Behind you. Oh, oh, slam him into the ground. Why don't I? I'm gonna do it again. Now, I wish I could tell the AI that this is what he did wrong because I'm not just gonna power up once, right? I'm not gonna power up only once. I'm going to become the full legend.  How do I wild sense? Wild sense! Gigantic charge! Oh, my God. Where is he? Oh, there he is. Oh, you're so lucky. I need two bars of key for this. All right, I got my two bars. I got my two bars. Damn, I got my two bars, bro. It's over. You broke my favorite armor. That was a present from my dad. It actually wasn't, but damn, why? Wait, I've kind of losing, too. Meteor shower. Soul Punisher. I didn't even know he had that move. Do I win? Oh, what is happening? I'm losing it, dude. Oh, my God. Oh, my God, I wasn't ready. I'm going to have to buy a new controller after playing this game. Every button on the controller is being assaulted. Look at the screen shake. Oh, no, he better not. We're going to have a Key Blast class that is going to rival that of the... No, no, no, no way he did this to me.  When I can't even fight, oh, I blocked it. Let's go. And I missed. You know what? I do want the Key Blast. I want us to clash. Wait, wait, don't do it yet. Wait, wait, don't do it yet. Wait, wait, I can't stress enough. Don't do it yet. OK, I got to dodge this. Soul Punisher dodge. Side step, side step. Easy side step. I spoke a little early. I spoke a little bit early. All right, do it. Do it. Do it, Gojira. Do it. No, no, you don't. No, you don't. You stay away from me. Oh, I can explain. Oh, he spared me. And he's killing me. Wait, Gojira, please. I like that. Gojira. Oh, Wild Sense. Why is Wild Sense so good? Where is he? Oh, Gojira. Oh, good fight. All right, well, after that humbling, I actually did want to do some more new Dragon Ball super content. So I'm going to the time next. I'm going all the way to challenges. And I'm going to take on Ultimate Battle Z, not just any ultimate battle, though. I want the whole Super Dragon Tower. Look at this lineup of characters I've got to go through. I don't think there's a single old character on this. If I make it even past Kaba, I will be impressed with myself. Of course, I will be going ahead and cheating just a little bit with my character choice. But I don't think anybody would mind. All right, so we're not fighting on the tournament of power stage. That is interesting. I thought for sure we would. I just thought for sure they would put us there. Who is up first again? It's Beerus, right? Beerus, help me test out this power. Yo, we got dialogue. I didn't intend to go easy on you this time. Bro, you don't have to go easy on me, Beerus. In fact, just try not to die, because I'm going to hit you with a godly display. I've had a serious lapse in my judgment. Why did I go past them? Oh, god, damn. Why is Beerus so good? All right, I'll be impressed if I make it past Beerus. This man has two health bars and is saucing me up right now. Damn, I'm getting sauced. I'm getting absolutes. Who would have known being terrible at this game would come back to haunt me all these years later? I'm getting sauced. I'm getting cucked. Godly display part two. No. Please. I'm getting cucked. Oh my god, this man has me on the grill. Oh, damn, damn, damn. There's no way he ducked at. There we go. Godly display. He can't dodge it now. No. You thought it was over. Oh, Beerus, you're still alive. There's no way you're alive. Don't, don't attack me, please. Oh, I just, came the old sock on bombers. Do I get health back? All right, I do. I do. Whoa, sweep the leg. How many times do I got to teach you this lesson, old man? You ain't Beerus. You ain't like that. You ain't Beerus. How many times? How many times, Frieza? You're not on my level. OK, you might be on my level is what you would have thought. Hey, Frieza, hold it. Whoa. Oh, Frieza, that is so embarrassing for you, bro. Where are you? There you are. There you are, Frieza. Come here. Give me my health back. The health that you took so unnecessarily. Kaba comes after Frieza. No way, Kaba, grab me. I'm sorry for sleeping on you. I'm sorry for sleeping on you. Yo, Kaba, where you at? He died. Damn, this guy got ultra-instinct as well. Yo, Kaba, fight back.  You can't, you can't hold me. Yo, Kaba can't guard me.  All right, I get it. I get it, Kaba. You kind of nice with the combos. Enjoy it while I last, Kaba, because this is not going to go on forever. Stay back. Damn, he got c- He got c- That man is lucky he didn't land in the lava. All right, hey, I actually haven't- Oh, what the- Oh my God. Okay, all right, all right. I got to stop sleeping on him. What the- Was that time skip? Jesus, I've never even seen him throw a Keyblast, let alone 17. I wanted to save this for some of the harder competitors, but I might need to start trying to bust out the ultimate. I'm saving it for Kevla. I saw Kevla on the list. Oh, the 6M worked. No, no, no, hands off. Hands off the merchandise.  Nice, nice. Oh, no, he grabbed- Wow, what kind of grab was that? Ha, ha, ha. Ow, ow, ow, ow, ow, ow, godly display. Let's go. How much damage does this do? Doesn't matter, I'm taking all of it. I'm taking all of it down to- Didn't do that much. 8,000, no, I'll take it. There's no way. Damn, he just uses time skip fists. Time prison. This man tried to put me in time prison. How well that worked against Sheeran, huh? All right, we're almost done with Hit. I really- I should not have just said that. Please just let me get through Hit. All I need to do is get to- All I need to- Okay, okay, okay, buddy. Oh, oh. He's fighting for time prison. I need to run, I need to run, I need to run. I need to do the ultimate. No, wait, godly display would kill him. It doesn't matter. I think I should build up my ultimate anyway. I'm running. I am just straight up running. I'll fight. I'm sorry. I'm sorry. No, no, I- No, please, please, please forgive me. Please forgive me, please forgive me. I can't let him hit me with this. Oh, that was so lucky. That was so lucky that he got hit by that. It's Kefla. Oh, I know Kefla's gonna be the one to do me in. Let's go. Wait, wait, Kefla, we can talk. All right, it's fine. I've been waiting for Kefla anyway. Man, this key comes back slow. No, no, no, no, no, no. Kefla, Kefla, Kefla, relax. Oh no, damn it. I didn't make it to Kefla. Can I get like a continue? Annoying. Ow, my ears. Hang on, I'm doing that one more time. I'm not gonna make you guys watch it, but we're definitely hitting Kefla with my ultimate, bro. You know what? I'm just gonna win. That's what I'm gonna do. I'm just gonna win this time. Oh, but first I gotta do this minigame. No, no, think. Use my brain. Don't tire up my hands just yet.  What, you're still standing? Beerus is like half the reason I lost the first time, bro. This man put the hands on me and I gotta pay him back a 10-fold. There's no way he's dodging this. There's just no way Beerus has those. I just refuse to believe Beerus has these kind of combos. What? Damn it, Beerus. Damn it, Beerus. Oh, wow. No, no, no, no, no, no, no. There's just no way. This guy's defense is insane. Beerus, Beerus, Beerus, man. There's no way, there's no way Beerus is putting the hands on me like this. I think I'm doing worse than last time. Die, Beerus. Die, get out of my game. Oh, nice dodge. Damn it. Oh, God. Hey, what's the matter, Kava fight back? Yeah, yeah, what's the matter? I'm playing a little different this time, huh? After a mid-strike coming in clutch here. After a mid-strike coming in clutch here, we be on the move. I'm going to just get full power, I think. I think I can probably force Kava to get out of here and then I can hit Kefla with this. Gallagun, damn, you really do remember your lessons with Vegeta. Anyway, let me teach you the lesson Vegeta should have taught you. You can't mess with Goku. Yeah, yeah. Oh yeah, you're looking just like Vegeta now. Oh, never mind, never mind, never mind, never mind. Kava, don't make me do this, bro. Kava, I'm, no, you know what, no. Nah, I'm saving the ultimate for Kefla. Get out of my way, Kava. Damn, look at the way he flew off-screen and it's out. Ha ha ha, look like he just slipped. I forgot about hits. I completely forgot this guy was in the way.  I completely forgot about hit. Ah, hit did not forget about me, though. Let me get full power again here. Let me get full power. Let me show you something. Let me show you something, hit. Let me show you something. He really tried it, too. He really did try it. All right, now we get full power and we get ready for Kefla. There's no way this plane backfires. There's no way this plane back- Oh, he countered?  No, no, no, I have to hit it. Yes, okay, perfect timing. No, no, no, my energy. Oh, my energy. Maybe I still have time. Oh, I still have time. Kefla, let's go. I've been waiting for you, Kefla. Panic, get out of my game. You know what? I'm going all the way to G-Rid. I'm gonna do it to her again. I've been waiting all this time. Why wouldn't I treat myself to it twice? Oh, first I gotta give him the full souffle, though. First I gotta give him the full souffle. Yeah, I've been waiting on this one, Kefla. Yeah, I've been waiting on this one. I've been waiting on this one. Stay down. She got cut. Toppo, dang, this guy is huge. Why is he, this guy is like at seven foot five on a bad day. This guy is crazy. Oh, no.  Why is he putting the men's on me? God, he's giving me the Mr. Clean, dude. Woo! Damn, oh my God. Oh my God. Oh, and the destructive fracture, what is that? Ah, oh my God. That, that Jesus Christ. Oh my God. Yeah, relax. Relax, relax, mercy, mercy, mercy, mercy. Jesus Christ. Oh my God. Okay, you win, you win, you win, you win, bro.   Oh, why did he get his ultimate? Nah, nah, nah, come here. You thought you were so good, huh? There's no way, there's no, he just backhanded me. I used all my power. I, there's no way, there's just no way I was supposed to win that. There's literally zero way I was supposed to win that. That man, oh my God. Well, I was gonna go into the Dragon World Tournament as a part of this video as well, but maybe I'll just do that another time if you guys liked this video and wanna see more of it cause I ain't gonna lie, Toppo just, just destroyed me. There is just no reason for him to do that to me at all. That was just, that was just unnecessary. We'll put it, we'll just say it how it is. That was unnecessary. Just not needed. Hopefully you guys enjoyed this video though. If you did, like I said, leave a like. Let me know if you wanna see more down below in the comments. Other than that, you can also check out some of the other videos that should be on your screen right now. I've been Dododoy and I will see you in the next one. Bye.


The study found that the quality and reliability of websites providing information about lingual orthodontics in Turkish is poor, with only 30 percent of the sites being balanced and unbiased. The authors recommend that clinicians warn patients that information on the internet about lingual orthodontics might be inadequate and direct them to higher quality websites. This article was authored by Hadisi Kubra-Alken and Arzu Ari Demerkaya.


Thank you. Thank you. Doctors. Thank you. Thank you. Thank you, first responders, UPS Workers, thank you. Thank you. Thank you, teachers. Thank you. Thank you. Thank you! Public health care professional, pilots. Thank you. Thank you. Law enforcement. Thank you. Thank you. Garbage men. Government officials. Thank you. Thank you. Thank you. Pharmacists. Food delivery people. Thank you. Thank you. Thank you. Thank you. And to everyone else working at this time. Thank you. Thank you. Thank you. Thank you. From the entire CCU athletics department. Thank you for all the hard work you're doing. Thank you. Thank you. Thank you.