J-j-b·Jun 3, 2013Submission
1 points · Open discussionNetflix
Cloud-Prize
DevOps & Cloud2013–2013
Netflix / Cloud-Prize
Cloud-Prize
Description and terms for the Netflix Cloud Prize, which runs from March-September 2013. Read the rules, fork to your GitHub account to create a Submission, then send us your email address.
4Distinct people
5Mentions
0Explicit recommenders
164GitHub stars
What to know before exploring
What it is
Description and terms for the Netflix Cloud Prize, which runs from March-September 2013. Read the rules, fork to your GitHub account to create a Submission, then send us your email address.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week5 dated mentions
Observed mentions: 2013-03-14 02:33:29 UTC to 2013-06-03 14:18:09 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Mar 11 | 2013-03-11 00:00:00 UTC | 2013-03-18 00:00:00 UTC | 4 | 3 | 1 |
| Mar 18 | 2013-03-18 00:00:00 UTC | 2013-03-25 00:00:00 UTC | 0 | 0 | 0 |
| Mar 25 | 2013-03-25 00:00:00 UTC | 2013-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 1 | 2013-04-01 00:00:00 UTC | 2013-04-08 00:00:00 UTC | 0 | 0 | 0 |
| Apr 8 | 2013-04-08 00:00:00 UTC | 2013-04-15 00:00:00 UTC | 0 | 0 | 0 |
| Apr 15 | 2013-04-15 00:00:00 UTC | 2013-04-22 00:00:00 UTC | 0 | 0 | 0 |
| Apr 22 | 2013-04-22 00:00:00 UTC | 2013-04-29 00:00:00 UTC | 0 | 0 | 0 |
| Apr 29 | 2013-04-29 00:00:00 UTC | 2013-05-06 00:00:00 UTC | 0 | 0 | 0 |
| May 6 | 2013-05-06 00:00:00 UTC | 2013-05-13 00:00:00 UTC | 0 | 0 | 0 |
| May 13 | 2013-05-13 00:00:00 UTC | 2013-05-20 00:00:00 UTC | 0 | 0 | 0 |
| May 20 | 2013-05-20 00:00:00 UTC | 2013-05-27 00:00:00 UTC | 0 | 0 | 0 |
| May 27 | 2013-05-27 00:00:00 UTC | 2013-06-03 00:00:00 UTC | 0 | 0 | 0 |
| Jun 3 | 2013-06-03 00:00:00 UTC | 2013-06-10 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
5 sourcesSome of the evaluation criteria [1]:
* Submission provides evidence that code is in use by other projects, or is running in production at Netflix or elsewhere
* Submission has a large number of watchers, stars and forks on github.com
So the entrant has to prove that it is used in production at Netflix? And why would they care about the number of watchers/stars/forks? If I made a great contribution to something very specific (let's say aiming for the "Best contribution to performance improvements" or "Best contribution to code quality" awards), why would anyone watch/star/fork my repo? This seems more like a popularity contest to be honest...
[1] https://github.com/Netflix/Cloud-Prize/wiki
In Announcing the Netflix Cloud PrizeAnnouncing the Netflix Cloud Prize
78 points · Open discussionAnnouncing the Netflix Cloud Prize
2 points · Open discussion