draft-ietf-shmoo-hackathon-00.txt   draft-ietf-shmoo-hackathon-01.txt 
shmoo C. Eckel shmoo C. Eckel
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Informational 27 May 2021 Intended status: Informational 9 July 2021
Expires: 28 November 2021 Expires: 10 January 2022
Running an IETF Hackathon Running an IETF Hackathon
draft-ietf-shmoo-hackathon-00 draft-ietf-shmoo-hackathon-01
Abstract Abstract
IETF Hackathons encourage the IETF community to collaborate on IETF Hackathons encourage the IETF community to collaborate on
running code related to existing and evolving Internet standards. running code related to existing and evolving Internet standards.
This document provides a set of practices for running IETF This document provides a set of practices that have been used for
Hackathons. running IETF Hackathons. These practices apply to Hackathons in
which both in-person and remote participation are possible with
adaptations for Hackathons that are online only.
Discussion Venues Discussion Venues
This note is to be removed before publishing as an RFC. This note is to be removed before publishing as an RFC.
Discussion of this document takes place on the Stay Home Meet Only Discussion of this document takes place on the Stay Home Meet Only
Online Working Group mailing list (manycouches@ietf.org), which is Online Working Group mailing list (manycouches@ietf.org), which is
archived at https://mailarchive.ietf.org/arch/browse/manycouches/. archived at https://mailarchive.ietf.org/arch/browse/manycouches/.
Source for this draft and an issue tracker can be found at Source for this draft and an issue tracker can be found at
skipping to change at page 1, line 44 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 28 November 2021. This Internet-Draft will expire on 10 January 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 3, line 19 skipping to change at page 3, line 24
6.1. IETF Survey Results . . . . . . . . . . . . . . . . . . . 20 6.1. IETF Survey Results . . . . . . . . . . . . . . . . . . . 20
6.2. Hackathon Survey Results . . . . . . . . . . . . . . . . 21 6.2. Hackathon Survey Results . . . . . . . . . . . . . . . . 21
7. Roles and Responsibilities . . . . . . . . . . . . . . . . . 21 7. Roles and Responsibilities . . . . . . . . . . . . . . . . . 21
7.1. Hackathon Chair(s) . . . . . . . . . . . . . . . . . . . 21 7.1. Hackathon Chair(s) . . . . . . . . . . . . . . . . . . . 21
7.2. Secretariat . . . . . . . . . . . . . . . . . . . . . . . 22 7.2. Secretariat . . . . . . . . . . . . . . . . . . . . . . . 22
7.3. Sponsor . . . . . . . . . . . . . . . . . . . . . . . . . 22 7.3. Sponsor . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.4. Champions of Projects . . . . . . . . . . . . . . . . . . 23 7.4. Champions of Projects . . . . . . . . . . . . . . . . . . 23
7.5. IETF LLC, Director of Communications and Operations (was 7.5. IETF LLC, Director of Communications and Operations (was
ISOC) . . . . . . . . . . . . . . . . . . . . . . . . . . 23 ISOC) . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.6. Judges . . . . . . . . . . . . . . . . . . . . . . . . . 24 7.6. Judges . . . . . . . . . . . . . . . . . . . . . . . . . 24
8. Security Considerations . . . . . . . . . . . . . . . . . . . 24 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 24
8.1. Privacy Considerations . . . . . . . . . . . . . . . . . 24 9. Security Considerations . . . . . . . . . . . . . . . . . . . 24
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 9.1. Privacy Considerations . . . . . . . . . . . . . . . . . 24
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 24 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 24 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 25
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 25
1. Introduction 1. Introduction
IETF Hackathons encourage the IETF community to collaborate on IETF Hackathons encourage the IETF community to collaborate on
running code related to existing and evolving Internet standards. running code related to existing and evolving Internet standards.
IETF Hackathons aim to: IETF Hackathons aim to:
* Advance the pace and relevance of IETF standards activities by * Advance the pace and relevance of IETF standards activities by
bringing the speed and collaborative spirit of open source bringing the speed and collaborative spirit of open source
development into the IETF development into the IETF
skipping to change at page 4, line 16 skipping to change at page 4, line 31
email. Working together to find common understanding of proposals, email. Working together to find common understanding of proposals,
concerns, and solutions that result in improvements to evolving concerns, and solutions that result in improvements to evolving
Internet standards is as important as the development of running code Internet standards is as important as the development of running code
that implements or validates the correctness of these same proposals. that implements or validates the correctness of these same proposals.
Consequently, IETF Hackathons are collaborative events, not Consequently, IETF Hackathons are collaborative events, not
competitions. Any competitiveness among participants is friendly and competitions. Any competitiveness among participants is friendly and
in the spirit of advancing the pace and relevance of new and evolving in the spirit of advancing the pace and relevance of new and evolving
Internet standards. Internet standards.
This document provides a set of practices for running IETF This document provides a set of practices that have been used for
Hackathons. running IETF Hackathons.
2. Timing 2. Timing
The first IETF Hackathon was held the weekend before the start of the The first IETF Hackathon was held the weekend before the start of the
IETF 92 meeting. The rationale was to avoid conflicts yet make it IETF 92 meeting. The rationale was to avoid conflicts yet make it
relatively convenient for those attending the IETF meeting to relatively convenient for those attending the IETF meeting to
participate in the Hackathon as well. Holding the Hackathon on the participate in the Hackathon as well. Holding the Hackathon on the
weekend was also viewed as making it more accessible to non IETF weekend was also viewed as making it more accessible to non IETF
meeting participants, including students and working professionals meeting participants, including students and working professionals
who would have other commitments during the week. The weekend before who would have other commitments during the week. The weekend before
skipping to change at page 19, line 18 skipping to change at page 19, line 18
networking functionality, including static IPv4 and IPv6 addresses, networking functionality, including static IPv4 and IPv6 addresses,
IPv6 only networking, a closed user group, NAT64, and IPv6PD. All of IPv6 only networking, a closed user group, NAT64, and IPv6PD. All of
this, and the IETF network in general, is made available by the start this, and the IETF network in general, is made available by the start
of the Hackathon and in advance for setup to the extent possible. of the Hackathon and in advance for setup to the extent possible.
5.8.1. Remote Networking 5.8.1. Remote Networking
Online only meetings present both a personal networking challenge and Online only meetings present both a personal networking challenge and
a computer networking challenge. The NOC came to the rescue for the a computer networking challenge. The NOC came to the rescue for the
latter with remote networking options to join the IETF network while latter with remote networking options to join the IETF network while
attending the meeting remotely. With a Raspberry Pi 2B, 3B, or 4B, attending a meeting remotely. This evolved into what is now known as
the NOC has a recipe that allow teams to be virtually connected to HackNet (https://hacknet.meeting.ietf.org/), a global Layer 2 VPN
the IETF network with all the previously mentioned options. This designed to support IETF protocol development across teams within the
remote networking capability is available for in-person and online IETF Hackathon. A limited set of devices for connecting to HackNet
only Hackathons. are supported. In addition to layer 2 connectivity, a subset of the
networking capabilities available at in-person meetings are
Virtual connectively to the IETF network remains generally available available. Both the set of devices and the set of networking
between meetings. Individuals or project champions can request capabilities are expected to expand and evolve over time. HackNet is
access through the IETF Ticketing System generally available between IETF meetings. Support is available via
(https://tickets.meeting.ietf.org/newticket). email to ticket@meeting.ietf.org (mailto:ticket@meeting.ietf.org).
5.9. Webex 5.9. Webex
Champions can request a Webex account Champions can request a Webex account
(https://ietf.webex.com/webappng/sites/ietf/dashboard?siteurl=ietf) (https://ietf.webex.com/webappng/sites/ietf/dashboard?siteurl=ietf)
they can use to schedule meetings for their team. These are similar they can use to schedule meetings for their team. These are similar
to the Webex accounts allocated to working group chairs to be used to the Webex accounts allocated to working group chairs to be used
for virtual interim meetings. An account can be requested by a team for virtual interim meetings. An account can be requested by a team
champion at any time. Accounts remain active and available champion at any time. Accounts remain active and available
throughout the duration of the Hackathon and the associated IETF throughout the duration of the Hackathon and the associated IETF
skipping to change at page 24, line 26 skipping to change at page 24, line 26
Judging and awarding of prizes led to confusion regarding the nature Judging and awarding of prizes led to confusion regarding the nature
of the Hackathon, making it appear to some overly competitive. of the Hackathon, making it appear to some overly competitive.
Procurement of appropriate prizes was financially and logistically Procurement of appropriate prizes was financially and logistically
challenging. Arrangement of judges, determination of winners, and challenging. Arrangement of judges, determination of winners, and
awarding of prizes all became more time consuming, especially as the awarding of prizes all became more time consuming, especially as the
number of projects and participants grew. Ultimately, it was deemed number of projects and participants grew. Ultimately, it was deemed
best to eliminate judging, awards, and prizes entirely. Apparently best to eliminate judging, awards, and prizes entirely. Apparently
the IETF community has an innate incentive to participate and present the IETF community has an innate incentive to participate and present
results in the Hackathon. results in the Hackathon.
8. Security Considerations 8. Implementation Status
The practices described in this document have been established, used,
and refined over the course of running numerous IETF Hackathons,
including several at online only IETF meetings. The draft-ietf-
shmoo-hackathon (https://github.com/eckelcu/draft-ietf-shmoo-
hackathon) GitHub repository has been used to collaborate on this
document. The IETF-Hackathon (https://github.com/ietf-hackathon)
GitHub organization contains code associated with IETF Hackathons.
9. Security Considerations
None. None.
8.1. Privacy Considerations 9.1. Privacy Considerations
Participant names and email addresses are displayed publicly in the Participant names and email addresses are displayed publicly in the
Participant List (Section 5.3.1). Participants may opt-in or opt-out Participant List (Section 5.3.1). Participants may opt-in or opt-out
of the display of their email address as part of their registration. of the display of their email address as part of their registration.
The email addresses of individual champions are often shared publicly The email addresses of individual champions are often shared publicly
by the champions on the wiki. This is done voluntarily by individual by the champions on the wiki. This is done voluntarily by individual
champions to make it easier for others to contact them. champions to make it easier for others to contact them.
9. IANA Considerations 10. IANA Considerations
This document has no IANA actions. This document has no IANA actions.
Acknowledgments Acknowledgments
Michael Richardson and Benson Muite provided valuable contributions The IETF Secretariat, notably Alexa Morris and Stephanie McCammon,
to this document. contributed significantly to the creation of the IETF Hackathon and
the practices in this document. Among other things, Alexa drafted
the initial breakdown of Roles and Responsibilities (Section 7), and
Stephanie McCammon created the initial web page and wiki. These have
evolved over time and are used to run each Hackathon.
Greg Wood, Barry Leiba, Michael Richardson, and Benson Muite also
provided significant contributions to the Hackathon and to this
document.
Author's Address Author's Address
Charles Eckel Charles Eckel
Cisco Systems Cisco Systems
United States of America
Email: eckelcu@cisco.com Email: eckelcu@cisco.com
 End of changes. 13 change blocks. 
28 lines changed or deleted 51 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/