# Apache Maka Roadmap: A Complete Guide to the Incubating Project's Development Plans > Explore the Apache Maka roadmap for this incubating project. Discover development plans and track component updates to stay informed on Maka's evolution. Learn more now. - Repository: [The Apache Software Foundation/maka](https://github.com/apache/maka) - Tags: roadmap - Published: 2026-09-11 --- **The official Apache Maka roadmap is documented in [`docs/archive/qoderwork-mcp-reverse-engineering-2026-07-18.md`](https://github.com/apache/maka/blob/main/docs/archive/qoderwork-mcp-reverse-engineering-2026-07-18.md) under section "## 12. Maka roadmap", while ongoing updates for specific components like the MCP runtime are tracked via GitHub issues such as #4329.** Apache Maka is currently an incubating project at the Apache Software Foundation (ASF), meaning it is undergoing review before potential graduation to a top-level project. The **Apache Maka roadmap** outlines planned milestones and feature priorities, though it resides in archived documentation rather than a dynamically updated file. Understanding where to find these plans is essential for contributors tracking the project's evolution toward full ASF graduation. ## Locating the Official Apache Maka Roadmap The concrete development plans for Apache Maka are not maintained in a continuously updated file at the repository root. Instead, the most recent roadmap information is preserved in the project's documentation archive. ### Primary Roadmap Document According to the source repository, the latest detailed roadmap lives in **[`docs/archive/qoderwork-mcp-reverse-engineering-2026-07-18.md`](https://github.com/apache/maka/blob/main/docs/archive/qoderwork-mcp-reverse-engineering-2026-07-18.md)**. This file contains the section "## 12. Maka roadmap" which enumerates planned milestones, feature priorities, and open items for upcoming releases. ### Archive Context and Limitations The `docs/archive/` directory serves as a historical reference. As noted in **[`docs/archive/README.md`](https://github.com/apache/maka/blob/main/docs/archive/README.md)**, these files provide context but do not constitute current contracts or guarantees. The roadmap may evolve as the project matures, making the archived version a snapshot rather than a dynamic planning document. ## Tracking Component-Specific Updates While the archived document provides the high-level **Apache Maka roadmap**, granular updates for specific subsystems are managed through the issue tracker. The **MCP post-V3 roadmap** is actively discussed in **Issue #4329**, which details future development plans for the MCP runtime component. This issue-based approach allows for community input and transparent iteration on specific technical directions separate from the archived historical documents. ## Programmatically Accessing Roadmap Data Since the roadmap is a documentation artifact rather than a code API, you may need to parse it for internal tooling or documentation generators. The following Node.js example demonstrates how to read the archived roadmap file: ```javascript // Node.js example: read the archived roadmap file import { readFileSync } from 'fs'; const roadmap = readFileSync('docs/archive/qoderwork-mcp-reverse-engineering-2026-07-18.md', 'utf8'); console.log(roadmap); ``` Replace the path with the appropriate location in your clone of the repository. This approach is useful for automation scripts that need to extract milestones or generate internal reports based on the documented plans. ## Summary - The **Apache Maka roadmap** is primarily documented in [`docs/archive/qoderwork-mcp-reverse-engineering-2026-07-18.md`](https://github.com/apache/maka/blob/main/docs/archive/qoderwork-mcp-reverse-engineering-2026-07-18.md) under section "## 12. Maka roadmap". - The project maintains an **incubating status** at the Apache Software Foundation, as declared in the main [`README.md`](https://github.com/apache/maka/blob/main/README.md). - Component-specific roadmaps, such as the MCP post-V3 plans, are tracked via GitHub issues like #4329. - Archive files serve historical purposes and may not reflect the absolute current state, though they represent the most recent formal roadmap available. - You can programmatically access roadmap content using standard file system operations for integration with internal tooling. ## Frequently Asked Questions ### Where is the Apache Maka roadmap officially documented? The official roadmap is located in [`docs/archive/qoderwork-mcp-reverse-engineering-2026-07-18.md`](https://github.com/apache/maka/blob/main/docs/archive/qoderwork-mcp-reverse-engineering-2026-07-18.md) within the section titled "## 12. Maka roadmap". This archived document contains the most recent formal listing of milestones and feature priorities for the incubating project. ### Is Apache Maka still an Apache Incubator project? Yes. According to the main [`README.md`](https://github.com/apache/maka/blob/main/README.md), Apache Maka is labeled **"Apache Maka (Incubating)"**, indicating it remains under review by the Apache Software Foundation and has not yet graduated to top-level project status. ### How can I find updates to the MCP runtime roadmap specifically? Updates for the MCP runtime component are tracked in **Issue #4329** titled "MCP post-V3 roadmap". This GitHub issue provides the most current discussion and planning details for that specific subsystem, supplementing the broader archived roadmap document. ### Why is the roadmap stored in an archive folder rather than a living document? The `docs/archive/` directory, as explained in [`docs/archive/README.md`](https://github.com/apache/maka/blob/main/docs/archive/README.md), preserves historical context and snapshots of project planning. While this means the roadmap is not continuously updated in real-time, it ensures that development history remains accessible while allowing the project to evolve its planning processes through issues and proposals.