Project Report

Open Source Development for Google Applications

Hackjudge
Abstract
During events, there is so much that needs to go into managing — from creating portals
and applications for the event to a whole mess of excel sheets that the organizing team
has to manage while scoring and ranking teams. To address this problem I created
Hackjudge, a platform to create and manage events from start to finish.

Tech Stack

Implementation
The project is divided into 2 components:
1. The admin side to “judge”
2. The participant’s side for letting participants/teams submit their ideas [the “hack”
part]
 All the backend code can be found in the following links:

Version 1 ===> https://github.com/pragati1610/hackjudge-backend

Version 2 ===>
https://github.com/Pragati1610/Hack-Backend/tree/bcca514035198b5759c57eb1b4d3b1e
099a72533

Version 3 ===> https://github.com/Pragati1610/Hack-Backend

Details on routes

https://documenter.getpostman.com/view/10709921/TVmJheF6

Screenshots of the projects

The project is the backend for this app. So no screenshots available for it. Here is instead
an architecture diagram for Hackjudge.

1. Designed and worked on the models and relations

2. Worked on middleware

✓ To check if a user is admin or not

✓ To check if a user is authorized

3. Implemented CRUD for models like Auth, Events, Teams, Metrics, Scores, Comments
✓ Then finally implemented those routes that were specific to the project’s
functionality

✓ Getting statistics about events

✓ Getting all participants

✓ Getting all teams, qualified teams, evaluated teams, and unevaluated teams of
an event

✓ Getting all reviews about an event, and a separate route to get data for a review

✓ Several routes to manage how a user can join a team and how a leader of the
team can manage the team and make their submission