IETF Logo Mail Archive

[edu-team] updated guidelines for presenters of tutorials

Alice Russo <arusso@amsl.com> Wed, 19 July 2017 16:44 UTC

Return-Path: <arusso@amsl.com>
X-Original-To: edu-team@ietfa.amsl.com
Delivered-To: edu-team@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 555531317CA for <edu-team@ietfa.amsl.com>; Wed, 19 Jul 2017 09:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vJTAAW39eSwA for <edu-team@ietfa.amsl.com>; Wed, 19 Jul 2017 09:44:05 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAA75129482 for <edu-team@ietf.org>; Wed, 19 Jul 2017 09:44:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 35B831CA55B for <edu-team@ietf.org>; Wed, 19 Jul 2017 09:43:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yNCxku9PGEOl for <edu-team@ietf.org>; Wed, 19 Jul 2017 09:43:56 -0700 (PDT)
Received: from dhcp-8340.meeting.ietf.org (dhcp-8340.meeting.ietf.org [31.133.131.64]) by c8a.amsl.com (Postfix) with ESMTPSA id 92ACD1CA547 for <edu-team@ietf.org>; Wed, 19 Jul 2017 09:43:55 -0700 (PDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Alice Russo <arusso@amsl.com>
In-Reply-To: <bd4dc7dd-8dac-9f0b-fef4-3fe003f15323@ripe.net>
Date: Wed, 19 Jul 2017 18:44:00 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <026C4133-4D63-4DEB-B02D-32914C524633@amsl.com>
References: <977c3e38-d6f3-b0e7-f0a4-0abb7d7006db@ripe.net> <bd4dc7dd-8dac-9f0b-fef4-3fe003f15323@ripe.net>
To: EDU Team <edu-team@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/edu-team/3Zxini_ZhXzfqXsSamKZHu2ZiIk>
Subject: [edu-team] updated guidelines for presenters of tutorials
X-BeenThere: edu-team@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Education Team <edu-team.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/edu-team>, <mailto:edu-team-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/edu-team/>
List-Post: <mailto:edu-team@ietf.org>
List-Help: <mailto:edu-team-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/edu-team>, <mailto:edu-team-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 16:44:07 -0000

Hi all,

For your review:
https://trac.ietf.org/trac/edu/wiki/GuidelinesForPresenters
(it's a new version of http://wiki.tools.ietf.org/group/edu/attachment/wiki/Other/GuidelinesEDU.pdf)

Target audience: someone who is considering (or has agreed to) giving a tutorial and needs to know what's involved and 'best practices'.

Potential topics for this page or elsewhere: 
- Where do I send my suggestion for a future tutorial? 
- Where do I send my request to present a Sunday tutorial on a specific topic?

Please feel free to send changes or update yourself (it's a wiki page after all). 

Thanks,
Alice

On Jul 19, 2017, at 4:13 PM, Mirjam Kuehne <mir@ripe.net> wrote:

> Alice suggested to review the presenters guidelines and also send them
> to the presenters before they agree to give a tutorial:
> -  add a section on how to present the overview tutorial
> - add more methodology and deadlines
> - add a “marketing” section: inform your relevant WG lists and others
> that you are giving this tutorial.
> 
> ACTION: Alice will find the doc and will update it. We will then also
> put that doc on the wiki.

v2.23.0 | Report a Bug | By Email