On 20-Dec-24 04:46, Jean Mahoney wrote:
...
To deal with the backlog, should we just close reports that have been
open for a long time?
I know this is tempting but who's to say that a report from 5 years ago wrong?
One suggestion (and it doesn't need a new process) is to send an email to
the reporter of each open report >N years old, saying "Is this still valid?
Unless you reply within one month, we will close it."
The definition of "long time" would need to be
determined.
There are currently the following open reports:
2010: 4
2013: 5
2014: 17
2015: 30
2016: 45
2017: 50
2018: 65
2019: 59
2020: 77
2021: 62
2022: 81
2023: 69
2024: 149
Total: 713
Here's a suggested plan:
- Arbitrarily close all reports on Legacy stream and Historic or Obsoleted or
Unknown RFCs. (And don't allow them in future.)
For all reports before 2020:
- Close all editorial reports.
- Send "Is this still valid?" messages for the rest, and close them a month
later if no reply.
Or should the RPC host a hackathon at an upcoming IETF
meeting where verifiers work through as many open reports as possible?
We could bring pizza :-)
Something like that for the reports since 2020; or launch an online hackathon.
Regards
Brian
Thanks!
Jean
We should chuck
it out and replace it entirely.
Cheers,
S.
--
rswg mailing list -- rswg@rfc-editor.org
To unsubscribe send an email to rswg-le...@rfc-editor.org
