Make it easy to see what groups have requested a meeting session at an upcoming IETF while that information is being collected #710
Comments
|
@rjsparks@nostrum.com changed priority from |
|
@rjsparks@nostrum.com commented Bumping this to major so we at least talk about it as a group at the Paris codesprint |
|
@rjsparks@nostrum.com changed owner from `` to |
|
@rjsparks@nostrum.com commented This looks like it's been finished (see http://datatracker.ietf.org/meeting/84/requests). |
|
@rjsparks@nostrum.com commented Nope - adam found a bug - the current page is showing reverse conflicts instead of conflicts. When that gets fixed the commit should note that it addresses this ticket. |
|
@adam@nostrum.com changed status from |
|
@adam@nostrum.com changed resolution from `` to |
|
@adam@nostrum.com edited the issue description |
|
@adam@nostrum.com commented Yeah, we appear to have fixed the "conflicts are backwards" problem a while back, but forgot to close this bug. Now we just need to figure out how to advertise the page more effectively. |
keyword_sprintowner:adam@nostrum.comresolution_fixedtype_enhancement| by rjsparks@nostrum.comThe database collects the set of requests for meeting sessions as input into the agenda that's prepared for each IETF meeting. It would be useful to expose this information in an easy to find place. (Perhaps the place where the agenda will eventually appear could point to that place).
The summary should be easy to see which groups have requested a session (and the duration requested), which groups have explicitly indicated they won't meet, and which groups have provided no input yet.
It should be possible to see the full meeting request, including the conflict lists and special requirements, for each group that has requested a session.
It would be nice if this page showed IRTF as well as IETF groups.
Issue migrated from trac:710 at 2022-03-04 01:53:45 +0000
The text was updated successfully, but these errors were encountered: