search

ietf-tools / datatracker

The day-to-day front-end to the IETF database for people who work on IETF standards.
https://datatracker.ietf.org
BSD 3-Clause "New" or "Revised" License
596 stars 359 forks source link

timers for RFC Ed Queue state labels are inaccurate #7982

Open ajeanmahoney opened 3 weeks ago

ajeanmahoney commented 3 weeks ago

Describe the issue

When documents in the RFC Editor's Queue are listed on a working group's document page, they have a timer label that says "In state for NN days; goal is <60 days." However, the number of days shown is for the document's entire time in the queue, not for the state shown. The placement of the timer label implies that it is referring to the queue state. For example, a document's queue state label says "AUTH48" and the timer label next to it says "In state for 133 days; goal is < 60 days", but the document has only been in AUTH48 for 28 days. If there was ever a goal for AUTH48, it was 2 days, but there's not an official goal now. For the example here, the label should say "In state for 28 days".

I'm not sure where the goal of "<60 days" came from. The current SLA specifies service levels for RFC Editor-controlled Time (RET), which is the time a document spends in EDIT and RFC-EDITOR states, but these levels change depending on how many pages are in the queue. Perhaps the "goal is <60 days" text should be dropped.

Code of Conduct

jennifer-richards commented 3 weeks ago

Info for addressing this:

The goal of 60 days is set here with a comment

# loosely based on the Publish Path page at the iesg wiki

That badge is indeed keying on the rfcqueue state and is not considering the rfceditor state at all. (The code is from 2012...)

Later in the same file, the auth48_alert_badge() looks into the rfceditor state. I'm not certain whether the events needed for tracking time in that state will be reliably available though I suspect they will.

ajeanmahoney commented 3 weeks ago

I found the IESG Publish Path page, which covers goals for docs before they enter the queue but doesn't discuss goals of docs once in the queue. It may have had different info in 2012. The current SLA went into effect in 2016.