"Purpose" table incorrect

[larseggert]

Describe the issue

The "purpose" table on the top of https://datatracker.ietf.org/meeting/requests seems to be incorrect. It currently lists 90 "regular" timeslot requests only, but when you look at the GEN-area requests, you see the hackathon requests with a purpose of "Coding" - shouldn't those be reported in that table?

Code of Conduct

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

[rjsparks]

Groups of type "team" are currently filtered out of the table - eodir, hackathon, and tools sessions don't show in the summary.

We could change the label of the summary, add a note about teams being filtered out of the summary, add a second summary table for groups that are not teams, or make some other adjustment.

The original request for the table came from Liz to help understand the pressure for the agenda building process. What use case do you have in mind where having the team sessions in the summary would be useful?

[rjsparks]

btw:

datatracker/ietf/meeting/views.py

Line 104 in e5dcc16

request_summary_exclude_group_types = ['team']

datatracker/ietf/meeting/views.py

Lines 2243 to 2248 in e5dcc16

	def request_summary_filter(session):
	if (session.group.area is None
	or session.group.type.slug in request_summary_exclude_group_types
	or session.current_status == 'notmeet'):
	return False
	return True

datatracker/ietf/meeting/views.py

Line 2351 in e5dcc16

summary_sessions = list(filter(request_summary_filter, sessions))

[larseggert]

I don't have a use case, I just noted what I saw as a discrepancy. Some explanatory text would be sufficient.