Hey, I'm Joel Klatt, and here are my top five quarterbacks for this year's 2019 NFL draft. Let's start with number five. At number five, I'm going to go with Will Greer. Now, he's a guy that's not cracking a lot of top five lists, but Will Greer is going to be on my top five lists for a very simple reason. Against his toughest opponents, he played his best football. That's what you've got to do at the next level. He's also a guy that has a lot of maturity. He's gotten that maturity from his time at Florida, then moving to West Virginia and playing under Dana Holgerson. He was terrific against Texas on the road, bringing him back late, ultimately winning that game. He was terrific against Oklahoma, even in loss. Those are really his two toughest opponents. The one thing he's got to work on, though, he tends to wait for the home run rather than just taking what's in front of him. Because of that, he's taken too many sacks, and he's put his team in some bad positions. If he can curve that mentality, which I think is more from a coaching standpoint, then I think he's going to work out at the next level. At number four, I'm going to go with the Missouri quarterback, Drew Locke. Now, I really struggled with whether Will Greer should be at four and Locke should be at five. But for me, Locke is going to go to four because of his arm talent. Listen, he's got a terrific arm, very stafford-esque, if you will, a guy that can really sling it. His problem comes when he relies on that too much. He loves to drive the ball and throw his fastball rather than winning with touch. At the next level, you're going to have to win with touch.  You have to layer that ball in those intermediate zones and into those intermediate windows. He's got to learn how to do that if he's going to have success at the next level. At number three is the Duke quarterback, Daniel Jones. Now, Daniel Jones has the quote-unquote coaching bloodlines. Remember, the Manning brothers played for Cutcliffe. Now all of a sudden, you've got Daniel Jones playing for Cutcliffe at Duke. That's going to help him out immensely as we move forward into this process. He understands the schematics, he understands how to work in the pocket, and I think that's his best trait. Very similar to the Mannings as they got into the NFL. They were comfortable in the pocket in the midst of chaos, and I think Daniel does that with spades. He does have a requisite arm. It's not the greatest thing in the world, but he wins with touch, which I think is more important than the ability to throw a big fastball. But Daniel Jones is number three for me. Now for my top two, who are separated from the rest by a wide margin, and I'll start with number two. Dwayne Haskins, the quarterback at Ohio State. What a tremendous year he had, and I think the finish to his year was even better than people want to give him credit for. In the middle of the season, he tended to struggle a little bit, in particular with his footwork. He got a little wonky in those areas, and because of that, his accuracy wasn't that great. Now, during the end of the season, that stretch runs, he played some of the best football of any quarterback in the country, in particular against Michigan, Northwestern in the Big Ten championship game, in the Rose Bowl against Washington, and those were all defenses that posed pretty formidable challenges in their own way. The man coverage from Michigan, the tight zone from Northwestern, and then Washington was just one of the best past defenses that we've got in the country. I think at Dwayne's best, he could be a Matt Ryan caliber quarterback, a tall guy that can sit in the pocket and make all the throws, but again, he needs to develop that footwork to do that. Now, Dwayne is an immense talent. His arm is terrific. What he will need to develop is his footwork in the pocket. When that wasn't there, he tried to win with his arm, and the ball lagged a little bit sailing downward. When he's got his footwork in concert with his upper body, there was none better. He's a project, probably needs to sit for a year. I think this guy does that, and his ceiling might be the highest of any quarterback in this draft. In my number one quarterback in this draft is Kyler Murray from Oklahoma. This guy has such a rare combination of passing acumen and efficiency with the ability to make plays with his feet. I've never seen anybody with this style of combination. We've seen Michael Vick in the past, and it was so rare at that point to have a guy that could throw the football as well as Michael Vick and be as explosive of a runner. But I'm here to tell you Murray's both more efficient as a passer than Vick was coming out of Virginia Tech, and he's more efficient as a runner than Vick was coming out of Virginia Tech. If you looked at Vick while he was with the Hokies, what you saw was a guy with a big strong arm that just used his athleticism to get out of trouble when he needed it. When you look at Murray, you see a guy that was over a yard better than Vick on a yard per carry basis and was much better from a completion percentage perspective and touchdown to interception ratio perspective. All of that lends itself to success at the next level. I think Murray is going to find himself in a great situation in the NFL, probably with Arizona, and I think he's going to have a really bright future. He's the quarterback that you take if you want to be better next week. He makes a team better right now because of that combination I was talking about, his passing acumen, and his ability to make plays with his feet. We have never, I repeat, never seen anybody like Kyler Murray in the NFL. There is one red flag with Kyler Murray, one his size. Last time I checked, I saw a Super Bowl get one by a quarterback that was 5'10". That was when Russell Wilson beat the Denver Broncos. I've seen now Drew Brees start to erase every record in the NFL record book, and this guy is barely over six foot tall. Baker Mayfield, barely over six foot tall, has tremendous success. Patrick Mahomes is not a tall guy. And shouldn't it be more about your production? Shouldn't it be more about how many passes are batted down at the line of scrimmage? Let's take a look at that. Of these five guys that I've mentioned in this video, you know that the two at the top are the ones that had the least amount of passes batted down at the line of scrimmage? Only five from Dwayne Haskins and Kyler Murray. Five. So you tell me if his height is an issue, because I don't think it is.


