Drop robot_pose_ekf

[mikeferguson]

Just noticed this repo existed -- as a current maintainer of navigation, I would highly suggest we drop robot_pose_ekf during the port to ROS2 -- it only works properly for robots with high-end IMUs like PR2, and there are better solutions (graft) that don't depend on horrible-to-release packages like bel

[mikeferguson]

As an additional note, carrot_planner, base_local_planner and navfn should probably also be considered for the chopping block (since we have dwa_local_planner and global_planner which are better codebases to maintain)

[wjwwood]

@mikeferguson Those both sound like fine suggestions. I'm not sure we'll do that right now in this repository. From my perspective, the main purpose of this repository atm is to support our demo we're working on. A little later we might want to push back what we've got to the original navigation repository and spend more time refactoring for the long term, including removing unused packages and applying more ROS 2 features to the design.

Either way it's good to start thinking about what needs to be ported and what should be left behind.

[mikeferguson]

FYI - we're actually planning to drop robot_pose_ekf in ROS1 in Melodic. ros-planning#701

[sloretz]

Closing issue; this repo is obsolete: #35