IETF Logo Mail Archive

Simplifying our processes: Conference Calls

Hannes Tschofenig <hannes.tschofenig@gmx.net> Mon, 03 December 2012 15:41 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99BAF21F86B1 for <ietf@ietfa.amsl.com>; Mon, 3 Dec 2012 07:41:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level:
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eryrF00H15Hz for <ietf@ietfa.amsl.com>; Mon, 3 Dec 2012 07:41:47 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 7C0EE21F85B1 for <ietf@ietf.org>; Mon, 3 Dec 2012 07:41:46 -0800 (PST)
Received: (qmail invoked by alias); 03 Dec 2012 15:41:45 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.109]) [88.115.216.191] by mail.gmx.net (mp004) with SMTP; 03 Dec 2012 16:41:45 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19cO48nLJRco3G4eeDentEH7QOyf9+HmvHvx1LJgr zaIt+LBT6RCwK4
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Simplifying our processes: Conference Calls
Date: Mon, 03 Dec 2012 17:41:43 +0200
Message-Id: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net>
To: "ietf@ietf.org Mailing List" <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
X-Y-GMX-Trusted: 0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2012 15:41:47 -0000

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@ietf.org
"

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. 

Could we please change that? 

Ciao
Hannes

v2.23.0 | Report a Bug | By Email