Contributors

Made by studentswho had class.

Nobody was paid for this and nobody was assigned it. Everything below happened around a full load of subjects, which is the only reason it looks like it was built by people who use it.

Design and engineering

Kien Leriss Serapio

BSCS-4B · '2027

kienleriss.serapio@tup.edu.ph

Built the app you are looking at — the schedule importer, the attendance and GWA maths, the commute planner, the offline layer, and every screen in between.

Standing on

Two student projects OneTUP would not exist without. Their work is inside this one.

TUPniverse

The 360° virtual campus tour. Every scene you walk through on the campus page is their work, not ours.

  • Lowel-Jay Rubino

    BSCS-4B · '2027

    loweljay.rubino@tup.edu.ph

  • Alltessa Jane Rosimo

    BSCS-4B · '2027

    alltessajane.rosimo@tup.edu.ph

  • Samantha Egar

    BSCS-4B · '2027

    samantha.egar@tup.edu.ph

  • Nicole Dela Cruz

    BSCS-4B · '2027

    nicole.delacruz@tup.edu.ph

ERS Schedule

The groundwork on reading a schedule out of ERS — the problem that had to be solved before any of the rest of this was possible.

  • Dan Jheniel Bringas

    BSCS-4B · '2027

    danjheniel.bringas@tup.edu.ph

OneTUP Contributors

These fill in as people send changes. Right now they are empty, which is the most honest thing this page can say — and the easiest gap anyone has ever had to fill.

  • +
    You?
  • +
    You?
  • +
    You?
  • +
    You?
  • +
    You?
  • +
    You?

Never contributed to anything before?

Neither had anyone here. The whole repository is open, the stack is TypeScript and Postgres, and the first pull request is mostly about getting over the idea that you need permission.

01

Find something that annoys you

The best first contribution is a thing you personally hit. A wrong room code, a route that takes you the long way, a button that lies about what it does.

02

Open an issue before you open a pull request

Say what you want to change and why. It takes five minutes and it saves you writing something that was already being written by someone else.

03

Fork it, branch it, break it locally

Clone your fork, run pnpm install, then pnpm dev. Make the change on a branch named for the thing it does. Nothing you do locally can affect anyone else.

04

Send the pull request

Small and finished beats large and nearly. Describe what changed and what you checked. Your name lands on this page when it merges.

Open the repositoryReport a problem instead