Update maintainers (#16) (#17)

(cherry picked from commit 2ea89dcb89)

Signed-off-by: Antón Casas <antoncasas@eprosima.com>
Co-authored-by: Antón Casas <antoncasas@eprosima.com>

CHANGELOG.rst

@@ -2,15 +2,12 @@
 Changelog for package micro_ros_msgs
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-6.0.0 (2024-05-31)
+3.0.1 (2024-02-01)
 ------------------
+* Add contributing file (`#9 <https://github.com/micro-ROS/micro_ros_msgs/issues/9>`_) (`#10 <https://github.com/micro-ROS/micro_ros_msgs/issues/10>`_)
+* Update package.xml (`#4 <https://github.com/micro-ROS/micro_ros_msgs/issues/4>`_) (`#5 <https://github.com/micro-ROS/micro_ros_msgs/issues/5>`_)
 
-5.0.1 (2024-02-01)
+3.0.0 (2023-06-06)
-------------------
-* 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)

CMakeLists.txt

@@ -1,4 +1,4 @@
-cmake_minimum_required(VERSION 3.10)
+cmake_minimum_required(VERSION 3.5)
 project(micro_ros_msgs)
 
 # Default to C99

CONTRIBUTING.md

@@ -1,24 +1,13 @@
-# Contributing Guidelines
+# 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 micro-ROS development team early in the process. Coordinating up
+with the system_modes development team early in the process. Coordinating up
 front helps to avoid frustration later on.
 
-Any contribution that you make to this repository will
+Your contribution must be licensed under the Apache-2.0 license, the license
-be under the Apache 2 License, as dictated by that
+used by this project.
-[license](http://www.apache.org/licenses/LICENSE-2.0.html):
-
-~~~
-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.
-~~~
 
 ## Add / retain copyright notices
 
@@ -34,7 +23,7 @@ Certificate of Origin (DCO; from [OSDL][DCO]) and Signed-off-by tags initially
 developed by the Linux kernel project.
 
 ```
-micro-ROS Developer's Certificate of Origin.  Version 1.0
+system_modes Developer's Certificate of Origin.  Version 1.0
 
 By making a contribution to this project, I certify that:
 
@@ -67,7 +56,7 @@ By making a contribution to this project, I certify that:
 
 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 micro-ROS Developer's Certificate of
+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>
@@ -90,7 +79,7 @@ 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 micro-ROS on
+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.
 
@@ -101,7 +90,7 @@ Each contributor is responsible for identifying themselves in the
 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 micro-ROS on
+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

NOTICE

@@ -1,26 +0,0 @@
-
-# This is the official list of copyright holders and authors.
-#
-# Often employers or academic institutions 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.
-#
-# When adding J Random Contributor's name to this file, either J's name on its
-# own or J's name associated with J's organization's name should be added,
-# depending on whether J's employer (or academic institution) has ownership
-# over code that is written for this project.
-#
-# How to add names to this file:
-#     Individual's name <submission email address>.
-#
-# If Individual's organization is copyright holder of her contributions add the
-# organization's name, optionally also the contributor's name:
-#
-#     Organization's name
-#         Individual's name <submission corporate email address>
-#
-# Please keep the list sorted.
-
-eProsima
-    Eugenio Collado <eugeniocollado@eprosima.com>
-    David Laseca <davidlaseca@eprosima.com>

package.xml

@@ -2,7 +2,7 @@
 <?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>
+  <version>3.0.1</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="eugeniocollado@eprosima.com">Eugenio Collado</maintainer>
   <maintainer email="carlosespinoza@eprosima.com">Carlos Espinoza</maintainer>