[eipipuz]

There might be a survivor bias here. How can we know how many similar projects didn't make it out of that cohort?

[gravypod]

What successful oss has been originally built by in office teams? I struggle to think of things past golang or mysql.

[UncleMeat]

The point is that there are lots of failed oss projects. Further, a startup has a lot more requirements than an oss hobby project. For your hobby you can send an email to a listserv and say “burned out, taking a three month break” or you can focus exclusively on the code.

But a startup needs to make money or it can’t pay people. You don’t just need code. You need a product and you need to sell it.

[bart_spoon]

> The point is that there are lots of failed oss projects.

There's a lot of failed start ups in general. Doesn't seem like its a feature unique to remote-only projects.

[UncleMeat]

Sure. My point is that "linux exists" is not evidence that remote startups will be statistically as likely to succeed as in person startups.

[gravypod]

Linux isn't the end of the list. You can also include everything from Gitlab, HashiCorp, and Elastic and they make quite a bit of software.

[nwsm]

Hadoop, Kafka, Kubernetes, Angular, React, GraphQL, TensorFlow, TypeScript, Android.

A lot of the Apache projects came from companies. Although some of these were more like one person at the company developed it and the company funded and maintained it.

[gravypod]

> Kubernetes

Did Kubernetes start in person as in in the same room? It was built by multiple people but I don't know if they shared an office space. I thought it was that they shared a building.

All of the other ones though are pretty solid examples of team-driven OSS work.

[vinerator]

MongoDB