Skip to content

Commit ec47168

Browse files
author
ShotaAk
committed
Add examples
1 parent c634b21 commit ec47168

File tree

3,418 files changed

+388864
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

3,418 files changed

+388864
-0
lines changed

‎micro_ros_arduino-2.0.5-foxy/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 does not directly contain 3rd party source code.
5+

‎micro_ros_arduino-2.0.5-foxy/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

‎micro_ros_arduino-2.0.5-foxy/LICENSE

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

‎micro_ros_arduino-2.0.5-foxy/NOTICE

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
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+
Pablo Garrido <pablogarrido@eprosima.com>
26+

0 commit comments

Comments
 (0)