Hi Wes, >> 1b) the presentation should have "pause points" where feedback is >> being solicited. > > Hi Kent, > > I love your write up and it's much more detailed than the similar idea I > presented at a hotrfc about a year ago. My thought was to make all > WG meetings a full week long with a similar 'mic queue' formed via > video/audio/whatever chats spread out as well. I love your idea of > pause points above, which is something I hadn't considered for the > presentation side of things. Note that there is nothing stopping a WG > from having multiple topic presentations happening at the same time > too… Cool beans. I’ve gotten positive feedback offline as well. The “pause point” idea could take various forms... A simple implementation would have no break in the presentation video as the author simply says “please provided questions, comments, concerns to this item via ’topic #N’, whereas the system then maintains an list of comments, order by time entered, by anyone, including the presenter, whose response could be a mutli-response (i.e., addressing the collective of comments in one go). A more complex implementation would instead arrange the responses Into a hierarchical tree, effectively mimicking threading. The launch- point for each pause point could be like one of those on-screen link boxes seen on many YouTube videos. A hierarchical tree of responses should provide better topic focus, but may make cross-referencing things said in another branch awkward. > The one idea I talked about that isn't in your list, that you may want > to consider, is a rate-limit for the number of comments you can say in > 24 hours (2? 3?). My thinking was that we needed to avoid the "oh my, > look how much mail arrived while I was sleeping because a topic blew up, > and now its too late to insert my points" problem. This, combined with > the simul-track of every presentation and every wg should bring us close > to the number of comments you can reasonably make at mic lines during a > physical WG meeting. Agreed, there should be something equivalent to cutting off the mic queue. Again, the goal is to bound the wall-clock time for the entire session to roughly what exists today. Here are some thoughts: 1) while your concern might occur, I question how often it would occur. This might be something worth deferring creating a policy for until after more information is known... 2) one idea to suppress "reply-storms” might be to limit each participant to single response per day, or at least until the presenter has had a chance to reply to it. Another idea might be to hide "audience” responses from others until after the presenter has had a chance to reply. Care should be taken, though, as these might have a negative dampening effect on the velocity of idea exchange. Kent
