All right, we're a little crazy, but it's Saturday and we've decided to come check out lumber prices We need to redo our deck in front of the house urgently And we need about 62 by 6 by 8 treated pieces of lumber deck lumber We're gonna sell kidney each pay for this And possibly Chevy we don't want to make that kind of sacrifice so kidney first Yeah, so let's go inside now. We're gonna see what their prices are at here. We have no idea what to expect I haven't looked at lumber in well so long since before all of this mess started happening There we go crazy Feel crazy Penner building center the only people open in the area on a Saturday We were gonna go to grunt all lumber, but apparently grunt all lumber closes at one o'clock on a Saturday You know the time of the time of week when everybody wants to do their rentals and stuff. That's right I'm gonna need my muzzle and say Getting very close to the point here where we're not gonna need these anymore Let me show you what we're working with And we don't really show the front of our house a lot so You guys may not even have seen this front deck the way it was before already So the owners before us what they did They built this deck on to sell the house. It was a really good feature. I I really like it. However, they did a They did a little cheap they'd used regular untreated two by fours for one and and Once they were done they painted it with deck over and This is what deck over does the very next year. This whole deck was finished last summer It's about a year a year old This is what it's looking like now. So what we're gonna do is we're gonna replace this top part with treated two by six deck lumber That's designed to be out here and then we're gonna seal it next month So it'll last a long time. I've already started taking off Some of the boards here, but it's very difficult because what they've done here you can see this What they did was they when they screwed these boards down They screwed the screws in really deep and then they filled the top with drywall mud To even it off and then painted the deck over over that for a smooth surface so it was a different way of doing a Doing a deck so Yeah, this looks pretty terrible, right? I don't want this to be the first thing people see you when they Come to visit So yeah, you're tracking in all that paint stuff too Let that be a lesson to you The deck over is terrible the same thing happened to my parents deck. They used a brown deck over It's sort of like a paint that's made for decks But It's not it's not good. It's not good quality. It always peels. The best is just to seal it So what we've gone and got now is a nice maple sealant We just got one can here for now, but we may need to go get another one a maple sealant. It's in here So it's exterior tintable wood stain with semi transparent finish Like I said, we tinted it to the color of maple Maybe because we're Canadian. I don't know maybe because we just like the color mostly because we like the color That's what we're gonna be doing out there. The wood we got is outside. I'll show it to you We got 62 by six by eights treated lumber and it cost us $1,500 Canadian which would probably be just a little over a thousand American Let's take a look This here is what? $1,500 looks like today in lumber. It's not too bad Lumber has actually come down on price by 27% since from last month So it was cheaper than it was and it's still expected to continue going down But we needed to get the project started now. So now is the time to go and buy it You know, it's been worse, but it's been a lot better to for price Hopefully we got everything we need there. We may need to go get a few more things just to finish it up I Think it's gonna be good. It's gonna be a lot bigger of a project than I thought it would be of course But that's the way it always is. That's the way it always goes At least we'll have a nice new finished deck and then my nephews from Britside are coming over Next month sometime if everything works out and and they're able to and Hopefully we're thinking that they're gonna help us stain it so we can probably get it done in a very short amount of time I was a little nervous to be honest going to the lumber store At first what we were gonna do is we were gonna use the pressure washer and blow all of that red paint stuff off of there And then restain the wood that's already there And we started realizing that more of the boards were rotten than we thought because they weren't treated They weren't made to be out in the rain For that long and it was just done a little bit cheap But hey, maybe that's all they could afford to do at least they had a nice deck, right? And it was a nice selling feature. It is really nice. We've used it quite a bit We like sitting out there first thing in the morning on the weekends having our coffee but uh, you know It just needs a little bit of an update So that's what I'm gonna be doing there We got our wood from EG Penner Which is the building supply store here in Steinback and It is a little bit expensive But again, like we were saying earlier, it's the only place that's open On Saturday and they're only open to like five o'clock. I don't understand some of the most of the stores around our area. I Understand most stores are still or a lot of stores so closed on Sundays. It's a it's a very religious faith-based area So a lot of companies don't Don't open on Sundays. I understand that part. I was raised in that as well So I understand I understand don't want to work on Sunday. Okay, I get that but why Saturday too Right like the all the other building stores around here And a lot of other businesses are closed on Saturdays Remember I went to go get a helmet from the Honda dealership in town Last Saturday or a few Saturdays ago and they were closed on Saturday. I Don't know if they closed early. I don't remember if they're closed all together only open Monday to Friday And then they're only open till six during the week So normal people who work Monday to Friday Don't have time to even get to these stores to buy anything. That's my problem. I'm like Saturdays. That's renovation day That's when people want to work on their decks when they want to work on their vehicles when they want to have fun You know, they might need the recreational vehicle tuned up or you know They're hot there their bike or their quad might need a little Apart or something so they can go have fun for the weekend But maybe something small broke. They just need to go buy a part so that they can get going No, we can't do that because on the day when we all have time to do these things The stores are all closed So we can't go and give them our money It just doesn't make sense to me Saturdays. That's the day you want to be open late. That's when everybody's gonna give you their money Right, right. Am I right? Coffee couldn't believe it. So E.G. Penner was the only place that was open We were gonna go and buy our lumber from Grunthal lumber because they have a lot better prices But hey Grunthal lumber wants to close at 1 p.m. On a Saturday when I want to go give them my money do some projects. Hey, I Guess E.G. Penner gets my money instead I'm just thinking from a straight-up business point of view here.  I have no idea. I'm talking to you right now. It's pretty cool pretty cool Congratulations on all your success. I wish you all the best Who knows maybe we're all just a bunch of employees a couple of truckers working for the big man Maybe we're between jobs right now. I don't know where you're at in your life right now We're all about right now. I'm happy with I'm happy with And we're a mat specifically right now with my coffee Exceptionally happy with things are always changing, you know things are always changing life sort of gets reassigned but Yeah, we we've invested quite a bit into this house already who installed the air conditioner top of the line air conditioner We're putting in a new deck in the front. We've put the fence around the yard We're going to be redoing the cover on that carport later this summer. Maybe in fall before winter and We'll be repainting in here and We're redoing the floors before we have our first child Which we have no news on yet. We we still have no news unfortunately for you guys. I know it's We'll get there but before we do have a first shot we want to put new flooring in here there's a couple of spots on this floor where it's coming up a little bit and It could hurt a baby crawling along it and we just want a little bit higher quality floor We also want a floor that's water resistant So that when you know spills happen You don't have to worry about you know If you forget or if you aren't able to get to wipe it up immediately Is this stuff if the floor gets wet like it's it's happened the floor gets wet and like there's a crack over here where They didn't do very good meat there and if you get water in there You have to dry it up immediately drop everything and go and dry it up immediately because If you don't it'll soak into the floor almost right away and swell up and the only way to fix that is to replace it I'm gonna go to my arm over here. That must be some some dog snot Diesel from the nose looking at that when I was holding the camera Yeah, that's what's going on around here I've changed my schedule up a little bit with my vlogs here just to make things a little bit less stressful on me There's a lot going on especially in summertime. I want to get out there and aside from you know projects like the deck and The motorcycle I want to get out there on the motorcycle this summer and enjoy it and make it worthwhile It's a little bit expensive to Register and ensure motorcycles in Manitoba compared to other places around the continent and around the country and around the US So I want to make it worth it. Okay, it's it's uh I want to make sure I get my riding in So I've changed my schedule a little bit with these vlogs You're still gonna be getting a vlog every day But I think it's going to be more consistent this way because I've been falling behind a little bit And if I didn't have time to edit Well, you guys just didn't get a video. There was no video on the internet Maybe that doesn't bother you but the consistent the lack of consistency bothers me So if I don't have time at the end of my day say I worked till 8 o'clock get home at 8 30 I don't have time to edit. So I just put my files on the computer and go to bed. Well, no video tomorrow I'm gonna adjust my schedule a little bit here so that we can have a video out at a regularly scheduled time again Maybe 4 a.m. Central time like we used to we can get it scheduled to release or maybe 10 maybe noon Maybe you can leave me some suggestions down below in the comments section there of what would be a good time To release my video. I always liked releasing it at 4 a.m. Because then it's It's available ready for everybody to watch with their coffee in the morning here in North America where the bulk of my viewers are and For people in Europe where the next big chunk of my viewers are it's ready for them when they get home from work They can sit down relax eat supper and then watch some sugar Josh Same thing with Australia too. I think Australia gets released in the middle of the night Then doesn't it or late in the evening But it's hard to make it a perfect time for everybody around the world because my my biggest chunk of viewers is here in North America The next biggest chunk is in the United Kingdom in Europe and the next biggest chunk is in Australia That is where the majority of you guys live the Anglosphere is what we'll call it the English-speaking countries Obviously because I guess I speak English so it makes sense. You can you can understand me Make sense, but there are a whole pile of you scattered throughout the rest of the world and you know I'm glad you're here as well. That's awesome. Yeah, we'll see how this works Okay, we're gonna try this for a little while and see how this works Brits is at work right now. I am at home With the commander. He's been very busy devising His latest schemes to take over the world Dude man, you got to act fast now Gotta act fast man Time's running out. I Know stressful. I get it deep breaths. That's good He's got a little bit of a wart on the top of his head there We don't touch it a little bit too old to have surgery on it now And it doesn't seem to be bothering him and it's not cancerous. So Just don't touch it we have Chevy right here and Let's rest the guys Well the other end of our massive mansion and There's a weasel. Hey diesel everybody wants a quick hello from you. Hello. Say hello Okay Hey guys perfect perfect Can't have a video without the weasel and it people get upset. I Think there's a wiener around here somewhere too. It's not me It's a little wiener.   That is my wife's dog Brits dog. She's had him since he was like since he was born pretty much And I am just I fall short from him In his eyes, I am just not the brightest crayon in the in the crayon box and He doesn't He does respect me. He listens to me. I was gonna say he doesn't respect me He does respect me. He listens well, but he gets sad when Brits not here. He's sad He goes in sulk's in his room over there. I'm special too Special too. They just all the dogs you all get more excited for mom than for me But yeah, how's it a little chat updating you on on what I've been doing here this weekend? Tomorrow I want to take the bike out for a ride We'll see if we can find the time too because I've also got projects to do I'll be riding into work every day this week. So if I don't get it out tomorrow We got all week. The weather is going to be great. It's finally summer time here in Canada We're gonna get a full three months of summer. I know I was joking around that we only get two weeks of summer I was being a little I was exaggerating a little bit for people who thought I was serious We we do have pretty good weather from about mid-May to mid-October Good weather for riding motorcycles. Maybe if you're brave, you can go a little further or start earlier, but That's riding season here from May 15th to the end of October. I think It's up to you. Sometimes we have snow by the end of October too Whoa, we have such brutal winters here that when summer comes around we like to seize it and make the most of it So another reason why I want to change the schedule up a little bit make it a little bit easier on me While still providing content for you to watch every day I'll see you tomorrow everybody. Thanks for hanging out. This is just a little chat Little hangout session Have a great weekend


