Next part of this lecture is the new module that is earth slopes, embankments and dams. So, let us start this first basic principles and basic physics and basic analysis of earth slope stability. Overview we can see outlines one is what is earth slope stability overview and what are the different causes of mass movements and types of slope movements. Then in that types of slope movements, infinite slope stability analysis, then finite slope stability analysis, in case of finite slope stability analysis, what are the different basic methods we will discuss. Then particularly finite slopes method of slices, by means of method of slices what are the different methods available, by felinus method, bisapp methods and simplified bisapp methods and at the end we will try some few examples, solved examples, how it has been solved this slope stability analysis. Now, what is the first overview, what is the cause of mass movement, what is the reason that mass movement and slope failure generally occurs. If you look at here, if you look at here this is my original topography, this is the dotted lines are original topography of a region, then it has been proposed a slope or embankment has to be constructed. So, this embankment construction is this part of this embankment construction, if you look at here this is the embankment has to be this has to be embankment has to be constructed and this is a planned proposed construction. So, from this original topography what will happen, this part has been taken out, this part has been taken out and also this part has been taken out and this part also feeling this part is your feeling. So, by means of this if you look at here, once I have taken out once I have taken out this soil mass from here while constructing this embankment, then what will happen, there is a flow of the mass this direction has been made, also here it is a feeling of soil mass the flow of this mass movements. Now, what are the different how it is possible this mass movement, if you look at here there are different cases case one case two case three case four also ardent dam also it has been drawn, let us start with this case one. So, if you look at here this is your case one in this case what will happen, this there will be if I consider this is my slope and this is the embankment, this is your embankment in this embankment w is your gravitational force acting downward and this dashes line particularly this dashes line with this arrow it indicates tendency of soil mass moving towards moving away moving not away moving towards this embankment site. So, what are the different forces coming into picture the forces are because of your self weight that is your normal gravity forces acting vertically downward and this dotted or arrow lines is your tendency how this mass movement occur and you can consider also new forces taking into consideration of seismic seismic or earthquake forces this is a typical pseudo static cases. Then case two high ground water level if this ground water level suppose this initially the ground water level or ground water table is at this point and it has been raised to up to this embankment. So, high ground water level causes a seepage force this is your seepage force seepage force in the direction of potential slope movement how the in case one we saw that direction of potential slope movement this is my direction of potential slope movement how slope movement this is your direction of the potential slope movement. So, once there is a water table from here to here up to the ground surface or up to the embankment level what will happen this seepage force also acting in the direction of in the direction of your ground movement a direction of your earth mass movement. So, what will happen along with this earth mass movement there is also seepage force movement. So, seepage water along with this it will add seepage force will add additional movement or additional earth slope movement and along with this directions which has been marked. Now, case three if in this embankment if in this embankment may be in this slope particularly this slope if there is a layer there is a layer which is a very weaker which is very weaker in nature. That means very weak as compared to this if I consider this is layer one and this is layer two if I compare with this layer one and layer two layer two is weaker than your layer one what will happen because of layer two is weaker. So, it will settle once it will settle. So, this entire mass this entire mass soil movement will occur. So, another reason is susceptible layer or zone weakened from continuous continual exposure to ground water or chemical waste leech eggs. Then fourth case is temporary or permanent excavation for construction of a project. If you look at here if this is a existing slope this is already the slope is there existing slope or embankment. In this case it has been it has been proposed to construct here. That means some new load will come here construct a structure here at this surface of the embankment at the same time what will happen there is a temporary excavation here this is your temporary excavation has been made. Once this temporary excavation has been made what will happen the soil because here it is new load or new structure has to be constructed what will happen this entire mass will try to move up move towards your excavation this is another cause of your this is another cause of your slope failure. Then for particularly earth dam if you look at the cross section of earth dam if I make it this earth dam there are two cells one and two in between there is a core in between there is a core. So, what will happen because of water reservoir this cell it will this earth movement will be direction of towards your water reservoir. So, these are all common what is the reason that there is a mass movement or may be a slope stability or slope movement may occur these are the all few reasons which has been highlighted. Now types of slope movement first one we discussed what are the reasons what is the cause for your slope movements. Once you know that cause the second one what kind of slope movement may occur if you look at here there are one two three four different cases if you look at here case one is your rotational case. Rotational case means entire soil mass entire soil mass will rotate entire soil mass will rotate if you look at here in this diagram this entire soil mass will rotate this is called rotational slope movement. Then another case two is your translation translation if you look at here there is a weak stratum it has been marked and shown here. Then what will happen translation means one up another this will be movement from this. So, this is your translation movement then third one is your block or block and wedge. That means what will happen instead of moving in case one entire soil mass if you look at here there is a bigger weaker zone below the slope instead of moving entire soil mass like rotational what will happen it will move like a two wedge it will move like a two wedge. So, here to here this will be one wedge and here to here this will be other wedge that means two wedges are moving. So, that is why this is called block or wedge why it is called block it will act like a block and the movement will be like a separate this entire soil mass will be separated into as a two blocks or two wedges. So, the movement will be called or soil movement will be called block block and wedge movement. Then another one is your spread spread movement if you look at this this conditions also it has been mentioned this is a farm clay this side this this part is your farm clay that means this entire soil here is whatever mark in the white these are all your farm clay below this farm clay. There is another soil layer that is a soft clay with water bearing silt and sand layer that is a soft clay with water bearing silt and sand layer below this. Then below this there is a farm gravel clay farm clay gravel or farm gravel that means in between two farm soils in between two farm soils there is one soft soil or soft layer of soil is there that means this is your farm soil this is your farm soil in between two farm soils the third one is your soft soil layer is there. So, in this in this case what will happen this soil movement will be like a not rotational not block or wedge not like translational it will be like a spread. So, one by one it will be spread above the surface. So, if you look at here one will be one soil movement mass movement will be in this direction other will be in this direction other will be in this direction all of sudden one layer is moving downward. So, it will spread half hazard movement it will spread all over it will spread all over then last one is called flow type of slope movement last one is called flow if you look at here flow this is your source area this is your source of your soil mass source area and this is marked by your main track how the flow will occur then this is your deposition area that means if there is a hilly region there is a slopey ground slopey ground the source area from the top what will happen the slope will flow it will it will fail or it will the movement will be in terms of flow that means soil at this part it will flow in the main track and deposited at the bottom in this case it is called flow movement. If I classify into basically in broadly broadly what are the different types of slope movement once again number one is your rotational in rotational entire soil mass will movement movement that means entire soil mass will move that means as if this will be a one soil mass it will move then second case it is a translation the movement will be like in a translation then third is your block and wedge that means each soil mass will not move like a independent one soil mass that rather it will move like a block one block other block so one is moving like this other is moving like this so this is called block movement then fourth one is your spread movement in in this case spread movement if there are two firm layers in between one soft layer is there what will happen then the soil will spread spread means there will be a vertical movement lateral movement all over it will be a spread then last one is your flow flow means if in case of hilly region if there is a there is a slopey ground what will happen entire soil mass at the top will flow and deposited at the bottom this is called flow movement now there are different case studies if you look at there are different case studies now I come back to here ground means if you look at this there are different case studies has been taken one is your case one it is 1964 alaska earthquake if you look at this alaska earthquake how the soil movement will be there from the top and it has been deposited because of earthquake enter mass of the soil mass in the slope has been movement means if you look at here this is one block this is another block these are all separated out the soil will be separated out then second one is your if you look at here 1995 kobe earthquake this is a case of kobe earthquake this building hang over the head scrap of a landslide in decomposed bed rock that was triggered by the 1995 kobe earthquake if you look at here kobe earthquake what will happen this building just simply hang below this entire soil mass entire soil mass it has movement soil movement is there so the building is simply hang now come back to second in third example in 1970 an earthquake induced rock and snow avalanche on waskram peru it is particularly a peru earthquake if you look at here peru earthquake how this flow from here to here how it has been movement of this soil mass movement will be there from here to here how this flow occur and it has been deposited this soil mass here this is your third example in 1970 peru earthquake now typical one cross section earth dam has been shown in 1971 earthquake if you look at here before earthquake 1971 this is an earth dam look at here this is your earth dam this is your maximum water level and this is your dam top of the dam and this is your earth dam once this earthquake has happened the soil mass if you look at here it has been marked by dotted the soil mass entire soil mass has been moved the movement of the soil mass has been occurred or you can say that this embankment failure occurred because of earthquake because the soil movement from here to here it move towards your downstream side means particularly towards your water level or reservoir side I have shown earlier also if you look at here this diagram I have shown in this case this particularly if you look at here there is a flow and one case I have shown here this case typical case I have shown if this is an earth dam and there is a reservoir if there is some earthquake some forces are coming so this part of the soil will movement move towards your reservoir that means this soil will move towards your reservoir so this is a earthquake in 1971 occurred in sun Fernando and magnitude comes about 6.7 6.7 and total from 48 death occurred in injuries 2000 and damage is about US dollar 511 million dollar has been damage has been marked and crest if if this is my dam crest this is the dam crest drop from 142 feet to 112 feet this crest has been drop from 142 feet to 11 feet another one is your 1994 17 January earthquake this magnitude is 6.7 6.7 if you look at here limit of landslides triggered by the north ridge earthquake and area of greatest landslide concentration shaded particularly greatest landslide concentration if you look at here how the landslide has been occurred entire soil mass has been eroded eroded means it has been the because of your slope failure entire soil mass has been flow to your downstream side and this has been shown in graphically means particularly pictorial point of view top view so this is your entire area how this landslide has been occurred from here to here this landslide failure rated correlated with shaking severity then slope stiffness then strength and engineering properties of geologic materials then is your water saturation then existing landslides areas if you look at here first one is your number one number one is coming out to be somewhere else 1 2 3 4 5 6 this is your 5 10 somewhere else number one here this is your shaking severity two is your slope stiffness slope stiffness then third is your strength and engineering properties of geologic materials then fifth is your existing landslide area if you look at here this is your fifth is your existing landslide area this is your number fifth this part is your number fifth this is your number fifth that means in this area this is your area of landslides landslides means entire soil movement entire soil or entire soil movement or slope failure there are two kind of slopes one is your infinite slope so the slope is in infinite nature then another is your finite slope now if you come for this infinite slope analysis before I go to the infinite slope analysis let me come to the finite cases in case of finite what are the different types of slope failure occurs finite means it is a distinguish particularly it is a finite shape infinite means it is a long infinitely long slopes so in this case particularly there are three category one is your slope failure another is your toe failure other is your base failure if you look at here this is a slope toe failure typical for soil possessing internal friction now this is your slope failure now that means the failure will be generated from this side and it will be somewhere else along the slope this is my slope this is my slope say this slope may be one is two one or one is two two it depending upon this what generally one is two one two one is two two or one is two three has been the slope has been provided so why this is called slope failure the failure surface the failure surface extend here from the embankment at it generate and it ends at the point of slope that is why it is called slope failure same cases it is also extend here and ends at the point of before along the along the slope then third one is your if this is my toe second one is your this is my toe if this is my toe if you look at here both this the case one and case two these are called slope failures because the failure starts from this embankment at the top and it continue and fail along the slope first two example is your slope failure because this failure starts from the embankment top and the failure it will it will terminate somewhere else along the slope here it is if I if I draw a draw embankment like this if this is my slope one is two two or one is two one so these failures these failures I can say failure surface one two three as slope failure because the failure surface ends at the point of anywhere else along the slope that is why it is called slope failure the moment I say that this is a toe failure that means particularly in case of finite slope that means the failure surface starts from some from at the top at and it propagate at and it ends just at the point of toe if this is my point of toe and this is my the top of the top of the embankment top of the embankment so here it starts the failure from the top at it ends at the point of toe this is called toe failure that means there are two one is your slope failure other is your toe failure third one is your base failure base failure generally occurs if there is a kind of if you look at here this is a clay layer this this this is your embankment constructed and this is your particularly clay soil it is written here then layer or zone of hard earth it is a harder stratum is there then what will happen then the base failure means the entire failure means this failure surface will start from the embankment it will progress progress and it will pass through below the toe it will pass through below the toe if this is my toe if this is the toe so it will pass through below the toe so that is why this is called this is called base failure now shape of this rotational slides shape of the rotational slides so if you look at this rotational as I said earlier now come back to this kind of second slides as I have explained earlier rotational slides rotational failure means types of slope movement rotational movement translational movement block and wedge movement then your spread movement then third is your flow if you come back to your rotational movement in this rotational movement what is what should be a shape how this rotational movement how it looks like one is your spoon shaped one is your spoon shaped as the spoon is a kind of this so this is a kind of a spoon shape so the failure is kind of a spoon shape failure so that is why it is called spoon shaped rotational slides other is cylindrical shape that means it will go in this so that it will take a cylindrical shape that is why it is called a cylindrical shaped rotational slides now if you look at this finite and infinite slopes I am discussing about right now this what are the equations what are the driving forces what are the different forces and how this finite and infinite slope particularly analysis has been done now go back to classifications so there are two types of slope failure one is your infinite in nature second is your finite slope in case of finite slope as we have discussed in case of finite slopes there are three kinds of slope failure one is your slope failure other is your toe failure third is your base failure now if you come back infinite and finite now in this case we have to identify what are the different forces acting what is your resisting forces what is your driving forces then we can find it out this factor of safety now if you look at this a typical figure shallow disrupted slide in very weakly cemented sediment in the Santa mountains slide is about one kilometer wide at the head the slide is if you look at this it is a mound and this slide has been shown this is this slide is about one kilometer wide can you imagine this slope this mass movement one kilometer wide this entire soil mass slides this width is about one kilometer one kilometer long stretch so this width is about one kilometer now if I look at this a typical this is a photographic view now if I analyze this if you look at here this is my original ground surface this is the original ground surface this is the original ground surface and this is your crown this part is called crown now now if you look at here this is the original ground surface and this is your crown now in this case if you look at here displacement material it starts from here to here now this is a main scrap main how it is scrapped so this part is generally main scrap then head then there are also at the same time what will happen at the same time what will happen there are cracks developed there are cracks developed over the period over the side by side so here if you look at here this cracks may be vertical or may be transverse so this crack is here it is shown this is a transverse crack this is a transverse crack transverse crack then there are two scrap scrap means how it move one is your main scrap main scrap will be at the top main scrap then another one is your minor scrap once it movement what will happen this slope is very stiff at the top then it becomes slightly stabilized so there will be a kind of there will be a kind of minor scrap now this is a main body if you look at here how the slope failure if I take it how the slope failure this is your main body this part is your main body it has been shown here main body now in this main point body this is has been marked tow tow means if I say this is heel this is your tow of the slope so this has been scrapped about one kilometer what has been said wide and this how the surface of rapture occur this is a surface of rapture occur this is a kind of rotational rotational shape then this part is your surface of separation this once there are again cracks develops so this shows how this oil movement starts particularly in case of slopes slopes and what are the major parts how how this rapture surface develops now next step we are going to go we are going to derive this basic equations for infinite as well as finite slopes now if you come back to infinite slope now I take a take a slope of infinite length and take a very small elementary part small elementary part of the soil in case of infinite slope now what are the component will have to see what is your driving forces what is your resisting forces now one is your one is your self weight of this self weight if I take a very small element of the soil in the infinite slope the slope angle is beta now this is your self weight w is equal to gamma into b into z b is equal to width z is equal to depth this depth is your z but and this is your weight self weight and what are the forces acting both the sides if you look at here one is your one is your infinite extend these are lateral forces e l e r if I take is your left hand side and right hand side this is your left hand side force this is your right hand side force as well as t is your particularly t is your frictional force t is your frictional force so it will be one is your vertical down other is your vertical up now sear force on the plane so because this is a infinite slope sear force on the plane s is equal to this and this is your normal force now if I take as a this length is called as a delta l delta l width is b this length is delta l so this delta l is your b by cos beta beta so this is your b sec beta we will discuss all these things next class complete derivation of your infinite as well as finite slope I can stop it here.


