Skip to content

Request to add maintainers for ROS 2 or transfer of ownership of ROS 2 to ethz-asl #413

@Ryanf55

Description

@Ryanf55

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:

  • start using labels to categorize issues and PR's with whether they are ROS 1 or ROS 2
  • Simplify and document the branching strategy to only use rolling, iron and humble
  • Close anything related to EOL ROS distritions that can't be reproduced in humble
  • Create an issue template such that issue reporters are required to fill out a ROS distribution
  • Prioritize compilation issues first, then address the reported memory leaks or compile warnings that cause undefined behavior
  • Develop a maintenance plan and improve automatition
  • Define a strategy to merge changes from master into ROS 2 branches
  • Set a goal for a release
  • Release binaries for rolling, iron and humble
  • Develop future maintenance plan

Metadata

Metadata

Assignees

No one assigned

    Labels

    ros2Affects ROS 2

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions