[Ovmsdev] Vehicle Sub-Modules
mark at webb-johnson.net
Sun May 26 21:20:52 HKT 2019
Given that the vehicle modules in v3 are pretty independent, and don’t seem to require any changes to the core code to implement (other than a Kconfig section, and a sub-directory in ‘components’), I’m considering a structural change.
The proposal is to make each vehicle an independent GitHub repository, and to use the git submodule functionality to bring them in. The advantage there is that those projects can be split off and maintained by different people. Project owners, looking after their own vehicle types, could directly commit to their own vehicle modules, without requiring this to be centrally managed.
What do people think? Is that a sensible way of doing this?
More information about the OvmsDev