Mike, for this session, but I'm Bevan Wishart. I work at Catalyst IT. I've been working there coming up on nine years at this point. So I've been doing Drupal for quite a long time. And this panel discussion today formed basically from a discussion we had in the Australian Slack channel about Drupal South.  And then you get back into the real world and you sort of get hit with a little bit of reality that sometimes these amazing tools that you sort of come out with a concept that they're magical and they're going to change your life and you'll never have a problem ever again. And it's just not the case. And it also comes up that everybody's made mistakes. Everybody has their challenges. So that's how these panel forms of the idea of doing a talk along those lines of let's be a little bit vulnerable and tell some stories effectively. So I've put together a short little introduction, presentation to get this going. And then I'll introduce the panel. So going through here, basic premise of our talk today, whether I got statistics or facts to back that up, I don't know, but it's an opinion. Drupal is the best CMS in the world, right? But it is great, but it does come with challenges and we all know that, right? There's challenges you hit with. It is awesome. The reason we're all here at the moment is for Drupal, where we're all invested in Drupal in some form or fashion. We all come in different shapes, we come in different sizes. There's different people in different roles from different backgrounds and there's amazing community around Drupal. We all know that's what we come for the technology, the software we stay for the community. And there's a real good opportunity to take advantage of that. So there's some points that back up what I just said. All right, so Dries recently gave a presentation and this graph was presented about how beginners seem to struggle with Drupal, but the experts love it. And if you look at that graph, you can see that things improve as you go on, but if you look at this blue one for clear, clarity just kind of stays a bit low all the way across the graph. So even though when you say experts love it, there's still an expression of a bit of confusion, sorry. Yeah, right, but so on that point, Drupal has a dip and it's learning curve, right? So you come into Drupal, it's a little bit exciting and then you hit some challenges and it dips.  So there's that moment of it's genesis, it's like, hey, let's get into Drupal, let's use Drupal. And then you go through an assimilation process where you really start to understand it and get a grasp of things and eventually you come outside and you've got a sense of mastery, I suppose, and you start to really enjoy the process. Now, where are we? There's, same point, even the experts experience and some challenges, so there's often decision-making processes, like when I'm building this site, what tools, what modules are not gonna use, how am I gonna form the classes, what project management style am I gonna use? So there's all these questions come up. So even the experts are having challenges and these kinds of questions, it happened from the entire stack, right, from basic how am I gonna write this class all the way through up to grand strategic ideas of how we're gonna get through that process. So before I introduce the panelists, a lot of these problems that we've got with Drupal, there are a lot of technological solutions coming through the pipeline. So in the next few years, there are gonna be technical solutions to a lot of these challenges and part of this is how do you deal with that today, right? There are solutions coming, but on a day today, when you go back to work on Monday and you're there, you're gonna face some challenges, how do you deal with that? So the panelists here today, we've got Lee Rollins, he's from previous next, I think those few would have heard of him before. I definitely have, of course, I'll speak to him on the Slack channel and OZNZ. I wanna point that out. Every single one of the panelists here is regular contributors to the Slack Australia and Z-channel. So that's their panel of the same. Drupal's strategy's open, so they've all very experienced Drupalers here. Adam, senior Drupal developer, I've worked with before, again, Slack with, chat with on Slack quite a bit and Ling who worked together a bit over the years and a bit more recently. So I've brought them all here just to sort of be able to give their insight into some of their daily challenges, mistakes they've made, how they overcame those and have a little bit of fun with this as well. So the whole point of this is a Drupal Confession Panel, so it's Confession Time. Before we run into that, I just wanna do a little bit of some values around that confession because we wanna have a little bit of structure. I don't wanna turn this into a big, big bitch-fest and pointing fingers. So first thing, I want you to tell the truth. Like, yeah, I'm gonna get some audience involvement, I'll explain how that works in a moment, but really come in and tell the truth.  I've got confidentiality, I don't know, this rule we filmed, so there's that, but I'm gonna use slide.o, which you can post anonymously, so there's a bit of confidentiality when I've got pointing fingers at who did what. Some self-responsibility, respect for people in the room that are gonna say things and come in, and by all means, have fun. That's a big part of what we're here to do today. So, for the audience participation, I've set up a Slido thing, so usually in these talks, everyone goes, can you turn your phones off? I'd ask you to get yours out, please. If you go to slide.do and enter the Drupal Confessions in that there, you can then go and put some questions in there. I'll post the questions in the prompt that's up in a moment, and then you can vote on them. We can put them to the panel. We can have the panel actually answer some of those questions themselves as well. So, to give you a bit of help, that's my favorite question, the top one, what did you do? I know I do this with people I work with sometimes, they come over and ask for help, and he's like, what did you do, right? So some of that. And we sort of have been having fun and being a bit serious. So, what are some things in Drupal at the moment or technical challenges you're having, you know, business and strategic challenges you're having as well? What's not working for you? What's the most frustrating thing you're experiencing at the moment or have done? What was the most frustrating thing you had to deal with as a Drupal user, expert developer, et cetera? And then some fine ones at the bottom. What's the silliest mistake you ever made, you know? And what misconceptions have you had? You know, I know there's times where I've been using Drupal for a long time, and then realize that I've been doing something wrong for a period of time. So, to get that started, I guess, I've got plenty of stories. I haven't even written them down because I've been toasting them up here at the moment. I did a talk a couple of years ago on configuration, whereas I was writing in the store profile and Drupal 8 was fairly new and I was getting my head around configuration. I don't know, I was doing a lot of putting stuff into the fault content and copying it around, and that was a big, like, became very unmanageable down the track of it. That same project, we also did a lot of media and video creations where I created my entities for that and then someone's gone, well, I didn't use the media module. And it's just like, yeah. It was a good point and it was too late at that point. So, and that project's still alive and we're still managing, still dealing with managing these entities I created myself. So there's a bit of confession of mine that was, in hindsight, that was the really obvious thing to not do. So there's my confession for you guys. So, if you guys can go to the slide I owe and post some questions up there. And there's some good ones here already. But while we're here, I might get the panel to, if you feel so compelled. Is that better? Yeah. I was just thinking about, actually, one of the biggest mistakes I think I still make is spending like three or four hours setting something up and then realizing after the fact that there's a control module that does it for you. And I just did that, like maybe a few months ago, with entity embed, media embed, like all the media stuff. I spent hours clicking around, trying to figure out where to go. 70 million settings, like entity browser views, all this stuff. And then I found the module that previous next did the PNX media or whatever it is. And I was like, oh my God, the whole thing could have been done by just enabling a single module.  One thing that I'm guilty of all the time is chasing a bug without updating the module first. So I'll get down a rabbit hole. I'll get down a rabbit hole, I'll open up the debugger and I'll find the bug. And I'm like, yes, I've got this. I know what this is. And then I'll go to open an issue in the queue and then I'll find that someone's already opened it. It's already fixed. And if I had it just updated to the new release, I would have fixed it. So I'm pretty guilty of that. And I think one thing that I wish I had known sooner was that you're not alone. So I'm like in regional Australia and I spent a good two and a half years, I'd say battling Drupal on my own without realizing there were all these people like you guys out here. And Syme Hobbs introduced me to IRC and like that completely changed everything. So if you're not on, if you don't use the Drupal Australia Slack channel, I think that's your homework from today. Is to join that. You have a slide for that, right, Bevan? Give a slide for it at the end. I do.  So what Bevan said about, you know, you saw these amazing things when you get to back to reality. Yeah, just trying to battle it on your own. There's a lot of ways to do things in Drupal and there's like many ways to skin a cat and sometimes the only way to learn that the way you thought was right is not right. He's like through tears, right? Through having Sam pointed out in public channels. Yeah, so like, and if you know someone who's already been through that and already got tears, that makes it a lot faster because you just like learn from their pain. So yeah, that's my, I wish I had have known that sooner. I think my biggest Drupal confession is probably I built a system for basically exporting and importing content from code. And then I left the company and realized what I built them was absolutely terrible. And now they're stuck maintaining it because I don't want to maintain it. I also did a talk on it and it was, in hindsight it was really like a proof of concept but I don't know how many sites I've got running on it now but yeah, I feel sorry for ever maintaining that now. What do I wish I did sooner? I had one but it's completely gone now. Okay, keep me coming back to it. The most thing I learned from Drupal is I have to join a community like Lisa. Sometimes years ago I just spent hours, hours and days trying to figure out one thing and if you just pop in the community, ask the question, always people help you. And the most time it's very simple. It's like sometimes ask Lee, oh, how is this not working? And he just said, did you clean the cache? I really had a piece A for piece paper that has clean the cache hanging under my wall. That's really important. Yeah, so yeah, learning from the community is very important. Something that I wish I did earlier was, and I suffered a lot from this, especially earlier in my career, was ignoring and trying to understand what Drupal is actually running on and how things actually work under the hood. The last two years I've kind of been getting more into the operations side of things and I think even having like a basic understanding of how your site's actually operating under the PHP level that you're actually writing is extremely important and has helped me architect my projects better and more efficiently and I think that's a really important thing that a lot of people sort of leave on the side. Yeah, just continuing that theme, my first experience with Drupal was Drupal 4.7 I had some requirements to build a local government site and one of my colleagues said, just use Drupal. So I installed it and created some content and saw this node slash one and I thought, well, let's have a look in the node folder and see what's in this one file. And I couldn't find it and it was a mystery and I just went, this is rubbish. And I put aside and didn't use Drupal for, oh, maybe later on in Drupal 5. So that's kind of what Adam was saying. Like, yeah, understanding what's happening under the hood is really powerful and back then I was a single, you had a PHP file for everything or a HTML file for everything and yeah, it was complete black magic and I didn't understand any of it, yeah. Okay, excellent feedback. Thank you very much. You guys have contributed. Thank you very much. We've got top voted question up here which probably question that was in the back of my mind as well but hadn't quite formulated it. So I'm glad that's up here. I'm interested in the panel, got some answers to this which is what's something you should definitely know when it just popped down by one middle, it's done. What's something you should definitely know but you're still Google for the answer. Basically everything. Yeah, what makes it worse is when you Google it and you find a blog post that you or your colleague wrote two years ago. There's a blog post that Nick wrote that I just keep coming back to every time. Like I search for like, oh yeah, that's right. See we've all been there, right? This is, we use Slack custom messages as well a lot of the time to like, you know, remember hard and long and hard to remember commands and things like that. So you can set up like, you know, Slack custom responses where you ask it a question and it will give you an answer. Oh nice. Yeah. That's really, really helpful. That's, we use that for our update Qualcommite. I was just gonna say the thing, cause I don't do it that much but every time I have to run Drupal updates I have to Google the command to run because there's just no way that I'm gonna remember that. Yeah. I mean, I think build tooling is important. Yeah, like there's so many flags to Drosh commands that you're gonna get them wrong, right? Oh there's another one, Drosh ULI for not user one. Yeah, yeah, so every time you have, yeah, you gotta have like aliases and make tasks and things like that so that, cause there's so many flags to so many of those commands you're never gonna get them right, yeah. Okay. Here's a fun one, a confession. Has anyone on the panel ever hidden an Easter egg in the site and got found out and got in trouble? No. I do mostly government sites, so no. Maybe. Easter egg is in like a terrible bug, probably, yeah. Well, one time, this isn't an Easter egg but after the first Drupalgetin, one of the devs and I were like joking cause we knew one of the sites hadn't updated and he accidentally ran the vulnerability and basically hacked their site and then he was freaking out because he was like, oh my God, are they gonna be able to figure out that way? Yeah, on the same theme, when that Drupalgetin bug came out, I knew some local businesses that I built the sites for that I knew weren't getting active support anymore because they'd moved to another provider that wasn't doing that and wasn't up to date with that bug and I actually used that exploit to patch their site cause they were a friend of mine and I didn't have access to it anymore and to leave it or not, there was talk in the community of that someone actually wrote a bot that was doing that cause there were people who were going to patch their sites and found they were already patched so a nameless Good Samaritan may have actually automated that for a lot of the sites because... That's amazing! Yeah, because the reputation or fallout for that was huge, right? So, yeah. See how we're going here with... Well, this is an interesting question I'm hesitant to ask. When was the last time you wondered why you're not just building it in WordPress? I've never installed WordPress, ever. I've opened up the wp-login.php file and saw a switch statement and got the... I've never shut a browser tab faster. If everyone's not seen wp-login.php, it's all of their login and authentication and logic intertwined with the HTML that builds the form to login. So if anyone was doing PHP in, like, 2000, like I was, that's how you built stuff with PHP. You read it all in HTML and then you had all these PHP opening tags inside your page and you probably had some code at the top of the file that if there was a form submission, you were doing processing and WordPress login is still that. There's all of the logic around their authentication and all that is just intertwined with a big switch statement inside the form that renders the login form when that just scares the crap out of me, yeah. We still have a WordPress site and for some reason, clients do have one too, especially for the conference site and the reason that we just counted that we have up to 40 WordPress sites, I talked to my manager, maybe we need to move them away to the drivel. Yeah. It's because it's just the maintenance things and updates, you have to update all each different site. Yeah. Almost, I've had very little experience with WordPress. I think around the same time I was being introduced to Drupal, a friend asked me to build a WordPress page, you know, a WordPress site and I was a little bit lost, but I quickly had someone hire me to do some Drupal stuff and funny enough, it actually seemed an easier process. I think it just made a little bit more sense. It was easy to understand what was going on for the same thing. So I haven't asked myself that question for a long time. I've been doing Drupal for a long time, so I don't know much about WordPress itself, except for little bits where it's kind of new. So the next question voted up on here that hasn't already been covered is, how do you honestly explain the upgrade from Drupal 7 to Drupal 8? It's a complete rebuild. Yeah, it's a rebuild. It's not an upgrade. Yeah. It's a completely different site. Okay. And it's necessary. And it's necessary. Yeah. Yeah, I mean, I think it's an opportunity to review your site and you know, the web is always changing and can you honestly say the site that you built five or seven or eight years ago is what you would build if you built it today? So that's the first question to ask. But in all honesty, the sites that I've gone from Drupal 7 to 8, what Adam and Pam said, they were rebuilds, but I've got a few small sites that I maintain that are getting to that point now where we're gonna have to do that upgrade. And I don't know if people are aware, but with Drupal 7 from 6, you ran update.php in Cross Your Fingers, but with Drupal 7 to 8, it uses the Migrate API. So the idea is you have one version of your site which is running Drupal 7, and then you have another version of your site, which is a Drupal 8 site, and you go to upgrade.php and you hit the button and you see what happens. And so the Migrate team have done a lot of work to make sure that there is actual migration paths for a lot of the stuff you'll find in core. Your mileage will obviously vary for Contrib, but the first step will be to run that and see how broken things are. So if you've got custom modules, you're gonna have to rewrite them. If you're on a like GovCMS style platform where you can't have custom modules, that's probably in your favor.  But the first step is to see how much stuff is broken. And if anyone's like here today, like Victoria is a Migrate maintainer, she's at the conference, she was at the Code Spring. She's actively working on a lot of that stuff and has done a huge amount of work behind the scenes where they basically take the Drupal 7 site and your fields get migrated, your content types get migrated, your views get migrated, like all the stuff that's in core, like there is a migration path for, the only things that are not working in core are the multilingual sites, which is for the IE18N module in Contrib. But they've done so much work. So I think if we talk about like, start again and that's probably good from a business point of view, but from the amount of effort that's going to that, there's a lot of functionality in there. Yeah, I think it doesn't have to be like a start from scratch. Like you can do a sort of tiered approach where you see what's broken and then I think that's a really good opportunity for clients to re-evaluate their website and really think about, okay, do we actually need this stuff and can we do it a better way and can things get consolidated to make our site easy to maintain or easy to use or whatever. So while migrating everything over might seem appealing, I think it's good to step back and think about how you can make your site just better in general. Yeah, and just to reiterate on the message that came from Bevan earlier and from Ling, is that like we're a community of people, right? And Victoria, we're lucky that she's in our time zone, she's in our community. So, you know, if you're having issues or you've done something posted in the channel, people might have already gone through that. Someone might be able to point you to something that you didn't know about. Yeah, just don't suffer in silence on your own. From the content preview, you have no choice. Can't be lazy, you can't copy one for the bunch of the old documents over to one site to another site. So it's time to clean it up from Drupal 7 to 8. You have to get rid of all the old contents and all the files and don't carry them over. You just have to do it, can't be lazy. It forces you to do it. Yeah, so, I mean, Ling speaks from experience there. They've been through this process with Charles Darwin, you know, yeah. So they had a lot of Drupal 7 sites and effectively they've brought on subsections of their Drupal 8 site and as they've done each subsection they've audited their content and thrown away the stuff that was no longer relevant or improve the stuff that could be improved. And I think that's really wise words of advice from Ling there, yeah. Okay, thank you for that. Well, while you've been talking, there's another question just shot right to the top. So, and I think this is a good question myself, which is what's one quadruple module you installed and then you regretted the decision that still causes you pain? Rabbit Hole. Which one? Rabbit Hole. Okay, yeah. That name tells you, like that. No, I just don't like it. I just wanted to say on that note and it kind of circles back to some of the stuff we were talking about before. I think as developers, like, we tend, or site builders or whatever, we tend to, you know, there's a module for that and store it and hey, it solves my issue and away we go. And that can be really good, but, you know, it's really important to start, like, getting into the habit of actually looking at what is happening in that module, looking at the code and seeing what it's actually doing, because, yeah, some things can get pretty hairy, pretty fast if you're just piling on modules after modules. For me, it would be the Node hierarchy module in Drupal 7. And if you want to know why, ask me where my DrupalCon Sydney went, where my Drupal South Melbourne went. That module caused so many issues for me on a large site and I don't ever recall in all of my history of Drupal ever having mass, like, widespread database corruption just from content editors. Like, yeah. Yeah, we worked on the same site. We had a different one. Field collection. I once, the day before a site was going live, I was like, I'll clean up all the users that were test users. So, you know, go through. Obviously, everyone knows now, I'm sure, when you do it in bulk, it automatically deletes them and their content. And what it ended up doing was it, I deleted all the test users in bulk, so deleted them and all their content, which effectively deleted every field collection on every Node the user ever saved. And this was in production the day before the site went live. So, I remember, like, just going completely white and thinking, what am I gonna do? I messaged Lee, he had, like, magically just copied the production database to staging, like, two hours before. And then the two of us spent the next, like, three hours going node by node and recopying every field collection. I can't believe you don't remember this. If this is the same site I think you're talking about, that actually read its head in the migration to Drupal. As well, the same data integrity issues. And I'm looking at Gibran, I didn't, yeah, he... And that was seven years ago. Yeah, no, but, yeah, I don't remember it, I'm sorry. I'm glad you don't remember it. It's one of my great shames. I was gonna say views as well. I mean, it was worse in Drupal 7, obviously, but I think, like, it can just cause so much pain, just, and so much joy. I'm normally very careful to use the contributor module, always check the state and statistics, how many sites to use, and how active the maintenance do, and go to Google, Google is my friend, and find the training video, and if I feel safe and tested, then go for it. Webform. Webform is the greatest module that was ever created. Both seven and eight. Excellent, okay. I think we've got quite a bit of time, so one or two more questions can come down the line. There's one here that's getting voted up some more, which was, what would be a recommended pathway to mastering Drupal for new devs jumping on the platform? I can talk about what my experience was, and I was talking to someone about this yesterday who said the exact same thing, is to think of where you've seen what you're trying to build before, and because it's open source, just go and use that as a copy. This was Ivan from WebWash, we were talking about this, and yeah, so I can, I remember when I first started, I did a lot of work around Ubicart, and a lot of work around, it always required these really complex forms that had table-based layouts, and every time, this was before we built admin user and admin content with views, and it would, well, I've seen this pattern before in think where you've seen the same thing, and just have a read of what the code's doing, and copy and paste it, and modify it from there, and yeah, but in my ariely days, it was very much a lot of what does this button do? So modify the code and see what breaks, and then learn from that, yeah, but I think the best way to get involved is to actually contribute. I think I could qualify my Drupal career into before I started contributing and after, and there are so many parts to Drupal that you can't know everything, and I think the sooner you accept that, the better, but the reality of it is throughout all of the ecosystem, there's people who are experts in their specific niche, and if you help contribute to that niche, they're more than happy to convey that knowledge to you, and so there's an excellent blog post that I linked some people to yesterday by Angela Byron, it's called Embrace the Chaos, so if you search for WebChick, Embrace the Chaos, and it's basically a tale of two developers. One developer is Sloppy Sam, has an idea for something, throws a patch up and says, what do you think people, and it's got no tests and doesn't meet coding standards, it's just a rough idea, and the other one is Perfectionist Pete, and he has a great idea and he spends three days coming up with the NT relationship diagrams and does everything like that. In the time he's taken to do those three days, someone's seen it and reviewed it and provided feedback, and Sloppy Sam's learned from that, rolls up a new patch, meanwhile Perfectionist Pete's still off coming up with the ultimate design, and anyway, read the blog post, but as long as the short of it is, through this process Sloppy Sam learns a whole lot, and because there's consensus and community activity around that, that's the patch that gets in. By the time Perfectionist Pete's finished, he goes to upload the patch and realize that it was already fixed yesterday and he's wasted five days or whatever of time, so yeah. Not the less than I thought it was gonna be. No. Yeah, I'm 100% Sloppy Sam, and people I talked to yesterday that said they'd worked on a patch and it wasn't finished, and I said, put it up, put it up, right? Because in our time zone, a lot of people in Drupal community refer to us as Code Fairies in the night, because they put stuff up and they come back the next morning, and because it's time zones, we've pushed that along a little bit further. If you work in a collaborative approach, you know, you learn from that other person, whereas if you kind of try to do it on your own, you don't get any of that expertise, so I think there's a lot of people in the Drupal community who would honestly say that they got their computer science education in the issue queues. Yeah, I'll sort of add to this a little bit. I like that Embrace the Chaos is an element of Zen, I think, to the development process, and that's part of what this talk, thank you, it's partly what this is about today, is sort of to express that everybody's having challenges and that some things are hard, but just get out there and do it and keep going and recognise you said, oh, you're not alone. There are people you can reach out to, but generally you're not the only one in that boat, right, so that's part and parcel of the job, don't freak out about it. I'll openly admit that there were things about PHP, I've been doing PHP since 2000-ish, and there were things about PHP I did not know until I started contributing to Drupal A.  If you're very guarded about that, then it's very difficult, yeah. Yeah, I think that's like, to add on that, it's like, yeah, you've gotta drop your ego and really just understand that there are a lot of other people that are smarter than you and you shouldn't say that as a bad thing, it's a good thing to, you know, embrace it and learn from them, and you know, for me, when I joined previous NEXT, working under people like Lee and Sam, all of us are here, you know, just learning so much from these people from, and a big part of that was, yeah, contributing back, and then even back when I very first started Drupal was chucked into the deep end to write a sub module for the revisioning module in Drupal 7 or 6, and yeah, it's just about that, like, chucking yourself in the deep end, learning from people, seeing what's out there, seeing how other things are done that are similar, and then just writing some code. Excellent. I think we do have time. They're turning up, my clothes will go pretty quick, so we've got time. There's another question that's come in and risen up to the top. Which would be interesting. What's the longstanding core issue that you most wish was fixed? There's an example here, allow query strings in your RLA aliases. That's open to... Oh yeah, there's a views operations caching bug, which is, yeah, no one would know about it until you start having edit-owned permissions and things like that. And I think, for me, yeah, most of it is around caching issues that I've started noticing are pretty common. I mean, it's a common problem and a lot of mod, like not only core, but also con-trip, custom, yeah, can really buy you. There are a couple of nasty menu bugs I've found in the last couple years that I very much wish were fixed, and I mostly wish I could help fix them, but I can't, so I'm just pestering other people to try to help me. But one of them is if you move a parent, if you move a menu link between menus, so if you move from the main menu side of the footer menu, it looks like all the children got moved as well, but then every time you save one of the child nodes, it bounces back to the main menu and goes to the top level because it has no parent anymore. So it's actually diabolical because it looks like it worked until you realize it didn't work, and then you have to change each one manually. So I really wish that were fixed. Yeah, on myself, there's a few issues around UIDs and tracking ID entities, which just seem to hang around. I feel myself sort of just frustratedly. It doesn't really cause me any issues, but it's really annoying. I find, because we pulled UIDs in and then we're still using serial IDs in places and part of me just goes, why? So that was a lot of the participant questions have come up. I might start wrapping this up a little bit now. I do have, I had an open question on here, but I think it might have come up a little bit, but I might put this out there again. If there's one thing you could impart on people in the audience today to help them, what would that be? We had this as a dev-specific question before, but generally across the whole panel, more of your broad experience as Drupal is, what's your encouragement you can give to people to increase and better their Drupal experience? I think just jump and slack and ask for help and someone will be there.  I think there are so many of us that have been in that situation, like even if it was years ago, we still remember what it was like and so we are eager to help if we can at all and so yeah, I would just say you're not alone, everybody struggles at times, don't be afraid to Google it, don't be afraid to ask for help. And the issue queue is useful, so if you have a bug to report, do use the issue queue, but if you just have like a question that you don't know the answer to or you just need help with something, definitely please come to Slack and chat with us. Yeah, I would say 50 maybe percent of the questions that the answers we provide in there aren't the answer, but who's the next person to ask? Because the community is vast and you can't know who's the expert, but you might know someone who knows someone, and so a lot of the work that happens in those channels is, oh, you need to ask that in the media channel, or you should go and speak to this person. So knowing what to ask is one thing, but knowing who to ask is another thing, and I think that that's one of the real benefits that that channel provides, yeah. Yeah, can't agree more than that, ask questions, because years ago I have a problem with the menu system, and I think that TIMC, remember, and I pop on the, that time I didn't use the Slack, another triple community channels, ask questions, and somebody just point me to the right direction. It's really helpful. Okay, thanks. So I'll jump over this one. It's a little bit of homework for you all. I think just to sort of, we're nearing the end of a conference, we're nearing the end of a year. So as people in the Drupal community for yourselves, it's a good time to sort of lock in and end the chapter, and sort of do a bit of a closing off and recognize where you've come. I think that's really helpful. It's good to know where you want to be, but also where you are, and particularly where you did come from. So there's some questions here you can go away and ask yourself, like, what have you already learned? Like, what didn't you know that you do now? What do you now do differently that you didn't do before? What have you actually achieved? Like, acknowledge that for yourself. What have you achieved? What have you built? What have you contributed? Because there will be something, find that. And have you actually acknowledged that for yourself? How far have you come? It'd be really helpful just to lock that in for yourself and be ready to go on to the next spot. And of course, what are you gonna do next? Answer that for yourself. You know, where's that journey going? So basically, if you want to continue this conversation, do you want to keep this conversation and keep getting this engagement, then go into the Slack channel. I've got a link up there for you. It's on posters around here. Find it, get in there. Talk to the people in the channel. Do we have 300 members? It was 296. 296. 296. 276. Oh yeah, come on guys, you can do this right now. Who's not in there? So I've put my name on there, but you'll find that everybody's got tags, but they've got pictures. It's really good. It's one of my favorite things actually about coming to Drupal South is getting to be face-to-face with people that I'm chatting to regularly. So yeah, all of us are on that Slack channel and we reiterated it. It's one of the best resources available.  But really, sometimes you've got to be vulnerable. I go in there and I just feel like I really should know the answer to this. I don't even know if it's the right question to ask.  And I'll ask the question anyway. And get an answer and go, whoa, I just saved hours of time and frustration just went away. Sometimes it's not even necessarily like, what's the answer? It's like, what do you guys think? What have you done before? What issues have you come across? So it's not necessarily like, I have this giant problem and I need a solution. It's more like, what experiences have you had, have you used this control module before? Did it cause any issues that you didn't foresee? All those kinds of things, it's not always sort of like debugging or troubleshooting, but just like general advice and shared experience. Yeah, and one thing I've tried to stress to people, if you do direct message someone with a specific question, they may route you back to the main channel and that's not because they don't wanna talk to you individually. It's because if you have that conversation in private, no one else benefits from it. And it's also because the person you ask might have a different opinion to someone else. And if you're asking the channel, you might get three differing views and even the person who answered the question the first time might learn from the person who answered with the second thing. So yeah, I think the golden rule of open sources, conversations have to happen in public and that like, yeah, it's good. Okay, thank you very much. Si, what are we up to? Well, thank you very much. Thanks for your contribution.


Today we're having our 30th annual Christmas party with the Free Hearts organization. We have brought 100 kids and their family out to Nashville Books and Toy Store. Pinnacle Bank and Casey Fonda have partnered together with Free Hearts to give the kids a free Christmas tree where the kids get to come in and they get to spend up to 100 plus dollars on any toys and any gifts they want out of the Toy Store. And the bookstore also had given these kids two free books. One of the biggest things for these kids, you know, through this time of year is having people that can give to them, having people that touch their hearts. The Casey Fund and Free Hearts is trying to do that, but another great year for Christmas and another great year of continuing to touch these people's hearts throughout the year. We reached out to Pinnacle Bank to ask them if they wanted to partner and basically match the Casey Fund of fitting up a couple of dollars to give these kids a shopping spree. And Pinnacle didn't hesitate at all. They came with a warm heart and jumped right in with our organization and with the partnership we have with Free Hearts. We definitely thank them so much for their participation in this. Today is just a great time just to touch people's hearts so just want to reach out to the people out there and say whenever you can, whenever you have time, whenever it's on your mind just always think about that next person that's in need of help and just laying that helping hand.


everyone Shaber 1000 here we got monkey and Bruno and we got all these decorations on the boat so we don't have them turned on yet but we got to meet over there at that bridge we got to meet over there at that bridge so that's where we're going now as soon as monkey does her intro and when it gets dark we'll light this thing up and show you what it looks like well at least from in here they were supposed to give us a parade route but they didn't get up the boat part time and any time it's dark you know it's supposed to be no way guide and they were just stacked like it was a race one it would go so fast some people gave up early but there was a lot of nice boats what their mom yeah mom I have fun Bruno I have fun so get back on when we get back to the house and I'll show you the boat from a distance I didn't show me I'm showing you okay guys so that is the boat parade hopefully I got some of it for you where'd you go there you are in the dark you can't see me oh you can see my neck so that's cool yeah I like my neck yeah I got one it's under the beard but so there's the boat I know you couldn't see much like monkey said in her video because we were in the boat so there's the boat turned out pretty good I did put the horn on it I don't know if you heard it or not we was blowing the horn and everybody was going nuts so take you for a walk around here and I'll just show it to you real quick monkey bought this simulated present at Walmart and well we knew we couldn't put it down in there because you couldn't see it and I thought oh I got an idea so there's the horn so we just stuck it over top of the horn but I had a great time there's a lot of fun being from Ohio never been in a Christmas boat parade before because you know I guess too cold for people but yeah so I got them plugged in now they're not running on battery power so we need plugged in so yeah that is the boat that's what it looks like there it is hey monkey come over this way I want to see your hat where in front of the lights I want you to see her hat it's cute she got little ears little ears right there and of course you seen me so yeah monkey have fun it was like she said it was kind of unorganized and I think I mentioned it in the dark you're supposed to be supposed to be no way idle and we were probably running 15 to 20 and still couldn't keep up with them no lead the lead boat and everybody just started breaking off yeah I mean I could see the lead boat but it's like whenever we got close they wanted to take off you should it's a parade yeah you're supposed to go slow yeah and they were they were going like it was a hurry up and get this over with kind of thing like it was a race yeah it was crazy then we got back into this cove and I seen the lead boat go to my left like through these trees we get back in there of course everybody's following us now and everybody got back in this cove got stuck there well we were stuck but well I mean you know everybody had to turn around because we couldn't see where that guy went yeah so you know we had our headlights on and stuff I mean that was stupid yeah but anyway so but we had fun huh yeah we had a good time and a lot of nice boots there people on the shore watching even some people that live on the lake there they were sitting and having a bomb fire while they were watching the boat parade go by setting off fireworks it was cool it was really cool and it was a great night wasn't real cold I didn't I brought my sweater but didn't really need it you know it got a little chilly coming back but it was nice it was perfect for this today yeah and but they loved the horn yeah they did I mean everybody was watching and waving and stuff I started hitting that horn yeah you could hear the whole crowd screaming and hollering over top of the engine of them because nobody else did that they had one guy he honked his and it sounded like it was a little little honk yeah it was just a regular boat horn so it was like so it was pretty fun but yeah it was just you know I'm thinking parade you know you go slow so I'm just gonna use a trolling motor and I brought some Christmas music but couldn't really play it because you know we had to use the gas motor to keep up with them yeah that trolling motor fast enough after dark that's about idle speed right oh well it was fun yeah it was a lot of fun I'll show you the boat again real quick month I'll let you know say goodbye oh what's that you're trying to go oh I was but I said monk oh monkey says she's out for now y'all all right and say Barry the myth the man legend gone for now hopefully we got some stuff for you monkey filmed its suit too so check out her channel monkey 1000 and she is one of my featured channels on my channel so you can get to her for me so there you guys go Merry Christmas everyone and stay tuned we're going camping Sunday night and we're coming home Monday just an overnighter we're not gonna take the boat but we're gonna do some fishing how about yeah all right guys we'll see you soon thanks for watching bye bye


