I would like to request to be added as a maintainer for the ROS 2 branches of grid_map.
Option 1: Add me as a maintainer
Option 2: Endorse having the ROS 2 port at https://github.com/ethz-asl/grid_map, and direct users there for pull requests.
I'm open to other options.
I am currently maintaining a few related libraries in ROS 2 like grid_map_geo, which heavily depends on grid_map.
While this repository is maintained for ROS 1, the same is not as clear for ROS 2. By opening up the library to more maintainers, this will alleviate some of the open issues and PR's for documentation and building the repo. Without this, it's become difficult to use grid_map in ROS 2, especially as the ROS 2 branch becomes further out of date with master.
Furthermore, the branch structure is not common practice for ROS 2, there is no policy or information on how to contribute to which branch. Obviously, foxy is now EOL, so those PR's may need forward-ported to a LTS release such as humble.
For clarity, here is a list of issues affecting ROS 2 that have not been addressed:
Hello,
I would like to request to be added as a maintainer for the ROS 2 branches of grid_map.
Option 1: Add me as a maintainer Option 2: Endorse having the ROS 2 port at https://github.com/ethz-asl/grid_map, and direct users there for pull requests. I'm open to other options.
I am currently maintaining a few related libraries in ROS 2 like grid_map_geo, which heavily depends on grid_map.
While this repository is maintained for ROS 1, the same is not as clear for ROS 2. By opening up the library to more maintainers, this will alleviate some of the open issues and PR's for documentation and building the repo. Without this, it's become difficult to use grid_map in ROS 2, especially as the ROS 2 branch becomes further out of date with
master
.Furthermore, the branch structure is not common practice for ROS 2, there is no policy or information on how to contribute to which branch. Obviously, foxy is now EOL, so those PR's may need forward-ported to a LTS release such as
humble
.For clarity, here is a list of issues affecting ROS 2 that have not been addressed:
As part of maintaining grid_map_geo, I would take the following approach, in chronological order:
rolling
,iron
andhumble
master
into ROS 2 branches