First things first: repos. Do we create a new repo for the new “gui tool” (and come up with a better name) or do we just start a v1 branch in the current repo?
I’d like to start a new repo just named “tools” that has a GUI as one of the tools. This leaves space for command-line tools to be developed as well and kept in this repository.
We might also want to refer to the GUI using something less generic then “gooey tool”. What about calling it the “UAVCAN control station” or “UAVCAN control suite”. Let’s make a “my name is best” list like we did for naming Subjects:
- UAVCAN control station (UCS)
- UAVCAN control suite (UCS)
- UAVCAN Diagnostics and Control (UDC)
- Visual UAVCAN (VUC)
- UAVCAN connect (UConn)
- UAVCAN 360 (this is a joke, somehow I went all Microsoft for the last three of these)
- CAN Opener
- CAN NT
- (sorry, this is fun)