We saw five minutes to launch here, but you can tell I'm kind of like Ready to kind of get going so we can do a little preliminary stuff. I'm curious Who here's like doing PHP unit stuff on a like a more or less regular part of right? certain amount how about be hat certain amount of be hat going on and like Selenium or Night watch Any any other testing frameworks that I have mentioned that people are using Cyprus and what is Cyprus test? and So full stack across yeah, and Any like link checkers Load load load testing any of some of that stuff. Yeah going out This isn't this isn't specifically a talk about testing and we could you know that would be a great talk to have to but But you can't really separate Delivery practices from testing they're kind of bundled together and So mostly we'll be talking around the edges of these these testing frameworks And so how many people here are on? One of these like hosted Services that bundles delivery like pantheon and platform that sh and I think you mentioned azure is has a bundled pipeline They have they have pipelines and and somebody also mentioned git lab is I'm not familiar But git lab also has like bundled pipeline so increasingly you don't have to build this stuff Right the way we did a few years ago Because it's all right there you can buy it. We're still up here, right? So we here's another I guess this is the little preview section is that This slide deck is done in remark J s Instead of using keynote. It's the first time I've done a remark J. S slide deck and it's pretty cool I like it right so it's and so it's sort of like a Like a meta version of continuous delivery because it's like continuous delivery for the slide deck Hey, because they because the and I can I we have a minute so I can show you that the Right Yeah, I don't know I don't know if I could be my screen management. It doesn't seem to show up I Can't really so but in any case the whole slide deck is just It's just marked down, you know, it's marked down in CSS and And it's just all pushed out to a website. It hangs off. It hangs off of a website And so and I could do the presentation from live this is my my Blog site Michael godeck.com and you can actually follow it on your on a phone or a laptop Go to Michael good at Michael godeck.com talks and then there's this triple con talk here And then down at the bottom. There's a link to slides and it's the same presentation that we're doing here Right. I'm just doing it from local host, right? So it's the same. It's actually the same Kind of thing, but I suppose it's more reliable to do it from local And so it's remarked js with Uses at Iran deck is a CSS library and Discard days is another CSS library that does the top typography And so what I'll do is I'll make a I'll make an additional slide that describes the technology that goes into the slide deck And I'll add it to the deck and I'll and I'll push it to the to the deck afterwards So we have that all out there So looks like we're on time so We're gonna start right and So we're gonna start with this question right which maybe I already know the answer to but you know Have you ever pushed code to production only to wish that you had known something first right something that you only learned After you push a few of you have been in that situation How many post-mortems have you been into when it turned out that the cause of failure could have really easily have been avoided If you'd only known something first And so really how would you like to be able to go back in time if you go to fix these things? So that like they're fixed before anybody sees that Well, you wouldn't really be the first person, right? This is so He's going back all the way back in the 18th century. There was this guy Irish writer named Samuel Madden and he published the first time travel story that I've ever heard of right he was 17 28 he was thinking about the stuff he wrote this book called Memoise of the 20th century and he didn't really have the technology Angle to work with and so he had a guardian angel like go into the future and his guardian angel goes to 1998 would have placed him in the Clinton administration, right and he finds these diplomatic letters I guess there were Madeline Albright's and he brings them back to 1728 to correct some, you know mistakes that people were about to make right, you know the story so That was pretty cool going back and that was a century before like Charles Dickens did Christmas Carol and what is it yeah Christmas Carol and then Washington Irving did Rip Van Winkle and then you know now we're in like we got dr. Who back to the future Black Mirror everything beyond well The news here really is that the company I work for which I can't tell you the name of it for legal reasons Has got a product called time orchestration Right, it's gonna really beat all of these CD tools because you're gonna be able to orchestrate time to go back and fix the Things before they actually happen and we've got a few Approval issues with the FDA about this product, but we're working on it And I've seen it with my own eyes other people in this room have seen it as well, although they might not admit to it But while we're working out the kinks about how this time travel stuff works then that you know the next best thing to time travel is Getting to know something Sooner and that's what we're gonna talk about here for the next half an hour is This poor man's version of time travel this continuous delivery So I'm Michael Godek I'm from little town in Texas just east of San Antonio and I work for this architecture and engineering group in a global pharma organization Where we really have a very big appetite to know a lot of things sooner Because there's a lot of stuff that we really wish we had no look just a little bit sooner So we're working we're working really hard on on these kinds of Problems we're putting a lot of resources into it And so I wanted to address at least this one part that you might wonder You know if the problems of like a global giant really how relevant that they could be with you I just spoke with a lot of you and a lot of you were really just getting started on a CD path And we've got a lot of resources going into it. We've got some amazing talent that works on it full-time but The playing field is really a lot more level than you think right because in a large organization With a lot of resources We have a lot of things that are going against us that are just the nature of being in a large organization That being in a small organization. You don't have those same problems. You can make decisions for yourself You can solve your own problems. And so we all face different problems but the question of getting faster feedback of Knowing things sooner right this is the common ground that I want to Focus on here and in software practice. We call that continuous delivery right as a practice and so just to provide kind of a definition of it is that Because there's a lot of confusion. We thought there's a lot of discussion around DevOps. There's continuous delivery Pipeline is a set of tools and protocols that use to control the quality of changes to production And so even if all you have is a checklist that's written down on the back of a napkin Then you've got to start right? That's your protocol for for delivering right and so if you can If you have some protocols without tooling that could actually be more valuable than having a lot of tooling Without really clear protocols Right so start start with just understanding what it is that you're trying to get done and get those protocols done Now I've done us sessions on continuous delivery at Drupal con Austin in Amsterdam 2014 Drupal South Melbourne in 2015 and there's a QR code to that YouTube video there And things have changed a lot in those last five years You can buy a lot of the things that we had to build five years ago And so this talk isn't really about like the state of the art of build automation but really just to try to get your thinking about CD to Not be so much around automation but thinking of it in terms of The way you go about improving your business practice, which is really what it is. We're trying to get at with CD And then we talk about Continuous delivery is agile successor that came off of a talk by at Andrew bin stock of bite magazine a Number of years back and it implies that agile has become the standard of practice in that like in responsible hands It's effective and I believe that so I'm taking that as a given for this group And we won't talk about it much and leaving aside late the problem of fake agile frameworks If we're just looking at the agile manifesto, right you can print it out on a single piece of paper You don't need a book or a PhD Embracing change coding and short sprints an emphasis on automated testing You know all those things have really helped us all improve in quality and productivity And a central problem that agile has been very effective at is adapting to changing customer requirements And so when we have a realistic grasp of agile then that's getting to be more and more something that we do well but the problem of Maintaining quality and delivery is still very complex and elusive problem Even for people that have put a lot of resources into it And for all of the enthusiasm around DevOps the delivery practices are still very much in the early days Right agile is pretty mature, but the delivery practices I think that we have years of work to do to get there and so I'd like to take you back in time a bit right to look at this pre-internet period And look at lean practice before the era of the internet especially at the Toyota production system And so a few years ago. I went to Japan I went to Kyoto like everybody does and I visited shrines, but I also visited the Toyota Museum in Nagoya Which is like a shrine and lean practice itself and the curators They went beyond making mere showcase to inventions that you might Expect, but they tell a story of innovation as a process So they tell the story to take you back to the 19th century Japan where these manually operated wooden Shuttle cock looms were the cornerstone of the economy and there was this teenager Sakashi Toyota who was really fascinated by how these things work He thought about it a lot and put his mind to it And he developed a model that you could operate with one hand which was a big improvement to productivity That was 1890 he got his patent for that and in the following years he iterated relentlessly and he came a number of a number of great designs including the first Automatic shuttle can't change loom in 1903 so when the spool runs out you didn't need any hands It would automatically shift one on and so that was a long and prodigious series of advancements that his competitors sought to copy and Toyota famously said quote The thieves may be was what happened was that people were stealing his designs and his colleagues Asked him what they were supposed to do about these patent violations And he'd said the thieves may be able to follow the design plans and produce a loom But we are modifying and improving our looms every day They don't have the expertise gained from the failures. It took to produce the original. We do not need to be concerned We need only continue as always making our improvements Right, so Toyota's insight into the value of learning from failure and Persistence in making improvements, right? That's the foundation of lean practice today So that stretches all the way back to 120 years ago 130 years ago and So the story goes on this the in kind of an exercise of recursive innovation because these people this family just continued to innovate and in in the 1920s They sold out of their business. They sold all the patents to their to their lip to the loom Technology that they developed they created a new company named Toyota with it with a T And the family name was with a D and they launched into the automotive industry that which was already dominated by American and European manufacturers and they came into it with decades of metal casting experience they thought it was really gonna they were gonna excel in this particular area, but the defect rate of the early engine box was just horrendous and there wasn't any guarantee of success and of course We know that you know, they did actually Pull out of that and the process that they pioneered at Toyota was Eventually championed in the West the way we know about it through was through the work of W. Edward Deming Who was assigned to work with Toyota in the post-war to period in the reconstruction period? He was a statistician a management consultant and just an all-around really great guy and Deming was a catalyst for the science of productivity and he merged this culture this culture of Toyota that already exists with his his own American culture that's identified with Benjamin Franklin of innovation and an invention and with his own really unique contribution of applied statistical analysis that Deming brought to the thing and so these early Japanese auto imports in the US were cheap and low quality But the fusion of Deming and Toyota and other contributors produced what became to be known as the Toyota production system and so Deming's you know through his course of his life at the end of his life his notoriety was limited to like management circles but when Ronald Reagan awarded him the National Medal of Technology and this generated publicity It sparked a series of articles and interviews With Deming he was 87 years old then that was 1987. He was born in 1900 and His unpretentious optimism is vitality resonated with people working beyond spheres of manufacturing where he was known including software thought leaders at the time His books were the cornerstone of the 1970 manufacturing evolution of just-in-time delivery and is a 1982 book Quality productivity and competitive position provides really a perspective of lean theory about the time when it intersected with us software development and So this lean lean manufacturing conception of just-in-time delivery was really when it came to America It was often misinterpreted by the American bean counters as merely a technique to reduce inventory carrying costs but software thought leaders recognized the essential value of establishing a systematic way of quickly capturing and correcting defects and They restated this quality assurance principle as a new standard of practice called continuous integration And that was popularized in 1999 By Kent Beck's book extreme programming explained Right came directly out of this So we'll take let's take a step back and we'll look at how the The assembly line in the Toyota production system informed the software delivery practices because the first time to run this Toyota production system in the US was the Toyota GM joint venture at the new me plant in Fremont, California and That was in 1984 and this same plant is the Tesla Motors factory today And so it was the GM plant it was this new me joint that GM Toyota joint venture and now it's Tesla So it's an awesome building has a lot of stories to tell that building So this GM plant in the 70s had the highest defect rate of any automotive plant in the 19 in the 1970s Which is saying something right and they were producing the Chevy celebrity in the old cutless era Until finally they shut the plant down because the quality was just so bad right And there was a UAW worker from that plant who had said quote I can't remember any time in my working life where anybody asked for idea my idea is to solve the problem There's nobody to pull you out at General Motors, so you're just gonna let something go hundreds of misassembled cars Never stopped the line was the motto at GM right just keep pushing things into production And it may sound odd, but it's like a lot of some organizations I've been into pushing code into production basically has that kind of feel to it like push to production Right don't stop So when taking over the Fremont plant the Toyota insisted on retaining the same union workforce that GM blamed for the quality problems Right GM shuttered the plant because of these terrible workers, right and the Toyota's guy the GM guys warned the Toyota team They said okay, we understand you're from Japan you're naive, right? You just don't understand really how bad Americans can be and so Toyota took these work these United Auto workers from the failed new me plants in Nagoya And they showed them how the plan is run and Toyota production system and these UAW workers were shocked to find that under Toyota They would have the power to like Shut down the line over a quality issue right they had the authority as an individual anybody on the plant for it had the authority so in the Toyota production system you have these Pull cords over every workstation you pull once and it turns on an amber light manager comes over immediately to inspect Whatever the issue is and if they couldn't resolve it immediately Second pole shuts down the whole line that is the foundation of what CI is in our system Right where we push code in to some process that we run a bunch of tests. That's the equivalent of the end-on cord From from the Toyota production system So this thing about finding and fixing defects in real time It seems like common sense, but there was a time when it was like not really the pattern and really made radical improvements to car Manufacturing and it brought brought radical transformation to how we build and deliver software And so identifying defects sooner is going to save a lot of time and money. That's pretty obvious, right? And it should be enough to justify investing in DevOps, but when you consider that Every break fix that you're looking at is an opportunity to discover root cause and To take action to try to prevent the same kind of defect to occur in the future That's really what you're after. That's even a bigger value than the cost savings of just finding and fixing things before they get to production And so if you think about that quote from Toyota when he said They don't have the expertise gained from failures. It took to produce the original Right, it's like he was looking at the whole thing of like the learning process of Examining defects right and Toyota plant when they Went from having the end-on cord pulled a thousand times a day to seven hundred times a day Was that do you think that was a positive or negative metric? Right when it happened the Toyota management brought the team in and they said what's wrong, right? The reduction in the number of times that the end-on cord was pulled was not taken as a positive thing Right. Nobody was getting criticized for stopping the line So learning from our defects. That's what's really allows us to improve our process our commitment to improving the process Is what sets us apart from our competitors? so if you look at it from the perspective of Lean theory right you can spend, you know three years getting a six sigma certification or you can take Three points from my talk and consider the job done Okay, and that is that one Lean focuses on identifying what creates value from the perspective of the customer so that's the first thing You know look at it from the perspective of the customer. What is it that creates value for them to? understand the process That creates that value and delivers that value and so that's CD practice Right step three finally never give up on making that process work better So if you do those three things you can skip the six sigma certification and just call yourself a lean practitioner Right those are the those are all the principles you really need in order to understand how to Make the most out of a CD practice at your CD practice as you build it out and so then you have this issue of like Deming if you read Deming It's like he constantly comes back to this question of fostering creativity Right that if you really want to understand what's wrong with your organization? What's holding you back then you need people to feel free to think and in an unrestrained way To not never have any fear of calling out defects or being caught for Being the source of a defect right defects in the internet a production system. It's always an opportunity to move forward Right so if you have a culture where it's like people are afraid of what's going to happen if they're the cause of a break then That's going to be a problem How many people are familiar with the Netflix Chaos Monkey? Right, so yeah, it's pretty broad. So Chaos Monkey. They run this process in their in their build pipeline That just goes and shuts down services and closes ports at random, right? It tears out your certificates and stuff and your and so it's like a pushing software into the build This is like the regular build process, right? It's like a game and so if you don't have a sense of humor then you there's no way you're gonna survive in Netflix, right? That takes there's a there's a certain attitude about this stuff It's like it should be there should be something that's like fine about this And if if the build pipeline is like soul crushing then you want to take a step back and think about it so the build pipeline is where you formalize the ways that your team responds to errors and You know creates a context where you're not just fixing things but learning and improving the delivery practice in the process And so it takes us back the reason why we're all doing this right the first principle of the agile manifesto is You know our highest priority is to satisfy the customer through early and continuous delivery of valuable software Right, that's a principle. That's the practice of CD The kind of the canonical reference to that is this book by Jess Humble and David Fairley Continuous delivery and so there's a lot we could talk great another 45 minutes into that But there's they talked specifically about Configuration management, which is really hard under Drupal and so we have a tremendous amount of work to do in that Configuration is going to be one of the biggest hurdles to running a good CD pipeline Feature toggles there's discussion of that and other things so It's a great read all the way through highly recommended So to try to kind of wrap things up. I want to give you three metrics kind of high-level metrics that you can look at to Tell how well your little poor man's time machine is running and they are One is to ask yourself the question Are you really testing integration?  Those three questions will take you a long way down the road. So the first one Are you testing integration? So CI is the first step of CD and this work, you know codes built every time there's a commit and the Value of CI is faster feedback and so if you have pipelines where the dev instance is unattended in a broken state for any period of time then You know you may have some build automation, but you know What are you doing? I mean, what's the point of that you should have a rule that of the amount of minutes That a put that an instance should stay in a in a broken state and whoever pushes a commit Should attend to see what the result of that is and if they can't fix it if they break the build if they can't fix it In ten minutes or whatever you decide then they should roll it back, right fix or roll back never leave broken So just humble sarcastically remarked there's two words in CI continuous and integration All right continuous means more often than you think and Integration means trunk right the branch of code that you're going to deliver to production So those are two kind of really big challenges in that way If you're bill if you're working on long-term feature branches, which I think is pretty common in this community Then you're probably not doing like many many commits through the course of the day You're probably not using feature toggles And those are those are practices that you aspirational practices that you can look forward to and if you're You're testing before you merge then is that really testing integration because the merge is integration That's what merge means is integration, right? So what we're looking for in in CI or small frequent pushes Where we're test where we have fast-running tests and so Martin Fowler put it this way he said quote one of the challenges of an automated build and test environment is you want your build to be Fast so that you can get fast feedback, but comprehensive takes tests take a long time to run so a Deployment pipeline is a way to deal with this by breaking your build into stages each stage provides increasing confidence Usually at the cost of extra extra time Early stages can find most problem but problems by yielding a faster feedback while stages Later stages provide slower more thorough probing. So deployment pipelines are a central part of continuous delivery That's the Martin Fowler quote. So think about that phrase Each stage provides increasing confidence Right think of the stages of a pipeline is being bolted together What are the bolts what bolts these things together, right? They're they're the the the protocols that you put in place the quality assurance contracts that you say when something's done with dev Then these things are guaranteed We're going to move it on to the next stage and when it's done with that next stage We're going to extend our guarantee on what it is that's tested and when it moves to the next stage Then our our guarantee is broader than that So if you're testing a feature branch on an on-demand environment can be helpful but if the code path from local to production is not consistently running across the same stages with the same guarantee protocols every time then You're vulnerable to the kind of inconsistencies that we're trying to resolve in this thing and Then finally, you know, who's supposed to be involved in the production release, right? So you're the ideal that we're shooting for is that you can have you can give a non-technical Stakeholder a green button and a red button and you show them the stuff that's on stage ready for delivery And if they like it they can push green and they shouldn't need any technical assistance for that to be delivered and you shouldn't really even need people on call for delivery and If there's anything that goes wrong with it, then they should be able to press the red button and it rolls it back and they also shouldn't need People on call to do that. And so that's one of the things if like if you're starting to build delivery pipeline Really one of the first things that you should do is to write rollback protocol Very first not don't wait, right? Write your rollback protocol at the very beginning because it's the beginning of this practice all the way through and If you're if you're a small shop got limited resources You're even working solo You can still embrace all of these goals, right? Because if your pipeline is just a few bash scripts with a few well-considered tests Guarding each stage then that can be a more proper Pipeline then some overblown DevOps operation with Kubernetes running and stuff that never seems to get like Every all their ducks like lined up in a row before things go to production, right? So the important thing about having a CD pipeline is Knowing what your protocols are and applying those protocols as you move stuff across to Production and the automation assists in all of that, but your automation is not your delivery pipeline Right your protocols are more important part of it and you don't need a budget in order to set your protocols You can do that without budget, right? so I Don't know if they're I don't know exactly. We're on time. Hopefully I have time for a few questions Thanks for coming out certainly come to the code contribution sprints sprints on Friday The slides are there and that QR code goes to the slides and again I'll update the slides for the Technology that goes into the slide deck and there's a bunch of other posts on my site that are kind of related to this whole topic area So thank you in any questions anybody Yes, no, maybe so thank you


