 Hello everyone and welcome to the Circuit Python Weekly Meeting for December 19th, 2022. It's that time of the week and the last time this year that we will get together to talk about all things Circuit Python. So I'm Jeff or Jepler and 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 and great folks like, say, Scott and Katnney and Dan, consider purchasing your hardware from Adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join any time by going to adafruit.it.discord. We hold the meeting in the Circuit Python DevText channel and the Circuit Python Voice channel. The meeting typically happens on Mondays at 2 p.m. Eastern, 11 a.m. Pacific, except when it coincides with a U.S. holiday. In the notes document, there's a link to a calendar you can add to your favorite calendar app. We also send notifications about upcoming meetings via Discord. To receive those notifications, ask a, well, anybody you see to add you to the Circuit Python Discord role, that is, ask any administrator or moderator to do that. There is a note stock to accompany the meeting and recording. If you're watching this after the fact, there should be a link in the video or podcast notes and it will have time stamps to go along with the video so you can skip to whatever part is most interesting to you. This meeting tends to run 50, 45 to 60 minutes, so we think the option to skip around is handy. After the meeting, we will post a link to the next meeting's notes document in the Circuit Python Dev Channel of the Adafruit Discord. Check the pin messages to find the latest note stock and add your notes for the next meeting any time you like. And if you wish to participate but can't attend live, please remember you can leave hug reports and status updates in the document for the host during the meeting. This meeting is held in five parts. Right after this is community news. This is a look at all things Circuit Python and Python on hardware in the community and a preview of the Python on microcontrollers newsletter. The second part is the state of Circuit Python, the libraries and Blinka. It's a statistical overview of the whole project by the numbers separate from what we're up to individually. Up after that is hug reports. Hug reports is an opportunity for everyone to highlight the good things folks are doing and take the time to recognize awesome folks in our community. The fourth part is status updates. That's another round robin where we get a chance to sync up on what we've each been up to. We invite everybody to take a couple of minutes to talk about what you've been doing in the past week or since the last meeting and what you'll be up to in the coming week or until the next meeting. And then the final part, if we need it, is called in the weeds. It's an opportunity for long form discussion that can either result from a status updates topic, but more often it's something that you've identified ahead of time as just being a discussion where you want to engage with the community to answer, to like resolve how are we going to do this or how should I do that? Anyway, and that covers how the meeting will go. And with that, I will start us on community news. So more on this in just a moment, but here are some top items in news for CircuitPython. First up, the issue uploading UF2 files with macOS 13.0 Ventura has been fixed by Apple in version 13.1. Uploading UF2 files with macOS 13.0 has been fixed in version 13.1. Not all is perfect though. It's still the case that UF2 uploading does not work on NRF 52.840 boards that use an older UF2 bootloader. You need version 0.6.2 and newer. On these boards, the bootloader appears to fail quickly, allowing no time to copy the UF2. And there is a link to some instructions to update your bootloader. Otherwise, on these NRF 52.840 boards, including the CircuitPython, the Circuit Playground Bluefruit, the Feather NRF 52.840, and the Itsy-Bitsy NRF 52.840. The only way to load a UF2 file is on a non-Ventura computer. And it is also still true that copying .hex files larger than one meg doesn't work, for example, on the micro bit. And yeah, check out the note stock for more links relative to that. But it is nice to see that the big main problem that affected a lot of people has been solved. Next up are Adafruit's iPhone app. PyLeap gets a major update now with Wi-Fi transfer and more. A major update, the free Adafruit iOS app simplifies downloading code files and assets and transferring them to an Adafruit device using VLE or Wi-Fi. And then next up, the best part of the newsletter is community projects. It's always a great way to see what other people are up to and get your own idea juices flowing. So this week is a runner's headlight, the MetaNerd Headlight Mark II. The Mark I was a success in the sense that it was made from entirely leftover parts of unrelated earlier projects. But I wasn't really satisfied with the design. Particularly the area around the too close range LEDs bothered me and I felt like it could be a little more compact, Inner Mark II. Not only is it physically smaller and uses less power, it also looks much more professionally designed. It has the same control and the same mix of close and long range lights. And it is controlled by an Adafruit Trinket M0 running CircuitPython and there is a link to Instagram which I guess doesn't preview in Discord. So you'll have to check that out using your Instagram app probably. So what is the CircuitPython weekly newsletter you may ask? It is a community run newsletter emailed every Tuesday. The complete archives are at adafruitdaily.com slash category slash CircuitPython. It highlights the latest Python on hardware related news from around the web, including CircuitPython, Python and MicroPython developments. And to subscribe, you'd go to the front page of adafruitdaily.com. But we also want to emphasize the community run aspect of it. So to contribute your own user project, you can edit next week's draft directly on GitHub and submit a pull request with the changes. You can also tag a tweet with hashtag CircuitPython on Twitter or email cpnews at adafruit.com. And also, for those of you that do tag CircuitPython on Mastodon, a lot of us are trying to keep an eye on that. But your surest route is to go pull request or the email. That's what I recommend. And a little bird told me that next week's issue will come out a day late due to the holidays. So just be aware of that. All right. And next up is the state of CircuitPython, the libraries and Blinka. And this is a report of information over the previous seven days. And that particularly means that any changes made today are not included in the report. And as we have our little holiday break, that means we'll miss acknowledging some people who were working during the upcoming week or so. And if we ever miss you, we apologize. We appreciate all of your work. But now to the numbers. Overall, this is across all CircuitPython-related 80 Fruit repositories on GitHub. We had 24 pull requests merged by 18 authors. So thanks to some names that are less familiar to me, Luis Malhadas, Icarozo, HappyMe531, VladAK, Spavlot. And just to everybody, whether it's your first pull request with us or your 100th, we really appreciate the way that the community comes together and makes CircuitPython and the libraries better. Reviewers-wise, we had seven, which is not a bad number. And thanks to our less frequent and outside of 80 Fruit organization reviewer, AskPatrickW. So it was nice to see some reviews come in from the community. And I always like to emphasize that those are official GitHub reviews. And we don't directly name the people who are just participating on issues and pull requests, providing information and good feedback. And we appreciate those people, too. We just don't list you all out. And that brings me to the last overall number, which is that we had 22 closed issues by 12 people and 19 open by 17 people. So it's nice to see us come down a few in open issues and also the number of people participating is very good to see. And with that, I will ask Dan to let us know what is up with the core of CircuitPython this week. OK, thank you, Jeff. So in the core of the past week, there were 11 pull requests emerged. And I've worked a couple more this morning because this is as of last night. And there were seven authors, notably Bablock B is probably new. And three reviewers, there are 21 open pull requests. Nine of those are drafts, which are often awaiting USB numbers or some other things like that. There were 11 issues closed by six people and six opened by six people. It's nice to see that we closed more than we opened. There are 578 open issues. Out of that, there aren't any open issues to add anything to 7.3.x. There are nine open issues for 800, which is a big improvement on the way it's been recently. And there should be six or seven soon. There are 27 open for following on in 8xx. And two open in 900, those are usually changes. Those are changes that are incompatible with 800. So they are deferred until 900. 20 issues are labeled as library issues. Often that's a request for a library. 511 long-term issues, nine support issues. We could probably close a bunch of those. And three third-party issues, which means they're awaiting some action by a third-party that we have no control over. And zero issues not assigned to Milestone, good about triaging. OK, that's it. All right, thank you, Dan. Next, as Katnia is out today, I have asked our own foamy guide to tell us about the libraries. Go ahead. All right, thanks, Jeff. This section covers the CircuitPython Libraries. On GitHub, you'll find those all with the name Adafruit underscore, CircuitPython underscore, and then the name of the library. This is the Python layer of the code that makes CircuitPython project work. This week in the numbers, we had seven pull requests merged by six authors. A few of the names Jeff mentioned before also were unfamiliar to me. So I think those folks may be newer, Vladak and Spavlott. So thank you to those folks. And of course, thank you to all the rest of our authors whose names I do recognize. Appreciate everyone who supports the libraries by submitting pull requests as always. We had four reviewers. So thank you to all of our reviewers. Amongst the pull requests that were merged this week, the oldest ones were about 40 days old, and the newest ones were just one day old. So we jumped on a couple of them real quick, as well as taking out some of the older ones. That does leave us with 43 open pull requests, at least as of yesterday, like was mentioned before. I happen to know a few of those are also tackled because I've been working on pull requests this morning. There are eight closed issues this week, or there were eight closed issues by five people, and there were 13 issues opened by 12 people. There are a total of 596 open issues, of which 95 of those are labeled good first issues. So those are ones that have been identified as not needing a particularly in-depth level of knowledge or experience. Those are great for folks who want to get started becoming involved in the project. If that sounds like something that you'd be interested in, head over to circuitpython.org slash contributing, which is where you'll find a list of all of the open issues and pull requests, as well as opportunities to filter them by that good first issue label. And that's what we've got in library land this week. Thanks, Jeff. All right, thank you. And rounding out this section of statistics is Melissa to tell us about Blinka. Hello, so Blinka is our circuitpython compatibility layer for MicroPython and single board computers like the Raspberry Pi. This week we had six pull requests merged by five authors and two reviewers. There are currently six open pull requests. There were three closed issues by three people and zero new ones opened, leaving a net of 86 open issues. There were 17,550 Pi PI downloads in last week, 7,181 Pi wheels downloads in the last month, and we are currently at 100 boards. So we're getting a little more activity than normal, but it's looking good. Thank you. And with that, we are ready to head on to the first round robin section called Hug Reports. And because I was a little bit busy and disjointed this morning, I will start it off with only a group hug. I know that there are some people that I really should give individual hugs to, but I didn't unfortunately take the time to write it down. And with that, I will pass it on to Dan, who has a bit more substantial thing to say. Okay, thanks. Okay, thank you, Jeff, for some debugging ideas, for some mysterious errors that I will discuss more in status reports. Thanks to Deshipu, Naradak, and Carter for helping on Help with Circuit High Pond. There were, particularly, there was somebody who had kind of a multi-day issue and they worked successfully with that person. That was great. And thanks to our translators, who continue to keep up with messages that need translation as 808 evolves, we do a lot of churning of the messages. So thank you, translators. Okay. All right, next up is Deshipu and then DJ Devon 3. Okay, thank you to you, Jeff, for all the camera support code and your help with that. Thank you to Dan for the reviews on the previous quests. They were very fast and very timely. And thank you to Tim for doing the deep dive. All right, I'm really happy you got that camera working. So, yeah, thanks for sharing that news when it was finally going. Anyway, all right, DJ Devon 3 are up next and then Foamy Guy. Yeah, that camera was really cool to see, Deshipu. First of all, hug is to Noah and Pedro for live streaming, how to add custom supports in Cura during 3D Hangouts. And I'm brand new to 3D printing, had no idea how to do supports and they like did this whole entire segment on it. So it's awesome. Hug to Sea Grover and Foamy Guy for their encouragement and ideas and obviously Foamy Guy for constantly streaming. To BlitzCityDIY for an excellent ongoing vlog series on her quantizer project. So it's really neat to get like status updates as she's learning. So I'm learning as she's learning and that's a great format. A hug to Joey Castilla for an amazing low power time-based Christmas tree user guide. And user guides, user pages don't get a lot of attention but I figured I'd throw that one out because he put a lot of effort. I don't know if any of you've read it, it's long and it's very well documented. And a hug to all the developers, reviewers, beta testers and helpers who do all the really hard work behind the scenes to make Circuit Python an amazing and enjoyable language to use. And a hug to everyone who's working on switching scripts from Twitter to Mastodon recently. And happy holiday hug to everyone. Thank you. Next up is Foamy Guy and then maker Melissa is on deck. All right, thanks Jeff. This week some hug reports for me, a hug report for Katny for some recent chats about setting up live streams as well as life generally. Hug report for DJ Devon for sharing his efforts on the Cowbell project as well as offering to send hardware to myself and some other members of the community. I'm looking forward to playing with us during some time off that I have coming up. A hug report to C Grover and D-Gloud, David for sharing some prior work around color gradients, both some example libraries as well as a pointer to some projects that did some interesting stuff with gradients. Hug report for TrevNose and the PyLeap developers. It's very cool to see the new Wi-Fi support being added to PyLeap. Definitely always excited to see more doors opening up for opportunities in mobile development. So that's really cool to see. And then a group hug to everyone. Happy holidays to everyone. And cheers to another great year with Circuit Python. This was kind of my first year working at least part-time on Mondays on the project and it's been a great year and I'm looking forward to another one. So thanks everybody. Thank you, Tim. Next up is Melissa, then I have some notes to read from other folks. Let's see, I just, oh, here it is. I wanted to get back to PT and Lamore for being so kind with a, one of my friend of mine passed away about a week and a half ago and I hugged Catney for a nice discussion and a group hug to everyone else. Thank you, Melissa. All right, I'll read notes from a few people and then up after that is Scott. So Mark, Gambler21 writes group hug and happy holidays everyone. Timmy makes things, who is missing the meeting, has a hug report to Catney for some recent chats and a group hug with warm holiday wishes to everyone. All right, now we come to Scott. Hello. Thank you, Jeff. First, a hug to my partner, Rebecca, for being an awesome mom and making Ari my son as comfortable as possible on the plane, two planes out here to my in-laws place in Michigan. I hugged to Daredeck, Dan, DJ Devin and the Shippu. Dan left himself out of the help in the help with CircuitPython channel. So thank you to all those folks who really being so helpful to so many people and like Dan caught, Carter is also super helpful. And then finally, a hug report to Chavnose for the new PILEAP release on iOS and also a shout out to BlitzCityDIY Liz for doing a lot of the testing of PILEAP to make sure it's working pretty well before it gets released. So congrats to Chavnose and I'm excited to see PILEAP and Glider really grow into their own in the next year. So thanks to BlitzCityDIY to Liz and Catny for helping move that along as well. Thank you, Scott. Last up, I have notes from Tectric. Tectric has a hug report to Catny for an excellent discussion about personal life and a group hug. And next, we will move on to status updates. Status updates is our time to sync up on what we're doing. I'll start and then go through the list in the document order to give everybody a chance to participate. When I call on you, take a couple of moments to talk about what you've been doing since the last meeting and what you'll be up to until the next meeting. It's also an opportunity to provide quick trip, quick tips and tricks relevant to what people are working on. But if a discussion looks like it's gonna be long, we will move it to in the weeds. And with that, I will get started. I felt like I didn't really have a lot of activity again this past week. The main thing that I did was I made a pull request to revert an update of the Protomatter library, which is what makes RGB matrix work. By doing this reversion, it works again on the ESP32 S3 microcontrollers with PS RAM. But we still need to, and by we, I mean me, still need to investigate what it takes to make the current version work on the ESP32 S3 with PS RAM as well as all the other microcontrollers. The reason has to do with the current version uses the LCD controller peripheral to drive the matrix and that saves more CPU time for your circuit Python code. But it means that there are some things around allocating the peripherals and allocating the memory that are different. And there's just a bug in there that needs to be found and fixed. And it's most likely a bug in circuit Python, not a bug in Protomatter, but at this point I can't rule anything out. The other thing that I did was further fixes to showing the special GAI error exception for name lookup failures. GAI I think stands for get address information. This exception I added a few weeks ago for compatibility with standard Python, but there were cases in which that exception wouldn't be thrown and a more generic OS error would be thrown instead. I think those are all fixed now. In any case, it's better. This week, my goals are to work on 800 bugs as well as adding mouse support to the next keyboard guide. And that will consist of one new page of research because the keyboard, the mouse plugs into the keyboard and then the keyboard processes the mouse information and can send it back to the computer. And so the new research is what does the mouse communicate? How does the keyboard communicate the mouse stuff? And then I'll need to update the program and the program explanation to go through and show people how that works. Noyan Pedro and I were working or hoping that a 3D printed project with the Feather Scorpio would be able to come out before Christmas. It looks like that is almost certainly not gonna happen. So we'll need a fresh idea of a project for that after the new year. So if you have a good idea for eight LED strips and a 3D print, you should share that with us. And finally, I have been looking for an alternative online calendar viewer for the weekly meeting calendar. The existing one disappeared earlier in the year, probably when the Heroku free tier was discontinued. So if you know of a website that you can embed an iCal calendar in and it will show the meeting times in your local time zone, drop me a note. I've found one thing that looked like an alternative but it doesn't show, it just shows the time zone that it says in the file. It doesn't show that translated to your local time. Anyway, with that I'll hand things on to Dan and we'll continue in the notes document order. So keep an eye on that and we'll go through these. Hello. Okay, thanks. All right, so I fixed about four issues or I was counting pull requests in the past week for circuit Python. Some of them were not what they appeared to be which often happens. I looked at a bunch of other issues, some of which I couldn't reproduce or I needed more information. So those are still open. Except I did close some that seemed to be fixed now. I pushed some issues forward to 8xx because they don't really need to be fixed for 800. They're not showstoppers. See, I will do a Beta 6 release probably this week by about Wednesday. It'll have the settings.toml change from .ent to settings.toml and possibly some other features. There's a Scotch submitted pull request which you can get in by then. So anyway, they'll be, I would like to have a before Christmas Beta 6. Now I'm investigating some mysterious crashes and oddities. Originally it was some crashes that had to do with compiling debug builds and it looked like you might be ready to display IO but it wasn't at all. It had to do with setting various compiler optimization flags. It was really complicated to do this because I tried to do a regular bisect and that didn't work and I finally I did kind of a manual bisect. And recently in the past day or two some other exception handling issues have come up which also are mysterious and these all may be related or may be not so we'll try to find out. So I'm continuing to work on that. Okay. All right, thanks Dan. Next up is to Shippu and then DJ Devon 3. So I'm coming back to some of my old projects because I have some free time before Christmas now. I finally, I mentioned that already, I finally got the camera shoot for the Lolin S2 Mini working with the test code. And I have a similar shoot for the Pico. That's very Pico coming up hopefully just before Christmas. So I hope that will make it a bit more easy for people to use cameras. You don't need to have that caluga board anymore. I also plan to use this shoot on my tiny spider robots and I had a problem where I'm using all the PWM channels on the robot already for the servos. And the camera needs one more PWM channel to provide the external clock. But you can actually get modules that already generate the external clock with a crystal on the board. So I added, I made that pin optional basically in the current ESP32 camera library. So now you can use also those words that already have the external clock and then you don't use the extra PWM channel. I got my external type working with the Plover HID which is much nicer than standard serial protocol Plover because you no longer have to select which serial device Plover is going to use. It just detects the HID device automatically when you connect it, which is much nicer. I got the Pew Pew, that's the eight by eight game console I think library is working on the R2-ROS Solder Party Flux game console. Of course, NN Circuit Python support for it was already there. Some month ago, I think, but I haven't talked about that yet, I made the driver for the capture sensor. It's very nice because you can make things, do things depending on how you wave hands in front of it. So it supports nine different gestures you can make. For instance, you can make a robot do different things. I'm still working on the spider robots of mine and I made just a version that has this Raspberry Pi Pico W because among other things that's going to use much more PWM channels for much more servers but also I hope that some other things will be easier with that. And yeah, and I made a little bit of progress with the electronic Ocarina thing that I'm working on. I still don't, didn't make it use MIDI but it has a built-in speaker now so you can just play it without connecting to the computer. And that's all, thank you. All right, I think that's plenty. All right, next up is DJ Devin 3 and up after that is Fome Guy. Hello, I spent my entire weekend learning everything I could about Fusion 360 and Curious Slicer. I just got a new Ender 3S1 Pro and learned that printing PLA is a piece of cake compared to PETG. My goal was to 3D print orange step switches for the TR Cowbell because that specific color is unavailable from Adafruit. The step switch caps require a precision of 0.12 millimeters and it took 22 revisions before I could get it just right. Fusion 360 automatically appends file save version numbers so if you really want to know how many times you fail before succeeding, use Fusion 360. The PB86 step switch 3D model was submitted as a PR this morning and it was added to Adafruit CAD parts and there's a URL for that. And happy holidays! The first batch of version 1.2 TR Cowbell should be arriving today or tomorrow to all the circuit bytes and ECSs who wanted one. Some kits are missing a few extras such as an SSD 1306 display or an encoder knob or a dip socket because I started running out of supplies and was trying to cobble things together but all the core components to get all the boards working are included. Those who wanted a kit versus a fully assembled board was about 50% which kind of surprised me. I thought everyone would want a fully assembled board which would require tons and tons of soldering so I kind of felt lucky that people were like hey I'll take a kit and I was like yes no I don't have to do all that soldering awesome just ship it. One lucky person will receive a magnetic micro B plug stuck in the end of the Pico because I forgot to take it out before packaging. I'm currently designing TR Cowbell 1.3 with RGB LEDs and other some new other features that I'm going to try and keep secret the best I can because it's really cool and I'm really excited about it and I'm looking forward to feedback from the version 1.2 owners to make the next iteration even better and I hope everyone has a nice holiday season and I will see everyone again in 2023. Alright thank you. Next up is from a guy on on deck Melissa. Alright past week or so I've been working on some PR reviews and testing a couple of the ones that I found particularly interesting this week were in the Ethernet library there was a fix that allowed it to work with my router which it turns out my router I think does something kind of weird and so I was having to do it in this weird specific way before to get it to work but the new version seems to work reliably in my setup so that was cool to test that out and discover the other one which I thought was neat that I looked into this week or one of the other ones that I thought was neat I should say was in the logging library there was a new feature added to allow you to set up multiple handlers so if you wanted to log to multiple places at once you can now do that so if you want to write to a file but also print or send it to the internet and also print and put it in a file with multiple handlers to make that happen this past week I also cookie cut and published the first version of a library with some helper functions for generating gradient color palettes I have a link there to github in the notes document I'll get it added to the community bundle soon there's no PR there yet but I do have that on my radar for this week so far I've been able to use the palettes that it generates with display IO bitmaps as well as vector IO shapes and then moving out of the display realm a bit I've also managed to use them on neopixel strips both setting it on the strip directly so that your full strip can just gradient from one color to another to another but I've also been working on some updated variations of some of the animations to use those color palettes inside of the color inside animations as well throughout the upcoming weeks a couple of the things that I have that I'm planning to look into I picked up this barcode scanner that has USB and UART a little couple weeks back I think it was I have unboxed it but not powered it up yet so I'm looking to jump into that get it hooked up hopefully to a circle python device and ideally what I want to do with it is create some sort of little hand held toy with barcodes I recently discovered a product called scanners I think it's radica maybe or something like that little electronics toy that was released in the early 2000s that was like a virtual pet where you scanned barcodes and it let you find stuff for your pet or something like that I missed it when that came out but after discovering it more recently on a youtube rabbit hole I thought it was fascinating and I've always been intrigued by barcodes I am interested in trying my hand at creating a similar sort of thing powered by circle python I will be building and playing with DG Devon's cowbell that was just mentioned a few minutes ago so I'm looking forward to getting that and putting it together and playing with it and then probably lots more stuff going on including ample video games but I'm not sure of any other specifics just yet but I will be around and streaming some while I am off of work for the next couple of weeks starting next week so I'll be around if anybody has anything interesting that they think I'd be interested in feel free to hit me up but other than that that's all I have going on thanks alright and once again I say that sounds like plenty we are getting close to the end of status updates so one last reminder that if you have a topic for in the weeds please go ahead and add that I'm ready to hear from maker Melissa and after that I'll read Tammy and then we'll go to Scott hi I was here last week so over the last couple weeks I had taken some time off because a close friend had passed away rather suddenly and I refactored during that time like last few days plus before that I had refactored USB workflow on code to make use of the file system access API for a more consistent experience and I've been working on polishing up with handling things like partial connections and the ability to run code via the REPL and this week I'm going to finish up the USB workflow and start working on integrating web serial SP tool into the main circuit python work site for the USB boards and that's where I'm at all right thank you Tammy's notes say spent last week buried in day job work not much time for circuit python hoping to get back to my NRPN extension to the Adafruit MIDI library and the project I'm intending to use it for this week trying to reset my schedule for 2023 to make more space for the things that matter to me outside of my day job and next up is Scott and then I'll round it out with notes from Tectric hey thanks Jeff last week was a split week due to traveling on Wednesday but Ari did well on the plane so that was good since I only had 4 days of work left before the holidays I went heads down on debugging the ULP deep sleep issues on the S3 I found an IDF issue that was causing me trouble it's a super common bug that we usually have which is you reset a pin and it resets everything even though it shouldn't reset everything so I found a place in the IDF that that happened and I just made a PR to the ESPIDF upstream as well it's already in our copy the fixes and so I made a pull request just in the last hour for the rework of the coprocessor API that MicroDev had done and so that's now out for review and I'm hoping to hear back from Jeff and MicroDev and maybe Dan if need be so that we can get that in by tomorrow which is my last day before the holidays the other thing I want to do before I go is write the kickoff post for CircuitPython 2023 which is our for folks who are new it's our annual kind of like hey let us know what you think like longer broader goal longer term broader goals of CircuitPython should be kind of what do you want to see this year and so I'll write that up and schedule it to go out publicly on New Year's Day and maybe I'll have a quick in the weeds topic about timing for that although I know Katniss input would be good even though she's not here but we can talk about that briefly I'll add that in a sec so yeah I'm working today and tomorrow on the goal of merging the co-processor API stuff in and then back the January 3rd which is the next meeting since folks are talking about what they're kind of doing in the off time when I'm visiting family this whole time so I'll be doing that but I have the site law-law.org that I did last year that is meant to kind of rearrange how all of the information about state legislative bills and stuff is organized it's kind of my interest in how laws get created and codified and stuff so there's a new state legislative session starting on the 9th and so I'm kind of dusting off the wallah python scripts that do all the fetching and organization of that the main thing that I'm excited about for this session is I made a request wrapper that caches past responses one of the challenges that I had was like I want to store the original copies of the URLs that I'm fetching even if the data coming back to me has been updated so I made a request wrapper that would basically allow me to every time I run it and tell it to fetch a new thing it will be able to I'll be able to like look back in an archive style like everything that the API had passed back to me when I run it which will be good in case I need to like reproduce things or fix bugs retroactively and stuff so that's that's these next two days and then my off time for me alright thank you Scott and I will round out this section by reading the notes from Tectric whose text only today last week implemented the draft PR for status display and community bundle updates in the weekly meeting report took my embedded systems to grad course exam thanks everyone in the community for teaching me a lot about the material and also giving me the confidence to enroll despite not taking the prerequisite very excited for principles and applications of sensors for engineering next semester sounds fun and relevant to making cool robot friends helped keep adabot running smoothly over the holidays fixing a bug with sensors that was implemented recently and built roughly 15 circuit pythonicas and now sending them to friends and family this week reviewing a security warning for adabot probably the best not to share specifics but I don't think it's an issue for us based on the described risk so I don't think changes are necessary happened to discuss privately with any of the maintainers who want a more detailed explanation see the security tab in the adabot repository for more information and finally Tectric is decided to Nevada for the holidays so they're logging off this week or until the next weekly meeting but we'll have the dev laptop with them please don't hesitate to ping me if any CI stops working but things are stable for now and with that we are going to roll over to in the weeds and let me just get back to my blurb about what in the weeds is in the weeds is an opportunity for more long form discussion that either come out of status updates or that folks have identified ahead of time if you have any in the weeds topics please make sure they get added while we're discussing other things so we're not waiting around to see if anyone has topics and with that I will turn it over to Scott who has the one and only topic for today. Thank you so one is just starting to think about my post for a circuit python 23 2023 I was just one in the original post I want to give a deadline last year in the years before we've kind of like kicked it off but not had an explicit deadline which means that it's a little bit of pulling teeth to get people to write it honestly so I think that maybe in this kickoff post that I'm going to about the draft I think it'd be good to include a like get your stuff in by this date so the summary last year went up February 1st but do any folks have opinions about how long should it be two weeks, three weeks four weeks, how long should it be open that sort of stuff any thoughts my gut says that two weeks is probably plenty I I don't know if there are a lot of people who really like aren't around their computers or taking time to think about it during the first two weeks one week I can see oh I've got that week off but I would think we would get the majority of the submissions we'd get within two weeks and then you know not that lag of a whole month until we summarize and bring it together and you or somebody tries to synthesize what are the big themes so two weeks sounds good to me I gave up on that I did that one time I'm not putting that on you then you don't have to do that the summaries now are just like a post that links to everybody's individual posts so I'm hearing two weeks all right yeah by acclaim it is two weeks I think maybe what I'll do is I'll do because we have a meeting on the third and then we have a meeting six days after that so maybe I'll do two weeks from the third which is like a we'll have a meeting the day before it closes just as a final like tomorrow's the last day sort of thing it'll be two weeks ish all right make it the 17th two weeks from our first meeting of the year one day after a final meeting it's a good idea make it so and then the next week we can do the summary post so okay cool thank you for the input on that draft it right now and with that we are ready to wrap up the meeting this has been the circuit python weekly in 1922 thanks to everybody who participated if you want to support Adafruit and circuit python as well as those of us that work on circuit python please consider purchasing from the Adafruit shop at adafruit.com the video of this meeting is released on youtube at youtube.com slash adafruit and the podcast goes up on major podcast services it will also be featured in the python for microcontrollers newsletter visit adafruitdaily.com subscribe the next meeting will be held hold it wait for it Tuesday January the 3rd 2023 there is no meeting the week of December 26 and then the next meeting is held one day later for the new year's holiday but we do hope to see you next year in 2023 the meeting is held on the Adafruit discord server which you can join by going to adafruit.it there are folks in most every time zone in the world who are ready to talk about circuit python about electronics about Arduino if you're into that so yeah just drop by it'll be buzzing over the holidays even though a lot of us who are normally working aren't there's a great community they're ready to welcome you and talk to you and meet each other anyway but back to the meeting to be notified about this meeting and any changes to the time or day you can ask to be added to the circuit pythonista's role on discord that will get you a couple of role mentions every week about when the meeting will be links to the notes document so you can add your notes as well as permission to speak in the voice channel during the meeting so that's all good and you don't have to have a long term commitment to us to do that if it's of interest to you and with that I am about to close out this meeting thank you and we hope to see you all next year on January 3rd have a great holiday