Thank you. Thank you. Okay, thanks. No, no, it's all right. Justice. You're on the panel. You're on the panel. You're on the panel. You're on the panel. You're on the panel. You're on the panel. You're on the panel. You're on the panel. You're on the panel. Okay. Thank you, everybody. Good morning. Lieutenant Governor Federman, Speaker Torsi, President Skarnati, Leader Corman, Leader Costa, Leader Cutler, Leader Durmati, members of the General Assembly, invited guests, friends and family, and especially my wife, Francis. And of course, my fellow Pennsylvanians. This is my fifth budget address.  She was a trusted advisor to Speaker Torsi, a friend, a mother, a sister, a daughter, and a respected member of our community. And for the same four years, I'd look out into this chamber and I'd see Flo Fabricio, Mike O'Brien, Sid Kovulich. This year, they're not with us. So let us all remember their lasting impact, their commitment to service, and carry forward in their memory. Three weeks ago, I had the honor of taking the oath of office for another term as governor. I spoke of a commonwealth on a comeback, a Pennsylvania on a path to a more functional government, a more prosperous economy, and a brighter future for our children.  And here in Harrisburg, we've proven that despite our differences, we remain capable of doing what Washington just can't seem to be able to do, tackle big challenges, put aside petty partisanship, and serve the public interest. We must never forget that embedded in Pennsylvania's history is the fact that not one, but two noble experiments were launched here. First, there was William Penn's holy experiment. Second, the founders launched their own experiment in self-government. Both of these are perpetual experiments. When we reaffirm our commitment to these experiments, we honor both our history and we honor those founders. And we show our constituents that whether they voted for us or not, we were making these experiments work right here and that our government is worthy of their trust. Now we have a chance to show that good faith once again. In proposing and debating this budget, we get to the heart of our perpetual experiment in self-government. We show the founders and our constituents that we can govern ourselves. So today I put forth my budget address. Let me cut to the chase. This proposal asks for no new taxes. At the same time, this budget proposes to do a number of things aimed at improving the lives of our fellow citizens. The people of Pennsylvania have made substantial sacrifices in recent years to help our state get up off the mat. And despite a budget that asks for no new taxes, we now have a chance to continue making some important new investments on their behalf. Investments in our schools. Investments to make sure more Pennsylvanians of all ages have real choices when it comes to their health care decisions. Continued investments to reinforce our commitment to the battle against the opioid epidemic that has claimed the lives of so many of our neighbors. Investments to support our farmers and agricultural producers so they can continue to sustain our rural communities for generations to come. In the coming weeks, we'll have a chance to discuss, debate, and negotiate the details of this budget. And I'm going to ask for your partnership in ensuring that this important work continues and that we maintain our commitment to advancing this experiment in self-government. My administration has worked hard to make these investments possible, striving to run our government not just more ethically but more efficiently so that it is worthy of the public trust and it's capable of advancing the public interest. We've saved billions of taxpayer dollars and reduced the number of state employees without furloughs and all the while improving customer service. We've gotten rid of facilities. We've gotten rid of leases that we don't use or need while consolidating commonwealth operations within the capital complex. We've made the procurement process smarter and more efficient and we will continue to look for ways to streamline government so we can invest in the things that matter most to Pennsylvanians while at the same time serving them better. Today, however, I want to focus on the most significant element of this budget proposal. A comprehensive plan for preparing Pennsylvanians to compete and win in our rapidly changing economy. A plan to create a new generation of prosperity in our commonwealth by building the strongest workforce in the nation. The credit for our economic success has always belonged to the people of Pennsylvania. The innovators who turned new ideas into new industries. The business leaders who built great companies, large and small. And the working women and men who toiled in the fields and mines and factories not to mention the research labs, the classrooms and the cubicles. There's a reason Pennsylvanians know names like Carnegie and Hershey and Westinghouse and the reason why we believe so strongly in the power of our work ethic and the importance of individual responsibility. That's who we are. But in the background, government has been there working on our behalf building canals and highways so manufacturers could get their goods to market protecting the integrity of the marketplace to ensure fair competition and helping to unlock the potential offered by our abundant resources. In the end however, our most important economic resource has always been our people. It's always been workers that have propelled our prosperity and that's why we've always made sure to invest in public schools and universities and training centers because the path to prosperity begins with an educated workforce. That's as true today as it has always been. But while that principle remains intact, a lot about our economy has changed. New businesses, new industries, new technology, new competition. And with all that, we have found a need for new skills. Over the last four years, Pennsylvania has created more than 12,000 new businesses and more than 239,000 new jobs. We've begun to match and advance beyond our neighbors. Now it's time for us to really pull ahead. Today I present a comprehensive plan to help grow our economy by continuing to invest in our workforce. This plan calls on contributions from the business community, labor unions, educators, research institutions, students, parents, and adult workers. And it increases opportunity for every Pennsylvanian at every stage of life from birth to retirement. I'm proposing a package of policies and investments called the Statewide Workforce Education and Accountability Program. It's the next step we can take together to build on all the work we've done over the past four years. Consider just how far we've already come. We've made Pennsylvania a leader in computer science education by establishing a workforce development initiative that invests in computer science and STEM education programs for our K through 12 students. We've increased the number of career and technical education students earning industry-recognized credentials by 34 percent. And we've increased the number of credentials earned by those students enrolled in career and technical education programs by 27 percent. We've provided high school students options to demonstrate graduation readiness as alternatives to high standardized testing. We've increased participation to nearly 800 registered apprenticeship programs and almost 17,000 active apprenticeships. And we have assisted nearly 3,000 companies in training more than 145,000 incumbent workers across the Commonwealth to help employees develop new skills to thrive in their jobs. But we know that there's more to do. When Amazon made its decision to locate its second headquarters somewhere other than Pennsylvania, it cited workforce concerns as a main reason. And in Western Pennsylvania, we struggled to find Pennsylvanians to fill the jobs as welders and pipe fitters at the Shell Cracker plant. Across the Commonwealth, we have workers aging out of our workforce. And too often, the next generation of workers is simply not there or doesn't have the skills to replace them. If we can strengthen our workforce, we're going to fall behind. And we cannot let our government's response to this problem be handcuffed by stale habit. We need to continue to break down silos. We need to inject our efforts with common purpose. And we need to make sure that as leaders, we are providing direction and giving teeth to our workforce development efforts. That's why we're going to do something a little different. Starting immediately, we're going to put together a Keystone Economic Development and Workforce Command Center. Agency secretaries are going to meet each week with plans in hand and sit together to make sure no workforce effort walks alone or falls through some crack in state government. If the Department of Community and Economic Development knows that a company needs 20 welders, and the Department of Labor and Industry has a welding program, we're going to connect them. Those connections within state government are valuable and necessary. But we also need to hear from businesses and from labor. Not just when they're upset and not just when we tour a facility in a hard hat. We need to hear from them constantly. We need to know when there's a problem so that we can fix it right away. If a labor union is having trouble establishing a training program because of antiquated procedures, then we need to fix it. We need to get those workers trained and into the workforce. If a business can hire a worker because of an out-of-date or unnecessary rule or regulation, we need to know about it so we can take action. If medical professionals are concerned about a licensing backlog, they need receptive years in state government. We're also not going to try to solve every problem of workforce problem on our own. The Command Center will have a first-of-its-kind employer fund, a public-private partnership that empowers businesses to address the skills gap from their end and encourages them to share their best ideas and best practices so that we can scale them up and learn from their success. After all, government does not have a monopoly on good ideas for addressing these challenges, but it can serve as an incubator for the best ones and a partner for putting them into action. The Command Center is going to be led by the Secretaries of the Departments of Community and Economic Development, Labor and Industry and State, three agencies that have the largest impact on Pennsylvania's workforce and business development. We're also going to bring outside forces in. My friends Gene Barr and Rick Bloomingdale will also be co-chairs. They co-chaired my middle-class task force, which helped launch many of the workforce development ideas we've implemented last year and that I'm proposing to build on in this plan. They'll be joined by Tony Bartolomeo, Team PA, and Auditor General Eugene de Pasquale, who has worked, both of them have worked on these issues and will have important recommendations. But again, we need to do more. We need policies that start at the very beginning and end with every Pennsylvanian receiving an excellent education and the opportunity to land a good job. Last year, I convened a ready-to-start task force, charging it with finding ways to improve the lives of children under three and their families. I know that no new parent looks at their baby and sees a spreadsheet, but the fact is that preparing our kids for success starts long before they ever enter the classroom or even before they take their first steps. And providing services for children helps to get parents into the workforce and to fight poverty. That's why this new program includes funding for home visits to support vulnerable pregnant women, new mothers, and at-risk infants and toddlers. Home visiting programs promote healthy relationships and safe and stable home environments. They're proven to work in preventing adverse childhood experiences, giving children and their parents the skills they need to reach their full potential and lift families out of poverty and into good jobs. You know, we already have programs like this working here in Pennsylvania. Ms. Riccordia University is home to one of only eight programs in the entire country that helps single mothers who are struggling economically to complete a college degree. The program provides counseling, housing, and other services to help mothers get into the workforce. We plan to replicate this innovative job training program all across the Commonwealth. And this program leverages federal funds to improve our child care system so we can get more kids off of waiting lists and into high-quality support systems and help more parents make their way into the workforce. Pennsylvania's children deserve every opportunity to succeed when they enter our public school system. And they deserve to enter a public school system that isn't just adequate, but world-class. Restoring $1 billion in funding to our schools was an important first step. But now we need to go further. We must continue to increase funding for education, starting with pre-K and culminating at the end of a student's journey. But that's not all. It's time to lower the age of compulsory attendance to age six, bringing our Commonwealth in the line with the vast majority of other states in this country. And we should consider going even further with a careful study of the costs and benefits of universal, free, full-day kindergarten for every five-year-old in Pennsylvania. We should increase the minimum dropout age to 18 and partner with school districts to keep our graduation rate rising. Of course, no governor, no legislator can do more for a child than a teacher can. And my program empowers teachers to do even more through a program called TeacherWorks that provides them with workplace experience in Pennsylvania businesses so they can better understand the needs of employers. We ask a lot of our teachers. And if we're going to prepare the next generation of Pennsylvanians for the jobs of the future, we're going to be asking even more of those teachers, including more training and more accountability. Teachers, on the other hand, they just want safe schools to work in. They want support from their administrative staff and they want a fair wage for the important work they do. That's not asking a lot. But the law governing teacher pay actually hasn't been updated in Pennsylvania since the 1980s. And so our classroom teachers have too often been getting the short end of the stick. I don't think anyone here in Harrisburg would say that we shouldn't value the contributions our educators have made over the last 30 years. And I don't think anyone would disagree that they have a critical role to play in securing our prosperity in the next 30. And yet our government has failed to address this injustice. That has to end now. My plan increases the pay floor for teachers to $45,000 a year. This is a real investment in our future. It's an investment the state, not local, school districts will make. And it's included in this budget. This is a fully funded mandate. We're also going to start competing to recruit and retain the very best educational professionals, not just in well-funded suburban schools, but in every community, every zip code of our commonwealth. This could be a game changer for our schools, especially in our communities that are struggling to attract and retain the next generation of educators. In fact, most districts that cannot afford to pay their teachers more are located in the heart of rural Pennsylvania. And it's time to make sure we are investing in educators in those areas today so that we can prepare the kids in those school districts for the competitive world of tomorrow. We're also going to do more to recruit students, ambitious, brilliant, creative young women and men who are looking for the next step in their education. Our commonwealth is blessed with a terrific system of colleges and universities, including, I would say, community colleges. We all know that our post-secondary institutions are laboratories for innovation, but they're also launch pads for job creators and the skilled workers that will fill those jobs. And that's why my plan creates a new grant program for students who graduate from a Pennsylvania Community College with an associate's degree or other industry-recognized credential and then stay in Pennsylvania to start their careers. If you're willing to put your newly acquired skills to work here in our commonwealth, the least we can do is help you avoid carrying around a crushing burden of student debt. And if you're a parent who wants to trade up from a job that pays the bills to a job that can sustain your family, my plan includes a parent pathway initiative designed to help you get the education you need to get ahead even while you prepare your own kids for success. Indeed, my workforce program is not just about the jobs of tomorrow, it's about the jobs of today. Last year, we launched PA Smart, a comprehensive new initiative focusing on STEM skills, apprenticeships, career counseling, and public-private partnerships. No matter how old you are, now is a great time to acquire new skills, and we want to make that opportunity available to every single Pennsylvania. As part of the PA Smart initiative, we just launched a new website, PA Smart.gov, that consolidates workforce resources and information for Pennsylvanians who want to get the training and education to enter the workforce or expand their skills. It's similar to the business one-stop shop we built last year and that we're still improving upon. We need comprehensive digital portals for both businesses and workers that gets them all the information they need in one place and that breaks down agency barriers. This year, I'm proposing $10 million in new funding for PA Smart so we can fill more advanced manufacturing positions. We can help more nontraditional students obtain the training they need to compete in the job market and create more jobs at better wages for more Pennsylvania workers. This program also includes funding to help returning veterans get the training they need to continue their contributions to our Commonwealth as members of our workforce, and even better, that funding is transferable, meaning that veterans can use it to help their children get a college degree or career credential as well. It's a GI Bill for Pennsylvania. One more thing, we cannot comprehensively address our workforce development system without fixing our criminal justice system. Tens of thousands of Pennsylvanians are shut out of our workforce or they're underemployed because of mistakes they made in their past. Families are being denied providers. Employers are being denied skilled workers. We've already passed clean slate legislation right here, making us the very first state in the country to do so, but we need to go farther. We need to make our criminal justice system more equitable and fair while helping people who have made amends enter the workforce. Indeed, even as we work on this budget, we also have to improve reentry programs and make it easier for those who have done their time to succeed in the workforce and in their daily lives. Our challenge demands an all-hands-on-deck approach, and this budget proposal itself asks Pennsylvanians to come together, business leaders, educators, students, workers, to address the challenge of renewing our prosperity for another generation. In my inaugural address, I asked us to do our best right here in Harrisburg to do two things. First, of course, to ensure the interests of all Pennsylvanians are reflected in the policies we pursue. But second, to show the world that Pennsylvanians know how to make representative democracy work. This budget is the embodiment of that noble effort. It asks for no new taxes, no new burdens on our citizens, while at the same time increasing dramatically our investments in the public goods that will make life better for all Pennsylvanians. This budget recognizes that government should not try to do everything. We have a long-held faith in our tradition of limited government and individual responsibility. But it also recognizes that government should not do nothing, either. The public goods government invests in should make the lives of our fellow citizens better. Public goods that give Pennsylvanians the skills they need to thrive in our 21st century economy. The public goods that promote their safety and their health. Public goods that connect them more seamlessly with each other. Public goods that keep our air and our water clean. That's what this budget aims to do. It makes investments in workforce readiness in our early childhood system, our schools, our universities, our community colleges, our apprenticeship training programs. It makes investments in ensuring that Pennsylvanians of all ages have real choices when it comes to their health care. It continues to prioritize the fight against the opioid epidemic that has destroyed the lives of so many of our friends and neighbors. But above all else this budget proclaims to the world that right here in Pennsylvania we do not indulge in the sterile politics of anger and insult, that here we know how to engage in the respectful and honest give and take that must stand at the heart of a functional democracy. While the rest of this country and indeed the rest of the world descends into divisive, nasty and unproductive bouts of shouting, we're showing everyone else right here in the heart of democracy how democracy is supposed to work. So this is our challenge. It's not just about yet another annual budget. It's about our democracy. Let us show the world, along with the rest of our country, that right here in Pennsylvania we are making this experiment work. That we are rededicating ourselves to this noble experiment in democratic self-government. Let's show that in the way we tackle the challenge of preparing our commonwealth for a brighter future starting with this budget. This, and no less than this, is our task. This is also our privilege. May God bless us in this task and may God bless the commonwealth of Pennsylvania. Thank you.


