Repository navigation
docs: apply Apache Incubator branding to release surfaces #3272
Copy link
Copy link
Open
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationstaleNo qualifying activity within the lifecycle policy windowNo qualifying activity within the lifecycle policy window
Description
English
Part of #2974 — G5: Incubator branding and release surfaces.
Outcome
Make repository and release-facing surfaces consistently identify the project
as Apache Maka (Incubating) and provide the disclaimer, source download, and
release-verification paths required for the source, npm, and Desktop artifacts.
Exit criteria
- Root English and Chinese READMEs first identify Apache Maka and its
incubating status and link the disclaimer. Done in docs: identify the project as Apache Maka (Incubating) in both READMEs #3391. - Repository description and metadata use Apache Incubator branding. The
description landed in chore: add .asf.yaml for ASF infrastructure self-service #3262; docs: identify the project as Apache Maka (Incubating) in both READMEs #3391 added the missingincubatortopic. -
maka.apache.orgserves the reviewed project website rather than 404. - The website provides an ASF-compliant source download path and points to
KEYSand verification instructions. - The npm package README/version page displays the full Incubator disclaimer
and links the approved source release. - GitHub release surfaces distinguish ASF releases from historical or
non-ASF product releases, carry the required Incubator disclaimer, and link
each Desktop convenience artifact to the approved source release. - The release announcement and download page use the approved project name
and distinguish the official source release from npm/Desktop convenience
artifacts.
Existing work
- docs: identify the project as Apache Maka (Incubating) in both READMEs #3391 identified both root READMEs as Apache Maka (Incubating), linked
DISCLAIMER-WIP, added the source-release versus convenience-artifact framing
and the ASF trademark attribution, removed the prebuilt download
recommendation that pointed at an unapproved build, and added theincubator
topic. - infra: publish the podling website at maka.apache.org #3404 tracks
maka.apache.org, which covers the website and source download
criteria above. - chore: add .asf.yaml for ASF infrastructure self-service #3262 directly covers
.asf.yamland repository metadata, but only part of
this gate. - docs: connect project metadata to public website #2924 targets the pre-Apache website and should not be merged as-is. It is
historical context, not a closing PR for this issue.
Out of scope
- Product website redesign unrelated to Apache release requirements.
- npm/Desktop packaging and licensing implementation.
- Export classification.
References
Ownership
Leave the overall issue unassigned until someone claims all release surfaces.
The author of #3262 remains responsible only for that PR's explicit scope.
简体中文
#2974 的一部分——G5:孵化器品牌与发版界面。
目标结果
让仓库和面向发版的界面一致标识项目为 Apache Maka (Incubating),并提供第一次发版
所需的免责声明,以及源码、npm 和 Desktop artifacts 的下载与验包入口。
完成条件
- 根目录英文和中文 README 首次提及时使用 Apache Maka 及其 incubating 状态,
并链接免责声明。已由 docs: identify the project as Apache Maka (Incubating) in both READMEs #3391 完成。 - 仓库描述和元数据使用 Apache Incubator 品牌。描述由 chore: add .asf.yaml for ASF infrastructure self-service #3262 落地,docs: identify the project as Apache Maka (Incubating) in both READMEs #3391 补上缺失的
incubatortopic。 -
maka.apache.org提供经过审查的项目网站,不再返回 404。 - 网站提供符合 ASF 要求的源码下载入口,并链接
KEYS和验包说明。 - npm package README/version 页面展示完整 Incubator disclaimer,并链接获批源码
release。 - GitHub release 界面区分 ASF release 与历史/非 ASF 产品版本,并携带所需的
Incubator disclaimer,同时将每个 Desktop convenience artifact 链接到获批源码
release。 - 发版公告和下载页使用批准的项目名称,并区分官方源码 release 与 npm/Desktop
convenience artifacts。
已有工作
- chore: add .asf.yaml for ASF infrastructure self-service #3262 直接覆盖
.asf.yaml和仓库元数据,但只完成这一 gate 的一部分。 - docs: identify the project as Apache Maka (Incubating) in both READMEs #3391 已让两个根 README 标识为 Apache Maka (Incubating)、链接
DISCLAIMER-WIP、
补上源码 release 与 convenience artifact 的区分和 ASF 商标声明,移除了指向未获批构建
的预构建下载推荐,并补上incubatortopic。 - infra: publish the podling website at maka.apache.org #3404 跟踪
maka.apache.org,覆盖上面的网站与源码下载两条完成条件。 - docs: connect project metadata to public website #2924 面向进入 Apache 前的网站,不应原样合并。它只是历史背景,不能关闭本 issue。
不在范围内
- 与 Apache 发版要求无关的产品网站重新设计。
- npm/Desktop 打包和许可证实现。
- Export classification。
参考资料
负责人边界
在有人认领全部发版界面前,整个 issue 保持 unassigned。#3262 author 只负责该 PR 明确
声明的范围。
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationstaleNo qualifying activity within the lifecycle policy windowNo qualifying activity within the lifecycle policy window
Activity
docs: identify the project as Apache Maka (Incubating) in both READMEs
Astro-Han commentedon Aug 21, 2026
English
Two of the seven exit criteria here are now in progress, and the website criteria have moved to their own issue.
DISCLAIMER-WIP;.asf.yamlgains theincubatortopic on top of the description chore: add .asf.yaml for ASF infrastructure self-service #3262 already landed. It also adds a "Releases and downloads" section stating the source-versus-convenience-artifact distinction in general terms, without asserting which convenience artifacts belong to the first release. Wording follows Apache OpenDAL.maka.apache.orgserving a reviewed site, and an ASF-compliant download path withKEYSand verification instructions. It is a migration of the existing Astro site rather than a new build, following OpenDAL's layout — site source in the main repository, a build pushed to a publish branch, and a matching.asf.yamlpublish:entry. IP clearance for the site content is a prerequisite and is tracked against legal: close incoming IP provenance for the first Apache release #3268.The remaining three criteria — the npm package page, the GitHub release surfaces, and the release announcement — are untouched. They depend on the first-release scope decision in #2974 and, for the release surfaces, on the pending mentor decision in #3274.
简体中文
七条完成条件中的两条已在推进,网站相关的两条已拆到独立 issue。
DISCLAIMER-WIP;.asf.yaml在 chore: add .asf.yaml for ASF infrastructure self-service #3262 已落的 description 之外补上incubatortopic。它还新增了「Releases and downloads」小节,以一般性表述区分源码 release 与 convenience artifacts,不断言哪些 convenience artifacts 属于首次发版。措辞参照 Apache OpenDAL。maka.apache.org提供经审查的站点,以及符合 ASF 要求、带KEYS和验包说明的下载入口。它是对现有 Astro 站点的迁移而非新建,照 OpenDAL 的布局——站点源码放主仓库、构建产物推到发布分支、.asf.yaml配对应的publish:。站点内容的 IP clearance 是前置条件,挂在 legal: close incoming IP provenance for the first Apache release #3268 追踪。其余三条——npm 包页面、GitHub release 界面和发版公告——未触及。它们依赖 #2974 中尚未确定的首发范围,其中 release 界面还依赖 #3274 等待中的 mentor 决策。
docs: identify the project as Apache Maka (Incubating) in both READMEs (
Astro-Han commentedon Sep 1, 2026
English
Status: core identification done; everything remaining depends on surfaces that do not exist yet
Two of seven exit criteria are met — the READMEs and repository metadata identify Apache Maka (Incubating) after #3391 and #3262. #2974 has been restructured and this issue now sits in its non-blocking table: incubator branding is not a gate on the source release vote.
The five open criteria all depend on something that does not exist yet:
maka.apache.orgstill returns 404. Tracked in infra: publish the podling website at maka.apache.org #3404, which is the real prerequisite for two of them.Nothing here can be worked ahead of #3404 except deciding the wording. Suggest this stays open as the branding acceptance list applied at each surface as it appears, rather than as a work item with its own schedule.
简体中文
进展:核心标识已完成;剩余各条都依赖尚不存在的载体
7 条出口条件中已满足 2 条——经 #3391 和 #3262,README 和仓库元数据已标识 Apache Maka (Incubating)。#2974 已重构,本 issue 现位于其非阻塞表中:孵化器品牌标识不是源码发布投票的门禁。
其余 5 条都依赖尚不存在的东西:
maka.apache.org仍返回 404。由 infra: publish the podling website at maka.apache.org #3404 跟踪,它是其中两条的实际前置。除了先确定措辞之外,这里没有能赶在 #3404 之前推进的工作。建议本 issue 保持开放,作为各载体出现时逐一套用的品牌验收清单,而不是一个有自身排期的工作项。
Drafted with help from Claude Code. I reviewed the final text and take responsibility for posting it.
github-actions commentedon Oct 2, 2026
This issue has had no human activity for 30 days and has been marked stale. It will be closed in 30 days unless someone comments.
If the issue is still current, please confirm it against the latest
mainand add any information that would help move it forward. Assigned issues and issues labelledpinnedare exempt from this policy.