Repository navigation
Conversation
UX Review (Opus 5.5, fork) — ⏭️ skippedRevision |
First Principles Review (Opus 5.5, fork) — ⏭️ skippedRevision |
Design Review (Opus 5.5, fork) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing blocks: this PR adds only a draft RFC and its index row, and every phase that sends or renders anything waits on a named maintainer decision. Notes
[DESIGN-REVIEWED] 6440fb5 Description read[DESCRIPTION-READ] 5c9b780da7470be72e2e8028f5311f37fe26634a6b654e52867998a8ba9ce1f6 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
GPT 6.1 Review (fork) — ✅ no blocking findingsReviewed Review detailsNo findings. |
Opus 5.5 Review (fork) — ✅ no blocking findingsReviewed |
10a40da to
f12825f
Compare
|
|
|
|
f12825f to
3b44485
Compare
|
|
|
3b44485 to
39f617e
Compare
|
|
CI note for maintainers: this PR changes only
A fork cannot re-run jobs, so a rerun of the failed jobs on the current head would be appreciated if either recurs. |
39f617e to
8c68d34
Compare
|
8ff44bb to
ee82da6
Compare
|
ee82da6 to
e0497ab
Compare
e0497ab to
78be152
Compare
|
78be152 to
ee831e6
Compare
|
CI note for maintainers on |
|
|
CI note for maintainers on
A fork cannot re-run jobs, so a rerun of the failed jobs on this head would be appreciated. |
|
|
Holding on head df7c609 because the branch conflicts with main in The document itself is a draft RFC with no code change, all checks on this head are green, and the earlier Opus and Design findings were answered with fixes. Two current-head AI notes look non-blocking, and you may want to fix them while rebasing:
— crew-pr-reviewer (r133) |
Add a draft RFC for showing a published app's builder its installs, active installs and version distribution over time: a weekly presence ping with a rotating per-app token, fields and a small-count floor added to the ranking document proposed in kirodotdev#17958, and a Usage section on the app detail page. External registries report only to a collector the owner confirmed. Refs kirodotdev#18761
|
Thanks a lot for this contribution, @FlorentLa. We have an RFC covering the same ground in #39107: per-app installs, updates and uninstalls by version, plus sessions and run time under each app. It already borrows from your small-count floor and version normalization ideas. Feel free to comment on that one; we would love your review there. |
Problem / Motivation
Goal: Propose a design that shows the builder of a published Kiro Crew app its installs, active installs and version distribution over time, on the app's listing.
A builder gets no usage feedback after publishing; an official listing shows GitHub stars and nothing else. The only app-level signal leaving a host is the official-app install receipt, which counts install events, carries Kiro Crew's release rather than the app's, never reports for external registries, and has no consumer in this repository. #18761 asks for these stats on any registry, and its triage reply asked for an RFC under
docs/request-for-change/.Why it matters
Without these numbers a builder cannot tell whether a release was adopted, whether an old version still needs support, or when a breaking change is safe.
Not a goal
What changed (motivation → approach → change)
Adds
docs/request-for-change/rfc-app-usage-stats.mdasdraft, and its row in the index. The document proposes:active,versions,series) and a small-count floor added to the ranking document feat(apps): publish install-count ranking that Discover can sort by #17958 proposes, instead of a second document;Eligibility fails closed: local, dev and legacy installs with unknown provenance never report. Phases are PR-sized with testable exit criteria, and the five decisions a maintainer must make, including who owns the official producer, gate the phases that send or render anything. Acceptance is requested from a maintainer; the status flips to
acceptedwhen one records it in the document.Backwards compatibility
Compatible: documentation only; no code, config or wire change.
Removes nothing: the diff adds a file and a table row.
Tests
N/A: documentation only.
python3 scripts/docs_lint.pypasses.Manual verification
Every claim about current code was checked against
d32c084921, the commit named in the front matter.Related Issues
Refs #18761. Related: #17520, #17958, #9490, #12883, #1440.
no linked issue: this is the design for #18761, which stays open for the implementation and for its finer-grained usage part.
Checklist
Contribution License Agreement
Contributed under the project's Apache-2.0 license.