Advertisement
Guest User

Untitled

a guest
Oct 17th, 2016
230
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 16.21 KB | None | 0 0
  1. The Accountant CodinGame Hackathon rules
  2.  
  3. Preamble
  4.  
  5.  
  6. The Accountant CodinGame Hackathon (the "Hackathon") is an online programming competition ("Contest"), free and accessible to all software developers / programmers from all over the world. The Hackathon is organized in promotion of the Warner Bros. motion picture The Accountant. The Hackathon consists in developing a computer program to solve a programming game in a limited time, and optimize it in order to climb in the rankings. Participants (the "Participants") compete for fun and to try to win prizes.
  7.  
  8. Article 1: Organization of the Hackathon
  9.  
  10.  
  11. CodinGame ("Organizer"), a simplified joint stock company with a capital of 15 400 Euros, registered with the Trade and Companies Register of Montpellier (France) under the number 75053861300019, whose headquarters are located in Cap Omega, Rond Point Benjamin Franklin CS 39521 - 34960 Montpellier Cedex 2, France, organizes the Hackathon.
  12.  
  13. The Hackathon will take place online on the Site www.codingame.com, from Saturday, October 1st 2016, at 12:00pm EST to Sunday, October 16th 2016, at 2:00pm EST.
  14.  
  15. The Hackathon is anonymous for all Participants.
  16.  
  17. Article 2: Conditions for participating in the Hackathon
  18.  
  19.  
  20. Detailed information on the Hackathon and how to participate will be found on the "Site": www.codingame.com/the-accountant
  21.  
  22. The Hackathon is open to any individual over 18 years old, with an internet connection and a valid email address, regardless of their nationality, and without any specific educational or professional requirements. Residents of any country to or on which the United States has embargoed goods or imposed targeted sanctions (including, without limitation, North Korea, Iran and Syria) are not eligible to enter. Employees, officers, directors, members, managers, agents, and representatives of Organizer and Warner Bros. Entertainment Inc. ("Warner Bros.") and each of their respective corporate partners, parent companies, divisions, subsidiaries, affiliates, assigns, and successors in interest and the immediate families (defined as any spouse, partner, parent, legal guardian, sibling, child, grandparent, or grandchild, regardless of where they reside) and members of the same household (whether legally related or not) of each such person, are ineligible to participate or win a prize in this Contest.
  23.  
  24.  
  25. CodinGame reserves the right to ask any Participant to justify these conditions. Any Participant who doesn't meet these conditions or who refuses to provide proof shall be excluded from the Hackathon and shall not benefit from the advantages if successful in the Hackathon.
  26.  
  27. By participating in the Hackathon, all Participants shall refrain from cheating, faking, thieving identity or any other technique to change the result of the Hackathon. They shall be required to participate and perform tests alone without the help of a third party or any technical assistance.
  28.  
  29. Participation in the Hackathon is free of charge for Participants and doesn't imply any purchase obligation.
  30.  
  31. Participation is strictly personal; each Participant may only register once for the Hackathon and may not participate in any way on behalf of third parties.
  32. The Participants irrevocably agree that all solutions that they submit to the CodinGame platform during the Hackathon may be published under GPL v3 license, and they may be made ​​available to anyone through CodinGame at the end of the Hackathon.
  33.  
  34. Participation in the Hackathon implies acceptance of these in their entirety. Failure to comply with these shall result in the participation being considered null and void.
  35.  
  36. Participants also state that they submit to the decisions of CodinGame for any case not provided for in these or any contentious situation.
  37.  
  38. Article 3: Registering for the Hackathon
  39.  
  40.  
  41. To participate in the Hackathon, Participants simply need to connect to the Site, click on the button "Register", and sign in by filling in the following fields:
  42. email
  43. password
  44. nickname
  45. country
  46.  
  47. Once the form is completed and validated, Participants will receive an email acknowledging receipt of their registration at the email address entered. Participants will be able to change this information by clicking on a link in the received email.
  48.  
  49. To become familiar with the development platform used for the Hackathon, Participants can access a training page on the Site by clicking on the following link: TRAINING.
  50.  
  51. Article 4: Practical programming test
  52.  
  53.  
  54. At the date and time the Hackathon starts, registered Participants will receive a link at the email address indicated when registering to the Hackathon, through which they will be able to connect to the Hackathon platform.
  55.  
  56. The platform provides an online development environment that allows Participants to solve the Hackathon’s programming problems and submit their program directly online, without having to resort to external programs.
  57.  
  58. Participants may choose to use their own development environment but they then must submit their response within the online development environment for the answer to be taken into account by the rating system (an illustrative example of this is on the Site).
  59.  
  60. The Hackathon starts and ends at the same time for every Participant. The time and date of launch of the Hackathon according to the different time zones in the world is indicated for information on the Site. Once on the platform, and after having clicked on the "Start" button, Participants shall have access to the first problem statement.
  61.  
  62. Participants have an overall time of fifteen (15) days to complete the Hackathon. Within that timeframe, Participants can manage the time they spend on the programming game as much as they wish, whenever they wish.
  63.  
  64. If at the end of the Hackathon, Participants have not submitted their solutions on the platform within the overall time limit, their work will be submitted automatically as is.
  65.  
  66. Article 5: Determination of result
  67.  
  68.  
  69. The evaluation of Participants is objective and is done on the platform through an automated system configured in order to evaluate the solutions submitted by Participants.
  70.  
  71. Code submitted by Participants for each question will be compiled and evaluated according to the following criteria:
  72.  
  73. Scores for the test cases
  74.  
  75. Scores are computed when the solution is sent to the platform ("Submission"): the code is tested with test cases that reflect the specifications associated with the problem statement. In order to avoid cheating, these test cases are different from those given in the problem statement.
  76.  
  77. The platform compute two scores for the Participant: the Completion score as a percentage and the Optimization score as a number.
  78.  
  79. Participants whose code passes all test cases on the platform servers shall obtain the maximum Completion score.
  80. Applicants whose code does not compile or fails all the test cases will be assigned a Completion score of zero.
  81. Participants' codes are evaluated on a set of test cases directly related to the statement of each problem.
  82. On the basis of this automatic evaluation, each Participant will receive a Completion score percentage calculated using the following formula: number of test passed / number of test cases * 100.
  83.  
  84. For each passed test case, a test case Optimization score will be computed automatically by the platform from the submitted code. The formula used to compute this Optimization score is explained in the problem statement.
  85. For each failed test case, the Optimization score is zero.
  86. With each submission, each Participant will receive an Optimization score which is the sum of the Optimization scores of all test cases.
  87.  
  88. Each participant can submit multiple times during the course of the Hackathon. The number of Submissions is limited to twenty-five per five hours.
  89.  
  90. Each time the Participant created a new Submission, the new computed set of scores overrides the previous set of scores if any.
  91.  
  92. To further avoid cheating the Organizer may decide, during the course of the Hackathon, to add new test cases used when computing the Completion and Optimization scores. When this happens the scores of all the Participant will be recomputed based on the new set of test cases.
  93.  
  94. Ranking
  95.  
  96. The ranking is based on the Completion score. In the case of tied Completion scores, Participants will be ranked according to the Optimization score. In the case of tied Completion and Optimization scores. Participants will be ranked according to the date and time of their Submission.
  97.  
  98. Participants results
  99.  
  100. The day following the Hackathon, all Participants will receive by email their detailed results, including the following:
  101.  
  102. Their score
  103. The source code of their solutions
  104. Success or failure of the test cases defined for each problem
  105.  
  106. The results are obtained by applying objective criteria, on validation of an automated performance measurement process and the scores and ranking cannot be disputed nor appealed.
  107.  
  108. Article 6: Rewards - Prizes
  109.  
  110.  
  111. The Hackathon will propose rewards in the form of cash prizes, which will be given to Participant(s) with the highest rank as stated on the Hackathon’s registration page on the Site:
  112.  
  113. First place: $10,000 (ten thousand dollars)
  114. Second place: $5,000 (five thousand dollars)
  115. Third place: $2,000 (two thousand dollars)
  116.  
  117. The Participant who has won an award shall be contacted by CodinGame within 2 weeks after the end of the Hackathon and the amount of the prize will be credited to the Participant either by bank transfer or Paypal Transfer.
  118.  
  119. Prizes offered may not give rise to any dispute, nor delivery of their exchange value in any form whatsoever, or their replacement or exchange for any causes whatsoever, since this Contest does not constitute a promotional game.
  120.  
  121. Article 7: Data Protection
  122.  
  123.  
  124. The information required on the Site, such as email, name, address, etc... is collected and used in order to run a service in line with expectations, to contact Participants, manage the platform, and keep track of discussions and transactions.
  125.  
  126. This information, as well as the information entered in the detailed profile shall be used to generate statistics internally. The technical service that may be responsible for the management of competitions, is obliged to respect the confidentiality of the information and use it only for the specific operation for which they are involved.
  127.  
  128. Participants have a right to access, correct or delete information personal information which may be exercised upon written request addressed to the headquarters CodinGame.
  129.  
  130. Personal data will be processed in accordance with the Data Protection Act of 6 January 1978.
  131.  
  132. Article 8: Exclusion
  133.  
  134.  
  135. Non-compliance with the provisions of one of the items listed above shall lead to disqualification from the Hackathon. The decision shall be made by CodinGame.
  136.  
  137. Cheating is forbidden, under penalty of disqualification from the Hackathon. Cheating means:
  138.  
  139. Public release of a solution
  140. Exploitation of a flaw in the computing system
  141. The use or misuse of a solution
  142. An attempt to attack CodinGame servers
  143. Cheating or wrongdoing observed, such as in particular being assisted by a person or a machine, participating collectively, replacing on behalf of a registered Participant
  144. Attempting to reverse engineer the test cases used to compute the Completion and Optimization score
  145. Automating the Submission process through the use of an undocumented API
  146. Blatantly hard coding a solution to the problem. The codes of the potential winners of the Hackathon will be manually checked for hard coding. The potential winners will be disqualified if their code shows that the sole reason of their high ranking is through the use of hard coding techniques.
  147.  
  148. CodinGame reserves the right to make all the necessary checks regarding the Participants' identity and address.
  149. Any indication of false identity or address shall cause the Participant to be eliminated.
  150. CodinGame may cancel the participation of any Participant who has not complied with these.
  151. This cancellation may be made at any time without notice.
  152.  
  153. Article 9: Industrial and Intellectual Property
  154.  
  155.  
  156. The reproduction, representation or use of all or part of the components proposed in the Hackathon is strictly prohibited.
  157.  
  158. All data of any kind, and in particular logos, text, graphics, video or audio clips, trademarks, software, etc., appearing on the Site are necessarily protected by copyright, trademarks and all other intellectual property rights belonging to the Organizer and Warner Bros.
  159.  
  160. The latter consents a private, non-collective and non-exclusive right on such content to the Participants.
  161.  
  162. The Participants commit under these not to reproduce, summarize, modify, alter or redistribute without the Organizer's or Warner Bros’s prior permission, all or any part of the contents referred to in this article.
  163.  
  164. Article 10: Liability and Force Majeure
  165.  
  166.  
  167. CodinGame may in no way be held responsible for the failure of the internet network and the successful sending and receipt of mail, and the lack of postal services.
  168.  
  169. CodinGame reserves the right to shorten, extend, suspend or cancel the Hackathon if so required. It shall not be held liable if an unforeseen circumstance or a case of force majeure imposed any changes whatsoever to the Hackathon.
  170.  
  171. CodinGame also reserves this right in case of computer viruses, external attack, fraud, technical failure, and Participants shall be unable to seek its responsibility for this.
  172. Thus CodinGame reserves the right to sue in court those responsible for these facts.
  173.  
  174. In addition, CodinGame and Warner Bros. shall not be held liable for damages of any nature whatsoever, originating from a case of force majeure or any other external element, such as loss of revenue, data, customers, or any financial or commercial loss, any disturbance to business, lost profits or immaterial damages
  175.  
  176. Also, the responsibility would not be sought if the contract execution is delayed prevented due to a case of force majeure or unforeseeable circumstances, due to the other party or a third party or an external cause such as social conflicts, the intervention of civil or military authorities, natural disasters, fires, water damage, malfunction or interruption of the telecommunications network or power supply.
  177.  
  178. Force majeure means any event outside the affected area, of an unforeseeable, unavoidable and insurmountable nature, that prevents either party from fulfilling all or part of their obligations as stipulated by this contract.
  179.  
  180. Article 11: Refund of participation costs
  181.  
  182.  
  183. It is recalled that any connection made on an unlimited flat-rate basis (Cable, DSL ..) will not give rise to any refund.
  184.  
  185. Article 12: Access and Availability
  186.  
  187.  
  188. CodinGame is subject to an obligation of means to the Participant for the Site maintenance and is therefore committed to take all necessary measures to ensure that the Hackathon takes place in the best conditions of transit time, useful debit and permanence.
  189.  
  190. However, CodinGame cannot guarantee the operation of services twenty-four hours per day and seven days a week in particular due to nature of Internet and computer and network infrastructures required to conduct the Hackathon.
  191.  
  192. In all the cases mentioned, no compensation will be paid to the Participants whatever the damage suffered.
  193.  
  194. Indeed, malfunction or unavailability of the Site does not constitute a period during which the Organizer does not fulfill its contractual obligations.
  195.  
  196. Article 13: Dispute
  197.  
  198.  
  199. If one or more provisions of these are declared invalid or unenforceable, the remaining provisions shall remain in full force and effect.
  200.  
  201. All cases not covered by the Hackathon shall be settled by CodinGame whose decisions are final.
  202.  
  203. The law applicable to this contract is the French law.
  204.  
  205. Any dispute arising in connection with the Hackathon shall be the subject of an attempt for amicable settlement.
  206.  
  207. In the absence of agreement, the dispute shall be submitted to the competent courts in the jurisdiction of the organizing company, unless contrary to public order.
  208.  
  209. Any dispute or claim relating to the Hackathon shall be made ​​in writing and sent to the registered head office.
  210.  
  211. No dispute shall be admissible later than two months after the Hackathon is closed.
  212.  
  213. The Accountant © 2016 Warner Bros. Entertainment Inc. All Rights Reserved.
  214. Warner Bros. Entertainment, Inc. is not responsible for the promotion, administration or execution of the Contest.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement