Skip to content

open an issue a week before a draft goes stale #64

Open

Description

@bc1cindy

follow-up from #50 (comment)

chapters can set a stale_after date, after which the draft should be treated as possibly outdated. right now nothing tells us when that date is getting close.

add a scheduled github action that checks each chapter's stale_after and opens an issue about a week before it passes. the issue should name the chapter and its date.

it shouldn't open a second issue for the same chapter if one is already open.

Activity

  1. yuval-block commented on Oct 17, 2026

    @yuval-block
    Collaborator

    note that this shouldn't be done for the stubs, only after we merge things so that we can periodically review until we release a complete spec

  2. self-assigned this
    on Nov 16, 2026
  3. arminsabouri commented on Nov 16, 2026

    @arminsabouri
    Collaborator

    What purpose does stale_after serve? i.e what action do we want doc authors to take when docs are about to be stale?

  4. bc1cindy commented on Nov 16, 2026

    @bc1cindy
    MemberAuthor

    it might be good to commit to specifying stale_after

    code ACK, but given i suggested this i want to make sure @arminsabouri is at least cACK on this as well

    where i hope to keep going with this is:

    • make use of status fields to define what is normative
    • make supporting documents more machine readable, including eventually adding an expanded citations / literature review document for the repo as a whole, containing brief summaries of why certain things are relevant

    the goal with using OKF is to make this more legibile to LLMs which i hope would help people using LLMs to work with the SDK to integrate things correctly, and OKF is a bit of semi-standardized glue to help put documents into context so LLMs can better utilize them

    Originally posted by @yuval-block in #50 (review)

    so stale_after marks drafts that may no longer reflect the current design, so readers (and LLMs) don't treat them as normative

    nothing tells us when that date is close, so #93 checks every chapter daily and opens an issue a week before

    the issue proposes the action: the author reviews the chapter and updates it if needed, then either moves stale_after later if it still holds, or changes its status (stable once it's settled, deprecated if it's abandoned)

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions