Define state, clean, and decide fate of this repo

[jgvictores]

Stemming from asrob-uc3m/rd2#1 (comment), this is a tracking issue to define the state, clean, and decide fate of this repo.

Here is a list of what we have as of current develop 6bfe26b:

1. A list pointing to robot repositories
2. Some generated QRs
3. An idea of a mini-web service, see Robot (first time) configuration through access point #8
4. Shared ini files

Spoken with @PeterBowman, if we wanted to destroy this repo:

1. A list pointing to robot repositories: could be moved to robotDevastation wiki or robotDevastation-user-manual
2. Some generated QRs: ?
3. An idea of a mini-web service, see Robot (first time) configuration through access point #8: ?
4. Shared ini files: This in fact involves a different decision on how/where we want these files:
   1. Centralized (robotDevastation-configuration-files)
   2. robot-specific, because it is very robot specific except for port name (however: we could recover pre- Replace yarprun by list of services parsed from file #29 robotName file). EDIT: an issue with this approach is that robot-specific repos are big and we'd maybe resolve to using wget of the specific config file.

[PeterBowman]

Doxygen stuff removed at 66690e3.

[jgvictores]

Idea: repo name change to robotDevastation-robot-configuration-files or simply robotDevastation-configuration-files.

The existing robot list could be moved to: any manual (user/developer), the main page, or even to a separate page like https://robots.ieee.org/ 😁

[jgvictores]

Idea: repo name change to robotDevastation-robot-configuration-files or simply robotDevastation-configuration-files.

Note that this was already proposed above 🙈