 Okay, so this is October 2nd and this is my crop tips. So this would be the end of our sprint Yes, that's what I thought so let's let's do a check in and see how we did Chris Do you want to can you pull up the the Jira tickets and we'll go through that. You're muted. I'm muted You're muted everybody see the sprint then okay? Yes Okay, yes, I guess I will get started since I have mine up for you know my daily tasks I Was able to get pretty much all of Salini the next version of slainie done I The only reason I'm holding off on the next version of Salini is I wanted to finish the Weightboard file naming scheme thing that we just came up with I think you know It's really not a lot of point creating a bunch of files with a thorough on the scheme. So I Should finish that today So it'll be early next week we'll have a slainie release But I did not get to any of the Of the tagging UI stuff Unless you count any operating angular 10 was kind of part of that But one thing I did Do spend some time on yesterday that took a little time was Angular 10 fixed a lot of our depend about issues on Salini So I went through you probably got all the email I went through and And you know cleared a lot of PRs and stuff because I checked the the versions on the angular 10 version of Salini UI and And all those got cleared off. So that took me a little while yesterday But yeah, so that's that's basically yeah, I'm just In this print ready to release the next version of Salini, but no no tiger UI stuff. Okay, great Is there anything else not tiger UI that didn't get worked on I Did not upgrade this course Which is small I should do it next branch until even I was just about to say well, okay That's not really critical, but the title is literally a critical update I Did spend some time looking at it and got distracted with something else. So I have an idea. I just need to execute Sorry, I was having a backup to that too seems to be Quite a lot. I wonder if we should look at printing some of those old ones out So we're not keeping it back up like daily and if we don't we aren't putting them to get pretty out of control Is there any any input into how long we should be keeping discourse backups I Mean I like to keep a pretty healthy list of backups, but you know, I feel like you know once it's gone past A month having a daily backup is not as necessary and you know, but I like to keep Personally, I like to keep you know, like then monthly backups or something like that, you know So that if there is something you can you can roll back to some kind of snapshot, but I Can't really see why we would want to roll back, but that's saying that that's exactly what you say when nothing's going wrong And Back when we roll back three months, you know, no, like that's why Unless unless everything back to that point didn't work. Yeah But it's been working so So we haven't tested the backup. So it's question whether the backups are working, you know Okay So how about we keep a month's worth Well, the scheme is you know, you keep Daily backups for a month or two months, right? And then you keep monthly backups for a couple of years, right? So I'll go through the backups and I'll add that to this ticket to I mean, we can keep yearly backups indefinitely and per month for the last two years you said sure And yearly after that, right any other questions on my progress? Miss print not for me. All right Derek so I think the biggest news is, you know, I was excited to show you guys prototype today, but I Kind of screwed up the printer. So I've got to fix the printer. I had to order some parts yesterday I got kind of a glob of death The printer failed on the fdm printer and just collected Plastic around the hot end So that was kind of a bummer But the cat is complete So hopefully as soon as I get that going I get parts on Monday So yeah, the gooey stuff is it's done I Got one of the SJ 230 is complete for Michael. The only thing holding me up on the other one for gays is I Need a print another speaker enclosure and that will be done Got all the sourcing done for the drivers and the displays in terms of Still working a bit on pricing on the drivers like to get a board Uh So michael asker like on the camera module. So we're evaluating camera watch. So I pulled out an old Version one Pie camera and plug it to the pie for it and it worked fine That's about the extent of it. So that's what I was thinking we'd go with It's the cheapest route Okay, we just need to get that and is that incorporated into the can anyway I don't have it in this current design. I kind of have it like blocked, but I don't have like Placed in there, but I don't have any of the bosses or anything in there. Yeah The only thing to think about that on that though I've been thinking about is really the ideal way to do it and clean nice ways And what we did with these eye links design we actually incorporated behind the cover glass So I'd like to go back And look at that possibly but that would include a custom cover glass from the display manufacturer It was a pretty minimal. Um, it's going like a 500 dollar in re when we did it last time So I'm gonna look into that so yeah And I've kind of blocked on this rollover stuff until we get the part back or till we get the devices back from them to see if we can test whether Whether or not they failed from what we expected with the re speaker microwave issue that we've seen in the past Yeah, it's about where I'm at Okay, great next Yeah, yeah, so I'm buttoning up. Well, I don't buttoning up as a relative term Uh, I haven't started investigating why we're getting stereo audio yet. Um The no audio output on first boot. I'm not seeing with the Which leads me to believe it was an issue with the re speaker board As far as the enclosure still goes so I got the um Switch is doing what the mark one does with volume up and down. So it goes around and you know, um That's it, you know, 100 percent whatever down to zero percent uh I I I made them go through if you're pushing the down button I made them red the ring and if you're pushing the up button. I made it green, but I could just make it all blue Uh, that's probably uh, something I wanted to discuss with derrick Um, I think I just figured out what was wrong with my mic. It was that the mic mute button was on Which leads me to the question What do we want to do When the mic mute button is odd Are we going to dedicate one of these leads to like a red green for the mic mute button? I mean having 12 leads is interesting because really tan is ideal for volume control Uh, and that would leave two open one for my commute. Maybe One for activate And I was reading through the mark one code Uh, to understand how the activate button works. It's kind of weird So i'm not mistaken the mark one was a pie and a arduino Board connected via serial port. Is that right? yeah so The way that the activate button work was kind of wonky. So instead of sending it out the message bus it actually create Created a sudo IPC communication concept where it would stick Files in a shared well-known location directory and call those signals Um, so, you know generate a signal would say Put this file this name there See if there's a signal there would say, you know return true and delete that file Um So anyway, uh Yes, I guess i'm gonna I guess i'm gonna maintain That our code is is chops full of mark one isms like, you know message bus stuff that's You know says move the mouth, but we have things that act upon it and it doesn't really move a mouth So, um anyway Uh That's that's where i'm at. Uh, I have not so I I pulled all the hardware volume stuff out of the skill All obviously all the leds and switches are out of the skill So the skill still has the stuff that responds to the message bus so, you know The the volume skill would send out a increased volume and he's Picking that message off, but then he's calling into this volume class. I created to do a hardware You know volume change or set or get I've created a separate subdirectory in that subdirectory called sj201 underscore rev a And in there live a lead class a volume class and a switch class And the assumption is moving forward That if we have I don't know You know a new board or I could just create a re-speaker if we wanted me to That would be the same but we'd have a lead class and a switch class Volume class might be a little bit different, but The main code would always Still, you know, basically instantiate a lead a volume and a switch And and the semantics should be identical So I've got that level of abstraction, but I have not moved this all into the actual enclosure Uh, don't know how far I want to go on that right now. Uh, I think there's other things that are needed like posts Which I was thinking about moving Um, so I don't know, uh, michael, I'll leave that up to you what I should do next if you want me to Refactor this and pull the all the stuff out of skill proper and put it into an enclosure class and move on to post Uh, processing I think posts is going to be a challenge without some sort of user Interaction the other thing is how did we set the mark one into setup mode? because I could Right now I have a a timer off of the switches Because when you ratchet it up and start, you know, displaying the volume level A couple of seconds right now. It's three seconds later. I want to blank them out after no button's been pressed So I could do the same thing with the activates or the action switch where if you held it down for like five or ten seconds I could drop us in the setup mode. I don't know how the mark one did that or what we're expecting out of that Um Anyway, Josh just uh, gave you an answer via chat Uh, he says that there was a menu you would hold down a button And then it would pop up a menu and then you would use some other buttons to scroll to the option you wanted so Yeah, three seconds hold it down for three seconds and I'll pop it So you want me to retain that behavior Derek? No, um, yeah, we're not gonna We're not gonna see that was kind of trying to use a lot of the we just had a one button and the rotary encoder. So We're gonna be able to do all the menu stuff Well, actually, this is this is part of this debate that we need to have for example in the cute design there is an entire menu in the touch screen, you know slides down like a drawer like the ui in a Phone and mobile phone you just drag from the top and you get all kinds of the menu options there Um, you know, it could be You know, it could be activated by holding down the uh, you know the action button for three seconds, but um I think we'll end up wanting to put it in the menu on the mark too. So did the mark one not have a setup mode? Well, what do you mean by setup mode? so, um If I have my mark one paired to my network in my house And then I bring it down to my condo How do I get it to go back through the wi-fi setup process? Right, so yeah, yeah, you'd hold down the button for three seconds and there's a wi-fi option in the menu So you'd scroll through all the options with the rotary encoder and you click wi-fi Okay, okay. Well, I can certainly do that. I won't do that at this moment But yeah, michael, I may want to talk to you outside of this meeting about power on self diagnostics and things like that the other thing that we wanted it to do was when it just you know to boot it up And there was no wi-fi or there's no You know, it didn't recognize any wi-fi that was saved and it's You know In the wta something or whatever it would just go straight into wi-fi Well, the concern there is wi-fi Connectivity could be intermittent in other words, uh, the wi-fi at my house could go out for half an hour or so which is not uncommon and Yeah, you just run right into wi-fi set. That could be a little confusing. So I'm not Yeah, I I know it does bark, right? It can't connect to the internet or something I've heard it bark at me That uh, the qt already does that as well. Um, but also I think we should hold off on that until we Make that make all those calls around how the wi-fi's gonna work and stuff um Yeah, yeah, I also We don't really want to do the menu button thing like because everything should should really like we can do that much nicer on the screen Yeah, yeah, exactly All right What was that chris? Sorry If we could use voice commands novel idea for a voice assistant Okay, there the only concern really is um As josh pointed out passwords Using voice can be tricky Well, not for wi-fi. So I was talking about like some of the The settings or the activity button stuff. I mean all that stuff should be supported with a voice command um Yeah, it sounds like this is a Going through a menu Sounds like this is a rape topic for uh, some digging into the the architecture getting in giving into uh Having a solid spec on that. I'm sure somebody had one back in the day, but none of us knows what it is so uh Let's go Uh, I'd like to put that on the uh, uh kens plate for next week To investigate core with respect to the boot up power on self-test and enclosure type code Okay Yeah, I feel like getting the enclosure code like deciding how we want that enclosure code to look so that we can start pulling out the mark one You know stuff that's sprinkled everywhere Um out into its own enclosure code as well. I think that would be a pretty valuable Yeah, I mean, I think I think what I'm hearing because like I said, I mean I could button up the enclosure Puto skill piece now if I wanted to The exception of the activity button doing something everything else seems to be working And of course, what do we want to do when the mute mic switches on or off would be nice to have an indicator so Simple minds like we don't get easily confused But I think we really are at a point as michael just pointed out that You should probably take a first stab at How do we define the beast? What is its high level functionality and how do we expect it to behave and all that good stuff? I think that really would answer a lot of the questions not only in the enclosure code, but moving forward So, um, yeah, I guess michael I'll try to get on your calendar at some point Really next week talk about power on self-diagnostics with you and I'll start taking a whack at putting that stack together And I'll work with both chris's and xeric to understand What we had and how we want to vary Does that sound like a plan? Yeah, let's do that early next week Okay All right, and that's it for me. I haven't gotten to the uh Prototype and closure stuff yet. Uh, but I should be able to button that up Can we close mark two 125 at the top there? and we You know, I'm gonna I'm gonna say Yeah, I mean because nobody's been reporting at psj201. It really does seem like it was a re-speaker issue Uh, I'm gonna I'm gonna go at my old adage. No screenshot. No bug. So yeah close Okay, I'll uh I'll make it a little fix I'm not really doing a battle. We're just gonna move on to the next design Yes, oh my I think that's showing me and in a moment. Oh Yeah, uh in terms of what did get done, um, you know, uh, there was a lot of focus on um, community stuff and and getting the Uh, the microp core in particular PRs sorted out. Um So yeah, that that feels a lot better. Um, we did get new versions of the microp skills kit out, um as well as, uh A new message bus client, um, which is you know, what people can use to To connect to a microp from, you know, other projects Um, just giving them a simple way to do that. Um Also yesterday, I pushed out some trademark usage guidelines that had kind of been mostly developed a couple of years ago, but um, just needed a little tidy up and hadn't gotten published. So, um, they're now out there and I'll um start pushing that out to the community and and just get people's feedback on that. Um Already sent it to one one person and and they were pretty pretty comfortable with them all so that that was good Um And what else is in there? Um the exposed logs, uh, I finally got that all knotted down. Um Um Just a lot of trial and error Uh replaying replaying jobs and seeing what happens. Um, and now there is a tiny conflict in the PR that I have to fix but um other than that, it's working good Um, and so hopefully that will also give us some more info on those two Um bugs that are still in the in progress. Um uh because The thought is that having the the service status stuff in there will will help those but um Because we've never been able to reproduce them locally Don't know for sure and so now next time they happen. We'll have we'll have logs for them, which will give us a hell of a lot more information Um What else we got the the roadmap, um, that seems pretty Good enough to to push out so I just haven't um Done the you know communications after the community for that. Um and then same with the I want to Provide ken's current test model precise model out. It would have to have a plate with Um, so I didn't get to that, uh, but it should be a pretty minimal thing um A bunch of little stuff in there bug fixes And then the other things that I that I haven't really got to Um, well the speck out media playback system Uh We we did a a good chunk of work on it But I just popped it back in to do because I wasn't actively working on it. Um, so that needs to get finished off at some point lingua franca, I still want to um get to because It's it's a basically it's a big change. Um And it's kind of blocking people from contributing new languages. Um while we're in this sort of state of change um And the skill api is all finished off. I just need to test it and um Uh after there was some extra changes made to it Uh, and then finally the war from alpha, um, I believe I talked to johnny about that yesterday. Um, and Uh, we we had an outstanding debt that they hadn't told us about or something like that. Um, they're bills Oh, there you go. Yeah So hopefully that's fixed pretty soon and then I'll revert that change. So Um, that's why that's still sitting there I think that's it Hey Gez. Yep I was reviewing that message type document you threw together Oh, yeah It'd be helpful if we knew which bus the message belong to Uh, are you mean in terms of the main bus or the gooey bus? Uh, or the recognizer bus The recognizer bus is is the main is all on the main bus. Everything's on the main bus except for gooey Yeah, there's only two bus donations right now Are you sure about that? It looks like I thought the recognizer had its own bus, but maybe not maybe it's got Its own loop on a bus. I'm not sure probably has his own client All the services have their own client I was in that code a little while ago and I thought it Anyway, all right, it has it the recognizer stuff has a a weird um sort of Name for the message types that might be like Um, what seems different so it has the it has this weird Recognize a loop colon you know And then and then whatever action whereas everything else uses Like microsoft dot audio dot service dot play whereas Yeah, the recognizer loop is is uses a different naming convention for for an unknown reason So maybe that Right the gooey bus and the main the main bus. Yeah. Yeah, but yeah, we should we should change those Names over at some point. Um, it's just Happening Yes There's a few other cleanup things I want to do with the message types as well where Even just things like the tents of things like, you know, making sure that it's just been around Did the thing happen or is it happening or? Yeah, I kind of think I'll make it An easy way to search across repositories A lot of these messages are just embedded As hard-coded strings and method calls. So yeah Yeah, so any change we have to be pretty careful about and it like There are other people also relying on those message buses on those message types as well. So You know, we'd want to we'd want to Potentially support both But this is also why it's kind of better to to do it earlier rather than later because You know, whilst it feels painful now like the more people you have relying on that the more painful it becomes Yeah, you gotta be careful too because some of them are overloaded and you know, yeah It might say move the mouth and it really triggers a completely different event like Start the recognizer or something. I'm not sure Anyway Anyway, it definitely can't happen until major release anyway, so But it's also something that take a bit of Careful review Is it also the case that there could be outstanding skills that are relying on those messages? Uh, yep, yep So they would they would magically break Yep How is it why is it difficult to search through multiple repos? I don't get it Just to find the files Yeah, I mean unless you check out all the repos Um And put them under one major subdirectory Well, you can Excellent Yeah, you can do that. I mean most of the message bus names are pretty a pretty unique You know, like globally so you can just search all of github for like Is does the recognizer loop a woken message exist in anyone's repo on github? And then you can search for a term across multiple repos. I didn't know Yeah, yeah, you couldn't do that on bit pocket. Okay. Good way to find new skills All right, good point. Okay. All right, uh, so thanks that was guest, right? Derek, do you or Michael want to take one go over Kevin's? Uh, sure, I can I can handle that Um, we sent out our request for quote on the next and hopefully last spin on the mark to Dev get prototype board for the sj201 so um In the next couple of weeks, I expect we'll have our fully functional uh board that we'll be able to um, you know, send out at least the dev kits for This will not necessarily be the board we take to production But it will be stable and have all the functionality we need to to continue continue our development efforts um And uh, yeah, that's covers both of Kevin's kicks, I believe Okay And I actually emailed Kevin With the gbi o18 ten issue Great challenge. Do you have any updates? Oh lots of stuff, but nothing Nothing here. I'm meeting with pantacolor and belina and abuntu about the update process I've been working with that coral co processor Um, and moving machine learning to the edge, which looks like it's a win and may May be something that we'll be discussing for the final mark to Been talking Michael's ear off about getting us all in the same room for a few weeks That was on the agenda for this meeting. Yes Did I miss that part? No, we're gonna do it at the end of the regular meeting. Oh Okay, um And then closed out the last pass credentials which have been fixed I don't have a lot of tickets in this ticketing system So anyway, I will be Okay. Oh, we can we can start working on it. Uh There's lots of things for that I should be helping with so Um, that's all I have though. Okay. So at the very least you've got the one ticket for uh, talking to canonical about updates Um, you just go ahead and make separate tickets for the the other two that you're looking at Okay for belina and for pantacor Yep, Michael. Uh, yeah, so I think I just discussed the plan Yeah We have uh, there actually is a there's this is actually in progress because It's not just about the uh, the initial Set of dev kits for us internally, but I want to actually have the full plan for how we're going to roll them out to the Kickstarter backers who wanted dev kits And anybody I need to go go in other campaigns who want dev kits and then, uh, opening up, you know The the door is for dev kits in general, uh, which is a different beast than The mark two, you know that we Will be releasing commercially, uh, mostly from the you know, the set of expectations that the users of those Devices will have in terms of how production ready with how polished is it and that sort of thing um, so Yeah, we're we're still working on that Yeah, so the the feeling at the moment is that people will be able to Order dev kits even if they haven't been in a backup. Is that? Uh, it's definitely an idea that we're talking about Yeah, cool because we're getting we're getting requests and like I know that Obviously we want to get everything out to the backers as soon as possible and dev kit backers would would have Would get the first units. Oh, yeah, absolutely but like getting people dev kits doesn't slow us down from Getting marked to production units at the door. In fact, it makes things better because there's more people testing it and and and um and helping us out there so um, exactly. Yeah cool. Yeah. Yeah, um and right and and you know, so We're also talking about going to the Kickstarter backers and and asking them. Hey, do you actually want a dev kit? You know, because we don't know necessarily which of those people Um, want a dev kit version versus, you know, who are just looking to use it as an end user And the dev kits to be clear on the Kickstarter. They said, we're gonna, you know What was promised in the Kickstarter is we'll give you all the parts you need to make your own mark too And uh, I think we can do one better than that, you know in this case We know the dev kits that I'm talking about will be pre-assembled. They will be, you know ready to just You know plop on your desk plug in and go But they will be very definitely in an alpha state, right? We're updating the firmware Um, may require you to pull the usb drive out and stick it in your computer and copy an image from the internet You know that kind of thing versus over the air updates and and all the nice ui stuff that that you really need for a commercial project. So um But yeah, well, you know, we'll be asking the Kickstarter backers about that If we do decide to make dev kits available to the to the public just to make sure that You know, they get they get priority Okay, so uh, so that's our sprint. Uh, let's go ahead and close this one out. Um, I did Do we want to, um Assign these on assigned Tasks to people. Oh, okay Interesting Those seem rather big Oh, okay actually I think scl 119 is probably a meeting I can set that up That's a discussion to have Yeah, uh these purchase parts bombs, uh Those look like they should be on Derek's plate Oh, these are some tasks for the Protests that is probably on Derek's plate, right? Yeah, there's something a little weird. Yeah, I think I need to just reorganize that a little bit Um, I mean, these are things that are kind of in progress Like the purple for example the purchase parts. That's like the displays and the Driver speaker drivers and a lot of good stuff So, yeah, let me take Are we where you put it? Oh, you're signing to me. Okay. I might end up consolidating or something But yeah, that works for now. Yeah, I don't know if it's a Maybe it's just we're using JIRA in a way that it's not meant to be used Or something. I don't know it seems intuitive Yeah, I think I just don't really like how they do sub tasks. I think it's weird So I've just kind of stopped doing You can sort insert other dependencies like, you know, is blocked by or that sort of thing Okay, so these two Do these have any further description? I think these are just high level Like this is a high level ticket for the tag. I don't know what says it's duplicate so Let's check out precise 65 make sure that it's a duplicate Yeah, sure. Okay So, yeah, we just mark that one as a duplicate Whatever we do with those things The other ones in the spring other The non The ones that they're duplicated. Are they in the spring? Like are they things that we actually want to do? Oh, good question I can speak to that. Yes, absolutely that ticket was simply because You can't delete tickets Or I didn't think you can now I can now Back to the end there's an artifact from not being able to delete that Yeah, you can delete it with a click on it But do we want to add the other ones into the sprint was I guess the 65 is in the sprint, I believe It is not No sprint, but I also think 65 might be Might be duplicated by everyone Right, so let's put it into sprint 16 We're going to resolve it then And data capture from devices Um I don't think again, this is done. This was done in selene. I think it was originally documented and precise, but This was a selene project. So this is probably a duplicate of everything. I just did Yeah, that's certainly nothing meaningful in here right now. So go ahead and get rid of it And again a duplicate Back in the days when I couldn't delete your ticket. Oh, this is that weird feature where we can't It doesn't really look like it's Okay, so let's close this out push everything forward and then on monday weekend Reorganize the tickets Okay, so any other business for this meeting, okay, great, uh, well, thanks for uh, Listening everybody you're muted Michael. Oh Right, so any other business for this meeting any issues any particular trouble blockers came up I assume we were talking about that already, but Okay, well then thanks everybody for listening and We were gonna get feedback on the summit Yeah, I'm doing that now that we've stopped recording