-
Notifications
You must be signed in to change notification settings - Fork 5
Solution Write up Guidelines
Everyone is invited to contribute solution write-ups to the challenges. We're giving first rights to the winners and then the runners up. After that, it's first come, first published.
If you'd like to submit a write-up, tell us at [email protected] and we'll let you know if someone else has reserved it already.
At the end of each challenge cycle, we'll post the final results and scores along with the write-ups for each challenge.
Below are some simple guidelines for how to format and submit the write-up.
The write-up should be a 1 - 3 paragraphs explaining:
- how the bug works
- what vulnerabilities it exposes, if any
- how it should be fixed
- anything else you think is interesting
If possible, write it in markdown. Don't worry if it doesn't look pretty. We can help with that.
E-mail it to [email protected]. It can be in the body of the message or a link to a gist.
Also, let us know your GitHub and / or Twitter handle so we can credit you in the write-up. For those of you with tinfoil hats, let us know if you'd like to remain anonymous.