Ninety Seconds in the Tracker: What a Stranger Actually Learns About Your Project

Every open-source project spends an outsized amount of energy on its landing page. There's a hero banner, a three-step quickstart, maybe a logo rendered in dark mode. Then a developer lands on the repository, scrolls past the README, and clicks the Issues tab — because that's where the truth lives.

What they find there decides, in most cases, whether they file a bug, open a pull request, or quietly close the tab. So we did what any skeptical engineer would do: we picked a mid-sized repository with an active community and gave ourselves ninety seconds as a total stranger. No prior context, no Discord membership, no memory of a conference talk. Just the tracker.

The First Ten Seconds: Labels or Noise

The label taxonomy is the first thing the eye hits, and it's where most projects lose the plot. This repo had forty-one labels, including three near-duplicates (bug, confirmed-bug, bug-report) and two that hadn't been applied to anything since 2022. To an outsider, that's not organization — it's sediment.

Worse, the triage labels told no story. An issue marked needs-triage from eleven months ago sits next to one marked triaged from last week, and nothing explains the difference in priority. A stranger can't tell whether the project is drowning or just untidy, and both readings cost you contributors.

The fix is boring and effective: collapse the taxonomy to under a dozen labels, delete the orphans, and make the triage states legible in sequence. If a label can't be explained in a five-word tooltip, it's decoration.

The Pinned Issues Are Your Constitution

Pinned issues function as the tracker's front page, and this project had pinned exactly one: a year-old release announcement. Meanwhile, a newcomer asking a genuinely good onboarding question sat unpinned on page four.

Compare this to how well-run US civic institutions handle signage — the moment you walk into a library or a DMV, the first thing you see tells you what to do next. A pinned issue should do the same: point first-time contributors at good-first-issue candidates, link the contribution guide, and state plainly what kinds of reports the maintainers want. Anything less and the tracker becomes a maze the visitor has to solve alone.

Templates Tell Strangers What You Value

The repository had a bug template — a good one, actually, with reproduction steps and version fields. It had no feature-request template and no question template, which meant every vague inquiry arrived as unstructured prose that a maintainer had to interrogate by hand.

Templates are quiet signals. A thorough bug template says, we take correctness seriously. A missing question template says, we'd rather you didn't ask. Neither message is typed by anyone, but both are read by everyone. If your response latency to templated issues is two days and to untemplated ones is three weeks, the template isn't paperwork — it's the queue-jump, and strangers figure that out fast.

The Ninety-Second Verdict

Here's what our stranger walked away with, in order:

1. The project is active (recent issues, recent commits referenced in threads).
2. The maintainers respond, but inconsistently — some threads get answers in hours, others in months.
3. Nobody is explicitly welcoming newcomers, because nothing in the tracker is aimed at them.

That's a mixed report card for a project whose README was excellent. The disconnect matters because contribution decisions are made at the tracker, not the landing page. A developer who reads a polished README and then finds a chaotic issue list concludes that the polish is marketing and the chaos is reality.

A Five-Point Audit You Can Run Today

• Open your tracker in a private window and set a timer for ninety seconds. Write down every judgment you make. That list is your real homepage.
• Prune labels ruthlessly. Anything unused in two release cycles gets deleted or merged.
• Pin for the newcomer, not for the announcement. Release notes belong in the releases tab; wayfinding belongs in pins.
• Audit response latency by label. If good-first-issue items wait longer than bug items, your onboarding funnel is inverted.
• Close or convert stale issues publicly. A thread with no activity for a year isn't neutral — it signals neglect to anyone who scrolls deep enough.

None of this requires a governance vote or a funding grant. It requires the same instinct you'd apply to any user-facing surface: assume the visitor knows nothing, has almost no time, and is deciding right now whether your project deserves their Saturday.

The issue tracker is where your project's culture is legible in a way no README can fake. Tend it like a front porch, not a junk drawer.