Hackathon Rules
Hackathon Rules
1. Code of Conduct
Participants are expected to conduct themselves professionally and respectfully at all times.
Harassment, discrimination, or any form of inappropriate behavior is strictly prohibited.
Participants must treat all individuals with courtesy and consideration.
2. Open Source Commitment
All code and related materials developed during the hackathon must be published under a permissible open-source license (e.g., MIT, Apache 2.0, GPL).
The chosen license must be clearly indicated in the project's repository.
Projects must be thoroughly documented to facilitate community contributions.
3. Original Work
Projects should primarily consist of original work created during the hackathon timeframe.
Any external libraries or resources used must be properly cited and attributed.
The scope of work completed within the hackathon timeframe must be clearly defined.
4. Technology Usage
There are no restrictions on the technologies used during the hackathon.
5. Project Submission
The deadline for project submissions is June 7th.
All submissions must include:
Proper documentation explaining the project's functionality and usage.
A public code repository hosted on a platform such as GitHub or GitLab, under a permissible open-source license.
At least one video demonstration of the tool or project in action.
6. Eligibility
Teams must consist of six or fewer participants.
There are no restrictions on participant affiliations.
7. Disqualification
Projects may be disqualified for:
Plagiarism or the submission of work that is not original.
Violation of the code of conduct.
Failure to meet the project submission requirements.
Failure to publish the code under an open source license.
8. Liability
Participants acknowledge that they participate in the hackathon at their own risk.
The hackathon organizers shall not be held liable for any damages, losses, or injuries incurred during the event.
Participants are responsible for ensuring their code does not infringe on any existing intellectual property.
9. Prize Disbursement and Invoicing
To facilitate the disbursement of prizes, Bio.XYZ will require winning teams or individuals to submit a valid invoice.
This invoice must include, at a minimum:
The full legal name of the recipient (individual or team representative).
A valid physical address.
Additional information may be requested as needed for tax or legal compliance.
Failure to provide a valid invoice within a reasonable timeframe, as specified by Bio.XYZ, may result in forfeiture of the prize.
All prizes will be paid in the form of $vBIO token which will unlock linearly over the course of a year.
Limitation of Liability Regarding Academic Publications and Data Usage:
Participants acknowledge that a significant portion of academic publications, particularly those published in traditional journals, are subject to copyright restrictions and are not available under open-source or permissible licenses. Participants are solely responsible for ensuring that any data or information used in their hackathon projects is obtained from publicly available sources or under a permissible license that allows for the intended use. Participants are further advised that the use of copyrighted materials without proper authorization may infringe upon the rights of the copyright holders and could result in legal consequences.
Bio.XYZ assumes no liability for any projects developed during the hackathon that utilize data or information that is not publicly available under a permissible license. Participants are solely responsible for ensuring that their projects comply with all applicable copyright laws and licensing agreements. Participants agree to indemnify and hold harmless Bio.XYZ, its organizers, judges, mentors, and affiliates from any and all claims, liabilities, damages, or expenses arising from the use of copyrighted materials or data without proper authorization in their hackathon projects.
Disclaimer: Bio.XYZ recommends that participants consult with legal counsel to ensure compliance with all applicable copyright laws and licensing agreements. This statement is provided for informational purposes only and does not constitute legal advice.
Last updated