convert_sdk 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 16cc235aa36baea77098bf6d47a5d479e840ca95a416b36b87f8f178b95895c1
+  data.tar.gz: 1354d6d78384ebea2f6b187ae601da34e7090de152fc6ca4fa95480e406c04a0
+SHA512:
+  metadata.gz: 5fc43abd0fbf174055ef97a00c3c983f232287f886151990931f2635a733fcd0a626e1b35a7f7ef564b2953bcc3cee32b6fe7cb96a9e9ba7dce40b5dfc2e7ae7
+  data.tar.gz: 74e704ae66077b55a6e92a008a44933190208f8b3caaacefbea041801b4e9bfe8e8498f082205bfa71b4901834ed9cca2ce5d3e80b5e317848e4fc4a2b925e6e

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,191 @@
+plugins:
+  - rubocop-performance
+
+AllCops:
+  TargetRubyVersion: 3.1
+  NewCops: enable
+  SuggestExtensions: false
+  Exclude:
+    - "bin/**/*"
+    - "vendor/**/*"
+    # RBS signature files are not Ruby; exclude from all cops.
+    - "**/*.rbs"
+    # The demo Rails app (Story 5.2) is an APP, not the gem's lib — it lives
+    # under demo/ purely to exercise the SDK end-to-end under a real Puma cluster.
+    # It must NOT enter the gem's quality gates (RuboCop here, SimpleCov coverage,
+    # RBS/Steep typing): its Rails-idiomatic style, its smoke script, and its
+    # boot files follow different conventions and would pollute the gem's offense
+    # count and coverage %. The gemspec already excludes every demo/ path from the
+    # package; this keeps the LINT gate equally clean. (SimpleCov tracks only
+    # lib/ — see spec/spec_helper.rb — so the demo never enters coverage; RBS/Steep
+    # only check sig/ against lib/, never demo/.)
+    - "demo/**/*"
+
+# Every .rb file MUST start with the frozen-string-literal magic comment.
+Style/FrozenStringLiteralComment:
+  Enabled: true
+  EnforcedStyle: always
+
+Style/StringLiterals:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Style/StringLiteralsInInterpolation:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Layout/LineLength:
+  Max: 120
+
+# RBS inline type annotations (`#: Type`) are deliberately written without a
+# space after `#` — that exact form is what Steep parses. The hardened HTTP
+# port (Story 1.5) uses them to type empty-literal seams (`{} #: Hash[...]`)
+# at the single Net::HTTP site. Allow the RBS-inline form for this cop.
+Layout/LeadingCommentSpace:
+  AllowRBSInlineAnnotation: true
+
+# Specs use long descriptive blocks; the default 25-line block limit is noise
+# for RSpec example groups and the SimpleCov config block in spec_helper.
+Metrics/BlockLength:
+  Exclude:
+    - "spec/**/*"
+    - "*.gemspec"
+    - "Rakefile"
+    - "spec/spec_helper.rb"
+
+Metrics/MethodLength:
+  Max: 20
+
+# The Client and DataManager are the two files Story 2.7's config-caching /
+# background-refresh / lazy-TTL feature extends — the architecture mandates "no
+# new lib files" for that story (refresh logic in the Client, snapshot + TTL
+# bookkeeping in the DataManager), so the cohesive feature surface lands inside
+# these two existing classes rather than being split across new files. The
+# resulting length is a deliberate architecture decision, not unmanaged growth.
+# RuleManager (Story 2.10) is added on the same principle: the OR->AND->OR_WHEN
+# walk levels + leaf evaluation + validation are one cohesive unit mirroring the
+# JS rule-manager.ts class — length is the walk surface, not unmanaged growth.
+# Context (Story 2.11) joins for the same reason: the per-visitor public API
+# (create/attributes/lookups from 2.8 + run_experience(s) decision entry points)
+# is one cohesive surface mirroring the JS context.ts class — the orchestration
+# itself lives in DataManager/ExperienceManager, Context just wires the entry
+# points, fires the lifecycle event, and holds the never-crash boundary.
+Metrics/ClassLength:
+  Exclude:
+    - "lib/convert_sdk/client.rb"
+    - "lib/convert_sdk/data_manager.rb"
+    - "lib/convert_sdk/rule_manager.rb"
+    - "lib/convert_sdk/context.rb"
+    # FeatureManager (Story 3.1) ports feature-manager.ts (the run_feature /
+    # run_features resolution surface) PLUS the castType truth table
+    # (types-utils.ts). The two cohesive JS modules it mirrors are the unit; the
+    # length reflects the ported reference surface, not unmanaged growth (same
+    # rationale as the DataManager/RuleManager feature surfaces above).
+    - "lib/convert_sdk/feature_manager.rb"
+
+# The Client (Story 2.5) is wired by explicit constructor injection of its six
+# collaborator managers (config, log, http, data-store, event, data) — the
+# architecture mandates constructor injection throughout with no globals or
+# singletons, so each dependency is a named keyword argument rather than being
+# hidden inside an options bag. The Context (Story 2.8) follows the same
+# injection contract and adds the two per-visitor values it binds (visitor_id +
+# attributes) on top of its five injected managers. Story 2.11 grows the
+# injection surface again: the DataManager gains its decision-flow collaborators
+# (bucketing_manager, rule_manager, account/project resolvers) and the Context
+# gains the experience_manager. Because every one of these is a NAMED keyword
+# argument (self-documenting at the call site — the readability problem the cop
+# guards against applies to positional lists, not keyword injection), keyword
+# args are excluded from the count; the positional limit stays at 7.
+Metrics/ParameterLists:
+  Max: 7
+  CountKeywordArgs: false
+
+# get_visitor_data / get_config_entity (Story 2.8) are FROZEN public-API parity
+# names mirroring the JS SDK surface (getVisitorData/getConfigEntity,
+# context.ts:495,549). The get_ prefix is mandated by the cross-SDK naming
+# contract, not an accessor-naming slip, so the cop is disabled for the Context.
+Naming/AccessorMethodName:
+  Exclude:
+    - "lib/convert_sdk/context.rb"
+
+# MurmurHash3 uses the canonical algorithm variable names from Austin Appleby's
+# reference implementation (h1 = hash state, k1 = block key). Renaming them would
+# break the line-by-line auditability of the vendored implementation against the
+# reference, so they are explicitly allowed as method parameter names.
+Naming/MethodParameterName:
+  AllowedNames:
+    - h1
+    - k1
+
+# The 13 rule operators (Story 2.10) port the JS SDK comparisons.ts signatures
+# verbatim: each takes a trailing positional `negation` boolean so RuleManager
+# can dispatch uniformly across all operators (processor[matching](value, rule
+# value, negation), mirroring rule-manager.ts:299-319). Keyword-izing it would
+# break the uniform positional dispatch and diverge from the JS contract.
+Style/OptionalBooleanParameter:
+  Exclude:
+    - "lib/convert_sdk/comparisons.rb"
+
+# is_in / does_not_exist are the snake_case mirrors of the FROZEN wire operator
+# names isIn / doesNotExist (the two-worlds rule for operator dispatch — the
+# dispatch-map keys stay byte-identical to the rule JSON match_type, the Ruby
+# methods underneath are snake_case). is_rule_matched (RuleManager, Story 2.10)
+# is the snake_case mirror of the FROZEN cross-SDK public API name isRuleMatched
+# (rule-manager.ts:99). The predicate-prefix cop would force in?/not_exist?/
+# rule_matched?, breaking those naming contracts.
+Naming/PredicatePrefix:
+  Exclude:
+    - "lib/convert_sdk/comparisons.rb"
+    - "lib/convert_sdk/rule_manager.rb"
+
+# custom_dimension_1 .. custom_dimension_5 (Story 4.3) are the snake_case mirrors
+# of the FROZEN wire goal-data keys customDimension1 .. customDimension5
+# (the two-worlds rule — the public track_conversion goal_data: kwarg surface is
+# snake_case symbols, the wire identifiers stay camelCase via GoalDataKey). The
+# trailing digit is part of the cross-SDK key name, not a variable-numbering
+# slip; normalcasing them to custom_dimension1 would break the public contract
+# and the snake↔camel mapping. Allowed as identifiers for this cop.
+Naming/VariableNumber:
+  AllowedIdentifiers:
+    - custom_dimension_1
+    - custom_dimension_2
+    - custom_dimension_3
+    - custom_dimension_4
+    - custom_dimension_5
+
+# cast_boolean is one branch of the symmetric cast_* helper family (cast_boolean
+# / cast_integer / cast_float / cast_json) that mirrors the JS castType switch
+# (types-utils.ts:13-54) one-to-one. Only the boolean branch happens to return a
+# bool; renaming it cast_boolean? would break the deliberate one-name-per-cast-
+# branch symmetry (the others return Integer/Float/parsed-JSON, not predicates).
+Naming/PredicateMethod:
+  Exclude:
+    - "lib/convert_sdk/feature_manager.rb"
+
+# Comparisons is a cohesive 13-operator + numeric-helper module; the operator
+# set is the unit, not unmanaged growth. (Mirrors the ClassLength rationale for
+# the Client/DataManager feature surfaces.)
+Metrics/ModuleLength:
+  Exclude:
+    - "lib/convert_sdk/comparisons.rb"
+
+# The frozen value objects (BucketedVariation, BucketedFeature) are declared as
+# explicit `class X < Struct.new(...)` subclasses. This is the form the
+# architecture mandates ("frozen Struct subclass") AND the only form Steep can
+# statically resolve: methods defined in a `Struct.new(...) do ... end` block are
+# mis-attributed by Steep to the enclosing module (Ruby::UndeclaredMethodDefinition),
+# whereas the subclass form attributes #error?/#initialize to the class as the RBS
+# declares. The Style/StructInheritance preference is overridden here for that reason.
+Style/StructInheritance:
+  Exclude:
+    - "lib/convert_sdk/bucketed_variation.rb"
+    - "lib/convert_sdk/bucketed_feature.rb"
+    - "lib/convert_sdk/http_client.rb"
+
+# The steep/ directory holds the build-time config-contract probe (qs-03). The
+# probe re-opens `module ConvertSdk` as a CI-only utility file (OUTSIDE lib/,
+# never required at runtime). The module is already documented in lib/
+# convert_sdk.rb; the probe re-opening does not warrant a second top-level doc.
+Style/Documentation:
+  Exclude:
+    - "steep/**/*"

data/.yardopts

@@ -0,0 +1,16 @@
+--output-dir doc
+--markup markdown
+--protected
+--no-private
+--readme README.md
+--title "Convert Ruby SDK"
+lib/**/*.rb
+-
+CONTRIBUTING.md
+docs/quickstart-rails.md
+docs/quickstart-sidekiq.md
+docs/quickstart-lambda.md
+docs/quickstart-cli.md
+docs/troubleshooting.md
+docs/migrate-from-kameleoon.md
+LICENSE

data/CONTRIBUTING.md

@@ -0,0 +1,131 @@
+# Contributing to the Convert Ruby SDK
+
+Thanks for contributing. This guide covers the dev setup, the conventions CI
+enforces, the test layout, and how releases happen.
+
+## Development setup
+
+Requires Ruby ≥ 3.1 (the gem supports CRuby 3.1–3.4 and JRuby).
+
+```sh
+bundle install        # install dev/test dependencies
+bundle exec rake      # the default task: RSpec + RuboCop
+```
+
+Type checking (RBS + Steep) lives in a separate Gemfile group so the JRuby
+matrix leg can skip the C-extension build:
+
+```sh
+bundle exec rbs -r net-http -r uri -r json -I sig validate   # validate RBS signatures
+bundle exec steep check                                      # static type check
+```
+
+The gem has **zero runtime dependencies** by design (stdlib only). Adding a
+runtime dependency is an architecture change, not a routine PR — discuss it
+first. All dev/test gems live in the `Gemfile`.
+
+## Conventions CI enforces
+
+The **Quality Checks** workflow (`.github/workflows/qa.yml`) gates every PR:
+
+- **RuboCop** — `bundle exec rubocop` must pass (config in `.rubocop.yml`).
+  Notably: frozen-string-literal magic comment on every file, double-quoted
+  strings, 120-char lines.
+- **RBS + Steep** — signatures in `sig/` must validate and type-check against
+  `lib/`.
+- **RSpec** — the full suite runs on the CRuby 3.1–3.4 + JRuby matrix, with
+  coverage gates (see below).
+- **Cross-SDK parity** — the 75-vector MurmurHash3 parity suite must pass 100%
+  (a byte-identical-bucketing release gate).
+- **Full-chain + gem-smoke + demo fork-smoke** — end-to-end release gates.
+
+### Conventional Commits + squash merge
+
+This repo is **squash-merge only**, so the **PR title** becomes the squash commit
+subject — and CI validates it as a [Conventional Commit](https://www.conventionalcommits.org/):
+
+```
+<type>(<scope>)?!?: <description>
+```
+
+Allowed types: `feat`, `fix`, `docs`, `test`, `refactor`, `perf`, `build`, `ci`,
+`chore`. A `feat` or `fix` (or a `!` breaking-change marker) drives the next
+release version (see below), so title accuracy matters.
+
+Examples:
+
+```
+feat(context): add run_features bulk evaluation
+fix(api): retain queue on a failed flush POST
+docs(readme): document the sentinel return contract
+```
+
+### Coverage gates
+
+Coverage is single-sourced in `spec/spec_helper.rb` (do not declare thresholds
+elsewhere). The global floor is 85% line coverage; the critical algorithm units
+(Hashing, Bucketing, Rules) require ≥ 95% line **and** branch coverage. Coverage
+runs on CRuby only — the JRuby leg runs the suite without the gate.
+
+## Test layout
+
+| Directory | What lives there |
+|-----------|------------------|
+| `spec/unit/` | Per-class unit specs (mock collaborators, isolated logic). |
+| `spec/integration/` | End-to-end specs: `full_chain_spec.rb` (the release-blocking create→decide→track→flush loop), `runtime_recipes_spec.rb` (the runtime-lifecycle recipes the quickstarts are transcribed from), `fork_safety_spec.rb`, `factory_wiring_spec.rb`. |
+| `spec/cross_sdk/` | The cross-SDK MurmurHash3 parity vectors (the byte-identical bucketing proof). |
+| `spec/docs/` | Docs-snippet smoke specs — run the README/quickstart code samples against the real gem so documentation never drifts. |
+| `spec/staging/` | The live-platform suite (runs on schedule/dispatch only, never in PR CI). |
+| `spec/support/` | Shared helpers (e.g. `runtime_recipe_helpers.rb`, which co-locates the recipe wiring snippets the quickstarts ship). |
+| `spec/fixtures/` | Vendored config fixtures (`test-config.json`). |
+| `demo/rails/` | The living Rails example app + fork-safety smoke (an app, not the lib — excluded from gem/RuboCop/coverage gates). |
+
+When adding a documented code sample, **copy it from a working spec or the demo**
+and add it to the `spec/docs/` smoke spec — never ship doc-only code that can
+drift from the real gem.
+
+## Testing & verification
+
+Run the default gate before opening a PR:
+
+```sh
+bundle exec rake      # RSpec + RuboCop — the same pair CI enforces
+```
+
+See the **[Testing wiki page](https://github.com/convertcom/ruby-sdk/wiki/Testing)**
+for the full command reference: individual RSpec invocations, the RBS/Steep type-check
+commands, the cross-SDK parity gate, the full-chain release gate, and the Puma-cluster
+fork smoke. Do not change the coverage configuration — it is single-sourced in
+`spec/spec_helper.rb` (see **Coverage gates** above).
+
+## API documentation (YARD)
+
+All public classes and methods are YARD-documented; `@api private` internals are
+excluded from the published docs (`.yardopts` sets `--no-private`). Build the
+docs locally with:
+
+```sh
+bundle exec yard doc                 # output to doc/
+bundle exec yard stats --list-undoc  # audit the public surface
+```
+
+The published docs deploy to [GitHub Pages](https://convertcom.github.io/ruby-sdk)
+on every push to `main` (`.github/workflows/pages.yml`).
+
+## Releases
+
+Releases are **fully automated** and run only from `main` — there is **no**
+`rake release` task (it is deliberately absent from the `Rakefile`). The release
+pipeline (semantic-release in `.github/workflows/release.yml`) reads the merged
+Conventional Commit subjects since the last release, computes the next semantic
+version, tags it, and publishes the gem to RubyGems via OIDC Trusted Publishing.
+The changelog is **GitHub Releases** (there is no `CHANGELOG.md` in the repo).
+
+You never bump the version or publish manually — write an accurate PR title and
+the pipeline does the rest on merge.
+
+See **[RELEASE.md](RELEASE.md)** for the full release runbook: the release chain,
+the Conventional-Commit → version map, one-time repo-admin setup (RubyGems
+trusted-publisher registration, GitHub Pages, branch-protection required checks),
+dry-runs, the first `v1.0.0` release, the fork-PR safeguard, rollback (`gem
+yank`), and troubleshooting.

data/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.