 Hello, everyone. This is the Circuit Python weekly meeting for July 11th, 2022. It's the time of week when we all get together to talk about all things Circuit Python. I'm Jeff, and Adafruit sponsors me to work on Circuit Python, which is a version of the Python programming language designed to run on tiny computers called microcontrollers. Circuit Python development is primarily sponsored by Adafruit. So if you want to support them and Circuit Python, consider purchasing hard work from adafruit.com. And if you live outside the U.S., check out the link at the bottom of the page, on every page on the store for international resellers. This meeting is hosted on the Adafruit Discord server. You can join anytime by going to adafruit.it.discord. We hold the meeting in the Circuit Python Dev Text Channel and the Circuit Python Voice Channel. It typically, as today, happens on Mondays at 2 p.m. Eastern, 11 a.m. Pacific, except when it coincides with a U.S. holiday. In the Notes Dock, there's a link to a calendar that you can view online or add to your favorite calendar app. We also send notifications about the upcoming meetings via Discord. To receive these notifications, ask us to add you to the Circuit Python East's Discord role. There is a Notes Dock to accompany the recording and meeting. The Notes document contains timestamps to go along with the video, so you can use it to skip to the parts that interest you the most. As the meeting can run up to 90 minutes, we think it's really handy to have the option to skip around. After each meeting, we'll post the link for the next week's meeting notes in the Circuit Python Dev Channel on the Adafruit Discord. Check the pinned messages to find the latest Notes Dock so you can add your notes for the following meeting. And if you wish to participate but can't attend, you can leave hug reports and status updates in the document for us to read during the meeting. The meeting is held in five parts. After this intro, the first part is community news, where we take a preview of the Python on Controllers newsletter and see what people around the web are doing with Circuit Python and Python on hardware. Next is the state of Circuit Python, the libraries, and Blinka, which is a statistical overview of the whole project, a chance to look at some numbers that summarize what's going on separate from what we're all individually doing. Then, the first of two participatory sections is hug reports, an opportunity for you to highlight the good things that folks are doing and to take the time to recognize awesome folks all around our community. The fourth part is status updates. Status updates is an opportunity to sync up on what we have been up to. You can take a couple of minutes and talk about what you've been doing in the last week since the last meeting and what you'll be up to over the next week until the next meeting. Then the last part when necessary is called in the weeds. If there's a need for a more long-term discussion, this is where we want to do it. It can either come out of status updates or be something that you've identified ahead of time as being too long or anything where you want to get back and forth and talk about opinions. That's where that goes. That covers the structure of the meeting. With that, I am going to head over and start community news. First up, and we're all really excited, announcing Circuit Python Day 2022 on August 19th. Is this correct? This says Tuesday, August 19th. I thought it was a Friday. Anyway, we'll double-check that. August 19th is Circuit Python Day 2022 and we've decided that that is the snakiest day of the year. The day highlights all things Circuit Python and Python on hardware. Do you work with Circuit Python? Tag your projects, hashtag Circuit Python Day 2022 on social media and Adafruit will look to highlight them. Special events will be held during the day. Keep an eye on Adafruit social media channel for announcements and there is a link to the Adafruit blog. We're really, as usual, soliciting the whole public to come and work with us on this. There's an email address to hit up with your ideas and we'll be in touch about that and looking forward to the day of. Next up, I like this link to inclusive design, a Microsoft methodology born out of digital environments that enables and draws on the full range of human diversity. Most importantly, this means including and learning from people with a range of perspectives and there's a link to Microsoft and also a PDF document version. It's probably not the last word but, you know, it's great to see thought going in this direction and everyone working better to make things more inclusive. So, next up after that, Project of the Week, the BornHack 2022 game on badge. The BornHack game on badge puts the focus on games. With the shape of a small controller and a color LCD screen in the middle, it's ready for a bunch of interesting homebrew games. There's a whole spec list but basically, it is going to be able to run Sergipython, MicroPython and all those great things that you know about and check out the newsletter if you want to know more. Then another badge called the title badge. It's got a funky little shape and it is your electronic companion at EMF 2022. Next up, a fun project with MicroPython using April tags and OpenMV to open a front gate and that one is via Hackaday. So, this is just a few items out of the upcoming newsletter. The Sergipython Weekly newsletter is a community-run newsletter emailed every Tuesday. The complete archives are at adafruitdaily.com slash category slash Sergipython. It highlights the latest Python on hardware-related news from around the web including Python, Sergipython and MicroPython developments. We want you to contribute your... We want you to contribute your own news or project, so please edit next week's draft on GitHub and submit a poll request with the change. There's a link in the note stock. You may also tag a tweet with hashtag Sergipython on Twitter or email cpnews at adafruit.com. And of course, thank you very much to our very own Ann who spearheads this newsletter every week and it's just wonderful. So anyway, that wraps up Community News and we are moving on to the state of Sergipython, the libraries and Blinka. So every week, we get an overview of activity on GitHub over the last seven days and divide it up into a couple of categories. And so overall, in terms of activity, we had 28 poll requests merged by 15 authors. And a name that I don't recognize is Liz Apple. And Ketney is hopefully highlighting a few for me. Carl F... Excuse me, Carl F.L., Theta Zero, and Tom24 are also newer or less frequent contributors, but we want to thank all 15 of those authors. Then we come to reviewers. Reviewers take a look at poll requests in an official capacity and say this looks great or this looks great, but we'd like a few changes. And anyway, this week we had eight of them and they are a lot of the usual people. So thank you very much to those reviewers and also people who are operating outside of the official reviewer capacity by just commenting on poll requests with, I looked at this, it looks good. I tried it, it fixes the problem. This helps us enormously in taking all the best changes and improving CircuitPython, the libraries and Blinka. And with that done, I will also tell you about the core. The core is the most central part of CircuitPython implemented in the C language and within that we had nine poll requests merged by eight authors. So LizApple is on that list again. So thanks for your contribution. And we had just two reviewers, Dan and Scott. And that is a big wake up call to me that I need to be reviewing poll requests of which we have 17 open poll requests. About half of them are under a week and some of them are open nearly 300 days. And so as usual, we need to kind of look at it from both ends and just keep on top of things a little better than we do. In terms of issues, we had nine closed issues by four people and 13 open by 10 people within the core. So we did have a small increase in the number of open issues leaving us with 538 open issues. And one thing that we did last week among Scott and Dan and Catney and I was review the bug list according to Milestones. We use Milestones to show Adafruit's priority in dealing with open issues. And so for 73X, we have three issues, probably what we hope are minor bug fixes that we'd like to make before releasing another stable seven, sort of Python seven version. And then for version eight, we have 41 open issues that we'd like to address before we release that as a stable version. And besides that, we have 469 issues labeled long term, which means that Adafruit isn't prioritizing them right now, although we always love community support to work on those issues. So if you're looking at an issue that you're interested in, pay no attention to the fact that it's long term. Let us know you want to work on it and get started and help us improve circuit Python. So yeah, as far as what's going on narratively, we are really working on version eight. Scott has made some huge strides with the web workflow, which was recently merged. And we would love it if you would kick the tires of that. And Dan has been working on the port to the ESP32, original version, which he's temporarily handed off to me. And so really our focus is on these, both finishing up these larger features that we would like in Ado and also tidying up a lot of smaller things. But that is where our thoughts and work are going. And with that, Katnie, I hope you can talk to us about the libraries. I can. So this section is about all of the Adafruit circuit Python libraries, which is everything that starts with Adafruit underscore, circuit Python underscore, as well as a few extras, such as the community bundle and our cookie cutter. Across all of those repositories, there were 19 pull requests merged by a few of the new names, including by a few of the new names that Jeff called out earlier, and a few folks that have been around for a while, thanks to all of our seven authors and seven reviewers. The oldest one was 11 days old, which is great. There were a number of them about a week old. And it looks like we're definitely keeping up with our newer ones as well. So that's really good to see. And that leaves us with 22 open pull requests, which is getting it a little bit down from last week. So that's good to see as well. We had 10 closed issues by five people and eight open by seven people, leaving 649 open issues. 175 of those are labeled good first issue. If you're looking to contribute to circuit Python on the Python side of things, check out circuitpython.org slash contributing. If you're interested in reviewing, you can check out the open pull requests. If you have the hardware tested, if you don't, you can check the code for spelling syntax, that sort of thing, and leave a note and let us know that you did. That's always helpful. And once you're comfortable with that, we can talk about leveling you up to the review team. If you are looking to contribute 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 circuit Python using Git and GitHub, as well as we're always available on Discord to help you out there as well. We want you to be able to contribute in a way that works for you. In terms of library updates in the last seven days, there were no new libraries, I don't think, and a list of updated libraries that are in the notes, but I will not read them off. And that's where we are with the libraries. Thank you, Katni. And last up in this section is Blinka. So, Melissa, if you are around, can you give us the details? I am. So, Blinka is our circuit Python compatibility layer for MicroPython, Raspberry Pi, and other single board computers. And this week, we had zero pull request merged. There are currently four open pull requests amongst the repositories. And there were zero closed issues and one open by one person. And that leaves us with 77 open issues. There were 7,896 Pi Wheels demos within the last month, and we are at 89 boards that we support. And that's it. Thank you, Melissa. And now it is time for the first round Robin section called Hug Reports. As I was saying earlier, Hug Reports is kind of an antidote to bug reports, and we want you to use this time to thank people around the community who helped you out or who you saw helping out a third party. And anyway, just generally recognizing and building up the people around us. So, I will start, and then we'll go in the order of the text of the notes document. So anyway, I wanted to thank Dan, Scott, and Katnie for meeting last week to go through the 80 issues list. And as well, Dan and Scott for meeting to talk about the ESP32 branch and brainstorm about the issues that we're facing there. And Katnie for helping keep the Discord server, this doesn't quite make sense. The Discord server moderation up to date with the latest technology, that's what I meant. And finally, a group hug. It's so nice to host the meeting again after my break, even though I'm rusty, it helps me feel like I'm back in the swing of things again. And yeah, so next up, I have a note from C Grover, who is listening in today, or text only, who has a hug for BlitzCityDIY for a very useful PyPortal Light Sensor Gesture Detection Scheme. Although my final method is different, it was inspiring to see Liz's creative approach and thorough logic. Next, AskPatrickW writes, thank you to Naridoc, Kyle Moore, Ealdave66, Purples, Meagher, Melissa, and Tanude for all their help and patience as I worked on the Wemos, Lola, and C3 board definition since April. An extra special thanks to Todd Bot for adding Wi-Fi.radio.tx power so the Wemos C3 can connect to Wi-Fi. Next, we have Charles Burniford, who has a group hug for everyone. And Dan, who is not at the meeting today, has a hug for me and for Tanude for the ESP32 port meeting and another for Tanude for an earlier discussion on expressive SDK config settings. A hug for me, Scott and Katny for the 800 bug triage meeting and finally a hug to Lady Aida for suggestions about ESP32 problems over the past several weeks. And I hope somebody else is going to talk after a while because I also have notes from David, who is in the meeting, who has a hug for Naridoc, Tanude, retired wizard Dan H, and Ealdave666JP and whoever else helped me to start playing with the web workflow or is also trying to be out there on the edge. And all right, I think this is the last one that I get to read out. Fome Guy has a hug for Naridoc for being on Show & Tell to show a web-based library management tool. That was a really cool show. So yeah, check that little segment out if you didn't see it last Wednesday. A hug to DJ Devon 3 for the new Bitmap Saver example as well as getting more involved in the community and helping folks on Discord and a group hug. And now, Katnick, it's your turn. I don't know, my list is pretty long. Maybe I should make you read it. Oh, no. All right, so first up, a hug to Scott, Dan, and Jeff for meeting to further triage the 8.0 milestone. To Brent, Phil, and Lamor for being super understanding during a situation on Friday. To Brent and Lauren for Whip or Snapper, I haven't had a chance to or a reason rather to mess with it until last week to help Brent out and what little I've seen of it so far seems really well done. Belated hug report to Mr. Certainly for helping me with some guide content that was finally published last week. I had a series of lists and or a list. There's multiple lists each with like a bit of content and an example of using that content. And it was all very much mixed up and not very well formatted. And Mr. Certainly is very good at dealing with stuff like that. So I tagged him in and he reordered it all perfectly and gave me a better way to format it and so on. And so it looks much better in that guide. To Foamy Guy for helping me with some code on the other guide I published last week including some last minute guidance. To Tech Trick for continuing to work on the switching to pyproject.tomol on the Libs. To Naradok for catching a potentially two-year-old bug with Sparkle in the LED animation library. To Dan for helping out a friend with getting started with CircuitPython development. Thanks to the folks on Discord who reported changes to how the moderation bot is working. And to everyone who's agreed to contribute to CircuitPython Day so far and a group hug. That's what it got. All right. Thanks, Catney. Next up is Kmatch. Hello. Hey, thanks, Jeff. My first hug goes out to all the folks that come on show and tell with their projects. It's really inspirational to see things and sometimes it's nerve-wracking to go on the video but thanks to everybody who brings their things and shows what cool stuff they're doing. And second for Lady Aida for answering questions on the live streams. So I don't know anywhere else where you could have a random question and actually get a good answer from a well-experienced engineer like that. So I appreciate that. Okay. Thanks all. All right. Thank you. Maker Melissa, you are next. You're muted. I know the window kept moving around. I just tried to hit the button. So I wanted to give a hug to Scott for helping me out getting the ESP IDF working with CircuitPython, so I can now compile the ESP boards again. Brent for helping figure out a good workaround for whippersnapper which was not going on to the QT by C3 board and a group hug to everyone else. All right. Thank you, Melissa. And now I have a couple of people to read their notes. So Mark writes group hug and Temmie makes things. Has a hug for Katnian PT for helping me get an Adafruit discount code for the DesertPyMeetUp and a group hug. And then we go to Scott. Hello. Hug report to Katnie for me for taking the lead on organizing CircuitPython Day and also Jeff and Offer, if you want me to read status updates, I'd be happy to do that. All right. If your voice is... Yeah, no, it's fine. I'm just hamming it up a little bit. Well, feel free to hand it off to me. Like, I know it can get tiring. I've been there. All right. And to round out the section, I am going to read notes from TechTrick who has a hug for Katnie for continuing to help with work on moving toward pryproject.com.toml, a hug for NairDoc and Fumiguy for helping to point out and fix the Adafruit logging quickly and a group hug. And that leads us to the next section of status updates. It's really important that we know what each other is up to. And so during this section, we invite you to let us know what you've been up to since the last time we had a chance to meet together and what you hope to be up to in the near future. If you're consistently with us, then that means one week. If you don't make it as often, then please feel free to fill us in on a little more. And if you want to give us a little glimpse into your wider life, that is totally cool and we'd love to hear about how, for instance, your kitchen remodel project is just out of control and you've got a plan to fix it with CircuitPython or whatever that might be. Anyway, so I'm still getting back up to speed a little bit. But last week, I played with QMK because of how the support for RP2040 is merged into their development branch and we'd like to do some guides around that. And I kind of have an outline of a guide in progress. I know what hardware I want to show it working on and I just need to flesh that out, get photos and test it more and all that good stuff. As mentioned several times, we went through the list of issues for version 8. We moved some to long term. We assigned others among us. And of course, we'd love your help with the 8.0 issues list and whether that's by actually fixing or implementing the things on that list or just providing information and testing as we go. Everything that you do is helpful. The other thing I did was I updated micro lab. The we go long enough between updates that there's always something interesting of compatibility problem to solve or new features that have a wrinkle in CircuitPython. But I think that that pull request is ready to go in and if it does CircuitPython 8 will ship with micro lab version 5. So this week I am starting on the ESP 32 CircuitPython port. Dan created a draft pull request but there's a fairly serious memory corruption bug which means it's not really usable. In any case, we will probably merge that PR because we don't believe it's disturbing other things other ports and that kind of lowers the barrier to someone with a debugger or with an idea who wants to try it. Although I'm going to take a couple of days to try and crack that first. And then besides working on this QMK guide I will work on other version 8 items that we identified last week and sometime in the future somebody maybe me is going to look at whether we can bring the Wi-Fi support of the PyCal in but that is definitely not something that's happening in the next week so I probably shouldn't mention it. And next up from Ask Patrick reports the Wemos C3 board definition definition is completed the CircuitPython.org board page is created and the Wemos stocks have been updated with links to CircuitPython. Cool. Dan writes that he's been working on the plain ESP32 port. The REPL works but there is a crash when Thani passes code to the raw REPL it might be a GC problem and pass the baton to me for debugging this. Also did some refactoring and some settings automation for all expressive ports in the process of adding ESP32. Next after that I have notes from David who excuse me is trying the absolute newest on all S2 and S3 boards to start playing with the web workflow and he also upgraded his game builder garage texture tool to auto detect and work automatically on five different boards. The clue the WIO terminal the S3 with the TFT feather the PyGamer and the expressive S3 USB OTG and there is a link in the notes dock to a GitHub repo. Future plans to test and document the web workflow for adding a texture in game builder garage. This should be possible by using the web workflow and the web server with the upload function. 22 will be for him the year of the Linux laptop. David writes I moved from Windows on a T440p to Ubuntu on a T540p. So my circuit Python workflow is a bit disturbed but I have the same you browser circuit and get so it's just a bit different. Dual booting never really worked for daily use of free software but having two separate laptops and forcing myself to use the Linux one is the solution. Next notes from FOMI guy. FOMI guy says house is getting new siding lots of banging and power tool noise for a few days. Still working on final touches for the octopus game and getting the structure of the guide laid out. Took apart an old project to get at the SD card slot on the 3.5 inch TFT feather wing to test a new bitmap saver example for it. Following up on OpenPRs and finally working on adding relevant links for the built in modules in the core circuit python docs pages and next up is catney. Hello. Hey. Last week finished up the github actions status tower light guide and put that into moderation. I did not note but the get action status light guide and the github excellent github profile guide were both published last week as well. I updated tested a new feature in learn found some bugs pass those on started circuit python day planning and started helping Brent out with whippersnapper guide templates for board guides. This week continue working on whippersnapper guide templates test for a bug in the sparkle LED animation. I need to check into our dino bot moderation that we use on discord to figure out what changed with flagged keywords. And then once available in the shop I will be getting the stem of QT quad segment displays and then do a scrolling countdown timer project with those and that's oh the other thing is I'll be off Thursday and Friday for the next few weeks we're building a room into our basement which should be it'd be interesting but it's well needed and I'm glad we're getting it done so that's the other personal side of things I guess that's all I've got all right and next up is came at thanks Jeff so this past week I created a feature request on github an issue that requests an interrupt driven event Q for capturing I squared C events this is all towards the objective of reducing the number of processor cycles used polling for touchscreen events so that I can spend most processor time on the actual animation part so if anyone has inputs on and I particularly learn on taking other modules seeing how they work and then happy to hack in those into something else if you have any other existing modules that might head in that direction one of which is keypad IO which does have any event Q in it but if there's others particularly related to scheduling like I to C queries or something like that I would appreciate it and there's an issue is noted in the document this week I had a request for proximity sensor problem and I'm want to study if ultra wideband might be a solution to do that then the last thing is just back to real work catching up on the backlog while was out for a little while okay thanks all right thank you and next is maker Melissa hello so last week I caught up on emails and messages from being awful few weeks before that and then I looked into an issue where the ESP webplaster is having issues flashing the C3 chip at addresses other than zero or actually is when it did multiple files at addresses other than that I updated the have actions for whippersnapper to add a separate workflow to C3 to produce a combined binary file and that got tested today and it works good I updated my circuit python installation I took over the ESP box light board that Scott had started and made some and I tweak the display and that parameters to work and got that submitted I started looking at web workflow what would need to be changed in code that circuit python to org to make use of it and I ended up getting the web workflow working but didn't end up getting further than that this week I'm going to finish up merging in and add that to circuit python dot org and then look at the web workflow and some more and get that now that I have it working and possibly work on a new project guide using the ESP box hopefully in a bit quick one and that's it thank you and next up mark button real quick if you want to read your notes but otherwise real life has been keeping me from doing a lot lately I'm still around a discord if anyone ever has a question in regards to anything I have written but I did find time to make googly eyes there's always time for googly eyes that was another good one on show and tell last week so thanks for that mark and then I have notes from Tammy makes things who writes last week prepared for and gave a circuit python demo at the desert pi meetup in phoenix had these and I gave away three circuit playground express devices with the giveaway winners chosen by random dot rand in run from the repel of a pie badge all of the feedback was very positive I tried to stream slush record the presentation but was unable to do so for technological reasons made a decision that at least for now my twitch streams will need to be on an ad hoc basis rather than on a regular schedule because my workload of my day job is very high right now and hoping to load a latest build of circuit python which fixes the async I oh issue I ran into on my matrix portal and finished my team city C I CD status board project hoping to stream at least once and do some more work on my card deck library and last was playing around this weekend with an implementation of Conway's game of life for someone else and I'm thinking about taking my implementation and wrapping a matrix portal UI round it next up hello okay so I am getting close on this web socket serial thing so this is the ability to do the serial connection from a web browser I got the HTML CSS and JavaScript working well enough on mobile that it's not terrible just at least on my phone zooming to input boxes through me for a loop so yeah HTML not my strong suit but I'm pretty happy with that as a Friday so I need to clean up this web socket stuff and make a PR I think it's ready for a PR I'll have to take a look and see if there's anything else but I think that's pretty much if for web sockets I'll look today my next step will be polishing up the work web workflow more and more people have been testing it which has been awesome so there are some issues that I'm going to have to take a look at and do things in particular making it work better including checking the responsiveness like there's a retired wizard came up with this fix to basically prevent ticks from being disabled I think we do want to disable ticks but I think we want to like poke poke the circuit Python task when sockets have stuff available I don't think that's happening right now so that's that's part of the fixing I need to do and then I also get more comfortable with new and our shell and Fani so that I can make sure that the the set title stuff doesn't break him and I'm also out next week for vacation this week there's a lot of stuff going on so I may not be here when you ping me but I'll try to get back within a few hours assuming it's not right before the end of the day because I am also trying not to work late into the night that's it for me thank you Scott and last up for this section is Tectric who is text only last week additional prep work for getting libraries to use pie project dot Tom all most of the work is done just going to give the few test libraries that I am using it time in the field before any next steps submitted a PR to update the read me for the actions see I repo reviewed type annotations PRs which is always fun the issues for a to fruit logging fixed up documentation in infrastructure for a couple of new libraries tried to figure out if the blue fruit connect phone app is able to send a large amount of data but I think my Bluetooth sniffer was thwarted by the sheer amount of BLE traffic in my apartment complex next week Tectric writes continue to add an update documentation in the core and continue working on status updates and the next section is in the weeds looks like we've got three topics here so I will take them in the order they are in the document so Tectric writes if the plan is to move from secrets dot pie to dot ENV files should we consider changing the suggested virtual environment name in library readme is away from dot ENV apparently we suggest the command line Python dash M V ENV dot ENV not sure if it might confuse users to be told to edit dot ENV if they also have a dot ENV folder comments yeah that's confusing yeah absolutely though it can be named whatever that's the the Python virtual environment so I think it would make a lot of sense to change that because the the name is arbitrary when it comes down to it if you're making a virtual environment to load a library um are there are there's some tools that automatically detect and move into virtual environment still excuse me um know what their defaults are oh there you go Paul says PyCharm and VS Code will detect both dot ENV and dot V ENV so well could we do do could we do V ENV then yeah because does ENV is now the thing you're doing right yeah yeah okay so let's switch it up to V ENV then um should be enough of a change to keep it from being confusing and not enough of a change to BORK IDEs yeah and I I would like to point out that virtual environments shouldn't be used on circuit by drives but this is a be able you should be be able to do the reverse of use it dot ENV file in regular Python this is when installing from Pip right so this this isn't telling you to do that onto a circuit by drive yeah it's a good point though that should be less confusing okay so the suggestion would be to use dot V ENV because it's supported by PyCharm and VS Code yes and cat and he's putting that in the docs or in the in the notes document thank you and Tectric's offering to do it all right thank you Tectric that's all we've got on that subject going once going twice then funny guy you are up all right I'll try to sneak it in quick here but if I disappear then I'll switch back to text but basically my question was around if we want to have guide pages or guides somewhere that cover display IO adjacent concepts like Vector IO and bitmap tools are the the specific to that I had in mind and then if we do want to have a guide that covers those would it makes sense to be a new guide or to be new pages perhaps within the display oh god I know looks like I did see definitely my question is how do you do you have to use display IO to use the other two um you you have to use display IO to use Vector IO I suppose you could use bitmap tools to just manipulate a bitmap in memory that's not common save it back to the file system but I would guess the overwhelming majority of people who are using it are gonna be using it in conjunction with display IO but I don't think it's new pages in the main display IO guide okay sounds good yep that's my thought awesome thank you all right nice clear cut answer from catney thank you both of you and catney I just wanted to highlight real quick circuit python day which is Friday August 19th 2022 and let you know if you want to participate or contribute please email circuit python day at adafruit.com with any questions suggestions or ideas we're looking still like we're very much in the early stages right now so we're looking for all kinds of things whether you have any ideas for events or how you would want to contribute if you could just let us know and that was all I got and it is a virtual event so I think what we're concentrating on is basically streaming some blog stuff maybe but streaming is kind of the number one thing that we're trying to do right yeah and but I had one idea and this like I said this is up in the air don't hold me to it was a possible stream where folks could contribute videos like short you know short one two minute videos and then if they can't make the stream because there's a lot of folks who can't make show and tell you know and wish they could do that though I thought if we could put together like a half hours worth of worth of video clips we could actually just do a one of the streams during the day be just highlighting video clips of of folks stuff that they send in so that's that's an idea doesn't stream or it has something to facilitate doing that I have no idea I was a little worried Phil would have to do it because I know they ask an engineer setup can do it yeah I think something was added to stream yard we should take a look at that or somebody okay but I'd be happy to take a look at it with you yeah yeah um sounds good uh that that's one of the one of the ideas that I had I thought that we could do a special edition show and tell um like so an actual live stream of folks um that would be ideally you know circuit python related um we obviously can't uh we're not gonna gate check folks um but the other thing Oh the other thing was was possibly a mini sprint if we can find enough folks who would be willing to facilitate that um it would be virtual so I don't know how many you know how how much we'd have participation but um it might still be cool to have a couple hours set aside to uh um you know help help new folks uh contribute to circuit python if they were interested in that because we've we've never done that before um but anyway those are the ideas about right now but if you have any other suggestions you being please send them in because we're we're in early stages of of getting ideas but um you may certainly have more ideas than we do so and it's only about a month from now so don't hold back yes don't wait yes yes please please do thank you catney thank you everybody who's participated today and everybody who's listened in I think we are ready to wrap up the meeting this has been the circuit python weekly meeting for July 11th 2022 and our next meeting will be at the usual time on Monday July 18th usual hour of the day and we look forward to seeing you there let's see what else am I supposed to say at the end the meeting is held on the Adafruit Discord we invite you to join us any time by going to A-D-A-F-R-U dot I-T slash Discord we've got going on 35,000 people and we just all help each other 24-7 as I said to be notified about changes to the time or day of the this meeting you can subscribe to the calendar and you can also ask to be added to the circuit python needs to his role on Discord and yeah video of this meeting will be released on YouTube and then later re-released an audio farm as a podcast so check us out on your favorite streaming service and that wraps it up we hope to see you all next week and thanks again to everybody thanks everyone