-
Notifications
You must be signed in to change notification settings - Fork 0
3.0 Rules
Please read the rules carefully. Breaching the rules could result in your project being disqualified and breaching the code of conduct could result in your expulsion from the hackathon.
• Attendees from all backgrounds, genders, and geographies are welcome. Attendees coming from traditionally underrepresented groups will have an advantage in the hackathon application process.
• Organizing Committee members are not eligible to participate in the hackathon. They may, however, assist teams as mentors during the coding/development phase.
• There is no country restriction but you must be eligible to receive prizes (in case you win) and you are responsible for paying any taxes on the prize winnings.
• Teams must consist of at least one member but not more than five members. Exceptions can be made for teams to have more than five members on a case by case basis. Contact the hackathon organizing committee in case you need to have a team of more than 5 members.
• Changes to team members are not permitted after Monday, 17.09.2018 8:00 PM. Exceptions can be made on a case by case basis as decided by the hackathon organizing committee.
• Teams are not allowed to begin work prior to the hackathon. If any team has a code base prior to the start of the hackathon it will be required for them to declare their code by publishing it openly to the team github before they begin and comment the part as “set up before hackathon”
• Teams starting with an established code base will also be required to present their starting point publicly during the initial pitch sessions (see agenda).
• It is recommended to brainstorm ideas and create wireframes/mockups prior to the hackathon as well as to discuss these ideas with one another under the appropriate track discussion board.
• Any software development tools, IDE, or programming language can be used for the event.
• If a team member uses a purchased tool licensed to him or her and the license is not transferable to other members the team should choose one available to all developer team members.
• To ensure a level field for all contestants, all code must be created only at the hackathon.
• You are permitted to use publicly developed API’s for your project.
• Project design/assets can be created prior to the start date of the hackathon. All assets should conform to the Creative Commons License agreement standard, or is freely available and you have permission or license to use it. Proof of permission must be given upon request.
• Assets, SDKs, APIs or other tools or components available under a trial license may be used.
• A team can submit only one entry for the hackathon. Participation at the hackathon is subjected on a “per-team” basis meaning you are not allowed to be on more than one team at the event.
• Any intellectual property developed during and within the scope of the hackathon must be open source and licensed under one of the licenses referenced in https://opensource.org/licenses.
• The license selected by the team must be clearly listed in code (page per page) or a generic page announcing the license the application adheres to. Also, the public code used in your application should also list the licenses the code is subjected to.
• A team can use multiple licenses in the application. For example, The public code used is subjected to the Apache license agreement whereas the code written by the team for the application is subjected to the MIT license agreement.
• A team may not code applications that violate the code of conduct. For example, Racially insensitive ideas for an application will automatically be disqualified.
All teams should have a team name, and maintain their code as a public repo on the Swiss Legal Tech GitHub organization. The Github team page should include a readme with the following information:
• The team lead must list a mobile phone number or a slack account
• The development tools used to build the project
• SDKs used in the project
• APIs used in the project
• Any assets used in the project
• Any libraries used in the project
• Any components not created at the hackathon
• All projects must be submitted as team repos with a track on the Swiss Legal Tech GitHub organization before judging begins on Tuesday, 18.09.2018 6 pm.Failure to submit will result in disqualification.
• Applications can be spot checked by code reviewers. All winning projects can be code reviewed to confirm that the code is indeed original work created at the hackathon and any breach of these rules in spirit or in fact, will be grounds for disqualification either at the hackathon or ex-post facto.
Our hackathon is dedicated to providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, nationality, religion, previous hackathon attendance or computing experience (or lack of any of the aforementioned). We do not tolerate harassment of hackathon participants in any form. Sexual language and imagery are not appropriate for any hackathon venue, including hacks, talks, workshops, parties, social media and other online media. Hackathon participants violating these rules may be sanctioned or expelled from the hackathon at the discretion of the hackathon organizers.
Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, nationality, or religion, sexual images in public spaces, deliberate intimidation, stalking, following, photography or audio/video recording against reasonable consent, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. Photography is encouraged, but other participants must be given a reasonable chance to opt out from being photographed. If they object to the taking of their photograph, comply with their request. It is inappropriate to take photographs in contexts where people have a reasonable expectation of privacy (in bathrooms or where participants are sleeping).
Participants asked to stop any harassing behavior are expected to comply immediately. As this is a hackathon, we like to explicitly note that the hacks created at our hackathon are equally subject to the anti-harassment policy. Sponsors and partners are also subject to the antiharassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Sponsor representatives (including volunteers) should not use sexualized clothing/ uniforms/costumes or otherwise, create a sexualized environment. If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of hackathon staff immediately.
Hackathon staff will be happy to help participants contact any local security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the hackathon. We value your attendance. If a participant engages in harassing behavior, the hackathon organizers may take any action they deem appropriate. This includes warning the offender, expulsion from the hackathon with no refund (if applicable), or reporting their behavior to local law enforcement. We expect participants to follow these rules at hackathon and workshop venues and hackathon related social events.
• In order to ensure fairness, jury members must abstain from votes on hackathon teams in which they have a vested interest (ie. Sponsors will not be able to cast votes for their own teams).
• For teams which started coding prior to the hackathon, to insure fairness, the jury will be instructed to consider their work on the basis of advancement from their publicly declared starting point as compared with their peers who started from scratch.
• Should a tie for one of the first three places occur, the judges will vote again on just the merits of the tied team.
Jury Members: Coop Rechtschutz SBB-Swiss Federal Railways PWC Legal Services Bucerius Law School Wolters Kluwer
The pitch of each team's solution takes place on Tuesday evening. The pitch should not take longer than 5 minutes but should contain all relevant information. This will be followed by a 2 minute Q&A.
Pitch Order
Teams will pitch in the alpahbetical order that their repository names have on github.
The evalutation of the pitch adresses the following points:
Vision (10 points):
• How innovative is the project?
Achievement (10 points):
• How good is the technical implementation/Design/Usability?
Learning process (10 points):
• Did the original idea change while developing? At which point did the team start?
• Did the team have previous knowledge about their vision?
• If the team started before the hackathon did the team declare their code base initially? (If not: Disqualification)
Compete and Collaborate (10 points):
• How many different companies are involved?
• How is the compete and collaboration process?
• Did the team bring many different companies and technologies together?
Relevance (10 points):
• Does it make sense to use the chosen technology?
• Is it relevant to challenges in the legal industry?
The hackathon winners will receive prize packages. Prize packages will be awarded for the first, second and third place winning teams.
#Credits
We'd like to thank the MIT Media Lab and the Blockchained Mobility Hackathon for inspiring the content and structure of our hackathon rules.