Dashboard › institutional-transition-lab › Distillation
a36c6cd5-f1c8-4e89-879e-20784c2f59b3["lore_tm_v1_oiMRm9kLMI4z2iyf1M169Azh9vRPH53sF10aDKZcPTI","lore_tm_v1_aXNCOcqIvc8wfhJGWjzmFQ64CvVXjt0Jy_UFht5Uo-Q","lore_tm_v1_3OpdZLqCIIFjJg6Qze1ojR2KWj2baxsjoNmbPiaXV9w"]
Date: Sep 8, 2026
valkey-io/valkey PR #1390, “Update governance and maintainers file for Valkey committers”: it separated committers from maintainers because adding two people with commit access would otherwise make them TSC members; committers were defined as having write access, while maintainers have full repository access and own governance; both roles must be listed in each repository’s MAINTAINERS.md. (meaning Dec 4–9, 2024)#1390 added a Current Committers section listing, in alphabetical GitHub-ID order: 1. Harkrishn Patro (hpatro, Amazon), 2. Ran Shidlansik (ranshid, Amazon); it also renamed Former Maintainers to Former Maintainers and Committers. The PR changed 2 files and merged as 4f61034934cf165163ef272e5795bccadc288b09. (meaning Dec 9, 2024)#1788, “Consistent look and feel of licenses”: standardized Valkey file notices, used SPDX-License-Identifier: BSD-3-Clause rather than BSD 3-Clause, normalized the copyright line to Copyright (c) Valkey Contributors, placed Valkey notices before documentation, and added separate Valkey BSD-3-Clause notices after inherited Redis license blocks where appropriate. The PR resolved issue #1692, referenced licensing documentation in PR #1787, changed 31 files, and merged as 089b830479f4984e77e570560f85e37212879740. (meaning Feb 27, 2025)#2927, “Refine major decision process and update TSC composition rules”: introduced separate Technical Major Decision and Governance Major Decision processes, a technical +2 fallback, a one-third organizational representation limit, tie preservation of the status quo, and clarified delegation/governance changes. It changed 1 file and merged as cd6faaa726791447f7adc196b6c77cc20658112d. (meaning Dec 11–12, 2025)#2927 made the TSC composition rule effective: no more than one third (1/3) of TSC members may represent the same organization or affiliated organizations; “organization” includes companies, corporations, universities, research institutes, non-profits, governmental institutions, subsidiaries, and affiliates. Exceedance must be reported promptly, corrective action must be taken, and the TSC should resolve and document compliance-restoration steps within 30 days.#2927 defined Technical Major Decisions as: 1. fundamental Valkey core data-structure changes, 2. a new data structure or API, 3. backward-compatibility changes, 4. new user-visible fields requiring maintenance, 5. adding/removing an external library such as a client or module when runtime behavior is affected.#2927 use simple-majority approval when obtainable. If no simple majority is reached within a two-week voting period and no TSC member votes against, explicit +2 support from at least 2 TSC members may approve it; a proposer’s +1 counts if the proposer is a TSC member. Any negative TSC vote disables the +2 path, and later objections to an approved +2 decision require a new major-decision process rather than retracting the approval.#2927 defined Governance Major Decisions, requiring a 2/3 affirmative vote of the entire TSC, as: 1. adding or involuntarily removing TSC members, 2. changing GOVERNANCE.md, 3. delegating project maintainership or governance authority, 4. creating/modifying/removing Valkey roles, 5. changing voting rules, TSC responsibilities, or oversight, 6. structurally changing the TSC, including composition limits.#2927: every voting TSC member has one vote; voting remains open at least two weeks; ties preserve the status quo; involuntary removal follows the Governance Major Decision process; members unresponsive for over six months may be removed by a simple majority of remaining active members; delegation to another project’s maintainers is a Governance Major Decision; the TSC may overrule other Valkey projects but “shall show restraint.”#345, “Initial PR outlining the governance for the project”: created GOVERNANCE.md, linked it from the contributing guide, and created MAINTAINERS.md; it established the TSC’s oversight of technical, project, approval, and policy matters across current and future Valkey-io repositories. The PR changed 3 files and merged as b283c6b508792892d76b9a4911e3086e37518748. (meaning Apr 21–30, 2024)#345 preferred consensus but allowed voting when consensus failed or an issue/PR was marked a major decision; each TSC member had one vote, voting stayed open at least two weeks, ordinary votes required a simple majority, adding/removing maintainers and amending governance required a 2/3 affirmative TSC vote, and project-maintainership delegation required an explicit major-decision vote.#4508 proposes creating valkey-io/langchain-valkey to host the standalone NPM package @langchain/valkey, implementing LangChainJS’s VectorStore interface with Valkey Search and valkey-glide. The need arose after upstream langchain-ai/langchainjs#9915 was closed because LangChain permanently requires new integrations to be independently published packages. (meaning Aug 24, 2026)@langchain/valkey capabilities are: KNN and range vector similarity search; TAG, TEXT, and NUMERIC metadata filters; custom index schemas; batched pipeline writes; escaped TAG values to prevent query injection; configurable index prefixes; and COSINE, IP, and L2 distance metrics.#4508: 1. personal/company GitHub organization—rejected for reduced discoverability and trust; 2. an existing valkey-io repository—rejected because the package needs an independent build, test, and release lifecycle; 3. waiting for LangChainJS to resume in-repository integrations—rejected because its guidelines and maintainer response make independent community packages the permanent model. The proposed naming follows spring-data-valkey, and the discoverability path is a listing PR to langchain-ai/docs.#4508 identifies existing implementation material at daric93/langchainjs, branch feature/valkey-vector-store, directory libs/providers/langchain-valkey/; upstream PR langchain-ai/langchainjs#9915 ran from February–May 2026 with 8 commits and addressed security review. The code requires adaptation for standalone CI, governance documentation, and release infrastructure.#4509 proposes creating valkey-io/n8n-nodes-valkey for the NPM package n8n-nodes-valkey, an n8n community Valkey Vector Store node. It would provide Insert, Load, Get, and Retrieve-as-Tool operations; use @langchain/valkey and transitively valkey-glide; integrate credentials and visual workflow configuration; and support self-hosted Valkey plus AWS ElastiCache, GCP Memorystore, Aiven, and other managed offerings. (meaning Aug 24, 2026)#4509: n8n’s Redis Vector Store node is incompatible with Valkey Search because document insertion attempts to create a TEXT field unsupported in the same way as Redis Stack. Evidence cited includes closed n8n issue #21361, an n8n statement that the Redis node is “simply not compatible with ValKey,” unmerged PR #16592, and users unable to connect n8n to ElastiCache Valkey Serverless.n8n-nodes-valkey capabilities are: KNN and range vector search in n8n’s visual builder; TAG, TEXT, and NUMERIC metadata filtering; automatic embeddings through n8n Embeddings sub-nodes; and Agent Tool retrieval for RAG workflows. @langchain/valkey from issue #4508 is a prerequisite, so langchain-valkey should be created first.#4509: 1. fix n8n’s Redis node—rejected because n8n explicitly declined compatible-database support; 2. use the LangChain Code Node workaround—rejected because it requires JavaScript, only works on self-hosted n8n, and lacks visual integration; 3. host in a personal organization—rejected for weaker trust, discoverability, maintenance commitment, and n8n verification prospects. The SAP HANA Vector Store community node was cited as a package-structure reference, and n8n-nodes-valkey follows n8n’s mandatory n8n-nodes- prefix.gpt-5.6-luna coders classified valkey-github-issue-2961 as a control_event with event_kind: "product", announced_on: "2025-12-22", no power changes, and confidence 0.98; one used body_patch_relation: "body_only" and the other not_applicable. The gpt-5.6-terra advisory instead classified it no_event, with null event kind/date/scope, body_patch_relation: "not_applicable", no power changes, and confidence 0.99, showing a substantive control-event versus no-event disagreement.valkey-github-issue-3289 is proposal_only, concerns control rights over major Valkey changes, was announced 2026-03-02, has no effective date, uses body_patch_relation: "body_only", and proposes adding a vote right for binding vote holders—active committers or TSC members—over foundational project changes. Confidence was 0.99, 0.98, and 0.98; all noted there was no evidence of adoption or implementation. (meaning Mar 2, 2026)VIP) process applies to major changes across Valkey Core, Modules, Clients, and Tooling, including major features, subsystems, functionality, network protocol/API behavior, AOF/RDB formats, and error/authentication log formats; it complements rather than replaces lightweight workflows for minor changes and bug fixes.VIP-3247: Valkey Sink: Tiered Storage; 2. complete required sections and add it to the tracking index; 3. open a Valkey Contributors Slack thread titled [DISCUSS] VIP-{number} {heading}, link the proposal, iterate on feedback, and communicate changes; 4. call [VOTE] after finalization, using lazy majority and keeping voting open at least 72/96 hours; 5. mark the VIP/index Accepted or Rejected and report the outcome in the voting thread.+1 votes and no binding vetoes; 2. Lazy Majority—3 binding +1 votes and more binding +1 than -1; 3. Lazy Approval—implicitly allowed unless a -1 triggers lazy majority or lazy consensus; 4. 2/3 Majority—at least two thirds of binding vote holders, defined as active committers or TSC members, vote +1, reserved for foundational changes.KIP) process was selected as the model, with terminology adapted for Valkey.