patrickarlt/2013.cascadiajs.com — explained in plain English
Analysis updated 2026-07-15 · repo last pushed 2013-08-11
Submit a talk proposal for CascadiaJS 2013 by adding a markdown file and sending a pull request.
Review all submitted conference talk proposals publicly through the pull request history.
Learn how to run a call-for-speakers process using GitHub pull requests instead of a web form.
| patrickarlt/2013.cascadiajs.com | agg23/csse333project | ctcpip/gitmoji | |
|---|---|---|---|
| Language | CSS | CSS | CSS |
| Last pushed | 2013-08-11 | 2018-01-21 | 2018-02-07 |
| Maintenance | Dormant | Dormant | Dormant |
| Setup difficulty | easy | moderate | easy |
| Complexity | 1/5 | 3/5 | 1/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a free GitHub account and basic familiarity with forking a repo and submitting a pull request.
This repository is the proposal submission system for CascadiaJS 2013, a JavaScript conference held in Vancouver, BC for developers in the Pacific Northwest. Instead of using a traditional web form or email to collect speaker applications, the organizers built their call-for-speakers process entirely around GitHub. Anyone who wanted to present a talk at the conference submitted their proposal by modifying this repository and sending a pull request. To submit a talk, a developer would create a copy of the repository, add a markdown text file containing their presentation details, and include a small profile photo. The proposal file needed to include their name, talk title, description, and bio. Once everything was committed, they would submit a pull request to notify the organizers and send a quick introductory email. The organizers would then review submissions and respond to everyone, whether accepted or not. The project is aimed at JavaScript developers and community members who wanted to speak at the conference, whether they were experienced presenters or first-timers. The organizers specifically emphasize that you don't need to be a JavaScript celebrity to submit, and they cover travel and accommodations for accepted speakers. They were looking for talks covering the open web, including browsers, Node.js, tooling, and related topics, but explicitly excluded vendor pitches. All talks were 30 minutes, and they also welcomed looser unconference topic ideas. What makes this approach notable is how it turns a static code repository into a lightweight application system. By requiring pull requests, the organizers filtered for people with at least basic familiarity with version control, while keeping the submission process transparent and collaborative. Contributors could revise their proposals up until the August 15, 2013 deadline, and the repository itself served as a public record of every talk idea submitted.
The call-for-speakers system for CascadiaJS 2013, a JavaScript conference. Instead of a web form, speakers submitted talk proposals by creating a markdown file and sending a pull request to this GitHub repository.
Mainly CSS. The stack also includes CSS, Markdown, Git.
Dormant — no commits in 2+ years (last push 2013-08-11).
No license information is provided in this repository, it is a conference submission template rather than a reusable software library.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.