- Beaverhacks is open to students and alumni of Oregon State University only.
- Graduate students and alumni are not eligible to win monetary prizes.
- Participants are allowed to form a team. A team may consist of 1 to 4 members. All team members must be registered on DevPost and added to the project submission.
- Projects must be built solely by team members entirely during the hackathon time-frame.
- Teams may work on an idea that they have worked on before as long as they are not reusing their previous code.
- Teams may use libraries, frameworks, or open-source code in their projects. Working on a project before the event and open-sourcing it for the sole purpose of using the code during the event is against the spirit of the rules and is not allowed.
- Teams . However, teams are allowed to debug and make small fixes to their programs after time is up. e.g. If during the voting period you find a bug that breaks your application and the fix is only a few lines of code, it's okay to fix that. Making large changes or adding new features is not allowed.
- Teams must submit their project submission by the deadline. If any issues, teams must contact Admin BEFORE the deadline closes.
- Submissions must include a link to the video demo. The video can be hosted on Youtube, Vimeo, etc.
- Projects must be hosted on a public Github repository. The entire commit history must be present. You will be required to submit your Github repository URL upon submission.
- If submitting a console app, you are also required to submit a repl.it project link.
- Projects or behavior that violate either the Hack Code of Conduct and/or the OSU Code of Student Conduct are not allowed.
- Teams can be disqualified from the competition at the organizers' discretion. Reasons might include but are not limited to breaking the rules, violating either code of conduct (see above) or other unsporting behaviour.
- Participation in this event constitutes your full and unconditional agreement to all rules, terms, and conditions of this event.