Describe the issue
The "activity report" in the meeting proceedings (e.g., https://datatracker.ietf.org/meeting/122/proceedings/activity-report/) does not currently show RFC stats correctly. They are all zero, as in the attached screen shot.
This is because ietf.meeting.utils.get_activity_stats() was not updated when RFCs became first-class objects. It is still looking for published_rfc events on draft documents, but these now hang from rfc documnets.
(Incidentally, I'm not sure whether the "0 WGs concluded" is accurate or not - it looks suspicious next to the RFC count, but may just be coincidental)
Code of Conduct
Describe the issue
The "activity report" in the meeting proceedings (e.g., https://datatracker.ietf.org/meeting/122/proceedings/activity-report/) does not currently show RFC stats correctly. They are all zero, as in the attached screen shot.
This is because
ietf.meeting.utils.get_activity_stats()was not updated when RFCs became first-class objects. It is still looking forpublished_rfcevents ondraftdocuments, but these now hang fromrfcdocumnets.(Incidentally, I'm not sure whether the "0 WGs concluded" is accurate or not - it looks suspicious next to the RFC count, but may just be coincidental)
Code of Conduct