Repository navigation
infra: publish the podling website at maka.apache.org #3404
Description
English
Part of #2974, supports #3272 (G5: Incubator branding and release surfaces).
maka.apache.org serves the podling website. This issue owns the publication path and the pages ASF policy requires; what the site says was settled in #4307.
Delivered
- The site source is in
apache/makaunderwebsite/, following OpenDAL rather than a separate site repository. A workflow builds it and force-pushes toasf-site,.asf.yamlpublishes that branch, andstaging: autostage: site/*gives release candidates a review path (feat(website): publish the podling site from website/ #4660, live since 2026-09-03). - Every page identifies Apache Maka (Incubating), carries the full Incubator disclaimer and the ASF footer, and loads nothing from a third party. Fonts and assets carry recorded provenance, and the site carries
LICENSEandNOTICE. - The downloads page states that the signed source archive is the release, keeps Desktop Nightly, source builds and future Apache Releases separate, and gives the
KEYS, GPG and SHA-512 steps a reviewer runs before voting. - The homepage is complete in English and Chinese with the same sections, claims, warnings and links. @Astro-Han keeps the two in sync. A benchmarks block links the reports in
docs/eval/without restating numbers. - The homepage, both READMEs and the repository description all open with the [DISCUSS] Rebuild the Maka website and project narrative #4307 sentence: "Apache Maka (Incubating) is a high-performance agent workspace that keeps a complete record of everything it did." (docs: hand the landing-page role from the README to maka.apache.org #4686)
Tests in website/test/site.test.mjs hold the ASF-required parts, the bilingual link parity and that sentence, so they fail rather than drift.
Remaining
- Run status semantics (fix(runtime): resume rejects provably-undispatched tools as dangling state #4423, feat(runtime): resume interrupted runs safely instead of parking them #4424) are fixed, so the site does not describe more than the product records. Both are open and still in design.
- A fact-check cadence is recorded: the homepage is re-checked against the product at every release, and for changes to positioning, the primary journey, platform support, or the trust boundary.
- The PPMC records what happens to
maka-agent.comand the GitHub Pages deployment. The direction settled is a redirect (comment); the DNS and Pages changes are not made yet.
Out of scope
- First-release artifact scope ([TRACKING] Apache Maka 0.2.0-incubating source release #2974), the README and repository metadata of docs: apply Apache Incubator branding to release surfaces #3272 that docs: identify the project as Apache Maka (Incubating) in both READMEs #3391 advances, and Nightly delivery mechanics (Should the Maka website provide a faster download path for Desktop Nightlies? #4301).
- Public governance decisions stay with the mentors and the PPMC; implementation ownership does not replace them.
AI use: I used Claude to draft this rewrite. I own the public change.
简体中文
属于 #2974，支撑 #3272（G5：孵化器品牌与发布面）。
maka.apache.org 已经在提供 podling 官网。 本 issue 负责发布链路和 ASF 政策要求的页面；官网讲什么由 #4307 定下。
已交付
- 站点源码在
apache/maka的website/下，照 OpenDAL 的做法，不新建独立站点仓库。workflow 构建后强推到asf-site，.asf.yaml发布该分支，staging: autostage: site/*为发版候选提供审查路径（feat(website): publish the podling site from website/ #4660，2026-09-03 起上线）。 - 每个页面都标识 Apache Maka (Incubating)，带完整 Incubator disclaimer 与 ASF 页脚，且不加载任何第三方资源。字体与资产有来源记录，站点具备
LICENSE与NOTICE。 - 下载页写明带签名的源码包才是 release，把 Desktop Nightly、源码构建与未来的 Apache Releases 分开，并给出 reviewer 投票前会实际执行的
KEYS、GPG 与 SHA-512 步骤。 - 首页中英两版章节、主张、警示与链接完全一致，由 @Astro-Han 负责同步。跑分板块链接
docs/eval/的报告，不复述数字。 - 首页、两份 README 和仓库描述都以 [DISCUSS] Rebuild the Maka website and project narrative #4307 那句话开头：「Apache Maka（孵化中）是一个高性能的 Agent 工作台，并完整记录它做过的每一件事。」（docs: hand the landing-page role from the README to maka.apache.org #4686）
website/test/site.test.mjs 里的测试守住 ASF 要求的部分、中英链接对齐和这句话，漂移会直接失败而不是悄悄发生。
待办
- Run 状态语义（fix(runtime): resume rejects provably-undispatched tools as dangling state #4423、feat(runtime): resume interrupted runs safely instead of parking them #4424）修好，使官网描述不超出产品实际记录。两个 issue 都还开着，仍在设计讨论中。
- 记录事实核对节奏：每次 release 都对照产品复核首页，定位、主要旅程、平台支持或信任边界变化时同样复核。
- PPMC 记录
maka-agent.com与 GitHub Pages 部署的去向。已确定方向是跳转（评论），DNS 与 Pages 尚未修改。
不在范围内
- 首个 release 的 artifact 范围（[TRACKING] Apache Maka 0.2.0-incubating source release #2974）、docs: apply Apache Incubator branding to release surfaces #3272 中由 docs: identify the project as Apache Maka (Incubating) in both READMEs #3391 推进的 README 与仓库元数据、Nightly 交付机制（Should the Maka website provide a faster download path for Desktop Nightlies? #4301）。
- 公开治理决定仍归 mentor 与 PPMC，实现层面的负责不替代它们。
AI use：本次重写由我用 Claude 起草，我对这次公开改动负责。
Activity
wy471x commentedon Aug 25, 2026
I guess I could try.
Astro-Han commentedon Aug 25, 2026
hi @wy471x, thanks for initial the take.
This issue is part of the Apache governance issue so it might be best leave to the current committee.
There are issues with help-wanted tag, which are great start point for contribution. Would you be interested to look at those?
Thanks!
wy471x commentedon Aug 25, 2026
Alright, I can take a look.
[-]infra: publish the podling website at maka.apache.org from the existing Maka site[/-][+]infra: publish the podling website at maka.apache.org[/+]Astro-Han commentedon Sep 1, 2026
English
Status: still 404, and the first exit criterion needs rewording
https://maka.apache.org/returns 404 as of 2026-09-01.The first exit criterion asks mentors to confirm how the site's code, copy, and design assets are covered — "by the software grant tracked in #3268 or by a separate Incubator IP clearance". #3268 has been proposed for closure (the software grant is an incubation setup item handled by the Incubator and the Secretary, not a release gate; evidence is on that issue). That does not remove this criterion, but it should stop pointing at #3268 for its answer.
The question itself is still real and still needs a mentor: website code and design assets that were not part of the original donation need their own coverage before they move into an ASF repository. Suggest rewording it to ask mentors directly whether the site content falls under the existing grant or needs separate IP clearance, and tracking the answer here.
Everything else on the list is unchanged. This issue is the real prerequisite for two of #3272's open criteria — the ASF-compliant download path and the incubating identification on the homepage — and #2974 now lists both in its non-blocking table, so neither gates RC1.
One sequencing note: the downloads page cannot be finished before there is an approved source release to link, but its structure —
KEYSlink, SHA-512 and signature links, GPG and checksum verification steps, and the statement that convenience artifacts are not the release — can be built ahead of time against the staged candidate. OpenDAL'sdownload.mdxis the reference this issue already names.简体中文
进展：仍为 404，第一条出口条件需要改写
截至 2026-09-01，
https://maka.apache.org/返回 404。第一条出口条件要求导师确认站点的代码、文案和设计资产如何被覆盖——「由 #3268 跟踪的软件授权书，或由单独的孵化器 IP clearance」。#3268 已提议关闭（软件授权书是由孵化器和秘书处办理的入孵事项，不是发布门禁；证据在该 issue 上）。这并不取消本条，但它不应再指向 #3268 求答案。
问题本身依然真实，也依然需要导师：不属于最初捐赠范围的网站代码和设计资产，在迁入 ASF 仓库之前需要各自的覆盖依据。建议改写为直接询问导师，站点内容是落在现有授权书之内，还是需要单独的 IP clearance，并把答复记录在本 issue。
清单上其余各项无变化。本 issue 是 #3272 两条开放条件的实际前置——符合 ASF 的下载路径，以及首页的孵化标识——而 #2974 现已将两者列入非阻塞表，因此都不构成 RC1 的门槛。
一条排序提示：下载页在有已获批准的源码发布可供链接之前无法完成，但它的结构——
KEYS链接、SHA-512 与签名链接、GPG 和校验和验证步骤，以及「convenience artifacts 不是发布」的声明——可以先针对暂存的候选包搭好。本 issue 已经点名的 OpenDALdownload.mdx就是参照。Drafted with help from Claude Code. I reviewed the final text and take responsibility for posting it.
feat(website): publish the podling site from website/
feat(website): publish the podling site from website/ (#4660)
Astro-Han commentedon Sep 3, 2026
English
Status: live at maka.apache.org
#4660 merged as 1fe21e6. The
Websiteworkflow built the site and force-pushed it toasf-site; asfyaml published it within three minutes.https://maka.apache.org/,/en/,/zh-CN/and/en/downloads/all return 200.Exit criteria now met, ticked in the body:
apache/makaunderwebsite/, following OpenDAL.asf-site; the branch carries its own.asf.yamlwith thepublish:entry.maka.apache.orgserves the site.-rctag pushessite/<tag>-staging, andworkflow_dispatchwithstage=<name>pushessite/<name>-staging. Wired and covered by the workflow policy tests, not yet exercised against a real candidate.download.mdx:KEYS,.asc, SHA-512, GPG and checksum steps, and it separates Desktop Nightly, source builds and Apache Releases, stating that convenience artifacts are not the release. Real artifact links wait for the first approved release.Copytype; the build fails if either language misses a section or link.docs/eval/without restating numbers in prose.@fontsource-variablepackages, OFL-1.1, license text published under/licenses/; the logo is the README'ssky.png; the Incubator logo is the ASF's published file.LICENSEandNOTICEship inasf-site.Still open:
docs/eval/and the product at every release and at any change to positioning, the primary journey, platform support or the trust boundary. Objections here; otherwise I record it as settled in a week.maka-agent.comand the GitHub Pages deployment. I will open that as its own thread.简体中文
进展：maka.apache.org 已上线
#4660 以 1fe21e6 合并。
Websiteworkflow 构建站点并强推到asf-site，asfyaml 在三分钟内发布。https://maka.apache.org/、/en/、/zh-CN/、/en/downloads/均返回 200。已满足并在正文勾选的出口条件：
apache/maka的website/，沿用 OpenDAL 布局。asf-site；该分支自带含publish:的.asf.yaml。maka.apache.org已提供该站点。-rctag 推送site/<tag>-staging，workflow_dispatch带stage=<name>推送site/<name>-staging。已接线并有 workflow 策略测试覆盖，尚未对真实候选包演练。download.mdx：KEYS、.asc、SHA-512、GPG 与校验步骤，并分开 Desktop Nightly、源码构建与 Apache Releases，声明 convenience artifacts 不是发布。真实制品链接等首个获批发布。Copy类型；任一语言缺章节或链接则构建失败。docs/eval/，不在正文复述数字。@fontsource-variable的 Geist 与 Geist Mono，OFL-1.1，许可文本发布在/licenses/；logo 为 README 的sky.png；孵化器 logo 为 ASF 官方文件。LICENSE与NOTICE随asf-site一起发布。仍开放：
docs/eval/与产品复核首页。有异议请在此提出，否则一周后记为已定。maka-agent.com与 GitHub Pages 部署的去留。我会单开一个串。Drafted with help from Claude Code. I reviewed the final text and take responsibility for posting it.
feat(website): publish the podling site from website/ (apache#4660)
Astro-Han commentedon Sep 4, 2026
Recording the direction settled for
maka-agent.comand the GitHub Pages deployment, so it is not carried only in conversation.Redirect, not retire and not keep as a second site. Now that
maka.apache.orgserves the podling site,maka-agent.comand the GitHub Pages deployment redirect to it rather than continuing to serve their own copy of the project narrative. That keeps one place where the project describes itself, and it avoids a non-ASF domain presenting itself as the project's site, which is what the branding guide asks podlings to avoid.Execution is still open: the DNS and Pages changes have not been made, and the old content stays reachable until they are. I will follow up with the work item once the redirect target and the handling of existing paths are settled.
If the PPMC wants this on the record as a formal decision rather than as a tracker note, it should go to the dev list; this comment is the tracker's copy of where we are.
简体中文
把
maka-agent.com和 GitHub Pages 部署的处理方向记录在这里，不再只留在对话里。跳转，不下线，也不保留为第二个站点。
maka.apache.org已经承载 podling 官网，maka-agent.com与 GitHub Pages 部署改为跳转过去，不再各自维护一份项目叙述。这样项目只有一处自我描述，也避免一个非 ASF 域名以项目官网的身份出现——那正是品牌指南要求 podling 回避的情况。执行尚未完成：DNS 与 Pages 都还没有改，改完之前旧内容仍然可达。跳转目标与既有路径的处理方式确定后，我会跟进工作项。
如果 PPMC 需要把这件事作为正式决定留档，而不只是 tracker 上的记录，应当走 dev 邮件列表；这条评论只是 tracker 这一侧的记录。
Astro-Han commentedon Sep 27, 2026
Closing: the goal of this issue is met.
https://maka.apache.org/has been live since #4660 (see the status comment above). The three unchecked items are not website infrastructure, so each goes to its own owner:maka-agent.comand the GitHub Pages deployment: the redirect direction is recorded above; the DNS and Pages change is a PPMC action.中文
关闭：本 issue 的目标已达成，
https://maka.apache.org/自 #4660 起已上线（见上方状态评论）。剩下三项未勾选的都不属于官网基础设施，各归其主：maka-agent.com与 GitHub Pages：跳转方向已在上方记录，DNS 与 Pages 的修改由 PPMC 执行。