 Okay. Hello everyone, this is the Circuit Python weekly meeting for January 31st, 2022. It's a Monday. This is the time of the week when we get together to talk about all things regarding Circuit Python. I'm Dan 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, consider purchasing hardware from adafruit.com. This meeting is hosted on the Adafruit Discord server. You can join any time by going to adafruit.it slash discord and there's an invite there to join the server. We hold the meeting in the Circuit Python dev text channel and the Circuit Python voice channel. We usually hold this meeting on Mondays at 2 p.m. Eastern time at 11 a.m. Pacific time in the United States, except when it coincides with a U.S. holiday on Mondays. In the notes doc, there's a link to the calendar that you can add to your own personal calendar and we give notes about the upcoming meetings in Discord. If you want to know about the meetings and be notified, get ping, you can be added to the Circuit Python Easter Discord role. So I ask for that. All right. I'll skip some of the other stuff that I said beforehand and we'll start with community news. And I called some stuff from the Circuit Python and Micro Discord or weekly newsletter that Ann works on most weeks and sign up for that newsletter if you haven't already. It's a great source of information. It has a lot of pictures. It has a lot of text. And if you join, you don't get added to any other mailing list. It's not used for marketing purposes whatsoever by Adafruit. You can sign up by going to adafruitdaily.com. Okay. So the top headline news that I found from newsletter. The first thing is that there's going to be a hack chat with Adafruit and Hackaday.io on Wednesday, this Wednesday, February 2nd at noon Pacific time. That's 3 p.m. Eastern time. And the more lady, that's Lady Aida from Adafruit, Jeff Epler, who's in the chat here and Phil from Adafruit will be hosting the hack chat. And you can go to find out more about this chat, find out what the work that we've been doing on floppy disks. Oh, I just made a redundant post here. I'll delete I thought it was going to be a picture of a floppy disk. So find out what all the kind of work that we're doing, reading all kinds of weird floppy disks and trying to write them to, including weird copy protected Commodore 64 disks and all kinds of stuff like that. Next headline is that Apple is finally removing Python 2 in macOS 12.3. If you've ever tried to use Python on macOS, you know that there are a lot of versions and it's very hard to get your versions right. There's a famous XKCD cartoon about the Maras that you can get into different Python versions on macOS. So this is going to be a nice thing to get rid of Python 2. Python 2 hasn't been supported by the Python community for some time now, since 2020, so for two years. And it doesn't get any bug fixes. And then another headline we've got here is that a company called Goliath, G-O-L-I-O-T-H has introduced an IoT cloud system for CircuitPython. Click on the link that's in the notes, if you want to know more. That's in the text channel. What if you could open a text document on a device, write code, click save and everything magically starts working. This is the promise of high-level programming languages like CircuitPython. Goliath Labs now has an SDK to utilize the languages fast prototyping capabilities. In addition to Goliath's cloud functions, it's super easy to pass data from a network device up to the Goliath cloud. Click save to stream IoT device data to the cloud. So this is perhaps like similar to Adafruit.io. It's another service. It may suit your needs more or not. Take a look at it. Okay, now we have another announcement of another upcoming live event. The pie cast celebrates 10 years of Raspberry Pi. New episodes with Lady Aida, Ebon Upton and others. Adafruit's late and the more freed will be on a live cast on February 15th, 2022. And there's a link for more information in the chat. And that February 15th is a Tuesday. Okay, so I won't conflict with this meeting whatsoever. Now a few more details about the CircuitPython weekly newsletter or sometimes it's called Python or Microcontrollers. There are archives available at AdafruitDaily.com. It highlights the latest Python and hardware related news from around the web including CircuitPython, Python and MicroPython developments. To contribute your own news and project, you can edit next week's draft in the GitHub repo we have. You can submit a poll request with your changes. You could also on Twitter tag a tweet with hashtag CircuitPython or you can email cpnews at Adafruit.com. Any of those are equally great ways to tell us about developments that you'd like to see in the newsletter. Okey-dokey. So now let me go on, take a time stamp here. The next section is called State of CircuitPython Libraries in Blinka. This, as a statistical overview of the entire project by the numbers, it gives us a chance to look at the health of the project separate from what we're up to. So it's kind of more quantitative than qualitative. We'll talk about the project overall then separately discuss the core libraries in Blinka. So we're mainly talking about statistics in GitHub, poll requests and issues and that kind of thing. So overall in the past week there were 59 poll requests merged, 28 authors, some new authors that I didn't recognize. They may have contributed before I'm not sure. The Woodsey, Jingleheimer SE, Rim Rolf Redux and Tammy Makes Things Are New that I saw and there may be other new people as well. Thank you very much. There were 28 authors, there were 12 reviewers of poll requests and there were 32 issues closed by 14 people and 30 opened by 20 people. So we're still keeping a kind of a stasis in terms of open and closed issues, in terms of the total number of open issues. So the next section is we'll dive down into the core, the CircuitPython core, which is the firmware that you load that's in a UF2 file or a bin file. In the core in the past week 18 poll requests were merged by 14 authors, there were five reviewers and right now we have nine open poll requests. These statistics are from I think midnight or so, so these numbers might be off a little bit. There were 10 closed issues by four people and 18 issues opened by 12 people. So we've got more new issues to look at. We've got six active milestones. We have some issues, 10 issues that we want to fix for the 7.2.0 release, 23 issues that we want to fix in the 7.0 series and we've got eight issues for 8.0, which need to be deferred for 8.0 because they're incompatible with 7.0 and we've got a lot of long-term issues open, 426 and we had three issues not assigned a milestone, but I assigned them a milestone this morning. So there should be zero of those right now. Next we'll look at statistics about the libraries and Katni, you can go on for that. All right, how's my audio? Sounds good. Excellent. So this section applies to all of the Adafruit CircuitPython libraries, which is everything that starts with Adafruit Underscore CircuitPython Underscore as well as a couple bonus libraries or repositories rather. So across all of those repos, we had 40 pull requests merged over the last week by 15 authors and 10 reviewers. And there's a couple of things I want to point out. One, the oldest one was 239 days old. We're still getting through older PRs, which is excellent to see. And the other exciting thing is that we have 18 open pull requests across approximately 300 repositories. So that's really amazing to see that number has gotten down so far, especially because there's always new PRs being put in. So these are not necessarily all older PRs that we're still trying to get through. So we're getting close. I'm very excited. We had 22 issues closed by 11 people and 11 opened by eight people leaving us with 634 open issues. 236 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. If you are interested in reviewing, check out the open PRs. Leave us a note. Let us know you took a look at it. Test it if you have the hardware. And once you're comfortable with that, we can talk about moving you into the actual review team. If you're interested in contributing code or documentation, check out the open issues. If you're new to everything, good first issue is a great place to start. We also have a guide on contributing to CircuitPython using Git and GitHub. And we're always available on Discord to help you. We want to assist you in contributing in whatever way works best for you. That's important to us. So never hesitate to ask questions. There are a number of updated libraries over the last week, but no new libraries. So I will not read off all of the updates. And like I said, the most exciting thing going on with libraries right now is getting through the older PRs and getting caught up. I am very happy that we are moving forward with that. And that's what we've got. Okay, thank you, Katnie. Okay, next is the Blinka section. Melissa, are you available to say what Blinka is and describe what's going on? Yeah. Blinka is our CircuitPython compatibility layer for MicroPython Raspberry Pi and other single board computers. And this week, we had one pull request merged by one author and one reviewer. There are currently five open pull requests. And there were zero closed issues by zero people and one opened by one person, leaving a net of 69 open issues. There were 17,266 pi wheels downloads in the last month, we're currently supporting 87 boards. And that's it. Okay, thank you very much. Okay. Our next section is hard reports. How reports is a chance to highlight folks in the CircuitPython community and beyond for doing awesome things? As I mentioned beforehand, we're going to do this section in order from top to bottom. I start and then we go in alphabetical order. So we appreciate, this is a section where we appreciate what people are doing and give them thanks. So I'll start. Take a time code here. First, I'd like to thank all our translators who've been making CircuitPython available and understandable for non inquis speakers. We had a Russian translation added recently and I really appreciate all the work that translators do. There are some translators who are extremely good at keeping up with going with new changes and others who do it in batches. Either of those is fine. It makes using CircuitPython much nicer for anybody who doesn't speak English natively. So thank you. I just, something, somebody just, something went away there. Thank you. Okay. We're tied to undo. Let's move on to Charles. Go ahead, Charles, unless you're just lurking. I just want to give a group hug to everybody. I'm working on an interesting musical project and I'm really interested, very much appreciative of MicroPython. It's been a help. All right. You're very welcome. Okay. Okay. David Glaut is working. I'll read your contribution. Thanks to maker Melissa for Stream Deck controlled RGB message panel using Adafruit IO Learn Guide. And thanks to Bren and Lamour for some other MQTT Learn Guide. All right. Thank you, David. Next is Foamy Guy. All right. Thanks, Dan. This week, hug reports for 560 on GitHub is the username there. They submitted some typing and some other improvements to the MacroPad library this week. So I appreciated them. Two Tammy makes things for submitting their first CircuitPython PR. And also, I noticed they are planning to start streaming on Twitch, which I'm also really happy to hear about more folks getting into the streaming. I always like to throw on a stream while I work. So I'll be happy to have more making and CircuitPython related content over there. And then lastly, to you, Dan, for working on the secondary USB drive stuff. If I understand correctly, maybe that may give us the ability to edit like files on an SD card, for instance, that are attached. And I definitely think that would be a super cool improvement. So thank you for working on that. That is right. Editing and at the very least looking at. And I realized that I missed reading some of my own items. So I'll finish them off because they disappeared while I was reading them. Thanks to Tammy make things for her first core PR. Thanks to Emerge Reanimator for working on generalizing the STM port and bringing it to new STM chips. And in the process, Emerge Reanimator has found several bugs in the STM port has been fixing them, which is great. And thanks to Scott Tannute for speedy progress, getting nimble, using nimble to implement BLE on the expressive chips, the S3 right now. So thank you, Scott. Okay, okay, we'll move on to Jeff now. Hi there, I'll start off with a group hug. I know there are some hugs that people deserve, but I forgot about them and liked out while I was writing my notes a little bit late. I hugged everybody pitching in on the recent regressions and their fixes like the bus built in bus stuff. And so forth. And thanks particularly to Dan who is integrating all of that into our seven one branch. And a big hug to Tammy makes things for your first PR. Hope that there are many more. That's what I got. Okay, thanks, Jeff. Okay, now Jerry. Hi, thanks. Yeah, so I'll do you Dan for that quick quick fix to the 751 issue that turned up yesterday. And and thanks to Franklin for joining the moderator team. Okay, yes, thank you. Thank you, Franklin. Okay. Next is Kathy. Yep, it is me. So first up, I'll report to Franklin for joining the discord moderation team. He is a different folks does forum support and was interested in joining us on discord. So he's he's somewhat new both to discord and to obviously to discord moderation. But he is really excited to learn about everything. And we are excited to help. I'm a report to Tammy makes things for rejoining the community after what sounds like an incredibly rough year and for their first PR to P Cutler for the upcoming circuit Python show podcast to foamy guy for continuing to get through older library PRs. I know I said it earlier, but I'll say it again. To tech trick for always being up for library work. It's been really great because we run into, you know, random documentation things that need to be fixed up. And sometimes the eight of our patches don't grab everything and tech tricks been quick to jump in and help with cleanup and so on. And that's been greatly appreciated by both Eva and myself to Carter for sending me a couple of pi zero W's because I can't for the life of me find mine. And I really wanted to use zero W for a project I'm working on, and a group hug to the community for many reasons. But specifically, I want to call out the effort that the current community members put into keeping the community welcoming and safe for both new and current folks. We as moderators do this. That is that is our purpose as admins and moderators. But we find pretty often that a lot of things that perhaps might be a moderation issue are handled by other community members. And everything is very smooth. And so I really appreciate the effort that folks put into helping us moderate our community. And that's what I've got. All right. Thank you, Kat. Okay. K match. Could you go ahead? Sure. Okay. Thanks, Dan. I'm getting back into building circuit Python. And I want to give thanks to Scott, Dan and Naradok for helping me get over some hopes to build a build again. And on a related note, thanks to Jerry for identifying error, I guess, noting that a similar issue from what I saw on my portal build and Dan, thanks for fixing it. Thanks a lot. Okay, you're welcome. All right. Thanks, Melissa, you can go ahead. I just wanted to give a group hug to everyone. Okay, thank you. Okay, now I'll read Mark gambler's contributions. Thanks to Tanute for catching a few more mistakes in my latest PR. And thanks to Tammy makes makes things for their first PR. And now, Tammy makes things, would you like, I don't know if you have audio would go ahead, if you do. I think I have audio. Assuming you all can hear me. Yes, we can. Good. Excellent. So thank you, everyone. I want to give a thanks to everybody, but especially to you, Dan and to Michael for helping me get my first PR through that release process and through some weirdness in the CI that was caused by an update that was released to black yesterday, which caused a whole bunch of things to not work in weird and mysterious ways. So thank you, everybody. And also a group hug because the community here is amazing. I'm super happy to be participating again. And to kind of echo something that Katniss said about this being a safe community, I've had so many places in my life where my interest in electronics and making and computers and all sorts of other stuff has been dreadfully stomped upon by ridiculous gendered nonsense in our society. And the Circuit Python community is amazing. And I really appreciate you all. Okay, thanks. Thank you very much, Tammy. And we appreciate your contributions to really glad to have you back and active. Okay, Scott, go ahead. Hello. First, a hug to Michael for the type PR. Also goes by purples, I think. Next, a hug to the mind virus for the links to the audio workload API in an issue. I'm always looking for interesting audio API. So it's certainly not a short term thing, but happy to have those links stored in an issue so that we can look back on them later. A hug report to Lady Ada who has been doing a lot of reviews and I wanted to just thank her for those. And then finally, a welcome and a thank you to Tammy make things for her new pixel PR as well. Okay, thanks, Scott. And finally, Tectric, but Tectric is not here. So I'll read their contribution. Thanks to Katnie for providing me with me with opportunities to help out with some of the library infrastructure and a group hug. Alright, so let me now clean up a bit here. And the next section is status updates. This is our time to sync up on what we're doing. Again, we'll start I'll start and then we'll go in alphabetical order in the note stock. It's both an opportunity to describe what you've been doing since the last meeting and what you plan to be doing up until the next meeting. And it's also an opportunity to provide tips and tricks relevant to people are working on. And if you say something that you want to talk about, that's more of a discussion. We can you can mention it in status updates and we can discuss it in more detail in the in the weeds section. So now I'll start. So as I mentioned for the past several weeks, I've been testing multiple logical units for USB mass storage. Unfortunately, it doesn't seem to work very well on Linux on Mac OS and Windows. It works great on Linux and tech, who's our tiny USB person. He's the originator of tiny USB. He is currently celebrating Lunar New Year, Tet, and he'll be so he was going to do some testing that he's off for a while. So this work will be on hold for a while until he finishes his his vacation. Okay, the other thing I've been doing is working on fixing some I to see bugs, particularly with respect to ESP 32 and researching some other eyes. I to see bugs. I have a PR in progress that should fix a lot of the current problems on the ESP chips right now. And as I mentioned, I fixed that a bug, a build bug having to do with a previous PR for Sandy. And I'm doing support and I'm doing the more doing more support recently. I'm not really sure whether it's deliberate or just because there's more support to do and I've been triaging a lot of triaging a lot of bugs that things that might be bugs but are may or may not be. And so I have to investigate to find out. So that's been taking some time. Okay, so Charles, you can go next. Okay, I'm, I've been basically working up what I've been doing and I'm still going to do continue on with is by since my keyboards for another devices for my synthesizer music making rig. The only thing I can't I just I just got a bunch of keyboard boards that I'm going to use for various things. And I'm still looking for sliders. Have they, does anybody know if they've been in in available? Oh, I keep looking and every time I look at they seem to be out of stock. I'm not having one. If anything is out of stock, you should add yourself to the please notify subscription. Yeah, I always I constantly do that. Okay, as I would. Every time I've gotten the notice that they're in stock, they immediately sell out. Yeah. Right. I'm sorry, you have to right now. I have to keep after it. Right. You have to be really on the ball. And I'm sorry. Yeah. Okay, I, I do just want to point out to Dan that it's I'm glad Charles that you do that, but it also functions as a way for Adafruit to prioritize what they make. So it is always good to get on that list, because they will make more. It absolutely makes sense. Thank you. I would also like to remind you that you can always check our other distributors, especially Digikey and Mauser, they sometimes have stock when we don't. So and it's fine to buy from them. That's, we get money to that way. It's so check it out. There are there are a number of things that I've told people to buy from Digikey recently when we haven't had stock. So that's like, no, but I do like to buy direct from Adafruit to the port. You guys and every and more and everybody else that makes all the neat like tronics that allows me to do what I want to do. Sure. But we do we do get money through the distributor. So don't don't worry if we don't have it. And you can always you can always buy something else from us later. Okay, I'll move on to David Cloud who's lurking. David says playing with MQTT from Feather S2 to mosquito on a pie. I tried all the simple tests and figured out how to go to my server rather than Adafruit.io. Hopping for networking to integrate with the asynchronous hoping, I guess hoping for networking to integrate with the asynchronous aspect and follow the great learn guide. Tested Neopixel on pi zero one W and it failed on me. I wrote an issue future plan do something like the learn guide stream deck controlled RGB message panel using Adafruit.io but with a piportle rather than the stream deck and my own MQTT server rather than Adafruit.io. So making your own mini cloud sounds sounds very interesting. Okay. All right, foamy guy. Are you available? Yeah, thanks, Dan. So a couple things from this week. I recorded a video for the Nico cat animation project and put the finishing touches on that guide and just put that into moderation this morning. So that should be coming out soon, I think I updated the documentation section inside the read me files in cookie cutter. The thing that generates new libraries whenever we make new libraries, you include a new link to the read the docs pages. I started working on a converter script for Winamp skins. So the way I have it set up now you download your preferred Winamp skin preview and then you run the script on it and it will resize it and chop a few parts out so that it's ready to load on to a piportle and then start playing some music from there. I have continued on PR reviews. One of the more interesting ones, one of the ones I should say I found more interesting this week was really learning more about button matrix circuits. I kind of had a rough idea of how that worked and I've used them in a couple of projects but never stopped and really considered the way that the circuit is built and I had to do that this week to make sure I had a circuit set up to test the PR with HT 16 K 33 breakout. And then another thing that I will be working on this week is a new project that's pulling data from a government traffic data source. The government has a website where you can pull JSON data from traffic through all their different various sites. So we working on that this week. And that's what I have. Thank you. Alright, that's very interesting. Alright, thank you. Alright, Jeff, can you go ahead? Hi. So I've been remaining in floppy land. So last week I wrote code for the RP 2040s PIO peripheral for very highly accurate timing when reading and writing the flux data from floppies. While this code is going to go into Arduino first, being able to prototype the PIO code in Python was invaluable. This week I have floppy stuff and that will remain outside of circuit Python for the moment. I'll be on the floppy hack chat this week. And we will eventually bring the floppy stuff into circuit Python. But mostly after we finish the implementation over in Arduino. And part of what I'm doing over there is taking into account the differences between the coding environments. We did this previously with proto matter, which powers RGB matrix. There's the Arduino library and then we selectively reuse the code in circuit Python. And so we share the implementation and it reduces the overall development time. But there's a lot of dare I say moving parts in floppy. So it's just taking a little while to get it all done. So that's where I'm at. Okay, thank you, Jeff. Jerry, are you ready and available? If I can just hit the unmute button once and get the cat out of here. Okay. Where'd it go? Yeah, so last week I spent a bunch of time playing with the micro bit v2 build. Just for fun. And one of the things that was playing with both the micro bit and the ESP 32 C2 build was. One of the problems was it was so hard to load stuff onto them, because there's no there's no circuit by drive. But it turns out that ampy does work. Had to play around a little bit. The v2 build that micro bit didn't have been ASCII. And one of the functions is used a lot in happy required it. So I put in a PR got that built into it and that worked fine. But then happy itself turns out. It's it's really based for micro Python and it uses you been ASCII. So I found a way to quickly patch that so that it will import been ASCII if you've been ASCII isn't there. So I put a PR and an issue into the happy site, but it's really not clear looking at happy whether it's being maintained anymore. So keep an eye on it. They're working on some new version, which I'm not quite sure where the status of it is either. Supposedly our shell is usable, although I tried it and I it didn't work for me when I tried it one time. And also it'll have the same DASCII problem. So I'll look at fixing that, but I'll have to get back to our shell to see if that works better. But it's nice that just have a tool like ampy to be able to upload a file quickly. Especially before the BLD for workflow is actually up and running, which is was the case on the C3, but I think that's changing very rapidly. So maybe this is all unnecessary because I did find to that the using on the C3. I'm sorry on the on the like a bit V2, the code.rc.circupython.org. BLE flow worked really well. So that was kind of fun to play with. And then this other project going that came out of a actually out of a a discord post or forum post a camera, which but somebody asked for help with it. And then I found it was really neat project that was to take an RFM9x and an MLX90640 thermal camera. And so have a remote transmitter that then transmits the radio to a receiver, which then displays the data. And so I finally got a that working in a way. I really like it. And you can so the transmitter is an RP2040 with the RFM9x feather wing and the MLX camera. And the receiver is another RP2040 with another radio, but with a 2.4 inch TFT display. So that's been kind of fun. And also been trying to work on using a Raspberry Pi as the receiving side, but I need to learn a lot more about pillow. So far, I can get a black and white image, but I get to get to learn alarm a lot more about how to do displays on the pie. So that's been my fun. Okay, thank you, Jerry. Okay, Catney is up next. As I'm adding to my notes. All right. So last week, I finished up the adding Artuino template to all the RP2040 board guides. We held off on that because we do things we wanted to make sure that Arduino was solid for the RP2040 and we wanted to figure out which direction things were going to go in terms of what core folks would use. And I think it's been a very good thing that people drifted to the Earl Philhauer core, because they are incredibly responsive for PRs and updates. And it's very solid, it works really well. So we updated all the guides to reflect that. I started the guide for the arcade button, semi QT breakout, which is a breakout where you can use the arcade button quick connect cables to connect for arcade buttons to it. And then you have basically a semi QT arcade button setup. It came out a bit ago, but the guide never got started. The bunch of other stuff took priority, but people have been asking about code. So we're bumping that up and getting it done. And some miscellaneous. Today so far, updated the newsletter like I do usually on Fridays, but totally forgot to do that because I got hooked into doing the arcade stomach guide. I updated the I had a simple test going where you just press the button, the light turns on, but Lamar wanted it to pulse the LED PWM when you press the button instead. So I wrote that code this morning, scrambled to continue slash finish up my circuit Python 2022 posts and ordered the hardware that I forgot to bring with me to do the async IO template. This week's plan finished the 2022 posts finished the arcade stomach QT guide. There's a feature in the learn system called groups that you can basically create a group and it links a bunch of different guides together. And I was totally unaware of this feature. And the developers are looking at making it more accessible to users and more obvious. And they also want feedback on both the background end of it, which would be creating the groups and about the foreground end of it, which is the user experience. So I'm going to dive into making a few groups and providing any feedback I have on that. I think a circuit circuit Python getting started group would be great. We often link, you know, three or four guides to folks who say, Hey, I'm new to circuit Python, where should I get started? And like, here's these four guides. Well, now we can just link the group. Once I got that going. So that'll be good. It was brought up a like last week or the week before that circuit Python.org slash trademarks is a placeholder. And multiple people within the last couple weeks have been asking about use cases for the circuit Python logo and circuit Python itself and blinker. So I'm going to get that updated with some content so that that's clear. And that'll be a living document as well where as we, you know, find new use cases or whatever, we will update that. So that'll be good. There's a few things left to do on the feather TFT guide. I have a couple of breakouts that have a STEM and QT revision done that the guide needs to be updated. And a probably out of order I will do after the circuit Python.org thing. The dot starts status LED template page so that and can get that into guides because he's waiting on that. And the asyncio template as well, which I need the hardware for, but I don't think I'm going to get to it before Thursday anyway, which I will have it by then. So that will be fine. And that is what I've got. All right, thank you, Cathy. Got a lot going on and you can see the output of all of this in guides and examples in the future. So thank you very much. Okay, K match. Can you go ahead? Good, thanks, Dan. So last week, I've been looking at how to view the REPL while you're also looking at other graphic outputs. And I came to realize that the REPL that shows on the screen with the Blinka logo is just another display IO object. So if you can find a way of accessing that, you can show both the REPL and make it interactive or show the I guess what would be the console of any print statements while you're also looking at your display IO window. So I'll show a little video of that and may consider a PR and see if people really want access to that as an option. This coming week, hope to spend some time trying to understand more about touch events and how to make them look like gestures rather than just touch down and touch up. Currently, the graphical user interface elements that have been developed in display IO layout are mostly or I guess solely relying on touchdown and touch up. But the question is, could we build other more complex reactions if we translate just touches to something more complex. So in particular, I'm looking for demos of that. So if anybody has any ways of pointing me to how to do that conversion, I'd be open to that. Okay, thanks a lot. Okay, thank you, Kmatch. Okay, maker Melissa, you're up next. So last week, I worked on porting a little fs to JavaScript some more. I'm continuing along that. And I had, well, I tried to take a little bit of a shortcut in terms of I attempted to use an existing project called little fs. Yes. But it hasn't been updated in four years in the format was unusable. So it was dead end. So I'm continuing back down the same route. I also updated my stream deck matrix learn guide with an updated 3d printable model for the new matrix. And so I'm going to continue doing or continue to debug work I've done on the little fs stuff in getting the details of the code. Okay, thank you, Melissa. Next up is Tammy. All right, thank you. So last week, I got the Circuit Python core build environment set up and working on my computer and submitted my first PR. This week, I want to learn my way around the Circuit Python code base a little bit better and maybe find some other low hanging fruit places that I can contribute. And since, as was mentioned earlier, I'm planning on starting to stream on Twitch soon. I want to get OBS set up and everything configured this week so that hopefully next week I can do it. My first sort of test stream. And so that's what I'm working on. Okay, thank you very much. And go ahead and put a link to your Twitch stream in the in the chat. That would be great. Thanks, I'll do that. Okay, next up Scott. Hello. Last week, I got Billy scanning and advertising going on the S3 scanning was a carryover from the previous week, but advertising got in. I started on services, servers and characteristics. And I've got a lot more work to do there. I did add a another example to the BLE library for just advertising that doesn't do any service stuff. I needed that for tests. So I put that there. Thanks to Dan for the quick review. I on my stream, I started doing a new broadcast net bridge that just used a circuit Python rather than the Raspberry Pi. So I'm gonna hope to finish that up this week, because it should be doable with just the scanning code that has already been there. And I did, we did find an issue that the the infinite timeout wasn't working. So I got to fix for that. But basically, I'm really going to try to get deep in the weeds of services and characteristics and try to do as much as I can there was a little distracted the last week. And so I'm hoping to get my brain thinking about this this week and making some progress. It's a bit more complicated than advertising and scanning. So there's more bumps to it, I think. Besides that, it's I want to wrap up circuit Python 22, either today or tomorrow. I know Kathy's finishing hers. So but yeah, that'll happen this week as well. Okay, thank you, Scott. And I'll read Tetris contributions. Because they're not in the meeting. Last week, nearing completion on the Discord linked Pi Badge project prototype, working with async.io and display.io has been extremely fun. Apparently some family and friends would like an auto lighting menorah. So I'm going to try to design a few simple print circuit boards to make assembling them easier a first for this Becky. I'm a mechanical engineer. This week in non circuit Python news, taking a small great break to work on grad school applications and moving. Mostly, I guess, taking a break because my own workstation is packed up, they say. And that's it for for for status reports. We would have in the weeds, but we have nothing in the weeds this time. So unless somebody has something I can move on. Otherwise, we'll close out here. Let me put a couple of timestamps in. Okey dokey. So thank you, everyone. This has been the circuit Python weekly for January 31, 2022. Thanks to everyone who participated, whether by typing notes or in the audio chat, or however, that's thank you very much. If you want to support Adafruit and circuit Python, and those of us that work on circuit Python, consider purchasing items from the Adafruit shop at Adafruit.com. The video of this meeting will be released on YouTube at YouTube.com slash Adafruit. There are thousands of videos there by Adafruit. And the podcast will be available on major podcast services. This meeting will also be featured in the upcoming Python for Microcontrollers newsletter. Visit Adafruit daily.com to subscribe to the newsletter. The next meeting will be held next Monday as usual at 2pm Eastern 11am Pacific US time. This meeting is held on the Adafruit Discord, which you can join by going to adafruit.it slash Discord. If you want to be notified about the meeting and any changes at the time or day, you can ask to be added to the circuit Pythonistas role on Discord once you join Discord. So we hope to see you all next week. Thanks everyone. I'll be putting up the new note stock later today for next week. Thanks, everyone. Thank you very much. And I will stop recording now.