High level block diagram of intended workflow

[SteveMacenski]

Coming from the standard nav stack and having built a few alternatives over time, I dont look at this project and have a good understand what's happening or how the elements interact.

Is there a plan to make a block diagram much like the move_base one to clear up your architectural intentions? It's challenging to get involved or track without it.

[SteveMacenski]

I see this guy (https://github.com/ros-planning/navigation2/blob/master/doc/design/Navigation_2_Overview.pdf) but that's not really a full block diagram of what you're trying to accomplish here with navigation2 restructuring instead of starting with navigation stack and building on top of it

[mkhansenbot]

@SteveMacenski - Steve I've added this to our TO DO. We'll create a better diagram or two and put it in a more obvious place, like the top-level README. Thanks for your feedback.

[SteveMacenski]

More generally speaking, I'd like to be involved in this effort as well. Having a good briefing about the thought process and what's being rebuilt vs. ported over would be good!

[mkhansenbot]

@SteveMacenski - now that we have READMEs and a ROS1 comparison, can we close this ticket? If not please let us know what else is needed.

[SteveMacenski]

I think there should probably be a 3-5 paragraph description in the root README about the general infrastructure and organization of the entire stack. Most of that knowledge exists in the READMEs and the docs directory, but I think something concise and clear would be good as an entry point. I think that's out of scope for this ticket.