Skip to content
Avoid the traffic jam that is judging through automation!
JavaScript HTML Python Other
Branch: master
Clone or download
sarah256 Merge pull request #19 from Bostonhacks/jasonli
set up our track and sponsor track CSVs
Latest commit d781cf1 Apr 4, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
giudice
scripts
tests
.gitignore
CODEOWNERS
LICENSE
README.md
judges.txt
requirements.txt
setup.py
submissions.csv

README.md

Giudice ✒️

Avoid the traffic jam that is judging through automation!

Description 🐍

A Python Flask web application that eases the judging process at hackathons.

  • Current Features:
    • Assigns each project a table number
    • Sorts projects by category so that sponsors know what tables to go to for their categories
    • Assigns judges to each project
    • Calculates the number of judges needed based on the number of submitted projects
  • Planned Features:
    • Easy way to submit Devpost CSV
    • Login to let judges judge projects directly from a mobile device or laptop and record their responses, including ranking projects and taking notes on them
    • Login for admin view to see all submitted scores
    • Ability to export scoring data into a separate file

Running Giudice Locally 🙏

It is recommended that you use a virtual environment to run Giudice for development. Be sure that you are using Python 3 for the virtual environment. See here for more on how to use them.

Once on your virtual environment:

To install dependencies, run:

$ pip install -r requirements.txt

To run Giudice, use the following command:

$ ./scripts/run-flask.sh

To run tests, use the following command:

$ ./scripts/run-tests.sh

How Judging Works at BostonHacks

Note for future contributors/users, here is how we at BostonHacks expect judging to work:

  • Utilize Devpost for project submissions (this is important, as Giudice relies on Devpost data - see next section for more on this)

  • Judges go to their assigned tables and give each project a score based on its unsponsored track

  • We leave the judging of sponsor tracks up to those sponsors, however this app will still let the sponsors know which tables to judge for their tracks.

  • In the case of a project with no given track, it will be judged solely overall.

Feel free to fork this repository and adjust Giudice according to your hackathon's own judging process!

Using Giudice 👀

Giudice relies on Devpost to get its submission data. Devpost provides a CSV file with all the necessary submission data. You can find it for your hackathon by going to your hackathon on your hackthon's admin Devpost account, and clicking: "Manage hackathon" >> "Metrics". From there, you can click "Generate .csv report", using the default options. This is the CSV file you should give to Giudice.

Giudice will also need a list of your judges. This list can be updated in the judges.txt file. Enter each judge's name on a separate line.

Contribution Guidelines 👋

  • EVERY pull request made on this repository must have at least one reviewer that approves it. If the code contribution is significant (a new feature, large commits, etc.) there must be at least two approving reviewers. If you feel your contribution is just too significant, it is okay to request a group review at a team meeting! You can explain your changes to us, and we will discuss them in the meeting.

  • This project follows Sphynx styling, and thus requires a docstring for every Python function.

A simple example of how to format a docstring in the Sphynx style would be:

def add(x, y):
	"""
	Add two numbers together

	:param int x: a number to be added
	:param int y: a number to be added
	:return: a sum of the two inputs
	:rtype: int
	"""
	return x + y

Other types beyond 'int' include, but are not limited to, 'bool', 'dict' and 'str', and must be spelled as such. For more on Sphynx, see here.

  • For every new feature added, please update the README accordingly.

  • For every new dependency added, please include it in the requirements.txt file on a newline.

  • Commits should have descriptive messages that state not WHAT you changed, but rather WHY you changed it. Remember: we generally know how to read your code, but we might not know why you did it! If you feel that your code is unclear as to WHAT you changed as well, only then is it necessary to state the "what" in the commit message, or if the "why" is self-evident. Please see the BostonHacks code guidelines for more details on proper formatting.

  • Write a test in the tests directory for new significant functions. Call the new test in the run_tests() function so that the testing script runs properly.

You can’t perform that action at this time.