 Hello, and welcome to the Microsoft AI 24th of August 2020 sprint discussion. So we've had a little pre-meeting discussion about some work behind the scenes, just in terms of reorganizing our system. And now we're going to talk about the interesting bits of what's going on in the current sprint and what's going to happen in our new sprint. Well, it looks like actually we've started our new sprint already. So let's go ahead and talk about that. This is going to be our, what we use to track the next two weeks' worth of work. And so I'll let Chris Verra take it from here. Okay, so these 27 issues that have come over from sprint 12 are everything that wasn't done, was in sprint 12 and wasn't finished. So I think first I'd like to go through this and see if there's anything in here that maybe shouldn't be in the sprint. And then we can add things to the sprint that need to be in here and we think it'll be on the next two weeks. So the first thing here is QT versus KV. I don't think we still need to have just more discussion on that, but I don't see that happening in this sprint. So that's like actually putting in the documentation exactly what's in the open data set, there's a link to the sort of work in progress in there, but it's just been sort of adding to it a bit by bit, so I find things. Okay, so you're working on this now, so we didn't leave that in here. That's just something you're spending time on. Yeah, I should just finish it off and publish it. Although, yeah, I'm not going to be around for the next week, so that, you know, probably maybe it should come out. Yeah, let's take that one out. It's not really a high priority. It is something we need to do, but I think there's probably some discussion that needs to happen around that as well. Okay. So this says to do with the .2 and the .3 version in core. Is that where are we with that whole issue? Ken, you're muted. Yeah, so we're open for now. I'm going to have to address it soon, but I want to look at the... You're going to address it in two weeks? Yeah, gee, I don't know. Is there any way to move it into the sprint after this one? Yeah. Let's do that on this ticket. Wow, this thing. Yeah, I should probably do this. The thing I got stuck on before is I could not find our, the graphic we were using for the website being down, so I couldn't figure out how we did it before, so that's what stopped me before. I should probably just, you know, we need to create a new graphic so I can put it up or I need to find it. Yeah, I can point you to the actual graphic. Yeah, just on that server. It's just not in WordPress, if WordPress goes down, then it can still show up. I mean, if WordPress goes down, but the server doesn't, then it will still display. Okay, yeah. You get with me after this and we'll, if I can get all that figured out, then I can finish this task. It's all that's been waiting on. This is not going to get done in the next two weeks. This was in review in the last sprint, so hopefully we'll continue. We'll get that finished. Audio chamber acoustic test. Yeah, that's, that's mostly done. Well, I'd need to wrap up or she thinks. Okay, you should finish it in the next two weeks. Yeah, yeah, yeah. Right. So to be clear, we're not necessarily talking about the status of any of these items except to ask the question, will it be finished in the next two weeks? Yeah. Right, right. Okay. I don't see me getting to this in the next two weeks. Or matter, the matter most upgrade, is there something critical in here that I need to do? Or is this just something we just need, needs to be on the. I think we do need to do that actually. Yeah. I am fairly sure things are going to break if we don't update. Particularly. If people are using the Android. Application. Throwing up an error. Saying that there's going to be compatibility issues and. Potentially to the bugs like we're moving out of. The portability territory. Do we have until October to do this or should we do it? We already have a problem with timing. No, I think. We're. I think we're. 511. Yeah. So. 511. Is the previous. So. Current. Yeah. Yeah. Yeah. Well. Can't be too far. Not pretty. Just about a year ago. Yeah. Yeah. I think, I think we were just on the previous. So it would have expired. You know, I don't know. I don't know. I don't know. I haven't had one long to go. Like April. Okay. No. It hasn't been that long. Surely. There's support cycles are pretty short. It's like the only support things for about a year. Okay. Keep up with it, I suppose. Yeah. I'm going to dev ops person. Thanks. Last pass credential access. I know. I know. That's a really cool thing. I mean, It's a really cool thing. Right. It's a really cool thing to see you today. Saying that he still had access to this. So we should probably go ahead and. Get this cleaned up. And miss Sprint. I would think it should be that hard to. I talked with Steve. Right. Last week. I talked to Steve. Last week. And he said that he'll have everything off. Monday is. just good to sound to Gmail and everything else before that stuff across the jazz. So that should be done this week. We're in this next sprint. Derek, will you have an OTC device built in the next couple of weeks for Ken? Yes. All right. And you'll have the parts to Josh for- Hey, do we still have the intern? I was gonna, well, not really. I was gonna give you guys an update on that. He's available, but very limited hours. So effectively not much. So I was just gonna, I kind of sick, see what we, you know, see how it goes. But I need to talk to you guys before I keep him on payroll or not. He started the school year, I assume? Yeah, yeah, started today. I would rather to spend intern wages making these things than spending your wages making these things Derek. So, and I also think that we haven't basically an unlimited appetite for these prototypes. So we should have somebody in at least half time just making prototypes. It's not like we're not gonna use it. Yeah, that's a good point. Well, the, in the case of the Kins, it's essentially done. I need to, I should be shooting it tomorrow. But yeah, making more, that's good. I mean, we should have several on the shelf ready to go in case we have a customer, in case we have some other needs. So it's not, you know, we're not behind the eight ball. And then just, you know, let's make sure that we fully account for the cost of each one. And if we do send them out, we recover that. So if there's 1200 bucks each, then when people wanna demo unit for whatever an enterprise engagement, if they don't, you know, if they want one, they're 1200. If they, you know, if they can't cost up to $100 and they're probably not an enterprise customer anyway. Okay, well, I think at least for a week or two until Charlie gets kind of settled in with things, he's not gonna be available much. So you might need to look at another option or might just, yeah, maybe we should just have a separate meeting about this. Yeah, sounds like a good idea. Okay, status service documentation. What's the status of that, Mr. Gosling? It's proposed to, we haven't really started work on it. So we could probably get this out of the sprint, do you think? Oh, I'm not muted. Great. So your pace has gone on the forum, so discussion. And there's the process data stuff already in the documentation. So I do want to put the overview of the status service into the documentation as well, which I can do very quickly right now. Okay, so we'll leave that in there. Alpha image for both the QT and QV Mark II images. You don't do that? Yeah, are you happy for the QV image to go out already? I didn't know if we wanted to get anything else in there before we relate it to the community. The only thing perhaps would be that Spotify task, get the Spotify figured out. So I'll do that for me. So to be clear, these are images for the PyCraft, right? The images for people who've built their own Mark II prototype. Oh, okay. So including the re-speaker array and all that? Yeah, I mean, you could use them, people can take them and tweak them for their own hardware and stuff, but I don't want to put any extra effort in to make them, you know, PyCraft-configurable for that sort of stuff. They're really intended to be, this is what we're using internally and there's no reason that we can't share them out. And my question is, yeah, where I was going with the question is, what product does this belong under? So it would be under the Mark II product. Yeah. Yeah. Precise model validation tool. Isn't it? Can you open that ticket up real quick, Chris? Yeah, it's over here on the side. Moving to the next print. This is basically just the VoigtConf tests for Precise and the model. It looks like this is a PR for some of the status stuff. So we need to get that over the go line. That's relying on the status stuff. Okay. And this is part of status stuff too? Yeah. Yeah. So these next several here are all the Wakeboard Collection Epic and I just moved all those from the sprint we had defined for this, into this sprint. We'll put them all in this Epic. So I can pretty confidently say that that's gonna keep me busy for the next two weeks. And hopefully I'll get more than this done because a lot of this stuff is just applying our schema discussions to things I've already done. But yeah, so that's one of my main things to get done in the sprint is this first part of the Wakeboard Collection process. Right. So that'll give us the back end, the database and that sort of thing. We should probably have a meeting during this sprint to start planning for the next sprint in terms of the UI and the objectives in terms of the tagging system. So we can start the next sprint. Yeah. So can we add a task to this sprint to have a meeting to discuss UI and what are our first targets in terms of tagging, that sort of thing. And we'll probably have a bunch of other tickets come out of that that we can then put into the next sprint. So that should be basically open to all of us. So let's wait until this gets back and Derek should be at that one and all that. Okay. So I can schedule that while I assign this to me it should be not, which are you out this week Chris or you out next week this week? Okay. So I'll schedule it for sometime next week. Yeah, sometime after like not Monday next week but after Monday next week. Okay. Okay. So I guess the next question then is do we all have enough to do in this sprint to keep us busy for the next two weeks? I would say in my case, the answer is yes. So I would throw that over to, I guess we can start with Gazz. I guess you only have one week to do the work in the sprint. So you have enough in here to keep you busy for the week do you think or? Damn me button. Can I go back there? Yeah. I'm going to be doing like, I don't know maybe I should add an item that's like do the 20.20.08 release. Yeah, I was just going to say just that. Even though it's a separate, if we're kind of now thinking of this micro sprint 13 as being the overarching defining feature but I mean 20.08, the 20.8 sprint will be in our sprint until it's finished. Okay, so I will move then all of the 20.08 issues in that sprint. I'll move them into this sprint and assign them to you if they aren't already. Do we have a? You're probably just going to finish on the finished ones, but yeah. Do we have a task in here for the actual release or is this? No. Well, because it was being tracked as a sprint and everything was done and then it would be finished. But I think, but yeah, I know. We definitely should add an item for the release itself. Yeah, so one of the things is I just had the actual checklist which is in a separate document as an item but obviously the checklist itself is like, all of the things that need to happen. So I'll pull those out into like the remaining tasks and make them separate items so that you can see exactly what has to happen. Okay. In case I get eaten by a crocodile for example. Or a dingo. Yeah, or a dingo. Okay, I'll let you do that and I'll go ahead after this meeting. I'll move all these down. So between 20.08 and these other smaller things you're gonna be good for the sprint, you think? Yeah, right. Mr. Ken, you don't have any tasks for the sprint. Where are your tasks and how can we move them in here? Well, I just looked that up while you were talking. Why don't you, to make life easy why don't you just tie me into a PREC-69? Put that in the sprint. That's the main task or the parent task for all the stuff I'm working on. So instead of bringing over five to eight tickets just bring that over. PREC-69. And then when you click on that that'll link to all the sub tasks, tickets. With the challenge then we're not gonna be able to finish PREC-69 at the end of this two weeks, right? I think my stuff on 69 will be done and short of the new data schema being stood up. And if I get done with what's on 69 and the schema is blocking me I'll move into the middle ticket. I can tell you what that one is too. We were kind of working from the two ends into the middle. I don't see that. The one that I'll move on to after 69 will be, well, it's a user community tag and we've captured data which is what we have our meeting for. So I'm not blocked. I mean, I'll have most of the stuff done by next week. Certainly. And I have other things I can work on but that particular one is a PREC-68. You wanna move that over into here. 69 is in progress and 68 will be to do. I'm gonna get done with that. Yeah, it's a little messy because I don't have delete privileges. So if I create a ticket and then I wanna break it into sub tickets, I have them both. I don't see you 69. PREC-69. I'm kinda filter on that. I mean, you have to clear your filter. Yeah. You're probably filtering on Minecraft, Project Minecraft instead of Precise. I'm in the Precise. No, I'm in the Precise. But it's showing you that little issues are visible. Or is that just the search? It's filtering. Sorry. I literally just go to flash, browse, flash. Yeah, I would just put any ticket. Yeah, I would just type it in. Can I go back to the, yeah. Got a little bit lashing. Flash, browse, flash, tag. There you go. So just move that guy into that sprint and you're good to go because this is all what I'm working on. Doesn't want to let me, you had to do a sprint and maybe that's, it's a sub task. That's why. Okay, move 60 over if you want. 60 is kinda like the main ticket that covers the three sub tickets or three sub projects. What if we turned Precise 60 this parenting into an epic? Would it then, would the subtops then automatically become top? That sounds nice. If magic happens. Well, it'll add 60 Chris. Yeah, 60's in there. All right, cool. So we're good. All right, will you finish? So the tagging actually wouldn't be included in the sprint. So we may need to break this out a little bit. Yeah, well, tagging is what we're gonna talk about next week. You're working on basically 67. I'm working on 69 and 68 is where we meet in the middle when you're done and I'm done. But we don't know what that is yet because we're gonna meet and discuss that next week. Okay, I think what I'll do then is I'll create, I'll make this an epic instead of a task. And then if you, Ken would take, so it looks like, so I'm a little confused. Part of this, I have an epic for data collection, data collection, which is what we're working on now. Should I, I think the second epic would be tagging. I don't know how you wanted to find it, but what this is, is this is phase one of the precise goals and roadmaps of which it has three sub tasks, which is capturing the data from the devices, tagging of that data, and then integrating that into new model creation. You can break it up however you want. Okay, I mean, I could rename the epic to be collection and tagging. If that makes more sense, if it's all. Okay. All right, one or the other, I'll move this stuff around so that we're all working. So you and I basically, this is working on the same thing. There's some different ends of it, so we'll just. Yeah, yeah. And then, you know, after next week we'll probably be working in the middle together. Yeah, probably. All right. And Mr. Derek, do you have, we'll get back to our sprays here. Let's show one. There's a handful of work to prototype things in here. Do you have enough in here yourself or do you have more to do? Yeah, yeah, I have enough. I put in the first full assembly of the DevKit SJ201 design back on the plate. So that's, and I do have, I got the Ultimaker 3D printer now. We bought another 3D printer, the FDM style to do this design, make sure that it'll print on those. I don't know if they can, Kevin then make his own prototypes but then, you know, eventually the community can as well. So that's, I guess achievable in the next two weeks to have the first draft of that printed. And hopefully, fingers crossed by the end of the week we might have boards actually working boards here too. So yeah, between that and the rest of the things I should, that was the new kind of the new thing. I should have enough to keep me busy. Plus I'm expecting stuff from our meeting next week on the tagging, if you like. All right, so one thing I wanna make sure we get out of the sprint planning going forward is actually plan the sprint. Every task in the sprint should have somebody assigned to it. So we know how much work we're expected to do. I think we're there. So yeah, I will list, Michael are you happy with the contents of the sprint? Yeah, that's the script. I think I will start it. Actually, you know what? I'll start it after this meeting. I wanna move the core 2008 stuff into that before I start it. So yeah, and the other changes we talked about like renaming the hardware project to the market project and stuff like that. Yeah. So by the end of today, I'll have this sprint started. Just administrative note real quick before we move on. Did I hear that we're actually paying our interns? Yes. We always pay people a living wage, like we won't take advantage of people whether they're in the United States or outside the United States. Well, we have plenty of money to treat people ethically. Right, but you can also get on the local universities program and they can often use a summer internship to gain credits. And... Yeah, we've been with a couple of those programs through the WillCats up at the KD Small Business Development Center where they've assigned some masters level students to help us with some business planning stuff. And the outcome has always been not tremendously useful. We find it's a lot easier. I'm happy to have university students in and we're not going to make them rich, but we do pay enough money that they can pay their bills. Mycroft is not hurting for money. You know, we want to be generous where we can because there may come a time when we can't do so. So yeah, but I hear you, I know that for some people it would be valuable experience and they are willing to work for free, but if we can find somebody who's got that level of enthusiasm, imagine how more enthusiastic they'll be when we're paid. Yeah, and we can find them fairly quickly. Like when I found Charlie, it was, you know, I posted on a KU job board in engineering and I had applicants the same day. Now, Charlie was good because he knew how to do everything like solder and, you know, he was familiar with electronics and all that stuff. So, you know, there is some screening to be done, but if we want to get another, a different intern if Charlie doesn't have the time because of other obligations, he's just a senior here. We should be able to find another intern fairly quickly if that's the route we want to get. Now our competition has been known to work interns for free, to make people cry at their desk, to drive their employees into unhealthy situations, to, you know, create working conditions that are inhumane, to outsource their manufacturing to places that have no environmental regulations and a very little labor law, and to exploit those people to bring ultra low prices to their customers. But we're not that company. Not yet. Wait, no. But we're working on it. So, all right, so we've got a sprint plan for the next week. Are there any other issues that people'd like to discuss? Just a call out to the community. If you're not running Dev, please do so for the next couple of weeks. Well, for the next week, just to catch any 20 or eight bugs. There shouldn't be any, but there should never be any bugs. You're the first software developer I've ever heard say that. Yeah, I might, I've done the draft release notes already, so I might post those up in the chat so that people can see what's coming along. But yeah, not so many breaking changes, so everything should continue working smoothly. All right, great. And I believe Derek alluded to this, but we are anticipating getting our second spin of the SJ201 boards in today. Assuming they don't get lost in the mail at the last one. And so, that'll be exciting. Yeah, incidentally, the last one did show up today. So, but we've already talked about that there were other problems with the board. It did show up. Those mail sorting machines weren't necessary after all. Well, actually it was the USPS that came through. I think it was, it got delivered to the wrong address and some kind of Samaritan got it in the mail, the US mail for us. Yeah, it's very nice. All right, well, then we can keep it short this week today and we'll talk again on Wednesday. All right, you're voting on Wednesday. See you on the next week. Thanks folks, thanks for hard work. Joe, you're welcome out. Thanks.