Good afternoon everyone. So Henry Guru is a guy with many hats in the biennial and I didn't expect it, but he will talk about new hats. He's a good young contributor of hats, so please welcome Henry Guru. No, but he is a guy with many hats in the biennial. Our chief weapons are developing weapons. The development of science is developing weapons. There are two weapons. The development of science and the development of science and all the other kinds. Three weapons are developing weapons. They've been maintained at the count and by the quote. Four most weapons. Amongst our weaponry are such elements as that the development of the American people. Artificial devotion to the social contract. Nobody expects that it contributes. Amongst our weaponry are such diverse elements elements as the integral step in maintenance, and it accounts back the forces and made it misrepresent of that. That's more possible. We clearly need another fact to make sense of all this. So let's make a new fact. I would like to create the fact of Debian. So that we can say, nobody expects Debian. Our chief weapon are Debian parameters full stop. A hat for everyone that contributes to Debian. Now the details are here. This is the file with notes. Is it readable at the end? No, you have much better eyesight than that. No, sorry, I open it in a different way. This is the text file with notes about what I plan to do. I would like to go through it with you and then edit it together with you. And at the end of this 45 minutes, I have a proposal that I'll try to implement doing that course and fail unless somebody helps me, probably. But anyway, we see how much of this we want to do, how much of it can be implemented with that course, and at the end of that course I'll take another talk about what we changed in Debian. So this is probably good. Okay, so the problem we want to solve, the problem I want to solve, you probably also want to solve once you realize your problem, is war wrapping. Now that we solved war wrapping, okay, so in Debian we have lots of contributions that we do not thank people for. In the sense that we do not acknowledge that people that did translations worked, we don't acknowledge it somewhere, people who did translations, people who record the products. There's lots of contributions outside of Debian, but if we look around the package production system, Debian developer package overview, it's all package based, because that's where we come from, and so we track uploads there is in the track, and we acknowledge uploads mostly. But there's so much more that we do not acknowledge at the moment. Also there is a need, there is, over the time we created so many ways of contributing to Debian, that outside being a Debian developer, so the head of the Italian translations in Debian is not a Debian developer, nobody know who she is. Well, I know who she is, Francesca told me, and at least two Debian developers that know who she is. I have no idea who's the head of the Vietnamese translation. Raise your hand if you know who is the head of the Vietnamese translation in Debian. I assume, yeah, we all know who the French one is, but I need a way to credit people properly. Debian is so much more than uploads and she's a wine boss. So there's this idea of creating a hot of Debian contributor, which is the ultimate duocracy hot. There is no bureaucracy involved. If you contribute to Debian, you are a Debian contributor. Automatically, there is no new Debian contributor process.  That's it. When you are a Debian contributor, you get such diverse privileges as having your name on a list of Debian contributors. And possibly, if you are not a Debian contributor anymore, then your name will be on a list of Debian contributors in 2012. And if we want to be really fancy when you click on a name on a list, you get a page about that person that lists what they've done. And that's about it. That's all I had in mind. You report a bug, you become a Debian contributor. Then maybe everything you do for Debian is reporting a bug on the 11th of August, 2013, then you will be a Debian contributor from the 11th of August, 2013 to the 11th of August, 2013. At least you have knowledge, as I didn't have that in. Mostly I've said all this. In order to do this, there needs to be a way of collecting this information. There are data sources we can easily tap into, such as package upload, but we can see mailing-based traffic easily. We can get backtracking system activity, hopefully easily. We can hook into commit logs of Arliov version control systems. This system, whenever at any point of its usage will be unfair, because there will always be some bit of Debian that isn't yet providing data for the list. However, the point is that by having such a system in place, we create a proper way of acknowledging people's work, and we give motivations for teams to contribute contribution information to the list. Questions so far? Sorry, I didn't understand the second point. Wouldn't this raise privacy concerns? Good question. If we collect this data automatically, would there be privacy concerns? Yes, possibly. To be discussed, all the information presented here is already public. There is a public record of package uploads, mailing lists are publicly alive, but the BTS is fully in the open, commit logs on Arliov are public. I would only mind or get data from sources that are either public or that people agree to disclose. However, it's the usual issue of the information is public, but not presented in that way, for example, when I collected information from Debian change logs to see the history of people's contribution in the process, I did not make it that information publicly available because it's a bit, I would want to have a discussion whether we want to present that information collated in such a way. So yes, that is an issue. My general idea would be that once the system knows public, there should be a way for people to opt out of having information about that display. Most of the privacy scenarios, so generally people, I don't understand it generally, the default would be that somebody likes their work to be credited. However, there may be people that would have issues if some of their work is credited. Most things revolve around job hunting, like recruiters looking at the internet, and you either want to be found, or if you don't want to be found, you already have a problem when contributing to Debian. I need to be careful about contributing with different names or something. But yes, my assumption is that it's not a big privacy issue to get this started as long as we give people an opportunity to opt out. Does it seem reasonable? Maybe by default it's not opt in. I would be fine with opt in. I wonder how many people would know that they can opt in and how to opt in. At the moment, the current Debian infrastructure is not even opt out. You can't say please don't show the messages I sent to them in making lists. I would see it surprising that such a thing would be opt in, because everything's already out by default. On the other hand, I could be convinced about making it opt in. It seems to be, at the moment, something that would impact the start of such a project. So, before somebody gets a useful list, I would need to go and tell a thousand people opt in the system so that that list can get populated. Yes? I think you should also look at legal aspects. You are collecting personal information. I don't know the law by heart, but as far as I understand it, it would be illegal in half of all European countries. Then let it be illegal. No. Currently, you are not collecting this information. You have it at different pieces and at different places where it is necessary. You have it in a bug report because the person wrote it there and it's that... The buggy tracking system would be illegal. No. This would be illegal. You don't collect information there when you collect it for the person. There you have it for specific purpose and this is not illegal, but if you collect it and collect all information for a specific person or for all persons and collect it, this could possibly be illegal, as far as I understand it. I would like... You said that you are not sure. I would like to talk with somebody who is sure because we already have things that would potentially be illegal in that new, like the buggy tracking system goes beyond listing at some of the uploaders because it collects information about everything visible about the person, bugs and so on. Would it be... Sorry, we said it was useful to construct this kind of thing by having some reasonable set of people listed as contributors. You could start by assuming that people who have said I would like to be a Debian developer or I would like to be a Debian member have implicitly given their authorization to be listed as Debian contributors. It's a subset of that. You might have to... We might have to run that by a lawyer but it seems a bit more reasonable. I was just going to say I think the legal thing should probably be separated off because in practical terms if you are only wired from a legal point of view you just need to get someone who is in Debian in the US to do this on the US server because the US doesn't basically have these kinds of orders. The relevant question is not about the legal thing is the kind of retiring but about what we want to do and what we think is fair and so on. Well I keep thinking we're doing something much more lightweight than launchpad is doing. Another way to enable this would be to do this automatically without publishing the data but with afterwards sending about once a year or even possibly less a mail to every contributor if he wants to be listed. So we have an opt-in instead of an opt-out. If we do it seldomly enough it would not even be so stressing people. Yeah that makes sense. You don't need to wait a year you can do it the first time you detect someone new someone who starts contributing you can say hello if you did something in Debian we would like to credit you. Wait for a month after the first contribution if you get more then yeah say you want to be thanked. Makes sense. Even without waiting we touch my tongue for the next channel. You know the stats about which companies contribute to the new channel. It's like that they check for new commits and they just send an email to us for affiliation. There are other systems that calculate karma. Those are illegal because then they produce information that could be used to hack people from a job point of view. Would that credit only be for persons also for organizations and companies? Interested about entities directly contributing to that. So if there's a some email and GPG key which belongs to an entity called Fubar LTD then Fubar LTD will be credited. I'm not interested that there is a real person behind this. I'm not interested that that's the real name of a person. It's just whatever is chosen for contribution. That we only check identities when we have to. Which is when we give people upload rights. Because we want to know where they live and go there to tickle them. So I take it that the main index will be the email. Even behind the scenes I mean probably the main index will be the email. That is an issue because depending on the data sources the index could be an email. In the BDS for example an Allioff account for commits in Allioff or the login name for sponsoring uploads. So possibly there could be some need of mixing things at some point. Which is a bit of a separate problem. I don't mind starting with that not being perfect or being fixed by hand. And if we evolve at some point there may be a way for people to login and quote that they control that GPG here that email address or that Allioff account. You know send an email challenge and say that's my email. But okay it is. Yes okay then emerge the two sets of contribution. Possibly for next year because it starts being a bit heavyweight. But there's a problem of doing this collection. If he's aware of something that may greatly help the NIA team. So this in the end can be something that can be used to detect when people are not contributing anymore. I would also want to make it so that if you are a data developer you are not automatically a data contributor. If you are not a data developer you are not automatically a data contributor. You are a data contributor only if you contribute to that data. If you are a data developer that does not contribute to that data then you are not on that list. You keep being a data developer. There's the usual I'm not interested in changing the rules for getting removed from data curing. I think what we have is fine but it's perfectly all right. If I'm not active in that for a year but I still care about the project and follow things but I don't contribute anymore then I'm perfectly happy that I'm not listed among the contributors for that year. There was a fact. Yes I'm delaying a comment from IRC. Wouldn't recognizing every small thing like just one body report debuts the weight of a data contributor that so other data contributors like the head of a translation team being equal to one back report that's the comment I'm not saying I agree. The way I see it again you can tell me if you don't like this but the way I see it they are the same. Maybe one has been a data contributor for much longer than the other so the time span of the contribution is the only extra bit or you can click on a person and list the contribution but I don't want to calculate a number of how much one is a contributor. I don't see why one would want to rank people by contribution. I'm not interested in that. I think it creates a kind of community where I don't want to be in personally. I mean that would be my personal feeling but I would be able to say thank you even if a person reports a bug that takes time to report a bug. There was an idea while talking about this formally earlier of having some data sources used only to compute the time span but not the status of contributors. For example mailing list traffic. Many people don't like the idea that if you send an email to a mailing list you are a data contributor. There's indeed many people that send lots of emails to their mailing list but do not contribute at all. However if somebody is a contributor for some other reason then it makes sense to look at mailing list involvement to say well you report the bug today but you will actively mailing list for a year so you are a data contributor because you report the bug and you've been a data contributor for a year because you've been into that for a long time. So splitting adding some data sources only used for computing the time and not the status. I would like to add something about the issue with detecting the people because we had some experience in the team maintenance thing and in UDD you have this carnivore database which is based on the key fingerprint and we even have for this people somebody with five different names, namespellings and so on. People are using different email addresses so I really really really doubt you can manage this for say more than 500 people because it's manual work and we tried it and it's hard to cope with this. No no I don't want to do manual work. Yeah but yeah okay good luck with automatic detection. No I don't want to do that much automatic detection either. I would like the things to be fixed as much as possible and at a lower level of data sources when that is not possible I would like to offer people a way to fix the data for themselves. There's that unpronounceable and evil website that tracks place of the developers that in my opinion should be legal but isn't. It starts with O, O-L-H-O-R or something like that.  So talking about privacy of these things and I guess if they can do what they do I think we don't have a problem to say thank you to a bunch of people. But they do have a mess their dataset is a mess but people still like that. I listed about 20 times their system and if I really cared about contributing then my identity for free for them to send it out then I can log in and merge these identities for them and I guess that's something we can offer and that can involve things like carnival and so on and possibly we can have personal updates for contributors. So they actively contribute to their individual identification? Yeah at least we've done all we can to thank them but well you know if I tell you thank you I don't expect you to say you didn't thank me in the appropriate way. Right? On the other hand I'm okay if people say well I also I'm the sort of person that they said that I don't need to thank me so many times and that's fine but on the other hand I'm perfectly happy if people want to use multiple identities for contributing to Debian. Somebody in Debian science may want to contribute to Debian games under a different name. For similar reasons I don't want to track the time frame of contributions below the month level. I don't want to say you have contributed to Debian games between 10 a.m. to 11 30 a.m. on a Thursday when you were meeting right? So it's I want it to be coarse it really needs to be mostly about thank you and about building reputation. It's reputation is also what we can reward people with which is kind of the point of the exercise and that reputation is nice to acknowledge and at the same time it's nice that we can look up someone's reputation at least as an account manager from best member if I can see what somebody's reputation and have a reasonable look then I can make the process much swifter for them and especially for non-uploading needs it's going to be very hard because I can't go and look at package changelogs to see that they've been active for 10 years in the process and if somebody is a non-uploading PDE that has no translations at the moment I have very hard time seeing what they've done possibly I don't understand the language so well and that makes makes it easier and that another outcome that I don't really want to see out of this is that we start to actually see in front of us that there is not just about technical development there's a lot more but people still perceive oh I'd like to contribute to that but I'm not a technical person and and many of us may have difficulty in pointing out the places but one can go and have a look at such a list of people and say hey look that there's people over there that do all sorts of other stuff it could be indexed by topic of contribution as well again uploading these are contributors that do uploading these are contributors that do translations that may be introduced at some point so that we can turn on a spotlight in several aspects of that in that we don't usually look into we just take it for granted. I have another question. Another concern more than anything one thing you have to say at the beginning is that maybe some people would be quite interested in this for for labor of reasons for work for creating a review and if it's as easy as to find a bag which can be very hard to do depending on the bag or very easy to do that depending on how much you put in and stuff wouldn't be wouldn't be able to be like calling people to put this running stuff or easy stuff there for just being in the list. Yeah well at that point it really depends on recruiters say that if you're a recruiter that just does a random google search and contacts whoever comes out like Google recruiters I keep being contacted about for things like managing clusters and if anyone's ever looked at what they do I don't manage clusters so if there's two recruiters like that then nothing you can do if people care to actually go in and to look at what the person has done then there is a way to find out what conversations actually were from just linking to the usual daily list of cards or uploads or commit logs and so on. So if I understand correctly you are ready to use the BTS as a source for the contributors and you could have a lot of nicknames that could be the the pope or plk8 or the name of a serial killer or whatever are you ready to use that maybe there could be some issue with people that would be falsely credited. Well I it depends we try and see what happens what happens it could be that for the backtracking system we need to have some extra intelligence built in to avoid crediting China manufacturing corporation or Viagra supplies for cheap. Mailing Mr. Kives Arvista somehow but again then maybe one maybe there's lots of noise and we want to to set a threshold that one contribution to the backtracking system is not going to be enough or maybe we can look if that bugger was closed no because you closed spam bugs anyway if there's craft if there's noise then we can filter somehow and maybe we lose some contributions but at least it wasn't for a lack of time I mean I don't want to go out of my way to thank someone I mean if I need to find out where you live to come to your home and say thank you because I don't see you anymore then or because I met you in a crowded square and you gave me directions but I didn't take down your phone number then it's unfair you won't be thanked when I find out there is my destination but that's life so yeah that maybe takes 10 emails to the BTS with different content to be acknowledged but it's possibly something to be I would leave freedom to the people doing an import thing something against it out of the backtracking system give that area freedom to work it out and and I won't I don't want anyone to be perfect the system is not going to be perfect if somebody would really like to be credited but isn't in the list and and what they do is report bugs I would be surprised because if if somebody wants to be credited only reported one bug I can say well just report some more I don't I'm not sure I want to have people in Debian that contributes in order to be credited if if contributing some more is a way to get credited then yeah we don't need to be perfect we just ask people to contribute some more or if people contribute the problem is when people contribute a lot but they're not credited that maybe we need to figure out how to import data from another part of that that we currently don't pack so well I'm totally not looking for perfection here have you sold about other ways to use mailing list archive because you said we don't always want to use it as a source of contribution but more to track the lengths of contribution but there are some lists for you on the FTA 810N translation list where I guess most people contribute are real contributors and sometimes they also use some code I mean the email could be notified like request for a view or something so you can add some hints on the type of contribution more precise than just sent a mail to the mailing list and maybe also for a user mailing list not tracking the question but only answers because why asking a question is not a real contribution to the event that helping someone else to use the Debian system is a contribution and one of the most important one to start this I guess decoding mailing list patterns fairly is not easy as far as I understand and I guess it changes from list to list but that could be solved by do adding a general mailing list source that only looks at time frame and having the translation team saying in our mailing list there's more semantic information that can be extracted so I'll make an extra imported from my team that decodes things and put it there properly as long as you can have many things done with data into the bucket then that works I currently have no idea well only take ideas on how what's the protocol to collect this data I would from from the central bit I wouldn't go much further than having a list of URLs from where I download something on a regular basis because that's the simplest protocol to identify whether some makes and whatnot and what's in the file that gets downloaded could be identity initial time final time if and then each data source makes a file available somewhere I was thinking of something super simple minded like that but then it's not enough because then if you want to look to make a link showing the contributions then well that needs something about how to how to collect how to make this data available from collection at the central point I'm only I want it as simple minded as possible I don't want the core of this to be about data collection about mine it should just be about collecting what has been mined last question just a suit on what you said there's a diversity project on the feed message which is very easy to have a bus collecting lots of information from various sorts of information among those there's already monitors that that I guess the BTS will be it's a source yeah but I guess even those evens could have made enough metadata like you don't fight a person the source is the feed message FED MSG it's from Fedora and the some of the students is trying to adapt it for a data just a stuff to a bus where you collect you get lots of evidence from various sources and maybe it could be a assuming that it goes further than this summer it could be an interesting use of this project okay as the mentor of this project I agree I think the students is arriving today so we're out of time so thank you and we're good yeah and you we can talk about this I plan to work on it during the datacons it shortly there should be Martin Ferrari coming who was also intending to work on a site similar to this and I guess we should all get together and think of something and feel free to stop me to talk about this and offer help or well that's the main thing I want to do at datacons and I want to get something done before the end of the datacons so we can present it properly thank you very much


Hello, and welcome to this screencast. In this video, we will solve an example of a separable differential equation. Our example of a differential equation is dy dt is equal to 3y plus 6. To solve this differential equation, that means we want to find a function y of t, so that when we differentiate that function y with respect to t, our result is 3 times that original function y plus 6. So our first step to solving this equation is factoring out the 3 on the right side, and so we get 3 times the quantity y plus 2. Next, we divide both sides by y plus 2, and so on the right side we're left with just 3. Our next step is to integrate both sides with respect to t. And on the left side, we see that we can simplify the integral by cancelling the dt, and so we're left with the integral of 1 divided by y plus 2 dy. When we evaluate that integral on the left side, we get the natural log of the absolute value of y plus 2. And on the right side, we get 3t plus some unknown constant c1. I called this constant c1 because I know we're going to modify it as we solve this before we're done with our problem, and so we'll change the name of an unknown constant as we go along. To solve this for y, we know we need to eliminate the natural log on the left side of the equation, so we're going to exponentiate both sides. On the left side, we raise e to the power of the natural log of y plus 2, and on the right side, we raise e to the power of 3t plus c1. e to the x in natural log of x are inverse functions, so the left side simplifies to just y plus 2. On the right side, we can use properties of logs to rewrite that as e to the 3t times e to a power of c1. Now the second part of that, e to the c1, is e raised to the power of a constant, and even though we don't know the value of c1, we do know that e to the c1 is just a constant, and so we can replace that with just c, so e to the 3t times c. We're almost there, now we just need to subtract 2 from both sides of our equation, and the result is y is equal to c times e to the 3t minus 2, where c is an unknown constant. This means there are infinitely many solutions to our differential equation that differ by the choice of that constant c, just like there are infinitely many anti-derivatives of a function. But we're not quite done yet, we still want to check our solution. So to do this, we start with the left side of the equation, and we differentiate our function y with respect to t. And the result is c times e to the 3t, and then since we're using the chain rule, we multiply that by 3, the derivative of the exponent. So that's the left side of our differential equation using our solution for y. Next, on the right side of our differential equation is 3y plus 6, and we want to find this for our value of y. So we substitute in c e to the 3t minus 2 for y, and then next we can distribute the 3, so we get 3c e to the 3t minus 6 and plus 6. So that minus 6 and plus 6 simplifies to 0, and leaving us with 3c e to the 3t. So that's our result for the right side of our equation using our solution for y. We compare these two results, and we see that using our solution for y, the left side and the right side of the differential equation are equal. And so that means our solution y is equal to c times e to the 3t minus 2 is in fact the correct one. Thanks for watching.


