Skip to content

docs: apply Apache Incubator branding to release surfaces #3272

Description

@M4n5ter
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 missing incubator topic.
  • maka.apache.org serves the reviewed project website rather than 404.
  • The website provides an ASF-compliant source download path and points to
    KEYS and 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

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 的下载与验包入口。

完成条件

已有工作

不在范围内

  • 与 Apache 发版要求无关的产品网站重新设计。
  • npm/Desktop 打包和许可证实现。
  • Export classification。

参考资料

负责人边界

在有人认领全部发版界面前,整个 issue 保持 unassigned。#3262 author 只负责该 PR 明确
声明的范围。

Activity

  1. Astro-Han commented on Aug 21, 2026

    @Astro-Han
    Contributor
    English

    Two of the seven exit criteria here are now in progress, and the website criteria have moved to their own issue.

    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。

    其余三条——npm 包页面、GitHub release 界面和发版公告——未触及。它们依赖 #2974 中尚未确定的首发范围,其中 release 界面还依赖 #3274 等待中的 mentor 决策。

  2. added theissue type on Aug 29, 2026
  3. Astro-Han commented on Sep 1, 2026

    @Astro-Han
    Contributor
    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.org still returns 404. Tracked in infra: publish the podling website at maka.apache.org #3404, which is the real prerequisite for two of them.
    • The npm package disclaimer and the GitHub release surfaces both need artifacts that will only exist after the source release is approved.
    • The announcement and download page are written as part of the release itself.

    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 跟踪,它是其中两条的实际前置。
    • npm 包免责声明和 GitHub release 载体,都需要在源码发布获批之后才会存在的产物。
    • 公告和下载页本身就是发布过程的一部分。

    除了先确定措辞之外,这里没有能赶在 #3404 之前推进的工作。建议本 issue 保持开放,作为各载体出现时逐一套用的品牌验收清单,而不是一个有自身排期的工作项。


    Drafted with help from Claude Code. I reviewed the final text and take responsibility for posting it.

  4. added
    staleNo qualifying activity within the lifecycle policy window
    on Oct 2, 2026
  5. github-actions commented on Oct 2, 2026

    @github-actions

    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 main and add any information that would help move it forward. Assigned issues and issues labelled pinned are exempt from this policy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationstaleNo qualifying activity within the lifecycle policy window

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions