Today, 22 volunteers assembled 3590 badge kits (minus the badge) in under 3 hours. It was epic to see such a self-optimizing machine at work once again, and we are super grateful to everyone who came to help out! :) 
We now have 3590 of these kits, ready to be completed with a badge. We'll be doing that next Saturday, and we can really use more hands! Sign up at wiki.mch2022.org/Team:Badge/Swe… or in our DMs :)
On this last leg of our pre-event adventure, we can also use your help in the software department! 🧵
We want to improve the UI of our hatchery.badge.team. Do you know Laravel or can you tell us how we can improve it? Please respond below ;)
We would like to have some useful apps like an event schedule and a weather app available on day 1. You can make this in whatever language/framework you want (Arduino, MicroPython/BadgePython, ESP-IDF are supported). This is your chance to make a really popular app :D
We also have plenty of firmware to-do's or nice-to-haves, but because of our time frame we may not have time to give you an extensive introduction or instruction for that. If you want to help, please check out github.com/orgs/badgeteam… and see if you can make sense of it :)
We would love to have support for our FPGA-featuring badge in Icestudio (icestudio.io), an open-source visual Verilog editor. We need our existing Verilog blocks to be wrapped as Icestudio blocks, a board config for our badge, and some examples to get people started.
Finally, we need more and better documentation, both Getting Started-style and API references. If you know how to write how-to's or if you're good at reading code and documenting API's, contact us!
For a full overview of all of the above and more, see github.com/orgs/badgeteam…
• • •
Missing some Tweet in this thread? You can try to
force a refresh