Hello everybody. I'm Dr. Sanjeev Rao. I work in the Department of Medicine at the Manipal Hospital. I've been here since 2001. On the occasion of the World Immunization Week, I am here to talk a few words about the importance of immunization. Immunization is a very simple thing which prevents a whole lot of unnecessary expenses and complications in certain cases, even death. Now, just because you have taken the immunization in childhood, that doesn't mean you will not get it in adults because after some time, your body starts to forget the childhood diseases. So you're prone to get it in adults. The other important thing you must realize is that there are some people who have immunocompromised such as diabetics, elderly more than 65, chronic labor patients, chronic kidney patients, transplant recipients, HIV. These people are low immune status, so they are no prone to infectious diseases and that is where this comes in. The other important thing is that the public in everyday life are so exposed to communicable diseases such as typhoid and H1N1, we certainly recommend that you take this every year or whatever the schedule is. The other important, the last thing I would like to stress is please make sure you take your H1N1 vaccine every year because it's so prevalent now compared to earlier and it is quite a severe disease if it does come.


Team keep it clean. It just came out a few minutes ago that the NFL will be shortening the preseason Eliminating both the first and last preseason games weeks one and four Now, of course, we already know that they eliminated the Hall of Fame game Between I believe it was gonna be as still as in the Cowboys this year but now they have officially dipped into the preseason But I think this comes as no surprise with all the reports of second wave of the pandemic that was also something that was to be expected And I mean, we'll see We'll see what happens next. I know this this sort of serves as a scare for a lot of people in regards to the NFL season I know it's a lot of people thinking there will be a season. There's a lot of people thinking there won't be a season Me I still think there will be a season, but I think there'll be a lot of changes Think there will certainly be a lot of changes. I as of right now I would not anticipate any fans being in the stadiums and he fans being in the stands and he tailgating anything like that and again there It's just there's gonna be a new norm It's gonna be a new norm just in life in general, but as regards to football is It's going to be a very different season just period already has been a very different season We already saw they had all these big plans for the drafts and stuff They had the players they had playing on the players coming out with the boats and stuff in the water and all that But that got changed. They did a virtual draft Free agency that was talk. Oh, they should push free agency back But NFL said no, we're not pushing free agency back. We're not doing that so free agency was virtual and They had to sign they they had to get their contracts faxed to them or whatnot and sign them that way So NFL has shown That Despite everything The show must go on and That's why I think the NFL the regular season isn't going anywhere things will be different, but I still don't think it's going anywhere With the NFL They they did all they did cancel the supplemental draft. That was another thing they cancelled so far They cancelled the supplemental draft and the first and fourth preseason game It's weird because those are the preseason games that actually The starters play the least amount of time in but Those are some of the preseason games that are most important for like backups and depth guys and Undrafted rookie free agents and dudes just trying to make the roster so This thing I was just talking to my wife about it yesterday telling her like man like this has affected a lot of people big time Just work wise period Not just NFL, but work wise period in the world And like people that we know personally, and I know people that y'all know personally too And it's tough man, it's tough It's very very tough, but then we think about it with the NFL is gonna affect a lot of them, too Because with people who are like shaky with making a roster Now it's like they they're even more shaky. They're probably even more scared now here Won't say here this news because it's supposed to officially come out like tomorrow But once they hear this news, it's gonna be like, oh man Now I have even less of a chance Now granted it could make them work even more harder, but at the same time it can be like very troubling Scary for that sixth or seventh round draft pick or that undrafted rookie free agent or that free agent that guy signed who Isn't a starter isn't an obvious starter and it's just considered a depth guy That guy may be thinking oh, so it's big. This is big. It's big news But we'll see What happens next team keeping clean appreciate y'all and I'm out


