We want the Dash to be fun and for everyone to have a good time. To help this and to make the expectations clear, we’ve got eight simple rules for the competition. Without further ado, they are:
- Majority in Django
- You can leverage other tools, but ~50% of your project ought to be in Django. We won't count the lines, but if you're not using Django, it's not really the Django Dash is it?
- Nothing Gets Built Ahead Of Time
- Ideas and/or pencil & paper (not digital) mockups ONLY before the competition. NO CODE.
- 48 Hours To Build
- Starts on July 30 @ 00:00 AM GMT and ends 48 hours later on July 31 @ 11:59 PM GMT. Anything submitted outside of that timeframe will be ignored during the judging.
- Max Team Of 3
- You and up to two other cohorts.
- Your Choice Of Git Or Mercurial
- By popular demand, you must use a DVCS this year (git or mercurial). In order to update the site, track who's competing and make sure things stay fair, you'll need to use either GitHub or BitBucket and setup the webhooks to talk to the Django Dash site. Instructions will be provided.
- Your Entry Is Open Source
- To help with the judging process, all entries must be open-source. This allows non-paid usage of GitHub or BitBucket (though their services are worth paying for). It will also remove questions about judging code quality AND it's good for the community.
- Third Party Allowances
- You may use any third party sources (Python modules/Django apps/etc) you wish. But be warned that the less code you write, the worse your judging score will be. The point is that you should build an app/site, not just tie a couple things together.
- You Must Use Pip Requirements Or Buildout
- Your entire project must be able to be installed using Pip via a requirements file (preferred) or via buildout. If your app isn't packaged & installable via one of these two options, it simply won't get judged.
Anything that's not strictly a rule of the competition can be found on our FAQ page, so you may want to give that a glance.