Re: [DISCUSS] Incubating Proposal for Maka Agent

[tison]

Hi Huajie,

Thanks for your interest and offering for help. You're added to the
proposed mentor list now.

Best,
tison.


Huajie Wang <benj...@apache.org> 于2026年8月5日周三 21:45写道：

> This is an interesting project, and I’m very interested in this project.I
> was wondering if the project is still looking for a mentor.
> If so, I would be happy to serve as a mentor.
>
>
> Best,
> Huajie Wang
>
>
>
> tison <wander4...@gmail.com> 于2026年8月5日周三 13:50写道：
>
> > Hi IPMC,
> >
> > I would like to propose Maka[1] as a new apache incubator project, you
> can
> > find the proposal[2] of Maka for more detail.
> >
> > [1] https://github.com/maka-agent/maka-agent/
> > [2]
> >
> >
> https://cwiki.apache.org/confluence/spaces/INCUBATOR/pages/446070971/Maka+Proposal
> >
> > Best,
> > tison.
> >
> > Full text of the proposal below:
> >
> > ## Abstract
> >
> > Maka is a local-first AI agent runtime and workspace. It records model
> > messages, tool calls, tool results, permission decisions, and termination
> > events in append-only logs. Sessions, model context, durable tasks, and
> > recovery are derived from those logs, allowing interrupted or
> long-running
> > agent work to be inspected, replayed, resumed, and evaluated.
> >
> > ## Proposal
> >
> > Maka provides a single execution runtime shared by its desktop
> application,
> > terminal TUI, non-interactive CLI, and headless task runner. Its design
> > separates durable execution facts from the temporary context sent to a
> > model.
> >
> > Maka provides:
> >
> > - Append-only execution records. Model messages, tool calls, tool
> results,
> > permission decisions, and termination events are persisted before they
> are
> > projected into user-facing state.
> > - Rebuildable state. Sessions, active context, UI state, and recovery
> > decisions are derived from the event log rather than maintained as
> > independent sources of truth.
> > - Context management without history deletion. Tool-result pruning and
> LLM
> > compaction reduce the context used for the next inference while
> preserving
> > the original execution record.
> > - Durable work beyond one turn. The headless runner gives a task its own
> > identity, event log, budgets, permission pauses, continuation, and resume
> > behavior.
> > - Evidence-based completion. The runtime records a model's completion
> claim
> > separately from verified process and tool outcomes.
> > - Multiple surfaces over one runtime. Maka provides an Electron desktop
> > application, a terminal TUI, a non-interactive CLI, and a headless
> runner.
> >
> > Maka is written primarily in TypeScript and runs on Node.js. Sessions,
> > settings, credentials, and run records remain on the user's machine by
> > default.
> >
> > ## Background
> >
> > An AI agent combines an LLM with tools, permissions, persistent state,
> and
> > a control loop. As tasks become longer, the surrounding runtime must
> handle
> > partial tool execution, context limits, process interruption, permission
> > boundaries, and recovery. Maka focuses on this runtime layer. The public
> > GitHub project was created on 2026-05-27 and has been developed through
> > public issues and pull requests since then.
> >
> > ## Rationale
> >
> > Many agent applications persist a final conversation but not the full
> > execution process that produced it. This makes interrupted work difficult
> > to recover and tool behavior difficult to audit or evaluate. Maka treats
> > execution history as durable evidence and uses that evidence to rebuild
> > state and resume work.
> >
> > The ASF offers neutral ownership, public decision-making, meritocratic
> > community growth, and long-term stewardship. These properties are
> important
> > for an agent runtime intended to support integrations and products
> > maintained by independent organizations.
> >
> > ## Initial Goals
> >
> > - Transfer the codebase to the ASF and complete name, provenance,
> license,
> > and IP clearance.
> > - Conduct technical and governance decisions on the public mailing list.
> > - Document a contributor-to-committer path based on sustained, reviewable
> > contributions.
> > - Broaden ownership across runtime, desktop, integrations, documentation,
> > and release engineering.
> > - Produce an Apache-compliant source release and establish a repeatable
> > release process.
> > - Grow adoption without coupling the project to a single model vendor or
> > commercial sponsor.
> >
> > ## Current Status
> >
> > ### Meritocracy
> >
> > Development takes place through public issues and pull requests.
> > Contributions are reviewed on technical merit, and repeat contributors
> have
> > taken responsibility for runtime, desktop, computer-use, provider, and
> > documentation work. During incubation, the project will make this
> > progression explicit through documented committer criteria and public
> > discussion.
> >
> > ### Community
> >
> > As of 2026-08-03, the repository has 1,104 GitHub stars, 123 forks, and
> 40
> > contributors. In the preceding 30 days, 34 authors contributed commits.
> > Collaboration currently takes place through GitHub issues and pull
> > requests; during incubation, project-wide decisions will move to the
> public
> > development mailing list.
> >
> > ### Core Developers
> >
> > - Jie Wen (jackwener) — project initiator; runtime architecture and
> > distributed-systems design. He is a PMC member and committer of Apache
> > Arrow, Apache DataFusion, and Apache Doris.
> > - Yuhan Lei (Astro-Han) — runtime, evaluation, benchmarking, and desktop
> > development; also an OpenCLI contributor.
> > - Kun Li (likun666661) — runtime event-log architecture, the headless
> task
> > loop, and completion verification.
> >
> > Additional module owners and repeat contributors include Haoqing Wang
> > (hqhq1025, computer-use), Zhanghan Gao (YayoiNanoka), sunheyi6, Nyvo-io,
> > Yongtao Wang (M4n5ter), Colafornia, GabrielDrapor, MicroGery, zhiiw, and
> > others.
> >
> > ### Alignment
> >
> > Maka is intended to be a vendor-neutral runtime used below model
> providers
> > and end-user applications. ASF governance can keep its interfaces,
> > execution records, and extension points independent of any single vendor.
> > The project also shares engineering concerns with ASF data and
> > infrastructure projects, including append-only logs, projections, durable
> > state, and reproducible execution.
> >
> > ## Known Risks
> >
> > ### Project Name
> >
> > A preliminary web and repository search found unrelated uses of "Maka,"
> > including a Chinese design and marketing service and several small
> > open-source projects. None appears to provide the same developer-facing
> AI
> > agent runtime, but this preliminary search is not a substitute for the
> ASF
> > name review. The podling will complete `PODLINGNAMESEARCH` during
> > incubation and will rename the project if required by ASF policy.
> >
> > ### Orphan Products
> >
> > The project is young, so long-term continuity has not yet been
> > demonstrated. The risk is reduced by multiple active maintainers and
> > contributors who already own runtime, desktop, headless, and computer-use
> > components. Incubation will focus on documenting these ownership
> > boundaries, adding committers, and making release knowledge shared rather
> > than person-specific.
> >
> > ### Inexperience with Open Source
> >
> > One initial committer is a PMC member and committer of Apache Arrow,
> Apache
> > DataFusion, and Apache Doris. Several other developers have experience
> > contributing to open-source projects. Most of the proposed community has
> > not yet operated an Apache release or conducted project business on an
> ASF
> > mailing list. The mentors will help the podling establish release,
> voting,
> > IP, and community practices, and those practices will be documented so
> they
> > do not depend on one experienced committer.
> >
> > ### Length of Incubation
> >
> > The project has no fixed graduation deadline. The initial expectation is
> > approximately two years, but graduation will depend on a sustainable and
> > diverse committer base, public governance, shared release ownership, and
> > multiple Apache-compliant releases.
> >
> > ### Homogenous Developers
> >
> > The initial committers currently share overlapping social and
> professional
> > networks, and much real-time coordination occurs in Chinese. They
> > nevertheless represent multiple employers, a university, and independent
> > contributors. The project will conduct decisions and votes in English on
> > the public development mailing list, improve English documentation, and
> > recruit contributors outside the current networks.
> >
> > ### Reliance on Salaried Developers
> >
> > The initial committers represent several employers, a university, and
> > individual contributors; they are not all paid by one organization. Paid
> > work may nevertheless influence where some contributors spend their time.
> > The podling will track affiliation diversity and broaden the committer
> base
> > so development and releases do not depend on one employer or a small
> group.
> >
> > ### Relationships with Other Apache Products
> >
> > Maka does not duplicate an existing ASF product. It operates at the AI
> > agent runtime layer, while sharing concepts with Apache data and
> > infrastructure projects such as append-only logs, projections, and
> durable
> > state. Future integrations may expose ASF storage, data-processing, and
> > observability systems as tools or backends, but no such integration is
> > required for incubation.
> >
> > ### An Excessive Fascination with the Apache Brand
> >
> > The project seeks neutral governance, public decision-making, a
> > meritocratic committer model, and long-term stewardship. The initial
> goals
> > focus on community and release practices rather than promotion under the
> > Apache name.
> >
> > ## Documentation
> >
> > - Repository and README: [
> >
> >
> https://github.com/maka-agent/maka-agent](https://github.com/maka-agent/maka-agent)
> > - Documentation index: [docs/README.md](
> > https://github.com/maka-agent/maka-agent/blob/main/docs/README.md)
> > - Architecture guide: [ARCHITECTURE.md](
> > https://github.com/maka-agent/maka-agent/blob/main/ARCHITECTURE.md),
> with
> > an eight-chapter index and bilingual English/Chinese chapters under
> > [docs/architecture/](
> > https://github.com/maka-agent/maka-agent/tree/main/docs/architecture).
> > - Additional design and verification documents cover computer-use safety,
> > execution evidence, durable workspaces, permissions, skills, and
> > evaluation.
> >
> > ## Initial Source
> >
> > The source is currently hosted at [
> >
> >
> https://github.com/maka-agent/maka-agent](https://github.com/maka-agent/maka-agent)
> > .
> > The public repository was created on 2026-05-27 and is licensed under the
> > Apache License, Version 2.0. If the proposal is accepted, the repository
> > will move to [
> >
> >
> https://github.com/apache/incubator-maka](https://github.com/apache/incubator-maka)
> > .
> > A future project website will use [https://maka.apache.org](
> > https://maka.apache.org).
> >
> > ## Source and Intellectual Property Submission Plan
> >
> > The existing source is licensed under the Apache License, Version 2.0.
> > Before or during code transfer, the podling will:
> >
> > - Obtain ICLAs from all initial committers and determine with the
> Incubator
> > PMC whether a Software Grant or CCLA is required for any contributed
> code.
> > - Verify the provenance of the initial codebase and identify code owned
> by
> > contributors or their employers.
> > - Bring source headers, `LICENSE`, and `NOTICE` files into line with ASF
> > policy.
> > - Remove, replace, or relicense any code or asset that cannot be
> > contributed to the ASF.
> > - Re-run dependency and assembled-artifact license audits before the
> first
> > Apache release.
> >
> > ### External Dependencies
> >
> > Maka is a TypeScript monorepo. Most of the runtime is implemented in
> Maka's
> > own workspace packages; the repository currently has 33 direct
> third-party
> > production dependencies. The full transitive closure is larger and is
> > generated from `package-lock.json` for each release rather than
> maintained
> > by hand in this proposal.
> >
> > The dependencies fall into five groups:
> >
> > - Runtime and user interfaces. Node.js (currently 22.19 or later) runs
> the
> > shared runtime, CLI, and headless surfaces. Electron/Chromium hosts the
> > desktop application. React and Astryx provide the desktop UI, while
> > `@earendil-works/pi-tui` provides the terminal TUI. The CLI and headless
> > runner do not require Electron or React.
> > - Model access. The Apache-2.0 Vercel `ai` SDK and its Anthropic, Cohere,
> > Google, OpenAI, and OpenAI-compatible adapters normalize model-provider
> > protocols. Maka does not require a particular commercial model service
> or a
> > Maka-operated control plane. A user may configure a remote provider or a
> > local compatible endpoint; credentials remain local and are not part of
> any
> > release.
> > - Agent protocols and local execution. `@modelcontextprotocol/sdk`
> > implements MCP interoperability. `node-pty` and the headless xterm
> packages
> > provide interactive shell sessions and terminal emulation,
> > `fs-native-extensions` provides cross-process file locking, and
> > `@jackwener/opencli` provides browser automation over CDP. Smaller
> > libraries such as `undici`, `ws`, `yaml`, and `zod` handle networking,
> > configuration, and validation.
> > - Optional integrations. Slack, Lark/Feishu, and WeCom SDKs are used only
> > when the user enables the corresponding bot channel. These services are
> > integrations, not infrastructure required to build or start Maka.
> > - Build and test tooling. TypeScript, esbuild, Vite, Electron Builder,
> > Playwright, Storybook, and Tailwind CSS build and test the project; Biome
> > provides linting and formatting. These tools are not loaded by the CLI or
> > headless runtime. Build outputs that enter a binary release are covered
> by
> > the release audit described below.
> >
> > #### License and Release Treatment
> >
> > On 2026-08-03, this inventory was regenerated and verified after `npm ci`
> > in a clean checkout. The result matches the checked-in file and records
> 239
> > production npm packages: 180 MIT, 21 Apache-2.0, 19 ISC, 15
> BSD-3-Clause, 2
> > BSD-2-Clause, 1 Python-2.0, and 1 BlueOak-1.0.0. These are ASF Category A
> > licenses, and that inventory records no Category X dependency.
> >
> > Generated npm inventory (exact `package@version`, grouped by selected
> > license)
> >
> > The following list is generated from the exact `@maka/desktop` production
> > dependency closure in `package-lock.json` by
> > `scripts/generate-third-party-notices.mjs`:
> >
> > - Apache-2.0 (21)
> >   - `@ai-sdk/anthropic@4.0.16`
> >   - `@ai-sdk/cohere@4.0.11`
> >   - `@ai-sdk/gateway@4.0.23`
> >   - `@ai-sdk/google@4.0.18`
> >   - `@ai-sdk/openai-compatible@3.0.12`
> >   - `@ai-sdk/openai@4.0.16`
> >   - `@ai-sdk/provider-utils@5.0.11`
> >   - `@ai-sdk/provider@4.0.3`
> >   - `@jackwener/opencli@1.8.4`
> >   - `@mozilla/readability@0.6.0`
> >   - `@vercel/oidc@3.2.0`
> >   - `@workflow/serde@4.1.0`
> >   - `ai@7.0.31`
> >   - `bare-addon-resolve@1.10.1`
> >   - `bare-module-resolve@1.12.4`
> >   - `bare-semver@1.1.0`
> >   - `class-variance-authority@0.7.1`
> >   - `fs-native-extensions@1.5.0`
> >   - `long@5.3.2`
> >   - `require-addon@1.2.0`
> >   - `which-runtime@1.4.0`
> > - BSD-2-Clause (2)
> >   - `@mixmark-io/domino@2.2.0`
> >   - `json-schema-typed@8.0.2`
> > - BSD-3-Clause (15)
> >   - `@protobufjs/aspromise@1.1.2`
> >   - `@protobufjs/base64@1.1.2`
> >   - `@protobufjs/codegen@2.0.5`
> >   - `@protobufjs/eventemitter@1.1.1`
> >   - `@protobufjs/fetch@1.1.1`
> >   - `@protobufjs/float@1.0.2`
> >   - `@protobufjs/path@1.1.2`
> >   - `@protobufjs/pool@1.1.0`
> >   - `@protobufjs/utf8@1.1.2`
> >   - `css-mediaquery@0.1.2`
> >   - `fast-uri@3.1.4`
> >   - `intl-messageformat@11.2.12`
> >   - `json-schema@0.4.0`
> >   - `protobufjs@7.6.5`
> >   - `qs@6.15.3`
> > - BlueOak-1.0.0 (1)
> >   - `sax@1.6.1`
> > - ISC (19)
> >   - `cliui@6.0.0`
> >   - `get-caller-file@2.0.5`
> >   - `graceful-fs@4.2.11`
> >   - `inherits@2.0.4`
> >   - `isexe@2.0.0`
> >   - `lucide-react@0.577.0`
> >   - `lucide-react@1.28.0`
> >   - `once@1.4.0`
> >   - `require-main-filename@2.0.0`
> >   - `semver@7.7.4`
> >   - `set-blocking@2.0.0`
> >   - `setprototypeof@1.2.0`
> >   - `which-module@2.0.1`
> >   - `which@2.0.2`
> >   - `wrappy@1.0.2`
> >   - `y18n@4.0.3`
> >   - `yaml@2.9.0`
> >   - `yargs-parser@18.1.3`
> >   - `zod-to-json-schema@3.25.2`
> > - MIT (180)
> >   - `@astryxdesign/core@0.2.0`
> >   - `@astryxdesign/theme-neutral@0.2.0`
> >   - `@colors/colors@1.5.0`
> >   - `@formatjs/fast-memoize@3.1.7`
> >   - `@formatjs/icu-messageformat-parser@3.5.15`
> >   - `@formatjs/icu-skeleton-parser@2.1.11`
> >   - `@hono/node-server@1.19.15`
> >   - `@larksuiteoapi/node-sdk@1.71.1`
> >   - `@modelcontextprotocol/sdk@1.29.0`
> >   - `@slack/logger@4.0.1`
> >   - `@slack/socket-mode@2.0.7`
> >   - `@slack/types@2.22.0`
> >   - `@slack/web-api@7.19.0`
> >   - `@standard-schema/spec@1.1.0`
> >   - `@stylexjs/stylex@0.19.0`
> >   - `@types/node@25.9.0`
> >   - `@types/retry@0.12.0`
> >   - `@types/ws@8.18.1`
> >   - `@wecom/aibot-node-sdk@1.0.7`
> >   - `@xterm/addon-unicode11@0.9.0`
> >   - `@xterm/headless@6.0.0`
> >   - `accepts@2.0.0`
> >   - `agent-base@6.0.2`
> >   - `ajv-formats@3.0.1`
> >   - `ajv@8.20.0`
> >   - `ansi-regex@5.0.1`
> >   - `ansi-styles@4.3.0`
> >   - `asynckit@0.4.0`
> >   - `axios@1.18.1`
> >   - `body-parser@2.3.0`
> >   - `builder-util-runtime@9.7.0`
> >   - `bytes@3.1.2`
> >   - `call-bind-apply-helpers@1.0.2`
> >   - `call-bound@1.0.4`
> >   - `camelcase@5.3.1`
> >   - `cli-table3@0.6.5`
> >   - `clsx@2.1.1`
> >   - `color-convert@2.0.1`
> >   - `color-name@1.1.4`
> >   - `combined-stream@1.0.8`
> >   - `commander@14.0.3`
> >   - `content-disposition@1.1.0`
> >   - `content-type@1.0.5`
> >   - `content-type@2.0.0`
> >   - `cookie-signature@1.2.2`
> >   - `cookie@0.7.2`
> >   - `cors@2.8.6`
> >   - `cross-spawn@7.0.6`
> >   - `debug@4.4.3`
> >   - `decamelize@1.2.0`
> >   - `delayed-stream@1.0.0`
> >   - `depd@2.0.0`
> >   - `dijkstrajs@1.0.3`
> >   - `dunder-proto@1.0.1`
> >   - `ee-first@1.1.1`
> >   - `electron-updater@6.8.9`
> >   - `emoji-regex@8.0.0`
> >   - `encodeurl@2.0.0`
> >   - `es-define-property@1.0.1`
> >   - `es-errors@1.3.0`
> >   - `es-object-atoms@1.1.2`
> >   - `es-set-tostringtag@2.1.0`
> >   - `escape-html@1.0.3`
> >   - `etag@1.8.1`
> >   - `eventemitter3@4.0.7`
> >   - `eventemitter3@5.0.4`
> >   - `eventsource-parser@3.0.8`
> >   - `eventsource@3.0.7`
> >   - `express-rate-limit@8.6.0`
> >   - `express@5.2.1`
> >   - `fast-deep-equal@3.1.3`
> >   - `finalhandler@2.1.1`
> >   - `find-up@4.1.0`
> >   - `follow-redirects@1.16.0`
> >   - `form-data@4.0.6`
> >   - `forwarded@0.2.0`
> >   - `fresh@2.0.0`
> >   - `fs-extra@10.1.0`
> >   - `function-bind@1.1.2`
> >   - `get-intrinsic@1.3.0`
> >   - `get-proto@1.0.1`
> >   - `gopd@1.2.0`
> >   - `has-symbols@1.1.0`
> >   - `has-tostringtag@1.0.2`
> >   - `hasown@2.0.4`
> >   - `hono@4.12.30`
> >   - `http-errors@2.0.1`
> >   - `https-proxy-agent@5.0.1`
> >   - `iconv-lite@0.7.3`
> >   - `image-dimensions@2.5.1`
> >   - `invariant@2.2.4`
> >   - `ip-address@10.2.0`
> >   - `ipaddr.js@1.9.1`
> >   - `is-electron@2.2.2`
> >   - `is-fullwidth-code-point@3.0.0`
> >   - `is-promise@4.0.0`
> >   - `is-stream@2.0.1`
> >   - `jose@6.2.3`
> >   - `js-tokens@4.0.0`
> >   - `js-yaml@4.3.0`
> >   - `json-schema-traverse@1.0.0`
> >   - `jsonfile@6.2.1`
> >   - `lazy-val@1.0.5`
> >   - `locate-path@5.0.0`
> >   - `lodash.escaperegexp@4.1.2`
> >   - `lodash.identity@3.0.0`
> >   - `lodash.isequal@4.5.0`
> >   - `lodash.merge@4.6.2`
> >   - `lodash.pickby@4.6.0`
> >   - `loose-envify@1.4.0`
> >   - `math-intrinsics@1.1.0`
> >   - `media-typer@1.1.0`
> >   - `merge-descriptors@2.0.0`
> >   - `mime-db@1.52.0`
> >   - `mime-db@1.54.0`
> >   - `mime-types@2.1.35`
> >   - `mime-types@3.0.2`
> >   - `ms@2.1.3`
> >   - `negotiator@1.0.0`
> >   - `node-addon-api@7.1.1`
> >   - `node-pty@1.2.0-beta.14`
> >   - `object-assign@4.1.1`
> >   - `object-inspect@1.13.4`
> >   - `on-finished@2.4.1`
> >   - `p-finally@1.0.0`
> >   - `p-limit@2.3.0`
> >   - `p-locate@4.1.0`
> >   - `p-queue@6.6.2`
> >   - `p-retry@4.6.2`
> >   - `p-timeout@3.2.0`
> >   - `p-try@2.2.0`
> >   - `parseurl@1.3.3`
> >   - `path-exists@4.0.0`
> >   - `path-key@3.1.1`
> >   - `path-to-regexp@8.4.2`
> >   - `pkce-challenge@5.0.1`
> >   - `pngjs@5.0.0`
> >   - `proxy-addr@2.0.7`
> >   - `proxy-from-env@2.1.0`
> >   - `qrcode@1.5.4`
> >   - `range-parser@1.3.0`
> >   - `raw-body@3.0.2`
> >   - `react-dom@19.2.6`
> >   - `react@19.2.6`
> >   - `require-directory@2.1.1`
> >   - `require-from-string@2.0.2`
> >   - `retry@0.13.1`
> >   - `router@2.2.0`
> >   - `safer-buffer@2.1.2`
> >   - `scheduler@0.27.0`
> >   - `send@1.2.1`
> >   - `serve-static@2.2.1`
> >   - `shebang-command@2.0.0`
> >   - `shebang-regex@3.0.0`
> >   - `side-channel-list@1.0.1`
> >   - `side-channel-map@1.0.1`
> >   - `side-channel-weakmap@1.0.2`
> >   - `side-channel@1.1.1`
> >   - `smart-buffer@4.2.0`
> >   - `socks@2.8.9`
> >   - `statuses@2.0.2`
> >   - `string-width@4.2.3`
> >   - `strip-ansi@6.0.1`
> >   - `styleq@0.2.1`
> >   - `tailwind-merge@3.6.0`
> >   - `tiny-typed-emitter@2.1.0`
> >   - `toidentifier@1.0.1`
> >   - `turndown-plugin-gfm@1.0.2`
> >   - `turndown@7.2.4`
> >   - `type-is@2.1.0`
> >   - `undici-types@7.24.6`
> >   - `undici@6.28.0`
> >   - `undici@8.7.0`
> >   - `universalify@2.0.1`
> >   - `unpipe@1.0.0`
> >   - `vary@1.1.2`
> >   - `wrap-ansi@6.2.0`
> >   - `ws@8.21.0`
> >   - `yargs@15.4.1`
> >   - `zod@4.4.3`
> > - Python-2.0 (1)
> >   - `argparse@2.0.1`
> >
> > This inventory is enforced by `scripts/generate-third-party-notices.mjs`.
> > The script walks the exact desktop production closure, rejects missing or
> > unapproved license metadata, records the selected license for
> dual-licensed
> > packages, and generates the complete license text shipped as
> > `THIRD_PARTY_NOTICES.txt`. The source distribution does not vendor
> > `node_modules`. Binary distributions carry separate notices for the npm
> > closure, Electron/Chromium, fonts, and icon assets.
> >
> > Build-only dependencies
> >
> > `lightningcss` (MPL-2.0) and `caniuse-lite` (CC-BY-4.0) are used only to
> > build the desktop application. They are not redistributed as components
> of
> > Maka.
> >
> > Optional macOS dependency
> >
> > The optional macOS computer-use backend uses `cua-driver`, which is based
> > on the MIT-licensed `trycua/cua` project. The `cua-driver` executable and
> > its Rust crates are not included in Maka source or binary distributions.
> > Apache releases ship with this backend disabled, so `cua-driver` is not
> > part of the release dependency inventory above.
> >
> > ### Cryptography
> >
> > Maka is not primarily a cryptographic product; it uses standard TLS/HTTPS
> > libraries for talking to model providers and standard hashing for
> > content-addressed artifacts. If any bundled cryptographic functionality
> > triggers ASF export-notification (ECCN) requirements, we will notify the
> > ASF and complete the required paperwork.
> >
> > ## Required Resources
> >
> > ### Mailing Lists
> >
> > - priv...@maka.apache.org
> > - d...@maka.apache.org
> > - comm...@maka.apache.org
> > - iss...@maka.apache.org
> >
> > ### Subversion Directory
> >
> > Not requested.
> >
> > ### Git Repositories
> >
> > - [
> >
> >
> https://gitbox.apache.org/repos/asf/incubator-maka.git](https://gitbox.apache.org/repos/asf/incubator-maka.git)
> > - Mirrored to [
> >
> >
> https://github.com/apache/incubator-maka](https://github.com/apache/incubator-maka)
> >
> > ### Issue Tracking
> >
> > The community would like to continue using GitHub Issues at [
> >
> >
> https://github.com/apache/incubator-maka/issues](https://github.com/apache/incubator-maka/issues)
> > .
> >
> > ### Other Resources
> >
> > The community would like to continue using GitHub Actions for continuous
> > integration. No additional infrastructure is currently required.
> >
> > ## Initial Committers
> >
> > | Name | GitHub ID | Mail Address | Affiliation |
> > | --- | --- | --- | --- |
> > | Jie Wen | jackwener | jakevin...@gmail.com | Botiverse, Inc. |
> > | Yuhan Lei | Astro-Han | lei.yu...@outlook.com | Shanghai CENO New
> > Material Technology Co., Ltd. |
> > | Kun Li | likun666661 | likun666...@outlook.com | Shanghai Geshu Zhizhi
> > Technology Co., Ltd. |
> > | Zhanghan Gao | YayoiNanoka | yayoinanok...@gmail.com | South China
> > University of Technology |
> > | Haoqing Wang | hqhq1025 | hqeric1...@qq.com | Beijing University of
> > Posts
> > and Telecommunications |
> > | Yuhang Chang | MicroGery | changyuh...@outlook.com | Shenzhen Morphi
> > Intelligence Technology Co., Ltd. |
> > | Yongtao Wang | M4n5ter | m4n5te...@gmail.com | Individual |
> >
> > ## Sponsors
> >
> > ### Champion
> >
> > tison [ti...@apache.org]
> >
> > ### Nominated Mentors
> >
> > - tison [ti...@apache.org]
> > - Hao Ding [xua...@apache.org]
> > - Zhuoran Shang [psi...@apache.org]
> > - Xinyu Tan [tanxi...@apache.org]
> >
> > ### Sponsor Entity
> >
> > - The Incubator
> >
>