# twostraws/wwdc is a README of day-by-day WWDC26 meetup links, and it goes stale the week the event ends

> twostraws/wwdc is a three-file GitHub repository that collects links to community events, watch parties and articles around Apple's WWDC. This article covers how the schedule is laid out, which entries need an Apple ticket, how to contribute and why the list stops being useful after June 2026.

**twostraws/wwdc** — WWDC Community: Learning and sharing together

- Repository: https://github.com/twostraws/wwdc
- Stars: 2,178 · Forks: 217
- Language: Unknown
- License: not declared
- Published: 2026-10-08 · Updated: 2026-10-30 · Language: en
- Canonical page: https://hysenlabs.com/projects/twostraws-wwdc

## The whole project is a README, a code of conduct and a .github folder

The top level of the repository lists three entries: .github/, CODE_OF_CONDUCT.md and README.md. There is no code, no build and no release. GitHub reports no primary language and no license, and the repository has no tagged releases.

Everything of value sits in the README. The stated purpose is that the Apple development community is open and inclusive to everyone, and during WWDC the organisers want to make sure everyone can join events, share articles about Apple's announcements, or just hang out with like-minded people. So a number of community members started the repository to host links to WWDC events, news and tutorials from around the community.

The README names the sources of linked content: SwiftUI Lab, Hacking with Swift, Donny Wals and Swift with Majid, and says it welcomes more, including your own articles. That sets expectations. The repository is a pointer list, and it does not host talks, slides or session notes itself.

The cost of the format is accuracy. Every link leads away from the repository to a page the maintainers do not control, so a cancelled event or a changed venue is fixed only when someone notices and sends a pull request.

## Events are grouped by weekday from Friday June 5 to Friday June 12, 2026

The README's Events and Meetups section starts with a warning. There are lots of events in and around Cupertino, along with others around the world, and most in-person events require tickets. A note asks readers to check the times and locations for each event, in case the maintainers made a mistake or something has changed.

The Cupertino list runs day by day. Friday June 5 has one entry, an iOS Folks Slack coffee meetup in San Francisco. Saturday June 6 has four, including a WWDC Run at 9:30am, a Pre-WWDC26 gathering at San Pedro Square Patio in San Jose and a try! Swift nomikai. Sunday June 7 is the busiest before the keynote, with a breakfast and private tour at the Computer History Museum, two workshops at CommunityKit and a RevenueCat pre-WWDC event.

Monday June 8 has the Special Event at Apple Park, from 9:00am to 4:00pm, plus watch parties. Tuesday June 9 holds the longest list, with a Developer Session at Apple Park, an Indie Developer Meetup, The Talk Show Live From WWDC 2026 by Daring Fireball and a spatial computing meetup. Wednesday June 10 and Thursday June 11 continue, and Friday June 12 closes with Feedback Friday and Make Something, Ship Nothing, both at CommunityKit.

Each entry carries a time range, a name and a link, mostly to Luma, with some on Eventbrite, Partiful and Tito.

## Bold entries are Apple's own and need a WWDC ticket

A few lines in the schedule are set in bold and end with the note requires WWDC ticket. These are Apple's events, not community ones: the WWDC Welcome reception at Infinite Loop on Sunday June 7 from 3:00pm to 7:00pm, the Special Event at Apple Park on Monday June 8, a Developer Session at Apple Park on Tuesday June 9 at 10:00am, a Mixer at the Apple Developer Center Cupertino at noon the same day, and a movie with a special guest at Steve Jobs Theater at 7:00pm.

The distinction answers a common question. Can anybody go to WWDC? Not to those lines. The ticketed Apple events admit people holding a WWDC ticket, and the README does not describe how tickets are obtained, so that question has to go to Apple's own WWDC pages, which the Special Event and Welcome reception entries link to.

The community events differ. Many are free or ticketed separately through their own pages, and the README states that most in-person events require tickets. Whether a given community event has space left is not something the list can say, because the README holds only a link and a time.

One Wednesday entry, the Apple Developer Community Meetup at the Apple Developer Center Cupertino, links to an Apple events page, so even an Apple venue can host a community-named session.

## CommunityKit hosts a large share of the daytime sessions

Reading the list, one venue name keeps coming back: CommunityKit. Its entries include two workshops on Sunday, a keynote watch party with iOSDevHappyHour and a State of the Union watch party on Monday, a WWDCWomen breakfast, an Apple Vision Pro meetup, an App Money Lunch Club presented by RevenueCat, an Indie Developer Meetup and a session on what is new in iOS 27 on Tuesday. Wednesday adds a community breakfast with trivia, a Launched LIVE session, Meet try!Swift, a Container Install Meetup, an Indie Fair and an accessibility meetup.

