The actual contest is buried in a PDF file:
<p>1. Best example application mash-up<p>Code that pulls together all the services, along with tutorial documentation that explains how it works and how to extend it.<p>2. Best new monkey
<p>Autonomous code that helps operate the platform, often clients of Edda's historical state database.<p>
3. Best contribution to code quality<p>Tests, fixes, improvements to robustness and antifragility, new code testing tools. Since this may be aggregated across many pull requests for test cases and bugs, they should be listed and documented in the Submission.<p>4. Best new feature<p>
The missing link, the one thing no one thought of doing, that makes a big difference to a project.<p>5. Best contribution to operational tools, availability and manageability<p>
Integration with existing monitoring and alerting tools, and/or completely new tools and automation that enhances availability.<p>6. Best portability enhancement<p>Portability across languages, operating systems, data stores, between cloud and datacenter, and across various cloud APIs which increase the applicable scope of NetflixOSS. Converting fixed interfaces into pluggable patterns.<p>7. Best contribution to performance improvements<p>New performance testing tools, results of performance tests and performance oriented bugs. Since this may be aggregated across many pull requests, they should be listed and documented in the Submission.<p>8. Best datastore integration
<p>Improved support for SQL and NoSQL databases, client library interfaces and operational automation.<p>
9. Best usability enhancement<p>Improvements to existing user interfaces, better icons and tutorials, and new tools that make NetflixOSS easier to use, deploy and diagnose.<p>10. Judges choice award<p>
An award given by the Judges to the best Submission that doesn't fit in a single category, perhaps straddling several or inventing a new category.