Moving to Github and de-branding as a Bob package
There is a general will to move software that can be used by a larger audience (that is not necessarily somebody at the @biometric group) to GitHub/conda-forge. This move would also de-brand this package as belonging to Bob.
To do this, I propose we take on this task by first identifying the various bits in here that would be useful as standalone components. I find there are mainly 5 categories of functions:
- Build tools for C++: cmake, boost, pkgconfig, utils, init
- Helpers for Sphinx building: utils (
link_documentation
) - Helpers to build CLIs:
scripts.click_helper
,scripts.main_cli
- Helpers for configuration: init, config, rc_config.py
- Helpers for logging:
log
(however some bits of it concern logging for C++)
I'm guessing that everything related to building other Bob packages (mostly the C++ code), can be considered deprecated once all C++ code has finally been ported to pure-Python alternatives. This then leaves us with the 4 other categories of helpers we have to somehow group (or not), to make packages.
Then, I propose we simply leave this package be (or archive it), and move the pieces of interest to a dedicated Python-only-builds GitHub project. We then ask each package going forward to make use of those specialised packages instead of bob.extension.