Re: Errata Processing Stats/Queue?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 7/8/19 14:31, Kathleen Moriarty wrote:
> 
> 
> On Tue, Aug 6, 2019 at 4:51 PM Michael Richardson <mcr+ietf@xxxxxxxxxxxx
> <mailto:mcr%2Bietf@xxxxxxxxxxxx>> wrote:
> 
> 
>     Fernando Gont <fgont@xxxxxxxxxxxxxxx <mailto:fgont@xxxxxxxxxxxxxxx>>
>     wrote:
>         >> And yes, it does help if WGs are responsive to errata as well.
> 
>         > FWIW, I do think when an appropriate WG is available, they
>     should work
>         > on emptying the errata queue.
> 
>         > Like bugs, if nobody cares in patching, why would folks care
>     to report?
> 
>     1) If WG-chairs could change the state themselves that would help.
>     2) If WG sessions had a number of errata as part of the status slide,
>        then that would probably help close the loop.
> 
> 
> I agree with this.  Errata needs to be delegated further to improve
> processing.  If all of the ones that existed where there is an open WG
> could be handled by the chairs, they would be more familiar with each
> errata, who the experts were that could approve them, and may have the
> history having been chairs for a long period of time.

+1


> Some ADs simply don't think errata is useful. 

Isn't it their duty to process them? (no matter what their personal
opinion is)




> I handled some, but
> worked with ADs who didn't care about them.  As a result, Security has
> the second highest score, leaving Ben and Roman with a bit too much to
> deal with at this point.

I understand that that wasn't a fresh start for them. That said, it
would seem to me that some mechanism and control loop should be in place
to avoid this kind of thing from continuing. Particularly for security,
it's kind of ironic that the queue of unprocessed technical errata is so
long.

That's the equivalent of a vendor not processing vulnerability reports....



> If there's no WG that remains or never was one, it would be nice if
> those could be delegated too.  The usual process is for editors of the
> draft to review the errata and respond on list as to their thoughts. 
> Then the AD is able to press the buttons.  Maybe someone else could
> monitor the list conversations and update the text in the errata filing
> accordingly with a link to said email confirmations and press the buttons?

Is there something like AD "secretary" (parallel to wg secretaries) that
might help with this?

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@xxxxxxxxxxxxxxx
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492







[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux