Distillation

2026-09-08

🟡 (21:42) Assistant directly inspected the frozen body source for valkey-github-issue-4276. The source is [NEW] Valkey Samples Repository, an RFC proposing the design, governance model, and contribution framework for valkey-io/valkey-samples as the official home for cookbook tutorials, focused code samples, and integration patterns.

🟡 (21:42) valkey-github-issue-4276 motivation states that Valkey serves caching uses such as rate limiting and pub-sub, is embedded by projects including SpringAI and Mem0, and is expanding into AI/Search use cases including semantic caching, agent memory, prompt routing, and KV caching. It argues that no official repository currently provides working examples with consistent quality, vendor neutrality, and community governance.

🟡 (21:42) valkey-github-issue-4276 says existing alternatives are insufficient: 1. the Valkey documentation site provides command/configuration reference rather than tutorials or runnable integrations; 2. individual contributor repositories lack official endorsement, discoverability, and consistent standards; 3. blog posts/external tutorials are point-in-time snapshots, untested in CI, and not community-maintainable; 4. upstream project documentation does not explain internal architectural choices or offer guidance about using Valkey for key use cases and datastore selection.

🟡 (21:42) valkey-github-issue-4276 lists 5 design principles in order: 1. community-first governance—transparent governance, inclusive decision-making, and rigorous quality; 2. vendor neutrality—avoid vendor lock-in; 3. quality over speed—prefer 3 excellent runnable samples over 30 inconsistent or broken ones; 4. no gatekeeping by complexity—avoid early-access JDKs, unreleased branches, and custom tooling; 5. open design—the RFC is open to community comment before implementation, and contribution must be equally open.

🟡 (21:42) valkey-github-issue-4276 compares 4 project models: 1. redis/redis-om-spring-demo, per-language demo repositories with README and Docker Compose—good self-containment but weak cross-language discoverability; 2. apache/kafka/examples, examples inside the main repository—tight release coupling and a heavy contribution barrier; 3. aws-samples, described as examples within the main repository—good isolation but poor cross-sample consistency; 4. kubernetes/examples, one curated categorized repository—good discoverability but inconsistent long-term maintenance. The proposal combines a single curated repository, self-contained directories, and mandatory CI validation.

🟡 (21:42) valkey-github-issue-4276 defines target audiences: primary—developers already building on Valkey who need reference patterns for new use cases and OSS integrations; primary—first-time evaluators who need examples runnable in under 5 minutes; secondary—operators and SREs who need configuration examples, deployment patterns, and migration guides; secondary—contributors who need examples of features they build and visibility into the wider ecosystem.

🟡 (21:42) valkey-github-issue-4276 explicitly excludes internal tooling experiments, content requiring proprietary or unreleased dependencies, and marketing or sales collateral.

🟡 (21:42) valkey-github-issue-4276 requires every contribution to satisfy 7 acceptance criteria in order: 1. build from a clean clone with publicly available dependencies pinned to specific versions; 2. run against the current stable Valkey release without unreleased branches, unstable Docker tags, or non-GA feature flags; 3. focus on Valkey features, commands, or patterns with minimal application scaffolding; 4. use current stable Valkey client libraries and document client choice rationale; 5. be vendor-neutral by default, with OpenAI or another broadly accessible LLM provider as default and vendor-specific variants allowed only as clearly labeled optional sections covering at least 2 providers equally or linking to provider documentation; 6. include a README describing the demonstrated concept/use case, versioned prerequisites, step-by-step execution, expected output, and relevant Valkey documentation; 7. pass CI on every PR, including dependency installation, compilation/linting, and completion against a Valkey instance.

🟡 (21:42) valkey-github-issue-4276 excludes 4 content types: curated link lists, which belong on the Valkey website or documentation wiki; unreproducible builds relying on unreleased software, private artifacts, or early-access tooling; marketing content containing uncited performance claims, cost comparisons, or promotional language; and single-vendor tutorials requiring one cloud provider’s credentials as the primary path.

🟡 (21:42) valkey-github-issue-4276 defines 3 contribution categories: 1. cookbooks—narrative, step-by-step tutorials with runnable code, including Jupyter notebooks or scripts with narrative READMEs; 2. demos—focused lightweight applications showing one Valkey use case without unrelated authentication, admin, or complex UI concerns; 3. sample apps—more complete, production-style integrations combining multiple use cases, which must document where Valkey-specific code resides and how to navigate to it.

🟡 (21:42) valkey-github-issue-4276 proposes repository root files README.md, CONTRIBUTING.md, LICENSE using BSD-3-Clause or Apache-2.0, and MAINTAINERS.md.

🟡 (21:42) Proposed valkey-samples/ content includes cookbooks/semantic-caching/ with README.md, requirements.txt, main.py, and docker-compose.yml; cookbooks/session-store/ with README.md, package.json, and index.js; and cookbooks/haystack-document-store/ with README.md, requirements.txt, and haystack_document_store.ipynb.

🟡 (21:42) Proposed valkey-samples/ content also includes demos/vector-similarity-search/ with README.md, requirements.txt, main.py, and docker-compose.yml; and samples/ecommerce-catalog/ with README.md, requirements.txt, docker-compose.yml, and src/.

🟡 (21:42) Proposed .github/ content includes .github/ISSUE_TEMPLATE/new-sample.md, .github/ISSUE_TEMPLATE/bug-report.md, .github/PULL_REQUEST_TEMPLATE.md, and workflows .github/workflows/validate-samples.yml for building and running every sample, .github/workflows/lint-markdown.yml for Markdown linting and link checking, and .github/workflows/label-sync.yml.

🟡 (21:42) valkey-github-issue-4276 lists 3 structural decisions: 1. every directory is self-contained and independently runnable; 2. content is categorized into cookbooks/, demos/, and samples/; 3. there are no nested language directories, with language instead included in flat directory names such as cache-aside-python/ and cache-aside-java/.

🟡 (21:42) The directly displayed frozen source for valkey-github-issue-4276 reaches ### 5. Governance Model, then #### Maintainers, and truncates mid-sentence after: “The repository has its own MAINTAINERS.md following the same model as other valkey-io repositorie”. Consequently, the complete maintainer rules and remaining governance model are unavailable in the frozen bytes.