Oh boy, this deus fishing freaks. I sound like Paul Bunyan coming off the lumber wagon. For some reason down here, I cannot breathe when I'm sleeping. So I'm just, I just, ah, been waking up like this every day. The van is about to be here. The van picks us up every morning. They pick up all of our tackle off the porch. They take us down to the lake. It's a windy ride down the edge of a mountain which you guys can't really see because it's in the middle of the dark. Today is the last day. It has been tough. My biggest pass of the trip is an 8-8. That is actually the biggest pass on the board as of right now out of our group. So it should be bigger than that and there should be more of those. Today we got changing conditions. There's a little wind in the air which is awesome.  And I'm fishing with my buddy Matt. He's good luck. He usually just catches a random big one. He's already caught a real nice one this trip. I got a better feeling about today. With the wind, keep that blade out in deep water. Joom, Joom, Joom, Joom, bye-ya. Plus I had a dream last night. I didn't pass math class. I went to college but they wouldn't give me my degree until I went back to high school and I had to pass college or, okay, exactly. Everyone was like on this digital thing and I was writing him a paper and I was terrible and then I woke up and I was like I'm so glad I don't have to go back to high school math class. It's gonna be a good day. To the first hole. Beautiful sunrise. Good day. We're on a giant, giant point that has huge boulders. This is the most distinct big structure, rock structure point on the whole lake. And I've heard a few stories about some giants being lost and caught here. Like some true giants. I think Ron Speed, the owner of the lodge, he had what he says is like a 24 or 25 pound bass on here. I think we're probably gonna throw spinner baits and other stuff out deep for a big bite but I'm just trying the top water right now just to see. Oh, got it. Lapina, boquito. This is not what we were expecting. 18 foot right here and back out. Hey, good times though. Yeah, I'll let you get that one. Yes, sir. Triple hooks. I think a good way to break the ice. First couple casts. Would've been nice if it was like six, but we'll get there. Those are bass. Dude, they are sitting here. Look at that. Oh my gosh, there's some big arcs right on this ledge below us. Right where they're supposed to. 15 to 18 on that drop net. The Mondo worm on a Texas rig is. It's about 200. It's, yes. That looks like three eight pounders right there is what that looks like on the graph. Not kidding. I wouldn't make that up. Fish number two. Absolutely choked a spinnerbait. Yeah, I'll give it a sniff. I have to smell a fish. Look at that fish. He's been cut. Nice. Have you fished the river much? A little bit. We're trying to decide where to go. It kind of all sucks right now, so we're not sure. We've already cracked open a medalo. I've tried something new. We're going with a Mondo worm. Aided Tago worm. So instead of throwing like a sinko, a baby. Where's Cass? Took my whole unit. Yay, set my first bite on this little dangler. This thing looks absolutely awesome in the water. Wait, yeah, on a weightless, there's one. He's got it. Yay, Pokémon! The weightless Mondo. Lightly weighted Mondo. Oh, boil on. Look at the size of that boil. That was a better fish. Oh, look at this tasty little bush. Ooh, hit it swimming in. What a guy. Toward my worm. I had one on, why? Lavena? See? Lavena y tilapia? Yeah. Possible? Cereza mueves. He's saying that there might be a bass with a tilapia down its throat over here. Let's check it out. There might be a bass over here that's eating the tilapia. And it's having some trouble at the surface, so we're gonna go investigate. See? See, lavena. Lavena y tilapia. It is. It's a small bass with a tilapia. Look at it. Look at that. That is crazy. It's not even that big. This is nuts. This isn't even a big bass. It's just, this is what they want right here. They have like a spine or something. There it is. Our biggest catch of the day. Crazy. Double-dip. Okay, we're gonna save this guy. We're gonna take the tilapia out.  So it takes a little finagling here. And that's a tilapia. That is a two-pound bass. Trying to eat it. All right, buddy. Let's make sure you're okay. All right, come on. Kick. Kick. There you go. There you go. Get back down there. Nice. Well, looks like we saved the bass' life. Lavena. Lavena is a bass. It's Spanish. That was awesome. It's not every day you see that, y'all. Chee-hoo. Is that Sobi? That was Sobi with a tripod. What was he holding then? That wouldn't surprise me. Well, I didn't hear any bullets was by, so I guess we're okay. Well, folks, when you're down in Mexico and you hear gunshots, it's... Yeah, it happens a little bit. There's someone up on the bank right now. Either shooting buzzards or shooting birds or shooting someone I don't really know. What was these guys over here? It's those guys? Yeah. Maybe, oh, he was holding a gun. He wasn't holding the tripod. I'm gonna guess that wasn't Sobi then. Look at the tilapia on the bank. We're in 16, 18. I'm gonna throw a big jig right here. This looks like a big jig bank. That is a solid two-and-three-quarter dandy. A little deeper. Slaying my crack in, man. Nope. Oh, no. GT, oh, that doesn't count. See, it came off. It's moved up. It's flared. We're in a quarter pound. So, it's our base is around, boys. So here is our drinking game. If you catch a bass under two pounds, you have to drink a beer. If you catch a bass over five pounds, you get to choose a person in the boat that has to drink a beer. If you catch a double-dig, pretty much the whole lake just has to get drunk.   That's your basis. What's going on today? You have it. He said the sunshine was a thing on the points and Dag Emma, he was right. He said we were gonna catch a little bass on the last spot and, well, he was right. Manager Matt just has everything dialed. I've seen all this lake. Now time to throw at this point right here, with that brush on it. This is the key to catching big bass, going to big points with deep water, close by chunking big baits and 12 to 15 feet of water, fishing slow, and then just waiting on that boom. And then don't mess up. This is a drink sponsor. Official fueler of the trip. Coffee, free-range coffee in Modelo. Fueling you through the hard times. Yeah.  It's a good fish. Fish on, fish on. Oh gosh, this is a beer fit. No, it's not. It's over two. No, no, no. Fish, you don't have to drink a beer to, that's, that's what I'm talking about. Hey. Dag Gummitch. Mui Gordo. Gosh, biggin. Biggin net? Oh gosh, no, it hit it and then it's in a tree. Dude, that was, whoo, honey. I don't know what really happened there. I guess he like yanked it off the hook or something. But he's bigger than two. No. Oh, marks, marks on the graph. Bueno, I was on the bottom when I got that bite. Oh, here we go now. There is, is that a five? No, it's a four. Does he have more? No. He's a fiver. You think so? There's definitely more right here, boys. We're on them? Yep. What's a five on them?  First class major league dangled tangler there. That's what happened when you threw a one out. Spinner bait around. And we got another one back here. Backlash or a stuck? Stucky. I got like 10 songs and loud. Imagine dragons? He did. You like it? You get, it's good? Cold beer and labinas. Labinas Ibruskis. Have a good booze, crew's gentlemen. Just had ourselves another survey set delivery. Had to drink a couple more beers out here since I caught that good fish. One Carlos, AKA Senior Bass, he caught a seven.  John's caught an eight, but there's big bass being caught out here. There's also a lot of available fish, so. Right here. Good suit. Oh, of course. There you go. I'm gonna take a time out here, drink my beers. It's called a two pound game. Get out. See? One last. See, yes. You gotta drink a beer if you catch one. Oh yeah. Uh-huh. Please be a 12 pounder.  La Cerveza, Ricardo. La Cerveza. La Cerveza. Imagine if all those one pound fish were fours and fives. There's Bryant back there, about four Modelo's. Short. Short on his game, slamming him on top waters and Mondo worms. What's wrong? Well, probably there's some homeowners in the way now. Just wait till we get to the next point. Yeah, yeah. You wanna feel all these dogs? Well, man's trying to take a whiz or here. And we're about to go to another point over here.  That's probably one of the best views you'll ever have while taking a tinkle. Everywhere we've been, there's been big bass on these points. And they just don't seem to wanna strike it, though. There's like a ridge that runs out right there. Also right here, though. It's gonna be big. It's gonna be big. Get him out. It's just head shaking, Bryant. It's gonna be huge. Watch this. This is gonna be a very big fish, Bryant. This is Bryant. Okay, oh. Hold that, hold that. I got it, I got it, I got it. That's a big fish. Oh my God! Yes, Bryant. Yes. Oh my God. Yes. That a boy. Oh my God. Mondo's a boy. That's my biggest best ever. Yeah. Look at that bad boy. Oh my gosh. Scale. Scale. Caught it on a train jog, baby. Oh my goodness. How about this? I don't know. We'll see. I'm gonna say it's definitely a seven. We'll see. Seven, nine. It's a seven, nine? I don't know, seven, eight. Freakin' toad. Nice, Bryant. Almost an eight pounder. Almost an eight, a seven, eight, four. Almost an eight pounder. So that's for the boy. That's frickin' awesome. His biggest bass ever. That is frickin' cool, dude. Bryant, good fish, buddy. Seven and three-quarter pounds. A little over seven and three-quarter pounds. Biggest bass ever for Bryant. Just let it go and give it a little tickle on the back. There you go. That's awesome, dude. Cool, caught on a goog and bait, PB.  And then I turn around, I see Bryant's rod doubled over and I'm like, get the net. That's a big one. It feels totally different, doesn't it? It does. It's just like. That's what she said. Well, he said this morning a big bass would cure all his illness. And it did. That's a drinkin' fish. That's a survey fish. What a nice fish. Under two, end of the day, end of the trip. What by him? He was losing all hope, I'm talking. Dude. Dude, I was so, I passed out for about an hour. I was sitting there, just dying. I could hear my heart pulsating through my ears. It was that bad. I was hallucinating at one point. Callin' off. Okay, y'all, we've had three PB's broken today. Epic, epic day. So Hector, who came down here, who I fished with on the first day, he broke his PB with an eight, four, baby! Ross broke his PB, Brian broke his PB. This is what Commendero is all about. We've been havin' an absolute fun time, but on the last day, on the last dangle.  I just got one in the lineup. Three beers, three fishermen, end of the day, three guys broke their PB today. I think it's only customary that we finish off the Paco Modelo's here, here at Bronzebees Adventures.  Congratulations. I think this is where I'm gonna send you off, folks. What an incredible day, an incredible experience here. As always, awesome in Mexico that leaves me hungry for more fishing trips down here. You guys know what to do. Subscribe right here to the channel. I love ya. I see ya out in the next one.


I would now like to introduce Andrew Bartlett, who is on the core of the SAMBA team to talk about packaging SAMBA 4.4 deviant, and his trials and tribulations on doing that. Hi, so I've been a SAMBA team member since 2001, and I've been working on the Active Directory DC since about 2006, so that was the SAMBA 4 project that so many of you have known and heard about for way more years than it ever actually really existed. And I've also been involved peripherally in the Debian packaging team. The Debian community has always had the most interesting SAMBA bugs, so even as a long time Fedora user, I have always hung out on the Debian packaging list because that's where you got some of the really interesting issues to chase down. And despite being a long time Fedora user, I ended up doing the Debian package merge for SAMBA 4 because I was working for Netgear at the time, and they run a Debian box inside those Netgear NASs, they're just a Debian wheezy these days, and they need packages. So they of course didn't want to be maintaining their own packages forever, so they just wanted to get the upstream ones into shape. So I also want to thank Catalyst, they keep me bed and watered while I do great things on SAMBA, and I also want to thank those fellow SAMBA team members in the Debian packaging team who took the work that I started and got polished enough that we now have it in the next release. I would very much appreciate it if folks would ask questions during the talk. This would be very boring if I'm just the one speaking, so please, if you've got some thoughts or you've been packaging other software that has some of these complexities or challenges, I'd rather go off and digression and discuss how we can do these things better. Now, most in the room you probably know what SAMBA is, but I thought I'd remind you how broad SAMBA is these days. It's more than just a file server, it's more than just a print server, it is the Active Directory demo controller, but also a number of quite fundamental libraries to a modern system. So TDB, TALAC, LDB, DCE, RPC client libraries for connecting to Microsoft Exchange servers, one of the most important things we now provide with SAMBA 4, and the Active Directory DC. I'd like to think of SAMBA as the center of the universe. Removing SAMBA from your system is rather detrimental to its operation. So our TDB is needed by 3,000 other packages indirectly, TALAC, 2,000, Lib S CME client will still remove your desktop, and the SAMBA Libs, which covers some of our other packages that use it, come to Reverse Dependency in 140 because of the evolution may be using our DCRPC libraries. So it's a fairly core and important package between the different bits that we all maintain as part of the SAMBA package, and that makes it important to get right, and also gives us some real challenges because we have a semi-monolithic system. We develop SAMBA as one whole of SAMBA. One SAMBA.tar.gz that is released, and yet you've got packages and parts of the package that you might wish to have advanced at different rates. You might really want your file server to be old and conservative, almost crusty, because it's just once a server files and you don't do that well. Or you might want to have the latest release of TALAC because we've added some useful feature there. We do have different versions for TDB and TALAC, but they do come out on the same table as SAMBA Master. We do generally require that version of TDB or TALAC when you build SAMBA so that you we basically say your system version must be the same as the version we have in Tree, because that's what we've actually tested within our order build system. We can relax those checks and some distributions do occasionally when they know that it's all OK. But in general, we don't do things in Tree. We're saying, oh, we'll do these workarounds for old versions of TDB or TALAC, we generally say, no, you'll have the current version. And so a lot of all these packages have to be upgraded all in sync, even if they don't all have to be installed at once. So TDB and TALAC do have their own build systems, though, but they use the big SAMBA build system, but they do build on their own. So it's, and one of the other important things is that SAMBA does follow the Debian rules and can build against system copies of TDB or TALAC or LEB. And indeed, that's the right way to do it, because we have quite strong rules that we don't want embedded copies of libraries because of all the challenges that brings. So SAMBA can do all these things, but it just makes the packaging worse, not better, rather than just being able to build SAMBA with the things that are in the tarball. We have to try and make sure all these other parts that we provided in the tarball are actually all correct anyway. So it's a bit complex and it makes it a little bit more off-putting to be part of the packaging effort, it seems. The other challenge that I alluded to earlier is that SAMBA is both very progressive and very conservative at the same time. One of the fundamental tensions in the SAMBA team is the tension between those who've got a stable file server that they just want to not change, not fuss with, not be innovative with, you know, that was a real, when the protocol wasn't changing for many years, that was a real feeling on the team. We've got this down, well, don't bust it, just get things, just fix things and keep people a file server they're putting in their NAS. We've also got the other end, where we were doing things like inventing Talica a while back when Trig did that work. He did a lot of work improving that and took, or LDB, or the whole Active Directory DC. And there we're trying to go the other way. We really want to be using things like we're using Python these days. We're wanting to be doing good work using modern, available things, like we want to maybe use external libraries that are unavailable everywhere. So there's a real tension, and our users are wanting their file server to remain really stable. If you've got a distribution and you're trying to pick what version of SAMBA to run, you've got the real compromise of the file server users wanting really stable, just don't mess with it. It was working. And the Active Directory users are saying, I need 2012 support. OK, so how are we going to do both of these at the same time? And how is a distribution like Debian going to cope for both of those users, giving them the packages they want? So one solution that we had to this, in a sense, was that SAMBA was packaged twice. SAMBA 4 was going to be the new SAMBA, and so a SAMBA 4 package forked to match the SAMBA 4 technology previous that we were making, particularly to support Open Change. We had SAMBA 4 in Experimental, and we had SAMBA in Main. And the two would coexist with different versions. It mirrored the reality and the sad reality that we had on the SAMBA team where we effectively did fork. And we never really wanted to admit that, and we tried not to talk a lot about it. But the team really did split in two under the one banner. And so the packages mirrored that reality. We were doing releases that were separate. We had SAMBA 3X releases continuing, and we had SAMBA 4 technology previews going at a completely different pace than unrelated to each other. So we had two lots of packages trying to mirror this new reality. SAMBA 3X was the traditional SAMBA, and SAMBA 4, including all the things you normally expect. So SMBD, NMD, Windbind, but not some of the libraries that packages like Evolution MAPI were really after. They were off in the SAMBA 4 package. And while we were at it, we packaged up the Active Directory domain controller, because the Debian attitude of if it's there, package it, and someone might want to use it that way. And that was, you know, got some people really good access into that code. We also gratuitously rewrote a number of client tools, keeping the same names, and had NSS Windbind, and we went, again, but it wasn't just here, SAMBA 3, here, SAMBA 4, and they don't need to mess with each other. Well, they used the same SMBDoc whole file. They used overlapping binary names, and so we got around to it and renamed Net from SAMBA 4 into SAMBA Tool. We had Net and Net. We had SMB Client and SMB Client. NMD Lookup and NMD Lookup. They've both gone into two different directions with different improvements. We even had different NSS Windbind and PAM Windbind, because they're looking for different copies of Windbind, because we'd forked that as well and rewritten it. This was not a very happy state of affairs, but at least when you install the SAMBA 4 packages, you got SAMBA 4, and you could sort of mostly keep it going with SAMBA 3. Alternatives were used to try and cope with two different binaries with the same name. And lots of good work was done by really smart developers like the Yomav Noi here, but it still wasn't very pretty. But neither was the situation upstream, so you can't really expect anything else. So time passes. SAMBA's gone from being just an experimental to unstable, because we want Evolution Mappy to be in unstable, because people want to be able to access their corporate email. The Active Directory DC follows into unstable, and it seems a reasonable place to go. At this point, there's still no prospect of a SAMBA 4 release. We may as well get the forked package featured so that people can use some of this software. And from testing it ends up, it goes into testing, and testing it goes into stable. In the meantime, SAMBA unhawks. We finally get our act together. We merge the Git repositories. We actually start merging the code base. We start trying to find similar bits of code, merging them together, putting them in common areas. SAMBA 10G was a previous fork of SAMBA, and a really nasty one in terms of how it impacted on the team. It was personal to some. It was painful to all. And a decade and more on those pains, the team was not willing to do that, even though we'd gone and really broken ourselves apart internally, we were not willing to break apart fully. And so the effort was really made to try and get SAMBA back together again. And that ended up being the precondition for SAMBA 4. The rule was that we would not release SAMBA 4.0. And it was very frustrating to me over many years, I feel like I couldn't release this thing. The rule the team set is you can't call it SAMBA 4.0 until there's one SAMBA 4.0. Because people who were working on SAMBA 3.6 did not want to be seen as working on the old version of SAMBA. Because SAMBA 4 was released and was replacing it all. And rightly so, they were doing really good work. And their work is now very much leading where SAMBA is going. But that was the rules. And that's where we ended up having to then make the packaging, the packaging start matching the new reality again of the SAMBA team of we're not forked with one tab or one release. We also had some changes in the way SAMBA was being updated. We couldn't keep updating unstable with new versions of SAMBA as we got them towards the 4.0 release. This situation of two different types of packages couldn't continue either. So further updates went into experimental. But we got around to our release of SAMBA 4.0 and Red Hat packages, SAMBA 4.0, and Debin is still saying that the latest is 3.6 and it's never heard of this 4.0 thing. We didn't strip out the SAMBA 4.0 package. When it got towards stable, we didn't do any work to try and put only in stable things that we thought were long-term stable parts of SAMBA. There are bits that we weren't going to be changing too much. The whole lot ended up in there. Oops. So an old, unsupported, previously SAMBA 4.0 ships, including the Active Directory DC, would beat it too because that's where we got to before the Debian freeze. And we nobody wanted to try and break the freeze to break the packages to remove the functionality because that was going against all sorts of other things that were important in Debian and also just required time and effort and things that none of us really had. So SAMBA 4.0 releases and people go, ooh, okay, Appget installs SAMBA, oh, that's SAMBA 3.6, Appget installs SAMBA 4. Oh, I've got my new SAMBA 4.0 DC. Guys, that's the one we stopped working on six months ago and there are lots of bugs we fixed since. And by the way, you're using the wrong file server because we developed a whole file server only to basically ditch it because we realized we didn't have the developers remain two file servers and the concepts, while some of them, great, did not end up. We try to patch our new file server better, but none of the code is being used. There's some interesting functionality it's got, but we've got Debian there shipping, in the stable release, shipping the file server that we don't want to maintain anymore and we don't really, we think it's well written, but not so good. And basically telling our users, there is no Debian package. If you want this, go off to a third party vendor and install their package. So Serdet, who supports our SAMBA XP conference, who's a big force behind SAMBA, has a website enterprise SAMBA and one of the things they provide is SAMBA packages that let the installers a different location in your system and generally complimentary. And so a lot of people are being suggested, we'll go over and run Serdet packages. So there's no simple upgrade path. They're so real way forward for our users. There's no one wanting to just package SAMBA, the way they've been packaged before. Because you could have, I suppose, done that.  We even had the old build system. We kept that around for one release. But no one really wanted to release a SAMBA 4.0 on Debian. They didn't include all the bits that people thought SAMBA 4.0 was, which is like the Active Directory Domain Controller and all the client libraries and things. Red Hat did though. Red Hat, they got some bits of our new advanced functionality, but none of the DC, they objected to us using Hymber Kerberos. But there's also no desire to try and keep this split up. And I don't think we could have because upstream had merged these two things together. And because we've moved to using one file server, SMBD, that we've always had and using that everywhere, we couldn't really start having the SAMBA 3.0 and SAMBA 4.0 packages be separate because they really had to be exactly the same versions and things like that. So the whole thing was basically stagnation. A large amount of work required to move forward and no one really stepping up to do any of it because it was clearly going to be months worth of work to do. And in the volunteer community, these things don't just sort of happen because one wants it to. So I stepped up. I'd done some RPMs before, so I was clearly qualified to do packaging. I figured I could learn, I was working with smart folks. And it didn't seem too hard. I had some things to start from. Netgear had had some things that they quickly hacked up and wanted improved. So we merged SAMBA 4.0. We got it into experimental in June of 2013 and we got it into unstable in October. I haven't really got many slides about exactly what the work involved there was, but it was a lot of trying to juggle which binaries to go where and trying to come up with a set of packages that wasn't insanely long yet, not just SAMBA. It's, for the first time, SAMBA has used shared libraries internally. So in the past, SAMBA essentially was statically linked. It would link dynamically against system libraries. But as far as anything that was internal, like SMBD and NBD share a lot of things in common, like loading the SMB.conf. But essentially, they were statically linked from that perspective. And more particularly, they shared the DCRPC client libraries. All the parsing of our protocols was separately in each of these binaries. And so these were now all shared. So once you've got shared libraries, you've got to put those shared libraries into packages that the right things depend on and not have dependency loops and all matter of claim. The deviant way of doing libraries is to have one library per package as the preferred way of doing it, particularly around public libraries. This turned out to be totally unmanageable. We have a lot of public libraries. And when we try to do any reasonable grouping of it, you end up just with circular dependencies. Because while the libraries themselves mostly don't have circular dependencies, there's one spot where we do, the packages, once you had reasonable groupings, the packages all did, and it just was a nightmare. So we ended up with just a SAMBA Lips package. So essentially have, which is basically which is the bulk of SAMBA. So the one that is SMBD contains is tiny because all the functionality is somewhere else in the shared libraries. And you've got this thing that has made a couple of support C files, but they end up jumping into a library. In fact, there's a big library for SMBD because we share that between SMBD and the torture process that basically does let you test some things. So it's still very difficult to split up, but we've got packages for PAMWINbind, Lips and Recline. The things that you really sort of notice on their own, and we basically don't consume directly. So we had some difficult choices to what to do about the situation in Stable. We basically ended up deciding that shipping beta 2 or SAMBA 4 to users was just dangerous. The security issues coming forward and other bits and pieces, no one was updating, no one was looking at it. So we basically emptied the packages of their binaries. So to force those packages, and I think we set some conflicts and things to try and force the packages off the system, but if you did update them, you would basically get a package without anything in there and read me saying, sorry, this has gone away. So it was pretty difficult and really shouldn't have been done in Stable. It really breaks all the rules of Debbie in Stable. And it's something we really should have had the gumption to do well before the release. We've got updated packages in, the packages were still being updated a little bit experimental, but even those were getting old. So mainly the way that we've basically told users to go forward is to then move to back ports. So the back ports do have a current SAMBA and you can install that on current Weezy. But it was a mess and telling people, your functionality's gone away, but it's over in back ports. You'll have to upgrade this a little bit. It's not how I'd like to be doing it, but at least we don't have that old code with this promise of support that we just can't make. We also have other challenges. One of the big things that Debbie is about is about using the system libraries. And so we use the system Heimdall. Because SAMBA bundles a copy of Heimdall, a very particular release of Heimdall that we then do our testing with. But we don't want to be using that in Debian. So we basically try to get our patches upstream, get those into the package that Debian's got, use then use the Debian library. Unfortunately, we have now allowed three years or so to develop between the two versions of Heimdall between SAMBA and the proper system Heimdall packages. So we've got things like segfaults in the KDC that we had to fix because a semi-private structure got changed. It's not quite clear whether they broke the rules. Well, it's clear that we're not delving into private header files. But basically, no one's really watching the ABI for KDC plugins because they're essentially we're the only one and no one's got a test. And so their patches had to be merged in with detecting which version we've got to get things right. It's still untested. Our users test it until it works. But we've updated SAMBA to current Heimdall in a test branch. I've been doing that work at Catalyst and it doesn't pass my test. So we know that there are issues that are gonna happen. And it does worry me that essentially the Debian SAMBA 4 package, we know that there are things that are breaks. And it makes things even more difficult for SAMBA 4.2 to go ahead. I had some good suggestions in the hallway track earlier about what to do for 4.2. I'm really concerned that we could have a security hole because password lockout, which is one of the features SAMBA 4.2 has, needs some hooks in the KDC to say, don't check the password if it's already locked out. Because otherwise you'll tell the user what the password, that they're still wrong with the password and let them keep on trying. We had a security hole with this. Microsoft had a security hole with this in a different area. So we probably need to actually have a runtime check that goes and tries to talk to our KDC, check the password of a user that's deliberately locked out and confirm that indeed it, we never get the password checked. We just get the check for the lockout value. Yeah? Do you have a jury bill or more like a jury run time? So the question was about whether, when we're doing this assertion about the password lockout is working, whether it should be in build or run time. I mean, I'd like to get the build time tests going, but what the suggestion was to me is that I should actually start having run time self assertions that start up to do a few self checks. So that we know that we're still running against a KDC that's actually gonna enforce the right things. I certainly don't look forward to the security release that we have because of mucking this kind of stuff up. So yes, there's some of the challenges that we've got and we're gonna have to, when we do upgrade to 4.2 it'll probably have to be combined with specially patching the Heimdall in Debian and then trying to make sure it stays that way. Password lockouts an interesting one because it's one of the few failures you can, where you can open a security hole where you don't notice it by seagull faults or those kind of things. It's just about not doing something. You're not checking a lockout flag before you do the normal thing as expected. So it's a subtle kind of bug like that unless you're really watching you can get. So I might have had a similar thing for the same kind of reasons. So I want make test in Debian. Our test suite is very comprehensive. It takes a couple of hours. I'd really like to be able to test the whole Debian package but not just as well as the KDC because of the reasons we talk about. There's some work that Red Hat's been doing to try and get make tests to run against a difference. They're code-based, they want to use MIT Kerberos and so they changed their make tests to work from something that worked on compile. We would actually override all the socket functions using a header file and a system called socket wrapper and we were able to create an entirely fake networking layer inside Samba and a number of other fake layers. One of the guys, Andreas Snyder from Red Hat has done some great work doing that with LD Preload. That gives us some great advantages because while you don't want to compile your production packages with socket wrapper, you certainly could allow them to be preloaded and so that could potentially allow us to run make test and then to be able to find these kind of issues at build time. Now, running a make test with about 10% failure rate in an automated build environment, of someone else's automated build environment is a bit challenging but it still gives us a lot better, more confidence that if it passes that that we're still actually still not screwing up. That's one of the things I'd like to go and I'd like to understand whether the Debian build and test system is actually up for doing a two hour long make test. So long-term implications of all this, we missed the boat on Weezy so we've still got an old version there. So there's no upstream support for functionality issues in the version of Samba in current Debian stable. There's even, there was for the first six months but often it's gone. Now it's in security support but it's about to leave security support as soon as we release Samba 4.2 in the next month or two. Do we, what do we promise our users? What resources do we have in the Debian packaging team for resolving bugs? I had people complaining about an issue with NTLM auth and machine accounts and it was fairly esoteric. We did some testing, it's gone on current master. We're not supporting that version anymore from a Samba team perspective. What should we be doing from a Debian perspective? What should we be telling our users about the software that's in stable and they think they can file bugs against? How do we communicate to users that the version of software that we've got in Debian stable is actually so old that it's not gonna be fixed because most bugs are too complex for the package team to deal with and upstream it's too old. Now it turns out we're a little more flexible now in that if you are, you may well find and get people to patch that. We could patch it up in Debian if you're really, really keen, if it was really bad enough. But does make me a little bit worried about just having let things get that far behind. Or do we basically end up having users basically go, oh, Debian is too old, use back ports or use a third party is the only way to get actually a supportable Samba. Is that the way we want to be dealing with core bits of our system? I'm not sure. How do we keep Samba up to date for our users? Even when Samba is in a mode of, we only make fixes to Samba that have a bug filed against it in our bug system as upstream, it seems to be very difficult to get those updated versions of Samba into Debian because Debian will only allow an upload if there's a Debian bug for every change that's in there and generally won't allow a version to be updated. Even the Samba team is doing a really good job of saying only issues with a bug attached and reviewed by two team members can be in new versions. I think that we're letting Samba get too far behind and we're not allowing our users to get the fixes that have been developed elsewhere and have considered production ready by the Samba team but Debian Stable is so conservative that we can't even do that. And I think that lets our users down. And how do we do this better next time? I mean, I hope Samba doesn't fork again. I really hope Samba doesn't fork again. That was not fun. How do we support file server and active directory user expectations? How do we try and deal with the conservative and the progressive in the same package? Should we have done the old libraries over here, this functionality there, separate projects, separate allowing things to skew against each other? Oh, you can use the old file server with a new this and that. That sounds insane to me as a developer trying to allow all manner of combinations particularly at the distributions discretion. I really liked the world we're in where we really forced know you'll use the current version. That's the one we tested with. I don't think we should let pre-release packages escape into Stable. I think we should have found them. And where we had to leave that because otherwise we were blocking other people's important work. I think we really should have cut it down to exactly what was needed by those other packages and not a thing more. As otherwise, we're just making just promises that are just really unfortunate. So everyone's been very quiet. I hope you found this interesting. These are things that we do at Catalyst. If you're interested in working on Samba and things like that, if you know see Python Git networking, Wireshark and don't think that list is getting too long already then please catch me in the hallway track. I'm trying to convince the bosses that we have a stunning candidate who wants to join me and increase the size of my Samba team and it'll be a lot easier with a name to point to. But Catalyst has been a really fun place to work for me for the last 18 months. They brought me over to Wellington to work on Samba and I would very much encourage the smart folks in this room that are looking for somewhere else to be that Catalyst might be somewhere you should think about joining. Okay, any questions? Hi, I have a whole bunch of questions. Oh, please. First of all, what was the history behind the earlier fork of Samba? Why was that happening? Why did Samba forked for the first place? So Samba 4 took off after the Samba 3.0 series. Sorry, I was referring to the original fork that was the TNG, that's right. Why did Samba TNG? Most of that history is before me and I won't really try to go into that. That was before I joined the team. But Samba 4 forked off for reasons that were relatively similar and that conservative versus progressive stuff was a bit of it for Samba 4. The file server area was getting very conservative and very resistant to change. And at that time, we thought we were building the next version of Samba. But we bit off far more than we could chew. Far more was rewritten rather than doing incremental rewrite and get it ready for release. It just kept on going as to new and fun stuff in an area that wasn't aimed back at releases. And then a strange thing happened. At that time, those who were working in Samba 4.0 were the only developers working. But one developer who had a lot of free time from the way his company had restructured was able to, he just decided to go fix some fixings in Samba 3.0 and he really got some momentum going on there. So suddenly we had two branches with momentum and that then meant there wasn't any clear pattern for where either was going. And it was just very poorly managed in hindsight by the team. We didn't really know what we were getting ourselves into. You know, we were in Dunedin and doing a first demonstration of Active Directory DC. We thought we'd be finished on that shortly after that. You know, we thought it was. And so there were lots of, but that's how Samba 3.0, 4.0, 4.0. But the 10G ones, a story for a different day. A smaller audience. This is a question. I don't want to hold the microphone if somebody else wants to ask a question. This is a question more related to the community aspect of things and you might not have an answer. But as a Samba user and systems administrator, it can be a little frustrating getting information. The wiki is good for what it covers generally, but some parts are a little out of date and it tends to be IRC or the mailing lists that have the best, most responsive place to go. It seems unusual that forums these days are normally a place to go for that kind of information, but there is no official Samba forum. Do you know if there's... Indeed, there isn't. The same team is really quite conservative, in many ways. And most of us as developers just are not interested in trying to run a forum. We work on mail. We're used to dealing with mail, you know, all these modern social networking things. We have our instant chat on IRC, we have email. It fulfills our basic needs. So really it's a developer conservative thing, so we didn't want to set up a forum where none of us would be there. So you can use... There are online interfaces that make our mailing lists look like a forum if you really need a web forum kind of look to it, but that's why we don't have a forum. My final question was related to the file server inside the early versions of SAM before. Could you elaborate on what features that would have been... Yeah, so the file server that was in early SAM before, we now call the NTVFS file server, and it was structured where the SMBD has a VFS layer that most closely resembles POSIX with a boatload of extensions on it for the things that POSIX can't do and where we've... And so it's a mix of POSIX and then some NT semantics where you can't represent them by POSIX. I should clarify, when you open a file in Windows, in Unix, you've got open, you've got three arguments, right? You know, the file name, the mode, and I think something else, you know, it's really simple. On Windows, you've got about 26, and so there are a lot more semantics that you're passing inside that open call, and they have to be atomically operated on in that open. So you get share modes, which are a way of saying no one else can touch this file, absolutely. You can set ACLs if you're getting a new file. You set what access bits you want. All manner of things can be done in that one call. So that all that gets put into and passed down to the VFS. So the Samba 3 layer tries to be like POSIX, but with these weird exceptions, a bit of a dog's breakfast, but it's relatively simple to understand because you've got open, closed, read, write, and a few odd ones. Samba 4 tried to say, well, we know that our protocol is really a thin shim on top of NTFS. So why don't we actually provide a protocol layer that with a full richness of the network protocol is passed all the way down to the module to deal with and so that we can implement, for example, a full SIFS proxy, and we have one, that takes every packet and maps it all the way down to C structures and sends it back out the other side. This should allow a file system module to implement the full semantics of NT if it's got a richer file system that can do special things because it can see the whole request, not a dumbed-down version of the request. And so it's a really good architecture for designing how Samba could be done. It was what was essentially how likewise, which was a competing S&B server, got implemented. But because so much was written from scratch and there were a lot of VFS modules that S&BD had, there wasn't, everyone said, oh, you'll never finish it because you'll need all the VFS modules that exist will have to be ported in all manner of other things. I actually wish I'd glued the two together. I reckon we could have had one on top of the other. But we, yes, that was the difference. A real different architecture. One of, we'll try to be posix plus extensions. The other try to be windows in, the windows full richness built as the layers. And so that was the difference between the two servers. And one was rewritten from scratch and one was the old one, been with a lot of really good refactoring over time. And the S&B2 file server was first built in Samba 4, but then that work was done in the Samba 3 stuff. So yeah, and sadly just didn't continue. I think it's a great architecture, but it's not anyone maintaining it. It's not got, it's mostly a nice model for where we might go in the future. So there's no plans for it to make its way eventually into? No, it remains basically a developer reference for how we could have built something. And the SIFS Proxy is really interesting because it's the only SIFS Proxy that I'm aware of. But it doesn't do S&B2 really well. It doesn't do S&B3. It's just a snapshot as it was seven years ago really when we moved from doing file server development to doing AD development. There's a great talk if you wanna understand about it all the way back in Perth, which which talks about a new VFS for Samba. And that was a long time ago, but that's when this design was first being put together and explains why we're trying to do it. So yeah, other questions? I'm more the user sort of things wanting to know how to learn more about the inner workings of Samba. Because sort of interfacing with Samba and I keep bumping across it just not working. So how do, what's the best way to learn more to try and be able to fix the problems myself with it? Turn up the debug level and just start diving around the code that's related. It's a big and difficult project to get into but that's where I'd start is just crank up the debug and just try and understand what it's doing. I don't have much more I can really suggest to a short question and answer like this. Catch me in the hallway track and tell me a bit more about what you're trying to do. Okay. One question back. My question is regarding with the Samba for trust if there's any updates on because... So trust support from is something we are working on. We have had some parts of it actually for some time but we haven't advertised it because we knew it wasn't finished. Stephen Metzmarker has just demonstrated doing an Interforest Trust between Samba and Free IPA and we thought that's really interesting because let's do some really interesting bridge work between the Unix and Windows worlds and those leading sort of servers in each of those markets. So we did a lot of work to use the Samba 3 windbind as being the only windbind going forward and the reason we did it was so that we could get further on trusts. We haven't really enabled any of the other features but we got it. We did that work because we knew that was going to be that was the blocker for doing trusts. So nothing's official. Nothing will be in Samba 4-2 yet but some slow progress is being made. There's a surprising amount of it working under the hood but we haven't been willing to start telling people it's there until we finish some things but it's not like there's no code and no hope. It's more that we know there's still more to do. So maybe you'll see it in 4-3. Best way to do it is to step up and help us work on the development. That's, you know, there's lots of stuff. Sammy's hard to start on but the only way we're going to get forward is if we get more developers interested in things and I'm very happy to help new developers get up to speed. Any other questions? He said, oh, in an hour and a half. One last question before we go. Are you aware of any NAS vendors or distributions that are working on getting Samba 4 into their products? Well, Samba 4 is in many products but as the Samba 4.0 file server and the 4.1 file server. In terms of, if you ask them about the Active Directory DC, I'm not aware of... FreeNAS, I think, was looked at at one point but, you know, there's... I'm not aware of any, you know, physical buyer box vendors doing it that way. You're better to install it on a generic distribution. Anyway, thank you. Thank you, Andrew. So next up, we have got Angus Lee's talking about getting the Rust programming language or bootstrapping a new language into Debian. So there'll be a slight pause as you get things set up.


Hello everybody, welcome to my channel. It's Eva from Bohemian Crafting here. I would like to welcome you in my new craft room in my new studio. I have spent last few weeks with cleaning my studio. While creating my journals, I made a huge mess all around and as this is also my bedroom, it was very important to tidy up my mess. I started to feel like I'm losing my mojo, but it wasn't losing my mojo. I was disgusted by my room. I will put here a few pictures so you can imagine what I have created, how messy I started to be and why I went through to all that change. I felt terrible, like really terrible. What have I did with my room and with no, with my room.  I kind of took few not good habits which are not healthy and they are not rising my creativity. I started many, many different projects which I didn't finish.  So I had to change it. I spent few weeks with that work, a few times I felt like I'm gonna cry. I regretted few times that why, why I, not just that starting, that starting was good that I already started. I regretted what I did before. So I'm gonna show you very quickly what I've got here as my room. I'm not gonna go through all these boxes because it's actually just papercraft. It's papers over there. There is my bed behind my table. So there are boxes with papers. Here are boxes with craft supplies like metal embellishments, stickers. I don't know what is there, frames, molds, labels, etiquettes, butterflies, all kind of glitters here, all kind of that embellishment. Here mostly in these drawers, in these drawers I've got metal things like closures and stuff like that. Underneath I've got three drawers with unfinished projects. Behind me in those boxes and drawers are papers, fabrics, stumps and thighs. Here behind me in that beautiful bookcase I've got papers six by six on the top, then my own papers designs and then on the bottom I've got 12 by 12 and here in that pigeonhole I've got cards and small yeah also colors and sharpies and stuff like that that I've got more for decorating my room. You've got these pictures and there is end of my room and my board. I have created for this room here behind me I've got still two boxes which I can't even fit in here. My room is overloaded, overloaded with stuff and I have to start to do something with this. Always when I watch some video and I see something new I was like oh I have to have it, oh I have to have it. It was really bad. If you do have same habits like I did and if you're a room start to be overloaded, maybe it's time that you will jump in it and do same what I did go through every single paper, every single piece, every single die and start to sort it out and then start to use it. I forgot to use my craft supplies. I always bought new supplies and now I don't know where to place it. Those two boxes and this is just serrally boxes for my for my journals but those two boxes which I don't know where to place them that's huge red flag for me that stop buying and start to use everything I've got. So this is my new craft room. If you feel same like I felt if you think that you are losing your mojo or you don't want a craft for some reason and you don't you are not sure which is that reason maybe maybe you need to be organized maybe you need changed colors. It's actually helped to me to change my room to gray and pink. I think these colors will kind of motivate me to keep this this room clean because these colors are more not sure how to call that and not like posh not not like posh but more for clean spaces I think. So hopefully these colors will motivate me to clean after every single creating season or session session is that right word so hopefully that will motivate me tidy up Evie otherwise you will end up in huge mess again. I'm happy I did it even it was very hard work it was very painful to see what I did and I felt how it did that right word when you feel I felt awkward for myself what I have became so if you do have same problem stay strong and jump in it. I know it it's hard work I know it's scary to go all that stuff through to all that stuff and maybe you will regret it a few times that that can happen but in the end I'm so happy I did it I am I can't explain express how much happy I am I did it because now I feel like a human in my room like I am creative but I'm human I'm not messy I'm not not if I will say pig I will hood to that animal that I feel normal in this room I know I've got still huge stuff but it's clean it's smell fresh it's it's nice to have a look so go for it I know it's scary and I know it needs few maybe few days maybe few weeks to to what is that right word to prepare yourself for that hard work but go for it you will don't regret it in the end you will be happy and if you do have a problem like I had that you think that you are maybe losing your mojo in the end you will feel amazing you will feel I want to actually create something finally again so thank you so much for jumping in and I hope we will create together something nice


