# Source: Utah Tech Calendar origin announcements (Forge Utah Slack)

**Type:** source
**Status:** Useful
**Confidence:** Medium
**Source Type:** testimony
**URL:** https://forgeutah.slack.com/archives/CHNQPPQKB/p1781099671909789
**Publisher:** Forge Utah Slack, #localevents
**Raw:** raw/utah-tech-calendar-origin-announcements/2026-08-12-06af04fa1ad6.txt
**Updated:** 2026-08-11

## Summary

Two messages posted the same day — 2026-06-10 — in the Forge Utah Slack `#localevents` channel: one
from **Benjamin Reece** announcing that he had built `utahtechcalendar.com`, and one from
**Clint Berry**, Forge Utah's president, explaining that he had considered the same domain for a
different calendar and chose another name.

Together they are the only located account of **who built the calendar and why**, and they are the
reason this wiki no longer describes it as a Forge Utah property.

## Useful Claims

- **Benjamin Reece built `utahtechcalendar.com`** and announced it himself, in the first person — "I
  put this together".
- He built it because an existing calendar, **Utah Dev Events**, was **missing sources** and lacked
  features he wanted. He describes that predecessor as having been "amazing for me", so the project
  is an extension of it rather than a repudiation.
- He solicited **additional sources** from the channel, which matches the site's own submission model.
- **Clint Berry, Forge Utah's president, is associated with the predecessor**, not with Utah Tech
  Calendar: he says he "almost bought" the `utahtechcalendar.com` domain and "went with 'dev' instead"
  after finding that searching "utah tech calendar" surfaced **Utah Tech University's** calendar.
- That naming collision is a real hazard for anyone searching: **Utah Tech University** is a distinct
  institution whose calendar competes for the same query.

## Verbatim

Each quote carries its speaker, channel, workspace, and date, because Slack message history is not
durable and the quote has to stand on its own once the original is gone. These are reproduced exactly
as typed, **including Slack's `<url|label>` link markup**, because the domain names are the substance
of the second quote and paraphrasing them away would defeat the point.

> Utah Dev events has been amazing for me, but there were many sources missing and features I needed.
> — Benjamin Reece, #localevents (Forge Utah Slack), 2026-06-10

> I put <https://utahtechcalendar.com|this> together so you could stay in the loop. If I'm missing any sources, let me know!
> — Benjamin Reece, #localevents (Forge Utah Slack), 2026-06-10

> I almost bought <http://utahtechcalendar.com|utahtechcalendar.com> too, but when you google utah tech calendar, it comes up with Utah Tech University calendar. So I went with "dev" instead
> — Clint Berry, #localevents (Forge Utah Slack), 2026-06-10

## Reliability Notes

The Forge Utah Slack is an open community workspace and `#localevents` is a public announcement
channel. These are a public launch announcement and a public reply about a domain choice — squarely
the "announcement written to be spread" case, not a private deliberation.

`testimony` rather than `official-page` because of **durability**: the permalinks resolve only for
signed-in members, nothing can fetch them signed out, and Slack retention will eventually delete them.
Hence no `**Retrieved:**` and no `**Archive:**`.

**This is a builder's first-person claim of authorship, and it is the strongest evidence available on
the point** — but it is uncorroborated by any durable record. The site itself names no operator, and
no registration was located. What raises confidence is the second message: the president of Forge Utah
replies in the same thread treating the calendar as **someone else's project he did not build**, which
is a costly thing to say if untrue in front of the community that would know.

That reply is the correction this page exists to record. Forge Utah's homepage promotes
`utahtechcalendar.com` under a "UTAH TECH CALENDAR" banner reading "Ours and everyone else's" — a
phrase describing the **events listed** (Forge's own plus other organizations') that this wiki
previously misread as a claim of **ownership of the calendar**. These messages show a Forge officer
distinguishing his calendar from this one by name, which is not consistent with Forge operating it.

Two limits worth stating. Neither message establishes any **current** relationship between Forge and
the calendar — promotion, funding, or informal endorsement are all compatible with what is said here,
and none is ruled out. And both messages date from launch week in June 2026; nothing here speaks to
who maintains the site now.

## Related Pages

- [Utah Tech Calendar](utah-tech-calendar.md)
- [Source: Utah Tech Calendar official website](utah-tech-calendar-official-website.md)
- [Forge Utah](forge-utah.md)
