Rules for the {open}:hack TM Forum Action Week Vancouver 25th to 26th September  

Overview

• The Hackathon is designed to help designers & developers to rapidly create new innovative solutions using an open ecosystem platform and open API suite.  
• The entire event is designed as a learning and innovation platform.  We pride ourselves on the quality expertise provided both as training and 1:1 support. 
• The Open API suite has been collaboratively created with contributions from across industry and these APIs are currently adopted by many communications service providers around the globe.
• The ecosystem platform exposes capabilities that are explicitly selected to help design solutions towards the challenges outlined for the hack. 
• As an innovator at the hack you can mash your product with many of these services to create new innovative solutions.  
• The fresh code rule applies to code created at the event, any integration code where new services are mashed together.  You need to be explicit about whats fresh and whats not in your submission. 
• The open hack also provides open data which can be used to enable greater context based decision making and therefore more efficient applications. 
• In summary, the open hack = open data + open platform + open APIs, as the key ingredients provided to stimulate innovation towards the challenges posed, and of course lots of good food and fun also!
• We are passionate about the challenges outlined for the hack.  
• The hackathon is designed to gain feedback on important new APIs such as the Privacy API and onboarding APIs.  The privacy API is designed taking into account new EU regulations regarding end user privacy rights. 
• TM Forum as an organisation is committed to the collaborative development of common open APIs for ease of enabling communications across ecosystems. 
• The {open}:hack training will take place between 2:00pm - 5:00pm Sunday Sepember 24th, followed by Hacking from Monday 9:00am - 8pm and Tues 9:00am - 2:00pm.  Following this pitches and awards will be announced with all activities ending by 6:30pm on Tuesday.  . 
• Sponsor and Administrator: The Hackathon is sponsored and administered by TM Forum. 4 Century Drive, Parsippany, NJ, 07054 USA.  The event is partnered with Telus & Sierra Wireless. 
• These rules were last updated on September 11th 2017.

Eligibility

• The Hackathon is open to all registered participants.  
• The roles specifically being sought are software developer from service providers, solution vendors and SMEs, IoT & Smart City Application Developers, Architects & product designers, Network Engineers & architects, startups, incubators, university students, UX developers and Business Analysts. 
• 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. 

Style

• TM Forum’s open hack in Vancouver September 25th-26th is a competitive hackathon.  While there will be significant learning and networking opportunities, there are also prizes.  
• The key style is guiding and supporting innovators, both enterprise and individual, to test out the art of the possible of their applications in an ecosystem environment where capabilities can be mashed together from different sources.
• TM Forum as a collaborative industry organisation will run this event in a highly collaborative and inclusive style where all participants are respected.
• The event will operate within the bylaws of TM Forum.
• Lively, interactive and fun
• Engaging with diverse groups of people
• Opportunities to network with senior technical influencers
• Fantastic learning opportunity from participants and expert mentors
• Excellent environment to incubate and test a new business or product ideas
• Open to all and free to participate
• Superb food and drinks provided
• The event will not run overnight: Outline schedule: Day 1 Sunday September 24th: Training 2:00pm - 5:00pm, followed by drinks reception, Hacking on Monday 9:00am - 8pm and Tues 9:00am - 2:00pm.  Following this pitches and awards will be announced with all activities ending by 6:30pm on Tuesday.   

Registration and Check-in

• Please register at https://actionweek.tmforum.org/open-hack/
• Doors open 09:00 Monday 25th September. Please arrive at the Hackathon venue between between 08:30 - 09:00 pm on Monday September 25th.   
• 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. 

Submission 

Please submit your team’s Entry to the location provided on DevPost by 12pm Tuesday September 26th. Your submission should include:

• 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 26th 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-2107.devpost.com/

• Presentation template

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. 
  
  

Allowed Technologies:

• TM Forum and Sponsor Platforms and APIs
• Products or applications brought to the hackathon by participants for sharing and leveraging in the open hack. 
• Other Technologies: You are also able to use source code, sample code, libraries, SDKs, and APIs as long as these technologies are publicly discoverable and available for public use in developing applications.

Reimbursement:

• 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 Monday September 25th.  
• 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 25th Sepetember. 

Forms required to be completed: 

Judging

• 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 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. 

Prizes

• The prizes available are as per the website prior to the event

How Your Entry May be Used

• You do not transfer ownership of your Entry (or any part of it). However, by submitting an Entry, you grant us an irrevocable, royalty-free, worldwide rights and license to: (a) use, review, assess, test, and otherwise analyze your Entry and all its content in connection with the Hackathon; and (b) feature your Entry and all its content for promotional purposes (including, but not limited to, in advertisements, press releases, presentations, and trade shows) in all media, now known or later developed. You also agree to sign any necessary documentation that may be required for us and our designees to make use of the rights you granted.
• You acknowledge that we, other entrants or others may have developed or commissioned materials similar or identical to your Entry, or may develop something similar in the future, and you waive any claims you may have resulting from any similarities to your Entry.
• Please note that after the Hackathon, you and/or your Entry may be publicized in advertisements related to the Hackathon. These advertisements may be distributed online and posted on our websites or third-party websites. 
• While we reserve the rights set forth above, we are not obligated to use your Entry for any purpose, even if it has been selected as a winning Entry. 

Privacy and Publicity

• Information you submit to us when you participate in the Hackathon will be treated in accordance with our Privacy Policy. In addition, when you submit information on a website run by a third party in connection with this Hackathon, your information may be used by that third party in accordance with its privacy policy. 
• You may be filmed or photographed while you are participating in the Hackathon. Except where prohibited, by participating in the Hackathon, you agree that we may use your name, likeness, photographs, audio-visual footage, comments, and any other record of your participation in the Hackathon.