On Dec 1, 2024, at 5:44 PM, StJohns, Michael <msj@xxxxxxxxxxxxxxxxxx> wrote:
Given that doing a dispatch during a meeting means that no progress will be made on a given topic until the next meeting…. Sort of…. Would it make any sense to move the dispatch sessions to interim virtual sessions at least a month before a given meeting date?
Mike
1/ not sure about the effectiveness of a virtual dispatch session 2/ also not sure about the actual delay of work expressed above -- how about the idea of interim virtual BOF?
Lixia PS: I meant to say keeping tech dispatch separate from *process*/operation discussions
after going through all the exchanges on the topic, I'd like to second the Mark's following 2 suggestions, - one technical dispatch covering all areas - keep it separate from progress/operation discussions.
my 2 cents, Lixia
Personally - I think that combining DISPATCH (what used to be Applications I mean ART I mean WIT) and SECDISPATCH makes sense, because there's a lot of overlap.
GETDISPATCH, however, is a somewhat different beast. Discussions about how to change our process and similar things need more iteration, and are more appropriate (IMO) in something like a GENAREA WG. Lumping them in with technical proposals leads to a lack of consideration in discussion.
Just my .02.
121attendees mailing list -- 121attendees@xxxxxxxx
To unsubscribe send an email to 121attendees-leave@xxxxxxxx
|
