Open martinthomson opened 2 years ago
Description
The current page only includes sessions from the last two meetings and one upcoming, but only the date distinguishes the meeting and only approximately. It would be very helpful if each request had a target meeting and if the page only showed the upcoming meetings (or the most recent one for meetings just passed, for when there are no upcoming requests).
For requests that slip a meeting or appear in subsequent meetings, it might make sense to include multiple meetings. Some BOFs have occurred outside of the regular schedule, so there probably needs to be a way to signal that also.
Code of Conduct
- [x] I agree to follow the IETF's Code of Conduct
Claro 👍
Related to #4029
Making the whole view more aware of history and state would be useful. Some model changes may be needed to easily capture "was discussed between IETF meetings", "was discussed at more than one meeting", and other combinations
Description
The current page only includes sessions from the last two meetings and one upcoming, but only the date distinguishes the meeting and only approximately. It would be very helpful if each request had a target meeting and if the page only showed the upcoming meetings (or the most recent one for meetings just passed, for when there are no upcoming requests).
For requests that slip a meeting or appear in subsequent meetings, it might make sense to include multiple meetings. Some BOFs have occurred outside of the regular schedule, so there probably needs to be a way to signal that also.
Code of Conduct