Alright guys here we go three box NFL mixture 2022. I'm at Phoenix and Don Russ number three random teams Find the results of late and sports cards calm if you need to check them out again. There's a Lincoln shot Let's do it start with Don Russ then Phoenix and I'm at kind of space for breaks All right, Donner's first come on. Let's see a night moves or a Downtown Even a marbles haven't seen a marbles SSP, okay, I haven't I haven't pulled one yet, so They were always the toughest one to pull though for whatever reason Shot white McCaffrey McBride portraits Red fedarian Mathis rated rookie commanders Son Haskins Zack Wilson on the Zachary Capone Wilson. That's a cool middle name Is that like Jason Capone? No chance he's the other Jason Capone. Oh, right Press through Fred Nick Bosa zero chance, right? Christian Watson rated rookie Bailey zappy the rookies George Pickens throwback there for sweetness or no, that was singletary not sweetness George Carloftus Drake London elite series Malik Willis dominators Watson Hassan Haskins and a Gold press proof mink if it's Patrick it goes Steelers nice color match 1 of 50 who is Andy? Snoop a No-name variations at tibidoo. Yep, cave-on tibidoo for the Giants rated rookie Fans of the game Kevin Durant's commanders press roof Eliza Veritzucker Kobe Dean Aquius test on the Donovan people's Jones cup Red press through Trey Hendrickson. Oh nice Nick's Kings Dude wasn't Vons and this is the biggest Nick's Kings game my lifetime It's so funny. It's who a power-plus duty red press through John Dotson commanders. That's so funny. I Don't think he's wrong though Maybe at least regular season ever The rookies James Cook I Was UCLA that's pretty cool Jermaine Johnson portraits Come on SSP come on now SSP This spiller Hutchinson elite series Dominators Antonio Gibson Hamilton nice a Jameson Williams purple 191 of 500 Lions rated rookie Yeah, not gonna show every single base card or at least for a long time Dual Jersey Tony Gonzalez and Kyle Pitts to 199 and passing the torch We'll do a two-sided card there. It's Carter and a press-proof red Nico Collins Sam Williams on the rated rookie Wanda Robinson the rookies Brian Robinson jr. Portrait rated rookie and a red T Higgins Wanda Robinson JK Dobbins elite series AJ Brown Is a how does he Titans AJ Brown and a red press proof Michael Thomas Daxon Hill Zach Wilson gridiron Kings Kurt Warner Desmond a reiterated rookie is this it be a nice one if it is Yeah, the rookies auto Christian Watson bookend 99 of 99. We go very nice head for the Packers That Christian Watson elite series behind it Yeah, pass the torch is pretty is it is a pretty cool design. It's kind of classic though It's been they've used that design for a long time sure I'm forward. I don't know if they've always been double-sided though I don't know that Aaron Donald the Drake London on the portrait in the orange Fletcher Cox Eagles number 84 of 91 84 of 91 Last pack of Don Ruston Phoenix To Marvin Leal DJ more power plus franchise feature at the end and right a rookie press-proof red Terry Davis price Niners For Jersey numbers This is 99 of 99 Good call Shane good call Shane for Jersey 99 of 99. All right box of Phoenix now Wanda Robinson to 149 on the rookie Jersey card for the Giants Color burst my homes nice Love the color versus here. I'm gonna have to get some I actually bought a lava type on board the other day Rookie teal Isaiah Spiller because I like to parallel so much. It's like a maze. We'll get a Patriot It's 150 on the Isaiah Spiller a flamethrowers burrow flamethrowers Trevor Lawrence bronze 36 of 50 go Jags nice insert hot routes Mike Williams Orange brand that I yoke Niners 23 of 99 contours my homes pink Jalen Hertz Eagles 143 of 199 rookie rising Garrett Wilson I'm done there. We got a teal contours rookie Matt Corral Panthers 124 of 150 Hot routes Cooper cups Cooper cup hot routes Cooper cup Anybody ready to buy a specific team next week and flawless basketball or you just you're not gonna tell you don't want to get sniped Oh, that's a nice AJ Brown black prism eight of ten for the Eagles Black Phoenix is just so sick Jamo Lyons rookie. I mean black and any the chrome products Be so cool. If he was wearing the alternate red I uke Niners Number 229 out of 250 Justin Jefferson Shane, you should have called a Skymore Nebula Crystal Lave rookie red 53 and 250 for the Saints blame there was Herbert Fire and ice rookie cave on thibbadoe Giants 31 to 50 contours Trevor Lawrence Peer strong junior red 250 Patriots rookie Cooper cup teal for the Rams 50 of 150 and I'm act time so bonuses a bucket dude He is he's so good He's gonna in his career being like a 12 like a 14 or 15 time all-star He's so good Orlando magic legend right there Trade on draft night Rashad Bateman 44 of 99 Ravens. There was it was there. Where's an auto? Overall, yeah, no autos in Phoenix guys Patch card 22 a 25 Cowboys Tony Pollard got Bill's dual Jersey Jim Kelly and Josh Allen to 99 Dude, look at this thing. Look at this rookie cap patch Bailey Zappy Two of six with the camo It's either salute the service or Memorial Day, right?  That's mzappe right there. That's filthy. Yeah, unfortunately Joshua We are gonna recapit the zappy We will recapit the zappy. We're also gonna rip another Phoenix box and take any autos Archie Manning prime patch auto to 75 for the Saints grad Saints Packers RPA Romeo Dobbs 83 of 99 We go Packers his auto Little rush there it looks like Grads Packers like I said, we're putting the extra Phoenix box here because we didn't have autos in that Bonus box, you know, we need our autos, right? We need our autos. This one's on us guys It definitely sucks getting in a break with three boxes and one of the boxes and have either of its autos Bonus box bonus box This one's gonna come out of Dylan's paycheck actually fire forage drew breeze 145-199 Saints Flame throwers Jalen Hurts Eagles Yeah, I can't do it every time obviously But this is the first time I really seem to Phoenix box like that sometimes you see it But like if you're doing a case it evens out for the most part, but There we go. Here's our first auto Tyler Beatty Ravens 12 and a 25 rookie auto Silver rookie Leo Chanel chiefs Good luck in the bonus box Pink deck press got flamethrowers to 150 to 175 Cowboys. Oh, yeah. Oh, yeah, Iowa State rock pretty breeze haul the same team. It's kind of wild It's a lot of a base. You got a teal miles Garrett to 150 for the Browns contours Brock Lesnar Why don't they have contours John Cena in this purple kiddle Niners Numbered 80 125 Malik Willis Titans rookie rising here comes our patch auto I believe tyke want Thornton to 50. Oh, not not not the auto. Sorry rookie patch Patriots. I thought it was gonna be Still nice for the Patriots. They're good looking yellow And a color burst for the Falcons rookie Tyler Algier Nice done in the month. Make sure you finish blue hands. I got I got one semester left to go and I never went back Classic Khalil Shakir rookie lava for the bills for 130 to 175 Although to be fair, I would never have done anything with my degree. So hot route straight London hence. I didn't finish That's why I didn't Walker Matt Corral to 50 on the rookie dual patch auto for the Panthers In silver Davis Mills Texans. Oh, it's your masters. Oh, man You already finished once you're here. Yeah, you already got done with school once.  I love this. I love this school thing. I need to go back to some more school Doesn't matter to 99 rookie Falcons. I'm just messing and grads though, man contours Corral Hey, that's what I did, but I didn't even get close to getting a I got close to getting a bachelor's Yeah, Roquan to 75 Ravens I'll open the first up breaker college When I when I get in my later years, I'll just open I'll be the The Dean and the only professor at the breaker college Trostin Rambo rookie ready for the Panthers the 250 That's Orlando Guardian legend right there actually Yeah, of course guys and pink Mark Andrews Ravens number two one 99 not the best Well, we got our autos and we got some extra, you know numbered cards everybody That was not the best box though tough boxes Phoenix guys. I'm sorry, but they get the bonus for y'all Sometimes I was bonnet sometimes you're up a bonus box and it's just like what Recap now it's your brown black to 10. That's a nice one Tony Pollard patch Kelly and Allen dual Jersey Wondell Robinson passionate torch pits and Gonzales for the Falcons tyke one Thornton autos of Tyler Beatty Christian Watson's a nice one for the Packers Matt Corral Romeo Dobbs RPA for the Packers Patch auto was Archie Manning to 75 Saints and Bailey's happy hat patch two of six Such a cool patch that'll do it everybody. We got another one of those mixers coming up


Hey guys, we are live here in Pasco County, Florida and I had to share with you this decomposition that we just got called to here. It is extremely bad and I'm going to explain to you what happened here and so you can really get the magnitude of it and then I'm going to show you some video and pictures so you can really see this. So this single white male lived in this two bedroom apartment by himself and passed away in early January and just so you know today is the 13th of February. So we're talking probably a month and a half deceased, undiscovered, he died on the floor of his bedroom and melted through, he's on the second floor, melted through his floor and he's dripping through to the first floor apartment which is a lady and her children. They noticed maggots and they are getting sick to of the smell and of the odor. So not only do you have the death in here, the filth is extreme. I mean we're talking disgusting. So I'm going to show you some video here and explain to you as best as I can but this is bad. So it looks like the person was bleeding for a while from whatever reason and didn't get treated or didn't get any attention and because the blood is in several areas of the room. But it's not blood like he was beaten or anything like that, it was just somebody was sick. So I'm going to turn the camera here and you guys can take a look.  Look at the walls, I mean you see, you see this here, look at the floor, hopefully you can see this, it is a little bit dark but I don't have any light, the light's not working. Look at this wall, absolutely gross, like absolutely gross. Look at the fridge, look at this. Okay so these, that's the kitchen and the entryway. So check out this TV room area. So apparently this person was a severe alcoholic but this place was very very neglected. So take a look at this carpet. So somebody liked vodka a lot. Now we're going to get into the bedroom where the death occurred but take a look at this hallway and notice the color differentiation of the carpet. So it's pretty bad, like I said, it is extremely bad. So for those of you that just joined this was a single male that passed away in early January. He was found only because he melted through the second floor into the bottom floor apartment and a woman and her children saw maggots and saw it coming from the ceiling.  That's the way it smells, it's pretty obnoxious. So any questions that I can answer from anyone regarding this horrible horrible cleanup. Okay guys I am signing off here, hopefully you've seen everything, I'll post some photos as well. Thanks for watching.


Of course, you all know that one of the big new features with the last release of D.B. and Sarge was a new installation system called D.B. installer and well, if you're some guys who are pretty much involved in the development of those nice stuff and who will tell us a little bit. So please welcome Joey Hess and his dancing apes. We have 45 minutes to do a talk. We're going to talk about the past, present, future of D.I. and how you can help with it. And we do have four people giving the talk, so wish us luck. I'd like to introduce everybody who's up here. We're going to start off with Holger, who has contributed to D.I. on the manual German localizations, other things in that area. He's been working in D.I. for a couple of years. And he's going to talk about the general overview of D.I. and then we have Christian, who is basically our internationalization coordinator. He basically gets lots of people to translate D.I. and does it really well. And he's going to talk about that. Over here we have Franz Popp, who's mostly been involved in working on the manual builds, that kind of thing. And is now taking over as a D.I. release manager. And he's going to talk about mostly the manual and I'll wrap up with future items and questions. I'd like you to hold your questions to the end, if you could, in case we don't run out of time. So, that's about it. I just wanted to ask anyone who's in the audience who has contributed to D.I. as a translator, as a developer or anything to please raise your hand. Loads of you. Well, I think we should just give you all a big round of applause because D.I. has made Bevian great. I'll hand things over to Holger now. Sorry about that. Microphone working. Hello? Hello? Hello? Oh, yeah. Now it's working. Yeah, start with the retrospect of the boot floppies. As far as I remember, I've always used boot floppies to install Bevian and it really always worked. It was the partitioner. It was not so easy to use, but after some years you got really used to it. The problem with boot floppies was that they were not maintained anymore since the end of the 90s. Nobody wanted to work on them. And for Woody, they were really a pain designed for I-386. There was no hardware detection. Localization was not really well included. It was made for Woody, but yeah, it sucked. And yeah, they were designed for floppies and so CD on that boot was also hacked into it. And the graphical installer was also not really possible with boot floppies. DI, the design is based on Depthcon mostly, which makes different frontamps very easily so we can have a graphical installer in Edge with, yeah, we'll have it. Also it's easy to translate. So internationalization and localization, as you already know, is part of DI. And also Depthcon gives preceding. So it can be used for various grades of automatic automation and with UDEPPS, DI is also modular. So the DI team does not work on the whole installer, but there are different people working on different parts of DI. UDEPPS are basically deviant packages, but they are smaller so that they fit into RAM disk and they don't have to comply with policy that's also because of the size constraint. Another design aspect that was used is the main menu, which is normally hidden from the user in the basic install. In cases of errors, the menu pops up and you can redo steps or do other steps like enabling SSH for network console or other things. The UDEPPS have one special control header, which is read by main menu and defines the order by which those functionalities are put into main menu. And this is basically it, the most important parts of the design. There are other parts like the partitioner, but those can be exchanged for another partitioner. This is basically what DI is based on. As you know, DI is teamwork. There are different people working on different areas. There is no real leadership, no formal leadership, but there is, of course, Joey is very much involved in everything. So it's very wise to get his advice, but it's only his advice that we discuss things on the mailing list or on ISC channel or in real life meetings. Yeah, for the code, we use the subversion repository on alias. The commit messages go on the mailing list and on the ISC channel. So you can see in real time, if somebody commits something, if you're on ISC. There's a trunk for new development. Experimental stuff is done in people branches. And there's the search branch for maintenance now. During the release, there were also release branches, which were used to branch the development from the trunk, basically. Yeah, this is how the development processes. And now, Christian will get some details of localization. Do you hear me? Is that fine? Okay, thank you. So it's again about localization and internationalization. Sorry about this. So what are the drawing IDs of DI localization? Well, the first one. Okay.  This is about all displayed text have to be translated. This is the main ID behind English sucks. Actually, in DI, English does not suck. It is very well written, very well reviewed by many people to be of the best quality possible. And of course, the translation also. Other drawing IDs, Olga said, we are based on Depcon for all our interface. So every translation goes through Depcon, and especially for the use of get text in PO-Depcon by using the PO-Depcon. The wonderful PO-Depcon system introduced by Danny Barbier over there just after the release of Woody. All translatable material go to Depcon templates. There are some enhancements to Depcon, in C-Depcon, to handle this. And there are some text templates, which are not very used in your packages, but are used in DI. So everything is in Depcon. So first of all, what is about interlocalization? This is what we covered with potato. OK, get a picture. Only English. This was Woody, pretty nice improvement. This is what we have in Sarge. And hopefully, this is what we will have in Edge. Not a big part, but I haven't seen you the small part in Asia. Yes, we expect to cover India, actually. So let me do it once again. Yeah, yeah, yeah. And yeah, yeah, yeah. Well-domination. And actually, I'm just doing a commit because I have an agency. I'm just committing 10 more languages in the DI repository. And we will add Vietnamese, Malagasy, Indian, Macedonian, Tagalog, Berarussian, Punjabi, Esperanto, Wolof, Cosa, and Estonian. That's the point. Cosa thanks to the Ubuntu people. Thank you, Mark, for giving the Cosa translation. There seems to be a question over there, but. That's basically, yeah, the question was about why are some countries not covered? Well, this is mostly to get you a picture. Many of this country actually have either English or French, especially in Africa, as official language. But I don't consider this country covered because their main language is not covered. This is also special for India because there are so many languages. There are like 20 languages over India. So I just put India in red because I expect these 20 languages to enter. Okay, so. Sorry, Christian? Yeah. And another red space to your slide. You might be getting some correspondence from somebody who wants to be Mongolian. The old script of Mongolia. Oh, yes, probably, yes. You're puzzling me a little bit, actually. So don't be too nitpicking these white spaces in this world map, actually, please. Okay. So how do we proceed? We have the concept of levels. So we go levels from DI translation down to world domination, okay? So first of all, what we call core DI package. This is what we call DI. Actually, this is all what happens before the first reboot. The second level is called level two, of course. This is the default base system install when you only install the base package. Everything that is used to input users has to be translated, only input users, not displayed text. Level three is any kind of base system install. Any user prompting has to be translated. Level four is all DI is translated for a base system install. You don't see any word of English except the kernel messages, hopefully someday. Anyway, and we will soon add a few more levels up to world domination. Probably level five will be the default desktop installs, all the prompting of x.org probably, and a few more things. Level six is translating every depth const templates all of the standard packages, and level seven is world domination. Of course, everything is Debian is translate. So I got seven points. All right, it was more like kidding, including kernel messages. I think it's a bit hard work. But you know, windows speak French to me, so we should do it. Okay, what's the future, except translating the kernel? We of course need to add new languages. I just added 11 languages, sorry. Some very small languages, very few spoken, and some quite white spoken, such as Indy. We need for this more locales for people who attended Dennis Talk just a few minutes ago, which is not easy to do. We need probably for this to have an easier to use framework, because most of the new translators are not very skilled to our SVN commit, and so on, and so on. So we need very simple framework. So I put a little thoughts, but there are already, ideas are not very clear, not matter, in my mind at least. But it's not a word clear in my mind. New languages, we need a graphical installer. This is probably the main point in localization for the well-combining languages. We talked a lot with Jalda about the support for Indy and all other languages from Indy. They are very tricky to support. We need to start depending on unicode text mode phones, the one we show because a lot of characters are missing there. We need better right to left and bidirectional languages display. Actually, we made a big progress during that conflict because now, Hebrew is right aligned. And before we had Hebrew right to left, but left aligned, which was silly. And of course, we need to final to universe domination and support Klingon to France for the installation guide. Thank you, Christian. So let me start off by asking a few questions. Who has actually done installations using DI? Well, that's both people. And who has used the installation manual while he was doing that? A while? While or before or whatever. Well, quite a few people, but absolutely a minority. And that's part of the problem with manual, I think. So these are the areas I will cover during this part of the talk. For technical aspects, I've covered some of them in the paper. So if you're interested in how the installer is written, how it's built, how it's translated, then please read the paper and visit the manual website pages because there's some more information there. The basic thing about how the manual is written is that there is only one source for all architectures. And there's a heavy use of conditions that makes some paragraphs appear in the build for one architecture and not in the build for other architectures. This makes it fairly hard to work on the manual because you have to keep all those relationships in mind and you will be confused by text that concerns an architecture that you may have no knowledge of. The manual is available in four formats, mainly published in HTML and is available from several sources. The official website has the current manual for the Sarge release and that is still being updated. So if you're looking for the latest version of the manual, please don't use the ones included on the CDs, but go to the official website. There's also a package Debian installer manual, but that has the same drawbacks that was built at the time of RC3 release of the candidates of DI. And so it's somewhat outdated. The development version of the manual has recently been updated so that it now reflects the edge version of the installer and that's between quotes because well, we may backport some of the new developments that are in there at point releases for Sarge. So then they will of course go into the Sarge version of the manual. So here's the status of the manual and as you can see, it's still largely based on the manual for Woody and as that was made on bootfloppy, or based on bootfloppies and there's a really big change from bootfloppies to DI, that's not a good thing. It's also not very well balanced. There are few areas that are covered fairly in depth like how to set up a a net boot server for net booting, while other areas like the details, the more specific stuff you can do with the DI, like details of preceding are not covered at all except by means of an example file, but it's not like written out what your options are and where stuff starts to happen if you do it a certain way. The big black border is there for a good reason. For a number of architectures that are listed, the manual includes this warning and that's because, well, since Woody, it has not really been checked for that architecture. So the information in there may not be accurate and what we really need is people involved in ports to care about the manual for their port and help us to check the manual against actual installations, tell us what's wrong there and if at all possible, help by submitting patches to the manual. And I'm, of course, willing to help you find your way around the XML source or even if you don't want to bother with that, take the HTML page, copy stuff of that, change it, submit the change text and I will worry about how to get it into the XML source. That's no problem, but we really need help in that area. So for translations, originally we used docbook.xml and originally the only option translators had was to take an English XML file, copy it and just translate the text that's in there. And at that time we had seven to 12 languages, seven languages were fully translated, the others were in various stages of progression. Last year we made a big improvement by adding support for PO file translation and that's drastically increased the number of languages languages that we now have for the manual. It's, we have currently 13 full translations and another six are being worked on. Besides English, you can see which languages are supported and especially I think the oriental languages are very well involved here. So what are we, what do we want for the future? If possible, more translations. There are also a few languages for which we currently can't build the PDF version of the manual, mainly the oriental languages, Russian and Greek or rather everything that really uses different characters set or font rather than letter type, then English and Western languages. I really hope that we can get there by also getting more work done together with the DDP project. I've heard that they would like to switch from Debbie and Doc, which they're currently using, to Docbook XML, well we are already doing that so I guess we could learn from each other and I also hope that for example the people in the oriental communities can help work out the PDF problems because they must have solved that already, probably. And the last thing is that we should think about restructuring or splitting the manual. Maybe into a guide for newbies, people installing Debian for the first time where we cover just the basic flow of an installation and a second guide which goes more in depth into the features of the I and how you can use it to customize how, for instance, derived distributions can work with it. So your help is very welcome in this area. That's the end of my part, I'll now hand over to Joey. I'd like to finish up the talk by talking a little bit about the future of DI and how you can help and get involved if you're interested in doing that. So I thought, first of all, I'd look back a little bit. These are two graphs. The topmost graph is how many people have committed to DI each month in the five years since the project was founded and the red commits or most are just everything that isn't a translation, green is translation commits. Then actually a number of people who've committed translations each month. So as you can see, we've grown the team quite a bit. Over the past, over mostly of this year, it's fallen off a little bit as we just tried to settle things down and just get everything stabilized for Sarge. You can see on the bottom graph here this is the actual number of commits each month by translators and by developers. And you can see that we did have some big peaks and things have again settled out there. If you look at these graphs in detail, which I probably shouldn't do, you can find all kinds of interesting events in here, which actually I should probably ask Christian for, because I'm forgetting them. But for example, you can see when we began to add lots of translations here, you can see a peak, which is, I believe this little peak here in 07, 2003 is around the DebConf in Oslo when it really began a lot of work and then we have several beta releases and so on. And anyway, the interesting thing from this graph from my point of view is that it definitely was up until the right, which is a marketing term, I believe, pretty well until we started stabilizing things out for Sarge. And I think it'd be good if we could pick development back up and really get some energy back in here and start doing lots of cool things again. So to that end, here is a slide which is very much not Zinni compliant. I believe it has 14 items on it, so I don't expect you to remember at all. But it is just some, very few of our to-do items. You'll find most of these in the paper. A couple of them have been added during DebConf here just based on feedback from people and things that have been brought to my attention and bumped up the to-do list a little bit to see if you can see them here. So I don't know if I have time to go over the whole thing, but I'll do a few of them. The topmost one sort of affects Debian as a whole. We would really like to move over to using UTF-8 by default as far as the installed system. DI already uses UTF-8 throughout, but you end up with a Debian system that isn't in UTF-8, which can be a little bit of a problem if your native language does need UTF-8. Next two items here. DI updates for Sarge and support for installing Sarge using the Edge installer are basically two different ways that we could attack the problem of having Sarge out there with a 268 kernel and no newer kernel version and lots of new hardware coming out. We would like to come up with some way to get newer kernel versions available using the Sarge installer. That's probably pretty technically difficult, but we at least need to do it for security fixes. As far as supporting installing Sarge using the Edge installer, that's something that we expect will happen and we'll just continue to support the installing Sarge throughout the lifetime of the installer, hopefully. The Sarge installer actually supports installing Woody to some extent due to the works of school Linux who actually use it to install Woody, so it shouldn't be a big deal. Next one is a big one, of course, the graphical installer. We do have a graphical installer, but very few people have actually managed to build it and get it to work and we do a lot of work in that area and once we get it working, a lot of work on polishing it and making it nice and actually taking advantage of everything you can do with a GUI. And I do think that's an important thing because it'll pull in a lot of new users who may be a little bit scared by the current text mode interface even though most people do find it fairly easy to use. Also, well, next one, improving automated installation. We do have a fairly good automated installation at Debian already using the installer, but there are some little areas which make it sort of difficult. The fact that you have to pass a whole lot of kernel command line parameters when you're booting, just to get it up to the point where you can automate the rest of the install can be a big problem. It makes it really hard for people who aren't intimately familiar with that stuff to get it working and I'd love it if we could just have some very simple documentation that walks you through every step of setting up an automated install so you can have your own CD image that automatically installs Debian exactly how you like it or you can have your network like we have here, netboot, DI as soon as somebody plugs their machine in, it'd be great. And so that's an area we want to work on. One of the ideas along those lines is to use DHCP for sending all the pre-seed information across the wire. There's some other ideas which could be worked on there. Next one is one that I threw in for the fun of it, encrypted file system support. I think it'd be great if you could just boot up DI and install your system with encrypted root file system on your laptop. And I don't know why nobody has worked on this yet but as far as I know nobody is. And I think it'd be a wonderful thing and our partition was actually designed with this as a specific feature in mind from the very beginning. So I'd love it if somebody out there did that. Another area where we need some work still is in hardware detection. Some of the big problems that we know about are the serial ATA drives pretty much. You know, they work sometimes. A lot of the hardware doesn't work. Apparently some of them that should work as far as the kernel support still don't work in DI. We need somebody or quite a few people probably to figure out individual cases why these drives don't work and get back to us with all the details of what we need to just load the modules up in the right order or whatever so they work. Which should be pretty simple if you actually have a SATA drive that doesn't work. I'd really encourage you to pound on it until it does. Other issues as far as hardware detection are currently we're using Discover in DI. We're thinking about using Hot Plug. We're thinking about moving to Discover 2. Haven't really decided what to do there. But we probably can't stick with Discover one forever and Hot Plug and Udev sort of go hand in hand and we're probably gonna have to move to Udev pretty soon because they're dropping DevFS out of the kernel. They don't think anybody uses it. Another issue in hardware detection is that if you have two network cards right now, it's fairly common that you'll install and get one of them as F1 during the install and then after you reboot, you get it as F0 during the install and after you reboot it will be F1 which completely screws up the rest of the install of course. That's really fairly difficult to solve completely just by loading the modules in the right order because it's basically just an ordering issue. Which whichever order you load the modules and you have to make DI and Debian exactly the same. So an alternative is to use Ethernet device naming so that it doesn't really matter if it comes up as F1 or F0 because you've given it a nice sane name which is something I'd love to see rolled in the DI. I think that Ubuntu already has code in this area and we just haven't gotten around to doing it and it's also to some extent, this like UTF-8 support is something that Debian has to decide they wanna do. It's not something that DI can just foist on Debian. So a lot of these issues come down to what Debian wants too. Next one is another good example of that because we are in the process of splitting out non-free firmware and drivers from the kernel and that means that DI is gonna have to deal with it somehow and probably requiring that users load it from a floppy or something isn't gonna make a lot of people happy. So we have to come up with better ways to deal with that. We've already done a little bit of work with using the NIT-RAMFS which lets you basically append the modules to the end of your DI boot image but we haven't figured out what to do about CD installs and all this is still fairly up in the air. We haven't figured it out. So the next issue here is an issue which I don't know if anybody in the room could help with but we would dearly love some help from people who can help us support people who are blind using the installer. Right now we do support it but only if you install from Floppy's which is pretty weird. Another one which since I'm in Europe I thought I'd mention is installed from PPPoE. Seems to be pretty big over here. There's even still some people here who use ISDN and we occasionally get requests for that and that's definitely possible to add to the installer at this point. It's a simple matter of coding and it's probably not even that hard. We already have all the modules there. We even have PPP in the installer if you need it. You just need a little bit of glue code to make it all work. So let's see. Yeah, the next one I think I'll skip for right now because it's something that's just my pet peeve but when after that, disk space checking for tasks would be really nice if when you went to install a desktop task you didn't download a gigabyte of data, unpack it all and run out of disk space in the middle. So if someone would like to work with me to develop a patch for that, that'd be great. I haven't quite figured out how to figure out how much disk space a task uses at runtime without being excessively slow or ugly or something. So I really appreciate some help there. Next one, there's a lot of work that we could still do to make it easier to customize the installer to let people put their own kernel into it and that kind of thing. We need more documentation along those lines and so on. So in the final one, which is I think probably one of the most important things we can do right now is just find a way to find a single question during the install and make most people not see it. And repeat, until done. So that's my enormous checklist of a few to-do items. And I think I'll open it up for questions now. So questions from anybody here. And I thought I'd also mention that we're gonna have a meeting today at seven. It's over in the glass walled room. And everybody's welcome to attend, especially people who've already worked on DI but anybody who's interested or would like to help or whatever, welcome to come. So questions? Anyone? Jodor? Jerry, yesterday I heard that Ubuntu is also working on a graphical installer. Are they working with the Debian team or this is a separate project of their own? I actually haven't heard much about Ubuntu's plans for a graphical installer. I bet it looks like Mark's gonna tell us all about it. Colin continues to hack. I think he did the GTK stuff for DI. That's right, he did do that. But we're mostly likely to sort of do a copy from live CD thing like Nopex. So we'd have two ways to install graphically effectively, either the industrial strength DI one, which would let you configure it in more detail or the kind of copy from live CD approach. And you're gonna use DI for the copy from live CD approach or something still sort of. Okay, so the live CD uses DI, he said. Got a question? Yeah, if I've seen about what, which areas of Debian you've talked about, I think it really touched most of the areas of Debian, so have you had the feeling that the Debian installer was something like a push in many areas of Debian to bring new things in or did it just take things that existed and integrate in this installer? And how is your relation to, for example, package maintainers of a DHC client or something like that? Well, you know, one of the things about DI is that it's sort of like a little miniature Linux distribution based on its own package format and all that. But the fact of the matter is that all these little packages are maintained by people in Debian. Our DHCP client, you'd have this maintained by the same people who maintain your DHCP, your DHCP DEB. And so we do have fairly tight lines of communication there. Of course, there is a lot of work that we've done to push changes into Debian that make it easier to install, you know, things like people just have to use Debconf now and we had to go through and make sure that was true. And as far as things like UTF-8 support, you know, we have to let Debian know that it's a problem that the installer has to fall back to non-TF-8 at the end. And so I think there's an ongoing process there of just communicating ideas back and getting things from Debian as soon as they become available, of course. You know, we work closely with a lot of different areas of Debian at this point. I hope that answered it. Next question? Yeah, I was curious about what you guys are thinking about how you're gonna go about doing graphical installers, because I know some of the issues with doing that and why it hasn't been done so far is because it's very architecture-dependent. And I suppose, like you can't use the Piggy installer from Progeny because it's I-386 specific, but if there was some initial architecture detection at the very beginning to figure out if you can use that, would you use something like that, or what are your thoughts for dealing with that? Okay, as I understand it, the current graphical installers that exist is a GTK front-end for CDebconf, which then runs on top of either X or a GTK frame buffer interface. And we haven't quite settled on which of those to run it on because that's one of the harder parts of the problem, of course, just to get a display up there. As far as hardware detection for getting the graphical installer going, and ripping something out of Piggy or something like that, we found it's really hard to take very much from another installer. We can definitely take ideas and we can take small pieces of code, but it's just the way these things work. It's very hard to take larger chunks, fortunately, which is actually something that DI aims to solve to some extent. So I hope that answered. I also wanted to remind everybody that we do have three other people here who could have specific questions addressed to them if necessary, or if y'all have anything that you would like to add to any of my answers, please. Okay, so who's next? Okay, Sapphire. Let's try to get one over there next time. My name is Sapphire Cicero, which I come from Bosnia and Herzegovina. I work as a DI translator. I just have one question regarding the development of DI. That is the speed of the development. I know that we have had the problem so far in relation to kernels in DI. I mean, in relation to updating kernels, especially 2.6 ones, to a new revision. That's why we have a 2.68 in Sarge, and not some more recent kernel. Because it was very hard for us to keep up with security updates and supports with kernels in Sarge and likewise, other kernels which are in the archive. I'm just wondering if there are any changes being made now or are planned for the future so that we can avoid such a mess because we have so many kernel packages. Okay, thank you. That's a great question. Part of the answer to that is we've already started work to address the issues that made it very hard to update to new kernels toward the end of the Sarge release process. And we were working with the kernel team pretty closely because they were very interested in this question too, of course. I do think it's important to note that this was the first time that we did it and we've learned a lot and we were very cautious about some areas as far as getting DI out there for Sarge. So for example, I believe that the kernel team still intends to upload 2.6.12 today. And I intend to update DI to that within like half an hour of their upload. It's already, as soon as they give me a dip. So I do think we can improve. I think that we're going to, okay. Anybody else? Yeah. It's important there is also a need to have creative testing when a new kernel is implemented in the installer. Because it will break for people who have previously had successful installs. Yeah. One question I guess mostly for France about the documentation. I've heard about preceding for a long time. I've sometimes read that blog entries about preceding, I have yet to find documentation about preceding. How do I get preceding done? Is there any basic documentation to get me started or do you need help on further documenting it? What is the current status? Well, there is basic documentation. There is a section in the manual about preceding and there is an appendix that has an example precede file. And you can take a lot of tips from that on how to get started. The problem is that the more advanced features of preceding are not documented there. Like if you used early command or late command where exactly does that command happen? You really need to test it out a bit. And also for some questions you will just need to get into the code or get into the DEPCON database to see what values are being used and such. There's no full list of values that can be preceded. But I don't think that's going to happen anyway because there's just too many options. But a little bit more documentation about the possibilities you have with preceding would be very good to have, yes? On that subject. I've got a worked example of preceding which makes it fairly easy to get up and running pretty much instantaneously with how to and how to set up your media for CDs, USB sticks and PXC booting. And it's at hands.com slash D minus I. I'm quite happy to move that into the manual and I'd really like to get some features. So there are a couple of features. I'm doing it against the SOG Debbie Installer at the moment and I was trying. So I've got a few nasty hacks that patch into the image because I was trying to use a stable base to build my stuff on rather than building on a moving platform. So if people want to have a look at that, I'm perfectly happy to take recipes from people and add that into there or have a central repository for recipes that we put into the main subversion. But I think it'd be really nice to be able to get it down so that you've only got one or two parameters on the boot line will make it into a preceder and say, I want that sort of a machine and get you there. So that was my vision and I'll hopefully try and get that into the main subversion fairly soon. There are a couple of features that I need to work on and I've been utterly useless at getting anything to boot because I haven't got a spare machine this week. So as soon as I get that sorted out, I'll work on that. Related to that, I was wondering what criteria we're going to use for back porting features into the SOG. So that was hands.com slash D minus I and it's got a sort of read me and a few how tos and it's a spelling mistake, so I imagine. Let me just say that I think it's great that Phil's here pimping his preceded files and I want to see more of that and I do think we should work to get it all merged, get the documentation and merge back in and so on. That's great. You asked about back porting stuff in the SOG. Our criteria right now are fairly strict but I think that we do have the potential to make another point release a SOG with a new version of DI and we just have to work it out with a stable release manager and all that. So it's still sort of up in the air at this point. So I think that I should probably stop now. Do we have time for one more? No, sorry? I think that's true. There is information about preceding on the wiki. There is some more there. Well, I don't, okay, since we don't have much more time I'd like to thank you all and remind you that we do have a meeting today at seven. So if you have more questions come there. Thank you.


