IESG View of WGs

[rdanyliw]

Description

If the spirit of the AD Workload page, (https://datatracker.ietf.org/doc/ad/), I would propose a related page summarizing the disposition of the WGs. This was inspired by Francesca and Murray's analysis of ART to decide on the required number of ADs, Martin Duke's analysis which led to ART/WIT area creation, and Roman's on-boarding as the new chair.

Page title: IESG View of WGs

Table 1: Area Size and Load

• Column 1: Area Name
• Column 2: Count of WGs in the area
• Column 3: Count of "Active I-Ds" (i.e., "Adopted I-Ds")
• Column 4: Count of pages in "Active I-Ds"
• (divider)
• Column 5: % of all WGs
• Column 6: % of all "Active I-Ds"
• Column 7: % of all pages
• Last row would be a total of each column from above

Table 1: Area Director Load

• Column 1: Area Director Name
• Column 2: Area
• Column 3: Count of WG for which the AD is responsible
• Column 4: Count of "Active I-Ds" in those WGs counted in Column 3
• Column 5: Count of pages in the "Active I-Ds" counted in Column 4
• (divider)
• Column 6: % of all WGs
• Column 7: % of all "Active I-Ds"
• Column 8: % of all pages
• Last row would be a total of each column from above

Table 2: WG Summary

• Column 1: WG name
• Column 2: Area
• Column 3: Responsible AD
• Column 4: Count of Adopted I-Ds
• Column 5: Count of Adopted I-Ds page count
• Column 6: Count of Published RFCs
• Column 7: Count of Related I-Ds
• Column 8: RFC Publication Rate (calculated by taking Published RFC / Years in existence)
• Column 9: Count of Open Milestones
• Column 10: Count of Open Milestones in the past
• Column 11: Last F2F or interim meeting date
• Last row would be a total of each column from above

All columns would be sortable

Code of Conduct

• I agree to follow the IETF's Code of Conduct

[rjsparks]

Probably want some indication of "uses dateless milestones". Open Milestones in the past doesn't make sense for those.
Could just say N/A or similar in the column.

[rjsparks]

How about "met X times in the last year" and/or "met X times per year over its existence"?

[OR13]

I support this, perhaps we can cut the feature set down a bit to only the low handing fruit, so its easy to get out an MVP.