Suggestion: rename repository

[gavanderhoorn]

Simple really (or maybe not so much): rename the repository and metapackage to universal_robots from what it is now (universal_robot).

It's probably lost to history why this package and repository were created as universal_robot, but it's something that's been like that ever since the first version of the driver and description packages was created (eaff5f3).

The company's name is Universal Robots and the package(s) should reflect that.

[ipa-nhg]

@gavanderhoorn I am agree with you
For the metapackage is quite trivial: #401. Although til we release once the repo with the new name it doesn't take "real" effect.
The repository (and its url) is more sensitive for those that already have a fork and/or a local git clone, but communicating the change in the right channels should be enough.

Note: the wiki site has also to be renamed http://wiki.ros.org/universal_robot

[davetcoleman]

renaming a package on github isn't a big deal because the old name will auto-redirect to the new name, even during git clone

+1

[gavanderhoorn]

This will have to be done tick-tock, in order to not break existing installation instructions.

[davetcoleman]

When you rename a repository, all existing information, with the exception of Project Pages URLs, is automatically redirected to the new name
In addition to redirecting web traffic, all git clone, git fetch, or git push operations targeting the previous location will continue to function as if made on the new location.

https://help.github.com/en/articles/renaming-a-repository

[gavanderhoorn]

Thanks @davetcoleman, but I'm well aware of how GH handles repository renames.

My comment was about more than just the name of the repository itself.

[fmauch]

The meta-package itself is renamed already, the ROS Wiki page is renamed and a redirection is in place. So, everything left to do should be actually renaming the repository and afterwards update the docs:

• README
• ROS Wiki
• ur_robot_driver
• ur_tutorials

[fmauch]

Removing this from the milestone, as this is not effectively stopping us from releasing.