 Hello, everyone. This is the Circuit Python weekly for Monday, August 7th, 2023. This is the time of the week when we get together to talk about all things Circuit Python. I'm Dan, and I'm sponsored by Adafruit to work on Circuit Python. You might ask, what is Circuit Python? It's 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 anytime by going to adafru.it slash discord. We hold the meeting in the Circuit Python DevText channel and the Capital Circuit Python voice channel. Typically, this meeting happens on Mondays at US time, 2 p.m. Eastern time and 11 a.m. Pacific time, except when it coincides with US holiday. In the notes document, which we'll talk about later, there's a link to a calendar you can view online or add to your favorite calendar app. We will also send notifications about upcoming meetings via Discord. If you would like to receive these notifications, ask us to add you to the AdSign Circuit Pythonistas Discord role, and you'll get a ping once a week and before the meeting. There is a notes document, which is currently a shared Google Doc document, to accommodate the meeting and recording. The final notes document includes timestamps to go along with the video, so you use the doc to skip around and view the parts of the meeting that interest you most. The meeting tends to run 45 to 60 minutes. After each meeting, we will post a link for the next meeting's notes document to the Circuit Python Dev Channel on the Adafruit Discord. Check the PIN messages to find the latest notes docs so you can add your notes for the following meeting. If you wish to participate but cannot 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, Community News, the State of Circuit Python, Libraries and Blinka, Hug Reports, Status Updates, Updates. I'll explain each of those as they come around. And when we'll get started by doing Community News, Community News comes from the weekly Python or Microcontrollers newsletter, which goes out by email on Monday morning. You can go visit AdafruitDaily.com to subscribe to the newsletter. Thanks to Ann for putting the newsletter together. If you have any Python and Hardware projects to share or find content you'd like to see included in the newsletter, please consider contributing. You can open a PR on GitHub. The newsletter is collected, it's explained that the newsletter is collected weekly in GitHub. Tag at sign underscore engineer on Twitter with hashtag sort of Python or email cpnews at adafruit.com with a link to the interesting news. Okay. So first I'll go over what we've got in the upcoming newsletter. Newsletter came out this morning, so you've probably seen, if you get the newsletter, you've seen this already. And for the rest of you, this will be a review of the kind of content you can get. These are kind of the top headline items that are particularly pertinent to Circuit Python. So Circuit Python Day, which comes once a week, is this year is on August 18th. That is a Friday, not very long from now, 11 days. And a slate of events is being developed to celebrate the snakiest day of the year. There's a link in the notes document to the blog post, which has the current agenda for things that are happening. And there may be more that it be added. Highlights are Paul Cutler will be hosting a panel about Circuit Python's new Synthio module. Tim Fomegai will be hosting a Circuit Python code gem. Melissa will be hosting a project live stream. And Jeff Dan and Katnay will be having a Circuit Python chat. So keep track of this blog post for updates on specific details and events and when they are. If you'd like to tag something and have it mentioned during Circuit Python Day, tag your project, Circuit Python Day, hashtag Circuit Python Day 2023 on social media. Look for those and highlight them. You have other events that you'd like folks to attend or have projects in the works. You can email them your thoughts to CircuitPythonDay at Adafruit.com. And we've had, for instance, one year there was a Project Day in India, which was on Circuit Python Day. And that's the kind of thing we'd love to highlight. So thanks to everybody for contributing to that and attending when it does happen. Next item is about that Damien George, the MicroPython lead was on the embedded.fm podcast. Damien George spoke with embedded.fm about developing with and for MicroPython, while Alicia White tries not to spill all the secrets about her client. I'm not quite sure what that means. Maybe it's another person who's on the same podcast. To start at the beginning and understand what's going on, you will probably want to check out MicroPython.org. Before listening to the show, you might read the Wikipedia MicroPython entry, because they kind of start in the middle in the show. So you want some background. Next item, and I've been failing to take a time stamp, so let's take a time stamp. Here we go. One is changing their native module naming scheme. It used to be that the native modules all began with the letter U, like UOS and UJSON and so forth. Starting in version 1.21, all built-in modules will have been renamed to match the regular, the CPython name, OSSJSON, et cetera. That's what CircuitPython has been doing for a while. The only exception is UC types, which is really not anything like C types. So it will keep the C types' names. Also UAsyncIO and your requests have been renamed to AsyncIO requests. Those are Python libraries, but they're actually part of the MicroPython code base. There's a lot of existing code that uses the U prefix, like import, you might say import UOS or import your requests. So those things will continue to work. So they're basically an alias for the old name. But please prefer to use just a new non-U prefix name from now on. And going along with this, the idea also, as has been true in CircuitPython for a while, is that these libraries are the same as or subsets of the CPython functionality, mostly. There are a few exceptions. But the idea is that if it could run in MicroPython, then it should be able to run on regular CPython. That's regular desktop Python, usually. OK, next item. There is an FPGA ice called Ice40. And there's now a CircuitPython library that lets you program that FPGA, the details. I will not read all the details here. But there's a library called IcePython. And it lets you program any Ice40 FPGA with the simple, by writing some CircuitPython code. So read about that in the newsletter. And there are links to the details in the notes also. And there's an FPGA, there's a feather shaped board that has this FPGA Ice40 on it for you to see. OK, as I mentioned, all this material comes from the CircuitPython Clean Newsletter, also called the Python and Microcontrollers Newsletter, because it's really more than just CircuitPython. So there are links to contribute. There's a link to the GitHub repository where we collect information each week. And you can also, as we said, tag a tweet with hashtag CircuitPython on Twitter or some other social media site or email cpnews at Adafruit.com and we'll pick that stuff up. OK, our next major section is the state of CircuitPython, the libraries and Blinka. This report contains information from the previous seven days, but it was done last night. So any changes that have happened since then are not included in this report. And somebody did this work for me because I forgot to do it. Thank you whoever pasted all that in. Overall, there were 32 pro requests merged with 20 authors, five reviewers, and there were 13 closed issues by five people and 13 opened by 12 people. So we're running, we have the same number of issues open as closed as open. OK, next up is the core section. And Scott, if you were able to read that, go ahead. Yeah, I'm here. Just finding my, finding my windows. OK, so the core, we had 20 pull requests merged from 12 different authors. Thank you to those folks. Lint Smikka is new. Alp, Alpakinian is relatively new as well. And I think a number of those other folks are translators. So thank you to everybody who's contributed to the core recently. We had three reviewers, Jeff Dan and I. We had 25 open poll requests, which puts us on that single page mark, which is great. And a number of those are pretty new, which shouldn't make it easy to get through as well. Issues-wise for the core, we had three closed issues by two people and six opened by six people. So we're up three for a total of 681 open issues. We prioritize 80 fruit funded development using the milestones. So this is to say that if you want to work on something that's marked long term, you're more than welcome to and we're happy to assist. But the milestones tend to be used for the 80 fruit funded development. We have zero open issues for 802X, so stables looking good. We have 49 issues open for 9.0.0, which is a lot. But we're also not nowhere close to releasing 9.0. And then the other interesting thing here or classification is that we had three issues not assigned to milestones. We always want to make sure and look at issues and triage them just so that we know if anything urgent's come up. And that's the stats for the core. Okay, thank you, Scott. Okay, next up is a report on Certified Fund Libraries. And Katny, could you read that? Absolutely. This is the section applies to all of the 80 fruit circuit Python libraries and all of the libraries in our community bundle as well as a few extras. So across all of those repositories, we had 11 pull requests merged from 10 different authors and four different reviewers. And that leaves us with 51 open pull requests. The oldest open pull request at the moment is 433 days. And that is because our very, very, very longest open pull request, which was 1042 days, has been merged. I'm very excited to see that. Not to mention all but four of the 11 were 18 days or older, including some that were 100 days plus. So I'm really excited to see that we're getting through that. And thank you very much to FOMI guy for seeing to it that that's happening. As for issues, we had nine closed issues by two people and seven open by six people leaving us with 628 open issues. 19 of those are labeled good first issue. If you're interested in contributing to Circuit Python on the Python side of things, check out circuitpython.org slash contributing. You'll find all of this information and more including open pull requests and open issues. If you're interested in reviewing, check out the open pull requests. Feel free to leave a comment with what you find if you have the hardware test it, otherwise just let us know what you think of the code. And once you are comfortable with that, we can talk about leveling you up to the review team. If you're interested in contributing code or documentation, check out the open issues. Find something that interests you. Leave a comment, let us know you're working on it. If you're new to Git and GitHub, we have a guide on contributing to Circuit Python using Git and GitHub. And we're always available on Discord to help out. We want to make sure that you can contribute in a way that works for you. In terms of library PyPI download stats this week, we had 164,880 PyPI downloads over 311 libraries. And the top 10 are listed in the notes if you're interested. Library updates in the last seven days, we had four updated libraries and no new libraries. And that's where we are at the libraries. Thank you, Katny. OK, next up, it's about Blinka. And Melissa, if you're available to explain about that. Yeah. So Blinka is our Circuit Python compatibility layer for MicroPython, Raspberry Pi, and other single board computers. This week, we had one pull request merged by one author and one reviewer. There are four open pull requests amongst all the repositories. There's one closed issue by one person and zero opened. That leaves in 100 open issues. And there were 12,256 PyPI downloads in the last week, 10,214 PyWheels downloads in the last month, and we are at 119 supported boards. OK, that's it. Go ahead. Thank you very much, Melissa. OK, I'm not sure if somebody else has anything to say. OK, next up is Hug Reports. What is Hug Reports? It's a chance to highlight folks in the Circuit Python community and beyond for doing awesome things. I'll start, and we'll go down the list alphabetically, as in the notes, to give everybody a chance to participate. If you are text only or missing the meeting, I'll read your notes when I get to them in the list. So I will start. First of all, let me put a timestamp in here. I managed to reset my timestamp board, so I'll be doing it by hand from now on. Thanks to Alpha Cannon for working on several Circuit Python issues over the past few weeks, including several pull requests and bugs and things like that. That was thanks for working on this thing very nice. Thanks to Brent and Jeff for a quick update of the expired certificate that Adafruit IO depended on. So people were having trouble connecting to Adafruit IO because there was a certificate that had expired, which Adafruit IO depended on. And so we updated a list of certificates in Circuit Python. And we also updated, Brent updated, the Nina firmware, which the Airlift board chips, Airlift co-processors use with their own various boards and also our own breakouts. And also, finally, thanks to Deshipu for noticing that a lot of issues that were marked as good first issue were not really such good issues, good first issues. And he went through them and triaged them. And I also helped clean them up in coordination with him. So that worked out really nicely. OK, next up is C Grover. And I'll read theirs. That's a group hug. And next up is DJ Devon 3. Thank you. I just have a hug to AnikData and LP Kennan for help with ideas and sample NVM code to allow API tokens to persist even after a reset. Thank you. OK, thanks. And next, I'll read David Gloves' contribution. Let me get a better timestamp here. And he has a group hug. And next up is FomiGuy. All right, thanks, Dan. Hug reports this week. Thank you to America Melissa, who implemented support for RGB bitmaps inside ImageLoad Library. That's really cool to see, as well as pointing me towards some resources to better understand how those different formats work. On Discord, one of the community helpers, Ed Keys, thank you to them for pointing me in the right direction and giving me some guidance on trying to analyze some audio data that I came across and a group hug for everybody. Thanks. All right, thanks. And next up is Jeff. Hi, I've got a couple of things today. I want to start out with a group hug, because y'all are awesome, and then some specifics. Kmatch98, thank you for implementing dot-clock displays in CircuitPython. I believe that's over a year ago now. And I'm really looking forward to learning from your code. And more about that a little later. And a hug to Tectric for popping up right away on the weekend when I ran into trouble building a Circuit Python library in GitHub Actions. Tectric had put in a pull request to change some details about how the tests are done. And I had reviewed it, and we both thought this looked perfectly safe. And it had actually broken building modules that had tests in it. So I guess the key is to test. But now it's fixed. So that's great. That's all. OK, thank you, Jeff. Getting next up is Katny. Hello. This week I have a hug for Todd Bot for helping me get started with Synth.io. I have a little synth board care package on the way that I'm super excited about. To FumiGuy for going through older PRs, as I mentioned, and merging the oldest open PR. And I will echo Dan with a hug report for Deshipu for cleaning up some of the good first issued labels. They were certainly labeled on things that were not good first issues. And we were running into discouraging new folks, which is something we obviously want to avoid. And I also appreciate Deshipu for even bringing up the concern in the first place. That was something that he came up with on his own and offered to help with, which was excellent. And I also have a group hug. OK, thanks, Katny. And Melissa, you are up next. I wanted to give a hug to Jepler for some helpful suggestions with Bitmap Tools and also another one for adding the blip function to Bitmap Tools. Hug to FumiGuy for talking through some ideas to get the Alpha Blend working veteran Bitmap Tools. And hug to FumiGuy and Matland for reviewing my image load PR and a group hug to everyone else. All right, thank you, Melissa. And Paul Kettler is up next. Thanks, Dan. I have a hug for Jepler, Katny, Toddbot, and JP for all agreeing to be on the SynthIO panel for Circuit Python Day and a group hug. OK, thanks. And finally, last but not least is Scott. Go ahead. Thank you, Dan. Hug report to FumiGuy for adding my USB host descriptor library to the bundle for me. Hug to Greg Steyer, who used to work for NSP and is still a helpful person to ask for helping with an IMX RT chip ID question. And then lastly, hug to DCD for taking time codes during my deep dive last week. OK, thanks, Scott. OK, next up is status updates. So this is our time to tell folks what we're working on individually. I'll start and, again, go through the list in the note stock. So say what you've been doing since the last meeting and what you've been doing in the next meeting, or if you have some interesting things to share, go ahead. It could also be, it doesn't have to be circuit Python related if you're working on something else that's interesting. And if a discussion becomes too long, we can always move it to in the weeds, especially if we'd like to have some give and take on a certain topic. All right, I'll start with the time code. So I'm still continuing on the MicroPython v1.19.1 merge. I did a second pass on all the differences and made some edits to that, which I think are going to save time in the long run. And then the next thing is to try to build it. And of course, you immediately run into compiler errors. And so I've just been knocking those off one by one. I'm making that's a thing that is sort of satisfying to make progress on. I do see that there are some major changes that are affecting the code that we wrote for doing long live storage allocation. But that code is sort of what it does is kind of optional. So I'm actually just going to comment that out for the moment and see if I can get the whole thing to at least compile and then go back and study this issue in more detail. And then we talk to Scott about it because he wrote that code originally. In circuitpython.org, I added a more prominent notice in the download of the latest stable version section that for NRF boards, if your boot loader is too old, which is true for a lot of boards, you will need to update that boot loader in order to make 820 load because it's bigger than what the old boot loader could load. So we do keep having people run into this. And they don't necessarily see this problem up front because it's kind of buried in the release notes or it's just within the blog post. So now it is right there where you download circuitpython. And as I mentioned, I released circuitpython 822 a week ago, like last Monday evening, with updated certificates for Adafruit.io. OK, and that is it. So we'll move on to C Grover, and I'll read their contribution. Took a break from technology products through comprehensively upgrade workshop storage with overhead shelving, French cleat tool, and cabinet system. It also meant uncovering and completing an overwhelming collection of delayed carpentry and yard art projects. Just started working out a few PCB projects to our art quote, art projects unquote. Using Ash Park After Dark Color is the other universal version of the Transformerless Class D amplifier output to audio line level circuit known as the reintegrator. The new version will support a 3.5 millimeter TRS style audio jack for the single ended output and two PicoBleg connectors for balanced input and speaker through signals. And next up is DJ Devon 3. I can't hear you. Yeah, other ones. It's going to be really loud with my fan. I'm sorry. I finally found a way to get Fitbit tokens to persist after a hard reset. Again, thank you to AnikData using 64 bytes of NVM storage, my first time ever trying to use NVM. And my goal with all Adafruit API requests that I write is to make them beginner friendly. And adding the token to NVM is an acceptable workaround for persistent storage for the token. There's no need for boot.py and file rights or a server callback, which was one of their required methods. So it's a really neat workaround and can still be considered beginner friendly as long as they don't need to mess with the NVM stuff and they just want to mess with the request stuff. And I submitted a small basic Fitbit API example to the Adafruit Request Library this week. It will require a reviewer to have a Fitbit device. I don't know if that's a really bad thing or not, but I mean, there it is. That's all I got. OK, thank you. I don't think it's a bad thing. We have libraries that are quite hardware-specific, so I don't think there's anything wrong with that. Next up, I'll read David Glode's contribution. It was PicoPad week for him, soldered by PicoPad. It is kind of a pie gamer powered by a Pico and comes as a solder kit. It is made in the Czech Republic and all the software is open sorts. Tested the many built-in games. Tested the CircuitPython firmware and various Hello World and demos. Adopted CP code from LearnGuides for two extensions, PicoPad DS18x20 and PicoPad PhotoCell. Ordered another PicoPad and all the available extensions for my niece. After checking with her father, the soldering part would be OK. Upgraded a few boards to 822 and or the latest Nina firmware and or to the new UF2 boot loader that's the NRF boot loader. OK. And next up is FungiGuy. All right, let's see here. What's my spot? It's scrolled back. There we go. So this past week I was working on submitting some Oshua certificate requests into their system. I finished up the remaining items that are on the new items page on the Adafruit Store currently. This week I am going to work on some scripts to compare a full list of PIDs against whatever's in the Oshua system to find ones that are still missing and get those knocked out next. I did some testing on the RGB support inside the image load. I have been still continuing to make progress through some of the older PRs, knocked out a couple more of those this week or last week I should say and have some more loaded up for the desk this week to look at. I am going to look into adding a new section on the infrastructure issues page in circuitpathlin.org, a section that will find libraries that are in the state where the most recent release is not the one that is marked latest in GitHub. Because apparently those are two different concepts I guess. I found one or two in that state recently. So it would be nice to have kind of an early warning check for those somewhere. As noted a little bit earlier for CircuitPython Day, I'll be hosting and participating in a CircuitPython themed game jam. So I'll stream some of the work on the game that I create that weekend probably. And then anybody else who is interested in participating, I would encourage you to do so. If you do participate and you want to share the game that you make, feel free to put the word out and we can showcase that kind of on like a recap stream or something after the game jam has concluded. If anybody is interested in making something to sharing and sharing it, that'd be great. Outside of CircuitPython land, at least for now, I picked up this toy, this LeapFrog SmartPause toy that I found on clearance at the store recently. It's a thing that allows the parents to customize the child's name as well as a couple other things that the toy can then sing about or say. And there's lots of different activities the child can do with it and different buttons in the pause and all this stuff. But the thing that caught my eye is the way that you can figure it is through a web application that you can use on a phone or a PC. And there's a 3 and 1 half millimeter jack on the toy that plugs in. So it sends data over audio into the toy. And I'm kind of starting to poke around at it and try to reverse engineer and figure out how it's encoding the data it's sending and see if there's any possible way to put customized audio into it beyond what they have pre-programmed. If I don't end up having success with that, I probably will eventually turn to a more surgical approach where I will just implant CircuitPython in place of whatever guts are inside of it today to make it play whatever I want. And that is what I have got going on. Thanks. Okay, thank you for me, guys. Next up is Jeff. Hello. So over the last week, I did a lot of miscellaneous as well as pie camera. I like two or three weeks ago had made some changes to PIO on the special peripheral on the RP2040. This weekend, I got back to testing that, fixed some problems and pronounced it ready. Scott had some very helpful review comments related to hug report to you, Scott, that I need to address so that we can get that merged in that enables two new features of the PIO peripheral, which is to load a program at a specific offset, which you might need to do because of reasons, and the ability to have a program that contains input pins, but not an in instruction because the instruction is run on a demand-based. You know, when the Python code decides it wants to read out a value, it executes an in instruction. And so it just had to bypass or change some error handling so that that was possible. And both of these enable different ways of reading from quadrature or rotary encoders. As for the pie camera, you know, I've got this prototype board. It is a cool little board. It is still a ways out from being offered on the Adafruit Store, but keep an eye out for it because it is a lot of fun. Remember to drink your oval team. Let's see. It was let slip that I will be on a panel discussion on Circuit Python Day. I wrote here in all likelihood, but I guess it's a done deal. So next up, I'm gonna shift gears for a while and I got some boards from Tindy that have so-called dot clock displays and the ESP32 S3 microcontroller. And I'll have to start by writing Circuit Python board definitions for them. And then I will be studying K matches code to interact with dot clock displays. I have a feeling that I will be starting with a fresh implementation, but starting with that initial kind of knowledge of how to interface with it is gonna be super helpful. And then something else that may or may not happen sometime soon, we've talked internally about making a doom port to the pie camera. It has six buttons, so you might even be able to play it. If you'll recall sometime maybe over the winter, I did a port to the ESP32 S3 feather with built-in TFT and that would only play the demo, play the recorded demos, but this one with the input buttons, we might actually make it playable. So just another thing that would be really fun to do. And that's what I've got going on right now, thanks. All right, thank you, Jeff. And the next step is Catney. Hello. So my list is quite short. Over the last week, I've been working on the Metro RP2040 guide. It is not yet available in the shop, but it is in the shop. So sign up if you're interested in getting that board. I'm just looking at the rest of my list. Yeah, that's all I've been working on. Doing the pinouts pages in the RP2040 guides are very involved because every pin can do 1,000 things and we show not only what the pins can do based on name, but we also have a huge list that shows you based on feature, what which pins fall under each feature. And because this is a new board and exposed way more pins than any other RP2040 we've ever done, there was no copying and pasting to be done. It was all very new. So there was a lot of data sheet digging, a lot of getting the pretty pins diagram in order so I could verify what I was finding in the data sheet. And a lot of forgetting that I had to translate spy TX and spy RX to MISO and MOSI. So hopefully I didn't miss any of those. And that is until that is done, that is what I'll be working on. Okay, thanks, Caddy. All right, next up is maker Melissa. Hello, last week I was working on code for a message board guy that I'm working on and learning how to use the bitmap tools in the process. I added the 1624 and 32 bitmap support to the image load library. And I'm working on improving the, I worked on improving the alpha blend function in Circuit Python Core for better handling darker bitmaps. I'm finishing updating those alpha blend improvements this week and looking into adding compression type three support for true color bitmaps for the image load library. Continue working on the code for the message board and finish up my Circuit Python PR for the Arduino Nano ESP32. And that's it. Okay, thank you, Melissa. And finally, we have Scott. Hello, okay. So I made libraries for the USB host descriptors, which is a very basic library just meant to help understand the descriptor part of USB. And then I also made a mass storage library that allows you to mount a USB drive into Circuit Python, which was pretty neat. I need to update tiny USB today probably because TAC added support for port reset. The USB host right now is at super resilient across the reloads because you might be in the middle of a transaction. So hopefully by resetting USB devices across reloads will actually make it more reliable. I'm gonna plant pair with Dan on the MicroPy thumbbridge and the IDF 5.1 update. And then what I'm actually working on right now is I'm working on adding black magic support for the IMX RT-1011, which supports the 1060 just fine. And I was like, oh, this is great. And then I moved it over to the 1011 and it didn't work. So it's open source. So I'm able to dig in. And I think it's a pretty simple fix. And I'm right to the point where I can determine that that's actually the case. So I'm working on that. And for anybody who in the future makes an ASIC chip, make sure there's a register people can read to know what chip they're actually talking to. Because the IMX RTs don't tell you the way that even some NXP code does it is they literally just read like part of the ROM code and it changes based on like the build that they did. So it's a little silly, but I've got my box of boards in my lap and I'm gonna run through it and make sure that that works decently well. Okay. That's what I meant. Is that it, Scott? Yeah. Okay. All right, thank you. All right. So that's it for status reports. And the next section is in the weeds where we have a longer discussion of the things that people are proposing or have questions about or just want some input on. So I will, let me take a time stamp for what I just said. And Dexter has something they'd like to talk about. So why don't you just go ahead? If you want to have audio, Dexter, go ahead. Do you want to speak or do you want me to read it? Oh, no audio. Okay. So I will read, Dexter says, what if we set up a quote community project, something everyone could build using in stock products? It would need to build materials and instructions. These could be on GitHub. Maybe we could build a useful gadget with a screen and some keyboard switches. So if I understand Dexter, you're saying like, the kind of project that is on learn, you would propose that that be done in kind of by several people or by a bunch of people at once. And everyone might contribute toward this. Is that what you're interested in saying? And I'll look for it, wait for a text from you. Yeah, Dexter says, let's build something together. So one thing I might say is that it's not for shared stuff right now, but anyone who's registered on as an Adafruit.com user can, there are things called user pages or playground pages in which they can write something that looks like a guide page. It's kind of a simplified version of the same content management system that we use to write guides. Now there's no way to share access to that right now, but the ultimate form of this project could be there rather than in GitHub or it could be in GitHub if it must be more collaborative or it could be a Google doc or something like that. And as David said, you can make something that is sufficiently interesting, but can also just be turned into a learn guide. So this sounds like an interesting idea. Dexter, I assume you want to take the ball and coordinate this. Do you have anything else that you might say about this or would you like to just maybe open a some shared either GitHub or a Google doc or something and have people start contributing to it. And maybe there could be a separate meeting or just an exchange in chat after this about what this project might be. And Dexter says, let's talk about it more on CircuitPython Day. That sounds like a very interesting idea. If you'd like to host something, we could have a GitHub, I mean a Discord audio or video meetup about that on CircuitPython Day and coordinate it with the time or the other things. So we could create a temporary channel as David says. Does anybody else have any contributions they'd like to say out loud? All right. I don't hear that, but sounds good. So let's plan on something. It's only in 11 days, so let's plan on something. And you can, as you said, you can write to CircuitPythonDay at Adafruit.com and propose something and we'll find a schedule slot for it and say what your own constraints are about when it could be and what you want the form of it to be. Okay, great, sounds great. All right, if nobody else has anything else, for in the weeds, I'll wrap up the meeting. Let me take a timestamp for that. This has been the CircuitPython Weekly for Monday, August 7th, 2023. Thank you to everyone who participated. If you want to support Adafruit and CircuitPython and those of us that work on CircuitPython, consider purchasing things from the Adafruit shop at Adafruit.com. The video of this meeting will be released on YouTube at YouTube.com slash Adafruit and the podcast will be available on major podcast services. The meeting will also be featured in the Python for Microcontrollers newsletter. Visit AdafruitDaily.com to subscribe. Next week, the next meeting will be held next Monday as usual at 2 p.m. US Eastern time at 11 a.m. US Pacific time. As we mentioned, this meeting is held in Adafruit Discord, which you can join by going to adafru.it slash discord. And there's a link there. You can click to join the Discord. And to be notified about the meeting and any changes to the time or day, you can ask to be added to the AdSign CircuitPythonista's role on Discord. So we'll see everybody next week. Thank you for attending and contributing. And I will stop recording.