All right, so now what we're going to do is you've seen all the basics, you've seen the kinds of floors, you've kind of understood how to improve the quality of Maida by adding gluten, vital weight gluten, what salt does, what sugar does, what milk and yogurt and fats do in the context of making a dough. So now let's kind of understand in what situation do you use what. So let's start with, let's start with Maida. Let's assume you have Maida and you added salt, which is one or two percent salt, and you've added yeast or so you worked in the, you've added the powdered yeast into the, into the. Right. So this is, so this is where you are right now. So now, if you add 65% water. Okay. 65% of the weight of Maida, that much amount of water, right. You have a dough that is ready for focaccia, ciabatta, pizza and things like that. Right. Now, some qualifications here. So the assumption here, so you're going to add the water, you're going to need it and you're going to let it rise till it doubles. And then you're going to deflate it and then stretch it into whatever shape you want focaccia is a flat ciabatta is like a very rough looking bread loaf pizzas again flat. So it's just, you know, there's just some standard shapes into which you, so beyond the adding the water, letting it rise, then you need to shape it. And after you shape it, you're going to have to let it rise for a second time so that you know that the yeast is still alive and you know you can get the right shape you want. Then about half an hour later, you're going to put it in the oven. So that's the general workflow. So that's implicit in any one of these things. So Maida salt is 65% water, you can make focaccia, ciabatta, pizza, any of these things, right. If you add semolina to this, while you're doing this water, you also add a little bit of maybe a teaspoon or tablespoon of semolina, which is the rubber. That's the dough you can use for batura. Now, incidentally, you can make batura with baking soda which is usually what restaurants use because nobody's spending two hours trying to use yeast and make it rise and all of that they use baking soda. So that's essentially how restaurants do it. But batura made with yeast, as it's traditionally used to be made before baking soda came along, is tremendously way more delicious than batura made with baking soda. A ton more flavor. So the semolina here actually plays a very interesting role. So what's semolina? The semolina, if you notice, is sort of very tiny, very dry, has very little moisture inside it, right. So what happens is that the dough is wet, the semolina mixed into that is still reasonably dry inside. And it's only at a high enough temperature that the moisture inside the semolina is going to turn into vapor at which point it will expand.  Because you want the semolina to give up its water only when you're deep frying, at which point the water vapor then fills up so you get an absolute guarantee puffing up. So if you're worried about puris never puffing up, adding a little bit of semolina to the dough is how you achieve that. So this is how you make batura. Now let's switch to another kind. So let's say you use only 50% water but use 15% yogurt. We spoke about how yogurt also is mostly water. So if you use this kind still gets to about 65% hydration but 50% water, 15% yogurt. You can actually make naan, kulcha, kamiri rogi. This is the dough that is typically used, right. The yogurt adds a little bit of sourness, it adds a little bit of softness and so on. And again, if you're using yogurt and sometimes if you don't want to use yeast, you can simply use baking soda and which is how restaurants make naan and so on. Which is mostly just, it's not as airy if you notice, right. It's more chewy rather than a genuinely fluffy yeast based naan which is strangely enough not as common in India but pretty common say in the northwest part of say Pakistan or in United Kingdom and in the US where they tend to prefer not the chewy kind of naans but really the fluffy yeasted kind of naans, right. So this is how you make naans and so on. The distinction between kulcha, naans, et cetera is very, very tiny, it may have to do with slightly less water. Naans can have a little bit more enrichment in terms of sometimes you might add oil and all that. Bear in mind, none of this is actually meant to give you some kind of notion of authentic recipe. This is meant to be a cheat sheet for you so you can get started and with just one set of standard set of heuristics you can make like 15 different kinds of bread, right. Obviously then you can do your own research, add more things and do all of that but this is just a starting point, right. So this is, you can make naan, kulcha, kabir, et cetera, right. If you have a dough that's made from 40% water, 25% milk and butter, right. So you add like 10% additional butter also. This is the dough that you can make any kind of general purpose bread like pao, you know pao bhaji, pao, milk bread or buns like burger buns and so on, right. So it has a buttery taste and it has a little bit, it's a little bit sweet because of all the milk sugars and it is also super, super soft, right. Because of all the butter, because of all the fats, right. So this is, so these are in some sense, you know, rather than search for like a million recipes, just remember these things. Roughly you're aiming for between 60 to 65% water, right. Either it's just water or it's a mix of water and yogurt or it's a mix of water, milk, butter and things like that, right. And based on what you do, you could make pao milk bread. The rest of it is that you let the dough rise, you really need it well, you let it rise and then after that you shape it into whatever you want. So if you're making pao, it means that you've got to use a dough cutter and cut it into small pieces like 30 or 40 grams and then sort of, you know, shape it into small balls and let it rise again so that then you bake it. So that's how you get pao. It's one, so maybe I'll link to some videos of me making pao so you can get a sense of this, right. So this is the whole Maida 11 breads algorithm, right. Now, let's say you are actually, you don't want yeast, right. So you just want to make unleavened breads, right. So just you just Maida salt. If you add 55% water, salt, semolina, sugar, and work in 10% oil, right into the dough, oil into the dough, right. You get a dough that's perfect for some, what Bengali is called Luchi, which is, which is this Maida based puri, which is flaky, really, really soft and perfect as a breakfast with, you know, aloo sabji and so on. Fantastic dish in the streets of Calcutta, right. Now, instead of oil, if you add 10% butter, you get a dough that is perfect for parotta, your Malabar parotta. Now, how you make a parotta is something so, you know, so my subsequent mint column will have a instructions on actually how to do this. So, so you need to roll it out and cut it into small strips, apply butter on it, you know, then assemble it all and then roll it very gently and then make the Malabar parotta. So, so, but then this is how this is the dough that you need to make, right. Again, same thing, the semolina adds that crispness.  Now, the last one is obviously if you have atta, right. So atta, please do not bake with atta. It's a terrible, but if you're, you know, if you're like super health conscious and you're someone who bakes daily. Yeah, then you can mix, you know, 30% atta and 70% mitre. Anything more than that will be, will result in very sad and disappointing bread. So in your general dough, don't use more than 30% atta if you're actually baking. But if you're making parotta or roti, you know, this is exactly what you use. So atta is a slightly thirstier flow. So a thirstier flow essentially needs more water, right. So it needs between 80 to 100% water depending on how comfortable you are and what brand of atta it is, how much fibrous it is. So that's why I said I can't give you a perfect number, but anyway between 80 to 100 is and by weight, right. So please don't put two cups of atta and two cups of water, you'll end with slush. Okay. It's a cup of water weighs twice as much as a cup of atta. So two cups of atta to one cup of water is general rule of thumb. But if you do it by weight, you'll find that it's about, you know, double. So that's the general idea of how you measure for water, right. And if you're using a very, very organic high fiber variety and so on, it's going to need more water. If you use a slightly cheaper, more mass market one if you need a little bit less water. And by the way, you'll also need less water depending on the humidity in your house that time at that point of time, and also how old the floor is and so on. So a ton of other things that factor that go into but trust your feel, it should feel like a pliable smooth dough. So that's the general idea. So this is how you make chapatis with this, right. Now bear in mind that there are many ways to make a chapati soft. And it's also there's also personal taste. For example, I like my chapati slightly chewier, not like ultra flaky and thin. So it varies, right. So if you want ultra flaky like break apart in your hands, kind of texture, then you use hot water as opposed to regular room temperature. What hot water will do it will cook the starches, some of the starches, it will gelatinize the starches that then gives you an ultra flaky soft texture as well. So, so this is, so this is that right. If you're how you use 80% water and use some oil, right, so you get what's called a paratha so it can vary between 60 to 80% you get a paratha dough. It needs to be slightly harder than chapati. And so this is what you make parathas with, not parota paratha. And then if you use 55% water and a lot more oil, you get puri very similar to luchi except without. And by the way, also I forgot about it you might want to add a little bit of semolina here. I think it will definitely improve the puffability of your cooking and so on. So this is the general purpose algorithm for really being able to bake any kind of thing. Now, so let's kind of summarize the broad principles before we get into Q&A. So let me summarize all the principles here. So first thing is, flour. Flour is bread flour is best. If you don't want to spend 450 rupees kg for bread flour, please use Maida plus vital wheat gluten. Ata is the worst for baking. So if you're using Ata use 30% Ata, 70% Maida of some kind. So that's that's the general principles around flour. Hydration. So general rule of thumb, more water, better bread. Because the idea is that anyway in the oven at 200 Celsius all the water is going to boil off anyway. So you just need enough to be able to have enough water there so that the bread gets brown and the insides are still soft. You don't want the insides to get rock hard while the outside is still not brown. As I said, you can replace or enrich water with milk yogurt for softer breads and so on. By the way, you can mix and match. So nothing stopping you from making none with milk or none with yogurt or anything else. Or a paratha with yogurt. It's not uncommon for people to use yogurt in their paratha dough as well. So next thing is obviously yeast. If you're using industrial yeast, that's fast. If you're using a sourdough starter, it's going to be slow. And sourdough based doughs are better off with more water. They are tremendously painful to handle. So you might want to get used to that. So the other important thing is that as you are kneading, you will find that it's quite frustrating. It's sticky and it's not coming together and so on. When it's not coming together, when in doubt, just give it a break. So the single biggest magic when it comes to baking, the most amazing help you have out there is time. Time improves flavor, time improves gluten structures. You don't have to do anything. Let time do all the work for you. So resting the dough is absolutely useful. So you're trying to knead it, start coming to leave it for 15 minutes to 30 minutes. Come back, cover it, come back and then knead again, you will find that it really just works much better. Likewise, fermentation also, the longer you ferment, the better. So we'll talk about that. Kneading. So if you're dealing with very, very wet doughs, it's generally better to let it rest. So autoless is in the sense that you just let the dough rest with water and flour and you just gently stretch and fold many times over several hours. You can do this at room temperature or then you do it at room temperature, put it in the fridge, then bring it back and do it depending on how hot it is. Or if you want to hand knead, knock yourself out, great exercise, 15 to 30 minutes to get it. In my experience, if you're using bread flour, the kneading time is significantly reduced. If you're using Maida, you're going to need quite a lot to develop that amount of gluten, given that it has less protein. But if you're using machine, like a dough maker or a food processor attachment, or a dough hook and so on, or a stand mixer, if you're really portioned and so on, you don't overdo it, don't do it for more than 10 minutes, then do the final stage by hand because you have to run the risk of overworking and over kneading the gluten. So that's it as well. The next rule to keep in mind is that the slower and longer the fermentation, the better. This is often a problem in hot places like Chennai where the fermentation is so fast that it doubles. So the yeast has not had enough time to build a lot more complex flavor. So often what we would do is just refrigerate it. So seal the dough properly, put it in that glass vessel, refrigerate it. Eight hours later, the dough will still rise at that temperature you have in the fridge, but it will do it very slowly. That way you develop a lot more complex flavor. In fact, if you're making pizzas, it's not uncommon for you to just make a very, very wet and sticky dough. Don't need to do nothing, just shove it in the fridge, let it sit for 48 hours. And then you'll get amazing pizza. All the gluten development will happen inside. And then so that's basically the thing. So the longer, slower, longer better flavor. You can do this for naan too actually. So if you make the dough today, refrigerate it and let it rise and then make the naan tomorrow, it'll be much, much more tasty as well. Now, coming to the principles of rising, focus on volume, not time. So the first rise is to aerate the dough. So the yeast will produce the carbon dioxide, the dough will get fluffy and so on. And then you have to deflate it. When you're deflating it, you're only deflating the large air bubbles. The dough is still aerated for most part. And then you shape it, after you deflate it, you shape it into the shape you want. Now, let's really go through it. If you're trying to make a focaccia bread, you don't have to do anything, no shaping. All you have to do is deflate after the first rise, stretch it on this big flat pan and let it sit for 30 minutes. Then poke some holes, pour some olive oil or flavored olive oil on top and bake for 30 minutes at the highest temperature you have. And you're good to go. If you're making a loaf of bread, in which case then you need to shape, you can fold it. You can look at YouTube videos on how to fold a dough so that it forms the shape of a bread loaf. And again, you'll have to make sure that you have the right size. So which is why precision is important largely again only because you have this, a loaf will hold dough of a certain dimension and size. So if you're buying a 8 into 5 kind of loaf, you need to know that you need about 500 to 800 grams of dough. It's appropriately 500 grams of water, 500 grams of flour and 300 grams of water and so on. So you need to understand based on what kind of... But if you're not making like sandwich loaf, you're just making these very misshapen, broadly loose just focaccia, ciabatta type breads, then you don't need to worry. You just make whatever you want. So then it comes to enrichment, right? So if you want your bread to taste to be flaky and soft, you need fats, you add fats. How much you'll kind of figure out, 10% is a good starting point, but you'll figure it out. Then you can also use hot water and gelatinize the starch so that you get a soft and fluffy texture. If you don't want to use hot water directly into the dough because it makes it hard to knead, you can take a little bit of flour and heat it in water so that it forms a roux where the starch gelatinizes, it becomes the sticky thing, then you add that back. So that's one way of adding this as well. There are a couple of other things which I didn't want to spend too much time on. There are other add-ons like diastatic malt powder, which is basically made from sprouted grains. So it has the digestive enzyme called amylase. So amylase is the enzyme that breaks down amylose, which is the starch. So diastatic malt powder, what it does is that it really accelerates yeast activity because the amylase will break down the starches into sugar so that yeast can act much faster. So faster, stronger rice essentially means you'll get better browning when you're actually putting the bread in the oven. So professional bakers will use diastatic malt powder. In fact, if you've seen bagels, not very common in India, but at least you get that even golden brown color that's completely smooth. They do that by adding diastatic malt powder to the dough. So that's essentially a couple of other things that you can keep in mind and shaping. So the most frustrating thing for any beginner baker is dealing with the dough and shaping the dough if it's ultra sticky. Rather counterintuitively, the wetter your hands are, it will prevent stickiness. You remember the principle of how gluten works. All the water-loving parts are inside, the water-hating parts of gluten are actually on the outside. So if your hands are mildly wet, the dough is less likely to stick to your hand, which seems counterintuitive. So you just dip your fingers in a little bit of water when you work the dough so that it's easier. But if you press it too hard, then you're introducing more water into the dough. If you're gently folding, it's better for your hands to be slightly wet. So avoid using extra flour. In the beginning, it will be tempted to use flour for dusting. All this raw flour is going to burn in the oven.  So the lesser dusting flour you use, the better and you'll get better with practice. And don't worry about shape, misshapen breads are equally delicious. Your most misshapen bread will still be tastier than the fanciest looking industrial dough from a shop. We spoke about the differences between air fry and OTG convection oven. They're all operating on the same principle. Air fry is really small. OTG is slightly bigger and convection is the larger one. So if you want even browning, before you put it in the oven, it's common to either apply some milk on top of the bread because the milk, again, because it has proteins and sugars will add to the Maillard reaction when the oven is baking. So you'll get a nice even brown color. Otherwise, you'll only get brown where there are more sugars and proteins on the surface. So this allows you to do that. You can also do this with egg, to just add some egg wash. Break open an egg and just apply it on top. You get a very glaze, you get that very shiny surface. You get that with an egg wash. So this is before you put the bread in the oven. When you're baking, trust your nose and eyes and nose, not the amount of time and the temperature that is given in the recipe. You'll know when the bread is done. It will look brown enough. And remember that don't get, especially when you're baking like loaves of bread, the outer crust can get pretty, pretty dark. Don't worry about it. If you kind of stop when it's still very light brown, inside won't be cooked. And you'll figure it out. And not only that, other thing is that if you spray a little bit of water or keep a small little tray of water in your oven, that will improve the rice. Again, simply because what happens is that what's happening is that the dough is rising a little bit in the oven as temperatures are getting really, really hot. But the outer surface is getting assaulted by a high temperature air. So it's going to dehydrate and lose water. At some point of time, the outer crust is not going to be elastic anymore. So at that point, no further air can expand because it's not elastic anymore. So what steam does is that the steam keeps the outer surface wet for long enough so that all the air can expand inside and achieve its full potential for the largest loaf you can bake before all the water boils off and then it becomes really perfectly proper. So some steam ovens naturally have a steam setting but you can just spray some water inside and so on. So this is what it is. And then last but not the least, please wait for the bread to reach room temperature before digging in. So otherwise, it will be uncooked. And so you want to wait for that to finish. So with that, let's do Q&A. So go bake some delicious bread and please pre-order my book on Amazon. Thank you.


