AYAB developer meeting notes 6/18/23

gistfile1.txt

# Agenda
- Existing bugs
- eKnitter
- Next version of the hardware
- First mailing list post
- Community Server conversion

# Existing bugs
- Need to cut another release
- One major bug selecting the wrong line. Tom is looking at it. Happening with the knit carriage. Might only be working for the garter carraige but not the knit carraige.
- Debugging the firmware is hard, we don't have a good way to do that. Sam wants to build more debug state info into the desktop software.
- Maybe adding a button to the shield to send off a status indication.
- Chris creating another build.

# eKnitter
- We should probably do nothing.
- Get our Alpha/Beta ready to go.
- Our API is shifting might cause them problems
- GPL stuff. Chris reached out, they said they've shared the code somewhere on github. We should find their fork. 
- Wait until they ship, see what software they're shipping, then engage.

# Next hardware rev
- Have talked about waiting for a hardware rev until the 1.0 software is ready.
- Are these the same people? Will this take away from software resources.
- Goal to continue supporting the existing hardware while working on new.
- Goal to create something that people can have manufactured.
- Can Windell help? Priced to low last time. Had trouble supporting usage.
- Separate meeting to plan hardware. Draft a hardware team?
- Would be nice if eKnitter were open source and willing to handle manufacturing and distribution. But until then we need to do our own.
- Part sourcing will be tricky. 
- Revist to find a leader next meeting, everyone is in the middle of moving. Should advertise in the Discord to get volunteers.
- Will be mostly upgrading what we already have not starting from scratch.
- Bug: Signal missing from the 910 right hand sensor. Can we hack around it? Prevents starting on the right for the lace and garter carriages.
  - May not offically support this but would be open to working with a hack if someone builds one.
- How long should we support legacy hardware? Will need to be discussed. 
- We will need to make a decision when we get to the point of serving a web page from the interface.
- Automatic setting in the desktop software to override the. 

# Mailing list
- Advertise in the Facebook group.

# Community Server conversion
- Volunteers to be moderators
  - Sam
  - Sonia
  
 # Documentation
 - The manual, Adrienne used to have edit access.
 - Not much has changed, we might just update as we go.
 - Separate repo ayab-manual. Some changes https://github.com/AllYarnsAreBeautiful/ayab-manual/compare/master...1.0.0-dev
 - This is going to be hard for the community to contribute to. Would be nice to make it self serve.
 - Automatically deploy from github is possible.
 - Something more like a wiki? Github has a few options but maybe they aren't very good. Navigation sucks. No versioning.
 - Auto deploy might be good enough with a channel to help with the documentation part. AI to Sam to setup auto deploy.
 - Web page is also hosted in the repo. Sam has volunteered to do auto deploy.