Fair point. I guess I’m compartmentalizing the blame.
On Jul 27, 2020, at 9:50 PM, Mark Nottingham <mnot@xxxxxxxx> wrote:Ultimately, we share some collective responsibility; they came here to standardize the thing, after all.Sent from my iPhoneOn 28 Jul 2020, at 12:39 pm, Ben Campbell <ben@xxxxxxxxxxx> wrote:Certainly, that was not my intention. I personally default to Safari, and have more than once had to exit and reenter the room because I forgot to select “Open with…”It’s not clear to me that Meetecho can be blamed for the inconsistent WebRTC implementations among browser vendors—but it is very clear that users are not to blame.Ben.On Jul 27, 2020, at 9:35 PM, Mark Nottingham <mnot@xxxxxxxx> wrote:s/browser choice/compatibility of the tool with different browsers/.
Let’s not blame the user for the limitations of the system we’ve chosen.Sent from my iPhoneOn 28 Jul 2020, at 12:10 pm, Ben Campbell <ben@xxxxxxxxxxx> wrote:In all fairness, DISPATCH was in the first session on Monday morning, at a time when the chairs would normally be asleep. (at least this chair.) We had little opportunity to learn from the mistakes of others :-)IMO, the biggest time eaters were involved individual participants with media problem. These seemed to be caused by browser choices, or by changing media devices after joining. Hopefully future versions of Meetecho will deal with both more gracefully.Ben.On Jul 27, 2020, at 9:39 AM, Richard Barnes <rlb@xxxxxx> wrote:Not sure what session you were in, but DISPATCH spent literally about 15% of its time figuring out how to navigate the multi-phase commit to let someone comment from the floor.On Mon, Jul 27, 2020 at 10:35 AM Peter Yee <peter@xxxxxxxxxx> wrote:I participated in the session that Chris chaired and my perceptions were similar to his. Everything went quite well and that was my first use of MeetEcho (I missed out on the test session). My second session was also pretty good. There were some minor issues with the third session I’m currently in, but that seems to be down to lack of experience and preparation, not so much the tool.
-Peter
Richard Barnes writes:
While there has been a lot of progress since 107, it is clear from the first couple of sessions that there are still a many rough edges that are wasting a lot of WG time. We should take a serious look at whether it's worth investing more in refining this tool, or whether a more standard tool would be appropriate.
On Mon, Jul 27, 2020 at 10:08 AM Chris Inacio <inacio@xxxxxxxx> wrote:
I just want to say that I finished chairing a WG this morning and to say kudos to MeetEcho. Since it seems all I do is spend time in (many different) video conferencing apps, I think the updates to MeetEcho for the full virtual meeting are VERY impressive in the time from “Vancouver” till now.
It went smoother than I would have thought. I think MeetEcho did an amazing job. Thanks to them and all the leadership making the tooling work for this meeting.
There is the human problem of people reading the Jabber chat continuously during the meeting, because it really is now multiple stream communications during the meeting. If I knew the human / UI fix to that, I would suggest it, I don’t. I chair a small working group, so we can multitask that way. Large working groups will like have to the use the queue more formally than we did - with the chairs possibly voicing the jabber room.
