Current tech lead: Mark Fan
CMU Eats is committed to providing up-to-date, easily-accessible info for all things dining-related!
This is where we store feature drafts (aka RFCs) (some were unfinished from last year), env variables (yes, very secure of course), reference docs, and incident reports. To contribute to either our frontend repo or backend repo, assign yourself to anything on our Project Board, and let us know in the Slack! The documentation below is not required reading, but it will be very helpful should you choose to become a long-term contributor!
Do also ask either @Mark Fan or @Eric Xu for repo access if you can’t push branches or make PRs to either repo. See each repo’s README for local setup instructions!
Figma: https://www.figma.com/design/dp9RzhJtoMFWiUGjVCd6K7/CMUEats?node-id=1392-63743&t=N0BhdudttZYpNrzy-1
Running list of data issues we should fix
<aside>
we recommend you to make one before (or during) implementation!
</aside>
(📄 - draft, ⚙️ - in progress, ✅ - done, ❓- unclear, should discuss)
[archive 2025-26] New features we can add
RFC - Introduction of dining api db schema w/ location data and time overwrites
memcho should restart railway prod services on 5 min of downtime