---
# System prepended metadata

title: Valkey Community Wiki

---

---
title: 'Valkey Community Wiki'
---

<div style="
position:fixed;
top: 50px;
right: 20px;
width: 50px;
border-left: 3px solid #007bff;
padding-left: 15px;
background: #ffffff;
box-shadow: -2px 2px 10px rgba(0,0,0,0.05);
z-index: 100;
">
<b>Navigation</b>
[TOC]
</div>

<style>
.markdown-body {
    max-width: 900px !important;
    margin: 0 auto;
}
.guide-card {
    border: 1px solid #e1e4e8;
    border-radius: 6px;
    padding: 1.5em;
    margin-bottom: 2em;
    background-color: #f6f8fa;
}
.step-number {
    background: #232d37;
    color: white;
    border-radius: 50%;
    width: 24px;
    height: 24px;
    display: inline-block;
    text-align: center;
    line-height: 24px;
    margin-right: 10px;
    font-size: 14px;
}
</style>
<img src="https://hackmd.io/_uploads/S1h_aLl5Ze.svg" width=50%>

# Valkey Community Wiki

Welcome to the **Valkey Project** community wiki. Valkey is an open-source, high-performance key-value store hosted by [The Linux Foundation](https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community).

### Quick Links
- [Technical Steering Committee (TSC)](https://github.com/valkey-io/valkey/blob/unstable/GOVERNANCE.md)
- [Community Code of Conduct](https://valkey.io/code_of_conduct/)
- [Main Website](https://valkey.io)

---

## 🚀 Ways to Get Involved

### 1. Contributing to the Valkey Blog
We welcome both **Community** and **Project** focused content. Regardless of the type, all blog journeys begin on GitHub.

:::info
💡 **Crucial First Step**: Before writing, always [Open a GitHub Issue](https://github.com/valkey-io/valkey-io.github.io/issues/new?template=blog_post_template.md) to pitch your idea. This ensures your topic is aligned with the roadmap and prevents duplicate efforts.
:::

#### 📝 Community Blogs
*Focus: Tutorials, use-cases, event recaps, and integrations.*

:::spoiler View Community Submission Process
1.  **Pitch it:** Open a [GitHub Issue](https://github.com/valkey-io/valkey-io.github.io/issues) with your topic summary.

2.  **Choose your drafting method (pick what works for you):**
    - 🧑‍💻 **GitHub PR (for contributors comfortable with Git):**  
      You can fork the repo and submit a pull request directly with your blog draft. Make sure to add PR to the issue.
    - 📝 **Google Docs / Word (recommended if you prefer writing first):**  
      Draft your content in Google Docs or Word and share the link in the [submission form](https://form.asana.com/?k=9zh9lhK3yWLavaOi6C0hgA&d=9283783873717).

3.  **Review:** The team will review your submission and provide feedback or next steps.
:::

#### 🛠️ Project Blogs
*Focus: Official releases, deep technical milestones, and governance updates.*

:::spoiler View Technical/Project Submission Process (Zola)
1.  **Issue First:** Open a [blog issue on GitHub](https://github.com/valkey-io/valkey-io.github.io/issues/new?template=blog_post_template.md).
2.  **Fork & Branch:** Fork the [valkey-io.github.io](https://github.com/valkey-io/valkey-io.github.io) repo.
3.  **Author Profile:** Add your headshot to `static/assets/media/authors` and create `authors/yourname.md`.
4.  **Create Content:** * Create folder: `content/blog/yyyy-mm-dd-title'
    * Add file: `index.md`
    * Test locally using `zola serve`.
5.  **Submit PR:** Link your PR to the original GitHub issue.
:::
:::warning
### ⚠️ Contribution Checklist for ALL blogs
1. **Issue First:** Always create an issue prior to drafting.
2. **DCO Sign-off:** We require Developer Certificate of Origin sign-offs. Use the `-s` flag in your commits:
   `git commit -s -m "Your commit message"`
3. **Stay Vendor Neutral:** All contributions must benefit the community as a whole.
---
:::

### 2. Run a Local Meetup
Help grow the Valkey ecosystem by hosting or organizing a local gathering. [Detailed Meetup Charter](https://valkey.io/community/meetup-groups/).

:::info
**Planning a Meetup?** [Fill out this form](https://form.asana.com/?k=9zh9lhK3yWLavaOi6C0hgA&d=9283783873717) to get social media support and promotion from the official Valkey channels.
:::

:::spoiler Meetup Guidelines & Best Practices
#### Goals
* **Educate:** Share real-world Valkey production stories.
* **Connect:** Bridge the gap between maintainers and local users.
* **Grow:** Increase awareness of high-performance open-source infra.

#### Post-Meetup Checklist
* **Share Highlights:** Use `#ValkeyCommunity` on social media.
* **Recap:** Post slides or a short summary to the GitHub discussion board.
* **Feedback:** Ask your local community what they want to see next!
:::

---

### 3. Community Calendar & Meetings
**➡️ [View Valkey Events](https://valkey.io/events/)**

### 4. Contribution Directory by Feature

Valkey is a multi-repository project. Use the guide below to find "Good First Issues" based on your technical interests.

| Feature Area | Tech Stack | Repository | Best For... |
| :--- | :--- | :--- | :--- |
| **Valkey Core** | C | [`valkey-io/valkey`](https://github.com/valkey-io/valkey) | Database internals, performance, & CLI. |
| **Search & AI** | C++ | [`valkey-io/valkey-search`](https://github.com/valkey-io/valkey-search) | Vector search, indexing, & query engines. |
| **Admin Tools** | TypeScript/React | [`valkey-io/valkey-admin`](https://github.com/valkey-io/valkey-admin) | UI/UX, dashboards, & cluster management. |
| **Glide (Clients)** | Rust / Polyglot | [`valkey-io/valkey-glide`](https://github.com/valkey-io/valkey-glide) | Cross-language drivers (Java, Python, Go). |
| **Documentation** | Markdown | [`valkey-io/valkey-doc`](https://github.com/valkey-io/valkey-doc) | Technical writing & examples. |

---

### 🔍 Where to find "Good First Issues"

#### 1. Valkey Search (Indexing & Vector Search)
Perfect for those who enjoy C++ and data structures.
* **Focus:** Improving query parser error messages and adding unit tests for edge-case filters.
* [👉 View Search Issues](https://github.com/valkey-io/valkey-search/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)

#### 2. Valkey Admin (Management Console)
The best place for Frontend and Fullstack developers. 
* **Focus:** Visualizing cluster topology, improving the "Hot Key" dashboard, and UI polishing.
* [👉 View Admin Issues](https://github.com/valkey-io/valkey-admin/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)

#### 3. Valkey Core (The Engine)
If you know C, this is where the magic happens.
* **Focus:** Adding new metrics to `INFO` commands and refactoring legacy code for better readability.
* [👉 View Core Issues](https://github.com/valkey-io/valkey/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)

#### 4. Valkey Glide (Reliable Clients)
Help build the bridge between Valkey and the world's most popular languages.
* **Focus:** Implementing missing commands in specific language wrappers (e.g., Python or Java).
* [👉 View Glide Issues](https://github.com/valkey-io/valkey-glide/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)

:::warning
### ⚠️ Contribution Checklist
1. **Comment First:** Always comment on an issue saying *"I would like to work on this"* before starting.
2. **DCO Sign-off:** We require Developer Certificate of Origin sign-offs. Use the `-s` flag in your commits:
   `git commit -s -m "Your commit message"`
3. **Stay Vendor Neutral:** All contributions must benefit the community as a whole.

### ⚖️ Project Leadership & Governance
::::info
**Learn about the roles and responsibilities**

:::spoiler Leadership & Governance Details
### Meet the Leadership
Valkey is a community-led project under **The Linux Foundation**. Our governance is designed to be transparent, meritocratic, and vendor-neutral.

👉 **[Official Leadership Directory](https://valkey.io/leadership/)**

---

#### 🏗️ Governance Bodies
* **Technical Steering Committee (TSC):** Responsible for technical direction, release cycles, and architectural evolution. Members are elected based on merit.
* **Maintainers:** The "boots on the ground" who review code and manage specific repositories (Core, Search, Glide, etc.).

#### 📈 The Contributor Ladder
| Role | Responsibility | How to Reach |
| :--- | :--- | :--- |
| **Contributor** | Submits code or docs. | Open your first Pull Request. |
| **Member** | Regular contributor. | Sponsorship by a Maintainer. |
| **Maintainer** | Approves/Merges PRs. | High-impact, consistent leadership. |
| **TSC Member** | Sets project policy. | Elected by the maintainers. |