Developer Challenge Rules
- Entries should come from at least one developer though teams are welcome.
- Entries should be presented by at least one member of the team either live during the judging session on Friday 2nd August 2013 at 1100 (BST) at Repository Fringe 2013 or in a pre-recorded video to be shown at the session. Please note that videos must be submitted by Thursday 1st August 2013 at 1600 (BST).
- Entrants must post their idea or intention by registering their team on this form by Thursday 1st August 2013 at 1600 (BST). You will need to provide a name for your team or hack, and who is in the team. Don’t worry if you want to change the name later or the composition of the team. You will also need to provide a short description and a URL (e.g. to code, presentation/images, or working demo) for the hack or idea.
- The winners and runners up will be announced in a Results session held in the afternoon of Friday 2nd August 2013 at the Repository Fringe event. It will also be announced via the @repofringe Twitter account.
- The winners and runners up must be willing to have their name published by Repository Fringe 2013 team, alongside a description of their hack.
- Entries can take the form of prototypes or working code. Prototypes should primarily be presented as user interfaces, not as bullet points or architectural diagrams. If the prototype consists of only mock interfaces (e.g. “photoshopped” or a “paper prototype”), then there should be a brief explanation of how the interface could be built using a particular code base / architecture.
- Whilst new code for prototypes is encouraged, previously written code may also be used.
- The same code may be used in multiple prototypes. Sharing of code is encouraged.
- No code is off limits for use so long as it is legally used. Third party libraries, applications and web services are fair game.
- Participants must ensure that entries do not in any way infringe copyright or other intellectual property rights of any third party.
- The judging process will use the following methodology:
- Judges will agree a winner for each of the categories
- If a consensus cannot be reached then the chair of the judging panel will be responsible for the final decision.
- A member of the Repository Fringe 2013 organising team will oversee the judging process.
- The evaluation criteria for the competition are: innovative, visionary, coolness, usability, potential for wider use, technical viability, functionality and overall fit to the theme of digital preservation.
- The judges’ decisions are final.