--On Sunday, March 25, 2012 17:34 +0200 Simon Pietro Romano <[email protected]> wrote:
> Hi John, > > what can I say...I'm really sorry that you had such a hard > time trying to get the link. Simon, thanks, Don't be. I think we are likely to learn far more from the experience than we would have learned had things been more smooth. The underlying problem is real and it isn't your fault. > We actually sent the announcement > on the vmeet mailing list as soon as we were done with the > setup of the tutorial room. Good move, but far too late. The problem for me is that I've overwhelmed by email with a lousy S/N ratio, so I've been following vmeet by reading through the archives every once in a while rather than being subscribed to the mailing list. I finally subscribed this morning, but apparently too late to get your message (nor had it shown up in the archives by the time the session started). FWIW, I'm coincidentally had connectivity problems with one of my ISPs in the last few days, forcefully reminding me of something we often forget: email is designed to be robust but not necessarily real-time. > We had to first find the mixer > guys, then explain to them what we needed in order to connect > to both audio input and audio output, then help them with the > cables and the mixer configuration, and so on and so forth. I > can just add that the organization of the tutorial was a bit > more complicated than with the usual IETF rooms, for the > reasons that you illustrated in detail in your e-mail. Yes. And it shouldn't be your problem. Yes, things were a little special because the tutorial was about a remote participation tool. But, had I decided I wanted to listen in on one of the other tutorials, I would have had equal or greater problems -- in your case, I at least knew where and to whom to complain (you, your "team" list, and the vmeet list). If I had wanted to find out about Tools for Internet-Drafts or OAM, I would not have had even a clue. > And, > yes, it is definitely true that the devil is in the details > and that we do need to better design, prepare and announce > events envisaging the presence of remote participants. As to > the agenda for remote participation, it should be up-to-date > and coherent with the actual program. The links it contains > should be all correct and point to the right Meetecho room > once they are activated (i.e., a few minutes before the > session starts). If you find inconsistencies, just let us know > and we'll fix them up. The one I noticed is that EAI is still listed in spite of our canceling some days ago. The last time I looked, the main agenda showed it as cancelled; the tools agenda shows it as canceled but still shows audio and Jabber links. Whether that is desirable or not is a question that someone should address in a serious way. As EAI co-chair, I certainly don't want a permanent record of whatever is said within range of a microphone in 212/213 on Monday afternoon registered as an EAI audio recording -- nor do I expect to have to watch for such a thing and ask that it be taken down. > I hope you will be able to participate > and have a less stressful experience next time. Anyhow, thank > you for your precious feedback and considerations. Based on the last time I tried to do this (Prague), it will get a lot easier once the regular sessions start Monday morning :-). Paul, let me make a specific suggestion in public. If you have not successfully drawn rpsreqs/ vmeet to a close before Vancouver, stay home. One learns lots of things trying to actually do this that people will forget to tell you about and that don't have quite the same immediacy and impact in reports than if one experiences the frustration in person. One of them is that, for many people, IETF now starts with supplemental meetings on Saturday morning. Leaving people who are sitting in the meeting to cope or make their own arrangements may be reasonable but, if we believe in Internet-based remote participation, the meeting network actually needs to be up by breakfast time Saturday, not sometime Sunday afternoon. Thanks again to all for trying to make this work. best, john _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html. https://www.ietf.org/mailman/listinfo/vmeet
