Atlassian's Codegeist is back in a big way for 2020. This year, we’re looking for creative cloud applications in two tracks:
BUILT WITH CONNECT
Create production-ready applications and integrations for your favorite Atlassian Cloud tools: Jira, Confluence, Bitbucket and more. Think about solutions that would help your team work smarter or pick a topic of your own that inspires you.
Plus, use the Trello customization platform to build Trello Power-Ups and compete for the corresponding bonus prizes!
BUILT WITH FORGE
Atlassian's new cloud app development platform, Forge, allows you to build trusted, scalable apps in as little as a few hours with Atlassian-hosted compute and storage, eliminating the need to manage infrastructure or security. Forge is still in beta so join the waitlist using referral “Codegeist” to get access and start building.
Bonus: The top 100 eligible Forge apps will win $500!
We can’t wait to see what you build!
Codegeist 2020 Official Rules – (the “Official Rules”)
NO PURCHASE OR PAYMENT NECESSARY. A PURCHASE OR PAYMENT OF ANY KIND WILL NOT INCREASE YOUR CHANCES OF WINNING.
Hackathon Name: Codegeist 2020 (the “Hackathon”)
Hackathon Website: https://codegeist.devpost.com (the “Hackathon Website”)
1. POSTER & ADMINISTRATOR
Poster (the “Poster” or “Sponsor”): Atlassian Pty Ltd - Level 6, 341 George Street, Sydney, NSW, 2000, Australia
The Poster is the Sponsor and entity responsible for the Hackathon.
Administrator (the “Administrator”): Devpost, Inc. (“Devpost”), 222 Broadway, 19th Floor, New York, NY 10038.
2. DATES AND TIMING
Hackathon Submission Period: May 19, 2020 (10:00am Eastern Time) – July 13, 2020 (5:00pm Eastern Time) (the “Hackathon Submission Period”)
Judging Period: July 17, 2020 (10:00am Eastern Time) – July 23, 2020 (5:00pm Eastern Time) (the “Judging Period”)
Winners Announced: On or around July 29, 2020 (2:00pm Eastern Time)
The Administrator will be the official timekeeper for the Hackathon.
3. ELIGIBILITY
A. The Hackathon IS open to:
The above are collectively, “Makers”.
An Eligible Individual may join more than one Team, or Organization and an Eligible Individual who is part of a Team or Organization may also enter the Hackathon on an individual basis.
If a Team or Organization is entering the Hackathon, they must appoint and authorize one individual (the “Representative”) to represent, act, and enter a Submission, on their behalf. The Representative must meet the eligibility requirements above. By entering a Submission on the Site on behalf of a Team or Organization you represent and warrant that you are the Representative authorized to act on behalf of your Team or Organization.
B. The Hackathon IS NOT open to:
*Agents include individuals or organizations that in creating a Submission to the Hackathon, are acting on behalf of, and at the direction of, an Organization involved with the design, production, paid promotion, execution or distribution of the Hackathon through a contractual or similar relationship.
**The members of an individual’s immediate family include the individual’s spouse, children and stepchildren, parents and stepparents, and siblings and stepsiblings. The members of an individual’s household include any other person that shares the same residence as the individual for at least three (3) months out of the year.
***An affiliate is: (a) an organization that is under common control, sharing a common majority or controlling owner, or common management; or (b) an organization that has a substantial ownership in, or is substantially owned by the other organization.
Additional Prize specific eligibility requirements are stated below in Section 7 (Prizes).
4. SUBMISSION REQUIREMENTS
Makers must do the following to participate in the Hackathon:
A. Language Requirements
All Submission materials must be in English or, if not in English, the Maker must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted.
B. Application Requirements
(i) What to Create: Makers must build innovative cloud apps on Atlassian in one of the two categories:
(each an “Application”).
(ii) Functionality: The Application must be capable of being successfully installed and running consistently on the platform for which it is intended, and must function as depicted in the video and/or expressed in the text description.
(iii) Platforms: A submitted Application must run on at least one of the following:
(iv) New & Existing: Applications must be either newly created by the Maker or, if the Application existed prior to the Hackathon Submission Period, must have been significantly updated after the start of the Hackathon Submission Period.
(v) Testing: The Maker must make the Application available free of charge and without any restriction, for testing, evaluation and use by the Poster, Administrator and judges during the Hackathon and until the Judging Period ends.
If the Application includes software that runs on proprietary or third party hardware that is not widely available to the public, including software running on devices or wearable technology other than smartphones, tablets, or desktop computers, the Sponsor and/or Administrator reserve the right, at their sole discretion, to require the Maker to provide physical access to the Application hardware upon request.
For Applications running on widely available smartphones, tablets, or desktop computers, Makers may make their Application available using one of the following methods:
a. Android Applications: Upload an .apk file on the Enter a Submission form or provide a link for downloading the Application in the “Testing Instructions” field on the Enter a Submission form.
b. iOS Applications:
Administrator UDID:
iPhone 8 (iOS 13.3.1) a2d30c918b5b7184172fe7c000caa2241d9cb710
c. Web/Mobile Web: Provide a link for accessing your Application on the “Testing Instructions” field on the Enter a Submission form.
(vi) Public Distribution: The Maker may make the Application available to the public via a website or online store, but is not required to do so.
(vii) Multiple Submissions: A Maker may submit more than one Submission, however, each Submission must be unique and substantially different from each of the Maker’s other Submissions, as determined by the Poster and/or the Administrator.
(viii) SDKs, APIs, & Data: Applications may integrate SDKs, APIs and data, provided the Maker is authorized to use them.
(ix) Intellectual Property: Your Submission must: (a) be your (or your Team or Organization’s) original work product; (b) be solely owned by you, your Team, or your Organization with no other person or entity having any right or interest in it; and (c) not violate the intellectual property rights or other rights including but not limited to copyright, trademark, patent, contract, and/or privacy rights, of any other person or entity. A Maker may contract with a third party for technical assistance to create the Submission provided the Submission components are solely the Maker’s work product and the result of the Maker’s ideas and creativity, and the Maker owns all rights to them. A Maker may submit a Submission that includes the use of open source software or hardware, provided the Maker complies with applicable open source licenses and, as part of the Submission, creates software that enhances and builds upon the features and functionality included in the underlying open source product. By entering the Hackathon you represent, warrant, and agree that your Submission meets these requirements.
(x) Financial or Preferential Support: An Application must not have been developed, or derived from an Application developed, with financial or preferential support from the Poster or Administrator. Such Applications include, but are not limited to, those that received funding or investment for their development, were developed under contract, or received a commercial license, from the Poster or Administrator any time prior to the end of Hackathon Submission Period. The Poster, at its sole discretion, may disqualify an Application, if awarding a prize to the Application would create a real or apparent conflict of interest.
C. Text Description, Image, and Video Requirements
(i) Text Description: The text description should explain the features and functionality of your Application.
(ii) Images: The image(s) should be photographs or screenshots of your working Application.
(iii) Video: The required video portion of the Submission:
a. should be less than three (3) minutes;
b. must include footage that clearly explains the Application’s features and functionality through a comprehensive demo of the software;
c. must be uploaded to YouTube, Vimeo, Facebook Video, or Youku, and a link to the video must be provided on the submission form on the Hackathon Website; and
d. must not include third party trademarks, or copyrighted music or other material unless the Maker has permission to use such material.
D. Submission Modifications
i. Draft Submissions: Prior to the end of the Submission Period, you may save draft versions of your Submission on Devpost to your portfolio before submitting the Submission materials to the Competition for evaluation. Once the Submission Period has ended, you may not make any changes or alterations to your Submission, but you may continue to update the project in your Devpost portfolio.
ii. Modifications after the Submission Period. The Poster may permit you to modify part of your Submission after the Submission Period for the purpose of removing material that potentially infringes a third party mark or right, discloses personally identifiable information, or is otherwise inappropriate. The modified Submission must remain substantively the same as the original Submission with the only modification being what the Poster permits.
5. SUBMISSION RIGHTS
A. Maker Rights: Subject to the licenses described below, any applicable intellectual property rights to a Submission will remain with the Maker.
B. Poster Rights: By entering the Hackathon, you grant to the Poster, Administrator, and any other third parties acting on the Poster’s behalf, a royalty-free, non-exclusive, worldwide perpetual license to display publicly and use for promotional purposes the Submission, in perpetuity. This license includes, but is not limited to, posting or linking to the Submission on Poster’s, Administrator’s, and partners’ websites and applications, including the Hackathon Website, and display and promotion of the Submission in any other media, worldwide.
C. Submission Display: The following Submission components may be displayed to the public: name, description, images, video URL, website URL, team members, the Submission category and platform, and submitter type. Other Submission materials may be viewed by the Poster, Administrator, and Judges for screening and evaluation.
D. Makers represent and warrant that the Poster, Administrator, and Hackathon partners are free to use Makers’ Submission in the manner described above, as provided or as modified by the Administrator, without obtaining permission or license from any third party and without any compensation to Makers.
6. JUDGING
A. Judges: Eligible Submissions will be evaluated by a panel of judges selected by the Poster (the “Judges”). Judges may be employees of the Poster or external, may or may not be listed individually on the Hackathon Website, and may change before or during the Judging Period. Judging may take place in one or more rounds with one or more panels of Judges, at the discretion of the Poster.
B. Criteria: The Judges will score eligible Submissions using the following equally weighted criteria (the “Judging Criteria”):
(i) Quality of Idea (Includes creativity and originality);
(ii) Implementation of Idea (Includes how well the idea was executed by the developer); and
(iii) Potential Impact (Includes the extent to which the solution can help the most Atlassian users)
The Maker(s) that are eligible for a Prize, and whose Submissions earn the highest overall scores based on the applicable Judging Criteria, will become potential winners of that Category Prize.
C. Submission Review: JUDGES ARE NOT REQUIRED TO TEST THE APPLICATION AND MAY CHOOSE TO JUDGE BASED SOLELY ON THE TEXT DESCRIPTION, IMAGES AND VIDEO PROVIDED IN THE SUBMISSION.
D. Tie Breaker: For each Prize listed in Section 7 below, if two or more Submissions are tied, the tied Submission with the highest score in the first applicable criterion listed above will be considered the higher scoring Submission. In the event any ties remain, this process will be repeated, as needed, by comparing the tied Submissions’ scores on the next applicable criterion. If two or more Submissions are tied on all applicable criteria, the panel of Judges will vote on the tied Submissions.
7. PRIZES
|
Winner |
Prize |
Eligible Makers |
Applicable Judging Criteria |
|
Built with Connect Category Prizes |
|||
|
Grand Prize |
|
All Eligible Submissions in the Connect category |
i,ii,iii |
|
Second Place |
|
All Eligible Submissions in the Connect category |
i,ii,iii |
|
Third Place |
|
All Eligible Submissions in the Connect category |
i,ii,iii |
|
Fourth Place |
|
All Eligible Submissions in the Connect category |
i,ii,iii |
|
Fifth Place |
|
All Eligible Submissions in the Connect category |
i,ii,iii |
|
Honorable Mentions (5) |
|
All Eligible Submissions in the Connect category |
i,ii,iii |
|
Built with Forge Category Prizes |
|||
|
Grand Prize |
|
All Eligible Submissions in the Forge category |
i,ii,iii |
|
Second Place |
|
All Eligible Submissions in the Forge category |
i,ii,iii |
|
Third Place |
|
All Eligible Submissions in the Forge category |
i,ii,iii |
|
Honorable Mentions (5) |
|
All Eligible Submissions in the Forge category |
i,ii,iii |
|
Top 100 Forge Apps (100) |
|
All Eligible Submissions in the Forge category |
i,ii,iii |
|
Bonus Prizes (Connect & Forge)* |
|||
|
Best App for Remote Working |
|
All Eligible Submissions |
i,ii,iii |
|
Best App for Remote DevOps |
|
All Eligible Submissions |
i,ii,iii |
|
Best Open Source Forge App |
|
All Eligible Forge Submissions that have been made open source before the deadline |
i,ii,iii |
|
Best Trello Power- Up |
|
All Eligible Trello Power Up Submissions |
i,ii,iii |
|
Best Jira App |
|
All Eligible Jira App Submissions |
i,ii,iii |
|
Participation Prizes (Connect & Forge) |
|||
|
Participation Prize |
|
All Eligible Makers who enter an Eligible Submission (maximum quantity 500) |
N/A |
* For clarity, the total number of Bonus Prizes awarded will be five (5)
IMPORTANT NOTES ON PRIZE ELIGIBILITY:
8. VERIFICATION OF POTENTIAL WINNERS
A. Verification Requirement: THE AWARD OF A PRIZE TO A POTENTIAL WINNER IS SUBJECT TO VERIFICATION OF THE IDENTITY, QUALIFICATIONS AND ROLE OF THE POTENTIAL WINNER IN THE CREATION OF THE SUBMISSION. The final decision to designate a winner shall be made by the Poster and/or Administrator.
B. Required Forms: Potential winners will be notified using the email address associated with the Devpost account used to enter the Submission (the submitter is the “Representative” in the case of a Team or Organization). In order to receive a Prize, the potential winner (including all participating team members in the case of a Team or Organization) will be required to sign and return to the Poster or Administrator, affidavit(s) of eligibility (or a similar verification document) and liability/publicity release(s), and any applicable tax forms (“Required Forms”).
Deadline for Returning Required Forms: ten (10) business days after the Required Forms are sent.
C. Disqualification: The Poster and/or Administrator may deem a potential winner (or participating team members) ineligible to win if:
(i) the potential winner’s Representative or any participating member does not respond to multiple emails or fails to sign and return the Required Forms by the deadline listed above, or responds and rejects the Prize;
(ii) the Prize or Prize notification is returned as undeliverable; or
(iii) the Submission or the potential winner, or any member of a potential winner’s Team or Organization, is disqualified for any other reason.
In the event of a disqualification, the Poster and/or Administrator may award the applicable Prize to an alternate potential winner.
9. PRIZE DISTRIBUTION
A. Substitutions & Changes: The Poster has the right to make a Prize substitution of equivalent or greater value. The Poster will not award a Prize if there are no eligible Submissions entered in the Hackathon, or if there are no eligible Makers or Submissions for a specific Prize.
B. Prize Delivery: Prizes will be payable to the Maker, if an individual, to the Maker’s Representative, if a Team, or to the Organization, if the Maker is an Organization. It will be the responsibility of the winning Maker’s Representative to allocate the prize among their Team or Organization’s participating members, as the Representative deems appropriate. Prizes are payable via any means of the Sponsor or Administrator's choosing, whether electronic or not, and are payable only after receipt and verification of the Winner Documents and any other required forms. A winning Maker may be required to provide a mailing address, bank information, and/or create an account with an electronic payment provider of the Sponsor or Administrator’s choosing in order to receive payment.
Failure to provide correct information on the Required Forms, or other correct information required for the delivery of a Prize, may result in delayed Prize delivery, disqualification or the Maker, or forfeiture of a Prize.
Participation Prize Delivery: Within sixty (60) days of submitting an Eligible Submission, a Maker will receive an email containing a promotional code which may be used to collect Atlassian swag. Sponsor or Administrator may choose at their own discretion to substitute any awards via alternate means of the same value. For clarity, such Participation Prizes will only be given to eligible Makers, and no maker shall receive more than one (1) Participation Prize.
C. Prize Delivery Timeframe: Within sixty (60) days of the Poster or Administrator’s receipt of the Required Forms
D. Fees & Taxes: Winners (and in the case of Team or Organization, all participating members) are responsible for any fees associated with receiving or using a prize, including but not limited to, wiring fees. Winners (and in the case of Team or Organization, all participating members) are responsible for reporting and paying all applicable taxes in their jurisdiction of residence (federal, state/provincial/territorial and local). Winners may be required to provide certain information to facilitate receipt of the award, including completing and submitting any tax or other forms necessary for compliance with applicable withholding and reporting requirements. United States residents are required to provide a completed form W-9 and residents of other countries are required to provide a completed W-8BEN form. Winners are also responsible for complying with foreign exchange and banking regulations in their respective jurisdictions and reporting the receipt of the Prize to relevant government departments/agencies, if necessary. THE POSTER, ADMINISTRATOR, AND/OR PRIZE PROVIDER RESERVE THE RIGHT TO WITHHOLD A PORTION OF THE PRIZE AMOUNT TO COMPLY WITH THE TAX LAWS OF THE UNITED STATES OR OTHER POSTER JURISDICTION, OR THOSE OF A WINNER’S JURISDICTION.
10. ENTRY CONDITIONS AND RELEASE
A. By entering the Hackathon, you (and, if you are entering on behalf of a Team or Organization each participating members) agree(s) to the following:
(i) The relationship between you, the Maker, and the Poster and Administrator, is not a confidential, fiduciary, or other special relationship.
(ii) You will be bound by and comply with these Official Rules and the decisions of the Poster, Administrator, and/or the Hackathon Judges which are binding and final in all matters relating to the Hackathon.
(iii) You release, indemnify, defend and hold harmless the Poster, Administrator, Promotion Entities, and their respective parent, subsidiary, and affiliated companies, the Prize suppliers and any other organizations responsible for sponsoring, fulfilling, administering, advertising or promoting the Hackathon, and all of their respective past and present officers, directors, employees, agents and representatives (hereafter the “Released Parties”) from and against any and all claims, expenses, and liabilities (including reasonable attorneys’ fees), including but not limited to negligence and damages of any kind to persons and property, defamation, slander, libel, violation of right of publicity, infringement of trademark, copyright or other intellectual property rights, property damage, or death or personal injury arising out of or relating to a Maker’s entry, creation of Submission or entry of a Submission, participation in the Hackathon, acceptance or use or misuse of the Prize (including any travel or activity related thereto) and/or the broadcast, transmission, performance, exploitation or use of the Submission as authorized or licensed by these Official Rules.
B. Without limiting the foregoing, the Released Parties shall have no liability in connection with:
(i) any incorrect or inaccurate information, whether caused by the Poster or Administrator’s electronic or printing error, or by any of the equipment or programming associated with or utilized in the Hackathon;
(ii) technical failures of any kind, including, but not limited to malfunctions, interruptions, or disconnections in phone lines, internet connectivity or electronic transmission errors, or network hardware or software or failure of the Hackathon Website;
(iii) unauthorized human intervention in any part of the entry process or the Hackathon;
(iv) technical or human error which may occur in the administration of the Hackathon or the processing of Submissions; or
(v) any injury or damage to persons or property which may be caused, directly or indirectly, in whole or in part, from the Maker’s participation in the Hackathon or receipt or use or misuse of any Prize.
The Released Parties are not responsible for incomplete, late, misdirected, damaged, lost, illegible, or incomprehensible Submissions or for address or email address changes of the Makers. Proof of sending or submitting will not be deemed to be proof of receipt by the Poster or Administrator.
If for any reason any Maker’s Submission is determined to have not been received or been erroneously deleted, lost, or otherwise destroyed or corrupted, the Maker’s sole remedy is to request the opportunity to resubmit its Submission. Such request must be made promptly after the Maker knows or should have known there was a problem, and will be determined at the sole discretion of the Poster.
16. CONTACT
If you have any questions or comments, or wish to send us any notice regarding this Hackathon, please email us at Support@Devpost.com.
Main Requirement: Build innovative cloud apps on Atlassian in one of the two categories:
Submit the following materials:
Read the Complete Guideline on Devpost Website Via https://codegeist.devpost.com/
Leave a Comment