6.0.0

(cherry picked from commit 9bf9ddf7ce)

Co-authored-by: Pablo Garrido <pablogs9@gmail.com>

.github/ISSUE_TEMPLATE/general-issue.md

@@ -0,0 +1,24 @@
+---
+name: General issue
+about: General issue template for micro-ROS
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+## Issue template
+
+- Hardware description: <!-- hardware where you are using micro-ROS -->
+- RTOS: <!-- RTOS where you are using micro-ROS -->
+- Installation type: <!-- micro_ros_setup, modules, etc  -->
+- Version or commit hash: <!-- version of micro-ROS used: foxy, rolling  -->
+
+#### Steps to reproduce the issue
+<!-- Detailed instructions on how to reliably reproduce this issue http://sscce.org/-->
+
+#### Expected behavior
+
+#### Actual behavior
+
+#### Additional information

CHANGELOG.rst

@@ -0,0 +1,21 @@
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Changelog for package micro_ros_msgs
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+6.0.0 (2024-05-31)
+------------------
+
+5.0.1 (2024-02-01)
+------------------
+* Add contributing file (`#9 <https://github.com/micro-ROS/micro_ros_msgs/issues/9>`_) (`#11 <https://github.com/micro-ROS/micro_ros_msgs/issues/11>`_)
+* Update package.xml (`#4 <https://github.com/micro-ROS/micro_ros_msgs/issues/4>`_) (`#6 <https://github.com/micro-ROS/micro_ros_msgs/issues/6>`_)
+
+5.0.0 (2023-06-06)
+------------------
+
+1.0.0 (2021-08-30)
+------------------
+* Remove not necessary dependencies (`#1 <https://github.com/micro-ROS/micro_ros_msgs/issues/1>`_)
+* Add issue template
+* Add msg definitions used by micro-ROS graph manager
+* Update README.md

CMakeLists.txt

@@ -0,0 +1,36 @@
+cmake_minimum_required(VERSION 3.5)
+project(micro_ros_msgs)
+
+# Default to C99
+if(NOT CMAKE_C_STANDARD)
+  set(CMAKE_C_STANDARD 99)
+endif()
+
+# Default to C++14
+if(NOT CMAKE_CXX_STANDARD)
+  set(CMAKE_CXX_STANDARD 14)
+endif()
+
+if(CMAKE_COMPILER_IS_GNUCXX OR CMAKE_CXX_COMPILER_ID MATCHES "Clang")
+  add_compile_options(-Wall -Wextra -Wpedantic)
+endif()
+
+# find dependencies
+find_package(ament_cmake REQUIRED)
+find_package(rosidl_default_generators REQUIRED)
+
+if(BUILD_TESTING)
+  find_package(ament_lint_auto REQUIRED)
+  ament_lint_auto_find_test_dependencies()
+endif()
+
+rosidl_generate_interfaces(
+  ${PROJECT_NAME}
+  "msg/Graph.msg"
+  "msg/Node.msg"
+  "msg/Entity.msg"
+)
+
+ament_export_libraries()
+
+ament_package()

CONTRIBUTING.md

@@ -0,0 +1,107 @@
+# Contributing
+
+Want to contribute? Great! You can do so through the standard GitHub pull
+request model. For large contributions we do encourage you to file a ticket in
+the GitHub issues tracking system prior to any code development to coordinate
+with the system_modes development team early in the process. Coordinating up
+front helps to avoid frustration later on.
+
+Your contribution must be licensed under the Apache-2.0 license, the license
+used by this project.
+
+## Add / retain copyright notices
+
+Include a copyright notice and license in each new file to be contributed,
+consistent with the style used by this project. If your contribution contains
+code under the copyright of a third party, document its origin, license, and
+copyright holders.
+
+## Sign your work
+
+This project tracks patch provenance and licensing using a modified Developer
+Certificate of Origin (DCO; from [OSDL][DCO]) and Signed-off-by tags initially
+developed by the Linux kernel project.
+
+```
+system_modes Developer's Certificate of Origin.  Version 1.0
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the "Apache License, Version 2.0"
+    ("Apache-2.0"); or
+
+(b) The contribution is based upon previous work that is covered by
+    an appropriate open source license and I have the right under
+    that license to submit that work with modifications, whether
+    created in whole or in part by me, under the Apache-2.0 license;
+    or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a) or (b) and I have not modified it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    metadata and personal information I submit with it, including my
+    sign-off) is maintained indefinitely and may be redistributed
+    consistent with this project and the requirements of the Apache-2.0
+    license or any open source license(s) involved, where they are
+    relevant.
+
+(e) I am granting the contribution to this project under the terms of
+    Apache-2.0.
+
+    http://www.apache.org/licenses/LICENSE-2.0
+```
+
+With the sign-off in a commit message you certify that you authored the patch
+or otherwise have the right to submit it under an open source license. The
+procedure is simple: To certify above system_modes Developer's Certificate of
+Origin 1.0 for your contribution just append a line
+
+    Signed-off-by: Random J Developer <random@developer.example.org>
+
+to every commit message using your real name or your pseudonym and a valid
+email address.
+
+If you have set your `user.name` and `user.email` git configs you can
+automatically sign the commit by running the git-commit command with the `-s`
+option.  There may be multiple sign-offs if more than one developer was
+involved in authoring the contribution.
+
+For a more detailed description of this procedure, please see
+[SubmittingPatches][] which was extracted from the Linux kernel project, and
+which is stored in an external repository.
+
+### Individual vs. Corporate Contributors
+
+Often employers or academic institution have ownership over code that is
+written in certain circumstances, so please do due diligence to ensure that
+you have the right to submit the code.
+
+If you are a developer who is authorized to contribute to system_modes on
+behalf of your employer, then please use your corporate email address in the
+Signed-off-by tag. Otherwise please use a personal email address.
+
+## Maintain Copyright holder / Contributor list
+
+Each contributor is responsible for identifying themselves in the
+[NOTICE](NOTICE) file, the project's list of copyright holders and authors.
+Please add the respective information corresponding to the Signed-off-by tag
+as part of your first pull request.
+
+If you are a developer who is authorized to contribute to system_modes on
+behalf of your employer, then add your company / organization to the list of
+copyright holders in the [NOTICE](NOTICE) file. As author of a corporate
+contribution you can also add your name and corporate email address as in the
+Signed-off-by tag.
+
+If your contribution is covered by this project's DCO's clause "(c) The
+contribution was provided directly to me by some other person who certified
+(a) or (b) and I have not modified it", please add the appropriate copyright
+holder(s) to the [NOTICE](NOTICE) file as part of your contribution.
+
+
+[DCO]: http://web.archive.org/web/20070306195036/http://osdlab.org/newsroom/press_releases/2004/2004_05_24_dco.html
+
+[SubmittingPatches]: https://github.com/wking/signed-off-by/blob/7d71be37194df05c349157a2161c7534feaf86a4/Documentation/SubmittingPatches

README.md

@@ -1,2 +1,20 @@
 # micro_ros_msgs
-Collection of ROS 2 message definitions used throughout the implementation of micro-ROS, both in the agent and client endpoints.
+
+## Summary
+
+Collection of ROS 2 message definitions used throughout the implementation of micro-ROS, both in the server ([micro-ROS Agent](https://github.com/micro-ROS/micro-ROS-Agent/)) and client ([micro-ROS RMW](https://github.com/micro-ROS/rmw-microxrcedds)) endpoints.
+
+## Purpose of the Project
+
+This software is not ready for production use.
+It has neither been developed nor tested for a specific use case.
+However, the license conditions of the applicable Open Source licenses allow you to adapt the software to your needs.
+Before using it in a safety relevant setting, make sure that the software fulfills your requirements and adjust it according to any applicable safety standards, e.g., ISO 26262.
+
+## License
+
+This repository is open-sourced under the Apache-2.0 license. See the LICENSE file for details.
+
+## Known Issues/Limitations
+
+There are no known limitations.

msg/Entity.msg

@@ -0,0 +1,8 @@
+byte PUBLISHER=0
+byte SUBSCRIBER=1
+byte SERVICE_SERVER=2
+byte SERVICE_CLIENT=3
+
+byte entity_type
+string<=256 name
+string<=256[] types

msg/Graph.msg

@@ -0,0 +1 @@
+Node[] nodes

msg/Node.msg

@@ -0,0 +1,3 @@
+string<=256 node_namespace
+string<=256 node_name
+Entity[] entities

package.xml

@@ -0,0 +1,22 @@
+<?xml version="1.0"?>
+<?xml-model href="http://download.ros.org/schema/package_format3.xsd" schematypens="http://www.w3.org/2001/XMLSchema"?>
+<package format="3">
+  <name>micro_ros_msgs</name>
+  <version>6.0.0</version>
+  <description>Definitions for the ROS 2 msgs entities information used by micro-ROS to leverage its functionality to the same level as ROS 2, by means of a dedicated graph manager</description>
+  <maintainer email="pablogarrido@eprosima.com">Pablo Garrido</maintainer>
+  <license>Apache License 2.0</license>
+
+  <buildtool_depend>ament_cmake</buildtool_depend>
+
+  <test_depend>ament_lint_auto</test_depend>
+  <test_depend>ament_lint_common</test_depend>
+
+  <build_depend>rosidl_default_generators</build_depend>
+  <exec_depend>rosidl_default_runtime</exec_depend>
+  <member_of_group>rosidl_interface_packages</member_of_group>
+
+  <export>
+    <build_type>ament_cmake</build_type>
+  </export>
+</package>