We are not the ones desperately trying to hang on to dominion power and authority. That's been secured in Christ. It's the enemy who's working through the disobedience of wicked men and women who is trying to desperately cling to what little he has left. He's clamoring to hang on to whatever he can knowing that he has been defeated, decimated, put to shame publicly by the power of the cross and the resurrection of our Lord Jesus.


Hey everyone, Drew with Geowarm and I am back to talk to you about the L5210 and L7000 panels and how to figure out if they are the proper revision to use the LTE cellular communicator or whether or not you're going to need to do the MSD update, which I also will include a link to or a direct link to at the end of this video, so you can watch that as well. Alright, so the first thing that I want to get into here is I want to go ahead and talk about the L5200, the 5200 which is here. This panel can be updated to the L5210 Rev9 with the MSD update tool. That's the whole reason why I put this in this video. I just want you guys to know that have the 5200 that there is a solution for you. So the MSD update tool will also update this old 5200 and take it to a 520 Rev9. Once again, I'm going to go ahead and include a link to that video at the end of this video. So if you have the 5200, you can go ahead and fast forward to the end of this video and then click that link that I'm talking about that will bring you directly to the video you're going to need to watch. Now I'm going to go ahead and put this 5200 over to the side here. What we're going to be doing here first is we'll grab the 5200. What we're going to do is we're going to check for the panel revision. So you're going to hit security, you're going to hit more, then you're going to hit tools. You'll enter your installer code, which mine is the factory of 4112. Once you get into the programming, all you should have to do is hit test. Now at the very bottom, it should say Rev and then it'll have a colon and then the actual Rev. As you can see on this one, it is a Rev9 panel. So this 52110 is good to go. It's ready for the new LTE cellular communicator. So if you have the L52110, your portion of the video is done and you've determined at this point whether or not you have the proper revision. If you do not, once again, wait for the end of this video. That link will pop up so you can watch the video to get this updated. All right, I'm going to go ahead and move this over to the side as well now. Now we'll be working on the 7000 panel. The 7000 operates a little similar. So we'll just hit on the main screen, we'll hit security, then we'll go more, then we'll go tools. Then you'll enter 4112. Go ahead and hit test. At the bottom, it should tell you the revision. As you can see, my panel Rev is not high enough. It's a Rev7. So I would need to MSD update this using the tool in order to flash it into the Rev9, which is the proper firmware revision. And as I said, at the end of this video, you will see the video that will show you how to do this. So we've determined how to check for panel Rev on both the L52110 and the L7000. And you L5200 people out there, you know what you need to do as well with the MSD update tool to get it to 52110. If you guys have any questions or any comments or you need any help with anything at all, please leave a comment below or give us a call here at GeoWarm. Other than that, you guys take care and have a great day. Make sure to subscribe to our YouTube page and click the Show More tab underneath the video where you can view valuable links pertaining to this product, similar how-to videos and our low-cost, no-contract alarm monitoring services.


