 Good morning everyone. Let's kick off day two of the hackathon for those of us in Europe. I hope everyone had a really good start to the hackathon yesterday. And for those of you who have been working for overnight for us, even Asia or Australia or the Americas, I hope you guys have had a really productive few hours. So quick check-in today just to go over some common points and get everyone ready for day two. So today is nothing special. We've got the check-in now. We're going to have your group check-ups, check-ins in Jitsi at lunchtime, as mentioned in the introduction yesterday. And then we'll have a check-out again later in the afternoon. So the check-out will be the main time where we go over everything that we've done today. There are a few things that have changed. All of the project boards on GitHub, where we're keeping all of the issues and things that you guys are working on. We've made a new column in there, or Kevin's made a new column in there called Done Tuesday. And automation's been updated. So hopefully as you tick off new things today, that will go into a Tuesday column and the Monday one will stay there off to the side. So that way it's easy for us to see what's new today, basically. With the hack and defiles, I don't think we've started this yet, but if you can make a note, when you add things that you've done, if you can make a note of your name and also whether you did it on Tuesday, that really helps us in the check-out meetings, because we can scan through those notes and see what's new rather than having to read through the entire document again. Otherwise, there's a couple of other things we're going to say. Yeah, as the pull requests start to come in more, as you guys are wrapping up work you've done, please try and dedicate a little bit of time to reviewing other people's pull requests. We need to get them in merged as well, and we need to check each other's code quality. That's kind of what part of what makes this community great. So please, for every pull request you do, try and leave two reviews on someone else's pull requests. That's a good rule of thumb. A few of you have been playing with NF Core Tools and some of the new things we've added there, especially with modules. As we said, a lot of that functionality is very hot off the press. We're literally kind of committed it last week. And sometimes you've been running into things which are a bit unintuitive, not obvious. In some cases, broken. So please, when that happens, don't just kind of think it was you that was doing something wrong or silly. Please make a note of it in an issue or something because if it's unintuitive for you, it's unintuitive for everybody. So we want to tweak that, add some documentation and change the log message, make it easier for the next person who runs into the same thing that's confusing. Of course, if it's broken, we need to fix it. Yesterday, we managed to collect quite a lot of bugs reported on for the tools package, which is kind of sad for me, but good generally, that you're all testing it so thoroughly. So that's a focus this morning. Definitely, I was hoping to get it out last night, but it didn't happen. The focus this morning is to try and fix those and do a hot fix patch release of tools. So that will hopefully be incoming this morning if I managed to get anywhere near a keyboard today. Right, what else are we going to say? Do any of the project leaders have anything that they would like to bring up and meet yourself and jump in now if that's the case? Maxime wanted to remind you all about the Spotify playlist. We've got a channel called the Spotify playlist where you can add stuff. Hands up if you've been listening to that yesterday. Some bangers on there. I've been enjoying it. I've even been listening to it on the car this morning. So if you haven't already checked that out, there's some good tunes in there. Add your favorites. Just in case you hadn't been aware of it, we had a few issues with some of the services we used yesterday. So if you were trying to access GitHub and got an error 500 message and you weren't doing anything wrong, GitHub had some status hiccups yesterday. There's something to do with our hackathons. Every time we have a hackathon, we're going to have a hackathon. We're going to have a hackathon. And the third time has happened. It's ridiculous. But hopefully we won't hit that today. Also key.io where we have bio containers. That was also having problems yesterday. Hopefully also won't be an issue today. So just in case you were having weird problems to deal with, putting containers or accessing GitHub, it wasn't you. I want to remind people we have the NFCOR Bingo still ongoing. So you can start again with a new board or continue from yesterday if it still, if your browser is remembered, you're a board. And yeah. So have lots of fun with that to keep an eye out for funny memes or tropes of NFCOR in the next floor. Yeah. And I'd like to say that those of us mentioned in the Bingo cards are open to being bribed to say the correct things. Very good. All right, I've run out of stuff to say. Does anyone have anything that they think would be generally of use to say? Shout now if you'd like to just kind of say hello or anything you came up against yesterday? Hello. Thanks, Arshall. Is there anything you want to say, Arshall, about DSL2? There was a lot of activity yesterday. There was a lot of activity. So we finally managed to add 15 modules yesterday, which is quite something given that a lot of, a lot of the people on that Slack had literally just dived into adding modules to NFCOR modules yesterday. So it seems like we're sort of 80% there with documentation and possibly functionality. But like you mentioned in the intro, we're still sort of missing stuff that we need to add. And if people can make a note of this and bring it up, it's most likely, like Phil said, because we've missed it. So it'd be great if we can fix it. Yeah, but thank you. More of the same. There has been some confusion around how to do the tests and stuff. So I was a bit unprepared this morning to sort of give an intro to that as he suggested, Phil, but maybe I can do that tomorrow morning to show how to run the tests for it. And then hopefully, because these talks are recorded, then it will sort of be a persistent link that people can look at to see how to add the tests. Well, maybe Kevin can do it. Kevin's a genius behind the code there. But yeah, more of the same, guys. Thank you very much. This has just been amazing. If you need anything to show. Yeah, and it's worth saying we've got the bite-size talks that I know a lot of you have been going back to look at. This is another good thing. If there's stuff like DSLT module testing is a great example where if we don't have time for it in a hackathon, but you think it would be useful to have some kind of resource, then please suggest that as topic ideas for bite-size. We're just finalizing the next batch of talks, which we're going to announce this week because the next talk is this time next week. But yeah, we're definitely open to ideas. So for stuff you think is a bit unintuitive or you'd like more information on, please suggest it. There's a bite-size channel in Slack. So that's a place to go. Great. Okay. If no one else has anything else, then I think we will go back to Slack. Keep chatting, keep working, keep hacking, keep contributing. We're off to a flying start. Really excited to see what we get done today. There's been some suggestion it might be worth having a catch up in Jitsi in your project groups right now. If you want to go over kind of what everyone's been doing in a bit more detail. I'll leave that up to all of you to kind of self-organize within the different projects. And otherwise, we'll see you later today. Enjoy.