draft-ietf-shmoo-hackathon-01.txt   draft-ietf-shmoo-hackathon-02.txt 
shmoo C. Eckel shmoo C. Eckel
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Informational 9 July 2021 Intended status: Informational 10 November 2021
Expires: 10 January 2022 Expires: 14 May 2022
Running an IETF Hackathon Running an IETF Hackathon
draft-ietf-shmoo-hackathon-01 draft-ietf-shmoo-hackathon-02
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 10 January 2022. This Internet-Draft will expire on 14 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
skipping to change at page 2, line 27 skipping to change at page 2, line 27
provided without warranty as described in the Simplified BSD License. provided without warranty as described in the Simplified 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 . . . . . . . . . . . . . . . . . . . . . . . 7 2.5. Online Only . . . . . . . . . . . . . . . . . . . . . . . 8
3. Funding . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 3. Funding . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1. Sponsorship . . . . . . . . . . . . . . . . . . . . . . . 8 3.1. Sponsorship . . . . . . . . . . . . . . . . . . . . . . . 9
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 . . . . . . . . . . . . . . . . . . . . 11 4. Project Presentations . . . . . . . . . . . . . . . . . . . . 12
4.1. Project Pitches . . . . . . . . . . . . . . . . . . . . . 12 4.1. Project Pitches . . . . . . . . . . . . . . . . . . . . . 12
4.2. Results Summaries . . . . . . . . . . . . . . . . . . . . 12 4.2. Results Summaries . . . . . . . . . . . . . . . . . . . . 12
4.2.1. Templates . . . . . . . . . . . . . . . . . . . . . . 12 4.2.1. Templates . . . . . . . . . . . . . . . . . . . . . . 13
4.3. Upload to GitHub . . . . . . . . . . . . . . . . . . . . 13 4.3. Upload to GitHub . . . . . . . . . . . . . . . . . . . . 13
4.4. Presenting in Person . . . . . . . . . . . . . . . . . . 13 4.4. Presenting in Person . . . . . . . . . . . . . . . . . . 14
4.5. Presenting Remotely . . . . . . . . . . . . . . . . . . . 13 4.5. Presenting Remotely . . . . . . . . . . . . . . . . . . . 14
5. Tooling . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 5. Tooling . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.1. Datatracker . . . . . . . . . . . . . . . . . . . . . . . 14 5.1. Datatracker . . . . . . . . . . . . . . . . . . . . . . . 14
5.2. IETF Website . . . . . . . . . . . . . . . . . . . . . . 14 5.2. IETF Website . . . . . . . . . . . . . . . . . . . . . . 14
5.2.1. Hackathon Webpage . . . . . . . . . . . . . . . . . . 14 5.2.1. Hackathon Website . . . . . . . . . . . . . . . . . . 14
5.2.2. Meeting Webpage . . . . . . . . . . . . . . . . . . . 14 5.2.2. Meeting Website . . . . . . . . . . . . . . . . . . . 15
5.3. Registration . . . . . . . . . . . . . . . . . . . . . . 14 5.3. Registration . . . . . . . . . . . . . . . . . . . . . . 15
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 . . . . . . . . . . . . . . . . . . . . . . 15 5.4.1. Hackathon . . . . . . . . . . . . . . . . . . . . . . 16
5.4.2. Lost and Found . . . . . . . . . . . . . . . . . . . 16 5.4.2. Lost and Found . . . . . . . . . . . . . . . . . . . 16
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 . . . . . . . . . . . . . . . . . . . . . 17
5.5. Mailing List . . . . . . . . . . . . . . . . . . . . . . 17 5.5. Email List . . . . . . . . . . . . . . . . . . . . . . . 17
5.5.1. Hackathon Chairs Email Alias . . . . . . . . . . . . 17 5.5.1. Hackathon Chairs Email Alias . . . . . . . . . . . . 18
5.6. GitHub . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.6. GitHub . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.7. Meetecho . . . . . . . . . . . . . . . . . . . . . . . . 18 5.7. Meetecho . . . . . . . . . . . . . . . . . . . . . . . . 18
5.8. Network . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.8. Network . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.8.1. Remote Networking . . . . . . . . . . . . . . . . . . 19 5.8.1. Remote Networking . . . . . . . . . . . . . . . . . . 19
5.9. Webex . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.9. Webex . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.10. Gather . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.10. Gather . . . . . . . . . . . . . . . . . . . . . . . . . 20
6. Statistics and Metrics . . . . . . . . . . . . . . . . . . . 20 6. Statistics and Metrics . . . . . . . . . . . . . . . . . . . 20
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. Implementation Status . . . . . . . . . . . . . . . . . . . . 24 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 24
9. Security Considerations . . . . . . . . . . . . . . . . . . . 24 9. Security Considerations . . . . . . . . . . . . . . . . . . . 24
9.1. Privacy Considerations . . . . . . . . . . . . . . . . . 24 9.1. Privacy Considerations . . . . . . . . . . . . . . . . . 24
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 25 11. Informative References . . . . . . . . . . . . . . . . . . . 25
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 25 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 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
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 6, line 26 skipping to change at page 6, line 26
encouraged. encouraged.
The end of the Hackathon on Sunday is driven by other IETF meeting The end of the Hackathon on Sunday is driven by other IETF meeting
events. There typically are Newcomer events that start at 16:00. events. There typically are Newcomer events that start at 16:00.
The IETF Hackathon typically includes many newcomers in its list of The IETF Hackathon typically includes many newcomers in its list of
participants. It is important to provide them time to participate in participants. It is important to provide them time to participate in
the Newcomer events. The opening reception typically start at 17:00, the Newcomer events. The opening reception typically start at 17:00,
and we want to make it easy for all Hackathon participants to join and we want to make it easy for all Hackathon participants to join
that as well. that as well.
Hackdemo Happy Hour (ref) and the Code Lounge (ref) exist to Hackdemo Happy Hour (Section 2.2) and the Code Lounge (Section 2.3)
facilitate ongoing discussion and work on projects beyond the exist to facilitate ongoing discussion and work on projects beyond
official end of the Hackathon weekend. the official end of the Hackathon weekend.
2.2. Hackdemo Happy Hour 2.2. Hackdemo Happy Hour
Hackdemo Happy Hour provides an opportunity for more in depth sharing Hackdemo Happy Hour provides an opportunity for more in depth sharing
and discussion than is possible within the time constraints of the and discussion than is possible within the time constraints of the
result presentation that occur at the end of the Hackathon. This result presentation that occur at the end of the Hackathon. This
opportunity is made available to all teams. As with the results opportunity is made available to all teams. As with the results
presentation, participation is optional. presentation, participation is optional.
Initially, we did something similar as part of Bits and Bites. This Initially, we did something similar as part of Bits and Bites. This
skipping to change at page 7, line 43 skipping to change at page 8, line 11
benefits of a customized event. The practice that exists today is to benefits of a customized event. The practice that exists today is to
locate the events physically close to each other to facilitate locate the events physically close to each other to facilitate
switching back and forth between the two events. switching back and forth between the two events.
2.5. Online Only 2.5. Online Only
The IETF 107 Hackathon was originally scheduled to be the weekend at The IETF 107 Hackathon was originally scheduled to be the weekend at
the start of the IETF meeting in Vancouver. When COVID-19 hit and it the start of the IETF meeting in Vancouver. When COVID-19 hit and it
became clear the IETF meeting could not occur in person, the became clear the IETF meeting could not occur in person, the
Hackathon already had 23 projects and 176 registrations. With only Hackathon already had 23 projects and 176 registrations. With only
10 days until the anticipated start of the Hackathon, a survey 10 days until the anticipated start of the Hackathon, a [SURVEY] went
(https://www.surveymonkey.com/results/SM-9HLRXN8M7/) went out to the out to the Hackathon community, including all project champions and
Hackathon community, including all project champions and registered registered participants, to see if they wanted to participate in the
participants, to see if they wanted to participate in the Hackathon Hackathon exactly as planned except with everyone participating
exactly as planned except with everyone participating remotely rather remotely rather than in person. A relatively small number of people
than in person. A relatively small number of people expressed expressed interest in participating, with even fewer wanting to
interest in participating, with even fewer wanting to continue to continue to champion their projects. The fact that the Hackathon was
champion their projects. The fact that the Hackathon was planned for planned for the weekend before the IETF meeting and in the local time
the weekend before the IETF meeting and in the local time zone, both zone, both of which were historically very convenient and attractive
of which were historically very convenient and attractive to to Hackathon participants, suddenly became huge obstacles.
Hackathon participants, suddenly became huge obstacles.
Consequently, the IETF 107 Hackathon was cancelled. Consequently, the IETF 107 Hackathon was cancelled.
We knew more in advance that IETF 108 would be an online only We knew more in advance that IETF 108 would be an online only
meeting. We moved and expanded the schedule to run the entire work meeting. We moved and expanded the schedule to run the entire work
week before the rest of the IETF meeting. The Hackathon kickoff was week before the rest of the IETF meeting. The Hackathon kickoff was
set for Monday, the closing for Friday, with all the time in between set for Monday, the closing for Friday, with all the time in between
left for individual project teams to arrange to meet how and when was left for individual project teams to arrange to meet how and when was
most convenient for them. The kickoff and closing sessions were most convenient for them. The kickoff and closing sessions were
schedule to align with the time frame established for the IETF 108 schedule to align with the time frame established for the IETF 108
meeting. All of this was, of course, not ideal, and it worked much meeting. All of this was, of course, not ideal, and it worked much
better for some people than for others, but at least everyone knew better for some people than for others, but at least everyone knew
the plan and corresponding time commitment well in advance and had the plan and corresponding time commitment well in advance and had
the ability to plan accordingly. the ability to plan accordingly.
We ultimately had 19 projects and almost 300 registrations. It is We ultimately had 19 projects and almost 300 registrations. It is
hard to say how many people actually participated and for how long, hard to say how many people actually participated and for how long,
but many projects were able to get substantial work done. For the but many projects were able to get substantial work done. For the
closing, 10 teams produced and shared presentations summarizing their closing, 10 teams produced and shared presentations summarizing their
findings and achievements. All presentations as well as the agenda findings and achievements. All presentations as well as the agenda
and a recording of the closing session are available via the IETF 108 and a recording of the closing session are available via the
Hackathon wiki (https://trac.ietf.org/trac/ietf/meeting/ [IETF-108-HACKATHON-WIKI]. This level of participation was strong
wiki/108hackathon). This level of participation was strong enough to enough to be considered a success and justify including the Hackathon
be considered a success and justify including the Hackathon in future in future online only IETF meetings.
online only IETF meetings.
Hackdemo Happy Hour and the Code Lounge are not applicable for online Hackdemo Happy Hour and the Code Lounge are not applicable for online
only Hackathons. only Hackathons.
3. Funding 3. Funding
The Hackathon requires funding, and that funding increases with the The Hackathon requires funding, and that funding increases with the
number of participants. Participating has always been free; number of participants. Participating has always been free;
therefore, funding from other sources than participant fees is therefore, funding from other sources than participant fees is
required. required.
skipping to change at page 9, line 11 skipping to change at page 9, line 31
Hackathon had become a proven success. Consequently, the IETF Hackathon had become a proven success. Consequently, the IETF
decided to fund the Hackathon as part of the IETF meeting, with decided to fund the Hackathon as part of the IETF meeting, with
Hackathon sponsorship being on a best effort basis. Hackathon sponsorship being on a best effort basis.
Online only Hackathons in response to the COVID-19 pandemic, and Online only Hackathons in response to the COVID-19 pandemic, and
increased remote participating in general, result in increased cloud increased remote participating in general, result in increased cloud
infrastructure requirements that make Hackathon sponsorship more infrastructure requirements that make Hackathon sponsorship more
attractive to cloud infrastructure providers. attractive to cloud infrastructure providers.
Hackathon sponsorship is available at different levels as part of Hackathon sponsorship is available at different levels as part of
being an IETF Running Code Sponsor (https://www.ietf.org/about/ being an [IETF-RUNNING-CODE-SPONSOR].
support/#running-code).
3.2. Expenses 3.2. Expenses
The primary expenses associated with the Hackathon are those for The primary expenses associated with the Hackathon are those for
hosting an in-person event, e.g., meeting space, food and beverage, hosting an in-person event, e.g., meeting space, food and beverage,
etc. It is often challenging to quantify the portion of this etc. It is often challenging to quantify the portion of this
associated with the Hackathon from that incurred for the IETF meeting associated with the Hackathon from that incurred for the IETF meeting
overall. overall.
3.2.1. In-person Event Expenses 3.2.1. In-person Event Expenses
skipping to change at page 13, line 13 skipping to change at page 13, line 30
(https://github.com/ietf-hackathon/ietf110-project-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 (https://github.com/gnab/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., https://github.com/ietf-hackathon/ietf110-project-
presentations (https://github.com/ietf-hackathon/ietf110-project- presentations (https://github.com/ietf-hackathon/ietf110-project-
presentations). The contents of this repo are used as the source for presentations). The contents of this repo are used as the source for
all project presentations at the end of the Hackathon and remain as a all project presentations at the end of the Hackathon and remain as a
reference after the Hackathon. reference after the Hackathon.
One must be a member of the IETF-Hackathon GitHub org to upload a new One must be a member of the [IETF-HACKATHON-GITHUB] organization to
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)
* send your GitHub user name to the Chair(s) * send your GitHub user name to the Chair(s)
Presenters are asked to do this at their earliest convenience as the Presenters are asked to do this at their earliest convenience as the
Chair(s) typically get very busy as the start of presentations Chair(s) typically get very busy as the start of presentations
approaches. approaches.
4.4. Presenting in Person 4.4. Presenting in Person
Presentations are run from a shared ChromeBook at the front of the Presentations are run from a shared ChromeBook at the front of the
Hackathon room. This Chromebook is provided by the Secretariat. Hackathon room. This Chromebook is provided by the Secretariat.
4.5. Presenting Remotely 4.5. Presenting Remotely
skipping to change at page 14, line 12 skipping to change at page 14, line 27
Hackathon Chairs can share the presentation and advance slides for Hackathon Chairs can share the presentation and advance slides for
the presenter. the presenter.
5. Tooling 5. Tooling
The IETF Hackathon uses the same tooling used by the IETF community The IETF Hackathon uses the same tooling used by the IETF community
for its work and meetings. for its work and meetings.
5.1. Datatracker 5.1. Datatracker
The datatracker (https://datatracker.ietf.org/) supports the notion The [DATATRACKER] supports the notion of Teams that are not a part of
of Teams that are not a part of the standards development process. the standards development process. The Hackathon exists as one such
The Hackathon exists as one such Team. From the datatracker menu, Team. From the datatracker menu, navigate to "Other" -> "Active
navigate to "Other" -> "Active Teams" -> "Hackathon". Here exists a Teams" -> "Hackathon". Here exists a datatracker space for the
datatracker space for the Hackathon similar to what is available for Hackathon similar to what is available for working groups, including
working groups, including meeting materials, agendas, etc. meeting materials, agendas, etc. Initially, there was some attempt
Initially, there was some attempt to copy materials hosted in GitHub to copy materials hosted in the [IETF-HACKATHON-GITHUB] to the
(https://github.com/ietf-hackathon) to the datatracker. Now this is Datatracker. Now this is done only when required for integration
done only when required for integration with other IETF tooling, with other IETF tooling, including to:
including:
* requesting sessions (https://datatracker.ietf.org/secr/sreq/) for * [REQUEST-SESSIONS] for the Hackathon kickoff and closing, and for
the Hackathon kickoff and closing, and for Hackdemo Happy Hour Hackdemo Happy Hour
* posting agendas (https://datatracker.ietf.org/meeting/agenda/) * post [AGENDAS]
5.2. IETF Website 5.2. IETF Website
5.2.1. Hackathon Webpage 5.2.1. Hackathon Website
The IETF website includes a dedicated page for the Hackathon webpage The IETF website includes a [HACKATHON-WEBSITE]. This website
(https://www.ietf.org/how/runningcode/hackathons/). This page
contains information about the Hackathon in general as well as links contains information about the Hackathon in general as well as links
to past, present, and future Hackathons. The relevant links are to past, present, and future Hackathons. The relevant links are
updated after each IETF meeting. Other content on the page is updated after each IETF meeting. Other content on the website is
updated on a more ad hoc basis. updated on a more ad hoc basis.
5.2.2. Meeting Webpage 5.2.2. Meeting Website
Each IETF meeting webpage (https://www.ietf.org/how/meetings/) Each [MEETING-WEBSITE] contains information about the corresponding
contains information about the corresponding Hackathon, including the Hackathon, including the dates of the Hackathon in the header and a
dates of the Hackathon in the header, a link to the Hackathon webpage link to the Hackathon website in the "Additional Events" section.
in the "Additional Events" section.
5.3. Registration 5.3. Registration
Registration for the Hackathon is through the IETF meeting Registration for the Hackathon is through the IETF meeting
registration (https://registration.ietf.org) system. Participant [REGISTRATION-SYSTEM]. Participant registration for the Hackathon
registration for the Hackathon is is:
* independent of participation registration for the meeting * independent of participation registration for the meeting
* free * free
* required * required
As with meeting registration, registrants for the Hackathon As with meeting registration, registrants for the Hackathon
acknowledge the Note Well (https://ietf.org/about/note-well/) during acknowledge the [NOTE-WELL] during the registration process.
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.,
https://registration.ietf.org/110/participants/hackathon/ https://registration.ietf.org/110/participants/hackathon/
(https://registration.ietf.org/110/participants/hackathon/), is (https://registration.ietf.org/110/participants/hackathon/), is
maintained by the Secretariat. Important information displayed for maintained by the Secretariat. Important information displayed for
each registrant includes the set of projects and technologies in 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
skipping to change at page 15, line 34 skipping to change at page 15, line 48
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 each The [MEETING-WIKI] serves as the primary source of information for
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.,
https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon
(https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon), is (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 requesting credentials. Credentials can be obtained by creating a
(https://datatracker.ietf.org/accounts/create/) a new datatracker [DATATRACKER-ACCOUNT].
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.,
https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/lost&found https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/lost&found
(https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/ (https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/
lost&found), is created by the Chairs for each Hackathon. lost&found), is created by the Chairs for each Hackathon.
Participants looking for a team are encouraged to add themselves to Participants looking for a team are encouraged to add themselves to
the "Skills to Offer" table, providing some information about their the "Skills to Offer" table, providing some information about their
skills and interests. This will help others with matching needs and/ skills and interests. This will help others with matching needs and/
skipping to change at page 17, line 33 skipping to change at page 17, line 43
teamschedule teamschedule
(https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/ (https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon/
teamschedule), is created by the Chairs for each online only teamschedule), is created by the Chairs for each online only
Hackathon. Online only Hackathons take place globally for an entire Hackathon. Online only Hackathons take place globally for an entire
week. It is up to individual project teams to determine the week. It is up to individual project teams to determine the
preferred dates, times, and ways to meet to work on their project preferred dates, times, and ways to meet to work on their project
within the context of that week (e.g., Zoom, Webex, Slack). This within the context of that week (e.g., Zoom, Webex, Slack). This
page is meant to help facilitate coordination of schedules within and page is meant to help facilitate coordination of schedules within and
across teams. across teams.
5.5. Mailing List 5.5. Email List
The Hackathon mail list, hacakthon@ietf.org The Hackathon email list, [EMAIL-LIST], is used for all email
(https://www.ietf.org/mailman/listinfo/Hackathon), is used for all communication and announcement related to the Hackathon. All
email 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
The email alias hackathon-chairs@ietf.org (mailto:hackathon- The email alias, [EMAIL-ALIAS], was created and is maintained by the
chairs@ietf.org) was created and is maintained by the Secretariat. Secretariat. It is used on Hackathon webpages and wiki pages to
It is used on hackathons webpages and wiki pages to provide a single provide a single point of contact for the Hackathon.
point of contact for the Hackathon.
5.6. GitHub 5.6. GitHub
The IETF-Hackathon (https://github.com/ietf-hackathon) is used to The [IETF-HACKATHON-GITHUB] is used to share code, presentations, and
share code, presentations, and other artifacts at IETF Hackathons. other artifacts at IETF Hackathons. The Hackathon Chairs are
The Hackathon Chairs are responsible for administering the GitHub responsible for administering the GitHub organization.
org.
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., https://github.com/ietf-hackathon/ietf110-project-
presentations (https://github.com/ietf-hackathon/ietf110-project- presentations (https://github.com/ietf-hackathon/ietf110-project-
presentations). This repo is for participants to upload project presentations). This repo is for participants to upload project
presentations. The contents of this repo are used as the source for presentations. The contents of this repo are used as the source for
all project presentations at the end of the Hackathon and remain as a all project presentations at the end of the Hackathon and remain as a
reference after the Hackathon. reference after the Hackathon.
5.7. Meetecho 5.7. Meetecho
Meetecho (https://www.meetecho.com/) is used for the kickoff and [MEETECHO] is used for the kickoff and closing sessions of the
closing sessions of the Hackathon. This provides many capabilities, Hackathon. This provides many capabilities, including the following:
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
sessions sessions
* enable remote presentations of project results * enable remote presentations of project results
* capture recording of Hackathon sessions * capture recording of Hackathon sessions
skipping to change at page 19, line 17 skipping to change at page 19, line 28
Champions are able to request in advance wired access and special Champions are able to request in advance wired access and special
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 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 (https://hacknet.meeting.ietf.org/), a global Layer 2 VPN [HACKNET], a global Layer 2 VPN designed to support IETF protocol
designed to support IETF protocol development across teams within the development across teams within the IETF Hackathon. A limited set of
IETF Hackathon. A limited set of devices for connecting to HackNet devices for connecting to HackNet are supported. In addition to
are supported. In addition to layer 2 connectivity, a subset of the layer 2 connectivity, a subset of the networking capabilities
networking capabilities available at in-person meetings are available at in-person meetings are available. Both the set of
available. Both the set of devices and the set of networking devices and the set of networking capabilities are expected to expand
capabilities are expected to expand and evolve over time. HackNet is and evolve over time. However, it is important to note that HackNet
generally available between IETF meetings. Support is available via is still an experiment and not a production service. Best effort
email to ticket@meeting.ietf.org (mailto:ticket@meeting.ietf.org). support is available via 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] they can use to schedule
(https://ietf.webex.com/webappng/sites/ietf/dashboard?siteurl=ietf) meetings for their team. These are similar to the Webex accounts
they can use to schedule meetings for their team. These are similar allocated to working group chairs to be used for virtual interim
to the Webex accounts allocated to working group chairs to be used meetings. An account can be requested by a team champion at any
for virtual interim meetings. An account can be requested by a team time. Accounts remain active and available throughout the duration
champion at any time. Accounts remain active and available of the Hackathon and the associated IETF meeting. A project name may
throughout the duration of the Hackathon and the associated IETF be used in place of "Working Group Name" in the request form.
meeting. A project name may be used in place of "Working Group Name"
in the request form.
5.10. Gather 5.10. Gather
Gather (https://gather.town/) facilitates virtual hallway interaction [GATHER] facilitates virtual hallway interaction during IETF
during IETF meetings. A dedicated area within the overall space is meetings. A dedicated area within the overall space is created by
created by the Secretariat for the Hackathon. The area includes the Secretariat for the Hackathon. The area includes tables,
tables, identified by letters of the alphabet, that teams are free to identified by letters of the alphabet, that teams are free to self
self assign and use as and when they like. Eight to ten seats around assign and use as and when they like. Eight to ten seats around each
each table facilitate group discussions within the team. A table facilitate group discussions within the team. A whiteboard or
whiteboard or shared notes tablet (via CodiMD) at tables facilitates shared notes tablet, e.g., [HEDGEDOC], at tables facilitates sharing
sharing of information within the team. The tables also facilitate of information within the team. The tables also facilitate
collaboration across teams. One cautionary note, Gather has relative collaboration across teams. One cautionary note, Gather has relative
high network bandwidth and CPU requirements, and as such may not be high network bandwidth and CPU requirements, and as such may not be
well suited for some Hackathon participants. well suited for some Hackathon participants.
The Gather space remains available between IETF meetings, with The Gather space remains available between IETF meetings, with
incremental improvements and additions made during this time. The incremental improvements and additions made during this time. The
space is cleaned about a month prior to the start of the next space is cleaned about a month prior to the start of the next
meeting, removing anything left over from the previous meeting. meeting, removing anything left over from the previous meeting.
Hackathon teams are encouraged to make a copy of anything they want Hackathon teams are encouraged to make a copy of anything they want
to retain within a week of the end of the IETF meeting. to retain within a week of the end of the IETF meeting.
skipping to change at page 20, line 49 skipping to change at page 20, line 49
Hackathon participation has grown from 45 at IETF 92 to a maximum of Hackathon participation has grown from 45 at IETF 92 to a maximum of
406 at IETF 104. Participation is tends to be slightly higher when 406 at IETF 104. Participation is tends to be slightly higher when
the IETF meeting is located in Europe. Recent in-person Hackathons the IETF meeting is located in Europe. Recent in-person Hackathons
have had roughly 30-40% as many participants as the corresponding have had roughly 30-40% as many participants as the corresponding
IETF meeting. For roughly 20-30% of Hackathon participants, the IETF meeting. For roughly 20-30% of Hackathon participants, the
Hackathon is their first experience at any IETF event. Hackathon is their first experience at any IETF event.
6.1. IETF Survey Results 6.1. IETF Survey Results
For each IETF meeting, there is a post event survey that often For each IETF meeting, there is a post event survey that often
includes a question or two about the Hackathon, e.g., IETF 106 Survey includes a question or two about the Hackathon, e.g.,
Results (https://www.ietf.org/media/documents/ [IETF-106-SURVEY]
IETF_106_Meeting_Survey.pdf).
6.2. Hackathon Survey Results 6.2. Hackathon Survey Results
Hackathon specific surveys have been used on some occasions to obtain Hackathon specific surveys have been used on some occasions to obtain
more detailed feedback about the Hackathon from the IETF community. more detailed feedback about the Hackathon from the IETF community.
This has been especially useful for feedback on online only This has been especially useful for feedback on online only
Hackathons. Survey have been short with most questions being Hackathons. Survey have been short with most questions being
optional, e.g., IETF 110 Hackathon Survey Results optional, e.g., [IETF-110-SURVEY].
(https://ql.tc/8K1JeZ).
7. Roles and Responsibilities 7. Roles and Responsibilities
This section provides a summary of the roles and responsibilities of This section provides a summary of the roles and responsibilities of
individuals and groups involved in a successful IETF Hackathon. The individuals and groups involved in a successful IETF Hackathon. The
summary provided here is not meant to be exhaustive. Some summary provided here is not meant to be exhaustive. Some
responsibilities are described entirely or in more detail throughout responsibilities are described entirely or in more detail throughout
the rest of the document. the rest of the document.
7.1. Hackathon Chair(s) 7.1. Hackathon Chair(s)
skipping to change at page 21, line 41 skipping to change at page 21, line 40
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.,
https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon
(https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon), and (https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon), and
all of its child pages. all of its child pages.
* Moderate hackathon@ietf.org (mailto:hackathon@ietf.org) email list * Moderate Hackathon email list (Section 5.5)
* Request sessions (https://datatracker.ietf.org/secr/sreq/) for the * [REQUEST-SESSIONS] for the Hackathon opening and closing in 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 repo used for each Hackathon, e.g., * Create and manage the GitHub repository used for each Hackathon,
https://github.com/ietf-hackathon/ietf110-project-presentations e.g., https://github.com/ietf-hackathon/ietf110-project-
(https://github.com/ietf-hackathon/ietf110-project-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 * Configure and manage Hackathon registration system (Section 5.3)
* Maintain Hackathon web page (https://www.ietf.org/how/runningcode/ * Maintain Hackathon website (Section 5.2.1)
hackathons/)
* 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/ https://www.ietf.org/how/runningcode/hackathons/110-hackathon/
(https://www.ietf.org/how/runningcode/hackathons/110-hackathon/) (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 https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon
(https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon). This (https://trac.ietf.org/trac/ietf/meeting/wiki/110hackathon). This
is initialized and updated at times by the Secretariat, but the is initialized and updated at times by the Secretariat, but the
Chair(s) are ultimately 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,
including issuing badges and participant t-shirts when available including issuing badges and Hackathon t-shirts (Section 3.2.1.3)
when available
7.3. Sponsor 7.3. Sponsor
Key responsibilities include: Key responsibilities include:
* Provide some funding to help offset costs of Hackathon (either per * Provide some funding to help offset costs of Hackathon (either per
meeting or per year, depending on model) meeting or per year, depending on model)
* Optionally provide t-shirts or other giveaways * Optionally provide t-shirts or other giveaways
skipping to change at page 23, line 13 skipping to change at page 23, line 13
* Sponsor logo on Hackathon t-shirts * Sponsor logo on Hackathon t-shirts
* Sponsor logo on Hackathon signage * Sponsor logo on Hackathon signage
* Sponsor logo on Hackathon webpage and wiki * Sponsor logo on Hackathon webpage and wiki
* Sponsor logo and call out in Hackathon kickoff and closing * Sponsor logo and call out in Hackathon kickoff and closing
presentation presentation
* Sponsor logo and call out in IETF Plenary presentation * Sponsor logo and call out in IETF Plenary presentation
* Sponsor logo and call out in Hackathon recap on IETF blog * Sponsor logo and call out in Hackathon recap on [IETF-BLOG]
(https://www.ietf.org/blog/)
* Recognition in IETF community for helping the IETF Hackathon * Recognition in IETF community for helping the IETF Hackathon
remain free and open to everyone remain free and open to everyone
7.4. Champions of Projects 7.4. Champions of Projects
Champions of projects are the key to a successful Hackathon. Key Champions of projects are the key to a successful Hackathon. Key
responsibilities for champions include: responsibilities for champions include:
* Volunteer to lead a project at the Hackathon * Volunteer to lead a project at the Hackathon
skipping to change at page 24, line 30 skipping to change at page 24, line 28
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. Implementation Status 8. Implementation Status
The practices described in this document have been established, used, The practices described in this document have been established, used,
and refined over the course of running numerous IETF Hackathons, and refined over the course of running numerous IETF Hackathons,
including several at online only IETF meetings. The draft-ietf- including several at online only IETF meetings. The [GITHUB-REPO]
shmoo-hackathon (https://github.com/eckelcu/draft-ietf-shmoo- GitHub repository has been used to collaborate on this document. The
hackathon) GitHub repository has been used to collaborate on this IETF-Hackathon GitHub (Section 5.6) contains code associated with
document. The IETF-Hackathon (https://github.com/ietf-hackathon) IETF Hackathons.
GitHub organization contains code associated with IETF Hackathons.
9. Security Considerations 9. Security Considerations
None. HackNet (Section 5.8.1) enables Hackathon participants to join the
IETF network while attending a meeting remotely. The intent is for
those connecting remotely to have as open a network as possible, just
like those connecting to the IETF network at an in person meeting. A
user must have a datatracker account to access HackNet and is
expected to respect it just as they are expected to respect the IETF
network at an in person meeting. If HackNet is exploited, it is
addressed as an exploitation of the IETF network would be at an in
person meeting.
9.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.
10. IANA Considerations 10. IANA Considerations
This document has no IANA actions. This document has no IANA actions.
11. Informative References
[AGENDAS] "agendas", n.d.,
<https://datatracker.ietf.org/meeting/agenda/>.
[DATATRACKER]
"Datatracker", n.d., <https://datatracker.ietf.org/>.
[DATATRACKER-ACCOUNT]
"Datatracker account", n.d.,
<https://datatracker.ietf.org/accounts/create/>.
[EMAIL-ALIAS]
"hackathon-chairs@ietf.org", n.d., <mailto:hackathon-
chairs@ietf.org>.
[EMAIL-LIST]
"hackathon@ietf.org", n.d.,
<https://www.ietf.org/mailman/listinfo/Hackathon/>.
[GATHER] "Gather", n.d., <https://gather.town/>.
[GITHUB-REPO]
"draft-ietf-shmoo-hackathon", n.d.,
<https://github.com/eckelcu/draft-ietf-shmoo-hackathon/>.
[HACKATHON-WEBSITE]
"Hackathon website", n.d.,
<https://www.ietf.org/how/runningcode/hackathons/>.
[HACKNET] "HackNet", n.d., <https://hacknet.meeting.ietf.org/>.
[HEDGEDOC] "HedgeDoc", n.d., <https://notes.ietf.org/>.
[IETF-106-SURVEY]
"IETF 106 Meeting Survey", n.d.,
<https://www.ietf.org/media/documents/
IETF_106_Meeting_Survey.pdf>.
[IETF-108-HACKATHON-WIKI]
"IETF 108 Hackathon Wiki", n.d.,
<https://trac.ietf.org/trac/ietf/meeting/
wiki/108hackathon/>.
[IETF-110-SURVEY]
"IETF 110 Meeting Survey", n.d., <https://ql.tc/8K1JeZ/>.
[IETF-BLOG]
"IETF blog", n.d., <https://www.ietf.org/blog/>.
[IETF-HACKATHON-GITHUB]
"IETF-Hackathon GitHub", n.d.,
<https://github.com/ietf-hackathon/>.
[IETF-RUNNING-CODE-SPONSOR]
"IETF Running Code Sponsor", n.d.,
<https://www.ietf.org/about/support/#running-code/>.
[MEETECHO] "Meetecho", n.d., <https://www.meetecho.com/>.
[MEETING-WEBSITE]
"meeting website", n.d.,
<https://www.ietf.org/how/meetings/>.
[MEETING-WIKI]
"meeting wiki", n.d.,
<https://trac.ietf.org/trac/ietf/meeting/wiki>.
[NOTE-WELL]
"Note Well", n.d., <https://ietf.org/about/note-well/>.
[REGISTRATION-SYSTEM]
"registration system", n.d.,
<https://registration.ietf.org/>.
[REMARK] "remark GitHub repository", n.d.,
<https://github.com/gnab/remark/>.
[REQUEST-SESSIONS]
"request sessions", n.d.,
<https://datatracker.ietf.org/secr/sreq/>.
[SURVEY] "IETF 107 Hackathon Participant Survey", n.d.,
<https://www.surveymonkey.com/results/SM-9HLRXN8M7/>.
[WEBEX-ACCOUNT]
"Webex account", n.d.,
<https://ietf.webex.com/webappng/sites/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 web page and wiki. These have Stephanie McCammon created the initial Hackathon website and wiki.
evolved over time and are used to run each Hackathon. These have evolved over time and are used to run each Hackathon.
Greg Wood, Barry Leiba, Michael Richardson, and Benson Muite also Greg Wood, Barry Leiba, Michael Richardson, Benson Muite, and Dhruv
provided significant contributions to the Hackathon and to this Dhody also provided significant contributions to the Hackathon and to
document. this document.
Author's Address Author's Address
Charles Eckel Charles Eckel
Cisco Systems Cisco Systems
United States of America United States of America
Email: eckelcu@cisco.com Email: eckelcu@cisco.com
 End of changes. 56 change blocks. 
148 lines changed or deleted 231 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/