The pattern is that one venue works as the daytime hub, while evening events spread across Cupertino and San Jose, each organised by a company, a conference or an individual. RevenueCat, Superwall, Bitrig and Helium with Paddle and Autosana appear as sponsors or organisers of the larger evening parties.

A limit follows from the format. The README gives names and times but no capacity, address or cost, so for CommunityKit sessions the only way to learn those is to open each linked page. A reader building a personal schedule has to click through every entry.

Times also overlap heavily. Tuesday afternoon alone has several sessions at 2:00pm and 3:00pm, so attending everything is impossible and the list gives no help choosing.

## Keynote watch parties start at 10am Pacific on June 8

A separate section covers watching the keynote with other people. The keynote starts at 10am Pacific Time on June 8th, and events are taking place to stream it in other places. The section invites readers to add their own in a pull request.

The watch parties in the schedule include a Keynote Watch Party with iOSDevHappyHour at CommunityKit from 9:00am to 12:00pm, a WWDC 26 Watch Party in Santa Clara from 9:30am to 11:30am and a State of the Union watch party at CommunityKit from 1:00pm to 4:00pm. Apple's own Special Event at Apple Park runs from 9:00am to 4:00pm that day and requires a ticket.

The README text available here is cut off partway through the watch party section, so the world-wide parties it goes on to list are in the full file. If you are outside California, that is the part of the README to read.

The practical point for someone outside the Pacific time zone is that the 10am start is a fixed time, so convert it before the day, and do not rely on the schedule's local times being yours.

## Contributing means a pull request, under a code of conduct

The README repeatedly asks for additions. Event organisers can add their event, authors can add articles, and watch party hosts can add theirs, all through pull requests. The repository has a CODE_OF_CONDUCT.md at the top level, and a .github folder that holds repository configuration files.

The contribution route is light. There is no CONTRIBUTING.md, no template listed and no schema for an entry, so the rule is to copy the format of the lines around yours: a day heading, a time range, a name in link form, and an organiser or venue where relevant.

The README is open about its own error rate. It asks readers to check times and locations in case the maintainers made a mistake. That honesty is useful, and it also means a wrong time can sit in the list until a reader reports it. If you run an event, you are the person best placed to keep your entry correct.

A formatting detail shows how informal the list is. The RevenueCat entry on Tuesday carries a strikethrough in its name, turning House into Mansionparty, which is a joke baked into the markup. The project is a community noticeboard, and it reads like one.

## The list covers June 2026 only, and the last push was on June 26

The schedule is tied to one WWDC. Every dated entry sits between June 5 and June 12, 2026, and the last push to the repository was on 2026-06-26, two weeks after the final listed event. The repository is not archived, so a future year's list could be added to the same README or the repository could be cleared and reused, but the README does not say which.

For a reader today, the schedule is a record. The links are likely to be dead or pointing to past event pages, and no entry gives you something to attend. The still-useful part is the article list from community writers, if the full README keeps it up to date, and that cannot be confirmed from the portion of the file shown here.

What the repository does show is a model. A small group of community members put a single Markdown file on GitHub and let pull requests do the editing. It needs no hosting, no database and no login, and anyone who has used Git can contribute.

For next year, the reasonable expectation is a rewritten README with new dates. Check the repository's commit history before assuming that has happened.

## Conclusion

Use twostraws/wwdc as a directory of community events and articles around WWDC, and open a pull request if you run an event of your own. Do not rely on it for ticketing or times, because the README itself asks you to check each event's page. The 2026 schedule runs only from June 5 to June 12, so read it as an archive now.

## FAQ

### What is the schedule for WWDC 2026 in this list?

The community event list runs from Friday June 5 to Friday June 12, 2026. The keynote starts at 10am Pacific Time on June 8th, and the Apple Park Special Event that day runs 9:00am to 4:00pm.

### Where will WWDC 2026 be held according to the list?

The listed events are in and around Cupertino, including Apple Park, Infinite Loop and the Apple Developer Center Cupertino, with other events in San Francisco, San Jose and Santa Clara.

### Can anybody go to WWDC events in this list?

Community events are open through their own pages, though most in-person events require tickets. The entries marked as requiring a WWDC ticket, such as the Special Event at Apple Park, need an Apple ticket.

## Sources

- [Issues](https://github.com/twostraws/wwdc/issues)
- [README](https://github.com/twostraws/wwdc/blob/main/README.md)
- [twostraws/wwdc on GitHub](https://github.com/twostraws/wwdc)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/twostraws-wwdc
