Created
February 25, 2024 22:36
-
-
Save clholgat/e164e355ddc8ad23748753e08cec780f to your computer and use it in GitHub Desktop.
AYAB 1.0 Developer meeting notes 2/25/24
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Agenda | |
- GSOC | |
- New hardware | |
- Pricing new hardware | |
- Getting started documentation | |
- Governance documentation | |
- Web | |
- 1.0 relase remaining issues | |
# Notes | |
- GSOC | |
- Google said no | |
- Projects are still on the table | |
- Use all of the resources available (Carson used to work at Google) | |
- Identified documentation gaps | |
- Onboarding documentation is missing | |
- Going to try again next year | |
- Website needs updates | |
- New hardware | |
- Showed up today | |
- Looks good but small changes need to be made. Pull up resistors are missing. Boots. JTAG is there. | |
- Bringup is starting | |
- Repo for test firmware toggling things and checking encoder | |
- Put the test code in the ayab project | |
- Budget is good 10 peices $30 each, 50 should be $20 each | |
- Victoria posted a spreadsheet about pricing | |
- Whoever is selling it picks the price | |
- eKnitter is $200 | |
- hardware is product or project? | |
- Seller will ultimately determine the price | |
- Seller will be on the hook for support | |
- Craftwork will handle distribution - we need to talk to them | |
- Could go directly to the manufacturer if you want. Files checked into github. Will be able to generate production files from command line | |
- Could be able to produce as part of builds | |
- Could populate it yourself except for maybe the ESP32 but pads are under the chip | |
- We will probably have to handle support requests with unknown board manufacturer. Probably want some test suite to validate boards. | |
- Second meeting about pricing. Suggestion for Craftwork and then go from there. | |
- Need to start a list of who has what machine. | |
- Funding for these things? | |
- Governance documentation | |
- GSOC asked about this. Tom said self organized with vague leadership roles. | |
- Need to handle money at some point. Oversite of money handling. | |
- Needs documentation | |
- Organizing body to deal with money | |
- 1.0 release | |
- 930 mispatterning on the lace carriage | |
- 1.0 address regressions | |
- mac build is still broken on apple silicon. Matei offered to help test. | |
- fbs doesn't really work. Sam has been patching. | |
- Timebox this and see about pulling out fbs. | |
- Not a whole lot of fbs work to do | |
- Sam has gotten a build working, needs to document and get things sorted out | |
- Virtual deadline forced by the hardware | |
- Will need more abstraction, not too much work | |
- Set a deadline for 1.0 release - End of Q2 which is end of June | |
- Beta some time before that on Facebook, even if just Windows and Linux | |
- Not pulling in the big refactor | |
- No ESP32 support | |
- Will need some tooling for flashing the new board, probably from web | |
- Next release build? Last one was end of December. | |
- We should cut a firmware release and then a desktop to go with it. Carson TODO | |
- Web | |
- Tom started a prototype, buttons, not a whole lot of functionality | |
- Should go into the organization's git repos | |
- Going to schedule some thinking and planning after the 1.0 meeting. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment