The goal is to displace Meetup.com for the monthly hack night: events live on the site, members RSVP in one click,
every RSVP gets a calendar file, and reminders go out a week and a day ahead. Below are the forks that actually
change the build. Each has a recommended option, which is what the drafted spec says today, and a way to pick
something else.
Decided 2026-10-13. All seven went with the recommended option; the notes are folded into the spec:
the RSVP follow-up is now a three-way choice (decision 2), "programs" became an optional series plus a structured agenda on each event (decision 4),
private RSVPs via the shadow store are written up as the future path (decision 5), and a desktop rendering of the home strip is below decision 3. Forms stay live if you change your mind.
Laddr's events model held exactly four records in twelve years: Launchpad 2018, 2019, 2023 and DataHack 2020.
Each was a program with a day-grouped "Schedule" sidebar of sessions. It had no RSVP, no
attendee list, no calendar export, no timezone, no cancel flag. Hack nights never touched it: they lived on
Meetup, and the old home page parsed Meetup's iCal feed live for a "check in" form keyed by Meetup event id.
The schedule sidebar is the one piece of UI worth keeping in mind (decision 4).
Laddr /events/*past: title, start/end, truncated description, no location, no pagination.Laddr event detail: markdown body plus the day-grouped Schedule sidebar of sessions with venue and time range.
Decision 1
What does /events look like?
With roughly one event a month, the page's job is to make the next event unmissable and let people subscribe once.
A · Agenda list
Spec'd · recommended
ProjectsEventsHelp WantedMembers
Events📅 Subscribe to calendar
UpcomingPast
November 2026
Tue
3
Nov
Code for Philly Hack Night
6:00–8:30 PM EST · Indy Hall
You're going ✓ · 14
Sat
14
Nov
Open Data Workshop
10:00 AM–1:00 PM EST · Online
6 going
December 2026
Tue
1
Dec
Code for Philly Hack Night
6:00–8:30 PM EST · Indy Hall
2 going
Date block carries the scan; month headings group without a grid's empty cells.
Same card renders on the home strip and in Past; one component.
Doesn't shout the next event any louder than the third one.
B · "Next up" hero + list
Alternative
ProjectsEventsHelp WantedMembers
Next up · in 6 days
Code for Philly Hack Night
Tue, Nov 3 · 6:00–8:30 PM EST · Indy Hall, 709 N 2nd St
I'm going14 going
Later
Sat
14
Nov
Open Data Workshop
10:00 AM–1:00 PM EST · Online
6 going
Tue
1
Dec
Code for Philly Hack Night
6:00–8:30 PM EST · Indy Hall
2 going
RSVP to the next hack night without leaving the list.
Reads as "there's a thing happening", which is the Meetup feeling we're replacing.
Two card designs; the hero looks odd when the next event is a cancelled one or months away.
C · Month grid
Deferred
ProjectsEventsHelp WantedMembers
‹November 2026›
S
M
T
W
T
F
S
1
2
3 Hack Night
4
5
6
7
8
9
10
11
12
13
14 Workshop
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
1
2
3
4
5
Matches the word "calendar" in the issue title.
28 empty cells for 2 events; terrible on phones; a second code path to maintain.
The webcal:// feed already puts events in the member's real calendar.
Decision 2
How does someone RSVP?
Travis: "MVP is working RSVPs." Chris: "optionally RSVP to a particular project." The question is whether the project choice sits before or after the click.
A · One click, project after
Spec'd · recommended
Code for Philly Hack Night
Tuesday, November 3 · 6:00–8:30 PM EST Indy Hall · 709 N 2nd St, 3rd Floor ↗
I'm going14 going
Your name will appear on the attendee list.
▼ after the click
You're going ✓Can't make it?
What are you coming to do? (optional)
I'm new to Code for PhillyI don't have a project yetI'm coming to work on Pick a project ▾
Also listed on Meetup ↗
"Going" is one click, from the detail page or the home strip. Nothing to fill in.
Updated per your note: the follow-up gives newcomers an answer that isn't "pick a project". Attendee list groups by project, then "New to Code for Philly", "Looking for a project", "Not sure yet".
Some people will never answer. Fine: it's a bonus, not the RSVP.
B · RSVP dialog
Alternative
RSVP…14 going
RSVP to Hack Night
ConfirmCancel
Captures guests and a note in one place, like Meetup's flow.
A form between the member and "going". Every field is a reason to close the tab.
Guests and notes have no consumer yet; they'd be stored and never read.
C · External RSVP link
Status quo
Code for Philly Hack Night
Tuesday, November 3 · 6:00–8:30 PM EST · Indy Hall
RSVP on Meetup ↗
No attendee list. No calendar file. No reminders we control.
Nothing to build beyond the event record.
Keeps Meetup as the system of record, which is the thing the issue wants to end.
Decision 3
Where do events show on the home page?
The issue asks for "a short list on the homepage". Today the page is hero → featured projects → get involved → activity + help-wanted rail.
A · Strip under the hero
Spec'd · recommended
Contribute towards technology-related projects… Volunteer
Upcoming EventsSee all · Subscribe
Tue
3
Nov
Hack Night
6:00 PM EST · Indy Hall · 14 going
RSVP
Sat
14
Nov
Open Data Workshop
10:00 AM EST · Online · 6 going
→
Join a Project · ▢ ▢ ▢
The next hack night is one click from the first screen a newcomer sees.
Hidden entirely when nothing is scheduled, so it never advertises an empty calendar.
Pushes featured projects down ~120px.
B · Card in "Get involved"
Alternative
Contribute towards technology-related projects…
Join a Project · ▢ ▢ ▢
Sponsor
Start a Project
Volunteer
Next event Nov 3 · Hack Night
Zero layout shift above; events become a fourth way to get involved.
Below the fold on most phones; one event only; "Get involved" becomes four cards of unequal shape.
C · Rail beside activity
Alternative
Contribute towards technology-related projects…
Join a Project · ▢ ▢ ▢ Get involved · ▢ ▢ ▢
Latest Project Activity
Events Nov 3 · Hack Night Nov 14 · Workshop
Help Wanted
Sits with the other "live" content; matches the help-wanted rail pattern.
Bottom of the page. Members who come to the site for the hack night date scroll past everything.
A on a desktop viewport
Full-width strip at ~1280px. The soonest event takes the left two-thirds with the RSVP; the next two sit as compact rows on the right. Below md it stacks into the three-row list shown above.
Contribute towards technology-related projects that benefit the City of Philadelphia. No coding experience required. Volunteer
Upcoming EventsSee all events → · 📅 Subscribe
Tue
3
Nov
Code for Philly Hack Night
6:00–8:30 PM EST · Indy Hall, 709 N 2nd St
14 going · 3 new to CfP
I'm going
Sat
14
Nov
Open Data Workshop
10:00 AM EST · Online
6 going
Tue
1
Dec
Code for Philly Hack Night
6:00 PM EST · Indy Hall
2 going
Join a Project
Decision 4
What is an event record?
Laddr modelled programs with sessions because it only ever stored Launchpads. The current need is the monthly hack night. Both can be true over time.
A · Flat event + series + agenda
Spec'd · updated
event-series/monthly-hack-nights.toml
title, description (a label, not a rule)
events/2026-11-03-hack-night.toml
title, description (md)
startsAt, endsAt (UTC; shown ET)
venueName, venueAddress
onlineUrl, meetupUrl
seriesId → monthly-hack-nights
[[agenda]] (optional, embedded)
startsAt, endsAt?, title
venueName?, description?
status draft|scheduled|cancelled
icsSequence, reminders{}
event-rsvps/2026-11-03-hack-night/
chris.toml plan = project, projectId = …
travis.toml plan = newcomer
One record = one thing you can RSVP to. No "which session?" question on a hack night.
Updated per your note: an optional series ("Monthly Hack Nights", "Launchpad") with its own page, and a structured agenda that renders laddr's day-grouped Schedule sidebar. Sessions get identity only when they need RSVPs: then they become events in the same series.
The agenda row editor is the most form-heavy piece; it hides behind a disclosure so a hack night form stays short.
B · Program + sessions now
Laddr's shape
events/launchpad-2023.toml
(program: spans Mar 31 – May 10)
event-sessions/launchpad-2023/
friday-night-kickoff.toml
opening-work-day.toml
showcase-night.toml
↳ RSVPs live here
events/2026-11-03-hack-night.toml
(a program with… one session?)
Faithful to the four laddr records; schedule sidebar on day one.
Every hack night becomes a program wrapping one session, or two code paths for "simple" vs "program" events.
Doubles the API, screens, and tests before the first hack night is on the site.
C · Flat + markdown schedule
Variant of A
events/launchpad-2023.toml
description = """
## Schedule
### Friday, March 31
**6–9pm** · City Hall, Caucus Room
Friday Night Kickoff — …
### Saturday, April 1
**9am–7pm** · Philadelphia Innovation Lab
Opening Work Day — …
"""
This is exactly how A backfills the four historical events.
As a permanent answer it means big events never get per-session RSVPs.
Decision 5
What is an RSVP, and who can see it?
RSVP records would live in the public data repo like everything else. That settles visibility more than any UI toggle could.
A · Binary and public
Spec'd · recommended
Going (14)
SquadQuest · 5
Clean & Green Philly · 3
Undecided · 6
RSVPs open until the event ends — tap "I'm going" from the door.
A record exists = going. Withdraw = delete. Nothing to misread.
Attendee list grouped by project answers "who'll be at the table for X?" — laddr's check-in feature, for free.
Honest about the storage: the data repo is public anyway.
No way to RSVP quietly. Members who don't want to be listed don't RSVP.
B · Going / Maybe / Not going
Old Meetup
GoingMaybeCan't go
14 going · 9 maybe · 3 not going
Familiar vocabulary.
"Maybe" tells organizers nothing and inflates the list; Meetup itself removed it.
Storing a public "not going" is a strange thing to publish about someone.
C · Private RSVPs
Can't honor
I'm going
14 going
The record is in a public git repo; a "hide me" checkbox would be a promise the storage breaks.
Moving RSVPs to the private store loses the attendee list, which is the feature.
Decision 6
What sends the one-week and one-day reminders?
Single replica, no job queue, no database. The reminder has to be at-most-once across pod restarts.
A · In-process sweep
Spec'd · recommended
every 5 min (like the revocation sweeper):
for event in scheduled, startsAt ≤ now+7d:
week due? now ≥ start−7d && now < start−24h
&& reminders.weekSentAt unset
day due? now ≥ start−24h && now < start
&& reminders.daySentAt unset
→ commit reminders.*SentAt = now (mutex)
→ email each RSVP (fire-and-forget)
Nothing new to deploy; bookkeeping lives on the event record in git.
Closed windows make a long outage a skipped reminder, never a late or duplicate one.
Timer doesn't run while the pod is down. At 5-minute ticks that only matters for multi-day outages.
B · GitHub Actions cron → internal endpoint
Alternative
.github/workflows/event-reminders.yml
schedule: "*/30 * * * *"
→ POST /api/_internal/send-reminders
Authorization: Bearer $SECRET
(same due-window logic behind the endpoint)
Externally observable: the Actions log shows every tick.
Another secret to seal per cluster; GitHub's cron is best-effort and often minutes late.
Same logic, one more moving part. Easy to add later if we want the audit trail.
C · Provider-scheduled sends
Not viable
on RSVP:
schedule email for start−7d
schedule email for start−1d
on withdraw / cancel / reschedule:
find and cancel the scheduled sends
No timer in our process.
Postmark has no scheduled-send API; every edit, withdrawal, or cancellation would need to chase queued mail.
Decision 7
How does the monthly hack night get created each month?
A · Duplicate and adjust
Spec'd · recommended
EditDuplicateCancel event…
Copied from Hack Night (Nov 3). Check the date.
Publish now
Every occurrence is an independent record: its own RSVPs, its own cancel, its own history in the data repo.
Form opens prefilled, date shifted one month in Philly time (DST-safe). Thirty seconds a month.
A human does it monthly. If the venue changes for good, each future copy is edited separately.
B · Recurrence rule
Deferred
Edits apply to: ◯ this event ◯ this and following ◯ all
Set once.
Exceptions ("skip December", "move to Thursday this once") need the this/following/all edit model, materialized occurrences, and a generator — the hardest part of every calendar product.
RSVPs and reminders still need a concrete record per occurrence, so it generates A anyway.
Also in the drafted spec
Settled by the issue thread or by existing conventions. Annotate anything here you'd change.
Topic
What the spec says
URLs
/events, /events/past, /events/<slug>; /calendar redirects to /events. Slugs default to 2026-11-03-hack-night so the data-repo folder reads chronologically. Laddr's /events/*past and the four old event handles keep working.
Time
Stored UTC, always displayed in America/New_York with the zone abbreviation. Staff form takes Philly wall-clock; "Ends" defaults to start + 2h30.
Who creates
Staff only. Status draft → scheduled → cancelled via explicit publish/cancel endpoints; hard delete only for drafts or RSVP-less events.
Calendar files
.ics attached to the confirmation email; "Add to Google Calendar" link; "Download .ics"; a webcal:// subscription feed of all events. Stable UID + incrementing SEQUENCE so edits and cancellations update entries in place.
Emails
Confirmation (with .ics), week-before, day-before, "event updated" when time or venue changes, "cancelled" with the staff note. All through the existing Postmark notifier, fire-and-forget. Reminders at-most-once.
Meetup transition
Optional meetupUrl rendered as a small "Also listed on Meetup" link below the RSVP control. Never the call to action.
Navigation
"Events" in the header after Projects, in the footer Explore column, breadcrumbs for every events route.
Deferred (documented)
Programs with sessions (via parentId), recurrence, capacity/waitlist/guests, cover images, Slack announcements (ties to #195), month grid and search.
Plans
events-core (model, API, screens, emails, home strip) → events-reminders (the sweep) and events-legacy-backfill (the four laddr events) in parallel.
Done picking? Press Send to Agent in the Lavish bar. Free-form notes on any mockup or row work too.