The introduction of containers in container orchestration has made it easier to deploy and update applications. Likewise, the growing popularity of database cloud service offerings has also simplified the development and deployment of stateful applications. However, developers often access these database services in many different ways, often dealing with a myriad of credentials, and this can make it rather difficult for cluster administrators to maintain a comprehensive overview and understanding of all the various database offerings in use. Hi, I'm Jeremy Aree, an engineer in Red Hat's application ecosystem development team, and today I'd like to share a bit with you about Red Hat OpenShift Database Access, our newest cloud service offering that makes it easier for administrators to provision and manage access to multiple third-party database services. Red Hat OpenShift Database Access is currently available via two OpenShift cloud services, OpenShift Dedicated and OpenShift Service in AWS. Initially, our service supports three database vendor offerings, MongoDB Atlas, a popular cloud database service, CrunchyBridge by CrunchyData, which provides a managed PostgreSQL cloud service, and CockroachDB Cloud, a distributed SQL database service. As a prerequisite, administrators need to complete a few steps on the chosen provider's platform. In this case, we'll demonstrate using MongoDB Atlas and we'll begin by setting up our organization's projects and permissions. Red Hat is providing an access service, however, the database instances themselves reside on the respective provider's cloud infrastructure. Given that, we'll need access to those resources. Our first step is to establish our teams and API access. Let's take a look at an example organization within Atlas. This organization, called Appinch, consists of several projects. Currently, we're taking a closer look at project one. Within this project, we can find one cluster that will be of particular interest to us later, named Debast Cluster One. If we go ahead and take a peek at the collections inside this instance, we'll see a pre-established dataset ready for use by an application, but let's come back to that later. Before we dive in, let's quickly switch over to the Red Hat OpenShift Hybrid Console and take a look at where we enabled OpenShift Database access service. In this case, intended to run as a service on an OpenShift-dedicated cluster. As the cloud service offered by Red Hat, we provide the SRE resources and day-to-day management of the Kubernetes application platform so you can focus on enabling your developers. As seen here, we've already leveraged the add-on tab to add OpenShift database access to our cluster. Back over on the cluster, once installed, we can see that our operator takes care of a few dependencies that require us at that level as well. Note that we have operators for each provider. Here we see CockroachDB, CrunchyBridge, MongoDB Atlas, as well as the service binding operator, which will help with setting up our connectivity when we're ready for that step in the developer workflow later. With all of our operator dependencies in place, we can begin the instance discovery process. OpenShift Database access provides the cluster administrator with a consolidated view of all the connected database services that are available on their cluster, including details like which instances are already in use, what user has requested that connectivity, and in what project it has occurred. Let's start our discovery process by using one of the actions available to us here inside of the summary view to create a provider account resource. Here, we select the provider which we wish to target, in our case, MongoDB Atlas, and supply the credentials associated with our account. After receiving the create successful status message, we get back a list of instances associated with those credentials. Back over in the summary view, as with MongoDB, we can also create a provider account for CrunchyBridge and discover what Postgres instances we have on their platform as well. Notice that the sets of credentials required for each provider may vary. Here, with the CrunchyBridge provider, we need only two values, the public and private API key in secret. With that now complete, let's swap back over to summary view and take a look at the comprehensive list of instances available via both provider accounts which we've now set up. With those in place, we have now, as administrators, enabled our developers to create trial database instances via any of our various providers as well as establish connectivity with their applications from within their various projects. Once a database vendor provider account is added, the developer can access or create a new instance from the connected database tile. I hope this helps show how you, as an administrator, can use Red Hat OpenShift database access to bring a low-touch administrative experience to provisioning and managing access of external database cloud services. You can check out our companion video for application developers, which shows how they can simplify access through a drag-and-drop UI to connect their applications to third-party database vendor instances, or give it a try yourself at red.ht slash dbaccess.