 Okie-dokie. Hi. Hello everyone. This is the Circuit Python Weekly Meeting for Monday, December 27th, 2021. This is the time of the week when we get together and talk about all things Circuit Python. I'm Dan. I'm sponsored by Adafruit to work on Circuit Python. Circuit Python is a version of Python designed to run on tiny computers called microcontrollers. Circuit Python development is primarily sponsored by Adafruit. So if you want to support Adafruit and Circuit Python, consider purchasing hardware from adafruit.com or our distributors. This meeting is hosted on the Adafruit Discord server. You can join anytime by going to adafru.it slash discord. You hold the meeting in the Circuit Python dash dev text channel and the Circuit Python voice channel. Basically this meeting is on Mondays at 2 p.m. Eastern time, United States time, 11 a.m. Pacific time, U.S. except when it coincides with the U.S. holiday. If the meeting time has changed, you'll see notices on Discord. If you want to get notified about changes to the meeting, we can add you to the Circuit Pythonistas Discord role. So just ask. There's also a calendar available that we try to keep updated if you'd like to subscribe to that. That's a Google calendar. This meeting is recorded. We record audio from the voice channel and video of the text channel, which is the Discord window. If you'd rather not have your voice recorded, you are still welcome to participate. This meeting will be posted on YouTube and video forum and the audio is released as a podcast. If you find this podcast is not available on your favorite podcast service, please let us know. There's a notes document that accompanies the meeting and the recording. If you wish to participate but can't make it to the meeting, leave stuff in the document and we'll read it off during the meeting. So we'll start with community news. You can go to the notes doc. I'm going to paste it in here so you can take a look at it. It's in the chat in the CircuitPython Dev channel. So we are honored today to have Lady Aida here in the voice channel and also Phil P.T. from Aida Fruit. Phil is doing the CircuitPython newsletter, the Python or microcontrollers newsletter this week. Phil, would you like to read the community news? Yeah, the document is not set to share, it looks like maybe. Really? OK, hold on a second. You can get the right link. Yeah, I will... There we go. I'll keep the room going so there's no dead air while you're doing this. Let me hit refresh on the doc. I'm still getting access denied. I think you got to set it to link anyone can view, but let me see if this one... Oh, there we go. Great. OK, community news. This is kind of on me this week, so I'll tell you the plan and this is going to be in the newsletter that I'm working on. So the plan and I said this joke sort of in our meeting before this that we have with our team. Everyone has a plan until they get punched in the face. I was a Mike Tyson quote. So my plan was like, hey, like ants would do an amazing on the newsletter. The team's been going. I purposely have been diverted on helping the lady in our team run Adafruit all during this time from COVID that's still not gone to supply chain issues, you name it. Everything has been happening in the last 18 months. So the plan was, hey, give Anna break. I have I always try to have some writing time the last couple weeks of the year to catch up on stuff, be reflective. And thank you notes to people you name it. I try to do that. And of course, Omicron, which is I think one of the Decepticons or Dinobots or whatever decides to show up and everything is getting shifted and moved. The Adafruit team is doing fine. I figured I would let everyone know. We don't do a weekly update on ask an engineer and show and tell because a lot is the same as far as like everyone's vaccinated. We have paid time off for anyone who needs it for taking care of others or for COVID testing. We have a whole thing on our site, Adafruit.com slash open safely. And we also on brand be as transparent about everything as we can because a lot of people they're they're trying to get through this and they're trying to run their own companies. And there's not a lot of good information and certainly a lot of folks are reluctant to share what they're doing and protocols and all that. But we've been trying to set a good example and say, here's what we're all about. A lot of companies, a lot of people have emailed like, hey, can I check out your handbook and heard you do paid time off for charity or I heard you do this or you do that. So that's been one of the things that we wanted to do. And over the last 18 months or so, you know, there's been a few times where like, oh, you know what, I really want to stop doing show and tell or this is we're so busy and we're so exhausted. Maybe we should we should take a little bit of a break or something. But we also know how important a lot of these things are to a lot of you out there and certainly the community. So we're just going to keep doing this and we're going to do this for as long as we're we're alive. And for the newsletter, the plan was give Anna break and, you know, kind of have like a wrap up. So I don't have as much time as I thought I would, but I'm still going to do. I have a bunch of things that I did manage to get done for the newsletter. So some of it is going to be how we come up with names of things. Some of it is just some stories about how Adafruit works, how we how we build things together as a community. Because I the genesis of of circuit Python and Katniss here coined the phrase code plus community. It really is the way we steer this ship. It's it's it's always something that I think people can point to and say this community listen to each other. They're elevating each other and they're bringing other people in and that's how we're we're growing it. So if you haven't already go to Adafruit daily, plan up for the newsletter. We have over 9000 people. I put a little note in why we do things that seem very different encounter intuitive. Adafruit daily is a separate site not connected to Adafruit store account. There's all these things that we do just to show and demonstrate that we're not going to spam. We're not going to harvest emails. We're not going to do anything like that. We don't even want something confusing where someone like, oh, maybe I signed up for newsletter. We want to be really respectful of everyone. And I think that's one of the things that have helped carry us all the way to here is we try not to let you all down. So with all that being said, this week, however, no show until no ask an engineer because we are going to take off that little bit of time. We are going to recharge. Lady, it is working on a ton of hardware and we decided, well, I think we could do a few small videos during the week of the last week of December. But if we can feed Lady to either dumplings or usually some type of tasty high carb thing, engineering and products pop out. So that's the plan this week. So a little bit of a community news that's all over the place, but mostly I want to say thank you to everyone here for being so supportive of the team each and every week for doing these meetings. When you look at the last, I think, Circuit Python newsletter we started in 2016, you can look back and see all the progress and all the things that we've been able to do together. So I just wanted to say thanks to everyone and hopefully this way will go away as fast as it came upon us. And I hope to return to doing newsletters and a lot of the other things. Our Lady, it is here too. Lamor, do you have any end of year things you want to say before we both bounce to the next thing? Well, we did a lot of stuff this year, which is pretty cool. We've got new chipsets like the ESP32S2. Scott has had a lot of fun working on native Bluetooth support, which has been really good. It means that we can support more chips that don't have USB but do have Bluetooth. And there's also, of course, more chips that's coming out with BLE, as well as the native Raspberry Pi support, which has been super fun to watch. It's kind of interesting to see how can we use Circuit Python as a non-OS programming language. Kind of reminds me of the Apple IIs that I grew up with where you start up and it's like, hi, I'm in Apple Basic and you can code it immediately. There's no Finder or anything. But I think a lot of it has been more support. I think we're finally getting to a lot of stuff that's been on our list for a while. We did a lot of low-power stuff. This year, we're doing asynchronous support. We did RP2040 support. So it's a lot of stuff got done. And it's been cool to see, especially with boards based on the RP2040, having that native HID support that we cared about very early on became a very powerful factor in people wanting to pick up Circuit Python and use it. So I think there's sometimes we add stuff to Circuit Python support and we're like, oh, this is sort of fun and we don't really think about it. But then years later, it kind of becomes the most important thing. And a lot of that is based on tax work with Tina USB that allowed us to have a very consistent USB experience. For me, a lot of it is learning from doing Arduino for 15 years. What are some of the things I wish that we had done earlier in Arduino development, language development, kind of bringing all those lessons into Circuit Python, which I think has been successful. And I can't wait for people to learn from Circuit Python and bring those lessons into other languages. So really good stuff, a really strong community, a lot of contributions, a lot of new boards. I think we have like 265 supported boards in Circuit Python, which is great. And it's really easy to add more. There's like a new one or two added every week. That's good. It means there's a lot more buy-in from other companies, a lot of people. People want to see Circuit Python on their hardware. They see how easy it is. It's one of the easiest languages to add support for. We have a guide on how to do it and we have a beautiful download page. And I think that's awesome. It's also supporting the greater ecosystem of maker companies and open source hardware companies. People can design hardware and then they focus on the hardware. They don't have to think as much about the software because that's taking care of basically for them. And then hopefully they contribute guides, tutorials, or libraries, what have you. And I'm starting to see it. More companies releasing hardware and saying Circuit Python is supported. And you can get first class support for free. And that's what we're all about, doing open source hardware and making it easier for people to use Circuit Python, doing more and more documentation, more and more libraries. Just having a really good experience overall. I think Circuit Python is surprisingly powerful. And it's always fun to see people have that joy when they use Circuit Python to see like, okay, here's how electronics can work. It can work in a way that's easy and maintainable and fun. That's my yearly update. Oh, okay, well worth it. Does anyone have any questions for one more night before we bounce on to the next? Well, I guess I just want to say I'm still learning how easy Circuit Python is. And that's a weird thing to feel after you've been using software for a couple of years. Yeah, I love it. I'm so happy to be working with it. So thank you both. Yeah, I think one of the observations that I see a lot is it's weird to say is everyone is expecting the worst out of all things technology related. And when they start using Circuit Python, they won't have to get over it. It's just like, oh, wow, that was easier than I thought. Oh, wow, I didn't have to download an ID. Oh, wow, this is not some weird, terrible thing. And it's kind of a shame because we're all just kind of beaten down with what has happened to us. But it's also very refreshing that it just means that this is possible. And I hope folks will look at Circuit Python and MicroPython and a lot of things that Adafruit's worked on and a lot of things that Lamar's worked on, a lot of things our team worked on and said, well, maybe there's other things that can be easy and fun and inclusive. And maybe things don't have to be as terrible. And maybe things, it's not all doom and gloom. And I think it's hard to be an optimist sometimes. But when you use technology and you can see the impact it has on people, all the things with AT makers and Bill's work, we just posted up a video not too long ago that Bill made with Elsa. And you can see people that are able to communicate because of some code that we thought was going to be interesting for like keyboards or something. You can see how life-changing it is. And then you can see people running businesses for the first time and they don't have to do all the same things that we had to and kind of suffer through a lot of stuff. So anyways, I agree with you 100%. I have to remember too that sometimes I fall into old habits when I go and look at a project I want to do. And I'm like, oh man, this is going to be terrible. And it's like, oh wait a second, actually this is really easy. And I have to remember that we made things easy. And it's because things were terrible and hard before it doesn't. They always have to be. Well, Dan, I'm going to hand the mic back to you. DJ away. All right. Thank you very much. Thank you very much for all of the more. Thanks for stopping by. See you later and subscribe to the newsletter. Yeah, definitely. I'm ready. And I will talk about that in just a minute in more detail. Okey-dokey. So we'll go on with a couple of items of community news. It's a light news week. But a couple of interesting things happened. Mu, the first item is that Mu 1.1.0 beta 7 is out. That fixes a number of problems running on several different platforms. And please go ahead and go to codewith.mu and download the latest version and try it out and report any problems that you've been having. And then also to note is that the least candidates for CircuitPython 7.1.0 are now out. I'm going to put a timestamp in about that. RC.0 came out on December 23rd and we made a couple of minor changes for RC.1. And if nothing comes up in the next day or two, we will release RC.1 as 7.1.0 final. And then we'll be able to start having 7.2.0 alphas and betas, which we can only have one series of alphas and betas at a time and that's been a bit of a problem. So watch out for that soon, we hope. Alright, thanks very much. And as Phil mentioned about the newsletter, if you want to contribute, you can find the CircuitPython Weekly newsletter. It's really the Python and Microcontrollers newsletter. It has more than CircuitPython in it. The archives are at adafruitdaily.com and you can subscribe. And you will, the subscription is only for that. You don't have to worry about getting put on some other product mailing list or anything like that. If you want to send, if you want to contribute something to the CircuitPython newsletter, anything that you see that's of interest, send it to cpnewsatadafruit.com or mention it in Discord or tag us on Twitter. Any of those mechanisms are fine for getting stuff to us. So now we'll move on to the next section, which is the state of CircuitPython and the CircuitPython libraries and the Blinka libraries. I tried the statistics here. For some reason, the run last night failed. GitHub was having some trouble around midnight last night. And so this is Saturday midnight, Sunday morning's data, as opposed to Sunday midnight's data. But not a lot happened at yesterday anyway, so it's not a problem. So overall, we had 65 pull requests merged during this holiday time. There were 15 authors. And of note, there were some new authors that we haven't seen before, maybe from this week or last week. Smankusors, Danny Staples, Ezen010212, DroneCZ, and Tim Hawes. Thank you very much for joining the community and computing things. We had 11 reviewers of those pull requests, and we had 31 issues closed by 10 people and 10 opened by 10 people. So it's nice to see a bunch of net gain in the closed issues. In the CircuitPython core, let me take another timestamp, we had 19 pull requests merged with eight authors and six reviewers. We had 15 open pull requests. A bunch of those are on hold or are drafts. So it does not reflect a lot of pending work necessarily. There were 10 issues closed by five people and four issues opened by four people. And right now we have 462 open issues. A lot of those are long-term issues, enhancement requests and the like. And for fixing in the 7XX series, there are 15 open issues, and for fixing in 800, there are 10 open issues. And we've got a few other various kinds of issues, 17 library issues, seven support issues, and what issue that we need to figure out where it belongs. But we're in good shape. So, Katnie, can you go ahead and tell us about the CircuitPython libraries? I can. So this section is about all of the Adafruit CircuitPython libraries, which is everything that starts with Adafruit underscore, CircuitPython underscore, as well as a few extras. We had 45 pull requests merged, which is excellent. We are not in the middle of a sweep. So that is that high number is actually a series of non-related PRs or some of them may have been related, but it was not intentional. We had nine authors and eight reviewers. The oldest merged pull request was 525 days, which is amazing to see. We are getting through a lot of the older PRs, leaving us with, wait for it, 37 open pull requests, which is significantly down. And the oldest open pull request is 470 days, and that is significant because I believe previous to this, the oldest pull request was in the 700s. So we are finally catching up and I'm very excited about this. We had 20 issues closed by five people and six opened by six people, leaving us 629 open issues. 242 of those are labeled good first issue. If you're interested in contributing to CircuitPython on the Python side of things, check out circuitpython.org slash contributing. You'll find all of this information and more, including open issues and open pull requests. If you're interested in reviewing, check out the open pull requests and see what is there. If something interests you, if you have the hardware, give it a test. If you don't, you can look at the code for syntax, et cetera. And just leave a note that you did that. And once you've done that a few times and you feel comfortable with it, we can talk about upgrading you to the review team. If you're looking to contribute on the code side, check out the open issues. If you're new to everything, good first issue is a great place to start. Otherwise there's bug or enhancement. Find something that interests you. Let us know that you're working on it. And we're available to help you both on Discord and also there is a guide on contributing to CircuitPython using Git and GitHub available in the Adafruit Learn system. In terms of library updates in the last seven days, there are no new libraries, but there is a short list of updated libraries which I will not read off. And an early hug report, which there will be another one later, for FOMI guy who is going through the older pull requests right now and getting caught up. And like I said, that's a really important thing, something we really haven't had the cycles to do. And FOMI guy stepped up and is taking care of that. And that is a really excellent thing. And that's what we've got. Okay, thank you, Katnie. Okay, since Melissa is not here this week, Jeff, would you like to read the Blinka section? Sure, why not? Just give me a second. So Blinka is a library that brings circuit Python compatibility to MicroPython single board computers and a lot of other fun little stuff like USB dongles. So you can run the same program on your host computer. And in the last week, there was one pull request merged from FOMI guy reviewed by Melissa. There are five open pull requests within Adafruit Blinka and related repositories. Issues-wise, there was one issue closed by one person and no new issues. There are 67 open issues and you can track the ones in Adafruit Blinka by going to github.com slash Adafruit slash Adafruit underscore Blinka slash issues. You know, people are using the software because within the past month, there were 14,268 downloads from PyWheels and the number of supported boards is 85, which probably does not fully count the MicroPython variance where you could run it. And that's what's up with Blinka. Okay, thank you very much, Jeff. Okay, we'll move on to hug reports. Hug reports is a chance to highlight folks in the Cirque Python community and beyond for doing awesome things. We'll read this in order. I'll start and then we'll go alphabetically after that. Some people are text only and I'll just read their contributions. We really welcome hug reports. Hug reports are the opposite of bug reports. They really acknowledge people doing great work. Okay, so I'll start. I'd like to say thanks to Jeff who did some temporary fixes a few days ago to Cirque Python builds that were breaking because of some underlying stuff that was breaking and he quickly made some patches so that we could continue making sure that the pull requests run through to completion and make sure that they're correct. We were able to revert that after the underlying problems were fixed. And since this is the end of the year, I'd like to give a group hub to the entire community for a wonderful year of projects, community support in Discord and elsewhere and contributions to Cirque Python, whether it be just helping people or whether it be in terms of code or reviews or anything like that. So thank you very much. Okay, we'd see Grover's contribution now. To Jeff for his insightful RPN calculator guide, it provided me with a needed leg up on one of my current projects. The guide is also an excellent coding style example. Decimal objects are amazingly cool and could help with some other projects. See Grover says, reflecting on all of this year's projects and progress, can't thank the community enough for the unselfish and exceptionally positive support to fuel my personal development and growth. Okay, thank you. See Grover. You're the only guy you're up if you're able to speak now. Yeah, thanks, Dan. This week, Hug Reports first group hug to everyone working on the project and in the community, definitely looking forward to another great year with the project and community. To Dexter Starbird for sharing... They've actually shared several different display IO examples with some vector shapes and some other things. So they're always posting neat stuff and show and tell and on the Discord. Thank you to them and See Grover as well shared a matrix portal snowman with some nice falling snowflakes and stuff this week, which I thought was really cool. So thank you to them. And then to Intel and anyone else that is working on MIU for releasing a new version this week. That's what I got. Okay, Jeff, go ahead. Hello again. I wanted to thank you for the release candidates plural. I'm excited to get so close to version 7.1. And I wanted to thank FOMI guy for filling in on the Friday streams. I know a lot of people are enjoying those. And maybe a hug report, maybe a blush at See Grover for the kind of remarks about my code. And finally, a hug to everybody who's used and contributed to Circa Python in 2021. Seeing the projects in the newsletter almost every week is a high point and it's one of the reasons that I keep going with the stuff that we're doing together. Thank you. Thank you very much. Jerry, would you like to say something? Yeah, thanks. I'll hug this to Scott for in absentia for patiently helping me with getting started on the Broadcom parts. I had a lot of questions. You always had answers. And then I group hugged everybody and best wishes for the upcoming 2022. It's got to be better than last year. Okay, thanks Jerry. Go ahead. All right, so first up a hug to you Dan for running the meeting for me today. Would have been seriously rough without my setup. I'm running mobile on my laptop at the moment. Again, a hug report to FOMI guy for continuing to get through the older PRs. Once he came on with a little more time for Adafruit stuff I realized this would be an excellent time to have somebody go through and get those either merged or closed or whatever it is that is the best option for it. Just something that I haven't been able to do and I'm really excited that it's happening. To Mark Gambler for taking an interesting get any IS-31 going more smoothly in Circuit Python. To Carter for all of his help throughout the year with guide questions I so I just quick story started with Adafruit in 2017 with basically no experience. So there's some very fundamental things about electronics that I don't know or understand and these are things that are sometimes required for guides and Carter always steps in and carefully explains to me what it is that I don't understand and helps me get it to a point that I'm able to explain it to other people which is really the crucial thing for guides and I greatly appreciate it. To Kevin at Digikey for sending me some purple LEDs and some excellent Digikey swag I mentioned that I needed one LED and that I couldn't bring myself to make a Digikey order for one LED and Kevin got me taking care so that was amazing. To everyone who has been there for me throughout the last year I know there's people I'm missing I can barely remember what I did last week if I didn't have it written down so I know I've missed some folks but thank you to all of you it's been a very rough year I've gone through quite a lot and a lot of folks have stepped up and taken care of things and been there for me and I really appreciate it and finally a group hug to all involved in CircuitPython in this community you make it what it is without the community we wouldn't really have CircuitPython so thank you all for being part of that I hope everyone has a wonderful holiday or last week if that's not your thing and that everyone has a lovely new year Alright thank you Cadney Okay I have several text only entries that I'll read in fact all the rest I'd have to read so first we start with Kmatch who says as the days start to get longer it's a good time of year to count blessings just wanted to express my gratitude to Adafruit and the CircuitPython development team and extended CircuitPython library developer and sample code community while software and hardware sometimes are solitary activities it's always nice to connect with kind folks willing to lend a hand it makes each of us better and helps us all grow many thanks you all alright now Mark Gambler Mark thanks DigiKey for randomly picking me a winner for their DigiWish contest and group hug to everyone stay healthy and have great new year alright let me move on to micro dev now group hug to the entire CircuitPython community for awesome projects contributions and support throughout the year wishing everyone a very happy new year and finally Tetrick who hasn't been on discord all that long but has been very helpful and has asked a lot of good questions thanks to FOMIGuy for all their help with the typing PR as an FRAM library work FOMIGuy thanks to FOMIGuy and Paul SKPT for helping me get a quick quick fix through for an issue in the display text library thanks to Jepler for starting on making a font typing protocol that will make the typing easier for end users to understand thanks to Dan H for always answering my random questions on discord and github so I'm never stalled thanks to Caddy for checking in about letting me help out with some infrastructure stuff that I'm interested in helping to make a welcoming community and a group hug and happy new year alright now we move on to the status update section of the meeting last week I fixed one major bug alarm.wake alarm was not getting set properly when a sleeping program woke up from fake or real deep sleep so I fixed that, that was a regression that appeared at some point in the 7.0 series that was the last bug that we considered serious enough to fix for the 7.1.1.0 final there's still a number of 7xx issues most of which we would hope to address in versions after 7.1.0 and then last week I released on two release candidates, first 7.1.0 RC.0 and then 7.1.0 RC.1 on December 23rd and on Christmas respectively RC.1 was only minor changes, it turns on I2C power by default QDPy ESP32S2 board, L88 worked on that fix and also I updated the Fresno libraries properly which I hadn't done for RC.0 we're not sure when we're going to release 7.1.0 final but I think I'm going to do it tomorrow or Wednesday if there are no showstopper issues so that would be a nice relaxing thing to do next week when we won't have so much else otherwise to do okay now I'll go ahead and read C Grover's contributions continuing work on the RPN calculator with a few distractions into your retro widget display I.O. internals food and family and a wonderful shift to cool crisp weather okay phone we got you can go ahead alright thanks Dan, last week I worked on the code and I think we are most of the way there the PyPortal version of the busy simulator and I'll be working on the guide this week to document that project on Friday I did stream and we played with some vector I.O. shapes made some Christmas tree and snowman shapes with vector I.O. so that was a lot of fun I am continuing to work through the old PRs like Catney mentioned some of the ones that are coming up this week probably our HT16K33 I just got some feather wings assembled to test out some PRs with that library some other stuff I want to take on this week there's a couple of older PRs or open issues I should say rather in the core that are related to display I.O. stuff just implementing different small features here and there so I want to try to dig into some of those to get some more practice working inside the core and then I am streaming planning to stream again on Friday night so if folks are interested in watching something Friday evening I will be doing that that's what I got thank you okay thank you VomiGuy okay Jeff go ahead yeah so last week it felt like I did a lot of stuff with the CI or get have actions it needed to be groomed or kept like a well kept lawn maybe it's topiary sculpture I don't know it's one of those things but besides that I finished off my lamp project I don't know I guess I showed a previous partially complete version of an unshown telecouple weeks ago but anyway this week I'll be working on a guide for this lamp project so you can see it when that is out later and the latter part of the week I'll be out I don't know exactly when but you know I'll kind of trail off I'll be here today and tomorrow and not on Friday and in between I'll be half way disappeared and so happy new year to everybody if I don't talk to you again before then okay thank you Jeff okay Jerry go ahead yeah so finally after a lot of muddling around and trying things I got my Compute Module 4 IO board configured so that it boots now from the network and it can use an SD card just for the file system I still still haven't figured out how or why I can't get it to boot from the USB ports on the IO board but that'll come maybe not it's it's not clear that it can do it and then I've been playing around with it with the different Broadcom boards the Pi 4 build it does boot from the USB just fine and then it now also can use the SD card for its file system and that's that's working nicely so now my big goal is to remind myself and relearn how to use GDB effectively and actually try and try and be helpful with this project at some point and I spent a lot of time on some non-circuit Python projects but mostly it was a response to monitoring the forums and Discord and seeing seeing somebody has something you know thinking oh gee I think I know how to do that or I've done that digging out the old hardware to do it and most of the times the response was well it works for me which isn't always helpful to the person who it's not working for but at least it can you know hopefully gave them hope that it should work and there's nothing inherently wrong with their connections but in doing so I learned a lot and relearned a lot and so I'm finding that you know by monitoring the forums and Discord is a wonderful place to just pick up lots of ideas and try things and I find it a really great way to learn stuff and then I got some of the QDPI ESP32 S2 boards today and boy they're just really nice it's just so easy to stick a sensor on the stem upward and it works a really nice little package okay thank you Jerry anything else I interrupted you maybe no okay alright Cadney go ahead alright so last week was a short short week for me I got the absolute basic pages done for the QDPI ESP32 S2 guide that is the overview the pinouts page and the downloads resources page and that was made live simply because folks were asking questions but I didn't get to the rest of it so I'm going to go ahead and add some of the circuit python stuff to it and the Arduino stuff to it soon otherwise I will be picking that up next Monday other than that was a bonkers week so I did nothing else for work and then this week nothing I won't be working this week I attended meetings today simply to stay in the loop and then I will be picking everything on my list back up next week so you will hear about my whole list of things to do on Monday the 3rd so have a wonderful new year everyone alright thank you Cadney and have a great time doing nothing which is maybe some of you also aspire to do that sometimes okay and I'll read the last two entries here Mark Gambler writes one more test I want to run on the IS-31 FL-37-41 speed that's the special display that's used in the LED glasses that controller and need to write a summary of how it all works together may be doing this after the new year and Mark says they're getting a booster shot tomorrow okay and then finally Tektrick says after the holidays more typing PRs going for some more challenging libraries then add away for 7 segment displays to marquee and or print a variety of characters beyond setting segments individually that sounds very interesting and getting work on getting tap detection working on the LSM-6DS library alright that's it for status reports we don't have anything in the weeds is there anything that somebody thinks thought of at the last minute that they'd like to add here no but thank you for doing the release you're welcome alright and I think that wraps up this meeting we're going to have another meeting at the same time next next week that will also be right after a holiday weekend so it may also be likely attended but if you're around feel free to show up and we can hear about whatever what what has been happening since last week hopefully you hear about 7.1.0 final if not you'll hear about bug fixes in 7.1.0 so thanks thanks a lot everybody and I will stop recording now