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

Aaron Ding <Aaron.Ding@tudelft.nl> Mon, 21 February 2022 19:28 UTC

Return-Path: <Aaron.Ding@tudelft.nl>
X-Original-To: coin@ietfa.amsl.com
Delivered-To: coin@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 519743A09EF for <coin@ietfa.amsl.com>; Mon, 21 Feb 2022 11:28:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=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 G6s0XNTZnKZR for <coin@ietfa.amsl.com>; Mon, 21 Feb 2022 11:28:38 -0800 (PST)
Received: from mailservice.tudelft.nl (mailservice.tudelft.nl [130.161.131.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78AC73A09FF for <coin@irtf.org>; Mon, 21 Feb 2022 11:28:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by amavis (Postfix) with ESMTP id 856A6640084 for <coin@irtf.org>; Mon, 21 Feb 2022 20:28:35 +0100 (CET)
X-Virus-Scanned: amavisd-new at tudelft.nl
Received: from mailservice.tudelft.nl ([130.161.131.73]) by localhost (tudelft.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id J8sdGUjTaH7D for <coin@irtf.org>; Mon, 21 Feb 2022 20:28:34 +0100 (CET)
Received: from SRV225.tudelft.net (srv225.tudelft.net [131.180.6.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.tudelft.nl (Postfix) with ESMTPS id 0000B640070 for <coin@irtf.org>; Mon, 21 Feb 2022 20:28:33 +0100 (CET)
Received: from SRV223.tudelft.net (131.180.6.23) by SRV225.tudelft.net (131.180.6.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2375.18; Mon, 21 Feb 2022 20:28:32 +0100
Received: from SRV223.tudelft.net ([fe80::89f8:a8a8:176c:252c]) by SRV223.tudelft.net ([fe80::89f8:a8a8:176c:252c%2]) with mapi id 15.01.2375.018; Mon, 21 Feb 2022 20:28:31 +0100
From: Aaron Ding <Aaron.Ding@tudelft.nl>
To: "coin@irtf.org" <coin@irtf.org>
Thread-Topic: ACM SIGCOMM (Amsterdam) calling for tutorials and hackathons
Thread-Index: AQHYJ1kFhBsZhk8S9EaWm6i4J+FBXw==
Date: Mon, 21 Feb 2022 19:28:31 +0000
Message-ID: <39ba6571bc22477687171fc1cab7ad02@tudelft.nl>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_39ba6571bc22477687171fc1cab7ad02tudelftnl_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/ng7AuH-xPQri2je3tPmdoxouVQc>
Subject: [Coin] ACM SIGCOMM (Amsterdam) calling for tutorials and hackathons
X-BeenThere: coin@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "COIN: Computing in the Network" <coin.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/coin>, <mailto:coin-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/coin/>
List-Post: <mailto:coin@irtf.org>
List-Help: <mailto:coin-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/coin>, <mailto:coin-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Feb 2022 19:28:45 -0000

COIN IE/IRTFer,


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