[icnrg] ACM SIGCOMM (Amsterdam) calling for tutorials and hackathons

Aaron Ding <aaron.ding@tum.de> Mon, 21 February 2022 19:34 UTC

Return-Path: <aaron.ding@tum.de>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC8663A0C56 for <icnrg@ietfa.amsl.com>; Mon, 21 Feb 2022 11:34:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.832
X-Spam-Level:
X-Spam-Status: No, score=-0.832 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 OuUd1gsTFCih for <icnrg@ietfa.amsl.com>; Mon, 21 Feb 2022 11:33:56 -0800 (PST)
Received: from mail-out2.informatik.tu-muenchen.de (mail-out2.in.tum.de [131.159.0.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 204F63A0C75 for <icnrg@irtf.org>; Mon, 21 Feb 2022 11:33:55 -0800 (PST)
Received: from mailrelay1.rbg.tum.de (mailrelay1.in.tum.de [131.159.254.14]) by mail-out2.informatik.tu-muenchen.de (Postfix) with ESMTP id 007D9240129; Mon, 21 Feb 2022 20:33:54 +0100 (CET)
Received: by mailrelay1.rbg.tum.de (Postfix, from userid 112) id F2312167; Mon, 21 Feb 2022 20:33:53 +0100 (CET)
Received: from mailrelay1.rbg.tum.de (localhost [127.0.0.1]) by mailrelay1.rbg.tum.de (Postfix) with ESMTP id 9FD08166; Mon, 21 Feb 2022 20:33:53 +0100 (CET)
Received: from vmrbg463.in.tum.de (vmrbg463.in.tum.de [131.159.0.13]) by mailrelay1.rbg.tum.de (Postfix) with ESMTP id 9B515164; Mon, 21 Feb 2022 20:33:53 +0100 (CET)
Received: from webmail.in.tum.de (localhost [IPv6:::1]) by vmrbg463.in.tum.de (Postfix) with ESMTP id 94991100017; Mon, 21 Feb 2022 20:33:53 +0100 (CET)
MIME-Version: 1.0
Date: Mon, 21 Feb 2022 20:33:53 +0100
From: Aaron Ding <aaron.ding@tum.de>
To: quic@ietf.org, icnrg@irtf.org
In-Reply-To: <dc294f0f2e28d2c1cbc23f4798d8d214@tum.de>
References: <d62f56c7fda459a8c18720315e864675@tum.de> <3d572db069341497b07bfc38cfbe20a0@tum.de> <c20f2a5b99a2e1a425fd2fd23e22de1d@tum.de> <dc294f0f2e28d2c1cbc23f4798d8d214@tum.de>
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <f1cdc3ec8f8d72095a2ab8f760e31302@tum.de>
X-Sender: aaron.ding@tum.de
Organization: TU Munich
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/UyHLurJczVWvwPnEX-TCv_YRYNU>
Subject: [icnrg] ACM SIGCOMM (Amsterdam) calling for tutorials and hackathons
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Feb 2022 19:34:01 -0000

IE/IRTF hackers and engineers,

Call for Tutorials and Hackathons at ACM SIGCOMM 2022 in Amsterdam:
https://conferences.sigcomm.org/sigcomm/2022/cf-tutorials.html

We seek to extend the SIGCOMM experience by tutorials on selected topics 
given
by renowned scientists and practitioners in their fields. We therefore 
solicit
proposals for full-day or half-day tutorials on topics relevant to the 
SIGCOMM
community. We also solicit proposals to organize hackathons co-located 
with
SIGCOMM.

Tutorials must cover advanced topics that fit the scope of SIGCOMM and 
are of
current interest to the SIGCOMM community. Tutorials may be lectures,
interactive workshops, hands-on training, or any combination of the 
above.
Successful tutorials educate the community members on emerging methods,
concepts, and tools to expand the research capabilities of the 
community.
Cross-disciplinary topics are also welcome. Exploring diverse ways of
organizing the content, delivering the tutorial, and interacting with 
the
audience are especially encouraged.

A hackathon is an intense goal-oriented team-work activity organized in 
a
sprint-like one-day event, where members from various backgrounds and
expertise come together to work towards the stated goals of the 
hackathon. We
encourage applications from all fields that fit the interest of the 
SIGCOMM
community.

The current plan is that SIGCOMM 2022 will be primarily an in-person
conference. Still, we ask the authors to prepare a "plan B" for an 
online
tutorial/hackathon, in case there are travel restrictions due to 
COVID-19 at
the time of the event.

** Where To Submit
Tutorial and hackathon proposals should be submitted in PDF format, 
should not
exceed three (3) pages in total, and be sent to the Tutorial/Hackathon 
Co-chairs.

** Submit a Tutorial/Hackathon Proposal
Please visit 
https://conferences.sigcomm.org/sigcomm/2022/cf-tutorials.html

** Important dates
Submission deadline: April 9, 2022.
Notification of acceptance: April 30, 2022.

** Tutorial Proposals Must Include
- A motivation for the tutorial (why this, why now, why at SIGCOMM?).
- An outline of the tutorial content, including its tentative schedule 
(over a
half-day or full-day).
- The type of tutorial (e.g., lecture vs. hands-on). It is highly 
recommended
that full-day tutorials should include a hands-on component and not be 
limited
to only lectures. Hands-on components are well-known to be more engaging 
and
pedagogically better in teaching for full-day events.
- References to previous iterations of the tutorial (if applicable) 
including
their date, venue, topics and number of participants and the motivation 
for
the new proposal.
- Requirements for the attendees (e.g., must bring own laptop or other
hardware, familiarity with certain technologies or topics, speed of 
Internet
connection, artifacts to download beforehand, etc.).
- A clear indication whether or not the tutorial artifacts (slides, 
video,
notebooks, containers/VMs, etc.) are allowed to be posted publicly at 
the
onference website.
- Special requirements for a possible online tutorial.

** Hackathon Proposals Must Include
- A motivation for the hackathon (why this, why now, why at SIGCOMM?).
- An outline of the goals and guidelines of the hackathon, including its
tentative schedule.
- References to previous iterations of the hackathon (if applicable) 
including
their date, venue, topics and number of participants and the motivation 
for
the new proposal.
- Requirements for the attendees (e.g., must bring own laptop or other
hardware, familiarity with certain technologies or topics, speed of 
Internet
connection, artifacts to download beforehand, etc.).
- Special requirements for a possible online hackathon.

** Important notes
- Each tutorial will be scheduled at a particular time slot on Monday 
August
22nd, preceding the first day of the main SIGCOMM conference and in 
parallel
with the workshops. The hackathons will be scheduled on Saturday August 
27th,
after the last day of the main SIGCOMM conference.
- Preference in the acceptance decision process will be given to
tutorial/hackathon submissions that (1) provide hands-on experience to 
the
attendees, (2) build on open content that can be freely posted on the
conference website, and (3) formulate a clear and viable plan to hold 
the
event online if the COVID-19 situation requires so and make reasonable 
effort
to prepare for the online format (i.e., use Jupyter notebooks for 
hands-on
material, offer preinstalled VMs/containers, etc.).
- It is recommended that there are up to three speakers for a full-day
tutorial and up to two speakers for a half-day tutorial.
- Upon acceptance of a tutorial/hackathon proposal, either the
Tutorial/Hackathon Co-chairs or the tutorial speakers/hackathon 
organizers can
request a cancellation if there is clear evidence indicating low 
attendance by
the early registration deadline.

Compensation to tutorial speakers and hackathon organizers will not be 
provided.

** Contact the Tutorial/Hackathon Chairs
Yang Chen <chenyang@fudan.edu.cn>
Gabor Retvari <retvari@tmit.bme.hu>

Cheers,
Aaron