3 Commits
Author SHA1 Message Date
David Laseca Perez 3180a81f27 Bump lyrical
Signed-off-by: David Laseca Perez <davidlaseca@eprosima.com>
2026-09-01 08:09:27 +02:00
mergify[bot]andAntón Casas 839f17bab4 Update maintainers (#16) (#19)
(cherry picked from commit 2ea89dcb89)

Signed-off-by: Antón Casas <antoncasas@eprosima.com>
Co-authored-by: Antón Casas <antoncasas@eprosima.com>
2025-09-15 16:30:14 +02:00
Pablo Garrido b935f634ba Bump maintainer (#12) 2025-07-16 08:15:37 +02:00
3 changed files with 46 additions and 9 deletions
+1 -1
View File
@@ -1,4 +1,4 @@
cmake_minimum_required(VERSION 3.5)
cmake_minimum_required(VERSION 3.10)
project(micro_ros_msgs)
# Default to C99
+19 -8
View File
@@ -1,13 +1,24 @@
# Contributing
# Contributing Guidelines
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
with the micro-ROS 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.
Any contribution that you make to this repository will
be under the Apache 2 License, as dictated by that
[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
@@ -23,7 +34,7 @@ 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
micro-ROS Developer's Certificate of Origin. Version 1.0
By making a contribution to this project, I certify that:
@@ -56,7 +67,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 system_modes Developer's Certificate of
procedure is simple: To certify above micro-ROS Developer's Certificate of
Origin 1.0 for your contribution just append a line
Signed-off-by: Random J Developer <random@developer.example.org>
@@ -79,7 +90,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 system_modes on
If you are a developer who is authorized to contribute to micro-ROS 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.
@@ -90,7 +101,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 system_modes on
If you are a developer who is authorized to contribute to micro-ROS 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
+26
View File
@@ -0,0 +1,26 @@
# 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>