Rules: remove restriction on existing dapps, add open source requirement
This commit is contained in:
parent
74a6ef305c
commit
a58bc0d1d5
|
@ -263,7 +263,8 @@
|
|||
<li>The hackathon officially begins at the <strong>Kickoff</strong> event listed on the schedule. You have from that time until the <strong>Pencils Down</strong> event to work on your project. Before the <strong>Kickoff</strong>, you should <em>not</em> code your project. Prior to <strong>Kickoff</strong>, you can learn and practice with the Status API, discuss ideas, and find teammates.</li>
|
||||
<li>Do <em>not</em> make any modifications to your project after <strong>Pencils Down</strong>.</li>
|
||||
<li>You may only use preexisting code if it is already open source. That way, all teams have access to the code.</li>
|
||||
<li>If you are making an existing DApp mobile-compatible you must disclose that on your GitHub <em>issue</em> RSVP. Write “Existing DApp” for the <em>Type</em>. You will still be eligible for prizes—in fact, we will award a prize for the “Best Mobile Conversion”. If you want to be considered for the First, Second, and Third prizes, then in addition to making your DApp mobile-ready, consider adding a feature that changes its experience in some way—perhaps using chat or commands in a way that Status allows that wasn't quite possible before.</li>
|
||||
<li>If you are making an existing DApp mobile-compatible you must disclose that on your GitHub <em>issue</em> RSVP. Write “Existing DApp” for the <em>Type</em>. You will still be eligible for prizes—in fact, we will award a prize for the “Best Mobile Conversion”.</li>
|
||||
<li>Your team's source code must be available for public review and scrutiny so that anyone can audit it to check for ethics and bugs. One of our core tenants at Status is open development, so you'll be participating in the Ethereum ecosystem the same way we do. You are free to choose any type of licensing as long as your source code is publicly viewable.</li>
|
||||
</ol>
|
||||
</div>
|
||||
</div>
|
||||
|
|
Loading…
Reference in New Issue