 Okay, welcome back everybody. We are here for our developer sync. We've been out in Hawaii for a while and we got some really great work done. We're gonna resume our daily stand-ups and here we go. So let's start with Gebs. Hey, so Pencore was not ready and ready as I hoped. So they're approaching from two directions. So one is using a full 2024 image consistent with what we were using before. But it's a much bigger image so it's, you know, anytime there's an update, it could be up to like two gigabytes and every user has to download. So that is clearly not ideal and that's not the direction they want to go. But I've asked them to get us that just for the starting point so we can, you know, get moving on that. Yeah, the issue that they're having is with a conflict in Alpine Linux with libcrypto and QT 5.0. So we're solving that in different ways of dealing with that, connecting them with Alpine and we'll see if we can just actually just resolve the issue. Another option is that we bump the QT version to 5.5.14 and there's some detail around how the implications of that and how we do that and all that sort of stuff, but it's probably more than we can kind of deal with now. Yeah, just a quick question. None of the choices they've taken are to use our existing recipes that build a working QT image. Well, that's the one thing you wanted. That's the one thing you wanted for a long time. Are you saying you're getting a buy-in? I remitted a QT, yeah. I can't remember how many it is, but it's, you know, a number of gigabytes, yeah. Well, I mean, I think it's wonderful they could shave our image size down, but you might think that for the expense of a gig and a half of this, the storage, that we can afford it and they could move forward with whatever works and then they could work. The impression I got was it's not a storage issue, it's a download issue. It makes it a great internet connection. It's gonna take you a long freaking time to download two gig up to your top. Yeah, especially if it's an update every single time. But let's, we can discuss the soft line. Try to stick to our updates. All right, Derek, how's it going? Okay, okay. So I'm gonna see what's there. I was talking about getting the SJ230B2 update, which is compatible with the new SJ2211 that can just, so the new design is a little bit different size and the power comes out differently. So we needed to update the laser grid design and the 3D printer design. So I think I'd promised Josh that I'd not done one same. I did not get that done. So I did get that done today. So if you have 20 minutes or so, Josh, put it on the laser and cut it out for me. And then I've been printing parts for the updated version as well. So as soon as I get the board from Kevin, I can throw that in the new design and test anything up. So that's been going on. And then tomorrow, I would like to be sending one of these to our, hopefully our assembler for, at least for the initiative kits, but hopefully for everything. So I just got off an email to hand coordinate that. So hopefully I'll get those off tomorrow. With the caveat that it won't have the latest board in it, but I think that's okay. We can get it off the new board. So yeah, that's been. All right, what's coming up for tomorrow? So I have all of the parts for SJ240 printed except for the top and the back. So I do have a couple of weeks that can finish those. So I'll probably work it on that. In the morning, and then I think I, we need to thank Josh and Johnny and whoever else has raised their hand on that binding parts team. I need to stick on that a little bit and try to talk about some stuff. So maybe try and do that tomorrow. All right. Yeah. Try to give them a little heads up. Yeah. I'll sing up some today so you can try this. Yeah. Okay, sounds great. I'll just throw myself on the spot here. Because why not? So I had promised last week that I'd be working on the roadmap and trying to consolidate a lot of the documentation that we went through in Hawaii and created in Hawaii. When I dug into that, it was a little bit more extensive than I thought it was going to be. We've got something like 40 spec documents going back a couple of years. And then there's another, doesn't earn more, excuse me, roadmaps that I need to consolidate as well. But, so I don't have all of that work done, but I will at least get a roadmap for the roadmap out today, which I think will still be useful. And you guys can all tell me what you think of it later on. So, yeah, so that's what I've been up to. But I did enjoy my holiday, which I didn't know that I needed, but I did. So, Ken. You learned something new every day. I did not realize that our update process was us pushing a complete new unit out to every device on an update. That's interesting and carries its own ramifications of discussion from a serious point. Sorry, Ken, to interrupt. I don't think that's actually the case. I think they attempt to push small binary diffs, but given the size of the image it sounds like, it would end up being a lot of diffs anyway. So, but let's not get sidetracked on that. What are you working on? So anyway, yeah, I'm working on, actually I'm going through some of the things that Jarvis and Kevin went through. I'm almost completed with the refactoring and removal of the mark two skill, the second mark two skill to be in the tab and pulling that into the actual date, score, and closure for client and enclosure proper. So I'm knee deep in that, trying to get messages from both the viewing message bus and the regular message bus and keeping the existing volume skill in sync. So that when you were to push a button and it changes the volume, it wouldn't confuse the volume skill. So I throw a map, I anticipate having a full request ready to go tomorrow, so that it will find its way into the next kind of full release. And now I will move over to using Chris's API and getting back into the incremental machine learning project. Okay. All right, thanks. Are you still using the mark two feature branch? Is that we're still doing this work? Yeah, in other words, I haven't committed yet. That's where the full request is going to be put. There will be a few changes, lines of code that I'll ask you to commit on the whole blue system skill, just to dampen the actual output of the IPC command. So just two comments, comment two lines out and then just make sure that that's released in all future skills. Yeah, but other than that, I'll be on the market right here. Okay. Chris there, how was your Thanksgiving? It was okay, a little lonely. We sat around with a bunch of people here with just my family, so. Made a lot of food on the Thanksgiving dinner. But you have like seven dogs, right? So. That's true, I could share with them. But I did get a version of the query I was struggling with working. And I have the tagger itself working again, basically to the point where our initial iteration is supposed to be. So. Economic committed right now. I think what I'm going to do tomorrow is to test the whole path. You have tags and stuff, get it designated. You know, run from the batch jobs, make sure the whole thing kind of works end to end. And then once that's done, I will, I mean, we'll have to work with Ken on some of the, some of the whiteboard stuff, but because I'm curious as to what, what do you want me to do next? And then you send an email out about, you know, maybe building a whiteboard contributor tool. To help us get further faster with training the whiteboard. But then there's also some stuff that can take over possibly. And now that's a big stuff goes. So I just wasn't sure what my priority would be after I get this initial iteration of the tagger. Kind of ready to go. Okay. So it sounds like you've got another day of debugging and testing ahead of you. So let's figure that out between now and the end of tomorrow then. Yeah, I don't know. I circle up with the Ken and the guys and see if there's anything that you can help out with or that they need to help with on that front. Otherwise we'll, we'll get back into the job board and there's no shortage of stuff to work on. I mean, Chris, I think if you're ready, we can meet briefly tomorrow. You will be ready to make sure that everything's working there. You know, go over that. If nothing else, that'll validate. Maybe open up some stuff and you're ready for that. Whenever you're ready. Okay. All right, great. And Josh, any updates for us? I and I have been working through the, we'll couple things. NASA, we'll find out tomorrow whether we were awarded the following contract. And Johnny and I have been working on a financial model, which is what I'm looking at right now. That runs out through the end of 2022. And it allows us to deliver everything that we promised. And then I'm patiently waiting for an operating system for this thing. So when under that stunt, that would be great. Let me know if you want me to have a discussion with our vendor. Our vendor? Panticle. Oh. I mean, we're not, there was a lot of unknowns going into this, but as Gev said earlier, we're close. I've also been given a lot of thought to messaging, but that doesn't really belong at this meeting. So I will politely step aside. And then whenever Derek gets me stuff, I will start printing and what you're cutting and so on. All right, fair enough. Okay, and out of left field comes Emily. Emily, do you have an update for us? We, Kevin had talked with Emily in Hawaii about qualifying some PCBA companies for us. Just checking to see if... Oh, sorry. How's that going? I'm gonna need to offer him. I set up some logins for some of the companies, but he had to get some more information together for me to be able to do more. Okay, so you're still waiting on some info from Kevin. Okay, feel free to ping him. Again, he just got back recently from Hawaii. So, but he's back and he's working today. Okay, we'll do. All right, awesome. Okay, well, thanks everybody. That'll be it for today. And...