The year is 2020 and our world has been changed by the coronavirus pandemic code named COVID-19. Situations and events have emerged which, until now, were only imaginable in a Hollywood script. According to the United Nations, COVID-19 is the defining global health crisis of our time and the greatest challenge we've faced since World War II. I'd like to acknowledge that COVID is a challenging time for everybody and it's a shared experience. The impact of COVID is without precedent in our lifetimes. Nothing and nobody has been spared. Every country, economy, business, household and individual has been disrupted in some way. In a matter of months, it is like a tsunami has rolled in and washed away many lives and livelihoods.  According to the Harvard Business Review, globally speaking, more than 1.6 billion students have been impacted. This represents around 91% of all students in the world. University campuses have closed their doors. Students are attending lectures and classes virtually. And office workers have been told to work and learn remotely from home. This image depicts a traditional classroom in around the 1850s. It was a byproduct of the Industrial Revolution. Do you think this kind of classroom still exists today? Well, in some respects it does. The school oftentimes is a physical environment. Students are taught in large batches. Classrooms are organized in lines and rows and curricular standardized. So this old school model is somewhat akin to a mass production line in a factory. And now, with the arrival of COVID and social distancing measures, the old school method has been disrupted. Many believe COVID represents a major challenge for education. This is true. However, I also see an opportunity for a paradigm shift which empowers us to rethink the way we learn and work. It's taken a global pandemic to get us thinking differently about education. If it's OK with you, I'd like to talk about some positives. I think it's fair to say that COVID has improved our overall sense of community, collaboration and cooperation. Think to yourself for a moment what perhaps have been some of the benefits of COVID. If any at all, perhaps type those in the chat area there. There's quite possibly things like working from home, remote learning, greater flexibility, less commuting, meaning less emissions. So the environment wins. And overall, an improved work-study life balance that may result in less stress. Again, some of these things may be perceived benefits. So with all this disruption to the traditional education system, how do we as educators continue to deliver quality education? I'd like to bring your attention to the United Nations Sustainable Development Goals. And goal number four in particular is about quality education. On the same token, Moodle's mission is to empower educators to improve our world. So as Moodle educators, what can we learn from COVID that will enable us to continue delivering quality education? I believe there are seven key pillars which form the foundation of quality education. Whether that be face-to-face, blended or online, this is my model. Resources, communication, collaboration, assessment, accreditation, reporting and accessibility. So in line with those seven pillars, what I've done is handpicked seven tools to help us facilitate remote learning with Moodle. So in essence, it's one tool per pillar. So look at the list of tools there. Which of those tools are you most using at the moment? All right, let's start with pillar one. It's resources. And the chosen tool happens to be H5P. Now, here's just a snippet of some of the many content types that are available through H5P. It's the new kit on the block, and incidentally, it's an open-source content creation tool. The good news for us as educators is that it's super easy to use. And our learners win as well because it's very interactive and engaging. Oftentimes, people ask me if they were to learn just one of these H5P content types, which one provides the best return on investment. Well, I'd recommend you check out the interactive video. So H5P has been part of Moodle since 3.8. And in fact, with 3.9, the integration is even deeper. You can see here, this is Moodle version 3.9's activity chooser. You would select H5P, give the activity name and an optional description. And you can drag and drop or go about uploading a pre-created H5P learning object. Optionally, you can see at the bottom there I've highlighted, you could go to the course Content Bank. This is new for Moodle 3.9 as well. So you could stockpile H5P objects in your Content Bank. And all, you could come to this page and create one on the fly. So you add, click the Add button and then you select one of the H5P content types and you create it directly inside of Moodle as an activity. Now another way you can go, again with pre-created H5P content, is via the HTML Editor within Moodle, the Ato Editor. So anywhere you see that H5P icon, click it. And then you're able to either link to an existing H5P object or upload one. And then in essence, you're inserting it within perhaps a page or a book or a discussion forum. So on and so forth. A quiz, a lesson. Pillar 2 is communication and the tool is a forum. For centuries, the forum was the centre of daily life in ancient Rome. The site of processions, elections, public speeches, criminal trials, commercial fares and even gladiatorial matches. Likewise, and more recently in Moodle, the forum is an essential place. It's perfect for remote learners because they will be able to ask questions, get answers, share ideas and help others. I don't know if you've ever noticed this, but every new Moodle course automatically gets one activity. And it happens to be a forum. So I think Moodle is trying to tell us something here. The standard forum for general use is very much the Swiss Army Knife of Discussion Forums. It's multi-purpose. I would encourage you to also check out some of the other forum types and see if they are fit for purpose. Pillar 3's collaboration and the chosen tool is web conferencing. Here we are today, web conferencing connecting globally via a wonderful tool. It's all about human connection. And it's even more important in times such as these during isolation. So typically web conferencing tools allow us to share certain things, naturally voice, video, screen and files. Invariably there's also the option to chat, poll and some of the tools have breakout rooms and the option to record the session. So which web conferencing tool are you mostly using? Some of you may be using more than one tool. Some may be very new to this. So perhaps Big Blue buttons your conferencing tool of choice. Or is it Teams, Zoom, Adobe Connect or perhaps another. The good news is Moodle has plugins for many of the popular web conferencing tools. Zoom and Teams for example are app based. They do require a subscription. As far as Big Blue button goes, it's not app driven but rather it's accessed like we are today via a web browser. And in terms of setup, you will or your organization will require a web server to get this running. So that's the key point of difference there. In terms of look and feel, this is Big Blue button. We're using it today. You've got a screen grab there. This is Teams from Microsoft. The integration is quite deep with Outlook and Calendar, SharePoint and other applications as part of the Microsoft 365 suite. And all of these conferencing tools incidentally work across desktop, tablet and mobile. We've got Zoom. Zoom is also pet friendly apparently. The pillar four is assessment and the tool I've chosen is the workshop. Workshop is a wonderful peer assessment activity which fosters a sense of cooperation and interdependence. And these are things that really need to come to the fore in our current state, global state. How it works is this. Learners submit their work. They can receive submissions from their peers, which they assess according to a marking guide or rubric, which is likely put together by the teacher or trainer. And as you can see here, there are five phases to the workshop. We've got setup, submission, assessment, grading evaluation and close. And it's up to the teacher if they can predetermine the date and time that the respective phases open and close, or optionally they can come in and manually trigger the open and close of the respective phases. But the idea of a workshop is very stepwise and very sequential. This is a teacher trainer's view of the workshop grades and we can see who has submitted work, who has received grades, who has given grades. Pillar 5 is accreditation and the tool is badges. I ask you this, how do you recognize and reward learner achievement? Badges are a super simple way to incentivize our learners. When learners are motivated, they feel a stronger sense of purpose toward achieving a goal, whether that be completing a Moodle course or an activity within it. So here's a badge that was created earlier. It contains a pretty image. The badge has a name, a description and then a criteria or a set of conditions that must be achieved by the learner to be issued with the badge. When the badges are earned, they embed themselves on the user's profile and then the learner has the option to synchronize the badges to a backpack such as Badger. Because in reality, learners may be attaining badges from various sites and services. So Badger acts as a single repository to store the badges and then perhaps show them off to peers, potential employers that helps people land jobs and earn promotions. And in general, just show their level of knowledge, skill, capability and competence. Pillar 6 is reporting and the chosen tool is learning analytics. Learning analytics helps educators make informed decisions about learning and learners. With remote learning, this is especially important for educators because we need to know whether or not our learners are engaged. In a physical learning environment, that's a little easier to do. Learners are present, they're attending, they're turning up to class or lecture or the workplace. They are performing tasks, they are participating. In a remote environment, that's not so easy to identify. So the idea with learning analytics is learners who are at risk of failure can be identified, educators get notified and that enables them to intervene in a timely manner. And in the first instance, the intervention may be something as simple as a direct message via the Moodle platform. If we drill in a bit deeper here to one of these students who is at risk of dropping out, we can see that the prediction was made via Moodle's inbuilt predictive model. So this is AI and I guess the early stages of machine learning. And the flags are the indicators that allowed the predictive model to be triggered. So we can see the course has not been accessed at any stage nor has the learner written or read to the said course. Pillar 7 is accessibility and the tool is the mobile app. I don't know if you're aware 80% of global internet use is mobile. And with the recent spike in remote learning, it can be predicted many, many more learners will be accessing Moodle via mobile and tablet as opposed to desktop or laptop. The app gives learners the freedom and flexibility to learn anywhere at any time without being bound to a classroom or an office. And here we can see the Moodle mobile app. It's freely available for download from the various stores. We've got three screenshots here of a mobile in portrait mode. And you can see that the app is modern, clean and simply beautiful. Right, so here are your seven imperatives. Go and create a H5P activity. Initiate a discussion forum. And if you're using forums already, perhaps try a different forum type. Trial a web conferencing tool. And if you're using one already, go check out another one. Facilitate a workshop activity. Set up the conditions to issue badges in your Moodle course and enable learning analytics. Download the freely available Moodle mobile app from one of the major app stores. In closing, COVID represents a major crisis for all of us. It is a shared experience. As educators, we are essential workers in the frontline. It is our duty to continue delivering quality education. The old school model has been disrupted. Are you willing to be courageous? If so, then embrace a new model of education with innovative tools such as Moodle, and you will be the hero.