Rules

  1. Entries SHOULD use the API and Theme specified by the current Judge.

  2. Entries MAY be written using any computer language.

  3. Entries dependent on a language, library or other component not available on a standard install of Mac OS X with latest Developer Tools installed MUST contain all dependencies necessary to execute the entry.

  4. There is no rule 4.

  5. Where appropriate entries MUST contain a pre-compiled executable version of the software.

  6. Entries MUST come with documentation. At the very least said documentation MUST identify the author or authors, describe how to run the software, contain date and version information. Documentation SHOULD describe how the software makes use of the Theme and API if not obvious by the running of the software. Entries MUST specify the license of the software. See #8.

  7. Entries MUST be packaged as a zip, tarball or disk image file. Zip and tarballs are preferred.

  8. Entries MUST be licenses under an Open Source compatible license. BSD and MIT licenses are preferred. See http://opensource.org/docs/osd

  9. Unless specified otherwise by the current judge, entries MUST NOT implement system extensions, Haxies or Input Managers.

  10. Entries MUST be submitted at the Ironcoder submissions page before the contest finish time specified. Late entries MAY be considered at the judge’s discretion.

  11. Scoring is completely based upon judges discretion.

  12. The judge MAY impose other conditions and change any or all rules at will.

  13. The judge MAY specify the hardware and software the entry will be tested on.