Welcome to Logical Reasoning in Speeches Public Speakers beware. Errors in reasoning are also known as logical fallacies. The eight most common logical fallacies are ad hominem, ad absurdum, including the straw man argument, either or fallacy, post hoc ergo proctor hoc, ad vericundium, ad populum, red herring and slippery slope, ad hominem. Speakers who use this technique attack the integrity of a person to weaken that person's argument. For example, rather than deal with the substance of the real issue, such as environmental concerns for example, the speaker says, how can you trust this bureaucrat? Ad absurdum. Speakers who use this technique extend the argument to ridiculous extremes. For example, a teenager says to her parents when they disallow her going out one night, well fine, you might as well send me to the convent. A variation of ad absurdum is the straw man argument. The name straw man implies a flimsy argument that is knocked down. The straw man argument is a weak example that a speaker uses to suggest that it represents the entire population. For example, some of our students don't own a computer. We shouldn't have students use computers in school, either or fallacy. Speakers attempt to force a choice between two alternatives as if those are the only two. For example, either we build a new school or our children will never go to college. Post hoc ergo proctor hoc, better known as false cause. For example, if a black cat crosses your path and five minutes later you fall and break your arm, the cat was the cause of your bad luck. Ad vericundium, appealing to an authority for your argument. The problem is the authority may not be the authority on that issue. For example, remember years ago when then football player Joe Namath was endorsing a specific brand of pantyhose? Joe may not have been a real expert on that issue. Ad populum, often called jumping on the bandwagon. For example, recall those conversations with your parents when you asked them if you could do something because all of your friends were. Their response may have been, if they all jumped off a cliff would you too? Red herring. Fish has a strong odor. It is said that farmers in England used to drag a fish along the edge of the fields to keep hunters and hounds off track. Speakers who use the red herring technique divert attention from the subject of discussion. For example, why should we worry about the amount of violence on television when thousands of people are killed in automobile accidents each year? The number of people killed in automobile accidents is a serious problem, but it has no bearing on the question of whether there is too much violence on television. This is a red herring or a stinky fish dragged across the trail to divert the attention from the real problem. Slippery slope. The fallacy lies within the assumption that point A leads to point B, then to point C, and so on. For example, if you require background checks on gun purchases, the next thing is registration, then outlaw ownership, then confiscation. You have just learned about eight common logical fallacies. Logicians have identified in excess of 125 logical fallacies. This concludes this learning object on logical reasoning in speeches.