The registration will close 2 days 1 day prior to the start date.
Each team will have exactly 48 hours to work on their projects.
Teams
Team size is 1 to 4.
Every team member has to be a human being, not an organization.
All members of the team should be 13 years old or older.
Judges of this contest can not participate in it as members of a team.
Every team has to be registered by completing the registration form.
Projects
All projects should be written to run on the Erlang VM / BEAM.
They can be written in any BEAM-based language (i.e. Erlang, Elixir, LFE, efene, clojerl, etc.).
Supplementary languages such as Javascript (and JS frameworks) are allowed.
No code can be created before the start of the contest.
Each team should come up with their own project idea (If you need inspiration check this website)
The organizing team will create a git repository at GitHub for each team.
If a team needs more than one, they can ask the organizers to create extra repos for them.
All deliverables should be uploaded to the repository, which is what will be used by the jury to evaluate the projects.
The only required deliverable is the code, but everything in the repository will be used for evaluation.
Suggested extra deliverables to include: Documentation, comprehensive README.md, project-related art (e.g. Logos), tests and anything that makes building and understanding the system easier for the judges.
Usage of third party libraries and web services is not prohibited, even encouraged.
Ownership and Copyright: Each team retains all the rights to their submissions.
User Privacy: If a project is an online application (such as a web application) that collects personal information from its users, it should not reveal any of personally identifiable information unless required to do so by law. Please respect people’s privacy.
Lawful submissions only: please do not submit anything that can be considered harmful, unlawful or both.
Evaluation
Your work will be judged by a publicly known jury, unless previously disqualified.
Each sponsor is responsible for delivering the prize they provided to the corresponding winning team.
Each project will be evaluated in 6 different categories: Creativity, Usefulness, Innovation, Correctness, Maintainability and Completion.
Final interpretation of each category meaning is up to the judges, but as general guidelines:
Creativity
This category assigns points for unexpectedness, eccentricity, fun. This is a broad category that may apply to the project, its code, the team, etc.
Usefulness
How useful the project will be for its target users. Does it solve an existing problem? Does it significantly reduce work time for its users?
Innovation
How groundbreaking the project is. The more unique and unprecedented the idea behind the project, the better. Also applies to projects developed in a unique way.
Correctness
The less bugs, the better. This category values working products over complete ones.
Maintainability
How easy will be for future developers to keep contributing to this project after SpawnFest is over.
Completion
Is the project functional? Did the team get to a point where there is something to show, even if there are a few bugs here and there?
Final score of each team will be computed as the sum of the points received in all those categories.
The team with the highest final score will be the winner of the contest.
Other prizes, besides the one for the winner, will be awarded as well.
Other Rules
Individual participants or even entire teams can be disqualified if they don't abide by these rules. The organizers reserve the right to apply the punishment they consider fit to any transgression.
Event organizers will not reimburse you for any expenses or losses.
Event organizers are not responsible for any damage, legal actions or any other outcomes that might be a result of your participation.
Event organizers reserve the right to change these rules without prior notification.
