We now have 5 libraries that are broadly ready for wider release. PythonTemplate scikit-surgery scikit-surgerycore scikit-surgeryimage scikit-surgeryvideolag These should be published to Pypi and publisised internally (via slack). So add the pypi bit to the ci script, and create a subgroup on weisslab to contain SNAPPY packages that are ready.
Configuration control, agreed we will probably need a configuration manager in the future, but not to start on this yet. Update: Implemented for SmartLiver, issue 3 in scikit-surgerycore., reads .json.
Use VTK for all overlays (text/shapes etc) rather than OpenCV
Still use semantic versioning, even during early days, likely to end up with large minor version number before first milestone release
Decided we MUST use "Issue #" in commit message
Decided, multiple small apps in a project is better than multiple projects each containing one app. scikit-surgeryvideolag now obsolete, use scikit-surgeryvideoutils instead.
Decided. Tom refactoring Ardavin to use SNAPPY. Mian, move towards re-working BARD. Steve working on first tutorial to spread the news on PythonTemplate and SNAPPY
Decided that rather than install runners on Mock OR machines, we would have user accounts dedicated to each research group, who can then install/deploy as necessary. When a better use case becomes clear we can think again.
Having multiple classes in a single file/module is acceptable for Python projects. Any C++ code should stick to 1 class per file.