John, On 01/04/16 01:28, John C Klensin wrote: > However, I think > there has been a significant breach of community norms and > expectations about openness, consultation, and transparence. I agree that requiring registration of remote attendees without having announced that was a mistake. I agree with those who've said that it might be reasonable to require remote attendees who want to be in the meetecho queue-thing to have registered. But even so, that ought be a thing gets announced ahead of time. Personally I doubt that such registration is really needed even for the queue thing, but I'm willing to believe there may be an anti-DoS benefit there somewhere. That one can ask questions in the jabber room without registering for the IETF meeting is IMO just fine.) So yeah, I think someone (I dunno who) made a mistake. I expect it's not fixable for this meeting, but can be fixed for next time. Having an easier registration experience for those who do want to register as remote attendees is also something to fix. > I > also don't know if that failure was by "the community selected > committee members" or if some staff member is making decisions > without adequate supervision, but it is a problem either way and > I hope that whomever is involved will take the situation > seriously, explain the source or reason for the disconnect to > the community, and evaluate (along with the community) whether > they really want to do whatever job they are doing. That last is just over-reaction and nowhere near justified. I figure someone made a smallish mistake, nobody died, it can be and will be fixed. IMO taking the situation seriously requires us to not over-react in such ways. Cheers, S.
<<attachment: smime.p7s>>