wadim

I use solaar[0] on Linux for my MX Master 2S; it's really nice and mostly works out of the box!

[0] https://github.com/pwr-Solaar/Solaar

I'm also a big fan of CalVer (https://calver.org/), though I think it totally depends on the context. I wouldn't want to write C++ libraries with it.

But mixed-criticality systems are quite normal in many deployments nowadays, especially with the advent of virtualization and hypervisors you should be able to run safety critical and non-safety critical functions at the same time on the same SoC.

I guess the "easiest" solution would be a clean and separate "github" directory where no work happens and where you just cp all your changes from your actual working directory into.

If they version it, I could also imagine using master as an orphan branch and just cherry-pick the changes between two tags or commits into it.

Are they mutually exclusive, though? You might think the tools are adequate - or even good -, but not be happy with how other people handle remote collaboration.

My experience has been, that some people really like to call you directly and expect you to take their call, without creating a meeting or asking you if/when you have time. Others (still) have problems with muting/unmuting themselves or realizing that everybody can hear their environment. And I think when you're accustomed to never or very rarely working from home, there are a lot of things you have to do differently, so the learning or adaption curve is kinda steep at the beginning.

Have you thought about also looking at the guidelines for MISRA C++? The AUTOSAR ones[1] are fairly recent and might be a bit closer to Rust.

[1] https://www.autosar.org/fileadmin/user_upload/standards/adap...