Truman Computer Science Capstone Presentation System

A significant addition to the Truman Computer Science department's capstone system. Adds the ability to schedule capstone presentations using a calendar-like system.

Uses SvelteKit as the front-end framework.

Documentation

All external (non-code comment) documentation is inside the docs folder.

Dependencies

• git
• Node.js

Run

git clone https://github.com/jagger-harris/truman-cs-capstone-system.git
cd truman-cs-capstone-system
npm install
npm run dev

Further instructions to setup are in the docs folder within the file setup.txt.

Build For Production

npm run build

Contributing

• Pull requests should always be reviewed by at least one other member prior to being merged
  • Exceptions include very small pull requests that are not critical to functionality (making frontend buttons look nice as an example)
• Mark unfinished pull requests with the wip label
• When you start work on something you should have a pull request opened that same day. Or at least as soon as possible so others can be aware of the changes you are making
• You as the person opening the pull request should assign a reviewer

Merging

Once your pull request has been Approved it may be merged at your discretion. In most cases responsibility for merging is left to the person who opened the pull request, however for simple pull requests it is fine for anyone to merge.

If substantive changes are made after the pull request has been marked Approved you should ask for an additional round of review.

• Use squash and merge if all commits in the PR can be summarized succinctly by a single message
• Use rebase and merge if each commit in the PR has its own significance
• Avoid just merge as it will create an extraneous merge commit