On 03/12/2012 15:41, Hannes Tschofenig wrote: > Hi all, > > seeing all these discussions related to process improvements I just noticed one annoying thing related to working group conference calls. > > It turns out that the IESG guidelines on that topic (see http://www.ietf.org/iesg/statement/interim-meetings.html) say the following: > " > * Conference calls and jabber sessions must be announced at least two weeks prior to the call or session, and the agenda must be published at least one week before call or session > > * Announcement text must be sent to iesg-secretary@xxxxxxxx > " > > Having just scheduled conference calls for the OAuth mailing list I announced them on the OAuth WG mailing list (where I naively thought it belongs and forgot to re-read the IESG guidelines again). > > Why do we need to announce conference calls (or Jabber chats) on the IETF announce mailing list? How likely is it that someone cares about a working group effort, does not subscribe to the WG mailing list, has not seen a poll about the date and time, and wants to participate in the conference call? To me - this seems rather unlikely. The point is that we work in public, so the whole community should know. I regularly attend WG meetings where I am not subscribed - it's one of the side benefits of the week-long meetings - and who's to say that I might not want to drop into OAuth too? Suppose I happened to notice (I am making this up) that the foobar WG has decided to use the IPv6 Flow Label for an unintended purpose? I'd like to know if they are going to have a conf call, so that I can explain RFC 6437 to them. Otherwise, I have no interest in foobar. > Could we please change that? I hope not. Brian > > Ciao > Hannes > >