HACKATHON

Summary

The session served as the kickoff for the weekend IETF Hackathon. Co-chair Benno welcomed participants, including a notable number of first-time IETF attendees. The hackathon's primary goals were highlighted, emphasizing the IETF mantra of "rough consensus and running code." The session covered administrative rules regarding intellectual property, logistical information for both in-person and remote participants, and the schedule for the weekend, including instructions for the Sunday project presentations and the Monday Demo Happy Hour.

Key Discussion Points

Hackathon Goals and IETF Integration:
- Benno emphasized that standards are only relevant if deployed, requiring active implementations. The weekend focuses on open-source collaboration, interoperability testing, and advancing IETF drafts.
- The hackathon serves as a key mechanism for attracting developers, young professionals, and university students into the IETF community.
Administrative and IPR Rules:
- The IETF Note Well applies to the hackathon.
- A critical distinction was made regarding intellectual property: all discussions and presentations are considered IETF Contributions, but the code written during the event remains the property of the developers and is not an IETF contribution.
Logistics and Infrastructure:
- Team Formation: Participants were directed to the Hackathon Wiki and the "Lost and Found" board to match skills with existing projects. Co-chairs Benno and Barry are available to assist with project placement.
- Remote Participation: Remote team members can collaborate using GatherTown.
- Networking: Special networking requests are managed via Hacknet.
- GitHub: An IETF Hackathon Git repository is available for presentation templates (HTML/PowerPoint) and teams can create their own repositories within the IETF Hackathon GitHub organization for visibility.
- Code Lounge: Available on the 4th level for ongoing collaboration throughout the week.
Sunday Presentations:
- Presentations will take place on Sunday from 14:00 to 16:00.
- Time slots are strictly limited to 3 minutes per team (approximately 3-4 slides).
- Content should avoid deep technical details and instead focus on the problem being solved, achievements, lessons learned, and direct feedback to the relevant working groups.
- Slides must be uploaded as PDFs via the Datatracker (under the Sunday 14:00 Hackathon agenda slot). File names should remain consistent when uploading revisions to avoid duplicate entries.
GitHub Documentation Project:
- A brief announcement was made regarding an active project (facilitated by Greg and Durov at Table 20) focused on gathering community feedback to improve IETF documentation for authoring and reviewing drafts on GitHub.

Decisions and Action Items

Action Item: Participants working on projects who wish to present must finalize their coding and begin preparing their slides by Sunday at 13:30.
Action Item: Teams must upload their presentation slides (strictly in PDF format) to the IETF Datatracker before 14:00 on Sunday.
Action Item: Teams wishing to participate in the Monday Demo Happy Hour must register by 13:00 on Monday to ensure sufficient tables are organized.
Action Item: Participants utilizing GitHub for draft authoring or review are encouraged to visit Table 20 to provide feedback to the GitHub documentation project.

Next Steps

Saturday Schedule: Lunch at 12:30, Dinner at 18:30, and the room will be cleared prior to 21:00.
Sunday Schedule: Hackathon resumes at 09:30. Lunch at 12:30. Coding stops at 13:30 for presentation prep. Project presentations run from 14:00 to 16:00.
Monday Demo Happy Hour: Scheduled for 18:00 to 19:00 on the second-level foyer. Open to the entire IETF community to view hackathon results. Sponsored drinks and snacks will be provided.