Using DoraHacks

This platform does not currently meet MLH export requirements, so you will have to manually add the missing fields or do a secondary form as a workaround.

Setting up your DoraHacks hackathon page will help you manage your project submissions, judging, and assigning winners. Please follow this guide on DoraHacks for step by step instructions.

If you decide to use DoraHacks and are applying to be an MLH member event, please ensure the following:

1. Reach out to your Hackathon Community Manager at MLH for help getting DoraHacks set up within the MLH requirements.

2. Similar to Devfolio, DoraHacks has an approval process that your event needs to go through before you can publish it live. Make sure to work ahead of time to be approved so you can customize as needed.

3. You need to create the hackathon as an organization. If you don’t have an organization yet, create one first.

4. As the platform doesn’t support questions other than text type, we require you to use a platform, such as OrganizerHQ or others, that allow you to add MLH mandated registration fields and checkboxes for registrations. DoraHacks has a field where you can enter this registration link, and disable registration on their platform.

1. Please confirm that the submission requirements and rules for your event have been added correctly. https://guide.mlh.io/general-information/judging-and-submissions/rules-for-your-hackathon

2. As of our last check on 10/9, you can now select multiple tracks. We are leaving this documentation here but with a strikethrough for anyone we previously shared this page with. Make sure you understand what the difference between tracks and bounties are on DoraHacks. Once you become a Member Event, we’ll send you more information on the MLH partners that are active at your event.

   1. Tracks: A submitted project can belong to only one of the tracks, e.g software or hardware. Every hackathon initially has a default track, “All BUIDLs”. You can rename it, and you can also add more custom tracks. If Hackers can participate in multiple tracks, you need to make 1 General Track and instead have your tracks listed as bounties.

   2. Bounties: Bounties are the opt-in prize categories.

      1. ‘Necessity of bounty applications’ is for you to choose whether it’s mandatory for teams to select a category prize to make a successful submission.

      2. ‘Maximum number of bounties each BUIDL can apply for’ is the maximum prize categories that a team can opt-in to. You should ideally leave this field empty to let teams opt-in to as many categories as they wish to.

      3. Your organization is a default sponsor and is considered to have a prize category. If you don’t have one, you should list your overall prizes.

      4. Add each MLH partner category prize as a new bounty.

3. Add custom submission questions from Overview -> BUIDL submission tab.

   1. Links or other information relevant to MLH category prizes they opt-in to. Example - domain name that the team redeemed if a domain partner was active at your event.

   2. Share feedback about any technology you interacted with at this hackathon. Remember to mention what tech you're reviewing (e.g. MongoDB, GitHub, Auth0, etc.).

   3. Schools of all the team members (used in our Season competition).

      
4. DoraHacks project exports currently don’t include information such as project demo links and details of team members so make sure to practice exporting data from DoraHacks for judging. The platform does not currently meet MLH export requirements, so you will have to manually add the missing fields or do a secondary form as a workaround.

Updates as of 12/2

Here are some things our team noticed recently at an event using DoraHacks that your organizing team would probably benefit from knowing. Please keep in mind we also talked with the DoraHacks team, so some of this may change in the future.

• Only 10 users can be admin on a team account at once.

  • Try getting a team email set up for your help desk so that anyone on your team can help hackers or sponsors as needed.

• Hackers cannot edit required questions after an initial submission is made. This is very different from other platforms, which more of your hackers are likely to be familiar with. We recommend adding a first question to state that they understand the following set of questions cannot be edited after initial submission.

  • This includes the fields for each hacker's contact information that you need to have to meet MLH requirements, as if this is a required question, then hackers cannot edit it after their initial submission.

  • If you add a new question after a project/BUIDL is submitted, the new question will only appear on the new projects/BUIDLs (not on any who try to edit their application)

  • The default “GitHub url” question is forced set to optional, so you have to add an additional duplicate question set as required to force GitHub submissions.

• To add a sponsor/opt-in prize, you have to add the company under the bounties tab. After you have added the company, you have to go to the winner assignment tab and add the prizes under each company

  • You cannot edit/delete prizes after the hackathon period has started. The only fix is to move the hackathon start time back.

    • This is to prevent abuse/lowering of prize amount. Reach out to your DoraHacks representative via telegram/email/discord as needed and they can update on the backend.

    • This means you should aim to have all sponsor prizes ready before your event start. If you wish to announce "surprise" challenges during opening ceremony, make sure someone on your team is ready to update and you push back your start time as needed to make sure they are accurate.

• You cannot sort all submissions by the opt-in prize with the current export settings. To sort/export by opt-in prize, you have to go to the bounties tab and click on the sponsor/challenge. Schedule extra time to notify any sponsors or side challenges which teams they need to go judge.

• When exporting submissions, you have to scroll and click “view more” until all projects are displayed, then click the select all checkbox, then export if you want to export all of the projects. If you do not click all of the view more buttons, you will not get a full export

  • You can only export: Project id, project name, project url, project last updated time, submission time, contact email, track, bounties (opt-ins), custom questions (a new column for any custom question added), and review status

• To export user information, you have to follow the same process as exporting submissions, but under the hacker tab. The only fields that are exportable are: hacker nickname, handle, url, GitHub, registration time, skills, interests, and onboarding status. Note: THIS DOES NOT CONTAIN ANY CONTACT INFORMATION