Handle the newparticipant group better in meeting proceedings · Issue #8781 · ietf-tools/datatracker · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of the time of filing this issue, the newly created "newparticipant" group, which hosted all of the new participant sessions at 122, does not show up on the meeting proceedings.
This new group represents a change in the way the IETF is thinking about the structure of the training/introductory sessions before a meeting and working through how it is captured both in the agenda and proceedings going forward needs some design thinking rather than just trying to make it work given the current agenda and proceedings code.
I think this concept is likely to stick with us for the foreseeable future and the likely right thing to do is treat it as a special singleton, giving it its own section in the proceedings.
But we should review/discuss if it's truly unique, or if eodir, systers, or other such groups are the same kind of thing and we need to adjust how we handle those so that the new newparticipant group is handled the same way.
Whatever path we take, there are new requirements here about whether sessions should appear on the agenda but not on the proceedings (such as lunches that don't result in any materials).
Description
As of the time of filing this issue, the newly created "newparticipant" group, which hosted all of the new participant sessions at 122, does not show up on the meeting proceedings.
This new group represents a change in the way the IETF is thinking about the structure of the training/introductory sessions before a meeting and working through how it is captured both in the agenda and proceedings going forward needs some design thinking rather than just trying to make it work given the current agenda and proceedings code.
I think this concept is likely to stick with us for the foreseeable future and the likely right thing to do is treat it as a special singleton, giving it its own section in the proceedings.
But we should review/discuss if it's truly unique, or if eodir, systers, or other such groups are the same kind of thing and we need to adjust how we handle those so that the new newparticipant group is handled the same way.
Whatever path we take, there are new requirements here about whether sessions should appear on the agenda but not on the proceedings (such as lunches that don't result in any materials).
Code of Conduct
The text was updated successfully, but these errors were encountered: