 All right, welcome to October 12th, the Microsoft DevSync. We have a special guest, Kevin Jordan, is joining us today. He's been working on our Mark II design. He's just gonna be mostly listening in, but maybe he'll pipe up from time to time. So, welcome, Kevin. Thank you, glad to be here. So, where's Christopher? There he is. So, let's just go through our sprint real quick. If Chris, you could pull up the current active sprint and we'll just go through the issues. Remember, we don't need a recap of every particular issue. Let's just hit the highlights in terms of any problems that you have. And it's a general sense of whether you're making progress that you anticipated making, or are we going to finish this sprint on time? Or rather, are we going to finish the things that you thought we would finish in this sprint? So, thank you, Chris. So, we can go ahead and start with you. Okay. So, I'm working on... Yes, thank you. I mean, we can just make it simple when they close the tab at the end of the session, right? That'll be our first pass and we can get fancier later. Well, you can do it on the... You know, we're going to remind ourselves of that. We do have a insert timestamp on all the tables, actually. So, you could probably infer a session from looking at groups of timestamps if you wanted to, just, you know, for it. And know who did it. Is the tagging... Yeah, that's fine. Yeah, just... Yeah, but that's a different idea, I don't think we... All right, well, it sounds like there might be an issue that needs discussion here. So, let's take a note of that and move on. But I think you've got your short answer there, Chris. Yeah. All right. Yeah, so thank you. Okay, great. This is the... Okay, any surprises or anything new pop-up for the rest of the week? What should we worry about? No, everything's going pretty well. I still haven't dropped reviewing Kevin... Or Ken's large PR. I need to spend some more time on that. I got too involved in this API. So, but other than that, everything's going well. Yeah, I saw that there was some back and forth on that PR, having to do with a bunch of stuff I didn't really understand. And it looked like somebody was throwing up their hands on it. And so I just wanted to make sure that that PR is not getting abandoned. Well, it might have been a different PR that I'm thinking of, then, but it had something to do with some of the things that Ken wanted to do were causing problems. So, you're looking at the full request for... Yeah, that was it. So, could he make his change independently to a different branch? It's he doing me the right way. But was it a Kiwi issue or was it a message bus issue? I don't know the answer to that because I've never run Qt. All I know is with this bill, with my hardware, this sticks as a very annoying bug. I understand, I get perspective of what's going on and that this branch hasn't emerged from that stuff yet. There's a lot of stuff that's in it and we've been releasing it from that branch. So, like I said, I'm not going to worry about that too much. All I know is that if you look at the diffs on... Yeah, that was my question. It seems like it's a pretty targeted change and I was wondering if we couldn't just apply that change to the master branch or to the Qt branch directly. Okay, clearly this is... So, that bug fixes like that could be applied? Yeah, so I don't really understand everything that's going on here clearly. So, it's confusing to me as to why you can't merge a spot change into a different branch but maybe it's because that fix doesn't apply to the other branch because the problem doesn't exist in the other branch, right? So... Yeah, however, this branch is... This branch, what it's marked about... Okay. So, it sounds like it's specifically related to Kibbe versus Qt or Qt and... Yeah, that's how I think that develops. Okay, so I think this will be resolved by the end of November. Very specifically, it will be resolved during our get-together, assuming that goes forward. I think it requires a high enough bandwidth communication between everyone that we can probably just hammer this out in a couple of hours if we're able to get together and talk about it. Otherwise, we could also schedule some time to have a separate meeting about this. But honestly, I just don't understand the difference between the architectures of Qt versus Kibbe and why it's not a swappable module or that kind of thing. And maybe that just wasn't a consideration at the time and it wasn't important. But I think we need to get together and have a talk about the future of the GUI interfaces and interfaces in general with the devices and with core and just resolve this once and for all. And I think we can do that during our sprint we're planning for at the end of November. That would be my preference. And then we'll just be done with it. Okay. But are we not building our images off of the same branch that you're working on? We are, I just haven't done a build since he merged that change in. Okay. Well, that's also a thing that Josh is working on in terms of being able to deploy builds and stuff like that. So, not that that necessarily affects us, but okay. All right, moving on. So that was Chris's issues. Well, Ken, since we were chatting, why don't you go next? Okay. There's plenty of stuff we can be doing on the mark two in anticipation of getting our next grab of the boards back this Saturday as well. So that might be something that it would be useful to loop you in with Kevin on to- Yeah, anything? Yeah. Yeah, we should have a chat with you and Kevin just to bring you up to speed on the changes. They're pretty minor for this rev, but there are some optional changes that we do want to test relatively quickly because they will impact the next rev of the board. Do you think that makes sense? Sure, yeah. Okay. So is that it for you, Ken? That's it for me, yeah. Okay. Derek, how's it going? Yeah, looks like a box. For speakers. Yeah, it's a box, it's speakers. I showed you in the little tiny circle that was supposed to be the grill did not print nicely. So that's on directly in the print bed and it's trying to do what a 10,000 little circle and you're not like it. Yeah, it'll likely be the design we use for production, but yeah, it's just not going to kind of press the end. I'm going to just simplify the heck out of it. Can I come out of a 3D printer? Yeah, directly on my printer set. What is everybody on a 3D printer except for me? Apparently. Yeah. We're really not expensive here right here. Yeah, 800 bucks again. Yeah, you can resolve that problem pretty quickly, Ken. That's not one of those that's going to take a whole lot of thought. You should absolutely have a 3D printer. Like remember how it was when we used to have to write letters and like print them on paper and put them in the mail and they went from here to there. Like that's what solid plastic objects are now. Like why would I mail it to you? There's my wife will buy me one instead of a lawn mower. You should put a 3D printer on the lawn mower and see that's the way to do it. Double fast. Well, I could 3D print a lawn mower. Yeah. That you could do. Those ones are a little more expensive though. Yeah. Yeah. I mean, it's a big grand for the robotic lawn mower and the only most three quarters of an acre, but they're definitely. I definitely have them on my list of things that I would like to have at some point. It's a fascinating 90s. I was at a company and one of our sub companies was a plastic injection molding company and they were growing about how they have just bought a 3D printer. It was like only $180,000. Yeah. So the other thing I should mention, I got all parts ordered for this 20, we're getting 25 orders and we're making 20 of them for part of time. So I've got all those parts ordered now. Some of them have the pies showed up. Some of the cables showed up. So should be getting everybody a week. Everything. Great. That will sync up very nicely. And. All right. Well, Josh is next to the list. Yeah. My to do the end process document backup system. And then you can throw me a new fact that says make updates work. I am. I just sent you another one. Isn't the number going to be zero right now? I thought we turned that off. We're definitely getting new records. Okay. I must have been thinking of something, but people don't have the most recent person at the code. Still be right. We didn't disable our server. well we need to address that as well then great more tickets okay guess how are things going okay well I guess that's everyone oh was there anything else where you're done guys okay just a quick update on my end really the only salient thing is work on the hardware we're expecting the next rev of the SJ201s to come back on Saturday and Kevin's gonna test those program them and ship them off to Derek hopefully by Monday and that will you know they'll allow us to get our dev kits out to well not the dev kits but this iteration of the prototype up to to all of us and so we'll all be working off the same same piece of hardware for the first time in a while and immediately after that we're going to do another rev that changes some of the parts makes it more reliable and will be a cost reduction and add some other features so we're at least three revs away from production hardware with the third you know if all goes the best it can according to plan the third rep will be what we ship to our Kickstarter backers but there may be there may be another rubber two in there just depending on on how bugs whether we get any bugs with the next iteration so that's the hardware update and it sounds like we're on track we're in sync that Derek's gonna get all the parts the rest of the parts other than the SJ201 in by the end of the week so we should be in good shape for putting these together next week and so that means I'm gonna be coming up with a couple of tasks I think Kevin's gonna handle most of them but maybe can we get involved as well in terms of getting prepped for the bring up on the new SJ201 board so we get that ready and also we can start work on the tests for the next iteration of the board there's some provisions in the current spin that are optional and not things that we have to do such as getting interrupts over the USB bus instead of via a GPIO pin and we haven't actually tested how that works and before we do another spin that's gonna rely on that being functional I want to actually test it in software so so it's a couple of things like that that we want to do before committing to a final hardware design that's it for me all right so that's it for this week that's it for today and I'll see everybody again on Wednesday Can the folks stay on after the recording?