Open questions to be addressed

[Achllle]

I'm using this issue to communicate some open questions that could result in some additional entries in the multi-robot book. I'm opening this issue here instead of asking on answers.ros.org per request by @codebot and to provide a direct link to possible PRs following this.

1. Is there support for payload constraints for delivery tasks (or constraints in general for any task)? E.g. a factory might have parts that need to be delivered but some are too heavy for one of the robot types.
2. It would help to have an overview of all repos. What's the logic behind free_fleet, free_fleet_ros1, and free_fleet_ros2? It seems to me that the last two are not in use?
3. Can we make an entry for 'known an open-sourced adapters'?
4. SOSS (simply) connects middlewares. How does it fit in with fleet adapters?
5. There is a control level for fleet adapters that is called 'traffic light' (read access + start stop only). This is/might be confusing for those working in industrial automation, where traffic lights are physical devices used to control flow of people and mobile robots.
6. What's the process for adding new kinds of devices? Common control inputs are buttons, sensors, QR code scanners, and so on hooked up to PLCs. A button could have various functionalities such as validating that a robot is in the right spot or dispatching a new task, and a traffic light affects traffic management.
7. What is a 'workcell' defined as? The integration chapter only refers to two samples, a dispenser and ingestor. Assuming workcells means 'a static black box that takes in a part and spits it back out with something done to that part', how can a specific task be communicated to the workcell based on e.g. the part that is given to it (by some mobile robot)?

I realize that some of these questions might be XY questions. Appreciate any insights so I can piece things together and contribute.

[codebot]

Thanks @Achllle for taking the time to write up these open questions. We will address them individually and link back to this issue ticket as they are resolved.

Quick response to the question about the repo overview: we're wanting to do a grand re-organization of the repos in the near future, potentially including moving some things to a new github org, to try to collect the open-source RMF stuff all in one place. We hope to have a more detailed plan soon for this.

We'll address the other questions with documentation PR's. Thanks again for writing up these questions. Cheers