Dates

18th - 19th of June, 2022.

 

Eligibility

Open to college students from Delhi - NCR.

 

Project and Submission Requirements

All submissions shall be subjected to an extensive plagiarism check.

Your project repository must have continuous commits from the start of the project - we encourage committing after every update. Not only will these serve as checkpoints for you to backtrack your project should you need to, it will also be considered for plagiarism checking during project evaluation.

If you are not familiar with Git, reach out to one of the organisers (identifiable with white polo), they will help you with resources to get started.  

Your project must have an open source licence (GPL, MIT, Apache, and Unlicense are accepted, others may be considered on a case by case basis).

 

Plagiarism Policy

Plagiarism is not tolerated, and teams with plagiarized content, including self-plagiarism, will be disqualified. 

Participants are encouraged to submit projects coded only during the duration of the hackathon. 

However, if one decides to use an external source, use their own re-used code in their project, or even re-submit a project that they have already submitted previously to any other hackathon, one is to inform us about such information and to what extent it has been included in the project. 

If the RBH discovers that the project has re-used code that was not revealed in the submission, the participant will get a chance to explain the similarities and differences between the old and new work, in case of discrepancies or invalid submission, the contributions may be immediately disqualified from winning awards. 

Plagiarism will be checked on all students' work submitted. This involves using code comparison tools, plagiarism software, and reviewing the history of git commits, among other things. 

It is acceptable to use and reference others' code as long as any piece of work that is not entirely the students' own is not correctly referenced or acknowledged. 

It is the responsibility of each participant to ensure that any direct or indirect inclusion of the work of others is fully and adequately acknowledged. 

Plagiarism may be unintentional however it will still be treated as an offense. 

Participants are encouraged to seek help from Hackathon mentors or peers on their project work, but no contribution should incorporate code produced by others unless it is expressly acknowledged to them. Hence, if in any doubt, include attribution of all sources, or ask your Hackathon mentor for advice. 

All decisions pertaining to matters of plagiarism will be taken up by the RBH plagiarism committee and the decisions will be final and binding. 

The RBH plagiarism committee reserves the right to investigate the case after being filed using any means they deem appropriate including but not limited to monitoring network logs.

 

Judging Criteria

Criteria: Teams will be evaluated on a 1-100 point scale. Points will be averaged across judges. The pointers detailed under each criterion are for better understanding of the participants.

  • Technicality (0-20 points)
    • How well engineered is the project?
    • Is the coding and logic sound?
    • Did the team think about the user interface (UI) and user experience (UX)? Was the product designed with humans in mind?
  • Innovation (0-20 points)
    • Is this a novel approach / solution to addressing the problem?
    • Has this been done before?
  • Meeting Track Requirements (0-20 points)
    • Is this doing what the track requires?
    • How well does the submission align with the respective tracks’ goals?
  • Presentation (0-10 points)
    • How well does the presentation describe their idea, solution, and tech aspects?
  • Impact (0-30 points)
    • Is it feasible?
    • Does this create maximum impact for many people?
    • Is this solving a real solution?
    • Would this create net good?

Code of Conduct