Skip to content

Separate the krr_btcpp_ros2 package #3

@alex-quin-gabriel

Description

@alex-quin-gabriel

Separate the individual components into different packages:

cs-specific things should be neat and tidy: ;)

  • Decision System plugins and their sub-trees: coresense_decision_components
  • Decision System messages: move into coresense_msgs

things with potential to become part of coresense I don't care so much, but should be separated from everything else:

  • control-logic, main trees: krr_robot_control or so

KRR-task specific things could be nicely packaged and named for use as future baseline

  • KRR-task-specific plugins: krr_action_plugins or so
  • KRR-task-specific messages: krr_agent_msgs or so

anyway, those are my rough ideas to get inspired by.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions