 Welcome, it is December 2nd. This is the Minecraft Developer Sync. And we're just going to go around real quick and check on everybody's status. Giz, how's it going? Yep, you went through the Pantscore, you went through vocal images showing the GUI and some minor fixes on the back end, which means that all the Minecraft CLI and all those tools are now working again, which is good. So, and Ken's got his PR up, so I think once we get that in, it should work. The Wi-Fi Connect is not wired up yet, but they're working on that at the moment, and then we'll get back to the things like the UDEP rules and those little things, which should theoretically be fairly quick. Okay, was there a problem with the Wi-Fi Connect? I thought that was the next thing on the list from yesterday. Yeah, they were working on it yesterday, and I thought they were going to have it done by the end of the day, but I didn't have something working this morning, so presumably not. But they're asleep now, I'm sure. Right. Okay, but no, you don't know of any blockers that have come up. That's just taking longer than expected. All right. What's important for me, by the way, is that they get them so they can boot off of a USB drive, since I can't burn an SD card here without going out in mine. All right. Well, hey, Josh, you're next on the list, so do you want to go now? I broke my touchscreen. So yesterday we had a good sit-down in the afternoon and came up with a long list of questions that needed executive action. Forward those on to Michael for consideration and action, and then the decision was made to go ahead and start moving forward with getting dev kits shipped. Gez has asked me to make sure to let everybody on this call know that the dev kits will be in people's hands by December 24th, so please feel free to buy them and give them to your family for Christmas. No, we still don't have an actual ship date. We're targeting the end of this year or early next year provided that we can get all of the stuff that is coming in. The decision was made to ship the dev kits as three separate SKUs, the basic dev kit that folks bought on the Kickstarter, the basic dev kit with a camera is the second skew, and then an advanced dev kit that includes laser cut parts and resonating chambers and additional driver and all of the other goodies that allow you to actually open up a box and assemble this, so that will be available to folks who are interested in upgrading from the basics. And then I had a good meeting with Derek about all of these parts that he's been going, so that has now been handed off to the business development team. And finally, they got new resonating chambers printed. We're trying to get these to the point where they can be printed as an easy to do print. There's still some quality issues with infill and some overhangs that are properly supported, but we're getting very close to having something that you can just stick on an FDM with no support and hit print and it goes. So that's very exciting. When that's it, it's still early in the day. I'm looking forward to spending the afternoon on the phone with China and Taiwan and starting to get all this stuff moving through the door. We have a product, so I'm excited and I hear through the grapevine that we'll have an image in the next short period of time. It has been promised in the near term that I've been working with developers long enough to know that that's not always the case. It's not over. Tell it's over. So, all right. Well, thanks, Josh. Chris Vair. What did we decide on? Well, I have spent last 24 hours. I went through, excuse me, I went through JIRA and I talked to Michael about my next project. So I went through JIRA and did a little cleanup while I was waiting to talk to him. There's a new epic called account management. One of the things on my desk is going to be to make sure all the bugs and little things that are niggles with account management get solved. So onboarding is a good experience or a better experience is already good. So I went through all of our tickets. I also close a bunch of them. There are a bunch of key me tickets I closed because as won't do because we've mostly abandoned that. So that kind of stuff. I did a lot of that. Today was a lot of meetings. I talked to Michael a lot today about metrics and user management and what we're going to do with the memberships going forward. So that's the kind of stuff I'll be working on coming up. And I also talked to Ken a little bit about the API call on providing him for precise model training. So I just need to give him some examples of how to call that endpoint and then you'll give that some testing. And tomorrow we'll be trying to implement a couple key metrics. Josh is maybe listening. One of them being daily user activity. So once those are done, then I'll start doing some of the other things. I thought you'd enjoy that, Josh. Once he starts doing that, then I'll start doing some design work on the new account management stuff that I talked about today. All right. Sounds good. Ken, how goes it? Fine. As Chris mentioned, I went over some of the API stuff with him and I'll be moving on to that probably tomorrow. I spent the day getting the pull request actually working because, you know, it was working on my device, but my device turned out had artifacts from an old code line. So when I finally got my new pull request up, my new branch up, and then overwrote everything on my system with that branch, there were breakages, which really surprised me because I figured that would have got caught in Voight-com for in the build process. There was like missing modules and it was throwing exceptions. So I don't know why it built cleanly and I got a clean bill of health. We'll have to look at that moving forward. But yeah, so I actually got everything working on here. Just because you have an image doesn't mean it's going to work. I have no idea if the VF control USB that we have for 64-bit will run on their 64-bit image or not. So there's that sort of stuff. There's permissions regarding being able to run a pseudo. I have an easy fix where I can give you a one line to add to your pseudo errors until the Udev's done. But the point is it's going to be a little bit of a hump. So that's why I'm kind of pushing to get this code into the next build and then I'll recreate the image on this device here from the Panicor stuff clean and be in the same boat as everybody else. So that's kind of what's going to be consuming me is tracking still on the Panicor stuff and getting that build working on our devices and then moving over into the new training stuff and building out some code. I mean right now that stuff is a very simple script and what I really want to do is break it into a Python file so that each of the decision points calls out to decision makers. They can be really simple now and say if the file count new file count is greater than 100 that's great but at least it'll be a placeholder and then later we can enhance that and expand it to the actual balancing algorithms and stuff. So I'll be working on that and again looking at the closely at the Panicor stuff. Yes, when do you think you'll have the pull requests that I put up there merged into feature slash mark dash two because I'm assuming that that will be magically available the next time I go to burn an image, right? I'm muted. That's yeah that's right. I think there's just I want to just make sure that yeah it's it's it's all working so there's a couple of little things we'll need to change that I mentioned in the chat just before. Yeah, the off you're going to have to talk to them about if you don't want it in the main config, right? Sorry what was that? The opt config if you want me to pull that out of the main config and put it there you'll deal with Panicor about that. Yeah yeah so we'll put that in the in the etc config in the device level config. I also yeah I just want to like pull out like the vf control usb driver you know we don't want that in core and then there's some like where do you want to pull it in? Well at the moment we're just going to have to put it in the build recipe but but I also would see that build recipe is going to come from it's going to have to pull it from some static asset location, right? Yeah the file's got to live somewhere. Yeah so I think I think we'll throw it in like micro-off devices for the moment until we get the actual how. Well why don't we why don't we do this why don't we leave things as they are on that pull request for now and let's get this working and then what we can do is we can go back since we're going to have a bunch of other things that probably have to be altered for the Panicor build and we can get all those at the same time rather than holding the process up at this point until we can get the opt config deploy and until we can get all the others. Just if we eventually want to merge. You guys can problem solve one-on-one. I appreciate that you're eager to solve problems but let's get to that right after this meeting. Two comments, well questions I guess. Ken, that the VK test didn't catch things and said that your pull request was good when it was not is concerning so. I don't think the VK test runs on that PR so because it's not going into our mainline code and I just had a quick look. Okay so it didn't run at all that was the thing got it. Okay well that's good and maybe something to look at. Well wait a minute I'm not sure that's true. Well I thought in my thing it did run. Okay well that's another thing to look into then because it really should catch those things and then the other thing was yeah I mean ultimately I don't want to you know pollute core anymore than it already is right. We should be I mean I think we discussed putting all the driver stuff in the in the HAL repository and that VF control should be built from source right it shouldn't be a binary file so. Well wait a minute wait a minute so this was my response back to guess which is the HAL is a concept right now. Yeah. So don't speak of it as if it's a tangible object. Okay well you know it's like well we should get this in the HAL well we don't have a HAL right the point is we don't have a working image. I'd like to get a working image from PanaCore that I know is not going to work until I have a chance to spend a day or two with it and then back and forth repartee with them to get that stuff in the process. And so all I'm recommending is we get it working first we can worry about optimizing it and making it look pretty and extra spaces and changing the names after it's functionally working. I thought I heard somebody saying they wanted to send out dev kits sometime this year. All right I just want to make sure that that this doesn't become another one of those artifacts that we're you know gnashing our teeth about. It sure does sound like it's not going to get overlooked. So you can spend an awful lot of time picking things like this. I mean we really need to get you know some traction we need to get some images out there we need to get the product in people's hands I actually have a luxury all right all right all right and we need more skills. I wonder if we I wonder if we actually intentionally never merge this into you know if the aim is to not merge this into mainline like we put it in the feature branch but instead of merging that feature branch into mainline we should be pulling most of that all that stuff out to the how for the production release. There you go so let's just go ahead and get this image built and get everything working on this branch. We can worry about merging in the master town stream when we have something working that we want to merge. All right okay so it sounds like you're still wrestling with some of those issues and you're not going to be able to get to the wakeboard stuff for you know no no no no that's wrong I'm done I'm now blocked by Panicor and having a working USB bootable image from Panicor that fires up and does wi-fi and gotcha okay so you are moving out of the wakeboard stuff now but you said something that concerns me so is it the intent moving forward that things like vf control usb and possibly the kernel driver will be built at on-demand and not having a binary elf created and then that deployed because if that's the case then we need to again that probably falls on Panicor but we need to communicate that to somebody. Yeah let's talk about that I mean there was a make file concept that we talked about in each of those HAL directories but as you pointed out we don't have those yet but there's going to be a lot of you know firmware and stuff like that that needs to be captured and maybe get updated you know from time to time so we need to make sure that that stuff is is getting built properly. Yeah so basically the the status for me is unblocked until Panicor has a USB bootable 64-bit image that I can then see if our stuff works on and if not get it working on it so while I'm blocked I will go off and work on the wakeboard stuff because there's going to be some you know uptime I haven't worked on that in two months it's pretty complicated I got to get back in and look at the documents I put on wiki and get my bearing so yeah I'll move on to that. Sounds good right thanks Derek. All right so yeah I had a good Josh mission to sorry but a good meeting talking about how we move forward ordering parts so I kind of handed off this is kind of what we're working with now and you know I talked about you know we could maybe shave some costs off and we negotiate here and here or you know explore this alternative parts for a couple of things so Josh and Chris and Johnny thankfully for me have offered to to take that off my plate and to start that problem which leaves me to work more on you know documentation and continuing to tweak and refine things so that's mostly what I'm working on today is getting things ready to talk to a possible assembler solution tomorrow so I sent out an invite for that just a little bit ago haven't hurt back yet but I hope they've been working something out he's got the parts I sent them overnight so he should have those to evaluate and I've been working on other things to kind of describe what that is in terms of pictures and documentation and stuff. Yeah so we continue to do that and then based on Josh and Josh's conversations I do have a couple revisions that I'm going to try and make pretty quick to mostly audio chamber so I'll be working on that tomorrow as well so I can just get that done and then start a test print the idea there would be to try and get the audio chamber down at just one part which could save us a cool box and then so some possibly don't need adhesive such so yeah that's me for today and tomorrow. Awesome okay thanks as for me I think pretty much everything I've touched in the last today has been covered by somebody else Chris Vair I've been working with and prepping for earlier today and then I've been in meetings all day with Josh and other people so so that's pretty much it for me we have yeah we're moving on to some discussions with the people who are going to be doing fulfillment hopefully tomorrow so that's something to look forward to and yeah so still looking forward to getting my getting the software deployed on my device here so eerily awaiting that but sounds like things are going we're moving and there's a chance that we'll we'll you know get these things out by the end of the year but that's certainly not a promise and especially given the holidays in the covid situation but but we are ordering parts now so it is in process that's it we'll talk again tomorrow thanks everybody guys are you and I supposed to result