How can I request to be a member of ros-gbp?

Buildfarm
1

I wanted to be a member of ros-gbp to make it contain a release repo of our package in preparation for the ROS Noetic buildfarm.

I have seen instructions on doing this for ros2-gbp, but I can’t see any instructions on how to do it for ros-gbp:

Please advise.

2

You don’t need to be a member of the ros-gbp org to make a release. You can host the release repo on any public place, e.g. your personal github account.

3

Yes, you can use any repository you want, however a ros-gbp release repository is the recommended way to go. You can send a PR to the terraform config for the org here: GitHub - ros2-gbp/ros2-gbp-github-org

For more details on the process you can read @nuclearsandwich’s post here: Ros2-gbp release repository permissions are now managed via GitHub repository

4

The question was about a Noetic release, so no ros2.

1 Like
5

Wops, missed the noetic part :grimacing:.

6

Thank you for the response. Unfortunately, this is for a company source code. We can’t use personal github accounts instead, and we can’t use the company github account either because only employees are allowed to commit/push there (so the build farm won’t have access on it). We have no problem with ROS2 because it has a ros2-gbp repo (and procedures documented on registering the package there), however, we can’t see any procedure/contact email address for ROS1 (ros-gbp), even amidst all the packages present in that repo.

7

Thank you. Do you know any similar documentation for ros-gbp instead (we need ROS1 Noetic)? We are releasing a separate package for the ROS2 Humble (where we used that ros2-gbp), unfortunately, we also need access to ros-gbp due to our ROS1 Noetic version.

8

I touched up the documentation on ROS 2 GBP. Let me know if that helps. I am waiting for approval to add org level docs that should also help.

I’m talking to @clalancette to see what I can do about ROS 1 GBP. If there are any resources you find helpful along the way please let me know.

1 Like
9

The ros-gbp content is informally managed and became a lot of a burden so in general the recommendation is to self host for ROS 1.

In this case, I would recommend that you go ahead and follow the ros2-gbp process then. The ros2-gbp can also host ROS 1 release content. And hopefully in the future there will be a ROS 2 release of the packages eventually too. It’s a slightly more rigorous process but it sounds like that’s easier than resolving your other constraints.