This post serves as the agenda and notes for the working meetings on the FATT project and AMT Software. Currently, these meetings and work night happen 2x a month on Thursday night from 7pm to 8:30pm <this meeting was deferred for storms and availability issues)

Agenda

Contributors should add their proposed topics here!

1. Confirm the Agenda
2. Git Management – Team (10 min)
3. Update on Azure development space – Hal
4. Laser Fob Box Billing Next Steps – Crafty
5. Laser Fob Box update – Python version – MattA
6. Kremepuff 2 update – MattC
7. Kremepuff enclosures – Crafty
8. Access Point Test Criteria – Crafty
9. Door Status Update – Team
10. Next Steps
11. Post Next Agenda

Notes

1. Git Management – Team (10 min)
   1. What do we need right now?
      1. MC – write up of current repositories and access (public / private (what groups have what levels of read/write access to each repository))
   2. What would good management look like?
      1. MC – Access: (unless there are specific repositories that require higher responsibility roles)
         1. AMT Group -> Read access to all private repositories
         2. FATT group -> Write access to all FATT repositories
         3. Software Group -> Write access to GC & WP / Wiki repositories
      2. MC – Workflow:
         1. Branch – use tag based branch names eg: <username>/<task-name>/<extra info>
         2. Pull Request – Open PR when ready to submit or for discussion on current implementation
         3. Testing (IDEAL) – Use Github actions or similar to automatically run unit / integration tests for a PR
         4. Deploy – Dev (IDEAL) – Automatically deploy to a development / testing environment on tests passing
         5. PR Review – Third party to review code / test environment, add Github comments inline and PR chat for discussion of clarifications / needed changes
         6. Merge – Merge the pull request to trunk on Third party acceptance of PR
         7. Testing (IDEAL) – Automatically run unit / integration tests on merging to trunk (auto rollback commit on failure?).
         8. Deploy (IDEAL) – Automatically deploy to production environment on successful merge and tests
   3. How does migration to prod fit in?
      1. MC – Ideally using Azure pipelines a successful merge to trunk (with tests run / verified in test/dev environment) Azure pipelines would handle the build and deployment to a production environment.
   4. What are the attributes of a qualified manager?
      1. MC – I don’t know if we require a specific position for github/deployment management, this should be shared around the more trusted members of the software team otherwise a single manage will spend more time managing Pull Requests than contributing to the project.
2. Update on Azure development space – Hal
   1. What is the current state
   2. How close are we to spinning up environments
   3. What support is needed to accomplish this from Crafty? From the team?
3. Laser Fob Box Billing Next Steps – Crafty
   1. For the January Billing, we need somebody to pull the logs and run the calculations. Who can do this, please? By Feb. 2 preferably.
      1. MC – Happy to do this, do we also need to do December?
4. Laser Fob Box update – Python version – MattA
   1. Where is it at?
   2. What is needed next?
   3. Teensy delivered Monday, where did they get stored?
   4. The new screen should be here Monday 1-20
   5. Anything I should know before designing the new enclosure?
5. Kremepuff 2 update – MattC
   1. Is it ready for enclosure and installation?
      1. Yes
   2. Does it need testing first? If so what is the test criteria?
      1. Has been tested, but will require testing after installation in enclosure
      2. Test -> Scan fob, does a fob id print out on the printer?
   3. Where are the electronics currently?
      1. In printer box in clean fab, brown box, top shelf of electronics with other FATT boxes
6. Kremepuff enclosures – Crafty
   1. Enclosure 1 done and installed in coworking
   2. Next step is to package and release cut files and assembly write up
7. Access Point Test Criteria – Crafty
   1. This is the task Will be done by 23rd
8. Access Point/Door Status Update – Team
   1. Current bugs
      1. Laser showing folks as not certified when they are
      2. Bug: #113 and #214 not accepting Fob accepted by #206
9. Next Steps
   1. TBD. As this was not a live meeting.
10. Post Next Agenda