r2r_spl repository

Repository Summary

Checkout URI https://github.com/ros-sports/r2r_spl.git
VCS Type git
VCS Version humble
Last Updated 2022-06-18
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Packages

Name Version
r2r_spl_7 2.0.0
splsm_7 2.0.0
splsm_7_conversion 2.0.0

README

Robot-to-Robot communication in RoboCup SPL

Build and Test (foxy) Build and Test (galactic) Build and Test (humble) Build and Test (rolling) Build and Test (dev)

ROS2 package that handles intra-team communication using SPLStandardMessage defined in the RoboCup SPL rulebook.

For more information, see our Documentation

Branches

Note that this repository has an unusual branching strategy. The default branch is the dev branch.

The dev branch is unreleased, and should work with SPL GameController's master branch's SPLStandardMessage example. When a new SPLStandardMessage release is made (eg. version 8), a new package will be created (eg.r2r_spl_8) and be backported to all active distros (eg. rolling, humble, etc.) and released.

That way, teams can use new versions of SPLStandardMessage on distros apart from Rolling!

None of the distro branches should contain the r2r_spl_master package. When a distro is being branched off, make sure to delete the r2r_spl_master package on that branch because it will always have API breaking changes. The reason there is a separate dev branch, is because if rolling is the dev branch, then when a new distro is released (branched off from rolling), it will contain r2r_spl_master. (which is an issue)

CONTRIBUTING

Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:

5. Submission of Contributions. Unless You explicitly state otherwise,
   any Contribution intentionally submitted for inclusion in the Work
   by You to the Licensor shall be under the terms and conditions of
   this License, without any additional terms or conditions.
   Notwithstanding the above, nothing herein shall supersede or modify
   the terms of any separate license agreement you may have executed
   with Licensor regarding such Contributions.

Repository Summary

Checkout URI https://github.com/ros-sports/r2r_spl.git
VCS Type git
VCS Version galactic
Last Updated 2022-06-18
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Packages

Name Version
r2r_spl_7 1.0.0
splsm_7 1.0.0
splsm_7_conversion 1.0.0

README

Robot-to-Robot communication in RoboCup SPL

Build and Test (foxy) Build and Test (galactic) Build and Test (humble) Build and Test (rolling) Build and Test (dev)

ROS2 package that handles intra-team communication using SPLStandardMessage defined in the RoboCup SPL rulebook.

For more information, see our Documentation

Branches

Note that this repository has an unusual branching strategy. The default branch is the dev branch.

The dev branch is unreleased, and should work with SPL GameController's master branch's SPLStandardMessage example. When a new SPLStandardMessage release is made (eg. version 8), a new package will be created (eg.r2r_spl_8) and be backported to all active distros (eg. rolling, humble, etc.) and released.

That way, teams can use new versions of SPLStandardMessage on distros apart from Rolling!

None of the distro branches should contain the r2r_spl_master package. When a distro is being branched off, make sure to delete the r2r_spl_master package on that branch because it will always have API breaking changes. The reason there is a separate dev branch, is because if rolling is the dev branch, then when a new distro is released (branched off from rolling), it will contain r2r_spl_master. (which is an issue)

CONTRIBUTING

Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:

5. Submission of Contributions. Unless You explicitly state otherwise,
   any Contribution intentionally submitted for inclusion in the Work
   by You to the Licensor shall be under the terms and conditions of
   this License, without any additional terms or conditions.
   Notwithstanding the above, nothing herein shall supersede or modify
   the terms of any separate license agreement you may have executed
   with Licensor regarding such Contributions.

Repository Summary

Checkout URI https://github.com/ros-sports/r2r_spl.git
VCS Type git
VCS Version foxy
Last Updated 2022-06-18
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Packages

Name Version
r2r_spl_7 0.0.1
splsm_7 0.0.1
splsm_7_conversion 0.0.1

README

Robot-to-Robot communication in RoboCup SPL

Build and Test (foxy) Build and Test (galactic) Build and Test (humble) Build and Test (rolling) Build and Test (dev)

ROS2 package that handles intra-team communication using SPLStandardMessage defined in the RoboCup SPL rulebook.

For more information, see our Documentation

Branches

Note that this repository has an unusual branching strategy. The default branch is the dev branch.

The dev branch is unreleased, and should work with SPL GameController's master branch's SPLStandardMessage example. When a new SPLStandardMessage release is made (eg. version 8), a new package will be created (eg.r2r_spl_8) and be backported to all active distros (eg. rolling, humble, etc.) and released.

That way, teams can use new versions of SPLStandardMessage on distros apart from Rolling!

None of the distro branches should contain the r2r_spl_master package. When a distro is being branched off, make sure to delete the r2r_spl_master package on that branch because it will always have API breaking changes. The reason there is a separate dev branch, is because if rolling is the dev branch, then when a new distro is released (branched off from rolling), it will contain r2r_spl_master. (which is an issue)

CONTRIBUTING

Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:

5. Submission of Contributions. Unless You explicitly state otherwise,
   any Contribution intentionally submitted for inclusion in the Work
   by You to the Licensor shall be under the terms and conditions of
   this License, without any additional terms or conditions.
   Notwithstanding the above, nothing herein shall supersede or modify
   the terms of any separate license agreement you may have executed
   with Licensor regarding such Contributions.

Repository Summary

Checkout URI https://github.com/ros-sports/r2r_spl.git
VCS Type git
VCS Version rolling
Last Updated 2022-06-18
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Packages

Name Version
r2r_spl_7 3.0.0
splsm_7 3.0.0
splsm_7_conversion 3.0.0

README

Robot-to-Robot communication in RoboCup SPL

Build and Test (foxy) Build and Test (galactic) Build and Test (humble) Build and Test (rolling) Build and Test (dev)

ROS2 package that handles intra-team communication using SPLStandardMessage defined in the RoboCup SPL rulebook.

For more information, see our Documentation

Branches

Note that this repository has an unusual branching strategy. The default branch is the dev branch.

The dev branch is unreleased, and should work with SPL GameController's master branch's SPLStandardMessage example. When a new SPLStandardMessage release is made (eg. version 8), a new package will be created (eg.r2r_spl_8) and be backported to all active distros (eg. rolling, humble, etc.) and released.

That way, teams can use new versions of SPLStandardMessage on distros apart from Rolling!

None of the distro branches should contain the r2r_spl_master package. When a distro is being branched off, make sure to delete the r2r_spl_master package on that branch because it will always have API breaking changes. The reason there is a separate dev branch, is because if rolling is the dev branch, then when a new distro is released (branched off from rolling), it will contain r2r_spl_master. (which is an issue)

CONTRIBUTING

Any contribution that you make to this repository will be under the Apache 2 License, as dictated by that license:

5. Submission of Contributions. Unless You explicitly state otherwise,
   any Contribution intentionally submitted for inclusion in the Work
   by You to the Licensor shall be under the terms and conditions of
   this License, without any additional terms or conditions.
   Notwithstanding the above, nothing herein shall supersede or modify
   the terms of any separate license agreement you may have executed
   with Licensor regarding such Contributions.