streamcase 0.1.0a1__tar.gz

streamcase-0.1.0a1/.gitignore

@@ -0,0 +1,34 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.python-version
+
+# Environments
+.venv/
+venv/
+
+# Build and test output
+build/
+dist/
+.coverage
+coverage.xml
+htmlcov/
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+
+# IDE and OS files
+.idea/
+.vscode/
+.DS_Store
+Thumbs.db
+
+# Local project scratch space
+.tmp/
+
+# Spark local output
+metastore_db/
+spark-warehouse/
+derby.log
+

streamcase-0.1.0a1/CHANGELOG.md

@@ -0,0 +1,62 @@
+# Changelog
+
+All notable changes will be documented in this file. The format is based on
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and releases follow
+[Semantic Versioning](https://semver.org/).
+
+## [Unreleased]
+
+No changes yet.
+
+## [0.1.0a1] - Candidate (not published)
+
+This prerelease is prepared but has no publication date yet. See the
+[first-alpha release notes](docs/releases/0.1.0a1.md) for the tested support
+matrix and known limitations. Add the publication date only after #99 verifies
+the release.
+
+### Added
+
+- Clean wheel and sdist installation smoke checks for the core package and the
+  supported Spark combination.
+- Trusted Publishing release flow with checked tag provenance and SHA-256
+  verification across the Actions-artifact transfer to PyPI.
+- Public `Restart` execution that rebuilds the Spark stream and resumes later
+  batches with the same checkpoint, query settings, and output capture.
+- A private Spark query lifecycle controller with idempotent stop and
+  restart-safe writer configuration.
+- A two-batch public Spark runner quick start and matching integration test.
+- Public `streamcase.spark.run_scenario` API with caller-owned session,
+  transformation validation, and optional PySpark installation guidance.
+- Validated Spark query output modes and non-conflicting writer options for the
+  private scenario runner.
+- Managed cleanup for runner-owned Spark queries and run directories, preserving
+  execution failures when cleanup also fails.
+- Immutable `ScenarioResult` assembly after successful Spark batch execution,
+  ready for the existing result assertions.
+- Ordered `Batch` execution with one published input file and a Spark
+  `processAllAvailable()` barrier per action.
+- Immutable driver-side capture of Spark `foreachBatch` output, including empty
+  output batches and recursively converted nested values.
+- A deterministic Spark JSON file-stream source with explicit schemas and
+  runner-owned discovery options.
+- Atomic publication of deterministic JSON Lines files for scenario batches.
+- Isolated runner-owned input, checkpoint, and temporary directory layouts.
+- Dedicated Java 17 and PySpark 4.2 integration-test CI lane.
+- Optional `spark` extra for the supported PySpark 4.2 line and its compatibility
+  policy.
+- Immutable `Batch` scenario action and `batch()` convenience constructor.
+- Immutable `Restart` lifecycle action and `restart()` convenience constructor.
+- Immutable ordered `Scenario` model and `scenario()` convenience constructor.
+- Initial package scaffold.
+- Packaging, licensing, governance, and contribution documentation.
+- Issue forms, pull-request template, and automated quality gates.
+- Roadmap for incremental implementation.
+
+### Changed
+
+- Restart failures identify the failed transition and retry cleanup of a
+  replacement query registered before Spark raises, preserving cleanup errors
+  alongside the original failure.
+- Package and distribution metadata now read the version from one source.
+- Release automation now rejects tags that do not match the package version.

streamcase-0.1.0a1/CONTRIBUTING.md

@@ -0,0 +1,156 @@
+# Contributing to Streamcase
+
+Streamcase uses an issue-first, review-first workflow inspired by established
+Apache projects. The project is not an Apache Software Foundation project.
+
+## Before writing code
+
+1. Search existing issues and pull requests.
+2. Open an issue describing the problem, proposed behavior, and acceptance
+   criteria. Use the
+   [design proposal form](https://github.com/SEPURI-SAI-KRISHNA/streamcase/issues/new?template=design.yml)
+   for public API, architecture, compatibility, backend, or other consequential
+   decisions.
+3. Wait for scope agreement when the change affects public APIs, compatibility,
+   security, or architecture.
+4. Create a branch containing the issue number, such as
+   `feat/123-watermark-actions` or `fix/456-progress-parsing`.
+
+Direct code commits to `main` are not accepted.
+
+Significant changes remain labeled `needs-decision` until their contract and
+rationale are recorded publicly. Merging an issue-linked design record accepts
+the decision; implementation continues through separate focused issues and pull
+requests.
+
+Maintainers classify incoming work using the
+[issue triage and label guide](docs/maintainers/triage.md). Labels communicate
+scope and state, but do not replace acceptance criteria or review.
+
+## Development setup
+
+Create and activate a virtual environment, then install development dependencies:
+
+```shell
+python -m venv .venv
+python -m pip install --upgrade pip
+python -m pip install -e ".[dev]"
+```
+
+Run the local quality gates:
+
+```shell
+ruff format --check .
+ruff check .
+mypy
+pytest -m "not spark"
+python -m build
+python -m twine check dist/*
+```
+
+Use `ruff format .` to apply formatting locally.
+
+Spark integration tests require a Java 17 JDK and the optional Spark dependency:
+
+```shell
+python -m pip install -e ".[dev,spark]"
+java -version
+python -c "import pyspark; print(pyspark.__version__)"
+pytest -m spark -v
+```
+
+The separate Spark CI workflow runs the same marked tests in local mode. Keep
+ordinary unit tests backend-independent so the core Python matrix remains fast.
+
+## Pull requests
+
+- Link the issue with `Closes #123` in the pull-request description.
+- Keep the pull request focused on one problem.
+- Add or update tests for observable behavior.
+- Update user documentation and the changelog when appropriate.
+- Preserve compatibility unless the issue explicitly approves a breaking change.
+- Resolve every review conversation before merge.
+- Do not force-push after review unless necessary; explain rewritten history.
+
+All protected-branch checks must pass before merge. A pull request opened by a
+contributor requires approval from a maintainer who is not the author.
+
+While the project has only one maintainer, a maintainer-authored pull request
+cannot receive genuine independent approval from that same person. It may merge
+only after the maintainer:
+
+1. links a scoped issue and reviews the complete pull-request diff;
+2. confirms every required check passes;
+3. resolves every review conversation and records material decisions publicly;
+4. verifies that every commit carries the required DCO sign-off; and
+5. observes any additional waiting period, including the seven-day public-comment
+   period for governance changes.
+
+This process is a documented self-review, not an approval. The
+[CODEOWNERS](.github/CODEOWNERS) file records current responsibility and requests
+review where GitHub can do so; it does not bypass branch protection or turn an
+author's review into independent approval.
+
+When the project has a second active maintainer who can review without
+deadlocking development, branch protection should require at least one approving
+review and code-owner review. Until then, the issue, pull request, protected
+checks, conversation-resolution, and sign-off requirements remain mandatory.
+
+## Commit sign-off
+
+Contributors certify the Developer Certificate of Origin 1.1 by signing off each
+commit:
+
+```shell
+git commit -s -m "feat: add watermark action"
+```
+
+The sign-off asserts that you have the right to submit the contribution under the
+project license. Read the DCO at <https://developercertificate.org/>.
+
+The `DCO sign-off` check validates every non-merge human commit in a pull
+request. Each trailer must use the following form, and its name and email must
+match the commit author's or committer's identity:
+
+```text
+Signed-off-by: Random J Developer <random@developer.example.org>
+```
+
+Amend an unsigned commit with `git commit --amend --signoff`. If more than one
+commit is missing a sign-off, rewrite each affected commit with an interactive
+rebase. Rewriting published commits changes their identifiers, so coordinate
+with other contributors and explain any necessary force-push on the pull
+request. A later remediation commit does not repair an earlier unsigned commit,
+and maintainers cannot override a failed check.
+
+Recognized dependency-update bots are exempt because they cannot certify the
+DCO as a person. Repository owners, maintainers, and other human contributors
+are not exempt. GitHub web-based commits must also include a sign-off.
+
+A DCO sign-off is a contribution certification. It is not a cryptographic commit
+signature, copyright assignment, or substitute for code review.
+
+## Commit messages
+
+Use a concise Conventional Commit style where practical:
+
+- `feat: add checkpoint restart action`
+- `fix: preserve duplicate output rows`
+- `docs: explain Spark compatibility`
+- `test: cover state-row assertion`
+- `ci: validate Spark 4.x`
+
+## Compatibility changes
+
+Changes to supported Python or Spark versions require:
+
+- a dedicated issue;
+- CI evidence;
+- a changelog entry;
+- documentation updates; and
+- maintainer approval.
+
+## Reporting security issues
+
+Follow [SECURITY.md](SECURITY.md). Never include an unpatched vulnerability in a
+public issue or pull request.

streamcase-0.1.0a1/LICENSE

@@ -0,0 +1,202 @@
+                                 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 2026 Sepuri Sai Krishna
+
+   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.
+

streamcase-0.1.0a1/NOTICE

@@ -0,0 +1,9 @@
+Streamcase
+Copyright 2026 Sepuri Sai Krishna
+
+This product is licensed under the Apache License, Version 2.0.
+
+Apache Spark, Spark, Apache Flink, and Flink are trademarks of the Apache
+Software Foundation. This product is not affiliated with or endorsed by the
+Apache Software Foundation.
+

streamcase-0.1.0a1/PKG-INFO

@@ -0,0 +1,146 @@
+Metadata-Version: 2.5
+Name: streamcase
+Version: 0.1.0a1
+Summary: Deterministic testing for Apache Spark Structured Streaming pipelines
+Project-URL: Homepage, https://github.com/SEPURI-SAI-KRISHNA/streamcase
+Project-URL: Documentation, https://github.com/SEPURI-SAI-KRISHNA/streamcase/tree/main/docs
+Project-URL: Issues, https://github.com/SEPURI-SAI-KRISHNA/streamcase/issues
+Project-URL: Repository, https://github.com/SEPURI-SAI-KRISHNA/streamcase
+Project-URL: Changelog, https://github.com/SEPURI-SAI-KRISHNA/streamcase/blob/main/CHANGELOG.md
+Project-URL: Security, https://github.com/SEPURI-SAI-KRISHNA/streamcase/blob/main/SECURITY.md
+Author: Sepuri Sai Krishna
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: apache-spark,pyspark,pytest,structured-streaming,testing
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Information Technology
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.10
+Provides-Extra: dev
+Requires-Dist: build<2,>=1.2; extra == 'dev'
+Requires-Dist: mypy<2,>=1.15; extra == 'dev'
+Requires-Dist: pytest-cov<8,>=6; extra == 'dev'
+Requires-Dist: pytest<10,>=8.3; extra == 'dev'
+Requires-Dist: ruff<1,>=0.11; extra == 'dev'
+Requires-Dist: twine<8,>=7; extra == 'dev'
+Provides-Extra: spark
+Requires-Dist: pyspark<4.3,>=4.2; extra == 'spark'
+Provides-Extra: test
+Requires-Dist: pytest-cov<8,>=6; extra == 'test'
+Requires-Dist: pytest<10,>=8.3; extra == 'test'
+Description-Content-Type: text/markdown
+
+# Streamcase
+
+[![CI](https://github.com/SEPURI-SAI-KRISHNA/streamcase/actions/workflows/ci.yml/badge.svg)](https://github.com/SEPURI-SAI-KRISHNA/streamcase/actions/workflows/ci.yml)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](https://github.com/SEPURI-SAI-KRISHNA/streamcase/blob/main/LICENSE)
+
+Streamcase is an early-development pytest-oriented toolkit for deterministic Apache Spark
+Structured Streaming tests.
+
+> **Status:** the Spark runner, including checkpoint-preserving restart actions,
+> scenario model, results, and assertions are implemented. No release is published yet.
+> The proposed [first-alpha scope](https://github.com/SEPURI-SAI-KRISHNA/streamcase/blob/main/ROADMAP.md#first-alpha-candidate-010a1) is
+> narrower than the longer-term roadmap.
+
+The [0.1.0a1 candidate notes](docs/releases/0.1.0a1.md) describe the tested
+support matrix and limitations. Publication is tracked separately in #99.
+
+## Problem
+
+Ordinary DataFrame assertions do not exercise streaming semantics such as
+micro-batch boundaries, late data, watermarks, checkpoint restarts, or state
+growth. Streamcase will make those behaviors explicit and reproducible in Python
+tests while executing against Spark's public Structured Streaming interfaces.
+
+## Installation
+
+Until the first PyPI release, install the lightweight backend-independent
+package from this checkout with:
+
+```shell
+python -m pip install -e .
+```
+
+Install the approved PySpark line for the Spark runner from this checkout with:
+
+```shell
+python -m pip install -e ".[spark]"
+```
+
+The Spark extra keeps PySpark out of the core dependency set. See the
+[Spark compatibility policy](https://github.com/SEPURI-SAI-KRISHNA/streamcase/blob/main/docs/spark-compatibility.md) for the supported
+Python, Java, and Spark combination.
+
+## Available today
+
+Streamcase can describe immutable logical input batches and checkpoint-preserving
+restart boundaries, represent captured output, and assert row equality, batch
+counts, and unique keys without importing PySpark. The public Spark runner
+executes batches and restarts against a caller-owned session. See the
+[scenario model guide](https://github.com/SEPURI-SAI-KRISHNA/streamcase/blob/main/docs/scenario-model.md) and
+[results and assertions guide](https://github.com/SEPURI-SAI-KRISHNA/streamcase/blob/main/docs/results-and-assertions.md), plus the
+[two-batch Spark quick start and runner contract](https://github.com/SEPURI-SAI-KRISHNA/streamcase/blob/main/docs/spark-runner.md) and
+[checkpoint restart example](https://github.com/SEPURI-SAI-KRISHNA/streamcase/blob/main/docs/restart-scenarios.md).
+
+## Planned capabilities
+
+- progress, watermark, and state-store assertions;
+- pytest fixtures;
+- compatibility testing across supported Spark releases.
+
+These items are roadmap goals, not current package features. Each capability has
+its own issue, tests, documentation, and pull request.
+
+## Repository status
+
+This bootstrap establishes:
+
+- Python packaging with a `src` layout;
+- Apache License 2.0 and project governance;
+- issue and pull-request conventions;
+- formatting, linting, type checking, tests, and package validation in CI;
+- security and release policies.
+
+See [ROADMAP.md](https://github.com/SEPURI-SAI-KRISHNA/streamcase/blob/main/ROADMAP.md) for the planned delivery sequence and
+[docs/architecture.md](https://github.com/SEPURI-SAI-KRISHNA/streamcase/blob/main/docs/architecture.md) for the proposed technical shape.
+
+## Local checks
+
+```shell
+python -m venv .venv
+python -m pip install -e ".[dev]"
+ruff format --check .
+ruff check .
+mypy
+pytest -m "not spark"
+python -m build
+python -m twine check dist/*
+```
+
+Spark contributors can run the isolated integration suite with the setup in the
+[contribution guide](https://github.com/SEPURI-SAI-KRISHNA/streamcase/blob/main/CONTRIBUTING.md#development-setup).
+
+## Contributing
+
+All material work starts with a GitHub issue and reaches `main` only through a
+reviewed pull request. Read [CONTRIBUTING.md](https://github.com/SEPURI-SAI-KRISHNA/streamcase/blob/main/CONTRIBUTING.md) before making a
+change.
+
+## Trademark notice
+
+Apache Spark, Spark, Apache Flink, and Flink are trademarks of the Apache Software
+Foundation. Streamcase is independent software and is not endorsed by the Apache
+Software Foundation.
+
+## License
+
+Licensed under the [Apache License 2.0](https://github.com/SEPURI-SAI-KRISHNA/streamcase/blob/main/LICENSE).