[burger_moon]

I would love to hear from people involved in projects like this, what kind of work/ how much, was done to get it ready for and approved to be open sourced by the company.

Especially at large corps like Netflix I'm sure there's a lot of hoops to jump through.

[lhorie]

In my company (uber), it's actually not a whole lot of hoops. Basically a light legal review that checks the license, a code review to ensure there aren't references to closed source software and infrastructure, and approval from the team manager, who is usually already on board with the desire to open source.

[captain_perl]

I'm sure the first project took some time to setup, but Netflix has released dozens of projects since. So very low hoops.

[staticassertion]

Netflix seems to also have a really strong culture around this though, so I wouldn't be surprised if it's a lot less hoopy than you'd imagine.

[error54]

Not to shamelessly plug but if you're in the Bay Area on June 28, we're giving a talk that's a bit about performance, a bit about Netflix engineering culture: https://jstalks2018.splashthat.com/.

[MaxLeiter]

If I’m a student can I sign up to attend?

[wesleytodd]

Sure! (at least I don't see why you wouldn't be able to)

[koopa184]

Exactly. They had engineers dedicated to creating an open source latency/fault tolerance library called Hystrix. Not too surprising they’re dedicating resources to other projects, too.