Archive · Old QC Hack
Challenges 2022
QC HACK 2022 Challenges
Pre-Hacking Address: 9:00 AM EDT (UTC-04:00) on Saturday, April 9th, 2022
Hacking Opens: 10:00 AM EDT (UTC-04:00) on Saturday, April 9th, 2022
Hacking Closes: 10:00 AM EDT (UTC-04:00) on Sunday, April 10th, 2022
Judging: 10:01 AM EDT (UTC-04:00) on Sunday, April 10th 2022 to
10:00 AM EDT (UTC-04:00) on Friday, April 15th, 2022
Winners Announced: 2:00 PM EDT (UTC-04:00) on Friday, April 15th, 2022
Instructions
Instructions for each team (1 to 5 people):
Browse the challenges, and pick one to participate in.
Fork/duplicate the challenge repository of your choice, (for the purposes of these instructions, this forked/duplicated repository will be referred to as your “team repository”).
Work on your “team repository”.
Exactly one member of your team should submit the URL/link to your “team repository” via the QCHack 2022 Challenge Submission Form (released when hackathon begins). This team member may edit and submit the form as many times as they wish, up to and including the deadline above.
For your reference, the form will require the following fields:
Identifying & contact Information, such as emails and Discord
URL/link to your “team repository”
Challenge-specific fields
Acknowledgement of the “QCHack 2022 Hacking Rules” (https://docs.google.com/document/d/1XcnTnEAw-0Y8HJaqAG13ZEvYK7R5J4uUVsOwzx3USqM/edit?usp=sharing)
If you have submitted the above form, you have successfully submitted your team’s project and registered your entire team!
Please do not modify your repository between the judging period of 10:01 AM EDT on Sunday, April 10th 2022, and 10:00 AM EDT on Friday, April 15th, 2022.
If you modify your repository during this period, your submission may be subject to disqualification.
Tips & Suggestions
Review the above instructions before you begin.
We strongly encourage working with other teammates rather than by yourself. A hackathon is usually more fun and rewarding this way! Without that being said, it is perfectly possible to do well in a challenge regardless of the team size.
To find other teammates, feel free to introduce yourself in the #team-forming Discord channel. If you have a difficult time finding teammates, please message a member of the QCHack on Discord, and we will try our best to put you in a team with others in a similar position.
Why do we say Fork OR Duplicate the challenge repository? This is because GitHub doesn't allow you to change visibility of the forks. So if you’d like to keep your work private, you can either
fork the challenge repository, keep it public, and push your changes at the last possible moment;
duplicate the challenge repository, make it private to work on it during the Hacking period, and make it public at the end of the Hackathon. Your “team repository” is not required to be an actual fork of the challenge repository, it just has to follow the same folder structure for auto-graded tasks.
We recommend that your team submit a draft of the “QCHack 2022 Challenge Submission Form” at least 30 minutes before the deadline, since you can always edit and resubmit before the deadline!
Refresh this page and the challenge repositories often, as they may be updated with new information during the Hacking period! We will also inform you of all important updates on Discord.