Repository navigation
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
| On 2026-10-13 the three tracks reported: | ||
|
|
||
| - **OAuth WG:** 11 active drafts. The top three were `attestation-based-client-auth` (125), `rfc7523bis` (90), and `sd-jwt-vc` (83). | ||
| - **WIMSE:** 8 active WG drafts, 16 related drafts, 68 mailing-list posts scanned. The newest WG draft was `draft-ietf-wimse-aims-00` (AI Identity Management System). |
There was a problem hiding this comment.
The expansion "AI Identity Management System" for draft-ietf-wimse-aims-00 reads as recalled. Check it against the Datatracker title before this goes out. Also confirm that a -00 WG draft exists under that exact name. The same applies to the draft names and counts at lines 72 and 88–90, which come from a run I can't see. Please make sure they match the 2026-10-13 candidates.json and state.json.
There was a problem hiding this comment.
Checked against the source data: tracks/ietf-wimse/reports/daily/2026-10-13.md lists draft-ietf-wimse-aims-00 | 2026-09-15 | AI Identity Management System, and the OAuth WG ranks/scores (125 / 90 / 83, 11 active drafts) and the OpenID counts (65 repos, 172 PRs, 1,521 issues, top openid/authzen) match that day's reports and candidates.json. No change.
|
|
||
| ## From radar to deep dive | ||
|
|
||
| The ranking is only the first half. When something crosses the threshold, the repo has templates for a deep dive (context, spec notes, an interop checklist, and a hands-on log), so reading a spec ends with notes I can return to instead of a closed browser tab. The first one covers `draft-ietf-oauth-v2-1`. If WIMSE itself is new to you, I wrote a [WIMSE deep dive](https://dev.to/kanywst/wimse-workload-identity-in-multi-system-environments-deep-dive-standardizing-identity-5a12) earlier. |
There was a problem hiding this comment.
"The first one covers draft-ietf-oauth-v2-1" is a claim about another repo that I can't verify from here. Link the deep dive so readers can check it. Also note that cimd-02-deployment-vs-identity.md cites draft-ietf-oauth-v2-1-16, so the version you describe should be consistent with that.
There was a problem hiding this comment.
Linked the deep dive directory in the follow-up commit. The article does not name a revision, so it does not conflict with -16 elsewhere.
|
Only articles/identity-deep-dive-radar.md changed. Frontmatter fits the repo rules: 4 tags, a future date, and published: false, so the hourly schedule.yml will flip it. The WIMSE deep-dive link resolves to a real article in INDEX.md. Two things need a source check before publishing (inline comments posted):
Line 16 says "more than sixty GitHub repositories" while line 90 reports 65 OpenID repos alone. Make sure the totals are consistent across all tracks. |
|
|
||
| ## From radar to deep dive | ||
|
|
||
| The ranking is only the first half. When something crosses the threshold, the repo has templates for a deep dive (context, spec notes, an interop checklist, and a hands-on log), so reading a spec ends with notes I can return to instead of a closed browser tab. The first one covers [`draft-ietf-oauth-v2-1`](https://github.com/0-draft/identity-deep-dive/tree/main/tracks/oauth-wg/deep-dives/draft-ietf-oauth-v2-1). If WIMSE itself is new to you, I wrote a [WIMSE deep dive](https://dev.to/kanywst/wimse-workload-identity-in-multi-system-environments-deep-dive-standardizing-identity-5a12) earlier. |
There was a problem hiding this comment.
This links to tracks/oauth-wg/deep-dives/draft-ietf-oauth-v2-1 and templates/new-track/ (line 98) in another repo. I couldn't confirm either path exists on main, so please check them. Broken links won't be caught by the link checker if it only covers local files. The "first one covers" wording also needs to stay true until the 2026-11-13 publish date.
|
|
||
| ## What a daily run looks like | ||
|
|
||
| On 2026-10-13 the three tracks reported: |
There was a problem hiding this comment.
The article is scheduled for 2026-11-13 (line 11) but presents a 2026-10-13 snapshot as "what a daily run looks like" (lines 86-90). By publication the numbers will be a month old, yet the text says "the top candidate" and "newest WG draft" without qualification. Either refresh the figures close to publish time or word it as a point-in-time example. The figures and the draft-ietf-wimse-aims-00 expansion "AI Identity Management System" are also unsourced. I couldn't verify the draft's title from the repo, so please check it against Datatracker.
|
Reviewed the new Two items to check before the scheduled publish:
No EN/JA parity or workflow/injection issues in this diff. |
1 participant
Intro article for 0-draft/identity-deep-dive, written as the exposure step from the 2026-10-13 archive check (kanywst/bellman#307).
published: falsewithdate: 2026-11-13T00:00:00Z, so merging schedules it:schedule.ymlflips it live at that time. Change or drop the date before merging if you want it held.candidates.json,reports/daily/2026-10-13.md) andtracks/oauth-wg/config/scoring.yaml.validate_articles.pycould not run locally, so CI is the check for frontmatter and links.