Holy man, so Super Mario Odyssey, I knew it was selling well, Nintendo's financial briefing update said 2 million units were sold in the first 3 days, but they didn't break down where those units came from, which countries were doing best, and now we have some additional data that not only tells you that the first 3 days were amazing, we have data from the first 5 days in the United States that are extremely, extremely impressive, and now we have some information from Europe as well. So first let's cover the stuff I already knew that I didn't make a specific video about because I was waiting for more sales updates. Super Mario Odyssey is the fastest selling 3D Mario game in Japan, it sold over 500,000 copies on the first few days, and that's just amazing, the next closest one was a little over 300,000, and to put it into bigger perspective in Japan, only two games in the entire Mario franchise outpaced Super Mario Odyssey, and you guess what those are? New Super Mario Brothers, we and new Super Mario Brothers on DS, so yeah, outside of the first time bringing back 2D Mario, nothing in this sold faster than Super Mario Odyssey in Japan, and you figure out, well maybe that's where the story ends, but no, let's head on over to Europe. So Nintendo says that Super Mario Odyssey has become the fastest selling Super Mario game ever across Europe, so none of the games are ahead of it. It surpassed the launch weekend sales of Super Mario Galaxy 2, which came to Wii several years ago, Super Mario Odyssey is also the fastest selling Switch game in Europe, no numbers given, but obviously this is good news, when you're the fastest selling Mario game ever released in the whole of Europe, that's just intense. Now here's one where we do get some sales figures, and this includes two additional days that were not part of Nintendo's financial briefing at the time, because well frankly the game hadn't been out for five days at the time of that briefing. Mario Odyssey has sold apparently 1.1 million copies in the US in the first five days, and apparently now they're clarifying here it is the fastest selling Super Mario game ever, there are some mainline Mario games that aren't called Super Mario, so it's a little bit play on PR to try to get that best selling Mario game everything going, but here's the press release that they sent to my email. It says in just five days the new Super Mario Odyssey video game for the Nintendo Switch system sold more than, oh sorry, more than 1.1 million units in the US alone. That makes it the fastest selling Super Mario game ever in the United States, suppressing and this is what's really impressive, the new Super Mario Bros Wii game, Super Mario Odyssey is also the fastest selling game so far for the Nintendo Switch. The game has already been enjoyed by well over a million people and is likely to be enjoyed by many more, as those early players continue to spread their excitement for Mario. On Metacritic.com which aggregates scores from certain reviewers for example, the game currently has a critical review average of 97 with 43 perfect scores. This makes Super Mario Odyssey the best review game on Metacritic for any system of the last three years, tied only with Nintendo Switch launch game Breath of the Wild. The public continues to respond positively to Mario's latest adventures, said Reggie Fisame, Nintendo of America's president and COO. We are seeing sales momentum for Nintendo Switch thanks to an ever-growing catalogue of games from large publishers and indie developers. Nintendo has increased supplies to the Nintendo Switch to meet demand through the holidays. A total number of Nintendo Switch systems sold in the United States through the end of October now stands at 2.6 million. Oh my gosh, let me explain something to you about that 2.6 million mark. They just did that financial brief update. Through September 30th, the Switch had sold 2 million units in the United States. You know what that means for the month of October? Nintendo sold 600,000 units of the Nintendo Switch in the month of October. I'm sure Super Mario Odyssey had a big deal to do with that. People ordering the Odyssey bundle and just the fact that the Switch was just plentiful in October. In general, that's huge. That's 600,000 before we even get to the major holiday month of November. It could move in a million. No one on Nintendo updated their projections from 10 million to 14 or 16 million or whatever it was because look at what's happening. 600,000 in the very first month that the Switch was easy to get your hands on and we haven't even hit the full holiday stride. This is wow. Wow, wow, wow. Now our sale amount, we're going to continue through November. It should, thanks to the Black Friday shopping season at the end of this month. But there's also third party games and it'll be interesting to see if third party games this month can carry the load until Xenobite Chronicles 2 comes out. Now there has been some criticism of Nintendo because they haven't really been... They did that Xenobite Chronicles 2 long feature in a direct and that was nice and everything but they haven't... That kind of long feature doesn't really advertise the game well and let me explain. The one complaint I had when the last time they showed out Xenobite Chronicles 2 is it was just too much. It was information overload and when you do an information overload like that in a very complex game like a JRPG it could really be off-putting. And to be fair, I was kind of put off by Xenobite Chronicles 2 just because of how much information was thrown at you at once. It's too much. In a game like Xenobite you don't need to show off all of the complexities of it. People just need to know those complexities exist. And ever since then they really haven't said anything about the game. I haven't seen any TV ads for it which of course you know with Odyssey right now I won't expect TV ads for another couple weeks but Nintendo needs to do a better job promoting that game in this final month leading up to release. I mean we're less than a month away officially as of today for Xenobite Chronicles 2 coming out which it'll be arguably Nintendo's like biggest in terms of world and maybe even gameplay time game they've released on Switch themselves. So it would be nice to see that game. I want to see Xenobite treated like Zelda and Mario and Splatoon. I want to see Nintendo actually put a real marketing budget behind it because JRPG sell, people just need to know they exist. But yeah I'm really excited about these numbers. I mean Odyssey is just doing insane. I knew Odyssey was going to do well right. The day before release comes out we're recording this week's podcast and we're seeing all these perfect scores and all this. Okay Odyssey is going to blow up clearly these are the kind of sales numbers Zelda probably would have did if it released at this time if this number of switches were out. Man 1.1 million over that 600,000 units of the Switch selling in the United States. Fastest selling Super Mario game beating out Super Mario Wii beating out all the Mario games released in Europe beating out almost every single Mario game in Japan. This is just wow. Wow. You guys wanted some positivity on the channel. This is a pretty positive stuff right here. Odyssey could end up being the best selling 3D Mario game of all time. I think it's got a top 13 million I believe to become the best selling 3D Mario game. To become the best selling 2D Mario game it's got a long ways to go. I think I get like over 20 or 30. I can't remember the sales numbers for like the NES Mario game I think is really really high. I can't remember. I think it's at 40 million 50 million. So I don't think it could ever be I mean maybe it will become the best selling Mario game ever. I don't know but this is wow and Switch baby the Nintendo under project. I mean think about it they were just at what was it? This is just calling United States sales because we don't have full figures. What we do have full figures I think for Japan are a good idea on the figures but I believe the last figures were 7.67 million units sold just in the United States alone that got pushed over 8. If you throw Japan sales in there and European sales we could be looking at already 9 million units in sales before we get to the major selling month of November. Man oh man it's impossible by 2018 that we could be over 10 over 11 over 12 million units sold. It's possible it could be there. We obviously don't know what's going to happen in 2018 because we don't have a lineup of games with release dates yet known but oh man good on you Nintendo. Thank you thank you thank you. The Switch for all the criticisms I have I love the Switch. It is the perfect console at the perfect time. Yeah stay tuned because I'm thinking about working on a video about how Vita actually was the true precursor to Switch rather than Wii U. Like a lot of people are assuming although obviously I understand the Wii U sentiment that's a Nintendo system but there's actually a lot of similarities oddly enough between what the Vita was capable of doing and what the Switch is capable of doing not from a power perspective but like the idea behind the consoles and the functionality of those consoles and why it's working for Nintendo versus why Vita failed for Sony. I have an interesting take on that so we'll see if I can round that up and do a video today. Let me know down in the comments below if you'd be interested in seeing a quick comparison like that. I'm not going to go into every nitty gritty detail but I think there's an interesting comparison to be made about why Vita actually kind of did what Switch is doing but didn't do it good enough for certain reasons. Anyways folks I'm Nintendo RoverDance from Nintendo Prime and if you like this video you know what to do and if you dislike the video hit that dislike button subscribe for more content and I will catch you in the next one.


Jeff Belknap has thought a lot about Jeff. Thanks for discussing this with us today. What are your top of mind concerns if a company wants to integrate these tools, these generative AI tools? How do I let people experiment safely? How do we make sure they're not just taking all of my private data and throwing it into just whatever website they can think of? Where's the security risk? I think the primary risk is, you know, this is one of the first new technologies that come out that everything you put into it is something that it might very well spit back out to another user. If I'm an IT professional, what do I need to think about? If I've assured that all the security controls are in place, how do I just make it easy for my users to use? Because the thing to remember is the value that people in the security space add is enabling us to do hard things as a business, enabling the business to grow and thrive and move into new areas. And if you're accelerating that, that is your job. If you're saying no and we have to wait, people are gonna work around you anyway.


So, we're here to have a little chat about the Drupal South Committee and this, we just thought we'd prepare some information for anyone that wanted to find out about the committee and what we're doing and why we're here, so there's a bit of self-justification in this but also we want to be transparent about what we're doing and how it's running and the things we're trying to achieve at the moment. So, primarily this committee exists for one purpose, this is the primary purpose of the committee and that's to ensure the continuity of Drupal South. We want to make it easier for people to run these events, we want to make sure they get run and we want to make sure that people aren't reinventing the wheel every year but alongside that we see this as an opportunity to expand lots of different aspects of Drupal adoption in Australia and New Zealand and we're sort of trying to cherry pick ideas that people think are good and where there are opportunities. So, a lot of this for us has been about listening to what people have to say as well, so sometimes we might come out and say, we think this but if you guys tell us something else then we're going to listen to that and move in that direction as well. Alright, so why does this committee exist? What is the purpose of the Drupal South Committee? Well, previously when you wanted to run one of these events in Australia or New Zealand, you would usually go to Linux Australia and say, hey, I've got this idea for an event, can I have some money or can you spot me some cash till we get some ticket sales please? And they go, yeah, sure, right. And they might consult with previous organisers who we called Ghosts and those people would usually have had some involvement in the pitch anyway and that would all be accepted and you'd go and do it. But then the next time you wanted to do it, the same thing would happen again and the people would come along and have no idea what they were doing and it would be really hard work. So the Drupal South Steering Committee sits between Linux Australia and these event teams. The Steering Committee reports to Linux Australia on budget, an event, success, so we actually have an official Linux Australia capacity there. And then individual event teams report into us on their events and how they're going and we help them be a success. You'll notice that the Ghosts are missing from this slide, it's not really deliberate, it's just that the Ghosts were kind of necessary in the past, it didn't function without those Ghosts being there whereas it can continue now in a bit more of a structured way. And we're also trying to foster better cross event participation as well so that in any given year there might be some people on one event team who are going to go on and do other ones in the future so they get some experience. Or people who come back and do them again. Alright so the Steering Committee, Subcommittee of Linux Australia, it came out of a six month consultation period led by Ghosts, was formed in 2019 following a community vote. It has five members and we're on rolling two year terms. So we have a, I haven't put it up because it's a bit confusing, but we have a schedule to show when individual committee members will roll off and be re-elected and the idea is that we hold one election, the next one would probably be early 2020 and that elects the next five people and they roll on slowly. So the purpose of those overlapping rolling terms is to ensure that there's always continuity on the committee. You don't get a wholly fresh committee coming in not having any context or knowing what's going on. In any case, the whole committee gets re-elected next year. So current committee should all be in the room down the front, Owen Lansbury, elected as chair, Pamela Barone, Event Liaison and a Code of Conduct Reporting Officer, Tom Tugood, Government Liaison and a Code of Conduct Reporting Officer, Nicole Kirsch, Treasurer and myself, Christopher Skeen and I do Corporate Liaison and Marketing. So how does the committee function? What do we do on a day-to-day basis? Essentially, we're running this with a monthly meeting. Those haven't been public yet, but I think we're open to that idea of having public meetings. Yeah, so if you're interested in attending the meetings, let us know and we'll make sure you're included. We communicate a lot through Slack, through the Drupal South Slack and that's somewhere you can find us and we also are trying to post regularly on groups.drupal.org and the Drupal South website and I think going forward as we sort out what the hell we're doing because we often don't know ourselves, we'll be doing more mail-outs as well through the mailing list to keep people up to date. So we have a few current activities and these are based on some strategic priorities that we work through and also our discussions with people so I'll run through these pretty quick. First of all, we're coordinating the annual event program and now that is primarily Drupal South but it also includes Drupal Gov and it may include one or two other little events as well depending on where we think there are opportunities. We're doing some community initiatives so an example of this is some of the things we discussed in the BOF at 11 o'clock today around meetups so we're trying to find ways to improve the communication and knowledge sharing between meetups and see where the opportunities for those meetups are to work together. One of the interesting ideas that came out this morning, for example, was like shared regional meetups via video hookup, for example, there was some interest in that. Provide some common tools where they're useful for those meetup groups and potentially assist with funding for smaller items should you need them, event or venue hire or pizza or whatever, meetup. We're looking at annual sponsor packages as a way of providing for a more continuous and less burdensome method of funding Drupal South so instead of not really knowing how many events are going to crop up during the year and being asked maybe to fund all of them as a sponsor, you can have one opportunity to engage with Drupal South and then whatever we run comes out of that so that's good for Drupal South in the sense that we have a more predictable funding model and it's potentially good for sponsors and that we can offer value in different places as well and reduce the number of times you have to sit there and stare at a sponsor proposal. Anyway, we're still talking about that one. We're doing quite a lot of data collection stuff currently. We're trying to get a better understanding of the current market and what's going on. So we recently ran the Drupal sponsor survey in Australia and that fed into the huge response, fed into the BOF that was held yesterday and we are about to run a Drupal user survey. It was meant to be ready for this event because I was sick, it's not so it'll come soon but that is a survey hopefully of any and all Drupal users we can find in Australia and New Zealand and find out what they're doing and some of their interests. We also have a growth strategy. Now this is a bunch of various things that we've been poking at and looking at in different ways and I've put them together on this slide called growth strategy. We don't actually have a growth strategy, we just have some things that we're looking at. So some of these ideas are engaging a local marketing specialist to do a little bit of Drupal marketing for us. We're looking at refreshing the website. We've talked about one day decision maker summits like a CTO summit and similarly we're looking at maybe where we could possibly run like a Drupal booth at a related event. Now some of the strategy around that relates to why we would do that. So for example, are we going to places where we expect to be putting Drupal up against other systems like Adobe? Are we competing on behalf of our constituents? Or are we going out to recruit people into intern programs for example? So the reasoning behind that might depend on where we think the strategic priority is and that comes from what you tell us. We're also developing a content calendar and we're thinking about how we can create content, where we can create content be valuable. Obviously we're all volunteers, we have a limited amount of time. We're not going to be spinning out loads of content but maybe a little bit here and there where it's strategically useful. We have regional initiatives which we are looking at. One is the potential of running a Splash awards in Asia PAC and another is how we can share materials and events or not sorry not events materials and speakers with other Asia PAC events. So the Australian New Zealand Drupal group is by far the most active group in this part of the world outside of India. India has a very active group as well but pretty much every other country is quite small so you know potentially helping those areas with some sort of shared stuff is going to be useful too. And the last one on their work towards facilitating Drupalcon Asia Pacific with the Drupal Association might be a bit of a pipe dream or a wish list item but certainly we know we're able to deliver very high quality events consistently and with a high level of organisations so that might be a possibility of rebranding one of these as a Drupalcon. Public sector initiatives so we've incorporated this year the running of Drupalgov into the Drupal South schedule. Drupalgov has always been something that's run a bit ad hoc. I've kind of kept custodian ownership of it but other people have come along and done it. It's becoming a full part of the Drupal South schedule at this point though at the moment we haven't worked out how often or where we might run it. We just know that we think it makes sense to do it that way. And we've got Tom who's our public sector liaison as well so it's his job to reach out there. Corporate initiatives, this is about talking to corporates using Drupal and also agencies to some extent. We haven't done a whole lot here but the user survey is part of that. All right, so how can we help you? How can the committee, what can we do for people who are interested in being involved? Primarily outside of running the events and organising the events we provide support for camps, meetups and other local events. So we talked about that a bit already. We are looking at ways to support the Drupal market and share marketing around Drupal events. So I think just this morning we talked about putting up a shared channel in the Drupal South Slack. So if anyone's promoting any Drupal events or any of their own events that are Drupal related locally and they want a bit more wide press for that they can share it in the Drupal South Slack and we'll retweet it or push it through Facebook or whatever just to amplify your message a bit. And less useful for you guys I think but if you're looking for training or services or other providers then we can help you find those. Useful dates. Okay, the next steering committee elections according to our calendar are July 2020. So that's the first thing if you're interested in standing for the committee that's likely when the next elections will be. And the next Drupal South request for proposals probably going to be spring 2020. We haven't actually discussed this but that seems to be the logical date based on our current calendar. So what do we look for when we do a Drupal South request for proposals? We've done this once already and Owen ran that. Do you want to talk briefly about that? That's all right. I was actually trying to see when the keynote was on. Who would be interested in running a Drupal South? Yeah, what's your name? Nigel. Nice to meet you. So I think as Chris said, we view this committee's role as supporting local teams to run regional events without as much self-sacrifice as may have been required in the past. And I think credit to the team here they did do quite a lot of self-sacrifice because they were already in motion by the time that we formed the steering committee. But one of the ideas that we've put forward which one of the next organisers already jumped onto is to budget for an actual event facilitator slash coordinator to do a lot of the kind of grunt work of printing badges and doing ticket refunds and that type of thing. So we do want to elevate the local organisers into primarily a strategic role of content and programme formats and liaising with great keynote speakers and running really interesting workshops and that type of thing as opposed to being the ones that are actually pressing the print button on tickets and that kind of thing. So I think in terms of future events, we still want to have a back and forth between New Zealand and Australia as much as possible and that might be on a year for year basis. It might be in Australia for two years and in New Zealand for one year. We'll just kind of take it as it comes. And I think the considerations are great venue, location that's relatively easy to get to. I know that all the Kiwis had to get up at three o'clock in the morning to get here. It's not totally ideal, but I think something like Hobart counteracts that in terms of it's such an amazing location. So location is key. And then the big focus is on managing speakers and that type of thing. Does that kind of cover what you wanted me to talk about? I suppose so, yes. I mean, if you are interested at all, come and talk to us and we'll give you more information, I guess. Yeah. Any questions on events? Is the location of the Drupal South dependent on who's organizing it? So ideally, you would have people on the ground in the location that you're running it unless we run one in Fiji, for example. Definitely a possibility. Direct from most capital cities. Yeah. So I mean, that's definitely a consideration. I think the learning from the Drupal Association globally was that they really could not run successful Drupal cons in Europe, unassisted by a local team on the ground. So that's why they've gone with that model of having Coerney. But there might be some ideas that come out like a Fiji or some kind of really interesting location where it's like that makes total sense. Let's do something like that. The other thing I'll mention around events is Chris mentioned kind of summits and in one of the boss, we started talking about actual focused dev days and those types of things. I think the model that we're most likely to go with for that would be a professional facilitator for those events with some local presence again and non content expertise, that type of thing. So we're running a Drupal Dev Day in Sydney, Murray and the need up organisers may play a key role in that in terms of speakers and running workshops and that type of thing. So the message is that these events are where we all come together. But then I think there's a lot of opportunity for individual events that are targeting specific audiences that either don't get a huge amount out of coming to a big group event like this or have really specific needs. So people that are new to Drupal, really highly experienced developers, decision makers, all of that type of thing. We want to be able to have forums for those people to be able to interact. I should stop talking here. Yeah, so we I think our aim is to pick a good team regardless of the location and then make sure that they've got a good venue for the kind of event they want to run. And we're open to the kind of events that people want to run. Obviously, the only thing we really can't do is run the event. So if you come to us and go, this event is really cool, I want you to do one, we probably won't do it. But if you come along and say, this event is really cool, and I want you to help me do one, then we'd be very open to it. Yeah, I'm in a great example be run a women in Drupal event. Okay, don't run a women in Drupal event. If you chose to. Yeah, sure. I'm nearly done. So how can you talk to us? Well, you can talk to us here. And if you can, you can call us at any point in time, you can reach us through the email address, say hello at Drupal South.org. You can use the contact form. You can email us personally. I think most of you probably know us anyway. And if you are engaged in any kind of local Drupal community coordination, you can get into the Drupal South Slack if you're not already on it and participate in there too. So we do a lot of kind of coordination and organization there. And you can get an invite from the Australian Drupal Slack if you just ask or just ping one of us. Finally, and this is really important, we do handle code of conduct reports for our events. And we follow basically the Drupal code of conduct. We do have a copy of this adapted for Drupal South on our own website.  And we have two dedicated code of conduct officers, Pam and Tom. And when a code of conduct report comes into that email address, they see it and the rest of the committee doesn't. So that's a we're trying to follow the best practice that we can for this. And I think have both of you done the training or just just Pam. So Pam's also done code of conduct training as well. Do you want to talk about that at all? Yeah, I should. There's a company called OtterTech that the Drupal Association has engaged with to run a workshop in how to handle code of conduct incidents. And I participated in that. I think it was last week. And it was really interesting. I was a bit skeptical, but it was really informative. It just kind of talked about empathy when talking to both the reporter and the reported person and, you know, strategies for dealing with tricky situations and ways to mitigate things and just kind of how to treat, you know, first complaint, then sort of escalating and how to kind of how to consider something resolved or, you know, just anyway, it was really interesting. So I did that with a couple of Drupal Association people. And yeah, it was well worth it. I think we haven't had any complaints at this event though. So all good. One more party to go. So we take this very seriously and we have as a committee handled a couple of complaints in the last 12 months. So, you know, it's been a bit of a learning process for us too, but we do take it seriously. So yeah, good Q&A. Hi, I'm Heike. Now I'm hanging out on these events since Drupal South, if you don't even know, it was called Drupal South in Wellington. And in 2014, I've organized code sprints. I've organized the Drupal cards. I've done lots of things. And what I experienced, I wasn't in Canberra last year, sorry, but I've, I've, oh, sorry, you record me. Oh my God. Okay. You can complain about the code of conduct later if I go overboard. Okay. So I know most of your faces, maybe after all of these years, you know my face. This is my first problem. We are talking to each other all the time. Like it's the same people all the time. Now I was sitting in the keynote yesterday and we can think about this keynote. We can think about the keynote, whatever we want. But I was under the impression that she's preaching to the choir. But when I look at this, I think she isn't. Because if we want to have, sorry, that's really getting me here. But if we want to have days like women in Drupal, or Drupal death days, or Drupal South, or Drupal whatever, then we just create silos. Yeah. We need to collaborate. I mean, this wasn't rocket science what she said yesterday. It was like very like stereotype. And I thought like, Oh, okay. I actually think that the coder is the hipster. He has more tattoos. So I'm just, I'm just like, I don't understand why we, why we are not trying. So for example, just a tiny example in Wellington in 2014, we were just running and totally Drupal code sprint for Drupal who never seen Drupal. Yeah.  They got these, was like a game board and they could play the game and move around and stuff like that. And it worked next to your sprint at this time. You're like, you can do your thing and we can make room for this. And then, yeah, so how, how, how do we actually get out of this silo? It is about Drupal and I don't want to make it not about Drupal, but can't it be about more? I don't know. I mean, we want to, isn't, isn't what we want to do in the end do great websites? I don't. No, I, I, I, I guess I don't know what. Yeah, I, I must, I, when you say the silos and you don't think we should do dev days and you don't think we should do. No, I don't. Oh, is that not what you're saying? I guess I, I don't completely know if I know what angle you're taking. And I, I have thought a lot about this over the past few months. So Drupal South will always be the coming together. It's our signature event. It's the opportunity for us to all see what's happening in different parts of our community and ecosystem using Drupal. A lot of feedback that we have had though from buffs that we've run over the last couple of days with sponsors and with community organizers, who else did we run a buff with? So some of the feedback is if I'm a really experienced developer and I'm coming to Drupal South, I'm not necessarily learning things because things are usually at a relatively high level. level and not doing deep dives. I might get at that at the sprint if I'm participating in that. But I think something that Murray said before in the bof was that when they get together in meetups, it's a lot of people who are very experienced who sit around and just talk about deep Drupal problems. If you put someone who's a beginner near to Drupal, who's not a coder, who's a business decision maker etc, they're not going to get much out of those conversations but the really deep developers do. And so having a forum for those we view as being a potential. Yeah I'm not against code sprints. I just want non-developers go to code sprints. Yeah so I think I want non-developers go to code sprints. I've been on a lot of code sprints. So just to go back to what I first said Drupal South will be that but we have identified that there's really key audiences that we're not reaching at the moment or not having a dialogue with whose meet needs aren't necessarily met. And so another example would be business decision makers aren't necessarily coming to Drupal South. They view it as arts to techie, everyone's talking about coding. So there's definitely an opportunity for us to facilitate a decision maker summit where we're talking about Drupal at a very high level as a digital experience management platform or whatever where we're actually positioning Drupal as a real option for them to consider when they're talking about their next budgets. So one thing that I have said repeatedly over the last few days is there's no one-size-fits-all approach. We've got a lot of ideas. We can only initiate so many of them and one of the processes that we've gone through is to prioritise based on need, impact and effort. So if something has a clear need it's going to have a high impact and it's a relatively low effort for us to implement. They're the types of things that we'll start doing early on.  Does that kind of answer your question? I do a lot of consulting. This still looks very from the inside out to me and not from the outside in. I'm just wondering even with the business people, if the problem is that they don't feel that this is something they should go to, why isn't there a business forum that just happens at the same time that Drupal South happens so that they can actually see that we are not all nerds. Nothing against nerds are cool. That's definitely an option. They did run something like that in Seattle where they had a separate business track and my view is that it was quite a big failure. So it was really siloed off from the rest of the event. There really wasn't a lot of interaction. The content that was being talked about there really wasn't that well attended. So we can try different approaches, see what works. We're totally open to experimenting but I think just getting back to what I originally said, Drupal South will be an opportunity to bring a lot of people together but there's opportunities for us to be really talking more directly to people that might not otherwise come to this event. I think also this year there was a little experimentation so largely the same format but Vlad just decided to run some workshops and that actually he wasn't sure whether anyone was gonna show up and lots of people did show up. So that was a huge success and I think his feedback was we should definitely keep doing that because it's a way of attracting people that might not otherwise come. So I think also part of it is like if you feel strongly that there should be a business day at the next Drupal South then you know just kind of start the conversation. This was just an example of what he wants to silo and I just said whatever you want to silo I don't think it's a good idea to take it away from the synergy of this event. So we just basically like there's only so much attention and so much synergy in something and if you split those things the synergy stuff things happening people. No I know but I'm just saying the the conference is it's organized by an organizing team that all volunteers and all bring their own ideas so if you know if we decide that running a business day like to be honest with you I think getting those types to fly to Hobart or to fly to wherever it may be is a bit tricky so maybe we start with running one in one of the major cities see how it goes or again if you know if the people who are organizing the next one feel that there's a big business community that might be interested in that just run one but but the thing is that you know Campbell and his team didn't have the bandwidth to add another thing that's why like I said Vladimir came in and said I want to run a workshop he ran the workshop we have no complaints here like yeah no I know I'm saying though I'm saying that it's it's not about us telling the committee that the organizing teams what to do it's about the organizing teams doing what they have the capacity to do and coming up with ideas and us helping them achieve those but we're not here to tell the cities and the teams what they have to do and what format they have to meet we so that I mean I think when you said it's inside out rather than outside in ideally we are having a bit of outside each time like you know Campbell's relatively new to the community he came to Canberra to learn how it all worked and learn the ropes and I think he brought a fresh perspective so I think that yeah it's really definitely not us trying to tell the community tell whoever that this is how it has to be or this is what we want it's about us finding out what the community wants and then having the the framework to support it more than that well that's how I hope it works out it's only new but that's what I hope happens yeah okay that's exactly what we're sort of trying to achieve just to have a bit of a framework so easier for other organizers and then if you decide to do a business day or do a woman in tech or do an event then at least as templates you can use to make it easier for you because a lot of our companies invest a lot of time into us for organizing events so I think if we can reduce that time that would be I think that's sort of the ideal yeah I mean one of the things we have to look at as well I still remember that decision of actually running Drupal South in a weekday you know way back when and we're actually really privileged to be here on a Friday you know it's a work day on a you know another city our work allows us to do that and so a lot of these smaller events are critical to building this community because there's still what 270 here which are you know really lucky but there's a lot more in Australia New Zealand so we've got to have or you know we've got to build this community and make sure we're all inclusive there but what you're saying with non-code is going to code sprint events I was in Amsterdam I think it was one of the first ones they did it but they had a huge section of the sprint day dedicated to non-developers and it was really really successful so I mean that's something we can we can do here and then be guided by you know what's happening in the bigger community as well. I don't want to I don't want to steal the whole discussion but one more thing I'm sorry I totally got misunderstood this when Owen said that we're going to do this I think what you should or this is just a suggestion feedback I will send it via email if you do something like this it should be like there should be nothing else going on don't you want to talk to everybody like shouldn't this like for it shouldn't this like more of a kind of a panel thing. It is a panel.  So do you see I saw I saw stuff that you want to work with the Drupal association and Drupal cons and all of us but what do you see as your other opportunities to just not make this between us all the time like how do we get more people. Do you want me to answer this one first. So the last few months have been this kind of broad spread of ideas of where should our focus go. And I think it's it's come down to there's a Drupal product awareness component to what we need to do. So whether we're promoting Drupal into other open source communities into commercial environments so whether we're actually kind of running a generic Drupal sponsored boo that a key event that type of thing to raise product awareness and the Drupal association is also putting a huge amount of work around that. So they've got a dedicated marketing director. There's a lot of work being done around Drupal product marketing that we can all leverage. Another big component is reaching people that aren't using Drupal. So we've done a lot of talking a couple of buffs around how do we reach university students and demonstrate that there's a clear career path for Drupal implementing things like internship programs that they can move into more consolidated training materials and ecosystem for independent providers to do Drupal training. I think there are a couple more people who want to ask questions but I will say that's it's on the radar of things we want to address bringing more people in. We don't have the answer but it's one of the things that we definitely want to do because we don't enjoy just staring at each other. And then the final thing that I'll note is that we know that there's a huge number of Drupal users who are now working embedded in large organisations that we have no contact with as a community because those people turn up for their day job, they use Drupal, either as content editors, they might even be developers and it's just what they use at work. And I think there's, like I said, there's a different way of communicating with that type of audience in terms of content that would attract them that's not based on a sense of it's a Drupal community, it's I'm doing something with Drupal that's advancing my own career and by exposing them to Drupal and the community through those outreach programmes which are yet to be defined, you're then broadening the opportunity of people then starting to engage and that might be at a co-contribution level, it might be attendance at events like this etc etc. So did you want to go? I've forgotten your name. It just goes back to what Tom was saying I think about the code sprint and it just triggered a thought in my mind that I didn't notice a coder's lounge, I know there was the quiet room but it's just occurred to me that a coder's lounge has been absent from this year and maybe last year as well and I don't know if that's a facilities thing Yeah it usually is. So the number of rooms that are available in any given venue determines essentially what can be done there. I don't know, yeah we only had one bathroom, I don't know if there's other ones here, so I'm just going to answer that question. I do have a quick thing is that I feel like it's often a case of how much space we've got, we've actually got a lot of space here. There's actually a lot of places people can break out so sometimes it's something that's practical if the venue is kind of squishy but no I actually have a follow-up question. Sorry just the fact that it's not necessarily just coders involved in this process anymore and the DA is really pushing that fact is that I want to make it more welcoming. I'm going to do some photography outside again but I wanted to make a comment that it's really what I've really found really interesting is that Campbell's journey from two years ago going to Drupal South Auckland to running a conference has been quite incredible. We haven't been overly involved in pushing him in terms of guiding him other than the questions he's asked so a lot of the support he's got has been from the existing community. So sometimes I feel like the steering committee is just about formalising what we're already doing pretty well. I don't know how we're doing it well but we're doing it pretty well so yeah so I like what I hear about we don't need to make it top down. We want to get the Campbell's doing what they feel passionate about and bringing what they bring into it but then saying I need help. I need help for this, this and this who's done it before and how we connect those people up. And now we have money for it too so when you guys have ideas and you need help we can actually help with money now rather than just like cheerleading. So I'll be really quick first of all I just want to say I acknowledge that you guys are all volunteering in your own time so thank you for doing that. And I wish if I knew more of the people who were doing the groundwork like Campbell that we could say that to them as well because I feel like that's a thankless job and probably hasn't received enough recognition. My question however is why Linux Australia and what value is there in that relationship versus being I would have assumed that that would have been a Drupal Association top level sort of relationship. Sure that's a good question. There's a number of reasons. Firstly Linux Australia actually does a really good job of supporting open source communities in general. It supports us, it supports WordCamps, PyCon, Laravel, a whole bunch of stuff and what it does is it provides financial governance, insurance, banking and also a giant pool of cash in case somebody has a massive screw up and messes up an event. I think they have basically a slush fund that sits there for emergencies. So they're providing a guarantee essentially around delivery that's very helpful. They also understand this kind of event and how it runs in this country and then that's really useful. So as a supporter they're a great supporter. They're fairly good at what they do. Their business is supporting these kind of events and in return we give them 6% of gross income basically which is actually not a whole lot. It's a relatively small amount of money from the event and it's factored into our budgets quite easily. Okay good that's clear. Thank you. Yeah the Drupal Association has toyed with offering that level of support in the past. We've had some events in Australia that have run associated with the DA but it's all done through the US. It's all in US dollars. It's US insurances and then it's not practical for them to do it. So the model that most local Drupal Associations have followed is to incorporate themselves.  Let's facilitate collaboration, common best practices etc etc. So they're more facilitating at that level as opposed to getting directly involved. We've got about 10 minutes. Well, any last questions or comments? Oh thank you. Thank you for coming to Drupal South. Wouldn't happen without people coming. Fiji.


