[Meta] Prepare wider desktop distribution
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- release
Research direction
This is a tracking issue: the actionable scope lives in sub-issues #39-#42, so start by reading those plus docs/updates.md (the desktop update procedure) to learn how signed Sparkle builds and release manifests work. Treat the checkboxes as the definition of done; do not attempt the whole tracker as one first contribution — pick a single linked issue instead. The repo is already public, so the source-review/secret-scan item needs coordination with maintainers before any patch.
Written by the indexing model from the issue text.
Description
The first stable release, with its decisions and gate checklist, is tracked in #217. #40 is the only open distribution item.
Track the remaining work for wider desktop distribution: verifying a published upgrade on another Mac, moving downloads to a custom domain, third-party notices, and completing a source review and secret scan of the repository, which is already public.
Signed canary builds are published through the Sparkle feed described in the desktop update procedure. A release can build any clean pushed lane, so a published build contains its pinned source revision; consult its release manifest/workflow and the feed for its version and included changes rather than this issue.
Release
- #39
- #40
- #41
- #42
Migrated from TODO.md.
Windows and Linux desktop support is deferred for future reconsideration; #314 preserves the roadmap (closed as not planned).
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/ace2
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
githubnext/ace2#487 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
githubnext/ace2#486 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
githubnext/ace2#459 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/ace2#437 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
githubnext/ace2#442 ·
Similar issues
-
bug priority: P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
mattermost/compass-design#106 ·
Maintainers usually reply within 1 day
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:other issue-rating: 🦞 diamond lobster P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw#176671 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
nordcraftengine/nordcraft#1400 ·
Maintainers usually reply within 1 day