Deprecate this repository?

[diegoferigo]

The new xsens driver is temporarily stored in robotology-playground/wearables@XSensMVN.

We should take one of the following decisions:

1. Leave the driver in wearables and deprecate this repo (that contains the old driver we no longer use)
2. Move the driver from wearables to another repository (in order to have it standalone, and make it a wearables dependency) and deprecate this repo
3. Move the driver from wearables to this repository, removing all the other resources we no longer need

I would tend to do an hybrid between 2 and 3. Option 3 is appealing but the new driver has nothing shared with the old one. This would mean that all files in the repo would change, and I prefer starting from scratch. I propose:

1. Deprecate this repo and move it to robotology-legacy
2. Plan activities to spit the new XSensMVN driver from wearables
3. Create a fresh robotology/xsens-mvn repo and store the new driver
4. Add this repo as new wearables dependency
5. Write in the README of the deprecated repository that the new one is stored in robotology

I would proceed on this task after we release new hde v2. We should also move wearables to robotology before proceeding.

cc @yeshasvitvs @lrapetti @claudia-lat @DanielePucci @traversaro

[diegoferigo]

@traversaro @lrapetti @yeshasvitvs Can we proceed with the deprecation?

[traversaro]

Ok for me, let me know and I can move the repo in robotology legacy.

[lrapetti]

We can procede deprecating this repository and moving to legacy.

Regarding the initial discussion, I agree on splitting xsens related software from wearable.

[diegoferigo]

We can procede deprecating this repository and moving to legacy.

Agreed then

I agree on splitting xsens related software from wearable.

What's nice IMO is that the driver is not YARP specific, other people could use it. And when I mean splitting Xsens driver I intend only the pure C++ part of it, not the YARP device.