This tutorial is sponsored by environment textures comm high quality images for 3d artists and game developers Okay, so what we need to do now That the low poly is complete is UV map it No one likes UV mapping, but I think if we work together We can get through it So we're going to map different parts of this At a time, so let's just get into face mode And we'll select All these faces that go around like that How have I selected the bottom? I didn't want to do that. Okay. Let's just get the selection in this view Okay, so I just want those faces around the side first of all and then we're going to go to I'll open my UV editor so I can see what I'm working with Okay, and Can I just make that a little bit more visible? What does that do? Yeah, that'll help Okay So we're going to click on UV and we're going to do a cylindrical map because you know We're working on a cylinder that makes sense and we'll click on that and that actually looks Very clean. We don't need to do anything else to that that just worked So I'm just going to move that up out of the way for a minute. I'm pretty darn happy with that Next thing is to do some other bits and bobs so let's go back into this face mode and I want That ring there and I'm going to UV map this one with a planar projection on the y-axis and That's just that bit there. So let's move that over there And I want the one on the bottom as well and we'll just perform the same sort of projection on that Move that one up out of the way. So I know that they go together Okay, whilst I'm working on the top and bottom. I'll get this one here done Beautiful and that's going to be on the way axis as well So You can go there and then I need to do the bottom. So select all these faces It's got to be a quicker way of doing this and then we're going to go to UV planar boom There we go, right now Can you see that I've got these weird little things going on here and what they are? Are these bits here and these need to be cylindrically mapped as well? So I'm going to try and do these hello at the same time So let's do UV cylindrical and that looks okay, and I'm going to try Not quite. I'm just going to scale this up a little bit So it goes to the top and bottom of that as near as I can get it Just to try and match those up because that will make my life easier in Photoshop. Yeah, that looks okay right All I've got to do now is get all this to fit in the zero to one space so that I can Have this ready so I'm gonna click on this and see if it will just give me a favorable layout Sometimes it does sometimes it doesn't let's see what it goes me That's something I can work with I'm not happy with that. I think I'm gonna do it manually, so I might not get the most efficient layout doing this But I like to be in control Shell Okay, so I'll get those three shells and move them in And I want these to pretty much Be the width of my zero to one space. I think I need to go full screen for this I want to be able to see what I'm doing Okay, I'll move that down to the bottom Okay, next I'm gonna get these two and see I'm gonna have fun making these all fit I think what I'm gonna try and do To maximize the space is I'll bring these in around those Trying to give myself a little bit of space Like that. I think that looks okay And I've got one more of these up here. Try and get that kind of centered on there Bring that in after that. Yeah okay, so I'm pretty happy with that. I think I've given myself enough space So as UV maps go That's pretty tasty. Okay. What I can see though. I'm not particularly happy about is that I've got some that are Red and that means that they're not facing the right way The normals are in the wrong direction So we need to flip those normals and then we'll have a beautifully clean UV map Hopefully so select something red if you have anything red and just click on this and it will flip it around and Basically, just take it from being red to being blue Which is all we need there we go right that is Damn fine UV map it will probably be a little bit better if my sizes were a bit more consistent Which is really how he's supposed to work, but okay Right now that UV mapping is done and we're happy with that in the next step We're going to do the actual baking So we're going to bake the normal data from the high poly mesh onto the low poly mesh So I hope you will join me in the next step for that