agentic-fsm 0.1.5__tar.gz
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.
- agentic_fsm-0.1.5/.github/workflows/deploy.yml +59 -0
- agentic_fsm-0.1.5/.gitignore +6 -0
- agentic_fsm-0.1.5/CLAUDE.md +143 -0
- agentic_fsm-0.1.5/LICENCE.md +202 -0
- agentic_fsm-0.1.5/PKG-INFO +280 -0
- agentic_fsm-0.1.5/README.md +252 -0
- agentic_fsm-0.1.5/agentic_fsm/__init__.py +28 -0
- agentic_fsm-0.1.5/agentic_fsm/ask.py +185 -0
- agentic_fsm-0.1.5/agentic_fsm/backends/__init__.py +45 -0
- agentic_fsm-0.1.5/agentic_fsm/backends/base/__init__.py +0 -0
- agentic_fsm-0.1.5/agentic_fsm/backends/base/base.py +88 -0
- agentic_fsm-0.1.5/agentic_fsm/backends/django/__init__.py +0 -0
- agentic_fsm-0.1.5/agentic_fsm/backends/django/apps.py +8 -0
- agentic_fsm-0.1.5/agentic_fsm/backends/django/base.py +83 -0
- agentic_fsm-0.1.5/agentic_fsm/backends/django/migrations/0001_initial.py +62 -0
- agentic_fsm-0.1.5/agentic_fsm/backends/django/migrations/__init__.py +0 -0
- agentic_fsm-0.1.5/agentic_fsm/backends/django/models.py +43 -0
- agentic_fsm-0.1.5/agentic_fsm/backends/django/project.py +10 -0
- agentic_fsm-0.1.5/agentic_fsm/backends/locmem/__init__.py +0 -0
- agentic_fsm-0.1.5/agentic_fsm/backends/locmem/base.py +55 -0
- agentic_fsm-0.1.5/agentic_fsm/cli.py +261 -0
- agentic_fsm-0.1.5/agentic_fsm/conf/__init__.py +60 -0
- agentic_fsm-0.1.5/agentic_fsm/conf/global_settings.py +11 -0
- agentic_fsm-0.1.5/agentic_fsm/machine.py +378 -0
- agentic_fsm-0.1.5/agentic_fsm/states.py +111 -0
- agentic_fsm-0.1.5/pyproject.toml +61 -0
- agentic_fsm-0.1.5/tests/__init__.py +0 -0
- agentic_fsm-0.1.5/tests/conftest.py +64 -0
- agentic_fsm-0.1.5/tests/machines.py +8 -0
- agentic_fsm-0.1.5/tests/settings.py +5 -0
- agentic_fsm-0.1.5/tests/test_ask.py +375 -0
- agentic_fsm-0.1.5/tests/test_cli.py +309 -0
- agentic_fsm-0.1.5/tests/test_conf.py +59 -0
- agentic_fsm-0.1.5/tests/test_machine_build.py +177 -0
- agentic_fsm-0.1.5/tests/test_machine_moves.py +257 -0
- agentic_fsm-0.1.5/tests/test_states.py +51 -0
|
@@ -0,0 +1,59 @@
|
|
|
1
|
+
name: Deploy
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
push:
|
|
5
|
+
branches: [main]
|
|
6
|
+
|
|
7
|
+
jobs:
|
|
8
|
+
test:
|
|
9
|
+
runs-on: ubuntu-latest
|
|
10
|
+
steps:
|
|
11
|
+
- uses: actions/checkout@v4
|
|
12
|
+
|
|
13
|
+
- uses: actions/setup-python@v5
|
|
14
|
+
with:
|
|
15
|
+
python-version: "3.12"
|
|
16
|
+
|
|
17
|
+
- uses: astral-sh/setup-uv@v5
|
|
18
|
+
|
|
19
|
+
- name: Install
|
|
20
|
+
run: uv pip install --system -e ".[dev]"
|
|
21
|
+
|
|
22
|
+
- name: Run tests
|
|
23
|
+
run: pytest
|
|
24
|
+
|
|
25
|
+
# Every green push to `main` is a release. The version is derived here, not committed, so it
|
|
26
|
+
# cannot drift out of sync with what actually shipped.
|
|
27
|
+
publish-pypi:
|
|
28
|
+
if: github.ref == 'refs/heads/main'
|
|
29
|
+
needs: test
|
|
30
|
+
runs-on: ubuntu-latest
|
|
31
|
+
# Required: the PyPI trusted publisher is registered against this workflow filename
|
|
32
|
+
# *and* this environment name. Do not add a required reviewer to it — that would put
|
|
33
|
+
# every push behind a manual approval, which is the thing this job exists to remove.
|
|
34
|
+
environment: pypi
|
|
35
|
+
permissions:
|
|
36
|
+
id-token: write # PyPI trusted publishing
|
|
37
|
+
steps:
|
|
38
|
+
- uses: actions/checkout@v4
|
|
39
|
+
with:
|
|
40
|
+
fetch-depth: 0 # the version is a commit count; a shallow clone cannot count
|
|
41
|
+
|
|
42
|
+
- name: Derive the version from the commit count
|
|
43
|
+
id: version
|
|
44
|
+
run: |
|
|
45
|
+
set -euo pipefail
|
|
46
|
+
base=$(grep -m1 '^version = ' pyproject.toml | cut -d'"' -f2 | cut -d. -f1,2)
|
|
47
|
+
patch=$(git rev-list --count HEAD)
|
|
48
|
+
version="${base}.${patch}"
|
|
49
|
+
echo "Releasing ${version}"
|
|
50
|
+
sed -i "0,/^version = .*/s//version = \"${version}\"/" pyproject.toml
|
|
51
|
+
echo "value=${version}" >> "$GITHUB_OUTPUT"
|
|
52
|
+
|
|
53
|
+
- name: Build sdist + wheel
|
|
54
|
+
run: pipx run build
|
|
55
|
+
|
|
56
|
+
- name: Publish to PyPI
|
|
57
|
+
uses: pypa/gh-action-pypi-publish@release/v1
|
|
58
|
+
with:
|
|
59
|
+
skip-existing: true # a re-run of an already-published commit is a no-op
|
|
@@ -0,0 +1,143 @@
|
|
|
1
|
+
# CLAUDE.md
|
|
2
|
+
|
|
3
|
+
## Rules
|
|
4
|
+
|
|
5
|
+
- **Commits**: No `Co-Authored-By` lines. Single-line messages (no body). Same convention as
|
|
6
|
+
OpenOutFind, OpenOutSend and OpenOutLearn.
|
|
7
|
+
- **Always work on `main`.** Never create or switch to a feature branch.
|
|
8
|
+
- **Every green push to `main` is a release.** `.github/workflows/deploy.yml` runs the tests, then
|
|
9
|
+
derives the version from the commit count and publishes to PyPI via trusted publishing
|
|
10
|
+
(environment `pypi`). `needs: test` is the whole gate.
|
|
11
|
+
- **No memory**: never use the auto-memory system.
|
|
12
|
+
- **No roadmap here.** Work is tracked in `openoutreach-docs/roadmap/AgenticFSM/`. The design,
|
|
13
|
+
the milestones and what was weighed and not taken are in
|
|
14
|
+
`p1-e3-agentic-fsm-first-version.md` there. Read it before changing the interface.
|
|
15
|
+
- **This is a general-purpose library.** Nothing from OpenOutreach's domain (deals, leads,
|
|
16
|
+
batches) goes in the code, the docstrings, the README or the tests. The example everywhere is
|
|
17
|
+
a shop `Order`. A machine for a real domain lives in the repo that uses the library, as models
|
|
18
|
+
live in a Django project and not in Django.
|
|
19
|
+
- **The core imports no database.** Anything a state backend needs (Django, a driver) is
|
|
20
|
+
imported inside that backend's package and is an optional extra in `pyproject.toml`. Pydantic
|
|
21
|
+
AI is the library's one dependency: a model deciding a move is part of the core, not an extra.
|
|
22
|
+
- **Every default is a setting.** A default value is declared in `conf/global_settings.py` and
|
|
23
|
+
read as `settings.NAME`, never written where it's used and never read from `os.environ` there.
|
|
24
|
+
|
|
25
|
+
## Project Overview
|
|
26
|
+
|
|
27
|
+
`agentic_fsm` keeps entity lifecycles: many rows that each sit in a state for days and are moved
|
|
28
|
+
by whoever knows something new. A machine is three plain Python things.
|
|
29
|
+
|
|
30
|
+
- **States** (`states.py`): declared like Django model fields, `pending = InitialState("...")`.
|
|
31
|
+
`_StatesMeta` replaces each declaration with its stored value before the enum is built, so the
|
|
32
|
+
class is a real `str` enum (`Order.paid == "paid"`, usable as a Pydantic type) whose members
|
|
33
|
+
keep their description and kind. The description is required; it's the state's definition.
|
|
34
|
+
- **Steps**: a named function of the entity that returns the next state (or a `Decision`), or
|
|
35
|
+
`None` for "not now"; or an `Ask`, which puts the question to a model (see *Ask*).
|
|
36
|
+
- **Transitions**: one list of `(from, to, step)` rows; `from` may be a tuple. A step's allowed
|
|
37
|
+
targets out of a state are the rows it sits on there.
|
|
38
|
+
|
|
39
|
+
`Machine(states, rows, load=, backend=, name=)` (`machine.py`) checks the declaration and raises
|
|
40
|
+
`MachineError` naming the state or row. Then:
|
|
41
|
+
|
|
42
|
+
| Call | Does |
|
|
43
|
+
|---|---|
|
|
44
|
+
| `start(id)` | puts an entity in the initial state; `AlreadyStarted` if it has one |
|
|
45
|
+
| `fire(id, step)` | runs one step (the function, the `Ask` or its name); returns the logged `Move`, or `None` for "not now" |
|
|
46
|
+
| `fire(id, step, entity=)` | the same, on the entity already in hand instead of `load(id)` (`brief` takes it too) |
|
|
47
|
+
| `fire(id, step, answer=)` | decides an `Ask` in the model's place; no model call, the prompt doesn't run |
|
|
48
|
+
| `brief(id, step)` | the `Brief` an `Ask` would give the model: instructions, prompt, choices, schema, tools |
|
|
49
|
+
| `advance()` | per unfinished entity, tries the steps out of its state in list order and stops at the first that doesn't return `None`: at most one move per entity per call |
|
|
50
|
+
| `state_of(id)`, `in_state(state)`, `history(id)` | reads |
|
|
51
|
+
| `graph()` | states and rows as data |
|
|
52
|
+
|
|
53
|
+
A result outside the step's rows, or one that isn't a state, is logged as a refused `Move`
|
|
54
|
+
(`applied=False`, with a `reason`) and never applied. `fire` raises `TransitionError` when the
|
|
55
|
+
move can't even be tried (unknown step, entity not started, step doesn't leave the state). Entity
|
|
56
|
+
ids are stored as text, so `load` receives a string. The machine never opens a transaction around
|
|
57
|
+
a step: a step may send an email or call a model.
|
|
58
|
+
|
|
59
|
+
## Ask
|
|
60
|
+
|
|
61
|
+
`ask.py` holds `Decision` (a Pydantic model whose one field is `to`), `Ask(name=, prompt=,
|
|
62
|
+
agent= | schema=)` and `Brief`. The `Agent` is Pydantic AI's and is the whole model-side
|
|
63
|
+
definition; without one, `Ask` builds an agent for the `ASK_MODEL` setting with the schema as
|
|
64
|
+
its output type, with the model check deferred so no key is needed until it runs.
|
|
65
|
+
|
|
66
|
+
- **Run**: `Ask.run(entity, targets)` calls the prompt function (falsy: "not now", no call),
|
|
67
|
+
then `agent.run_sync(prompt, deps=entity, output_type=<narrowed schema>)`. The narrowed schema
|
|
68
|
+
is a copy whose `to` is a `Literal` of the step's targets out of the entity's state, with each
|
|
69
|
+
state's description in the field's description. The machine checks the result against the rows
|
|
70
|
+
afterwards either way. A model that keeps answering outside them raises Pydantic AI's
|
|
71
|
+
`UnexpectedModelBehavior`, and nothing is logged.
|
|
72
|
+
- **Answer**: `Ask.parse(answer, targets)` validates a dict, a JSON object or a bare state value
|
|
73
|
+
against the same narrowed schema. The machine logs an invalid one as a refused move.
|
|
74
|
+
- **Logged**: `decided_by` is `llm:<provider>:<model>` for a run, `agent` for an answer and
|
|
75
|
+
`code` for a function, and `Move.decision` holds the whole `Decision`.
|
|
76
|
+
- `Brief.instructions` and `Brief.tools` read the agent's plain-text instructions (a private
|
|
77
|
+
attribute of `Agent`) and its function tools. `tests/test_ask.py` fails if Pydantic AI moves
|
|
78
|
+
either.
|
|
79
|
+
|
|
80
|
+
Tests use Pydantic AI's `TestModel`; `models.ALLOW_MODEL_REQUESTS = False` keeps any test from
|
|
81
|
+
reaching a real model.
|
|
82
|
+
|
|
83
|
+
## CLI
|
|
84
|
+
|
|
85
|
+
`cli.py` is the console script `agfsm` (`main(argv)` returns the exit code), on `argparse` and
|
|
86
|
+
nothing else. It adds no behaviour: each command loads the machine (`--machine
|
|
87
|
+
package.module:name`, or the `MACHINE` setting) and calls one `Machine` method, `show` →
|
|
88
|
+
`graph()`, `start`, `list` → `in_state`, `fire` → `fire` / `brief` (`--agent`) /
|
|
89
|
+
`fire(answer=)` (`--answer`), `advance`. Each command returns a `Result` (the data for `--json`,
|
|
90
|
+
the text, the exit code: 0 applied or "not now", 1 refused, 2 can't be tried).
|
|
91
|
+
|
|
92
|
+
- An entity is `<machine name>:<id>`, checked against the loaded machine; a state given to
|
|
93
|
+
`list` is its stored value.
|
|
94
|
+
- `--machine` and `--json` go before or after the command: the subcommands' copies default to
|
|
95
|
+
`argparse.SUPPRESS` so they don't erase one given before.
|
|
96
|
+
- The working directory goes on `sys.path`, as `python -m` would put it.
|
|
97
|
+
- With `DJANGO_SETTINGS_MODULE` set, `backends/django/project.py:setup_project` runs before the
|
|
98
|
+
machine's module is imported, since that module usually imports the project's models.
|
|
99
|
+
- Pydantic AI's first-run banner goes to stderr, and never for a run an installed package
|
|
100
|
+
starts, so `--json` output stays clean.
|
|
101
|
+
|
|
102
|
+
`tests/test_cli.py` drives `main(argv)` on both backends with machines it puts in
|
|
103
|
+
`tests/machines.py`, the module `--machine tests.machines:orders` names.
|
|
104
|
+
|
|
105
|
+
## Settings
|
|
106
|
+
|
|
107
|
+
`conf/global_settings.py` lists every setting with its default (`BACKEND`, `ASK_MODEL`,
|
|
108
|
+
`MACHINE`), and
|
|
109
|
+
`conf/__init__.py` holds `settings`, as Django's `django.conf` does. A read takes the first of:
|
|
110
|
+
`settings.configure(...)`, the env var `AGENTIC_FSM_<NAME>`, the module named by
|
|
111
|
+
`AGENTIC_FSM_SETTINGS_MODULE`, the default. Nothing is cached, so import order doesn't matter. A
|
|
112
|
+
name `global_settings` doesn't declare raises.
|
|
113
|
+
|
|
114
|
+
## State backends
|
|
115
|
+
|
|
116
|
+
Laid out and chosen as Django lays out its database backends: one package per backend, each with
|
|
117
|
+
a `base` module holding a `StateBackend`, picked by the package's dotted path (the `BACKEND`
|
|
118
|
+
setting, e.g. `AGENTIC_FSM_BACKEND=agentic_fsm.backends.django`, or `Machine(..., backend=)`; a
|
|
119
|
+
machine with neither raises). `backends/__init__.py:get_backend` imports `<path>.base` on first use.
|
|
120
|
+
|
|
121
|
+
- `backends/base/base.py`: `BaseStateBackend` (seven calls: `start`, `move`, `refuse`, `current`,
|
|
122
|
+
`in_state`, `all_current`, `history`), plus the `Move` and `Current` dataclasses.
|
|
123
|
+
- `backends/locmem/`: in memory, for tests.
|
|
124
|
+
- `backends/django/`: a Django app (`INSTALLED_APPS = ["agentic_fsm.backends.django"]`, label
|
|
125
|
+
`agentic_fsm`) with two models, `LogEntry` (append-only) and `CurrentState` (one row per
|
|
126
|
+
entity, with a `version`), and their migration. It's the only place Django is imported.
|
|
127
|
+
|
|
128
|
+
Every backend keeps the same two things and the same rule: a move rewrites the entity's
|
|
129
|
+
current-state row and appends its log row in one transaction, and only if the entity's version is
|
|
130
|
+
still the one read before the step ran. A move that finds another version is logged as refused.
|
|
131
|
+
|
|
132
|
+
## Tests
|
|
133
|
+
|
|
134
|
+
```bash
|
|
135
|
+
uv venv && uv pip install -e ".[dev]"
|
|
136
|
+
pytest
|
|
137
|
+
```
|
|
138
|
+
|
|
139
|
+
`tests/conftest.py` holds the example `Order` machine. Its `backend` fixture is parametrized, so
|
|
140
|
+
every test that takes `orders` or `backend` runs once on `locmem` and once on `django`
|
|
141
|
+
(pytest-django, in-memory SQLite, `tests/settings.py`). A new backend is added to that fixture
|
|
142
|
+
and must pass the same tests. After changing a model, write the migration and check
|
|
143
|
+
`DJANGO_SETTINGS_MODULE=tests.settings python -m django makemigrations --check --dry-run`.
|
|
@@ -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 [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.
|