You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by hidmic April 12, 2023
During #35, I came to the realization that some of the naming we use in LAMBKIN is inadequate and confusing.
LAMBKIN, the repository. As long as LAMBKIN remains a monorepo project, it is reasonable to have an homonym repository hosting the components and tools that make up the toolkit.
lambkin, the package. This is a misnomer. This package is not the toolkit, it is an orchestration tool that is part of the toolkit.
*_benchmark, for ROS packages. These are misnomers. These packages are not benchmarks but collections of benchmarks.
Discussed in https://github.com/ekumenlabs/lambkin/discussions/41
Originally posted by hidmic April 12, 2023
During #35, I came to the realization that some of the naming we use in LAMBKIN is inadequate and confusing.
LAMBKIN
, the repository. As long as LAMBKIN remains a monorepo project, it is reasonable to have an homonym repository hosting the components and tools that make up the toolkit.lambkin
, the package. This is a misnomer. This package is not the toolkit, it is an orchestration tool that is part of the toolkit.*_benchmark
, for ROS packages. These are misnomers. These packages are not benchmarks but collections of benchmarks.So I propose some renaming:
lambkin
(the package) -->lambkin-shepherd
(using namespace packages)slam_toolbox_benchmark
-->slam_toolbox_benchmarks
cartographer_ros_benchmark
-->cartographer_ros_benchmarks
The text was updated successfully, but these errors were encountered: