• The Hackathon is open to all registered participants.  The roles specifically being sought are developers, designers, technologists, data scientists, and entrepreneur as well as enterprise developers.
• If you are an employee of a corporation, government agency, or an academic institution, you are responsible for ensuring that your participation in the Hackathon complies with any policies your corporation, agency, or institution may have regarding participation in an event of this type. We are not responsible for any disputes arising between you and your employer.

The submission deadline is 4:30pm PT on Tuesday July 12th 2016 to be made to this Devpost hackathon site. 

Late submissions will not be accepted

• Your submission should include:

  • Your App, product or service submission:
    • Title
    • Tagline
    • Description (should be approximately 500 words); 
    • Explanation regarding which TM Forum APIs have been used
    • Explanation and links regarding other platform capabilities used, example: IBM Bluemix, Ericsson Connected Car API, Vancouver Open Data, Telus Live Streaming, Sierra Wireless IoT capability etc
    • 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 6pm on Jul 12th. 
      • 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.