Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Please register at https://actionweek.tmforum.org/open-hack/
  • Doors open 12 noon Sunday May 14th09:00 Monday 25th September. Please arrive at the Hackathon venue between between 12noon 08:30 - 209:00pm 00 pm on Sunday Monday September 24th25th.   
  • A minimum of two and maximum of five eligible individuals will be permitted per team. Your entire team should register as team on DevPost by 1:00pm Monday September 25th & submit team name, hack idea & design. 
  • You will be issued a badge on site that you must wear visibly at the venue and required for re-entry. 

...

  • Your App, product or service submission:
    • Title
    • Tagline
    • Description (should be approximately 500 words); 
    • Explanation regarding which APIs you have used which were exposed at the hackathon. 
    • Explanation and links regarding other platform capabilities used 
    • Feedback regarding use of the APIs and platform from the event
    • Screenshots or images, with a maximum size of 5MB. Format should be JPG, PNG or GIF
    • Recommended: A link to a YouTube video of your submission
    • Git Commits:
      • Each team is suggested to commit their new code created during the {open}:hack to a public or private repository on GitHub by 2pm on Mar 16th26th September
      • The Git Commit should include all source code of your app including CSS and supporting media
      • If, for whatever reason, your team is unable to submit via Git, then the source should be zipped up and submitted via e-mail within the deadlines to [email protected]
    • It is not obligatory to submit the full code at the end of the hackathon. It is however, highly recommended to submit the new code created at the hackathon to the open source community and in particular any extensions to the Forum Open APIs which will be used as feedback to the wider industry. 
    • Clearly labeling where the fresh code rule applied and what applications and capabilities existed prior to the hack. 

  • By making the submission, you represent and warrant that:
  • Any code you supply for your entry is yours or your teams to choose to submit and is being submitted in alignment with TM Forum's IPR agreement. 
  • Devpost  https://open-hack-vancouver-20172107.devpost.com  /

  • Presentation template

View file
nameHack pitchback Vancouver 17.pptx
height250

...

 

General App Requirements

  • You should create an app or product using combination's of TM Forum Open APIs, Telus APIs, Sierra Wireless APIs and other digital assets exposed by the partnering sponsors.
  • You are encouraged to bring any product or service you may already have.  
  • Startups and enterprise developers are encouraged to bring their products and demonstrate how they can be used to create new services in an ecosystem environment.  They are not expected to submit their product as part of the submission. You will retain all your IPR on your product. 

...

  • TM Forum recognizes that costs are incurred by participants in attending the event
  • Therefore there is a reimbursement offer of $100 for students and startups (less than 2 years) which can be applied for by the first 50 eligible participants who arrive on site on Sunday Monday September 24th25th.  
  • The following requirements are needed to gain reimbursement:
    • Eligible participants must be present for the whole of the hackathon to receive travel voucher
    • $100 USD travel voucher can only be given via wire transfer where all forms are completed
    • Hacker is responsible for any bank fees from his/her bank when accepting wire transfer
    • Wire transfers will be done on Thursday, May 18 and will take a few days to be processed between the banks. 
    • The W8Ben, Invoice & Bank Details forms need to be completed and brought to the venue on May 14th25th Sepetember

Forms required to be completed: 

...

  • Judges will be listed on the Open Hack website prior to the event.  
  • Each financial sponsor will have the opportunity to nominate a judge for the hack. 
  • TM Forum will provide a judge and will chair the judging process. 
  • The full audience for the pitches will be allowed to participate in the voting process during the pitches.
  • The chair of the judging process will have a deciding vote in case of a dispute or tie.
  • Judges will base their decision on the pitch back, materials posted in DevPost and will consider feedback from the general audience. 
  • Judges are observing for:
    • Best use of APIs and technology exposed in the Hackathon 
      • Minimum required to qualify is one Forum Open API 
    • Design: Best overall techology technology design, aka platform based solution, minimum new code developed, minimum clicks
    • Innovation & Creativity: How disruptive is this solution / idea?
    • Impact and value to industry or society including feedback on use of the APIs, extensions to the APIs etc. 
    • Completeness: How ready is this to deploy? 
  • Be clear on where you have applied the fresh code rule!
  • Note the best teams are usually made up of different types of people including developers, UX developers, backend developers, product designers, business analysts etc. 

...