cloud_events 0.6.0 → 0.7.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/.yardopts +1 -1
- data/CHANGELOG.md +10 -0
- data/CONTRIBUTING.md +167 -0
- data/MAINTAINERS.md +5 -0
- data/README.md +5 -39
- data/RELEASING.md +25 -0
- data/lib/cloud_events/content_type.rb +1 -1
- data/lib/cloud_events/http_binding.rb +6 -0
- data/lib/cloud_events/version.rb +1 -1
- metadata +7 -5
- data/LICENSE.md +0 -202
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 3b24efea575e52e5e9290bfba5b64f06cc52145ddc8572153b418c2d29bf8bf2
|
|
4
|
+
data.tar.gz: dd6f1d1788846857a698c9b5152eaa7294f5d76d653b2e189762ee7ca108a89f
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 66a25968b6662e7603a2bd83b97f0b8390f05baddb36f1a4d26f68351c3ccb35596e12f8b889095186226c09b0d338c059a4d3c6f9035afe1325a8369cc714e1
|
|
7
|
+
data.tar.gz: ce94d00dde6b272e9c6d7e26a90e923c98cccbb184acf0b4ccc2de3081c20c0ba311080a4529cb2184908ea2aec1318f88c7fc161e1b04f24189a3e6061d7155
|
data/.yardopts
CHANGED
data/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,15 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
### v0.7.1 / 2023-10-04
|
|
4
|
+
|
|
5
|
+
* DOCS: Governance docs per CE PR 1226
|
|
6
|
+
|
|
7
|
+
### v0.7.0 / 2022-01-14
|
|
8
|
+
|
|
9
|
+
* HttpBinding#probable_event? returns false if the request method is GET or HEAD.
|
|
10
|
+
* HttpBinding#decode_event raises NotCloudEventError if the request method is GET or HEAD.
|
|
11
|
+
* Fixed a NoMethodError if nil content was passed to the ContentType constructor.
|
|
12
|
+
|
|
3
13
|
### v0.6.0 / 2021-08-23
|
|
4
14
|
|
|
5
15
|
This update further clarifies and cleans up the encoding behavior of event payloads. In particular, the event object now includes explicitly encoded data in the new `data_encoded` field, and provides information on whether the existing `data` field contains an encoded or decoded form of the payload.
|
data/CONTRIBUTING.md
ADDED
|
@@ -0,0 +1,167 @@
|
|
|
1
|
+
# Contributing to CloudEvents' Ruby SDK
|
|
2
|
+
|
|
3
|
+
:+1::tada: First off, thanks for taking the time to contribute! :tada::+1:
|
|
4
|
+
|
|
5
|
+
We welcome contributions from the community! Please take some time to become
|
|
6
|
+
acquainted with the process before submitting a pull request. There are just
|
|
7
|
+
a few things to keep in mind.
|
|
8
|
+
|
|
9
|
+
# Pull Requests
|
|
10
|
+
|
|
11
|
+
Typically, a pull request should relate to an existing issue. If you have
|
|
12
|
+
found a bug, want to add an improvement, or suggest an API change, please
|
|
13
|
+
create an issue before proceeding with a pull request. For very minor changes
|
|
14
|
+
such as typos in the documentation this isn't really necessary.
|
|
15
|
+
|
|
16
|
+
## Pull Request Guidelines
|
|
17
|
+
|
|
18
|
+
Here you will find step by step guidance for creating, submitting and updating
|
|
19
|
+
a pull request in this repository. We hope it will help you have an easy time
|
|
20
|
+
managing your work and a positive, satisfying experience when contributing
|
|
21
|
+
your code. Thanks for getting involved! :rocket:
|
|
22
|
+
|
|
23
|
+
* [Getting Started](#getting-started)
|
|
24
|
+
* [Branches](#branches)
|
|
25
|
+
* [Commit Messages](#commit-messages)
|
|
26
|
+
* [Staying current with main](#staying-current-with-main)
|
|
27
|
+
* [Submitting and Updating a Pull Request](#submitting-and-updating-a-pull-request)
|
|
28
|
+
* [Congratulations!](#congratulations)
|
|
29
|
+
|
|
30
|
+
## Getting Started
|
|
31
|
+
|
|
32
|
+
When creating a pull request, first fork this repository and clone it to your
|
|
33
|
+
local development environment. Then add this repository as the upstream.
|
|
34
|
+
|
|
35
|
+
```console
|
|
36
|
+
git clone https://github.com/mygithuborg/sdk-ruby.git
|
|
37
|
+
cd sdk-ruby
|
|
38
|
+
git remote add upstream https://github.com/cloudevents/sdk-ruby.git
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
## Branches
|
|
42
|
+
|
|
43
|
+
The first thing you'll need to do is create a branch for your work.
|
|
44
|
+
If you are submitting a pull request that fixes or relates to an existing
|
|
45
|
+
GitHub issue, you can use the issue number in your branch name to keep things
|
|
46
|
+
organized.
|
|
47
|
+
|
|
48
|
+
```console
|
|
49
|
+
git fetch upstream
|
|
50
|
+
git reset --hard upstream/main
|
|
51
|
+
git checkout FETCH_HEAD
|
|
52
|
+
git checkout -b 48-fix-http-agent-error
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
## Commit Messages
|
|
56
|
+
|
|
57
|
+
Please follow the
|
|
58
|
+
[Conventional Commits specification](https://www.conventionalcommits.org/en/v1.0.0/#summary).
|
|
59
|
+
The first line of your commit should be prefixed with a type, be a single
|
|
60
|
+
sentence with no period, and succinctly indicate what this commit changes.
|
|
61
|
+
|
|
62
|
+
All commit message lines should be kept to fewer than 80 characters if possible.
|
|
63
|
+
|
|
64
|
+
An example of a good commit message.
|
|
65
|
+
|
|
66
|
+
```log
|
|
67
|
+
docs: remove 0.1, 0.2 spec support from README
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
### Signing your commits
|
|
71
|
+
|
|
72
|
+
Each commit must be signed. Use the `--signoff` flag for your commits.
|
|
73
|
+
|
|
74
|
+
```console
|
|
75
|
+
git commit --signoff
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
This will add a line to every git commit message:
|
|
79
|
+
|
|
80
|
+
Signed-off-by: Joe Smith <joe.smith@email.com>
|
|
81
|
+
|
|
82
|
+
Use your real name (sorry, no pseudonyms or anonymous contributions.)
|
|
83
|
+
|
|
84
|
+
The sign-off is a signature line at the end of your commit message. Your
|
|
85
|
+
signature certifies that you wrote the patch or otherwise have the right to pass
|
|
86
|
+
it on as open-source code. See [developercertificate.org](http://developercertificate.org/)
|
|
87
|
+
for the full text of the certification.
|
|
88
|
+
|
|
89
|
+
Be sure to have your `user.name` and `user.email` set in your git config.
|
|
90
|
+
If your git config information is set properly then viewing the `git log`
|
|
91
|
+
information for your commit will look something like this:
|
|
92
|
+
|
|
93
|
+
```
|
|
94
|
+
Author: Joe Smith <joe.smith@email.com>
|
|
95
|
+
Date: Thu Feb 2 11:41:15 2018 -0800
|
|
96
|
+
|
|
97
|
+
Update README
|
|
98
|
+
|
|
99
|
+
Signed-off-by: Joe Smith <joe.smith@email.com>
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will
|
|
103
|
+
be rejected by the automated DCO check.
|
|
104
|
+
|
|
105
|
+
## Staying Current with `main`
|
|
106
|
+
|
|
107
|
+
As you are working on your branch, changes may happen on `main`. Before
|
|
108
|
+
submitting your pull request, be sure that your branch has been updated
|
|
109
|
+
with the latest commits.
|
|
110
|
+
|
|
111
|
+
```console
|
|
112
|
+
git fetch upstream
|
|
113
|
+
git rebase upstream/main
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
This may cause conflicts if the files you are changing on your branch are
|
|
117
|
+
also changed on main. Error messages from `git` will indicate if conflicts
|
|
118
|
+
exist and what files need attention. Resolve the conflicts in each file, then
|
|
119
|
+
continue with the rebase with `git rebase --continue`.
|
|
120
|
+
|
|
121
|
+
|
|
122
|
+
If you've already pushed some changes to your `origin` fork, you'll
|
|
123
|
+
need to force push these changes.
|
|
124
|
+
|
|
125
|
+
```console
|
|
126
|
+
git push -f origin 48-fix-http-agent-error
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
## Submitting and Updating Your Pull Request
|
|
130
|
+
|
|
131
|
+
Before submitting a pull request, you should make sure that all of the tests
|
|
132
|
+
successfully pass.
|
|
133
|
+
|
|
134
|
+
Once you have sent your pull request, `main` may continue to evolve
|
|
135
|
+
before your pull request has landed. If there are any commits on `main`
|
|
136
|
+
that conflict with your changes, you may need to update your branch with
|
|
137
|
+
these changes before the pull request can land. Resolve conflicts the same
|
|
138
|
+
way as before.
|
|
139
|
+
|
|
140
|
+
```console
|
|
141
|
+
git fetch upstream
|
|
142
|
+
git rebase upstream/main
|
|
143
|
+
# fix any potential conflicts
|
|
144
|
+
git push -f origin 48-fix-http-agent-error
|
|
145
|
+
```
|
|
146
|
+
|
|
147
|
+
This will cause the pull request to be updated with your changes, and
|
|
148
|
+
CI will rerun.
|
|
149
|
+
|
|
150
|
+
A maintainer may ask you to make changes to your pull request. Sometimes these
|
|
151
|
+
changes are minor and shouldn't appear in the commit log. For example, you may
|
|
152
|
+
have a typo in one of your code comments that should be fixed before merge.
|
|
153
|
+
You can prevent this from adding noise to the commit log with an interactive
|
|
154
|
+
rebase. See the [git documentation](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History)
|
|
155
|
+
for details.
|
|
156
|
+
|
|
157
|
+
```console
|
|
158
|
+
git commit -m "fixup: fix typo"
|
|
159
|
+
git rebase -i upstream/main # follow git instructions
|
|
160
|
+
```
|
|
161
|
+
|
|
162
|
+
Once you have rebased your commits, you can force push to your fork as before.
|
|
163
|
+
|
|
164
|
+
## Congratulations!
|
|
165
|
+
|
|
166
|
+
Congratulations! You've done it! We really appreciate the time and energy
|
|
167
|
+
you've given to the project. Thank you.
|
data/MAINTAINERS.md
ADDED
data/README.md
CHANGED
|
@@ -184,31 +184,6 @@ few things to keep in mind.
|
|
|
184
184
|
* **Make sure CI passes.** Invoke `toys ci` to run the tests locally before
|
|
185
185
|
opening a pull request. This will include code style checks.
|
|
186
186
|
|
|
187
|
-
### Releasing
|
|
188
|
-
|
|
189
|
-
Releases can be performed only by users with write access to the repository.
|
|
190
|
-
|
|
191
|
-
To perform a release:
|
|
192
|
-
|
|
193
|
-
1. Go to the GitHub Actions tab, and launch the "Request Release" workflow.
|
|
194
|
-
You can leave the input field blank.
|
|
195
|
-
|
|
196
|
-
2. The workflow will analyze the commit messages since the last release, and
|
|
197
|
-
open a pull request with a new version and a changelog entry. You can
|
|
198
|
-
optionally edit this pull request to modify the changelog or change the
|
|
199
|
-
version released.
|
|
200
|
-
|
|
201
|
-
3. Merge the pull request (keeping the `release: pending` label set.) Once the
|
|
202
|
-
CI tests have run successfully, a job will run automatically to perform the
|
|
203
|
-
release, including tagging the commit in git, building and releasing a gem,
|
|
204
|
-
and building and pushing documentation.
|
|
205
|
-
|
|
206
|
-
These tasks can also be performed manually by running the appropriate scripts
|
|
207
|
-
locally. See `toys release request --help` and `toys release perform --help`
|
|
208
|
-
for more information.
|
|
209
|
-
|
|
210
|
-
If a release fails, you may need to delete the release tag before retrying.
|
|
211
|
-
|
|
212
187
|
### For more information
|
|
213
188
|
|
|
214
189
|
* Library documentation: https://cloudevents.github.io/sdk-ruby
|
|
@@ -243,18 +218,9 @@ for how PR reviews and approval, and our
|
|
|
243
218
|
[Code of Conduct](https://github.com/cloudevents/spec/blob/master/community/GOVERNANCE.md#additional-information)
|
|
244
219
|
information.
|
|
245
220
|
|
|
246
|
-
##
|
|
247
|
-
|
|
248
|
-
Copyright 2020 Google LLC and the CloudEvents Ruby SDK Contributors
|
|
249
|
-
|
|
250
|
-
Licensed under the Apache License, Version 2.0 (the "License");
|
|
251
|
-
you may not use this software except in compliance with the License.
|
|
252
|
-
You may obtain a copy of the License at
|
|
253
|
-
|
|
254
|
-
https://www.apache.org/licenses/LICENSE-2.0
|
|
221
|
+
## Additional SDK Resources
|
|
255
222
|
|
|
256
|
-
|
|
257
|
-
|
|
258
|
-
|
|
259
|
-
|
|
260
|
-
limitations under the License.
|
|
223
|
+
- [List of current active maintainers](MAINTAINERS.md)
|
|
224
|
+
- [How to contribute to the project](CONTRIBUTING.md)
|
|
225
|
+
- [SDK's License](LICENSE)
|
|
226
|
+
- [SDK's Release process](RELEASING.md)
|
data/RELEASING.md
ADDED
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
# Releasing
|
|
2
|
+
|
|
3
|
+
Releases can be performed only by users with write access to the repository.
|
|
4
|
+
|
|
5
|
+
To perform a release:
|
|
6
|
+
|
|
7
|
+
1. Go to the GitHub Actions tab, and launch the "Request Release" workflow.
|
|
8
|
+
You can leave the input field blank.
|
|
9
|
+
|
|
10
|
+
2. The workflow will analyze the commit messages since the last release, and
|
|
11
|
+
open a pull request with a new version and a changelog entry. You can
|
|
12
|
+
optionally edit this pull request to modify the changelog or change the
|
|
13
|
+
version released.
|
|
14
|
+
|
|
15
|
+
3. Merge the pull request (keeping the `release: pending` label set.) Once the
|
|
16
|
+
CI tests have run successfully, a job will run automatically to perform the
|
|
17
|
+
release, including tagging the commit in git, building and releasing a gem,
|
|
18
|
+
and building and pushing documentation.
|
|
19
|
+
|
|
20
|
+
These tasks can also be performed manually by running the appropriate scripts
|
|
21
|
+
locally. See `toys release request --help` and `toys release perform --help`
|
|
22
|
+
for more information.
|
|
23
|
+
|
|
24
|
+
If a release fails, you may need to delete the release tag before retrying.
|
|
25
|
+
|
|
@@ -32,7 +32,7 @@ module CloudEvents
|
|
|
32
32
|
@params = []
|
|
33
33
|
@charset = default_charset || "us-ascii"
|
|
34
34
|
@error_message = nil
|
|
35
|
-
parse consume_comments string.strip
|
|
35
|
+
parse consume_comments @string.strip
|
|
36
36
|
@canonical_string = "#{@media_type}/#{@subtype}" +
|
|
37
37
|
@params.map { |k, v| "; #{k}=#{maybe_quote v}" }.join
|
|
38
38
|
full_freeze
|
|
@@ -20,6 +20,9 @@ module CloudEvents
|
|
|
20
20
|
#
|
|
21
21
|
JSON_FORMAT = "json"
|
|
22
22
|
|
|
23
|
+
# @private
|
|
24
|
+
ILLEGAL_METHODS = ["GET", "HEAD"].freeze
|
|
25
|
+
|
|
23
26
|
##
|
|
24
27
|
# Returns a default HTTP binding, including support for JSON format.
|
|
25
28
|
#
|
|
@@ -134,6 +137,7 @@ module CloudEvents
|
|
|
134
137
|
# @return [boolean] Whether the request is likely a CloudEvent.
|
|
135
138
|
#
|
|
136
139
|
def probable_event? env
|
|
140
|
+
return false if ILLEGAL_METHODS.include? env["REQUEST_METHOD"]
|
|
137
141
|
return true if env["HTTP_CE_SPECVERSION"]
|
|
138
142
|
content_type = ContentType.new env["CONTENT_TYPE"].to_s
|
|
139
143
|
content_type.media_type == "application" &&
|
|
@@ -163,6 +167,8 @@ module CloudEvents
|
|
|
163
167
|
# from the request.
|
|
164
168
|
#
|
|
165
169
|
def decode_event env, allow_opaque: false, **format_args
|
|
170
|
+
request_method = env["REQUEST_METHOD"]
|
|
171
|
+
raise NotCloudEventError, "Request method is #{request_method}" if ILLEGAL_METHODS.include? request_method
|
|
166
172
|
content_type_string = env["CONTENT_TYPE"]
|
|
167
173
|
content_type = ContentType.new content_type_string if content_type_string
|
|
168
174
|
content = read_with_charset env["rack.input"], content_type&.charset
|
data/lib/cloud_events/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: cloud_events
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.
|
|
4
|
+
version: 0.7.1
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Daniel Azuma
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date:
|
|
11
|
+
date: 2023-10-04 00:00:00.000000000 Z
|
|
12
12
|
dependencies: []
|
|
13
13
|
description: The official Ruby implementation of the CloudEvents Specification. Provides
|
|
14
14
|
data types for events, and HTTP/JSON bindings for marshalling and unmarshalling
|
|
@@ -21,8 +21,10 @@ extra_rdoc_files: []
|
|
|
21
21
|
files:
|
|
22
22
|
- ".yardopts"
|
|
23
23
|
- CHANGELOG.md
|
|
24
|
-
-
|
|
24
|
+
- CONTRIBUTING.md
|
|
25
|
+
- MAINTAINERS.md
|
|
25
26
|
- README.md
|
|
27
|
+
- RELEASING.md
|
|
26
28
|
- lib/cloud_events.rb
|
|
27
29
|
- lib/cloud_events/content_type.rb
|
|
28
30
|
- lib/cloud_events/errors.rb
|
|
@@ -41,10 +43,10 @@ homepage: https://github.com/cloudevents/sdk-ruby
|
|
|
41
43
|
licenses:
|
|
42
44
|
- Apache-2.0
|
|
43
45
|
metadata:
|
|
44
|
-
changelog_uri: https://cloudevents.github.io/sdk-ruby/v0.
|
|
46
|
+
changelog_uri: https://cloudevents.github.io/sdk-ruby/v0.7.1/file.CHANGELOG.html
|
|
45
47
|
source_code_uri: https://github.com/cloudevents/sdk-ruby
|
|
46
48
|
bug_tracker_uri: https://github.com/cloudevents/sdk-ruby/issues
|
|
47
|
-
documentation_uri: https://cloudevents.github.io/sdk-ruby/v0.
|
|
49
|
+
documentation_uri: https://cloudevents.github.io/sdk-ruby/v0.7.1
|
|
48
50
|
post_install_message:
|
|
49
51
|
rdoc_options: []
|
|
50
52
|
require_paths:
|
data/LICENSE.md
DELETED
|
@@ -1,202 +0,0 @@
|
|
|
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 [yyyy] [name of copyright owner]
|
|
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.
|