draft-ietf-shmoo-hackathon-02.txt   draft-ietf-shmoo-hackathon-03.txt 
shmoo C. Eckel shmoo C. Eckel
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Informational 10 November 2021 Intended status: Informational 22 November 2021
Expires: 14 May 2022 Expires: 26 May 2022
Running an IETF Hackathon Running an IETF Hackathon
draft-ietf-shmoo-hackathon-02 draft-ietf-shmoo-hackathon-03
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 that have been used for This document provides a set of practices that have been used for
running IETF Hackathons. These practices apply to Hackathons in running IETF Hackathons. These practices apply to Hackathons in
which both in-person and remote participation are possible with which both in-person and remote participation are possible with
adaptations for Hackathons that are online only. adaptations for Hackathons that are online only.
skipping to change at page 1, line 46 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 14 May 2022. This Internet-Draft will expire on 26 May 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
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License text extracted from this document must include Revised BSD License text as
as described in Section 4.e of the Trust Legal Provisions and are described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License. provided without warranty as described in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Agenda . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1. Agenda . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2. Hackdemo Happy Hour . . . . . . . . . . . . . . . . . . . 6 2.2. Hackdemo Happy Hour . . . . . . . . . . . . . . . . . . . 6
2.3. Code Lounge . . . . . . . . . . . . . . . . . . . . . . . 7 2.3. Code Lounge . . . . . . . . . . . . . . . . . . . . . . . 7
2.4. Code Sprint . . . . . . . . . . . . . . . . . . . . . . . 7 2.4. Code Sprint . . . . . . . . . . . . . . . . . . . . . . . 7
2.5. Online Only . . . . . . . . . . . . . . . . . . . . . . . 8 2.5. Online Only . . . . . . . . . . . . . . . . . . . . . . . 7
3. Funding . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3. Funding . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1. Sponsorship . . . . . . . . . . . . . . . . . . . . . . . 9 3.1. Sponsorship . . . . . . . . . . . . . . . . . . . . . . . 8
3.2. Expenses . . . . . . . . . . . . . . . . . . . . . . . . 9 3.2. Expenses . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2.1. In-person Event Expenses . . . . . . . . . . . . . . 9 3.2.1. In-person Event Expenses . . . . . . . . . . . . . . 9
3.2.2. Remote Participation Expenses . . . . . . . . . . . . 11 3.2.2. Remote Participation Expenses . . . . . . . . . . . . 11
4. Project Presentations . . . . . . . . . . . . . . . . . . . . 12 4. Project Presentations . . . . . . . . . . . . . . . . . . . . 11
4.1. Project Pitches . . . . . . . . . . . . . . . . . . . . . 12 4.1. Project Pitches . . . . . . . . . . . . . . . . . . . . . 12
4.2. Results Summaries . . . . . . . . . . . . . . . . . . . . 12 4.2. Results Summaries . . . . . . . . . . . . . . . . . . . . 12
4.2.1. Templates . . . . . . . . . . . . . . . . . . . . . . 13 4.2.1. Templates . . . . . . . . . . . . . . . . . . . . . . 12
4.3. Upload to GitHub . . . . . . . . . . . . . . . . . . . . 13 4.3. Upload to GitHub . . . . . . . . . . . . . . . . . . . . 13
4.4. Presenting in Person . . . . . . . . . . . . . . . . . . 14 4.4. Presenting in Person . . . . . . . . . . . . . . . . . . 13
4.5. Presenting Remotely . . . . . . . . . . . . . . . . . . . 14 4.5. Presenting Remotely . . . . . . . . . . . . . . . . . . . 13
5. Tooling . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5. Tooling . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1. Datatracker . . . . . . . . . . . . . . . . . . . . . . . 14 5.1. Datatracker . . . . . . . . . . . . . . . . . . . . . . . 14
5.2. IETF Website . . . . . . . . . . . . . . . . . . . . . . 14 5.2. IETF Website . . . . . . . . . . . . . . . . . . . . . . 14
5.2.1. Hackathon Website . . . . . . . . . . . . . . . . . . 14 5.2.1. Hackathon Website . . . . . . . . . . . . . . . . . . 14
5.2.2. Meeting Website . . . . . . . . . . . . . . . . . . . 15 5.2.2. Meeting Website . . . . . . . . . . . . . . . . . . . 14
5.3. Registration . . . . . . . . . . . . . . . . . . . . . . 15 5.3. Registration . . . . . . . . . . . . . . . . . . . . . . 14
5.3.1. Participant List . . . . . . . . . . . . . . . . . . 15 5.3.1. Participant List . . . . . . . . . . . . . . . . . . 15
5.3.2. Caps on Registrations . . . . . . . . . . . . . . . . 15 5.3.2. Caps on Registrations . . . . . . . . . . . . . . . . 15
5.4. Meeting Wiki . . . . . . . . . . . . . . . . . . . . . . 15 5.4. Meeting Wiki . . . . . . . . . . . . . . . . . . . . . . 15
5.4.1. Hackathon . . . . . . . . . . . . . . . . . . . . . . 16 5.4.1. Hackathon . . . . . . . . . . . . . . . . . . . . . . 15
5.4.2. Lost and Found . . . . . . . . . . . . . . . . . . . 16 5.4.2. Lost and Found . . . . . . . . . . . . . . . . . . . 15
5.4.3. Results Presentation Schedule . . . . . . . . . . . . 16 5.4.3. Results Presentation Schedule . . . . . . . . . . . . 16
5.4.4. In Person Only . . . . . . . . . . . . . . . . . . . 16 5.4.4. In Person Only . . . . . . . . . . . . . . . . . . . 16
5.4.5. Online Only . . . . . . . . . . . . . . . . . . . . . 17 5.4.5. Online Only . . . . . . . . . . . . . . . . . . . . . 16
5.5. Email List . . . . . . . . . . . . . . . . . . . . . . . 17 5.5. Email List . . . . . . . . . . . . . . . . . . . . . . . 17
5.5.1. Hackathon Chairs Email Alias . . . . . . . . . . . . 18 5.5.1. Hackathon Chairs Email Alias . . . . . . . . . . . . 17
5.6. GitHub . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.6. GitHub . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.7. Meetecho . . . . . . . . . . . . . . . . . . . . . . . . 18 5.7. Meetecho . . . . . . . . . . . . . . . . . . . . . . . . 17
5.8. Network . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.8. Network . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.8.1. Remote Networking . . . . . . . . . . . . . . . . . . 19 5.8.1. Remote Networking . . . . . . . . . . . . . . . . . . 18
5.9. Webex . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.9. Webex . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.10. Gather . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.10. Gather . . . . . . . . . . . . . . . . . . . . . . . . . 19
6. Statistics and Metrics . . . . . . . . . . . . . . . . . . . 20 6. Statistics and Metrics . . . . . . . . . . . . . . . . . . . 19
6.1. IETF Survey Results . . . . . . . . . . . . . . . . . . . 20 6.1. IETF Survey Results . . . . . . . . . . . . . . . . . . . 19
6.2. Hackathon Survey Results . . . . . . . . . . . . . . . . 21 6.2. Hackathon Survey Results . . . . . . . . . . . . . . . . 20
7. Roles and Responsibilities . . . . . . . . . . . . . . . . . 21 7. Roles and Responsibilities . . . . . . . . . . . . . . . . . 20
7.1. Hackathon Chair(s) . . . . . . . . . . . . . . . . . . . 21 7.1. Hackathon Chair(s) . . . . . . . . . . . . . . . . . . . 20
7.2. Secretariat . . . . . . . . . . . . . . . . . . . . . . . 22 7.2. Secretariat . . . . . . . . . . . . . . . . . . . . . . . 21
7.3. Sponsor . . . . . . . . . . . . . . . . . . . . . . . . . 22 7.3. Sponsor . . . . . . . . . . . . . . . . . . . . . . . . . 21
7.4. Champions of Projects . . . . . . . . . . . . . . . . . . 23 7.4. Champions of Projects . . . . . . . . . . . . . . . . . . 22
7.5. IETF LLC, Director of Communications and Operations (was 7.5. IETF LLC, Director of Communications and Operations (was
ISOC) . . . . . . . . . . . . . . . . . . . . . . . . . . 23 ISOC) . . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.6. Judges . . . . . . . . . . . . . . . . . . . . . . . . . 24 7.6. Judges . . . . . . . . . . . . . . . . . . . . . . . . . 23
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 24 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 23
9. Security Considerations . . . . . . . . . . . . . . . . . . . 24 9. Security Considerations . . . . . . . . . . . . . . . . . . . 23
9.1. Privacy Considerations . . . . . . . . . . . . . . . . . 24 9.1. Privacy Considerations . . . . . . . . . . . . . . . . . 23
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
11. Informative References . . . . . . . . . . . . . . . . . . . 25 11. Informative References . . . . . . . . . . . . . . . . . . . 24
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 27 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 27
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 27 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 27
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
skipping to change at page 13, line 19 skipping to change at page 12, line 47
that have indicated the desire to present. This maximum is strictly that have indicated the desire to present. This maximum is strictly
enforced to ensure all teams have the opportunity to present their enforced to ensure all teams have the opportunity to present their
results. Maximum durations of 3-5 minutes are typical. results. Maximum durations of 3-5 minutes are typical.
4.2.1. Templates 4.2.1. Templates
Project results presentation templates provides guidance on what to Project results presentation templates provides guidance on what to
cover. The use of these templates is optional. They are made cover. The use of these templates is optional. They are made
available in various in various formats in a GitHub repo created available in various in various formats in a GitHub repo created
specifically for the presentations for each IETF Hackathon, e.g., specifically for the presentations for each IETF Hackathon, e.g.,
https://github.com/ietf-hackathon/ietf110-project-presentations [RESULTS-PRESENTATIONS].
(https://github.com/ietf-hackathon/ietf110-project-presentations).
4.2.1.1. PPTX 4.2.1.1. PPTX
For portability, presentations that use this template should be made For portability, presentations that use this template should be made
exported into PDF format as well. exported into PDF format as well.
4.2.1.2. HTML format 4.2.1.2. HTML format
This template should render within any browser. It can be rendered This template should render within any browser. It can be rendered
as a slideshow using [REMARK]. as a slideshow using [REMARK].
4.3. Upload to GitHub 4.3. Upload to GitHub
All presentation are uploaded to the GitHub repo created the All presentation are uploaded to the GitHub repo created the
Hackathon, e.g., https://github.com/ietf-hackathon/ietf110-project- Hackathon, e.g., [RESULTS-PRESENTATIONS]. The contents of this repo
presentations (https://github.com/ietf-hackathon/ietf110-project- are used as the source for all project presentations at the end of
presentations). The contents of this repo are used as the source for the Hackathon and remain as a reference after the Hackathon.
all project presentations at the end of the Hackathon and remain as a
reference after the Hackathon.
One must be a member of the [IETF-HACKATHON-GITHUB] organization to One must be a member of the [IETF-HACKATHON-GITHUB] organization to
upload a new presentation or update/replace an existing presentation. upload a new presentation or update/replace an existing presentation.
To be added as a member, presenters are asked to: To be added as a member, presenters are asked to:
* include the name by which they are known in their GitHub profile * include the name by which they are known in their GitHub profile
* enable two factor authentication (2FA) * enable two factor authentication (2FA)
skipping to change at page 15, line 28 skipping to change at page 15, line 7
* free * free
* required * required
As with meeting registration, registrants for the Hackathon As with meeting registration, registrants for the Hackathon
acknowledge the [NOTE-WELL] during the registration process. acknowledge the [NOTE-WELL] during the registration process.
5.3.1. Participant List 5.3.1. Participant List
An active list of all registered participants, e.g., An active list of all registered participants, e.g., [PARTICIPANTS],
https://registration.ietf.org/110/participants/hackathon/ is maintained by the Secretariat. Important information displayed
(https://registration.ietf.org/110/participants/hackathon/), is for each registrant includes the set of projects and technologies in
maintained by the Secretariat. Important information displayed for
each registrant includes the set of projects and technologies in
which each participant is interested and an email address. This which each participant is interested and an email address. This
information is optional at the time of registration and may be information is optional at the time of registration and may be
updated or removed by editing one's registration. updated or removed by editing one's registration.
5.3.2. Caps on Registrations 5.3.2. Caps on Registrations
Registrations were capped for the first several Hackathons. This was Registrations were capped for the first several Hackathons. This was
done both for space and costs considerations. The cap was hit done both for space and costs considerations. The cap was hit
multiple times, each time resulting in temporary confusion and multiple times, each time resulting in temporary confusion and
frustration among would be registrants, followed by the cap being frustration among would be registrants, followed by the cap being
increased. Currently, there are no caps enforced by the registration increased. Currently, there are no caps enforced by the registration
system. system.
5.4. Meeting Wiki 5.4. Meeting Wiki
The [MEETING-WIKI] serves as the primary source of information for The [MEETING-WIKI] serves as the primary source of information for
each Hackathon. each Hackathon.
5.4.1. Hackathon 5.4.1. Hackathon
A page within the meeting wiki, e.g., A page within the meeting wiki, e.g., [IETF-110-HACKATHON-WIKI], is
https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon
(https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon), is
created by the Secretariat for each Hackathon and initialized with created by the Secretariat for each Hackathon and initialized with
information that is based largely on the information from the information that is based largely on the information from the
previous Hackathon. Once created, the Hackathon Chairs update and previous Hackathon. Once created, the Hackathon Chairs update and
moderate this page. Champions are requested and responsible for moderate this page. Champions are requested and responsible for
adding information about projects for which they are a champion. adding information about projects for which they are a champion.
Anyone can edit the wiki by logging in using their Datatracker login Anyone can edit the wiki by logging in using their Datatracker login
credentials. Credentials can be obtained by creating a credentials. Credentials can be obtained by creating a
[DATATRACKER-ACCOUNT]. [DATATRACKER-ACCOUNT].
5.4.2. Lost and Found 5.4.2. Lost and Found
A Lost and Found wiki page, e.g., A Lost and Found wiki page, e.g., [LOST-AND-FOUND], is created by the
https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/lost&found Chairs for each Hackathon. Participants looking for a team are
(https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/ encouraged to add themselves to the "Skills to Offer" table,
lost&found), is created by the Chairs for each Hackathon. providing some information about their skills and interests. This
Participants looking for a team are encouraged to add themselves to will help others with matching needs and/or interests find them.
the "Skills to Offer" table, providing some information about their Champions wanting help on their projects are encouraged to add their
skills and interests. This will help others with matching needs and/ teams to the "Skills Needed" table, providing some information about
or interests find them. Champions wanting help on their projects are the skills they seek.
encouraged to add their teams to the "Skills Needed" table, providing
some information about the skills they seek.
5.4.3. Results Presentation Schedule 5.4.3. Results Presentation Schedule
A Results Presentation Schedule wiki page, e.g., A Results Presentation Schedule wiki page, e.g.,
https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/ [RESULTS-PRESENTATION-SCHEDULE], is created by the Chairs for each
resultspresentationschedule
(https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/
resultspresentationschedule), is created by the Chairs for each
Hackathon. Hackathon teams are welcome and encouraged to present Hackathon. Hackathon teams are welcome and encouraged to present
their results during the Hackathon Closing. Hackathon teams add the their results during the Hackathon Closing. Hackathon teams add the
name of their project and the name of the presenter to the table at name of their project and the name of the presenter to the table at
the bottom of this page. the bottom of this page.
5.4.4. In Person Only 5.4.4. In Person Only
The following wiki pages are applicable for in-person Hackathons The following wiki pages are applicable for in-person Hackathons
only. only.
5.4.4.1. Hackdemo Happy Hour 5.4.4.1. Hackdemo Happy Hour
A Hackdemo Happy Hour wiki page, e.g., A Hackdemo Happy Hour wiki page, e.g., [HACKDEMO], is created by the
https://trac.ietf.org/trac/ietf/meeting/wiki/106hackdemo Chairs for each Hackathon. Champions are welcome and encouraged to
(https://trac.ietf.org/trac/ietf/meeting/wiki/106hackdemo), is add their project by entering the project name/acronym and a contact
created by the Chairs for each Hackathon. Champions are welcome and name and email address in the table displayed on the page.
encouraged to add their project by entering the project name/acronym
and a contact name and email address in the table displayed on the
page.
5.4.4.2. Code Lounge 5.4.4.2. Code Lounge
A Code Lounge wiki page, e.g., A Code Lounge wiki page, e.g., [CODE-LOUNGE], is created by the
https://trac.ietf.org/trac/ietf/meeting/wiki/106codelounge Chairs for each Hackathon. Champions are welcome and encouraged to
(https://trac.ietf.org/trac/ietf/meeting/wiki/106codelounge), is add their project by entering the project name/acronym and a contact
created by the Chairs for each Hackathon. Champions are welcome and name and email address in the table displayed on the page.
encouraged to add their project by entering the project name/acronym
and a contact name and email address in the table displayed on the
page.
5.4.5. Online Only 5.4.5. Online Only
The following wiki pages are applicable for online Hackathons only. The following wiki pages are applicable for online Hackathons only.
5.4.5.1. Team Schedule 5.4.5.1. Team Schedule
A Team Schedule wiki page, e.g., A Team Schedule wiki page, e.g., [TEAM-SCHEDULE], is created by the
https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/ Chairs for each online only Hackathon. Online only Hackathons take
teamschedule place globally for an entire week. It is up to individual project
(https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/ teams to determine the preferred dates, times, and ways to meet to
teamschedule), is created by the Chairs for each online only work on their project within the context of that week (e.g., Zoom,
Hackathon. Online only Hackathons take place globally for an entire Webex, Slack). This page is meant to help facilitate coordination of
week. It is up to individual project teams to determine the schedules within and across teams.
preferred dates, times, and ways to meet to work on their project
within the context of that week (e.g., Zoom, Webex, Slack). This
page is meant to help facilitate coordination of schedules within and
across teams.
5.5. Email List 5.5. Email List
The Hackathon email list, [EMAIL-LIST], is used for all email The Hackathon email list, [EMAIL-LIST], is used for all email
communication and announcement related to the Hackathon. All communication and announcement related to the Hackathon. All
registrants and given the option to subscribe to the list. Anyone registrants and given the option to subscribe to the list. Anyone
interested in staying up to date on the Hackathon is able to interested in staying up to date on the Hackathon is able to
subscribe at any time. subscribe at any time.
5.5.1. Hackathon Chairs Email Alias 5.5.1. Hackathon Chairs Email Alias
skipping to change at page 18, line 22 skipping to change at page 17, line 30
The [IETF-HACKATHON-GITHUB] is used to share code, presentations, and The [IETF-HACKATHON-GITHUB] is used to share code, presentations, and
other artifacts at IETF Hackathons. The Hackathon Chairs are other artifacts at IETF Hackathons. The Hackathon Chairs are
responsible for administering the GitHub organization. responsible for administering the GitHub organization.
Code for Hackathon projects often exist elsewhere, which is perfectly Code for Hackathon projects often exist elsewhere, which is perfectly
fine. Anyone needing a place to host code for the Hackathon can fine. Anyone needing a place to host code for the Hackathon can
request the creating of a repository for their project. request the creating of a repository for their project.
A repository is created and maintained by the Chairs for each A repository is created and maintained by the Chairs for each
Hackathon, e.g., https://github.com/ietf-hackathon/ietf110-project- Hackathon, e.g., [RESULTS-PRESENTATIONS]. This repo is for
presentations (https://github.com/ietf-hackathon/ietf110-project- participants to upload project presentations. The contents of this
presentations). This repo is for participants to upload project repo are used as the source for all project presentations at the end
presentations. The contents of this repo are used as the source for of the Hackathon and remain as a reference after the Hackathon.
all project presentations at the end of the Hackathon and remain as a
reference after the Hackathon.
5.7. Meetecho 5.7. Meetecho
[MEETECHO] is used for the kickoff and closing sessions of the [MEETECHO] is used for the kickoff and closing sessions of the
Hackathon. This provides many capabilities, including the following: Hackathon. This provides many capabilities, including the following:
* allows participants to join Hackathon sessions in person or * allows participants to join Hackathon sessions in person or
remotely remotely
* validate registration of participants at time of joining Hackathon * validate registration of participants at time of joining Hackathon
skipping to change at page 19, line 38 skipping to change at page 18, line 38
latter with an experimental mechanism to join the IETF network while latter with an experimental mechanism to join the IETF network while
attending a meeting remotely. This evolved into what is now known as attending a meeting remotely. This evolved into what is now known as
[HACKNET], a global Layer 2 VPN designed to support IETF protocol [HACKNET], a global Layer 2 VPN designed to support IETF protocol
development across teams within the IETF Hackathon. A limited set of development across teams within the IETF Hackathon. A limited set of
devices for connecting to HackNet are supported. In addition to devices for connecting to HackNet are supported. In addition to
layer 2 connectivity, a subset of the networking capabilities layer 2 connectivity, a subset of the networking capabilities
available at in-person meetings are available. Both the set of available at in-person meetings are available. Both the set of
devices and the set of networking capabilities are expected to expand devices and the set of networking capabilities are expected to expand
and evolve over time. However, it is important to note that HackNet and evolve over time. However, it is important to note that HackNet
is still an experiment and not a production service. Best effort is still an experiment and not a production service. Best effort
support is available via email to ticket@meeting.ietf.org support is available via email to [TICKET].
(mailto:ticket@meeting.ietf.org).
5.9. Webex 5.9. Webex
Champions can request a [WEBEX-ACCOUNT] they can use to schedule Champions can request a [WEBEX-ACCOUNT] they can use to schedule
meetings for their team. These are similar to the Webex accounts meetings for their team. These are similar to the Webex accounts
allocated to working group chairs to be used for virtual interim allocated to working group chairs to be used for virtual interim
meetings. An account can be requested by a team champion at any meetings. An account can be requested by a team champion at any
time. Accounts remain active and available throughout the duration time. Accounts remain active and available throughout the duration
of the Hackathon and the associated IETF meeting. A project name may of the Hackathon and the associated IETF meeting. A project name may
be used in place of "Working Group Name" in the request form. be used in place of "Working Group Name" in the request form.
skipping to change at page 21, line 35 skipping to change at page 20, line 35
chairs share responsibilities and workload. The Chairs work very chairs share responsibilities and workload. The Chairs work very
closely with the Secretariat on all responsibilities. Key closely with the Secretariat on all responsibilities. Key
responsibilities include: responsibilities include:
* Organize and deliver a Hackathon at each IETF meeting, soliciting * Organize and deliver a Hackathon at each IETF meeting, soliciting
help from all other roles to do much of the heavy lifting help from all other roles to do much of the heavy lifting
* Encourage and provide guidance to champions who volunteer to lead * Encourage and provide guidance to champions who volunteer to lead
projects projects
* Maintain the Hackathon wiki, e.g., * Maintain the Hackathon wiki, e.g., [IETF-110-HACKATHON-WIKI], and
https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon
(https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon), and
all of its child pages. all of its child pages.
* Moderate Hackathon email list (Section 5.5) * Moderate Hackathon email list (Section 5.5)
* [REQUEST-SESSIONS] for the Hackathon opening and closing in the * [REQUEST-SESSIONS] for the Hackathon opening and closing in the
IETF meeting IETF meeting
* Emcee the Hackathon, including the opening and closing sessions * Emcee the Hackathon, including the opening and closing sessions
and announcements in between and announcements in between
* Create and manage the GitHub repository used for each Hackathon, * Create and manage the GitHub repository used for each Hackathon,
e.g., https://github.com/ietf-hackathon/ietf110-project- e.g.,[RESULTS-PRESENTATIONS]
presentations (https://github.com/ietf-hackathon/ietf110-project-
presentations)
* Serve as main point of contact for all Hackathon questions and * Serve as main point of contact for all Hackathon questions and
concerns concerns
7.2. Secretariat 7.2. Secretariat
Key responsibilities include: Key responsibilities include:
* Configure and manage Hackathon registration system (Section 5.3) * Configure and manage Hackathon registration system (Section 5.3)
* Maintain Hackathon website (Section 5.2.1) * Maintain Hackathon website (Section 5.2.1)
* Create and maintain web page for each Hackathon, e.g., * Create and maintain web page for each Hackathon, e.g.,
https://www.ietf.org/how/runningcode/hackathons/110-hackathon/ [IETF-110-HACKATHON-WEBSITE]
(https://www.ietf.org/how/runningcode/hackathons/110-hackathon/)
* Create wiki page for each Hackathon, e.g., * Create wiki page for each Hackathon, e.g.,
https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon [IETF-110-HACKATHON-WIKI]. This is initialized and updated at
(https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon). This times by the Secretariat, but the Chair(s) are ultimately
is initialized and updated at times by the Secretariat, but the responsible for maintaining it.
Chair(s) are ultimately responsible for maintaining it.
* Handle venue logistics for Hackathon, Hackdemo Happy Hour, and * Handle venue logistics for Hackathon, Hackdemo Happy Hour, and
Code Lounge (e.g., reserve room, food and beverages, AV, etc.) Code Lounge (e.g., reserve room, food and beverages, AV, etc.)
* Internal IETF promotion (e.g., email messages to IETF community) * Internal IETF promotion (e.g., email messages to IETF community)
* Assist with external outreach, as needed, including finding * Assist with external outreach, as needed, including finding
sponsors sponsors
* Validate Hackathon registrations for in-person participants, * Validate Hackathon registrations for in-person participants,
skipping to change at page 23, line 42 skipping to change at page 22, line 38
* Welcome and organize members of the team * Welcome and organize members of the team
* Provide focus, guidance, and leadership for the project * Provide focus, guidance, and leadership for the project
7.5. IETF LLC, Director of Communications and Operations (was ISOC) 7.5. IETF LLC, Director of Communications and Operations (was ISOC)
Key responsibilities include: Key responsibilities include:
* External promotion outside of IETF, including web search engine ad * External promotion outside of IETF, including web search engine ad
words, social media posts, and listing on external event calendars words, social media posts, and listing on external event calendars
such as https://www.ripe.net/participate/meetings/calendar such as [RIPE-CALENDAR] and [NSRC-CALENDAR].
(https://www.ripe.net/participate/meetings/calendar) and
https://nsrc.org/calendar/ (https://nsrc.org/calendar/).
* Outreach to local universities * Outreach to local universities
* Provide photographer, including optional team photos and candid * Provide photographer, including optional team photos and candid
photos of collaborating during in-person events photos of collaborating during in-person events
* Laptop stickers (Section 3.2.1.4) at in-person events * Laptop stickers (Section 3.2.1.4) at in-person events
7.6. Judges 7.6. Judges
skipping to change at page 25, line 15 skipping to change at page 24, line 15
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.
10. IANA Considerations 10. IANA Considerations
This document has no IANA actions. This document has no IANA actions.
11. Informative References 11. Informative References
[AGENDAS] "agendas", n.d., [AGENDAS] "IETF Meeting Agenda", n.d.,
<https://datatracker.ietf.org/meeting/agenda/>. <https://datatracker.ietf.org/meeting/agenda/>.
[CODE-LOUNGE]
"IETF 106 Code Lounge", n.d.,
<https://trac.ietf.org/trac/ietf/meeting/
wiki/106codelounge>.
[DATATRACKER] [DATATRACKER]
"Datatracker", n.d., <https://datatracker.ietf.org/>. "IETF Datatracker", n.d., <https://datatracker.ietf.org/>.
[DATATRACKER-ACCOUNT] [DATATRACKER-ACCOUNT]
"Datatracker account", n.d., "IETF Datatracker Account Creation", n.d.,
<https://datatracker.ietf.org/accounts/create/>. <https://datatracker.ietf.org/accounts/create/>.
[EMAIL-ALIAS] [EMAIL-ALIAS]
"hackathon-chairs@ietf.org", n.d., <mailto:hackathon- "IETF Hackathon Chairs Email Alias", n.d.,
chairs@ietf.org>. <mailto:hackathon-chairs@ietf.org>.
[EMAIL-LIST] [EMAIL-LIST]
"hackathon@ietf.org", n.d., "IETF Hackathon Email List", n.d.,
<https://www.ietf.org/mailman/listinfo/Hackathon/>. <https://www.ietf.org/mailman/listinfo/Hackathon/>.
[GATHER] "Gather", n.d., <https://gather.town/>. [GATHER] "Gather", n.d., <https://gather.town/>.
[GITHUB-REPO] [GITHUB-REPO]
"draft-ietf-shmoo-hackathon", n.d., "GitHub Repository for draft-ietf-shmoo-hackathon", n.d.,
<https://github.com/eckelcu/draft-ietf-shmoo-hackathon/>. <https://github.com/eckelcu/draft-ietf-shmoo-hackathon/>.
[HACKATHON-WEBSITE] [HACKATHON-WEBSITE]
"Hackathon website", n.d., "IETF Hackathon Website", n.d.,
<https://www.ietf.org/how/runningcode/hackathons/>. <https://www.ietf.org/how/runningcode/hackathons/>.
[HACKDEMO] "IETF 106 Hackdemo Happy Hour", n.d.,
<https://trac.ietf.org/trac/ietf/meeting/
wiki/106hackdemo>.
[HACKNET] "HackNet", n.d., <https://hacknet.meeting.ietf.org/>. [HACKNET] "HackNet", n.d., <https://hacknet.meeting.ietf.org/>.
[HEDGEDOC] "HedgeDoc", n.d., <https://notes.ietf.org/>. [HEDGEDOC] "HedgeDoc", n.d., <https://notes.ietf.org/>.
[IETF-106-SURVEY] [IETF-106-SURVEY]
"IETF 106 Meeting Survey", n.d., "IETF 106 Meeting Survey", n.d.,
<https://www.ietf.org/media/documents/ <https://www.ietf.org/media/documents/
IETF_106_Meeting_Survey.pdf>. IETF_106_Meeting_Survey.pdf>.
[IETF-108-HACKATHON-WIKI] [IETF-108-HACKATHON-WIKI]
"IETF 108 Hackathon Wiki", n.d., "IETF 108 Hackathon Wiki", n.d.,
<https://trac.ietf.org/trac/ietf/meeting/ <https://trac.ietf.org/trac/ietf/meeting/
wiki/108hackathon/>. wiki/108hackathon/>.
[IETF-110-HACKATHON-WEBSITE]
"IETF 110 Hackathon Website", n.d.,
<https://www.ietf.org/how/runningcode/
hackathons/110-hackathon/>.
[IETF-110-HACKATHON-WIKI]
"IETF 110 Hackathon Wiki", n.d.,
<https://trac.ietf.org/trac/ietf/meeting/
wiki/110hackathon/>.
[IETF-110-SURVEY] [IETF-110-SURVEY]
"IETF 110 Meeting Survey", n.d., <https://ql.tc/8K1JeZ/>. "IETF 110 Meeting Survey", n.d., <https://ql.tc/8K1JeZ/>.
[IETF-BLOG] [IETF-BLOG]
"IETF blog", n.d., <https://www.ietf.org/blog/>. "IETF Blog", n.d., <https://www.ietf.org/blog/>.
[IETF-HACKATHON-GITHUB] [IETF-HACKATHON-GITHUB]
"IETF-Hackathon GitHub", n.d., "IETF-Hackathon GitHub", n.d.,
<https://github.com/ietf-hackathon/>. <https://github.com/ietf-hackathon/>.
[IETF-RUNNING-CODE-SPONSOR] [IETF-RUNNING-CODE-SPONSOR]
"IETF Running Code Sponsor", n.d., "IETF Running Code Sponsor", n.d.,
<https://www.ietf.org/about/support/#running-code/>. <https://www.ietf.org/about/support/#running-code/>.
[LOST-AND-FOUND]
"IETF 110 Hackathon Lost and Found", n.d.,
<https://trac.ietf.org/trac/ietf/meeting/
wiki/110hackathon/lost&found>.
[MEETECHO] "Meetecho", n.d., <https://www.meetecho.com/>. [MEETECHO] "Meetecho", n.d., <https://www.meetecho.com/>.
[MEETING-WEBSITE] [MEETING-WEBSITE]
"meeting website", n.d., "IETF Meeting Website", n.d.,
<https://www.ietf.org/how/meetings/>. <https://www.ietf.org/how/meetings/>.
[MEETING-WIKI] [MEETING-WIKI]
"meeting wiki", n.d., "IETF Meeting Wiki", n.d.,
<https://trac.ietf.org/trac/ietf/meeting/wiki>. <https://trac.ietf.org/trac/ietf/meeting/wiki>.
[NOTE-WELL] [NOTE-WELL]
"Note Well", n.d., <https://ietf.org/about/note-well/>. "IETF Note Well", n.d.,
<https://ietf.org/about/note-well/>.
[NSRC-CALENDAR]
"Network Startup Resource Center Calendar", n.d.,
<https://nsrc.org/calendar/>.
[PARTICIPANTS]
"IETF 110 Hackathon Participant List", n.d.,
<https://registration.ietf.org/110/participants/
hackathon/>.
[REGISTRATION-SYSTEM] [REGISTRATION-SYSTEM]
"registration system", n.d., "IETF Meeting Registration System", n.d.,
<https://registration.ietf.org/>. <https://registration.ietf.org/>.
[REMARK] "remark GitHub repository", n.d., [REMARK] "remark GitHub Repository", n.d.,
<https://github.com/gnab/remark/>. <https://github.com/gnab/remark/>.
[REQUEST-SESSIONS] [REQUEST-SESSIONS]
"request sessions", n.d., "IETF Session Request", n.d.,
<https://datatracker.ietf.org/secr/sreq/>. <https://datatracker.ietf.org/secr/sreq/>.
[RESULTS-PRESENTATION-SCHEDULE]
"IETF 110 Hackathon Results Presentation Schedule", n.d.,
<https://trac.ietf.org/trac/ietf/meeting/
wiki/110hackathon/resultspresentationschedule>.
[RESULTS-PRESENTATIONS]
"IETF 110 Hackathon Project Results Presentations", n.d.,
<https://github.com/ietf-hackathon/ietf110-project-
presentations>.
[RIPE-CALENDAR]
"RIPE Upcoming Events", n.d.,
<https://www.ripe.net/participate/meetings/calendar/>.
[SURVEY] "IETF 107 Hackathon Participant Survey", n.d., [SURVEY] "IETF 107 Hackathon Participant Survey", n.d.,
<https://www.surveymonkey.com/results/SM-9HLRXN8M7/>. <https://www.surveymonkey.com/results/SM-9HLRXN8M7/>.
[TEAM-SCHEDULE]
"IETF 110 Hackathon Team Schedule", n.d.,
<https://trac.ietf.org/trac/ietf/meeting/
wiki/110hackathon/teamschedule>.
[TICKET] "IETF Support Email Alias", n.d.,
<mailto://tickets@meeting.ietf.org>.
[WEBEX-ACCOUNT] [WEBEX-ACCOUNT]
"Webex account", n.d., "IETF Webex Account", n.d.,
<https://ietf.webex.com/webappng/sites/ietf/ <https://ietf.webex.com/webappng/sites/ietf/
dashboard?siteurl=ietf/>. dashboard?siteurl=ietf/>.
Acknowledgments Acknowledgments
The IETF Secretariat, notably Alexa Morris and Stephanie McCammon, The IETF Secretariat, notably Alexa Morris and Stephanie McCammon,
contributed significantly to the creation of the IETF Hackathon and contributed significantly to the creation of the IETF Hackathon and
the practices in this document. Among other things, Alexa drafted the practices in this document. Among other things, Alexa drafted
the initial breakdown of Roles and Responsibilities (Section 7), and the initial breakdown of Roles and Responsibilities (Section 7), and
Stephanie McCammon created the initial Hackathon website and wiki. Stephanie McCammon created the initial Hackathon website and wiki.
 End of changes. 50 change blocks. 
135 lines changed or deleted 158 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/