About

Why I made this site

COSC 499 is the biggest thing most of us build at UBC Okanagan: eight months, a real client, a team that has to figure out how to work together. Then it ends, the repos go quiet, and the next cohort starts from zero. I wanted a place where that work is remembered, and where the people coming next can learn from it.

A benchmark for the current and next cohort

When you're in week 6 of capstone, it's hard to tell whether your team is on pace. Is 200 commits a lot? Should you be merging more PRs by now? Do other teams actually review each other's code?

This site lets the current cohort, and the one after it, see how previous cohorts performed at the same point in their term. The tracking chart lines up every cohort by week, so you can benchmark your team against what real teams did before you, not against a guess.

See how 2026–27 is tracking Compare every cohort

Recognition for the work

A final demo shows the product, not the person who reviewed forty pull requests, closed the issue backlog, or kept the team shipping every week. Those people deserve credit too.

Every cohort and team page highlights its top contributors across commits, merged PRs, reviews and issues, so the work behind a project is visible, and you can point to it after you graduate.

Not just the big numbers: the quirky ones too

This isn't only a leaderboard. Alongside the most commits and most reviews, there are the night owls, the early birds, the 3 am regulars, the holiday heroes who committed over Christmas, the fastest PR ever merged and the one that waited the longest.

That means anyone can end up anywhere on this site. You don't need the most commits to show up; you might be the person who kept pushing at 3 am, or who merged a PR in eleven seconds. Capstone is full of those stories, and they're as much a part of it as the totals.

Keeping a record

Capstone repos get made private, deleted, or moved when people graduate, and each year's work quietly disappears. This site keeps a snapshot of the activity from 15 cohorts so far, back to 2017, so the history of the course stays in one place.

What the numbers don’t show

GitHub activity is only part of a capstone. Design, client meetings, planning, testing by hand, writing docs and pair programming rarely show up as commits, and teams work differently: some squash every PR into one commit, some commit every few minutes. So please read these as a picture of activity, not a grade.

That's also why the site celebrates, and never ranks anyone from the bottom. There are no "least active" lists, and personal pages only show your own work, never a comparison with your teammates.

Help complete it

Some cohorts look small because their repos are private or were moved off the course organization. If you were on one of those teams, you can probably see data I can't, and adding it takes about 15 minutes with no coding.

Add your cohort Ask for your page to be removed

Built by rin, a COSC 499 student, from public and course GitHub activity. Not affiliated with UBC.