Skip to content

Commit 9485f3c

Browse files
pablogs9pablogs9
authored
Update licensing (#15)
* Update * Update
1 parent 8f026e6 commit 9485f3c

5 files changed

Lines changed: 367 additions & 2 deletions

File tree

‎3rd-party-licenses.txt‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
Third Party Licenses
2+
====================
3+
4+
This repository contains the project Lab Project FreeRTOS POSIX released under a MIT License: https://github.com/FreeRTOS/Lab-Project-FreeRTOS-POSIX
5+

‎CONTRIBUTING.md‎

Lines changed: 107 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,107 @@
1+
# Contributing
2+
3+
Want to contribute? Great! You can do so through the standard GitHub pull
4+
request model. For large contributions we do encourage you to file a ticket in
5+
the GitHub issues tracking system prior to any code development to coordinate
6+
with the system_modes development team early in the process. Coordinating up
7+
front helps to avoid frustration later on.
8+
9+
Your contribution must be licensed under the Apache-2.0 license, the license
10+
used by this project.
11+
12+
## Add / retain copyright notices
13+
14+
Include a copyright notice and license in each new file to be contributed,
15+
consistent with the style used by this project. If your contribution contains
16+
code under the copyright of a third party, document its origin, license, and
17+
copyright holders.
18+
19+
## Sign your work
20+
21+
This project tracks patch provenance and licensing using a modified Developer
22+
Certificate of Origin (DCO; from [OSDL][DCO]) and Signed-off-by tags initially
23+
developed by the Linux kernel project.
24+
25+
```
26+
system_modes Developer's Certificate of Origin. Version 1.0
27+
28+
By making a contribution to this project, I certify that:
29+
30+
(a) The contribution was created in whole or in part by me and I
31+
have the right to submit it under the "Apache License, Version 2.0"
32+
("Apache-2.0"); or
33+
34+
(b) The contribution is based upon previous work that is covered by
35+
an appropriate open source license and I have the right under
36+
that license to submit that work with modifications, whether
37+
created in whole or in part by me, under the Apache-2.0 license;
38+
or
39+
40+
(c) The contribution was provided directly to me by some other
41+
person who certified (a) or (b) and I have not modified it.
42+
43+
(d) I understand and agree that this project and the contribution
44+
are public and that a record of the contribution (including all
45+
metadata and personal information I submit with it, including my
46+
sign-off) is maintained indefinitely and may be redistributed
47+
consistent with this project and the requirements of the Apache-2.0
48+
license or any open source license(s) involved, where they are
49+
relevant.
50+
51+
(e) I am granting the contribution to this project under the terms of
52+
Apache-2.0.
53+
54+
http://www.apache.org/licenses/LICENSE-2.0
55+
```
56+
57+
With the sign-off in a commit message you certify that you authored the patch
58+
or otherwise have the right to submit it under an open source license. The
59+
procedure is simple: To certify above system_modes Developer's Certificate of
60+
Origin 1.0 for your contribution just append a line
61+
62+
Signed-off-by: Random J Developer <random@developer.example.org>
63+
64+
to every commit message using your real name or your pseudonym and a valid
65+
email address.
66+
67+
If you have set your `user.name` and `user.email` git configs you can
68+
automatically sign the commit by running the git-commit command with the `-s`
69+
option. There may be multiple sign-offs if more than one developer was
70+
involved in authoring the contribution.
71+
72+
For a more detailed description of this procedure, please see
73+
[SubmittingPatches][] which was extracted from the Linux kernel project, and
74+
which is stored in an external repository.
75+
76+
### Individual vs. Corporate Contributors
77+
78+
Often employers or academic institution have ownership over code that is
79+
written in certain circumstances, so please do due diligence to ensure that
80+
you have the right to submit the code.
81+
82+
If you are a developer who is authorized to contribute to system_modes on
83+
behalf of your employer, then please use your corporate email address in the
84+
Signed-off-by tag. Otherwise please use a personal email address.
85+
86+
## Maintain Copyright holder / Contributor list
87+
88+
Each contributor is responsible for identifying themselves in the
89+
[NOTICE](NOTICE) file, the project's list of copyright holders and authors.
90+
Please add the respective information corresponding to the Signed-off-by tag
91+
as part of your first pull request.
92+
93+
If you are a developer who is authorized to contribute to system_modes on
94+
behalf of your employer, then add your company / organization to the list of
95+
copyright holders in the [NOTICE](NOTICE) file. As author of a corporate
96+
contribution you can also add your name and corporate email address as in the
97+
Signed-off-by tag.
98+
99+
If your contribution is covered by this project's DCO's clause "(c) The
100+
contribution was provided directly to me by some other person who certified
101+
(a) or (b) and I have not modified it", please add the appropriate copyright
102+
holder(s) to the [NOTICE](NOTICE) file as part of your contribution.
103+
104+
105+
[DCO]: http://web.archive.org/web/20070306195036/http://osdlab.org/newsroom/press_releases/2004/2004_05_24_dco.html
106+
107+
[SubmittingPatches]: https://github.com/wking/signed-off-by/blob/7d71be37194df05c349157a2161c7534feaf86a4/Documentation/SubmittingPatches

‎LICENSE‎

Lines changed: 202 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,202 @@
1+
2+
Apache License
3+
Version 2.0, January 2004
4+
http://www.apache.org/licenses/
5+
6+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7+
8+
1. Definitions.
9+
10+
"License" shall mean the terms and conditions for use, reproduction,
11+
and distribution as defined by Sections 1 through 9 of this document.
12+
13+
"Licensor" shall mean the copyright owner or entity authorized by
14+
the copyright owner that is granting the License.
15+
16+
"Legal Entity" shall mean the union of the acting entity and all
17+
other entities that control, are controlled by, or are under common
18+
control with that entity. For the purposes of this definition,
19+
"control" means (i) the power, direct or indirect, to cause the
20+
direction or management of such entity, whether by contract or
21+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
22+
outstanding shares, or (iii) beneficial ownership of such entity.
23+
24+
"You" (or "Your") shall mean an individual or Legal Entity
25+
exercising permissions granted by this License.
26+
27+
"Source" form shall mean the preferred form for making modifications,
28+
including but not limited to software source code, documentation
29+
source, and configuration files.
30+
31+
"Object" form shall mean any form resulting from mechanical
32+
transformation or translation of a Source form, including but
33+
not limited to compiled object code, generated documentation,
34+
and conversions to other media types.
35+
36+
"Work" shall mean the work of authorship, whether in Source or
37+
Object form, made available under the License, as indicated by a
38+
copyright notice that is included in or attached to the work
39+
(an example is provided in the Appendix below).
40+
41+
"Derivative Works" shall mean any work, whether in Source or Object
42+
form, that is based on (or derived from) the Work and for which the
43+
editorial revisions, annotations, elaborations, or other modifications
44+
represent, as a whole, an original work of authorship. For the purposes
45+
of this License, Derivative Works shall not include works that remain
46+
separable from, or merely link (or bind by name) to the interfaces of,
47+
the Work and Derivative Works thereof.
48+
49+
"Contribution" shall mean any work of authorship, including
50+
the original version of the Work and any modifications or additions
51+
to that Work or Derivative Works thereof, that is intentionally
52+
submitted to Licensor for inclusion in the Work by the copyright owner
53+
or by an individual or Legal Entity authorized to submit on behalf of
54+
the copyright owner. For the purposes of this definition, "submitted"
55+
means any form of electronic, verbal, or written communication sent
56+
to the Licensor or its representatives, including but not limited to
57+
communication on electronic mailing lists, source code control systems,
58+
and issue tracking systems that are managed by, or on behalf of, the
59+
Licensor for the purpose of discussing and improving the Work, but
60+
excluding communication that is conspicuously marked or otherwise
61+
designated in writing by the copyright owner as "Not a Contribution."
62+
63+
"Contributor" shall mean Licensor and any individual or Legal Entity
64+
on behalf of whom a Contribution has been received by Licensor and
65+
subsequently incorporated within the Work.
66+
67+
2. Grant of Copyright License. Subject to the terms and conditions of
68+
this License, each Contributor hereby grants to You a perpetual,
69+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70+
copyright license to reproduce, prepare Derivative Works of,
71+
publicly display, publicly perform, sublicense, and distribute the
72+
Work and such Derivative Works in Source or Object form.
73+
74+
3. Grant of Patent License. Subject to the terms and conditions of
75+
this License, each Contributor hereby grants to You a perpetual,
76+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77+
(except as stated in this section) patent license to make, have made,
78+
use, offer to sell, sell, import, and otherwise transfer the Work,
79+
where such license applies only to those patent claims licensable
80+
by such Contributor that are necessarily infringed by their
81+
Contribution(s) alone or by combination of their Contribution(s)
82+
with the Work to which such Contribution(s) was submitted. If You
83+
institute patent litigation against any entity (including a
84+
cross-claim or counterclaim in a lawsuit) alleging that the Work
85+
or a Contribution incorporated within the Work constitutes direct
86+
or contributory patent infringement, then any patent licenses
87+
granted to You under this License for that Work shall terminate
88+
as of the date such litigation is filed.
89+
90+
4. Redistribution. You may reproduce and distribute copies of the
91+
Work or Derivative Works thereof in any medium, with or without
92+
modifications, and in Source or Object form, provided that You
93+
meet the following conditions:
94+
95+
(a) You must give any other recipients of the Work or
96+
Derivative Works a copy of this License; and
97+
98+
(b) You must cause any modified files to carry prominent notices
99+
stating that You changed the files; and
100+
101+
(c) You must retain, in the Source form of any Derivative Works
102+
that You distribute, all copyright, patent, trademark, and
103+
attribution notices from the Source form of the Work,
104+
excluding those notices that do not pertain to any part of
105+
the Derivative Works; and
106+
107+
(d) If the Work includes a "NOTICE" text file as part of its
108+
distribution, then any Derivative Works that You distribute must
109+
include a readable copy of the attribution notices contained
110+
within such NOTICE file, excluding those notices that do not
111+
pertain to any part of the Derivative Works, in at least one
112+
of the following places: within a NOTICE text file distributed
113+
as part of the Derivative Works; within the Source form or
114+
documentation, if provided along with the Derivative Works; or,
115+
within a display generated by the Derivative Works, if and
116+
wherever such third-party notices normally appear. The contents
117+
of the NOTICE file are for informational purposes only and
118+
do not modify the License. You may add Your own attribution
119+
notices within Derivative Works that You distribute, alongside
120+
or as an addendum to the NOTICE text from the Work, provided
121+
that such additional attribution notices cannot be construed
122+
as modifying the License.
123+
124+
You may add Your own copyright statement to Your modifications and
125+
may provide additional or different license terms and conditions
126+
for use, reproduction, or distribution of Your modifications, or
127+
for any such Derivative Works as a whole, provided Your use,
128+
reproduction, and distribution of the Work otherwise complies with
129+
the conditions stated in this License.
130+
131+
5. Submission of Contributions. Unless You explicitly state otherwise,
132+
any Contribution intentionally submitted for inclusion in the Work
133+
by You to the Licensor shall be under the terms and conditions of
134+
this License, without any additional terms or conditions.
135+
Notwithstanding the above, nothing herein shall supersede or modify
136+
the terms of any separate license agreement you may have executed
137+
with Licensor regarding such Contributions.
138+
139+
6. Trademarks. This License does not grant permission to use the trade
140+
names, trademarks, service marks, or product names of the Licensor,
141+
except as required for reasonable and customary use in describing the
142+
origin of the Work and reproducing the content of the NOTICE file.
143+
144+
7. Disclaimer of Warranty. Unless required by applicable law or
145+
agreed to in writing, Licensor provides the Work (and each
146+
Contributor provides its Contributions) on an "AS IS" BASIS,
147+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148+
implied, including, without limitation, any warranties or conditions
149+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150+
PARTICULAR PURPOSE. You are solely responsible for determining the
151+
appropriateness of using or redistributing the Work and assume any
152+
risks associated with Your exercise of permissions under this License.
153+
154+
8. Limitation of Liability. In no event and under no legal theory,
155+
whether in tort (including negligence), contract, or otherwise,
156+
unless required by applicable law (such as deliberate and grossly
157+
negligent acts) or agreed to in writing, shall any Contributor be
158+
liable to You for damages, including any direct, indirect, special,
159+
incidental, or consequential damages of any character arising as a
160+
result of this License or out of the use or inability to use the
161+
Work (including but not limited to damages for loss of goodwill,
162+
work stoppage, computer failure or malfunction, or any and all
163+
other commercial damages or losses), even if such Contributor
164+
has been advised of the possibility of such damages.
165+
166+
9. Accepting Warranty or Additional Liability. While redistributing
167+
the Work or Derivative Works thereof, You may choose to offer,
168+
and charge a fee for, acceptance of support, warranty, indemnity,
169+
or other liability obligations and/or rights consistent with this
170+
License. However, in accepting such obligations, You may act only
171+
on Your own behalf and on Your sole responsibility, not on behalf
172+
of any other Contributor, and only if You agree to indemnify,
173+
defend, and hold each Contributor harmless for any liability
174+
incurred by, or claims asserted against, such Contributor by reason
175+
of your accepting any such warranty or additional liability.
176+
177+
END OF TERMS AND CONDITIONS
178+
179+
APPENDIX: How to apply the Apache License to your work.
180+
181+
To apply the Apache License to your work, attach the following
182+
boilerplate notice, with the fields enclosed by brackets "[]"
183+
replaced with your own identifying information. (Don't include
184+
the brackets!) The text should be enclosed in the appropriate
185+
comment syntax for the file format. We also recommend that a
186+
file or class name and description of purpose be included on the
187+
same "printed page" as the copyright notice for easier
188+
identification within third-party archives.
189+
190+
Copyright 2019 Robert Bosch GmbH
191+
192+
Licensed under the Apache License, Version 2.0 (the "License");
193+
you may not use this file except in compliance with the License.
194+
You may obtain a copy of the License at
195+
196+
http://www.apache.org/licenses/LICENSE-2.0
197+
198+
Unless required by applicable law or agreed to in writing, software
199+
distributed under the License is distributed on an "AS IS" BASIS,
200+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201+
See the License for the specific language governing permissions and
202+
limitations under the License.

‎NOTICE‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
2+
# This is the official list of copyright holders and authors.
3+
#
4+
# Often employers or academic institutions have ownership over code that is
5+
# written in certain circumstances, so please do due diligence to ensure that
6+
# you have the right to submit the code.
7+
#
8+
# When adding J Random Contributor's name to this file, either J's name on its
9+
# own or J's name associated with J's organization's name should be added,
10+
# depending on whether J's employer (or academic institution) has ownership
11+
# over code that is written for this project.
12+
#
13+
# How to add names to this file:
14+
# Individual's name <submission email address>.
15+
#
16+
# If Individual's organization is copyright holder of her contributions add the
17+
# organization's name, optionally also the contributor's name:
18+
#
19+
# Organization's name
20+
# Individual's name <submission corporate email address>
21+
#
22+
# Please keep the list sorted.
23+
24+
eProsima
25+
Jose Antonio Moral <joseantoniomoralparras@eprosima.com>
26+
Pablo Garrido <pablogarrido@eprosima.com>
27+

‎README.md‎

Lines changed: 26 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,35 @@
1-
# Introduction
2-
Set of example applications for micro-ROS running over FreeRTOS.
1+
# micro-ROS FreeRTOS Apps
2+
3+
This repository contains micro-ROS demos and support code for platforms based on FreeRTOS.
34

45
# Supported platforms
56
Supported hardware platforms are:
67
* Olimex STM32-E407 development board.
78
* Crazyflie 2.1 drone.
9+
* ST Nucleo F446ZE (community supported).
10+
811

912
# Usage
1013
These applications are integrated within the [micro-ROS build system](https://github.com/micro-ROS/micro-ros-build).
1114
Please refer to this repository's documentation for further information about how to configure, build and flash them.
15+
16+
17+
## Purpose of the Project
18+
19+
This software is not ready for production use. It has neither been developed nor
20+
tested for a specific use case. However, the license conditions of the
21+
applicable Open Source licenses allow you to adapt the software to your needs.
22+
Before using it in a safety relevant setting, make sure that the software
23+
fulfills your requirements and adjust it according to any applicable safety
24+
standards, e.g., ISO 26262.
25+
26+
## License
27+
28+
This repository is open-sourced under the Apache-2.0 license. See the [LICENSE](LICENSE) file for details.
29+
30+
For a list of other open-source components included in ROS 2 system_modes,
31+
see the file [3rd-party-licenses.txt](3rd-party-licenses.txt).
32+
33+
## Known Issues/Limitations
34+
35+
There are no known limitations.

0 commit comments

Comments
 (0)