* 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...
Or are you complaining about netflix wanting projects "that contain a substantive contribution, working code and which have high community adoption"?
If that's what they want, then that's what they want and should award prizes accordingly.
I guess I'm partly missing the point of the competition, and missed the fact that the entry could be anything(?) and does not have to do with something directly Netflix-related (either customer facing or operations).
The contest is exactly a popularity in most of those categories. Make something people find useful and share it. That's the entire idea behind OSS.
I imagine the performance categories are going to be judged a little bit differently, but for most categories the criteria look reasonable to me.
It's similar to their algorithm contest - where they basically had a fixed potential investment but reaped rewards thousands of times greater than what they could have afforded by tapping into people willing to work for free as a hobby.
On one hand I think it's a great idea, but on the other I'm concerned about how this can be exploited; industries built on passions tend to massively undervalue employees. See: Aviation, Sports, Publishing.
Much like the infamous recommendation data challenge, that was never put in production.
I am, too, a cynic - and I think their data model is flawed from the beginning (user account vs. household, among other things), causing schizophrenic recommendations.
Profiles are being tested now and will soon be deployed to all customers.
Disclaimer: I work for Netflix.
I thought Netflix OSS is great. They're opensourcing something like 30 projects, putting on super well organized meetups with expo like rooms where you can pick Netflixers brain about the software and their internal systems in general, free food&beers, free Ts, etc. It was great.
They do it go give back to the community, to get patches and ports from the community, and hiring of course, there's nothing wrong with that!
More Python should follow shortly. Python is much newer here, so we aren't as far along the open source path.
Does anyone have any suggestions on how to make this clearer? I've seen this question a few times.
Edit: Thanks for the feedback everyone. I've incorporated it into the page.
Also maybe spitball some examples of what you expect people will do with this. Lots of cool repos there but it is a bit overwhelming.
You can also write a new monkey in any language you want.
Assuming your job description is something like relations.
However, they are a fun way to recruit.