 Okay, today is the 26th of January. This is the dub sink. Hopefully this recording will work So let's go through we've got two more days left in our sprint here, so let's pull up that board again and Just check in and see how we're doing. I've got it up here on my screen But Chris, can you pull it up and share it? I think it tends to work a little better that way All right, so we can start with you Chris and Like you've got a lot of stuff and well a few things in progress. How's the Travis migration going aside from you being muted? oops Travis migration is doing okay. I Found out today that The cover all stuff we use for code coverage is not supporting the output from high-test and they get actions so I Am looking into and I wanted to bring this up and make sure this wasn't some a scope creep of any sort but I was looking at was switching from coveralls to Cove I'll bring up the ticket. Okay, so put these comments in Codeco bio allows free usage for open-source projects and does kind of the same thing or we you post our Our results our codeco results up there and you can see you know the results you can see differences between runs and The other thing that the coveralls did that this also do is to keep that our tests testing percentage In our read me file So I was going to go ahead with that unless Unless there's an objection That's the only thing left to do really it's I don't have any technical knowledge on wish to make a decision, but It seems like you've covered the bases so Yeah, I didn't want to so I spent a lot of time on this on the code coverage tough today. I researched You know different avenues I researched why coveralls wasn't working So I thought I'd be able to move on to something else today, but I did not so Hopefully I can finish this this afternoon and and then move on to something else tomorrow, but that's kind of where sounds good to me And the other two we talked about yesterday or just So rebuild preloaded mimic to cash. I actually just pushed that Nice. So that is done and implement new pairing workflow. I Think that still is up to a discussion yesterday about how we want to include that in The mark to image so that we can play with it without because we're kind of waiting on For one or two great to really work So I've added that to the build process It's just going to grab the latest version from that feature branch. So So that will be in the image Whatever the latest of that feature branches will be in each image and then once we hit 21 or two We can safely add that to the marketplace and we can remove that special Fix, okay, and I will mark this was done as well because the PR is actually is approved It's just and it works. It's just waiting for that. So Do you want should it go to like Derek or something to is that that's kind of last piece of The, you know, the new onboarding. Oh, you know what, you know I actually I have a little bit of work left to do on this because we changed Derek changed those two screens of the URLs Oh, yeah, so I do have to modify those Q and L files slightly So, yeah, I'll leave it in progress for now and that shouldn't take me very long to do Okay Great. Let's let's go on to whoever's next Derek faces here Derek's faces is the next face Okay Let's see So, yeah, I still have quite a few things in the in progress and I distracted myself today I want to mark to SGA 240 stuff as I've been trying to Make sure that those are going to be fine or work okay for the roll over Josh's pretty one as well So it's been actually a lot of my time today Kind of going over some of the issues I was Getting it picky about like the microphone alignment. It's not quite right The screws for the bottom speaker mounts are a little too short. They're not quite grabbing enough threads and I Was tweaking the microphone gasket itself which kind of creates the The airtight seal around the top of the plastic and the microphone So I have enough spinning Stuff Speakers But then I did spend a little bit of my time on the the mk2-263 ticket Hopefully around Building some of the spec sheets that we didn't have for we didn't really have one for the sj2 30 itself Josh provided some instructions on the threaded Other threaded inserts should be applied. So I was gonna add that to the spec sheet and You know the picture that I sent to Joe as I've got that in there So we know what all the sub the simply part numbers are Yeah, and then I schedule a couple means tomorrow to hopefully cover all the rest of that stuff with Johnny and Kevin So hopefully we can still knock that out There is like some work in progress stuff for the packaging In there Hopefully I can get back to that tomorrow too Yes, I'll do what I can try to get the rest of this done by tomorrow Okay, yeah the when you mean the packaging do you mean like the insert? Oh, yeah I was going to say I started going over the Disclosure for the prototype Yeah, I just found that that Dash 214 ticket a little while ago. I moved in into the sprint So I don't know if you noticed that but yeah, yeah, I did and so I was yeah started a new document and started Just like the last three minutes started right about draft of our version of that, right? So yeah, that's where I'm at. Hopefully tomorrow be more just on that stuff and less on that straight to 40 All right Josh the second one's done All the parts are in movement I'm not actually making a video I made a Instructible, but I'm I'm not done if it needs to be published effectively But all the crop images are cropped and all the instructions are in there and all the pictures are taken. I didn't realize I had tickets and then I I really do need to figure out how to make sure a part of my workflow. I Got the I Got the first round of mark two or mark the printer The PETG stuff strings a little bit, but all in all it's pretty solid and Anyway, so I'll assemble that today I have three SJ201s that are bound for our rollover So as soon as we have software to go with those or we have software that is That will update itself automatically you can put those in the mail as soon as I assemble them I will say the image that I'm using up in the kitchen right now did crash I Don't know what caused it. I honestly don't know what image I was using I'm using I I went back to Gezz's I'm loading up the one that Gezz made me yesterday Anyway I'll push that one in production here at the house and then give you guys feedback tomorrow. Hey Josh I just thought of something Do you have any fans? I Just realized that you might not have fans for these About some of these NF a 410 premium cooling fans They're for most printer, but that's the right size for this so it's fine Yeah, it's got a connector on it Why is the right 410 feel we've got they've got a bunch of it. I've got a bunch of adapters in here, too so Yeah, I can use these if not I can get them from Amazon for like I think this was like 12 bucks and it's really what you they're like 15 dba or something. They're very quiet Cool just double check make sure those will work with our board Okay, I'll try not to burn it out our board's pushing 12 or 24 Michael Okay, they should work fine. Yeah, and if you connect it depending on how the connectors are oriented The four pin connector should just work fine But if it's got an adapter in there to make it a two-pin connector that will force it to just be on always So you can do it that way if you want to Sure, I'll look it up and get it going Other than the stringing on the print which is the material and the printer settings not Derek's drawings I think we're good Derek and I do need to continue to go through and like he was talking about like tweaking the last little things I guess finally, I don't know if I told you this but I got to I got in touch with Steve Michon at Zero tolerance. He has room for us They now have a molding shop up there in Detroit So he can do both do all the molds and do all the injection molds for us against the plastics So as soon as we are ready to have that conversation that is in works All right, that's great Okay, who's next Ken so I'm still working on the Overflows, but I made some progress was able to get rid of them at the Lowest level where I wrote a chord audio driver so that record no longer gets them. I found some obscure It was a fix that it said shouldn't have been needed for newer versions of the kernel But I don't know what that means That seems to work problem is when I extend it up to my cruft now It's not working as expected. So that's where I'm at, but I do believe I've Fixed the problem or at least got the proper patch in place for the low-level also overrun issue That's great Yeah, that's really good I'll try to figure out why it's still causing trouble up in Up in my cruft Inside of my cruft seems to be working. Okay Nice. Well, that's great progress All right Yes I didn't have a huge day yesterday feeling pretty rubbish still but Probably I think Linux can't hang over and I don't know Anyway, but Yeah, I thought given I spend I Don't want to say how many hours a day in front of a computer that doing that for a conference would Not be any different but somehow it trades you and Anyway, but um, yeah the pairing skills Gonna be loaded in the next nightly image and Had a good meeting with a photo from tannikor to go through, you know, what the few last things that we need To to get in this And Before the DevKid ship and he's aiming to do that by the end of the week and the the buffer overrun stuff I It sounds like this was Accurate, but I've said that that's not on them at the moment which sounds Sounds like is the right choice cool So yeah, there's only a couple things like you know getting the right shell when you the right user when you when you ssh in Fitting the the reboot slash shutdown Adding the the boot screen stuff and Anyway, couple other things just the tickets that are in good lab What else Tests of the got a new image out Josh and Yeah, the the Python package stuff still seems to be working for those new images. So hopefully it was just an old image that got smashed to that USB That caused those things And I you'll notice that I cleared out a few of those things that I mentioned yesterday that we're gonna Bump back a little bit So Yeah Looking pretty close to getting this all finished off By the end of the sprint with our one-day remaining, right? Okay, well, there's there's two ones that are still marked as to do in your list And you know, one of them is kind of a big one. Well to me anyway They both actually look fairly significant the creating a process for rollover to develop their skill on the dev kit Well It could be it doesn't have to be through the back end, right? But as long, you know, that's that's something that's going to hold up sending us devices to rollover In my mind that is an email Okay, yeah As long as it's a doable that way, that's fine The other one is the the MSM unable to install system packages Yeah, so This is one of three things either it's an issue in MSM either or an issue in Paco, which is a little library that installs system packages across different package managers but Matthew Scofield wrote Or it's a user Missions issue. So Panicor is also going to have a look at that Okay, which is good Got it. So you're also keen to tie this off, right? Okay, so that it's got their name in front of it. So I assume that means that they're taking a point on it right now Yeah, yeah, so is it actually in progress or is it still to do? It was to do as of 12 hours ago, okay And I haven't seen anything to indicate otherwise yet got it so That should be done by end of the week Does that mean we can't install? We can't install new skills on the system right now You can't install certain skills. So Pandora, for example anything that requires a a system package So Pandora There's not too many of them to be honest like the desktop control skill which you wouldn't use on I have to go look. Yeah, so it's not critical right now No, and it's it's definitely fixable like it's It's one of three very clear problems, right? Okay, great So last person here is myself. Well and Kevin, but Kevin got stuck in a snowstorm So he's actually not even back yet from his trip to the mountains So as for me, I closed out a couple of things the worksheet system for tracking inventory that's done I need to talk to the biz team about making sure that's fully populated properly But that's a separate issue. I actually marked as won't do for the the Ticket I made for myself about checking the clock stability because I think that was a red herring and So in progress, I have my get organized One so I think we're actually doing But I've got a I do want to I'm gonna hit up a couple of you guys over the next few days to talk about some ideas about How we're handling sprints and That sort of thing but otherwise, I think we've actually implemented all of the stuff I do you know I want to get to the point where we're doing a weekly demo and those demos are gonna be not just about tech But it's also gonna ultimately it's gonna be you know on the business side. We'll be doing weekly reviews of you know Users and like how many new users are we picking up how much conversion are we getting and stuff like that? So we'll be doing, you know, not just demos of the mark to but demos of the salini and Coordinated as an 80 testing and usage statistics from people who up in and future development And all of the stuff that it will take to make us relevant exactly And as far as the firmware for the sj201, I can't do anything like that about that until I get my Actual mark 2 device, which I don't have because Kevin's still in the mountains, so So there you go, that's my update I got a question How's the production with the PCBA house? They're expecting to get their the the revised PCBs on Thursday And so if they get them Thursday and we give them the go-ahead they can start production that day and they said It's about two or three days to get things produced so You know, we should say, you know expect Production to be done by Tuesday Was there yeah So things are moving along there As long as we one outstanding issue that I have to talk with Kevin about is the the testing jig We need to make sure that They're coming off the line and working So we've still got that on our to-do list, but That's the only thing that could really hold it up right now is if if the testing process isn't complete in time Otherwise they have all the parts that need to just start production right away any other questions I don't have a question more of a Maybe just a question, but so today I Was chastised in two different places by one of our community members about the PR I'm working on for the GitHub actions Yeah, mostly because we have another community member who started that PR and I've I've taken some of his stuff and some of my stuff and I don't know just the way I looked at him was That I was not being false and not being a good open-source developer. So Not exactly sure how to handle that Well, I thought I would bring it up because Surely this is not the only time we've had a PR You know started by one person and finished by somebody else and I didn't know if there was a process there that I Need to you know that should be following that I'm not or what you know what to do about that Right. Well, you can stop sharing your screen and also that sounds like an excellent question or forgets any other issues questions All right, well, let's get back to it and we'll chat again tomorrow. Thanks everyone