It is day two of the Domains Workshop, and I am really excited about all the stuff we've been talking about so far. It was very fun to sit in on, watch your troubleshooting session with Amanda earlier. That was really great. Yeah, it was fun. I don't know that I've done that one and actually had a broken site to fix, which was kind of cool. I mean, to be fair, I broke it. Like, I knew what was wrong with it, but it was kind of cool to be able to demo that because the amount of times that we just need to go in and help people disable a plug-in is, I won't say, I said frequently and that's not really true, but it's probably the most common, like, serious WordPress thing that I have to do. Yeah. I would say less than, oh, this happens very frequently. It's when something like this happens, that's frequently the cause. Exactly. Yeah. I mean, now we're going to sort of move over from that to long-term management. So the troubleshooting is sort of short-term in the moment user comes to you with an issue and this is more about planning the future of your project and about growth. So we're going to cover a couple of things. We're going to sort of clarify the process, what that looks like, and then we're going to move into talking about how you may want to decide and set policies on things and then we're even going to talk about more specifically about some of the tools that are available to you. So we can just sort of hop into it. As Taylor is showing right now, we have resources available in our documentation about how to, just what different things you may want to look at, what you may want to consider for account cleanup for that management process. So there's just language around, if you want to be consolidating servers, which we do have some schools doing, as they deprovision, they say, oh, maybe we don't need as many servers as we have currently.  Just a sort of general quick overview of how the process works. I believe we have an article on that, as well as a couple of other things, just useful things to know and sort of sometimes a little bit what a individual user might need to know. But we're also here just to sort of talk about that with you today. Yeah. One thing I really like about this is that it does include sample language. That's drafting emails to end users and you mentioned that, but I think it's a really good, I don't know, I think everyone, I certainly do, but I think most people suffer from the blank email draft, right? So having something to work from is, I think, really valuable. So something that I wish I would have referenced when I was an admin. It totally existed. I just didn't bother to look for it. It's certainly very, we do try and encourage communication throughout the process and we definitely don't want anyone to just sort of be sitting there staring like, what do I say? How do I start this conversation? That's what these resources are for, basically. So just getting into the steps of the process. The first main thing to know is that in terms of the technicals, there's two steps, basically. There's suspension and there's termination. So in the WHMCS session earlier, we talked a little bit about the tools for suspension and termination.  We can use me as a little example of what suspension and termination looks like. So in the products and services tab, you'll be taken to one of my, now several accounts because I keep accidentally, accidentally on purpose. I decide to do it and then go, I should have done that, terminating my accounts. So yeah, Taylor is showing you right now the suspend button. And so the suspension, the suspend button suspends an account, exactly what it sounds like. And what that does is it makes a site unavailable. It takes it offline. So the data is still on the server. The site can be restored with the press of a button on suspend. It's still there, but it's not, the user who owns the account can't log into it. And people who are visiting the site on the front end, there is no site. They can't see it. Yeah. So right now, this isn't a perfect example because of course, pilot just made this for test purposes. There's nothing here. But this is an active account, right? This is an active account with sort of nothing in it. If I wanted to, I could log in and drop files. I could install something and populate it. Yeah. And when we hit, you can even see that if we hit the login button here from the WHMCS side. There we go. There's a cPanel account. Right? Yeah. So if we are to suspend my account, Taylor, if you can just go ahead and do that. The reason is for kicks demo, doesn't, yeah. Don't worry about it. It's fine. So then the, and Amanda is pointing out in the chat that suspended accounts do still count them against your domain of one's own limit. That is one of the things that we want to talk about that might maybe take them. Yeah. But so the idea being it's suspended. It's still there. It's still on the server. And as we talked about yesterday in WHMCS and maybe in WHM as well, suspended accounts because they're still on the server still count towards that total number of cPanel accounts on the server, which is what we're looking at. But we're not going to do this quite yet. But the terminate button, the terminate module command, which is also here in WHMCS changes that rather than suspending an account terminating the account takes it off the server entirely. It removes all the data. Users won't be able to log into it because it's just no longer there. Totally gone. And that is harder to walk back. It's not impossible. We keep backups for 30 days after termination just in case. And we're also happy to help you push those backups to a third-party location that's owned by the college. So if that's your AWS bucket, if that's Google Drive, that's Dropbox. We're happy to work with you on that. We definitely have schools that do that. But that's the difference between suspension and termination. I like to point out, too, here. It's not maybe not super important. But I like that they're color-coded in WHMCS. Terminated accounts are red. And suspended accounts are, they look green to me, but I'm weird with green and yellow. I'm also seeing green for what it's worth. So I don't love that color-coding in terms of green. Green seems positive, but it's kind of not. But that is color-coded there. And in WHM, it is color-coded there as well, but it's differently color-coded. Yeah. So if you hop into list accounts in WHM real quick, you'll see we have 140 records. And that's my account right now. We just suspended it. So it's in red. So there's 140 accounts on the server total counting towards that limit of 500 accounts on the server. And this account suspended so it can be marked. But it's still in this list. If it was terminated, it wouldn't be in this list anymore. It would just be gone. And so those are really the two fundamental principles of what deprovisioning is as a process. We're going to go into that and sort of complicate. I say complicate the process a little bit. Talk about steps for managing that process and considerations that you may have starting now. Which is basically what that means is different schools set different policies around when they want to suspend, when they want to terminate, when they want to get rid of an account. And that just comes in different forms, basically. We have schools that say, this is a sandbox project. When you sign up, you get one year to use your C-panel. You get to experiment with it. You get to do whatever you want. You get to learn the tools. And at the end of that year, it goes away.  And if you want to take it with you, you can move that day to somewhere else. Migration's super easy. Another thing we're going to talk about in a minute. But we are no longer going to host that account for you because we want to cycle it out to make room for someone else to learn. We also have schools that say, listen, we're happy to keep this for you for while you're studying with us. But once you graduate, that's it. It's going away. We have schools that say, when your email account expires, when you can no longer sign in with single sign-on, that's when it goes away. So there's just lots of different ways to do that. And there's different tools for gathering that data. Some schools just say, hey, if your account hasn't been logged into in eight months, a year, whenever, we have tools for tracking last login. Talk about, I keep saying this. Talk about this in a minute. But if your account hasn't been signed in, you have 30 days to sign in. And at that point, we're declaring this abandoned and we're going to suspend it and get rid of it. So in keeping all that in mind, that's really the first thing is to figure out what criteria do you want or does your team want for your school? Like what criteria can we use to determine what accounts we want to get rid of? That's step one. Figuring that out. And if you need figuring out what help to access, like what data you have access to and all that kind of stuff, we can definitely help you. We're gonna feature some things right off the bat here that you may want to look at. But that is the main thing is, okay, what accounts do we want to retire and what is our criteria for that? Some schools do very of a combination, right? They're looking at like, we're gonna look at this and this and this and then we're gonna email everybody and if we get responses back, we'll let them keep their account. That is probably a lot of manual work at that point. But it is an option too if you wanna be moving in that direction. I'll say when I was in the admin, it was just pretty straightforward. Like if you were a student who graduated, you got your account for a year after you graduated and at which point we were gonna retire it. And if you were a staff member that left the college, pretty much as soon as you leave. So that wasn't, I wasn't retiring accounts all the time but we would do a check-in once a year, make our list and say these people are no longer here. These people graduated more than a year ago and we're gonna mail them, let them know what's happening and then do this a month later basically. Yeah. So once you have those criteria, there's, Taylor says like we set timelines for when people leave the institution, there's defining the last time an account was logged into, is it being used? You can also look at the disk usage. So if an account has two megabytes of data on it, 10 megabytes of data on it and it was last logged into six months ago, you have a pretty good case for a blank account, something like that. And again, there's tools for how to get this information and that whether it's internal, seeing when did someone leave by institution or working with Reclaim to say, hey, how do I get the data for usage stats? And once you have all of that, then it's a good time to start planning your communication and your timeline. So this is again, this is part of why we encourage schools to think about this in advance, to think about the policies that they wanna set before they end up going, oh man, we're almost at our limit. I guess we gotta clean up fast. And so what this looks like is saying, when do you want to have these accounts suspended by? And when do you wanna have these accounts terminated by? How much warning do you wanna give users? What options do you want to give users?   After that, you have two months to come to us and say, can I please get backups? Can I please take this data away with me? Can I please migrate it to another service? Because CPanel is industry standard, you can pick up your account and take it with you and drop it pretty neatly into an account with pretty much any major hosting provider, anyone who's following that standard, including Reclaim. And we do offer migration options for Domain of One Zone. That's part of our language around those migrations that we have in our documentation. And students basically just need to sign up for an account with us and let us know that they want to migrate their stuff and we just do it. It doesn't cost them anything for the migration. So it's a pretty, about as seamless as possible process if you go with us, but yeah, because it's CPanel, you can go in almost any direction, any CPanel host, the web host that does CPanel, we'll be able to take a backup and in most cases, be able to restore that pretty seamlessly as well. Yeah, exactly. So this school says, all right, we're giving you six months notice and then two months to get in contact with us afterwards if you decide that you do want to migrate and we'll give you your data then. And then they check in six months, four months, two months to graduation. Probably another email around graduation time saying, remember, this is gonna happen. If you want to prep now, prep early, let's do this. We're just periodic reminders. That's a lot of communication. We actually have tools to help you manage that communication in WHMCS. So we showed you that suspended account tool, that termination account tool earlier. Taylor, if you have that up, do you wanna show us? It's called email campaigns. We actually talked about this yesterday in the WHMCS session. We're gonna go a little more into it these days. Yeah, it's under utilities in this version of WHMCS. It's called email campaigns, it's under utilities. In an older version of WHMCS, it's under clients and it's called like mass mail. Yep, mass mail tool. It's otherwise the same for mobile demo. It's just located in a different spot, basically. Yeah, so if you create a new campaign, the campaign name is we're getting rid of your stuff, account cleanup, whatever you wanna call it, Taylor. And the email type is just general. Product, go ahead. Well, and I wanted to kind of mention what these are here too, because they're always super handy for, but there is some kind of nice things in here. So you can go by product or service. General add-on is probably not gonna be super relevant for any of our schools, but domain, I think is also interesting if you are a school that has top-level domains, you can actually email folks based on the status of those top-level domains as well. But product and service can be nice if you want to do, if you want to do something like I wanna email everyone who's got a suspended account, you can totally do that with product and service and say, yep, let's make sure people that have a state U domain that also have a suspended account, we're gonna email them. But probably most often, you're gonna be doing a general email. And then we don't have a client group right now, but a client group is how you can configure the list of people. Yeah, you say everybody who is, for example, in the class of 2023, here's your notice, you're getting these emails, we're putting you in a client group that says class of 2023, and then we're just gonna be emailing you based on your class here. And how does the client groups get set up? So the client groups get set up by us, basically. You can set up a client group in WHMCS, but like managing suspension and termination, that's also something we take care of. You can send us a list of names and emails and we'll go, all right, these names and emails are now in the client group. We would be matching based on emails, so the emails are very important, but this list of people is now in the client group. And then you can just go in and say, all right, class of 2023 client group, we're putting you in here, you are now gonna be the ones receiving these emails. And then you can talk about, in the email, you can talk about timelines, you can talk about the migration options, just based on the language that we already have written in the documentation. If you go for compose message, this is not gonna send anything until we absolutely say send it. I don't know how you found me, that's great. Well, I did, like I said, I use that suspended one so that we can actually send this email to you in this case, so we can kind of see what that looks like, but most often, if you're just doing a client group, that would be the people in the client group. I do really like that it will give you that preview of this is who we're gonna send it to, so. Yeah, and then you would just put in the subject, you'd put in whatever you wanted to send me, getting rid of your stuff. And what this also means, I believe, because on the last section, we also said, like, here's the name of this, I believe this is setting a template that you can later come back to and reuse. Modify if you need to, duplicate, but. Yeah, and you can actually, so we'll get to the compose part here, but there's actually a lot you can do in here, so you can save drafts from within here. You can schedule if you don't wanna send it immediately, which is super handy. And you can also save the message, and this is what would save that template for later. So if you check this box, when you hit either save draft or send campaign, it will save the message, and then you can actually bring up past message that were saved from this list down here, which is really handy for future occurrences. Yeah. Oh, Amanda's saying you can also upload a previously created template at the very bottom. At the very bottom, I assume of load saved message that would be an option. Oh, load message. I'm not sure where this tool is, but one of the other things is that the, I believe the merge fields is you can personalize these. You can say, dear name.  So I grabbed the first name field. I won't use last name for now. Probably I want to have one that is the company domain. I think company domain is probably correct. This is something we maybe want to document a little better. Yeah, sure. So I'll make a note of that right now, but just the general idea is if you've ever used mail merge, things like that, where they let you create a blank field that auto-populates based on who you're sending it to or auto-populates based on fields in a CSV or something like that that you're using as a resource. This is exactly like that only. You don't need to have a CSV. You can just say, fill in the blank. I know you have this account information somewhere in here, WHMCS.  Yeah, I'll put it in Discord. I got to look after this, what field it is that you need for the domain name because I know you can do that, but I'm not seeing that here. It's probably something to do with the way our state UWHMCS is set up, but I'll look for that afterwards and confirm in Discord if anyone wants that information is suspended. So obviously you can draft your whole message here. We're getting rid of your stuff. I forgot that I had loaded that blank template. Yeah, one thing to mention is that there is a distinction between marketing email and not. So if you use WHMCS to send out emails to say everyone with an active account to say like, hey, you can get help with domain of one zone by coming into our office over here in these times or making an appointment or something, they can opt out if you check that box. If you don't check that box, they'll have no option to opt out. Super handy if you want to give people that option. I'm personally of the philosophy of you really got to strike that balance on email otherwise people will just tune out anyway and maybe that battle is already lost, but that's a really great option. Yeah, we also just quickly recommend sending a test email to just you, maybe another person, like if you set up a small client group that's me and two other colleagues and just to check that the merge fields are working, that there's not any typos, just like putting that in can be really useful. And with that, I think we're probably ready to go. You can send that because it's only sending to me. And that's, it's working on it. And just with that, we've covered basically the mail tools that we need. And then the only steps left would be the, the deadlines for suspension and termination. So you would say, all right, people graduate on May 20th. We want to suspend everything on May 31st right away. You tell us that we would set up a option we would set up a note in our schedule to say, all right, run that on May 31st. And that's when we would run those suspensions. We have a script. If you give us a CSV with emails, our current script matches on email, so it will suspend all accounts for users with that email. I think we're working on a script that will match based on username if you want to suspend specific accounts in the event that a user might have multiple accounts. That's not a super common scenario. It is possible. But so we're, that's something that we have in the pipeline. But we have the scripts. You don't have to go through and manually suspend things the way that Taylor manually suspended my account. You don't have to go through and manually suspend everything that would be a nightmare. You don't have to terminate. So bring that information to us and we are happy to take care of it for you. We have covered just about everything except for the ways to gather that data, which Taylor, I know you had a couple of thoughts on and we have a couple more minutes before our next session. So I think we should just get into that real quick. Sure, yeah. We can show that there's a report that we have on our servers called Last Logins that if you ask us for, we can send to you just a upon request. It's generated once a day and stored in the root account of the server. So you can also get it off by logging in to the server as root or using an SFTP client. But for a lot of folks that's maybe not something they want to deal with. So you can also always just ask for it. But this is what it looks like. And let me make this larger here. You may want to make it even just a little bit bigger Taylor if you can. Yeah, for sure. This particular application is strange. Anyway, so, but this is what the actual report looks like. So you've got your Last Login Date, your username, the email address, which I have replaced because I don't want to display everyone's emails on state U, the domain name and the disk usage that they currently have. So you can, because as you see of course you can open it up and sort it, do all kinds of things like that. And that disk usage is measured in megabytes. So earlier when we were talking about accounts that have two, three, 10 megabytes worth of usage, you can sort and say, all right, show me lowest to highest and we're just going to drop everybody who's below 30 megabytes worth of usage. Yeah, the, so that's super handy. Looks like that's running alphabetically instead of by value. Yeah, this particular, I should not have opened it in here. Hold on, let me use like a real actual program that people might use. Okay, so, but of course like, I have this in numbers right now but if you're an Excel person, you can do that, you can do Google Sheets, all of those are fine. But it's super handy to be able to have that disk usage, I think in addition to the last login, right in the same place. Because keeping in mind, this is the last login to the actual C panel, right? So there are totally occasions where someone may log in to their own WordPress directly. And that's not going to be reflected on this report. Similarly, if a user is using SFTP to upload files, I've had, I've worked with users who never wanted, never cared to log in with single sign-on, they just wanted to set up an SFTP account on day one and then use that to upload all of the work that they were doing, writing their own sites, that won't be reflected in last logins. And that's also why it's important to have that suspension period, that period in between suspension and termination, because then if you're going based on last login date, you give an option, a period of time, for a user to come to you and say, hey, why is my site down? I am still using this. And you say, well, you haven't logged in since 2018. And they say, what does that matter? You ignored our last two emails. Yeah, exactly. You haven't been responding to our emails and you haven't logged in in three, four years. And they say, I uploaded stuff last week and that should be just good enough. I wanted to mention too that this report, I think also serves as a really great way to start off with something. So if you wanna send us a list of emails, you can easily start from this report and prune it down to just the accounts you wanna get rid of and send that back. And we can obviously go from there. When I did this, when I was an admin, I got a list of students that had graduated from the previous year from our registrar and I compared that against email addresses in Google Sheets and then used that to make my report. So that was a real easy way for me to do things. Yeah. We are just about at time, if not a little bit over, but I think we've hit everything that I had on my list. Taylor, do you have anything that you want to add? Not really. Well, I will show here, just cause we've got a 15 minute break, I think, between the next two, is that true? Yes, we do. We do have a 15 minute break. So all this in one minute kind of shows something we're working on that I'm excited about. This may take a little bit to actually become available and everything, but one thing that we are working on is a more accessible version of that report that you can just pull up at any time without having to do any SFTP stuff. Yeah, so currently the process for accessing that is to log into the root of the server using SFTP or to ask us to get it for you. Exactly. In which case we would take that step on your behalf. But this... But we're working on this and this is sort of a very rough draft at this point, but we're working on a version of the report that can be actually visible right inside of your WordPress dashboard and it's sortable and you can search it, which is really kind of nice. So you could see the same information but be able to get right to it here and then you can also easily export it as a CSV or perhaps other file types right from this list and get a download of it. You can even of course click right on the account and see it that way, which is actually really nice because right now in WordPress, there isn't really a good way from WordPress to see what their primary domain name is for a particular account. But there are some shortcomings here, like keeping in mind that there are limited things that we can put in this report right now. That's just disk usage and last login date. I think looking way farther out, I'd love to put more information and metrics in here depending on what we can provide and really grow this report out to be something even more useful. For sure. But I think this is kind of step one is we wanna make this really easy to get to and I think this is a good starting place to be able to even at least see the primary domain names for accounts and stuff like that, right from WordPress and all that kind of thing. Yeah, I do wanna very, very quickly add that it's being offered in multiple file types right now. Our scripts that we have for suspension and termination take CSVs. So we know that a lot of people like to work in Excel. So right now we're offering that option to download it as an Excel file. But when you send us the final list, just export it as CSV. Just export it as a CSV. That'll make it a little smoother. Yeah, awesome. I think that's all our steps. And it's important to remember like we listed out a whole bunch of things to consider. You are always welcome to reach out to us in a ticket and to say, I don't know where to start. I want help thinking through the process. So reclaim never wants to define the deprovisioning process for you because each institution is different. They all have different considerations and different needs but we are happy to help consult with you on that process. If you're saying, hey, I think this would be useful but I don't know if it's doable. We can talk to you and talk you through that process and say, oh, other schools have done it this way. What information do you have access to from your institution? How do you wanna go about thinking about this? As we're designing this process. And then once it's designed, you have a policy that you can run year after year and you've done all the work upfront and you don't have to stress about it. Awesome. Well, I think that kinda caps it up for this session. We'll be back in about 10 minutes for kind of a Q&A slash ketchup session. If there's any questions that you have that you want answered, feel free to put them in Discord and we'll also be covering kind of loose ends that have popped up over the last two days. So see you in 10 minutes. See you in 10 minutes. Bye.