docs: connect project metadata to public website - #2924
Conversation
jackwener
left a comment
There was a problem hiding this comment.
Automated review of exact head c21859edb1f6ca7dcfbf3780408cdf022d0f93f0 against current main@d62857a8357e9160926726a2a13096bc2dc2b91d.
I included this as a documentation/metadata repair by another committer. Its original missing-link problem is real, but the proposed revision is now superseded by the Apache migration and should not be revived through conflict resolution.
Blocking: every new public authority still points at the pre-Apache project. The README navigation and package metadata publish maka-agent.com plus github.com/maka-agent/maka-agent; current main is apache/maka, .asf.yaml names Apache Maka (Incubating), and the open branding repair targets maka.apache.org. Merging these values would re-establish the obsolete project/domain as the package homepage, issue tracker, download authority, and documentation authority. The PR body also explicitly says its prerequisite website pages are unfinished and the links would otherwise be 404s.
Required conclusions:
- Optimal for the actual problem: no longer; the ownership/domain premise changed.
- Production code to delete: none; this is metadata/docs only.
- Tests to delete/replace: none identified.
- Deeper refactor: no—close this revision or rewrite it narrowly against the approved ASF website/download authorities after they exist.
- Ready to merge: no; it is Draft, conflicting, and depends on an obsolete/unshipped website surface.
- Residual risks/gaps: website, release/download wording, trademarks, and project metadata are governance/release surfaces requiring PPMC/mentor review and live link verification.
Status
Draft. This PR depends on the unfinished website page work in maka-agent/maka-agent.github.io#1. The website PR now includes the complete page inventory, planned public URLs, desktop/mobile screenshots, and an explicit design/content revision checklist.
Do not merge this PR before the website pages are redesigned, reviewed, merged, and deployed; otherwise the new README links will point to 404 routes.
Summary
Verification
git diff --checkpackage.jsonandpackage-lock.jsonsuccessfullyMaintainer follow-up
The current account can push code but cannot update repository settings. After the website and this PR are ready, please set:
https://maka-agent.com/ai-agent,desktop-app,local-first,agent-runtime,electron,typescript,cli,tui,open-sourceGitHub returned a permission-masked 404 when those settings were attempted through the API; they were not changed.