Skip to content

Latest commit

 

History

History
49 lines (30 loc) · 1.94 KB

SUBMISSION_FLOW.md

File metadata and controls

49 lines (30 loc) · 1.94 KB

Submission Flow & Demo

We will follow similar rules done by status.im global hackathon.

You can watch this YouTube video for the walkthrough

Step 1: Team registration (by Saturday noon).

Once you decide the team, please submit an issue describing the followings

  • Team name:
  • Team members (assign yourself to the issue):
  • Team leader:
  • What problem are you trying to solve?:
  • Why do you think Blockchain/SmartContract may be the right approach?:
  • API/DATA/Gadget you are thinking about using:
  • What area do you need help on?:

It is understandable that the idea will change througout the hackathon. This is more for us to understand what area you are working on and if mentors can help progressing your ideas.

Step2: Submission registration (by Sunday noon)

Please make the Pull Request with the following details and add @makoto as an approver

  • Github Issue ID:
  • Project name:
  • Project code repo URL:

Step3: Final submission (by 2pm)

When the deadline reaches, we will clone your repo into our org. Please follow the example README file

Step4: Tech cross review (by Sunday 2pm ~ 3pm)

While your team is finalising your pitch slide, I encourage some of your technical members to look into other team's code. If you noticed that any given project has no code or some suspicious code (eg: copy&past from somewhere), please comment on the PR, so that judges ,mentors, and organising members will take further look prior to the demo.

Step5: Pitch (3pm)

  • Main sponsors will have a short presentation (max 2min)
  • Each team have 5 min to pitch with following 2 min of Q&A from judges.

Setp6: Judging

After all participating team ends their pitches, the judges go to different room to decide winners. While judging,

  • Any sponsor/mentor/organisers teams who did the hack will present their result.

Step7 (5pm): Winners announced!