mirror of
https://github.com/micro-ROS/micro_ros_msgs.git
synced 2026-09-06 09:55:09 +02:00
Bump lyrical
Signed-off-by: David Laseca Perez <davidlaseca@eprosima.com>
This commit is contained in:
+20
-6
@@ -1,14 +1,28 @@
|
||||
# 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
|
||||
|
||||
Include a copyright notice and license in each new file to be contributed,
|
||||
@@ -23,7 +37,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 +70,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 +93,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 +104,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
|
||||
|
||||
Reference in New Issue
Block a user