Dashboard › institutional-transition-lab › Distillation
76d67fb9-9b59-431f-83d1-1ad545cb9b43["lore_tm_v1_6Zb7CzBO2NatEGIibfp-st0Pm0E3uG3QufYtS-YN8aE","lore_tm_v1_QGiiCyLxXx0-pJtoQ8bJIHUzDkDkEUWkMN86_JyVpgA","lore_tm_v1_AbR_Q64B7vwSWJZWkZbfPcXpdjPYliWh9Kzp54hOAro","lore_tm_v1_r3BNQyi21Ez4Uxmm3mJmXVOW1UAWuR_C0Tmu1ZOqhek","lore_tm_v1_ecGXbHIejdffaWDlRrJZ4zcrUXXxqyjxCKWwJq_a5q8"]
valkey-github-issue-4276, valkey-github-pr-2927, and valkey-github-pr-345.valkey-github-issue-4276, titled [NEW] Valkey Samples Repository, proposes an official valkey-io/valkey-samples repository governed for consistent quality, vendor neutrality, community contribution, and runnable Valkey cookbooks, demos, and sample apps.valkey-github-issue-4276 body was truncated in its Governance Model at “The repository has its own MAINTAINERS.md following the same model as other valkey-io repositorie”.valkey-github-issue-4276 RFC principles are ordered: 1. community-first governance; 2. vendor neutrality; 3. quality over speed, preferring 3 excellent runnable samples to 30 inconsistent/broken/misleading ones; 4. no gatekeeping through early-access JDKs, unreleased branches, or custom tooling; 5. open RFC design and contribution paths.valkey-github-issue-4276 RFC defines 3 contribution categories: 1. cookbooks/ for narrative tutorials with runnable code, including Jupyter notebooks or scripts plus README; 2. demos/ for lightweight single-use-case applications without unrelated concerns; 3. samples/ for fuller applications combining multiple Valkey use cases, with mandatory navigation guidance to Valkey-specific code.valkey-samples/ root artifacts are README.md, CONTRIBUTING.md, LICENSE (BSD-3-Clause or Apache-2.0), and MAINTAINERS.md; example content includes cookbooks/semantic-caching/, cookbooks/session-store/, cookbooks/haystack-document-store/, demos/vector-similarity-search/, and samples/ecommerce-catalog/.valkey-samples/ are .github/ISSUE_TEMPLATE/new-sample.md, .github/ISSUE_TEMPLATE/bug-report.md, .github/PULL_REQUEST_TEMPLATE.md, and workflows .github/workflows/validate-samples.yml, .github/workflows/lint-markdown.yml, and .github/workflows/label-sync.yml.valkey-github-issue-4276 structural decisions require each sample directory to be independently runnable, categorize content as cookbooks/, demos/, or samples/, and avoid nested language directories by putting language in flat directory names such as cache-aside-python/ and cache-aside-java/.valkey-github-pr-2927, “Refine major decision process and update TSC composition rules,” was merged with 1 changed file; base_sha=5940dbfb0b601dfc565ca7f349a3a62f67d7e5ed, head_sha=8d92a6e1392df217d841b869f581aa0c49542cb2, and merge_commit_sha=cd6faaa726791447f7adc196b6c77cc20658112d. (meaning Dec 12, 2025)valkey-github-pr-2927 patch limits employees, contractors, or representatives of one organization or affiliated organizations to no more than 1/3 of the TSC; excess affiliation must be reported promptly, compliance restored promptly, and resolution targeted within 30 days with documented steps.valkey-github-pr-2927 patch defines technical major decisions as fundamental core-data-structure changes, new data structures/APIs, backward-compatibility changes, maintained user-visible fields, and adding/removing an external library such as a client or module when runtime behavior is affected.valkey-github-pr-2927, technical major decisions use simple-majority approval when obtainable; if no simple majority is reached within a 2-week voting period and no TSC member votes against, explicit +2 support from at least 2 TSC members may approve the decision, with a TSC-member author/proposer’s +1 counting toward +2.valkey-github-pr-2927, any negative TSC vote blocks the +2 path and requires simple-majority voting; concerns after a +2 approval must be raised through a new major-decision process rather than retracting the approval directly.valkey-github-pr-2927 defines governance major decisions as adding or involuntarily removing TSC members, modifying the governance document, delegating project maintainership or governance authority, creating/modifying/removing project roles, changing voting rules/TSC responsibilities/project oversight, or structurally changing the TSC including composition limits; these require a 2/3 affirmative vote of the entire TSC.valkey-github-pr-2927 establishes that voting ties preserve the status quo, involuntary TSC removal follows the Governance Major Decision process, and delegation of project decision-making is a Governance Major Decision.valkey-github-pr-345, “Initial PR outlining the governance for the project,” was merged with 3 changed files; base_sha=4693aa258e993ebde96f68f608224884e5c8317d, head_sha=8cb7eae5919fe42da841aec43df0b5f5b58e7f37, and merge_commit_sha=b283c6b508792892d76b9a4911e3086e37518748. (meaning Apr 30, 2024)valkey-github-pr-345 placed all current and future Valkey-io repositories under a TSC composed of main Valkey repository maintainers, gave the TSC oversight of all technical, project, approval, and policy matters, required at least a 2/3 affirmative TSC vote to add/remove maintainers or amend governance, and allowed the TSC to add/remove non-main-repository members and other-repository maintainers.valkey-github-pr-345 voting rules preferred documented consensus; major decisions and failures to reach consensus triggered votes, each TSC member had 1 vote, voting remained open at least 2 weeks, and ordinary votes required a simple majority unless otherwise specified.valkey-github-pr-345 included core-data-structure changes, new data structures/APIs, backward-compatibility changes, maintained user-visible fields, governance-document modifications, adding project roles, delegating project maintainership, and adding/removing external libraries such as clients or modules.valkey-github-pr-345 termination rules were resignation by written notice, removal by 2/3 TSC vote, or simple-majority removal by remaining active TSC members after more than 6 months of unresponsiveness.valkey-github-pr-345 created MAINTAINERS.md with 6 initial maintainers in alphabetical GitHub-ID order: Zhu Binbin (enjoy-binbin, Tencent), Wen Hui (hwware, Huawei), Madelyn Olson (madolson, Amazon), Ping Xie (pingxie, Google), Zhao Zhao (soloestoy, Alibaba), and Viktor Söderqvist (zuiderkwast, Ericsson).valkey-github-pr-2927: Luna A classified it effective_institutional_change, event_kind=control_rights, body_patch_relation=patch_supersedes_body, confidence 0.96, announced 2025-12-11, effective 2025-12-12; Luna B classified it effective_institutional_change, event_kind=board_or_steering, body_patch_relation=consistent, confidence 0.98, with the same dates. (meaning Dec 11-12, 2025)valkey-github-pr-2927: approve technical major decisions; approve governance major decisions; set TSC organization-affiliation composition; remove TSC members involuntarily; and approve delegation of decision-making for projects.valkey-github-pr-2927: modified simple-majority approval of technical major decisions; added +2 approval when no majority is reached within 2 weeks and nobody votes against; added 2/3 approval of governance major decisions; and modified involuntary-removal authority over TSC members.valkey-github-pr-2927 was schema-invalid but substantively classified the record effective_institutional_change, event_kind=board_or_steering, body_patch_relation=patch_supersedes_body, confidence 0.92, announced 2025-12-11, effective 2025-12-12; it coded modified TSC rights over the 1/3 affiliation limit, technical-major-decision approval, governance-major-decision approval, and delegation of project decision-making. (meaning Dec 11-12, 2025)valkey-github-pr-2927: the body described simple-majority voting for non-technical decisions, whereas the merged patch made governance major decisions subject to a 2/3 threshold; both treated the patch as controlling, while Luna B marked body and patch consistent.source_id and quotations would remain separate from the truncated frozen body.valkey-io/valkey#4276 came from https://api.github.com/repos/valkey-io/valkey/issues/4276; issue ID 4993704331, node ID I_kwDOLjzmI88AAAABKaXhiw, author jbrinkman, label enhancement, state open, 2 comments, no assignee/milestone, created 2026-07-28T00:52:23Z, and updated 2026-08-10T16:03:48Z. (meaning Jul 28-Aug 10, 2026)valkey-github-issue-4276 completes the governance section: the repository gets its own MAINTAINERS.md; initial maintainers are appointed by the TSC; additional maintainers use the standard nomination process; and maintainers review PRs, enforce quality standards, and ensure vendor neutrality.valkey-samples contribution workflow is ordered: 1. contributor opens a new-sample proposal describing Valkey concept, target language, and scope; 2. a maintainer approves or requests changes before implementation; 3. contributor submits a PR under CONTRIBUTING.md; 4. at least 1 maintainer reviews acceptance criteria, vendor neutrality, code/documentation quality, and CI; 5. a maintainer merges after approval and green CI.valkey-samples CI checks are Markdown linting via markdownlint, URL checking via lychee or markdown-link-check, independent dependency installation via language-specific tools such as pip, npm, or gradle, language-specific code linting, execution against a Valkey Docker container, and a GitHub Actions matrix preventing broken builds; CI runs on every PR and weekly.localhost:6379 or environment variables; OpenAI or provider-agnostic LLM interfaces; production guidance covering at least 2 providers equally or remaining generic with external links; community clients such as valkey-py, valkey-java, or GLIDE rather than vendor-specific wrappers; README affiliation disclosures such as “Strands Agents is an Amazon open-source project”; and balanced curated links.README, CONTRIBUTING, MAINTAINERS, LICENSE, and CI workflows; no existing content is grandfathered in, and every contribution must undergo the standard workflow, acceptance review, vendor-neutrality review, removal of private/internal/unreleased dependencies, CI validation, and public visibility.valkey-samples launch plan is ordered: Phase 1 Foundation—merge the RFC after discussion, revert existing content to a clean slate, then create CONTRIBUTING.md, MAINTAINERS.md, LICENSE, CI workflows, and issue/PR templates; Phase 2 Initial Samples—submit 3-5 samples through proposal → approval → implementation → review → merge, use them as reference examples, and validate Docker/lint/execution CI end-to-end; Phase 3 Community Growth—announce guidelines, accept community contributions, and expand coverage based on demand and Valkey releases.valkey-github-issue-2961, Luna A classified the kernel-level hot-key-detection request as control_event, event_kind=product, body_patch_relation=body_only, confidence 0.98, announced 2025-12-22, no effective date or power changes; Luna B likewise classified it control_event, event_kind=product, body_patch_relation=not_applicable, confidence 0.98; Terra classified it no_event, confidence 0.99, with null dates/scope/event kind and no power changes. (meaning Dec 22, 2025)valkey-github-issue-3289, all 3 coders classified the proposed Valkey Improvement Proposal process as proposal_only, event_kind=control_rights, announced 2026-03-02, no effective date, because the source showed no adoption or implementation. (meaning Mar 2, 2026)valkey-github-issue-3289: binding vote holders—active committers or TSC members—would approve foundational changes through at least a 2/3 +1 majority; confidences were 0.99, 0.98, and 0.98, respectively.valkey-github-pr-1788, Luna A classified visible license-header standardization as an effective control_event, event_kind=license, body_patch_relation=consistent, confidence 0.91, announced/effective 2025-02-27, but noted the truncated patch selection prevented assessment of omitted changes. (meaning Feb 27, 2025)valkey-github-pr-1788, Luna B and Terra abstained because the patch selection was truncated and visible normalization did not establish a substantive licensing-rights change; both used event_kind=license, body_patch_relation=unclear, no effective date, and confidences 0.55 and 0.38, respectively.