Skip to content

Commit 3e28492

Browse files
committed
feat: add OpT-In VI in San Francisco (April 13-17, 2026)
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> Signed-off-by: Lars Trieloff <lars@trieloff.net>
1 parent b8e1aea commit 3e28492

File tree

2 files changed

+68
-0
lines changed

2 files changed

+68
-0
lines changed

hackathons/README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ Hackathons are back on! We have two tracks: one for Helix Operations and one for
55
## Upcoming Hackathons
66

77
1. [February 2nd to 6th 2026, somewhere in Palm Springs, CA](19-psp.md)
8+
2. [April 13th to 17th 2026, San Francisco, CA](opt-6-sfo.md)
89

910

1011
## Past Hackathons

hackathons/opt-6-sfo.md

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
# OpT-In VI
2+
3+
April 13th to 17th 2026, San Francisco, CA (Adobe Office)
4+
5+
---
6+
7+
(See the [Hackathon Archive](./README.md) for past Operations Workshops, Hackathons, Rumathons, and OpT-Ins)
8+
9+
### Agenda
10+
11+
> I hear this is an OpT-In workshop, what exactly am I'm opting into?
12+
13+
Trying to get as much of the virtual team together, the goal is to have high-bandwidth exchanges on the current state and next steps of strictly neccessary Operational Telemetry. We will try to keep it hands-on, so instead of presentations, we will rely on code settling arguments, this means we won't be hacking all the time, there will also be plenty of programming and coding.
14+
15+
The main purpose of the hackathon is social: allow the team to reconnect, meet new team members for the first time, and work on stuff that won't fit neatly into a 45-minute Teams meeting.
16+
17+
| Time | Monday | Tuesday | Wednesday | Thursday | Friday |
18+
| --------: | ------------------------------------------------------ | ------- | --------- | -------- | ------- |
19+
| Morning | Noon: Kickoff, Introductions, Architecture | Hacking | Hacking | Hacking | Demos |
20+
| Afternoon | Hacking | Hacking | Hacking | Hacking | - |
21+
| Evening | Social | Social | Social | Social | - |
22+
23+
### Location
24+
25+
> Where is this going to happen? Do you have a windowless conference room blocked out?
26+
27+
In the San Francisco office. We don't have a room yet, but it will likely have windows.
28+
29+
#### Travel
30+
31+
Fly into SFO and BART will take you to the city.
32+
33+
##### Accommodation
34+
35+
The closest hotel in walking distance is the Intercontinental San Francisco. The hotel is good, the walk to the office, while not terrible, involves seeing some of the rougher parts of the city.
36+
37+
### Goals
38+
39+
> What are you planning to show at the end of the week?
40+
41+
Put down the topic and the people that would like to discuss it:
42+
43+
The theme of this offsite will be determined based on team input and current priorities.
44+
45+
#### Ideas / Suggestions / Topics Collection
46+
47+
(Add your topics here)
48+
49+
### Attendees
50+
51+
> Who is going to be there? Can I come?
52+
53+
If you had your hands on Operational Telemetry code or documentation in the past year, you are welcome to join us. Put your name on the list, so that planning is a bit easier:
54+
55+
1. @trieloff
56+
57+
### Preparation
58+
59+
> What can I do to prepare for the Hackathon?
60+
61+
1. Join `#optel-explorers` on Slack
62+
2. Book your travel and accommodation early
63+
3. Add your topics and ideas to the collection above
64+
65+
### Demos
66+
67+
(To be added during the hackathon)

0 commit comments

Comments
 (0)