 All right, well, so we're back being recorded. And we've finally made public the thing that we've been quiet about for quite a while. And that's only interfered a little bit with having to record these things because of all the discussions behind the scenes. But yes, our Regulation CF crowdfunding campaign is underway. So that's really great. We've been making really good progress on that so far in the one week since launch. Very happy about that. But here we are gathered to talk about development. So let's get into that. We've been pushing towards a first-pass completion of all of what we've dubbed the essential skills. And we're making good progress on that. I think one place where we've lagged a little behind is in pushing those updates out to all the people who have the mark twos. So that's our current focus is to make sure we're sharing all this great work that we're doing with the people who've got the deficits. So I'd like to start by checking in on that. And well, before the end of the meeting, I'd like to figure out where we are in terms of the next push that's going to have some visible changes in it. So but we don't have to actually start with that. Let's start with just updates on what people have been up to in the last little while. So Derek usually has a time constraint, so let's go with him first. Yeah, all right. So yeah, I was going back looking through where things kind of left off because I've been bouncing between Reg CF and hardware stuff. So it looks like we haven't got the GUI for the alarm yet in the latest, so I wanted to check on that. Otherwise, stuff I'm actively working on in terms of skills is the common play skills, the shared common play GUI, working on the different mock-ups for, you know, we talked about the Friday, like starting off internally, we're working on the streaming, the radio, the local using NB. And then I also tried to, I wanted to look at the common QA skills as well, but they're not quite ready for the beta install method. So I'll have to wait on that. I do have timer, which Chris actually told me I'll hold off reviewing on that as well, but I've got the beta of that and the weather. So I'm going to go through and just make sure there's no GUI issues first, but then any other issues I see as well. On the alarm skill, the version that Ken did didn't have the GUI in it, and so there's a PR waiting to add the GUI into the actual skill, but he wanted to test the skill control branch of his on the device. So I could rebase that PR and put it into both versions so that would start getting pulled in as well, if that would help. Yeah, I mean, either way, I just wanted to take a look at it, see where it was at. Yeah, I did test the alarm, but it worked pretty well for me. But yeah, no GUI. Whatever the best method to get it to a somewhere, we can review it while you and Ken decide on that, as long as it doesn't take too long. Yeah, I mean, we're reviewing the audio and the GUI interfaces separately. Yeah. Yeah, like Derek said, whatever works for you guys. I think this is just the challenge with the skill control thing, is that we have to maintain two versions of the skill while we're testing out this skill control stuff. So yeah, that'll be the same with what was the other thing that did that, NPR News. We have to, yeah, so anyway. Yeah. Well, yeah, maybe we'll wait till Ken can chime in and make it so I've got plenty of other stuff to do until then. So yeah, that's what I've been up to. OK, thanks. I guess you want to go next? Yeah, given I'm talking anyway. I spent the day mostly doing just merging lots of things. And OK, it's been very helpful in the last 24 hours at bouncing back on OpenPRs and reviewing things and submitting some fixes too. So that's been great. Everything's starting to merge in the fixes that we were looking at last week worked. So the Mark II skill is now updated so that the home screen gets switched over to the home screen skill, which, again, is not the ideal way long term, but it's the way that the current default home screen gets selected. So it is what it is. I also pushed through the Adich's improvements to the playback UI GUI. Sorry, so that's all now in there. And people can make use of the plugin that he did. For the GUI playback back end, audio service back end technically, but it also does video. So that'll all go in today as well for the build tonight. And I did the change Ken requested for making the URLs for the connectivity check configurable so we can now switch those over. But as I was doing it, it made me question whether switching it to non-https is really going to solve our problems because it might allow the connectivity check to succeed. But then if we then try to ping the Selene back end over SSL, it's going to throw a certificate error anyway. So but I think it's a good change regardless because it means that people can choose which URLs they and services they want to ping every time their device turns on and checks for the internet. So I think that's good. It could be better for offline users or for air-gapped situations which we've been looking at with some people. And yeah, so I still think it's a great change, but yeah. Yeah, I mean, that call definitely needs to be, I mean, the spec for that call needs to be, it doesn't return true until the network works, right? And that includes setting the time and all that kind of stuff. So that's the bigger change that Ken was talking about doing. But then it kind of got into a big area of having to pull out a lot of plumbing from different areas to make that work. So I think that's a good discrete step in the right direction, but we definitely need to come back to that and implement it properly and really define it. Cool. Yeah, we don't return yes when we don't really mean yes. I will still put in a HTTP-only URL just to like, at the moment, we can give it a test and see what happens. It's not really going to hurt anything and it's going to be very easy to change back as well. So yeah. OK. Yeah, that was me. Chris? So I got the day-skill GUI done after meeting on Friday. I spent today in just in the interests of what we were talking about earlier, I spent today looking at why the weather skill was causing problems when we tried immersion into the marketplace. And basically it was I had to go deep into VK land and I found an obscure bug that only gets triggered when you make changes to the feature files, which I did as part of this version. So the reason, so if you look at the report from the VK tests, all of the tests that in the skill itself failed are worked, but there is this lingering set of tests. And this goes back to what we talked about before, that the VK tests don't clean up after themselves. So the old weather tests, because they were named something different or lingering in the feature file directory. And those tests don't work with the new code. And that's why all those tests were failing. So I spent some time with, OK, this afternoon talking about the best way to fix it. So we have a short-term fix, which is in the Microsoft skills docker file adding a remove statement, just an RM of the features files in that directory before we get started. And then later, the test setup script will add them back in that way. Anything that's old can't be lingering around. The longer-term fix is that we probably shouldn't be running test setup outside of the actual running of the VK test. So there's a script called run test suite that really all it does right now is actually call behave. Well, it starts in the Microsoft, call behave stops in the Microsoft. Any test setup and cleanups should probably also be included in that script. Otherwise, you'll have something like this where you have artifacts running around, because you ran setup before as part of your docker container setup, for example, and have lingering problems. And then we're going to add a cleanups step also to the end that cleans up all the feature files that were added as part of that test. So that way, you don't leave any artifacts lying around and the whole thing. You're cleaning when you start, you're cleaning when you finish. And it'll remove some errors, not just from this, but from when some of the problems we were having before. Like just running tests on my device, where it wasn't cleaning up after itself. So I think we have a good longer-term solution. It's just going to take a little bit more time to do that. And I think it's also because of how we run the skills tests against a major release that we can make the change now, probably won't show up until 2102 or 2108. I'm sorry, because of that. So I'd like to see this change made before 2108 so that it does get pulled in, but it doesn't have to be done at this minute right now. My short-term fix will get our interests aligned where we can, with the short-term fix, the weather skill should pass at all its tests and it should be able to merge it into the marketplace so people can use it. So later on today, I'm going to note I have that figured out. I'm going to review Ken's PRs for the Q&A skills so we can get those moving as well along. And hopefully he'll spend some time on reviewing the timer skill and then it can get moved along as well. OK, great. So pulling up the big to-do list here, so it looks like the things that are deployed, nothing's been deployed all the way up to the stable branch so far. What's been deployed to latest is the common query Q&A and the volume and pairing skills are up there, but nothing else. So it sounds like we've got about three that Chris just talked about that should be ready to go pretty soon. And the pairing skill is on the stable branch. It's just not the UI changes that we've been talking about. The base code, the rewrite of the voice experience is done. OK. So then it has been running for some time and stable, but we have to go back and bring out the pass of the screens. OK. Yeah, let's see. The GUX says there's nothing in that column, right? So we have an agent. Yeah, we blank it out because there's some work that's still. OK, so OK. The skill control versions of things are in the latest as well. So that's like the alarm and new skills. But I have also been finding some issues with the new skill that, yeah, probably need addressing. OK, but yeah, I see that they're deployed in the latest build. So you had to use a, they're kind of hacked in there, right? You said they're not merged in the default branch. Yeah, because the code in them doesn't work on the mainline of the Minecraft core, so we have to inject them separately. They can't go into Marketplace yet. Right. OK. So it looks like the next couple of skills are to go up. Weather should be able to go up pretty soon here. We've got that fixed in. And you said that you're reviewing the timer stuff now. Yeah, next week we're going after weather. It'll be the common query stuff in the timer scale. Once those code reviews get done, then we can talk about merging them into the Marketplace. And I think the home screen is like a, I think I put in there, it needs a bit of definition of what we consider done for that one. So the base experience is there. I have to, I can't remember if the wallpaper changing feature got in there already. Yeah, I don't think I second pass at that because it's going to interact with the date and time skill changes. Oh, yeah, yeah. So I think when I'm in there making those API calls, and maybe I'll take a make us another pass at it too and see what else anything else needs to be. Yeah, yeah, that would be good. I'm in there. So my next thing after the date and time skills are ready. Gotcha. And since we haven't done this in a while, for anyone who may not know, I've part of my changes to the date and time skill are actually to split them into two skills because of the lack of overlapping logic. So that's coming. So that means that the current time and date skill will stay what it is. And there will be two new skills that will start to get used for the Mark II and we can deprecate the date time skill in favor of these new ones. Yeah, and either 2108 or 2202, whatever makes sense. Yeah, right. Well, people can continue using the old one if they want to, but the new ones are going to be better. So yeah. Right. So the definition we're using for what is done as far as this pass goes is that the skill does not return incorrect results and it does not return misleading results. So for example, it gives the right answer for a certain context. But there may be ambiguity about what that context is. So we don't want it to be incorrect or misleading. And so that's the definition we're using right now for what is done. It doesn't mean all the bells and whistles are in there, but it should be usable and not confusing. And so we've made it through pretty much all of these, all of the essential skills in terms of the audio UX. But a lot of them are still in review and then we've got the graphical UX to clean up them in most cases as well. That's everyone on the home stretch. Yeah. OK. All right. I don't have any software updates. We're continuing to work on the hardware side of things. We're still negotiating the contract with the manufacturer. The global semiconductor shortage is continuing to be a major pain, but we're working through that. And we're going to basically design around any parts that have long lead times that would take us out of our desired ship window. So there may be, well, almost certainly will be some revisions to the SJ201 and maybe some other parts as well. But as far as I know, we've had zero hardware complaints since the Mark II DevTits shift. I feel pretty confident that we know what we're doing now. And any tweaks we make should be relatively straightforward. So yeah, that's the only update I've got. So all right, well, we'll keep at it. And I'd like to, by the end of this week, for sure, get a build out that's got all of the skills that we have completed. So let's get those reviews in so that we can merge all the rest of the skills that have been submitted. And so, I guess, has enough time to do a build and get it deployed out to latest. So we can all start to play with those without having to do any kind of command line beta testing stuff. So all right. Well, that's it. Thanks, everybody. Get them on. Beautiful. Bye.