 Alright, hello everyone. This is the CircuitPython Weekly Meeting for February the 7th, 2022. This is the time of the week where we get together to talk about all things CircuitPython. My name is Tim, and I am sponsored by Adafruit to work on CircuitPython. CircuitPython is a version of Python that's designed to run on tiny computers called microcontrollers. CircuitPython development is primarily funded by Adafruit, so if you want to support them and CircuitPython, consider purchasing hardware from Adafruit.com. The meeting is hosted on the Adafruit Discord server. You can join any time by going to adafruit.com. We hold the meeting in the CircuitPython Dev text channel as well as the CircuitPython voice channel. The meeting typically happens on Mondays at 2 p.m. Eastern, 11 a.m. Pacific, except when it coincides with the U.S. holiday. In the note stock, there is a link to a calendar that you can view online or add to your favorite calendar app. We'll also send out notifications for the upcoming meetings via Discord. If you would like to receive those notifications, ask us to add you to the CircuitPythonista's Discord role. There is a note stock that accompanies the meeting and recording. The notes document contains timestamps to go along with the video, so you can use the doc to view parts that interest you most. The meeting tends to run 60 to 90 minutes, so this gives you the option to skip around. After each meeting, we post a link for the next meeting's notes documents to the CircuitPython Dev channel in the Discord. Check out the pinned messages to find the latest note stock so you can add your notes for the following meeting. You wish to participate, but cannot attend. You can leave hug reports and status updates in the document for us to read for you during the meeting. The meeting will be held in five parts. The first part is community news. This will be a look at all things CircuitPython and Python on hardware in the community, and it's a preview of the lovely Python on microcontrollers newsletter, which comes out typically on Tuesdays. The second part is the state of CircuitPython, the libraries in Blinka. This is a statistical overview of the entire project. It's a chance to look at the project by the numbers and separate it out from what specifically we're all up to. The next part is hug reports. Hug reports is an opportunity to highlight the good things that folks are doing. Take time to recognize the awesome folks in our community. The fourth part is status updates. Status updates is an opportunity to sync up on what we've been up to. Take a few minutes to talk about what you've been doing in the last week since the previous meeting and what you'll be up to in the next week until the next meeting. The fifth and final part is in the weeds. This is an opportunity for more long-form discussions. These discussions can come out of status updates or be identified ahead of time as something that would be too long for status updates. That covers how the meeting will go. With that, we will get going on community news. I will take first timestamp. Let me get scrolled up here a little bit. We've got a couple of items from community news this week. The first one being the Raspberry Pi OS 64-bit is now out of beta. Over the past year Raspberry Pi has been trialing a beta of the Raspberry Pi OS 64-bit and last week it finally came out of beta. There is a link there to raspberrypi.com if you want to learn more about that. Next up, our own Adafruit Discord channel has reached 33,000 members. The Adafruit Discord community, where we do all of our Python development in the open, has reached over 33,000 humans this week. So thank you to everyone who has joined. Adafruit Believes Discord offers a unique way for Python on hardware folks to connect. You can join today at adafru.it-discord. See the announcement post with a chart of the server growth and that is posted on the Adafruit blog. Next up is a CircuitPython pull request, which was added recently by Kmatch. This gives us the ability, excuse me, it exposes the CircuitPython's REPL's display group elements and allows for relocation of the REPL in the serial terminal as well as opening up possibilities for things like split screens without breaking the existing display IO structure. So this I think is something I'm very excited about. This I think will be a very neat way to help folks learn about the basics of display IO. So check out a link there to Twitter and there is also a link to the specific PR on GitHub. And this is also merged in now, so if you're interested in that you can try it out yourself. Next up is Piku. This is a small command line utility for managing CircuitPython projects. With Piku you can make creating CircuitPython projects, installing packages, deploying and connecting to a CircuitPython device easy from the command line. There's links here to the Adafruit forms as well as the official listing on PyPy. Next up is the CircuitPython 2020 wrap ups. Thank you to everyone who wrote CircuitPython 2022 posts. We had 24 folks who posted that were in the wrap up. So thank you to all of the folks who posted. Thank you for all of your different ideas. I hope that folks collaborate to make these ideas a reality. And thank you to those whose ideas have been the guiding principles over the years. We would not be here without you. As Katani pointed out in her CircuitPython 2022 post, don't hesitate to let us know what you'd like to see from CircuitPython and the community throughout this year. Feel free to give us more ideas on the Adafruit Discord, Adafruit forums or the GitHub issues section for the CircuitPython project. And again, there's a link there to the Adafruit blog to read that wrap up post. A couple more here from around the web. We have a wordal game for the clue. So we are expecting a number of these ports of this new wordal game that has gained popularity. It's a New York Times word based game. And we have one project this week on the clue, which was ported over by Michael LeCocque. And it is it runs on the clue on CircuitPython 7 and it can actually run both with and without a keyboard. So that's very interesting. Another one we have here are a couple KB2040 powered keyboards. There are the first two are concepts that minimize finger movement. And these run Circuit Python, it has some five way switches instead of traditional key switches. I thought that was very interesting. And the other one is a split keyboard, which also uses the Adafruit KB2040 microcontroller. And this one runs the PRK firmware based on PicoRuby. And there are links to those from Reddit and Twitter, respectively. So that wraps up community news. I will mention all of these items and many more came from the Circuit Python weekly newsletter. This is a community run newsletter emailed out every Tuesday. The complete archives are available online at AdafruitDaily.com. It highlights the latest Python on hardware related news from around the web, including Circuit Python, Python and MicroPython developments. To contribute your own news or projects, edit this week's draft on GitHub. There is a link in the docs to there. So you can create a PR to that repository. You could also tag a tweet with hashtag CircuitPython on Twitter, or you can email cpnews at Adafruit.com. And to wrap it up, I will just mention thank you to Ann, who generally is the one writing and running the newsletter, keeping everything running and giving us a steady stream of great things to look at on Tuesday morning. So thank you to Ann for that. Next up is the state of Circuit Python, the libraries and Blinka. So I will read the overall state and then we'll dive into the core and the libraries and Blinka. So let me take a timestamp here and I'll read overall. So this week, overall, we had 49 pull requests merged by 22 authors, a couple of names that I don't recognize as being regular authors were Fabaf, Escauchee, Stone Hippo, Andy Piper, Life Imaging Services, BRT Chip, Chuan Yin, I'm going to guess on the pronunciation, I may be incorrect on the last one there, and Walsh HBP, or Walsh BP I should say. So thank you to those folks who again, I don't think they are regular contributors or if they are they haven't contributed in a little while. And of course, thank you to everyone else who contributed as well. We also had eight reviewers this week. So thank you to them. And we had 30 closed issues by 11 people and 25 issues were opened by 19 people. So I will pass it over to Scott to tell us about the core. Hello, thank you, Tim. So the stats for the core, we had 21 pull requests merged from 16 different authors. I won't highlight the new folks since Tim did that already. So thank you to everybody who authored stuff, we had three reviewers. So as always remember that reviewers tend to be the bottleneck for bringing in more authors. So if you're interested in doing reviewing for the core, please reach out to us. We'd be happy to get folks ramped up for that. Issues wise, or we have eight open pull requests. So we're actually doing pretty good keeping up. But three of those are over 100 days old. Issues wise, we had 14 closed issues by six people and 11 opens by 10 people. So we're net down three, which is good. So thank you to all those folks that were involved for a total of 498 issues. So we're up right about 500. So we are slowly increasing. It's not the end of the world. The way that we keep track of prioritization is through milestones. And we have eight open issues for 8.0, 23 open for 7xx, which are issues that we should probably fix sooner rather than later. And then we have 11 open issues for 720, which are things that we think we should do by 7.2. Although we should probably do a pass for this before 7.2. There's possible that we don't need all of that. And then we have 433 open issues. So that's where we are on issues and the milestones. And that's it for the core. Alright, thanks, Scott. And now I will turn it over to Catney to tell us about the libraries. Oh my gosh, I can click the right button. So this section applies to all of the Adafruit Circuit Python libraries, which is everything that starts with Adafruit underscore circuit Python underscore as well as a couple of extras. We had over the course of last week, we had 28 pull requests merged by 10 different authors and eight reviewers of those pull requests merged, three of them were over two weeks old, one of them was 255 days. So I'm very excited to see that we're still getting through those older PRs. And the rest were zero or one. So it's excellent to see that we're keeping up. And that's leaving us with 21 open pull requests, which is definitely the lowest that's been on a long time. We had 16 closed issues by seven people and 13 opened by 10 people, leaving us with 635 open issues. It's good to see the number of people that have been involved in opening and closing these issues. The number of issues open and closed is in my opinion less important than the number of people who have been involved. It's great to see so many people. 227 of those issues are good first issues. If you're looking to contribute 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'd like to get started reviewing, check out the open pull requests. If you have the hardware tested, if you don't take a look at the code, let us know what you think that always helps. If you're interested in contributing code or documentation, check out the issues. If you're new to everything, search for good first issue. We have a guide on contributing to Circuit Python using Git and GitHub. We're always available on Discord to help you out. We want to see you be able to contribute in a way that works for you. In terms of library updates in the last 7 days, we had one new library, Circuit Python HTTP server and a massive list of updated libraries from a recent patch. I'm fairly sure literally every library was on the list and that's why it's not listed here. I'm not going to read that off. There is a link to the report, though, if you're interested in seeing a giant list of libraries. And that's where we are with the libraries. Alright, thanks, Kutney. And now I will turn it over to Melissa to tell us about Blinka. Hello, for this week, for Blinka, we had no pull requests merged. There are currently five open pull requests amongst all the repositories. There were zero closed issues. And there was one open by one person. There are currently 70 open issues. And there were 17187 pie wheels downloads in the last month. And we are currently supporting 87 boards. And that's it. Alright, thanks, Melissa. So that rounds out the state of Circuit Python libraries and Blinka. And next up, we will have the hug reports section. Our reports is a chance for us to highlight the folks in the Circuit Python community and beyond for doing awesome things. As mentioned, this section is held as a round robin where I will start and then we'll go down the list alphabetically. We no longer circle back to the top. So we'll just go down that list. Again, this is in the note stock. If you're text only or you're missing the meeting, but you do have hug reports in the notes document, then I'll read them off as we get to your time in the list. So I will start it out for hug reports. Let me timestamp it. So this week, I have hug reports for Scott who discovered and shared a direct link for the James Webb telescope data straight from NASA. Originally, we had third party service that was scraping that data and returning it back to us. And now we have a link that we hope to be able to just pull the data from directly. So thank you to Scott. Thank you to Katny, who helped me get prepared to run this meeting. So huge thanks for that probably would not be here today without Katny's help. So thank you there to near doc and anecdata who both helped troubleshoot an issue fetching data from that NASA URL. Appreciate the help from both of those folks. And then my last time report is for a match who worked on a way to split the screen between serial and repel the serial repel and the output from display. That way we can have both showing, which I again think is a really super neat functionality. So thank you to a match. And with that, I will pass it over to Dan. Okay, thank you, Tim. Thanks to you for running your first meeting. Thanks to Dave Putz, who tracked down a PIO issue on RP 2040 that was had to do with order of arguments that was important to fix. Thanks to life imaging services, who submitted a really nice first PR, which is adding CRC CRC 32 checksum to binasky without having to drag in Zlib, which was where the implementation was originally, but we just factored out that part of it. And now we have this other nice checksum thing added. And thanks to Naradoc, who went through all the boards and added stem board dot stem I to see to all the boards that have a stem of the connector. That's really nice. And that's going to be a great thing to get into the next version of circuit Python. Okay. All right. Thanks, Dan. Next up then is going to be Jeff. All right. Hello. Well, I hope to you, for me guy for being the meeting host and generally stepping up on all things circuit Python. I hope you had fun saying sponsored by Adafruit in the intro, because that was that's exciting. Also, to a GitHub user, JWF McClain for bringing up a really interesting bug report about timekeeping on Sanity 51 to Noyan Pedro for the 3D models of Adafruit products. One came in handy this weekend. To Katni, I have a hug report for providing some slides and outlines for intro to circuit Python presentations. And of course, a group hug. All right. Thanks, Jeff. Next up is Jerry. Hi, group hug for me. Excellent. Thanks, Jerry. Next up is Katni. All right. So first up, I have a hug report for Carter and Neridoc for helping me get enumerate going in two examples I was writing when Pilant complained. I've not worked with enumerate previously and I was in a bit of a time crunch. So I didn't have time to put in the effort to actually go through learning it myself. And the two of them helped me get it going and actually explained it in a way that I understood. So bonus there. To Neridoc for adding the Stema underscore I squared C and Stema underscore I squared C1 to all applicable boards in circuit Python. This is super amazing. At the moment, we have to have commented out code for every single board that has SCL1 and SDA1 on the StemaQT connector. And this will make it so we won't have a whole list of boards in all the examples. It'll just be one or the other. And Stema I squared C will work on all boards that have a connector even though it's the same as the pins. So that maps to the same thing. But it's still it's good for consistency because then if you're using the Stema connector it's Stema. So hopefully that will clarify a lot of things for people. To you, Tim, for running the meeting for the first time congratulations and thank you very much. To TechTrick for figuring out how to automate fixing a library readme blender that was totally my fault. I had one of our people add another documentation section not realizing we had a documentation section already so it has different stuff under it and the fix is to move that stuff under the current documentation header so we're not duplicating things. But it was not something that we could do with our current patch system because it involved moving a whole chunk of text that into a you know section that was already existing. Anyway TechTrick figured out how to automate it so I'm really looking forward to being able to fix that and not waste a bunch of Eva's time. And a group hug. Alright, thanks Kenny. Next up is Kmatch. Thanks Tim. Thanks to you for the weekend stream on a win at player especially excited when your refactor basically worked the first time so that was that was exciting. Thanks Scott for the code suggestions and FOMA guy for your encouragement and also the stream last week on the split screen repel. Thanks on the forum discord forums to ed keys and mad badger for for helping me identify the specs on a tft display and lastly to mark gambler for heads up on a possibility of using keyboard input library that's existing as a first step towards converting touchscreen touches to gestures. Thanks. Thanks Kmatch. Next up is maker Melissa. I want to give a hug report to you from the guy for running your first meeting and a group hug different else. Alright, thank you Melissa and thanks to everyone who has given me her reports today. I appreciate appreciate all of you. Next up we have mark gambler who is missing the meeting today so I will read them. So their first target report is for Scott for finishing all the reviews of the IS 31 PR that's finally done and pointing me pointing me to getting excuse me pointing to some getting to getting started information for debugging with GDB. Next up mark has a hug for catney for helping set up to write some instructions on how to use it helping me set up write some instructions. I'm not sure I guess what the help them how to use what but thank you nonetheless from mark to catney and then a hug report they have the last one here is for me for hosting the meeting so thank you for that as well mark. And next up I will pass it over to Tammy makes things. Thanks so I have a hug report this week for the the PQ tool that we talked about earlier. It's really helping me to solve some of the challenges I've had with my own development workflow. I have a hug report for the shipping and logistics folks at Adafruit for getting some stuff out to me amazingly quickly this week in spite of the absolutely banana crackers weather that's happening on the east coast. And then a hug to everybody for being amazing and making community more than just an empty platitude in the circuit python community. Yeah for sure thank you to me. Next up we have Scott. Hello to echo the the chorus of thank yous thank you for the guy for joining the the meeting host rotation. It's particularly helpful to me considering that I will be out for a while this year. So it's nice to have another person in the rotation. So thank you for for hopping on board. And thank you to catney for getting uh phoma guy all ramped up. It's uh super helpful so thank you catney as well. And lastly a hug report to scooter for digging into circuit python on the stm-32 they already updated the library references and stuff so that was really helpful. So thank you scooter. All right thanks Scott. And next up I will read the notes for tech trick. Tech trick has a hug report. Thank you to foamy guy and near doc for help helping debug an issue with the ht-16k-22 pull request that was allowing the use of custom characters on seven segment displays. And tech trick also has a group hug for everyone. So thank you to them. And next up is v923z zoltan. Thanks Tim. So first of all I would like to thank Dan for his very generous help regarding an automated firmware compilation system. This is something I have been trying to set up for micro python and micro lab and asked him whether he would would care to share his insights and I was hoping for something like five minutes of discussion time and he gave me 25 so many thanks for that. And second I would like to thank Jeff for reviewing micro lab code and catching a number of silly errors or perhaps not silly errors but in any case they have been code. Thanks for that Jeff. All right thank you zoltan and thank you everyone else for reading hug reports today. That is it brings us to the end of the hug report section so next up will be status updates and as a reminder status updates this is our time to sync up on what we're doing. The section is also held as around Robin where I will start and we'll go through the list alphabetically again. When I call on you take a couple of minutes talk about what you've been doing since the last meeting and what you will be doing until the next meeting. This is also an opportunity to provide tips and tricks that are relevant to what people are working on and if a discussion becomes too much for status updates then we can move it down to end the weeds with that I will get started. So my status updates this past week I finished up the bulk of the work on the functionality of the Winamp project code. Both the the code that runs on circuit python as well as some code that runs in CPython that converts the existing Winamp themes over to be the right size and exports a couple of the colors and things for us to use on the circuit python side. I will be working on the guide for that this week. I have been continuing testing and reviewing the PRs. One of the ones that I found particularly interesting this week was my first time using a camera with circuit python. It's a VC0706 camera that has a ur interface that talks back and forth to the circuit python device and there was a PR that was created to enable motion sensing that I guess is built into that camera. It had a way for you to check whether or not it sensed motion between the previous frame and the current one. So that was a neat addition and I kind of got up to speed using cameras this week in order to test it out. I just streamed some basics of display IO on Thursday evening. If folks are interested there's a VOD out there on YouTube and in particular I was looking at the new split screen functionality that allows us to show the REPL and display IO at the same time. So if folks are interested in seeing what that's all about there's video out there. Some other things that I was doing in the previous week was absorbing everything needed to run this meeting. I must again gone through the script you know a half a dozen times or so and got everything trial runs and stuff so that's been something I've been doing this week and then something that I do hope to do coming up for the next week is troubleshoot an SSL error that we are getting when we try to fetch data from that nasa URL for the web telescope. So I have a note in the weeds to maybe discuss that a little further if anyone is up on SSL stuff. But that rounds out my status updates so I will pass it over to Dan next. Okay thank you. So I fixed a couple of bugs. There were some I2C problems on ESP32S2 that were solved by using an internal routine in the ESPIDF and that routine we really needed to be able to call when we didn't do it did a combined write read I2C transaction we need to be able to call that wrapper routine so we made a new comment halve routine to do that and I put that in all the relevant I2C implementations and did a lot of testing like I built a whole bunch of things that I never built before like Spresence or that I hadn't built for a long time and tested it on a whole bunch of platforms. There was a PR that had broken the SAMD build and I fixed that. That's both of those were last week. I worked on a web server library recently that runs on the ESP32S2. We had one that ran on the airlift breakout and airlift boards but not on the ESP32S2. Now there's a simple new library called Adafruit Circuit Python HTTP server. It's just in version 0.1.0. You can find it in GitHub. Try it out and if you have some suggestions make some suggestions and eventually will be in the bundle but it's not in the bundle right now. It also works in C Python so that you could easily transfer some code back and forth. In line with that I'm starting to look at how to make an async web client library. After looking at a bunch of these libraries I think I'm going to use the ASKS library which is kind of a joke on the request library which is a very, it's asked to be a version of request that does things in an async way and I'll start with that and see how it works out. Probably I will also go back and make the HTTP server library have an async capability as well and then there's still plenty of bugs to fix for the various 7.x releases. Also I don't have written this down but I'll add it is that it would be nice to make another alpha release soon like maybe this week with considering all the changes that we have so far. Okay that's it. Alright, thanks Dan. Next up is Jeff. Hello again. So last week Floppy's and PIO somehow took all week and it still isn't wrapped up. The state of the code is that reading with the PIO peripheral that is reading the data off of Floppy disk. It's working great in Arduino but it still needs tidying and then reintegration with the code that more has been working on for the m4 microcontrollers and one reason that that took all week is that I also spent a lot of time on a silly 3D printing project that I will be bringing to show and tell. It's not original but I think my version of this 3D printed project brings something a little different and more than the original so I'll have fun showing that off. This week this is a question mark at the end really wrapping up RP2040, Floppy reading and writing with PIO this week. I hope so and in coming weeks I have been asked to speak at an upcoming hybrid event hosted by the Dublin Linux users group with details to come. So I don't know how y'all could attend but I think there's a sign up and I'll share that info when I get it. All right, thanks Jeff. Next up is Jerry. Yeah, I hope your part involves going to Dublin to do it. That'd be fun. I responded to a question that came from the forum and this is another example of really cool things that come out of forum questions. So somebody was trying to use the RFM9x library to communicate with the Arduino Lora library and we're asking if it could work. My first reaction was yeah, I'd never even heard of the Arduino Lora library. I've always used Radiohead so I went and took a look at it and it turns out it actually if you just do a basic there simple test it works great. The problem is that library doesn't use the Radiohead headers that we use on the Circuit Python side but it just sends a string of bytes so if you build a header in the beginning of your packet it works fine. They were trying to transmit to a Raspberry Pi running the Circuit Python library and it all worked great with the default settings. The problem was this user wanted to tweak some of the settings to change the spreading factor on the library to try and increase their throughput and things fell apart. It didn't work at all and so I started looking into it more and realized that almost all of the use that we do in Circuit Python with the libraries we maybe had used the same spreading factor spreading factor seven it's the defaults used for all the standard communication and it works very nicely. A couple of other spreading factors 8, 9, 10 worked okay too but 6, 11, and 12 which are really more special cases didn't work at all and looking at the code it probably makes sense that they don't work because there's a lot of special handling you have to do for those spreading factors that isn't being done in our code in the Circuit Python code. That definitely needs to be fixed. Problem was I couldn't make it work even when I thought I was fixing it so there's a lot of understanding to dig into the data sheets and try and understand it so I'll be working on that as time allows. Fortunately it seems to be a pretty seldom come across problem but it certainly is a problem and so if anyone else come across that or want to dive in let me know or just dive in and see if you can understand any of it. Then I did try the new 64-bit REST BOS and it's off to a good start and trying some things with it and I tried Blinka and the first normal Blinka test worked fine but then at Maker Melissa's suggestion I tried Pulse in and it did not work because it couldn't find a particular library it needed. It turns out that library actually exists it's actually in the Blinka repository just needs to be copied to the right place and I thought it was going to be a real simple little PR but I couldn't figure out how to actually do that how to set it up for a PR so there's an issue out there for it if somebody can take a look at it and figure out hopefully it's a simple thing but there's just a couple of little steps that need to be done to make it work copy this file over there and set its permissions properly but it does work and I was able to actually run the DHT the evil DHT-22 actually worked fine on the 64-bit Raspberry Pi 4 then last thing there's I had this board called the Maker Pi Pico which is really a nice little development platform a little platform for playing with Raspberry Pi Picos and one of the ports it has on it is a little slot to stick an ESP-01S which is an ESP-80266 with an AT firmware on it and so I had this sort of hadn't played with that in a long time and I plugged one in and tried it and long ago it actually works so it's kind of fun the ESP-80 control library is one that hasn't gotten a lot of attention and probably will not get more attention it's really not supported but it does work and it's kind of fun to play with I do I really do like these Maker Pi Pico boards that's it thank you Jerry next up we will send it over to Katni hello so last week I finished up my circuit Python 2022 post got that published published the arcade QT guide that's a board that's been out for a bit but we hadn't gotten to the guide yet but folks have been asking for the examples to go with it because it's a little bit complicated of a board it runs the AT Tiny 817 using seesaw and so you have to know what pins things are on and this guide obviously tells you everything you need to know ran into issues with Arduino on the arcade QT which turned into a lot of troubleshooting it turns out it may do clock stretching which makes it not work on certain boards the only boards I had with me are a little bit weird in Arduino but it also had some issues on SAMD boards so I need next to try it on an actual like AVR board and see where that goes added content for the upcoming circuitpython.org slash start that's going to be a link on circuitpython.org obviously that has some real basic getting started stuff that links to guides links to other parts of circuitpython.org but basically sums up on some level the welcome to circuit Python guide plus some extras in very short order so folks can find their way around things without having to know where to look and then started the STEMMQT rev update to the guide for the HT16K337 segment LED backpack we updated that board to have STEMMQT connectors on it and so that guide needs updating so this week the first thing I'm going to be doing is updating the ADXL345 board files on GitHub and in the guide the board files that are on there are incorrect and so Lamor put together the current files and I need to update those per a user request need to as I said make sure the arcade QT plays nice with the metro and also see if I can replicate the issues I had on SAMD because apparently Lamor ran into some issues with the testers in the beginning and she just thought it was being flaky and it may actually not be a flaky issue it may be a SAMD issue continue on the STEMMQT rev update for the LED backpack guide create some learn groups in the late day for it learn system I've talked about this for a couple weeks but it's not top priority so it's still on my list basically there are things called groups that the developers are now making far more easy to get to through search so basically making them more user visible and so what I can do is put together a welcome to circuit Python group for example and then on you know discord for example if if someone is giving or giving support to someone who's new to circuit Python you don't have to link to five guides you'll be able to link to the group and the group will have all of them in there and I think that'll be super useful I still need to get content up on circuit python to org slash trademarks there is a QT guide update for the mcp 4725 there's a new adxl 375 that needs a new guide I still need to do the dot star status led template for and who's been going through all of the older guides and putting in all the templates which is super helpful thank you for that I need to do the async io template and then possibly get my readme blender fixed up with tech tricks script it depends on Eva's got is working on guides right now and those are the priorities so as soon as those guides are done hopefully we can get that script run and get the readme's updated that's what I've got all righty thank you Ketny next up is Kmatch yeah thanks Tim okay so last week I finalized the PR as mentioned above about resizing the REPL and placing it where you want it to go also found a minor issue in word ramping in the display text library and submitted a proposal to fix that next couple items are related to a sort of personal target to make a tablet that can run circuit python and I came across a rugged conference room scheduler touch display which is mounted to a wall outside of a room for seeing who's got the room available I got a couple of those and wanted to see if those might be good hackable units to do something like this and I learned a lot about tfts in the process and some challenges about driving them so there's a tear down with a link there unfortunately this one wasn't a good candidate to reuse other than the touch screen and so now I'm playing with that and that's related to my work this week first off this week I plan to submit library for scrolling text box with box widget where if you have a lot of text and you need to scroll up and down to read it you can do that and then the second one is is to experiment further with the touch screen responses and how to visualize touches and gestures with the hope of converting individual touch points into gestures like swipe or or rotate or zoom and sort of at a fork in the road whether I continue on with the existing display I sorry Arduino library or do I just go ahead and buckle down and make a start at a library for that that touch panel and circuit Python so that's what's going on for this week all right thanks Kimmich next up is maker Melissa hello see last week I worked on porting little fs to javascript some more continuing on that mostly I was mostly debugging errors at this point and I now have an image being generated which has the files extractable but there's just a couple little things it looks like so this week I'm going to work on finishing those final bugs and I'll also be speaking at the Dublin Linux users group with Jeff and that's it all right thanks Melissa next up is Tammy makes things thanks so last week I as I mentioned earlier I got excited about the the pick you development tool and so I contributed a PR to add Mac OS support to that because there's some things that work a little differently on a Mac I also have been building a little helper script because I have several boards that you I have a an mcp 22 whatever it is that you use with Blinka and I have an FT 232 and I have a Raspberry Pi Pico running the U2 IF whatever that firmware is and I was getting tired of having to keep track of which one I was using and setting environment variables so I'm writing a little helper script that probes the USB bus and automatically sets the right environment variable for whichever board is actually present so I'm trying to finish that up and get it in a place that I can share it I want to look for more opportunities this week to contribute and I'm also still getting all of the bits and pieces together to hopefully do my first Twitch stream either this week or the following week focusing on microcontrollers and CircuitPython and hardware hacking and stuff so that's what I'm working on and that's it all right that's awesome thank you Timmy next up is Scott hello last week thanks to Ketney for getting her CircuitPython 2022 post out I read that and went over over in my deep dive and then also did kind of the wrap up post on the blog besides that I was working on getting the GAT client stuff going so that's Billy where you're talking to another device that has the data that you want so to do that I got service discovery working so you can discover what things it can do I got connecting working so you can initiate the connection from CircuitPython now and I got characteristic buffer working which is what is used in the UART demo so that's what I got going last week over the weekend I switched to a new DIY keyboard of my own which is running a custom CircuitPython code so I'm trying not to get too distracted perfecting that but and thinking about how to set up the plugins and stuff so it's pretty extensible and pretty simple as well this week the last thing I want to do for GAT client is getting packet buffer working which I'm not sure we have a demo for but I should be able to put one together not too not too difficult similar to Echo but with packet buffer so I'll get a PR once I get packet buffer going for GAT client I'll get a PR out for review and then start on dynamic services going on in Nimbl which is probably going to be a bit more of a trick but it's just going to be super helpful to be able to do services so I think it's worth taking a look at so that's my week and probably next week too all righty thanks Scott next up is TechTrick who is missing the meeting today so I will read their notes TechTrick last week worked on a script for fixing library repo readmeas worked on some more missing type annotation PRs TechTrick submitted a PR for making touch pads iterable on the circuit playground library this allows you to de-init them as needed which is a bonus and they also submitted a PR for adding examples on pausing, resuming and cycling LED animations using push buttons this week TechTrick will be working on some let's see additional follow through on other PRs that were merged this past week and TechTrick also will be working on some more type annotations and anything else that is available in the open issues so thank you to TechTrick for those for sure and next up is v923z Thanks Tim so in the past two weeks I have completed the implementation of number of IO utilities in microlapse so this is something that a couple of people have been asking for basically you can you can now write some numerical output on a PC from numpy to a file and then you can put it on a microcontroller and then it can be read and vice versa so you can save measurement data for example into a file and this file can be can be done interpreted by standard numpy utilities I also fixed an incompatibility issue that Jeff pointed out something like half a year ago and unfortunately this is a breaking change the fix I mean so circuit python should probably hold off till version 8.0 but if there is some some bug that requires a speedy fix then we can discuss how we would do that without upsetting the present API so in the in the coming weeks I would like to release version 5.0 which includes these above mentions changes there are a couple of rough edges still and I will try to to clean up the documentation so this is this is mainly for for circuit python purposes but I hope that this is something that can be done till till version 8.0 incidentally I would like to ask what is the time frame for that if anyone could comment we don't have a time frame but we'll probably wait for the next version of micro python because it will probably rev mpy version okay so Damien Damien is currently working on the ability to like run code out of the file system mpy's which is really cool right and would reduce our dependence on on frozen modules so that's definitely of mpy revs and so I think we're kind of thinking that we'll probably do 8.0 around then okay okay great but with that I would like to pass it back to Tim thanks a lot all right yep thank you Zoltan that gets us to the end of status reports so we will round out today's meeting with in the weeds section and so as a reminder in the weeds is an opportunity for more long-form discussions these can either come out of status updates or they could have been identified ahead of time if you do have any in the weeds topics please make sure to add them into the bottom of the notes document go ahead and put your name as well as your topic and we will call folks in the order that they appear in the document and this week I actually have the the first one for in the weeds and so I was basically just put in a call out to see if there's anyone who is knowledgeable about SSL and HTTPS that might be able to help troubleshoot this SSL handshake error that we are getting when we attempt to fetch data from this NASA URL in the note stock I put the URL where we are trying to fetch it from there's also a historical link into discord back to last week when some of us discussed a little bit in the help with CircuitPython channel and it's it's kind of weird the it seems fine on a PC browser everything comes through and nothing looks you know to suspect in the in the header or anything else in the dev tools but for whatever reason on CircuitPython both ESP32 S2 devices as well as ESP32 spy with the airlift connection they both seem to fail in a similar way which ultimately traces back to a SSL handshake error when we add some additional logging into the library so I was just putting that call out to see if there is anybody who is into that SSL world that might have any ideas for troubleshooting so I don't know if you've talked with anecdote already but that's one of the people I probably would ask about okay yeah a little bit anecdote it seems pretty knowledgeable the other person I could think of is Brent actually okay because Brent's done a lot of like certificate management and making sure that like you have the right keys and stuff okay yeah I will I will ask Brent I think I'll scroll back and check out the history but I think anecdote maybe was there they tested some of this for us I think they did the PyPortal test on the ESP32 spy but I'll double check and then Brent's Brent's a good resource task so I will do that and I will mention sounds like David might have ideas too yeah David in the chat mentioned there might be a list of supported crypto could be very restrictive on the server side so I think you mean the algorithm that it is using to encrypted which could be the case I don't know yeah I don't know for sure what they use or what all we support but that's definitely a good a good thing to try to look into to figure out what both of those what we support and what they what they use on the site okay perfect yeah this is how we can I will continue very the blocks the block I wonder oh my guy I wonder if it isn't isn't a block the block you might not have the right block cypher yeah I think that may be that may be what David is suggesting as well I think just yeah different term okay so that that gives me at least another another stone to go and turn and look under so definitely appreciate folks pointing me in the right direction there but unless unless anybody has anything else to add on that one then I think we can go ahead and pass it over to catney for the next one yeah um so this was actually suggested by jeff but I like we keep forgetting about it I assume and I thought about it earlier today went during this meeting we should consider updating the description on the long-term milestone in the core to be something like while these issues are not a priority for ate a fruit we would absolutely love to have the community pick them up the idea being that we should make it clear that they're not like we're not putting off those issues because nobody should do them and if someone wants to pick them up we're happy to help I don't know how we can get that into a concise sentence but if if that's something that we think we want to do I'm happy to try and put something together so I don't know what anybody else thinks about that I think it sounds like a great idea okay I will I will think on that then so yeah so that's that's good enough for that the next thing I have is as I discussed in my circuit python 2022 post I want to see us do a call for input from the community more than once per year I think it'll help keep the community more involved with the evolution of circuit python versus only soliciting input one time per year spreading it out about three times would be about the end of April beginning of May and then I thought we could do one first circuit python day the two the second two don't need to be as involved as this call as in like we don't necessarily need to do you know weekly posts on who's posted what and all of that stuff we can if we want to do a roundup post at the end that's quick and easy and nobody should feel obligated to respond really to any of them including the New Year one but what do people think about those two times ish to just put out to actually be verbal about it because obviously we're happy to take you know input at any time but not everybody knows that I think circuit python day makes a lot of sense and if you think more than that then I would support that too okay my year is fragmented yeah yeah no I know yeah if you for this year you're you're not and you're not necessarily part of this I know but in general do because I mean I know a lot of the folks that are in this meeting are people who responded would you be interested in providing input again either one or two more times per year circuit python day for sure I think would be a great time to do it but as long as folks are interested in that that's something that I would um be happy to handle well I was kind of the one who mentioned this to catney first so I think it's a good idea I won't necessarily have different ideas in April but it's more about wanting to hear other people's ideas right and putting up the ask and seeing what comes out of the woodwork and then hopefully encouraging the community to work on those things because you know the other thing is we've all got plenty on our plates that is true and what I see happening is the more that we add to circuit python which we do very like we've been doing a lot more a lot more quickly I think it'll spark more ideas from other folks like that's that's kind of what I see like right now I don't think I would have new ideas in April either but you know based on what we add to circuit python between now and then I may say oh you know hey that sparked this idea that I had and I'm hoping that's kind of what will come out of this so okay sounds good I will pick if I want to do it again in April or May I'll pick a day for that and then definitely we'll do circuit python day which we because we do a bunch of leading up to that anyway so just adding in hey we're looking for another call for input will be rather easy to do and again I will deal with that okay that's what I've got thank you Kenny yeah thank you Kenny for sure and that is our last topic for in the weeds so we will do a wrap-up and then head off for the day so thank you to everyone that participated or anyone listening or watching after the fact this has been the circuit python weekly meeting for February the 7th 2022 thank you again to everyone who participated if you want to support Adafruit and circuit python and those of us that work on circuit python please consider purchasing hardware 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 made available on major podcast services it will also be featured in the python on microcontrollers newsletter visit adafruitdaily.com to subscribe the next meeting will be held Monday as usual next week the 14th is at the normal time 2 p.m eastern 7 a.m pacific however it is worth noting the following week I believe is going to be on a Tuesday so not next week but the week after I believe we're bumping to the Tuesday we hope to see everybody next Monday for the normally scheduled meeting and then the following Tuesday for that week this meeting is held on the Adafruit discord which you can join by going to adafru.it slash discord to be notified about the meeting and any changes to the time or day you can ask to be added to the circuit python east as role on discord and that is going to be at first day we hope to see you all again next week and thank you again to everyone thanks everyone all right