3 ms·

I have statistics about real team size behind open-source repositories, and it is exceedingly rare to be larger than 50: https://play.clickhouse.com/play?user=p

I have statistics about real team size behind open-source repositories, and it is exceedingly rare to be larger than 50: https://play.clickhouse.com/play?user=play#U0VMRUNUIHJlcG9fbmFtZSwgbWVkaWFuKHUpIEFTIHRlYW0gRlJPTSAoU0VMRUNUIHJlcG9fbmFtZSwgY3JlYXRlZF9hdDo6RGF0ZSBBUyBkLCB1bmlxKGFjdG9yX2xvZ2luKSBBUyB1IEZST00gZ2l0aHViX2V2ZW50cyBXSEVSRSB0b1N0YXJ0T2ZNb250aChjcmVhdGVkX2F0KSA9ICcyMDI0LTA5LTAxJyBBTkQgZXZlbnRfdHlwZSA9ICdQdWxsUmVxdWVzdEV2ZW50JyBHUk9VUCBCWSByZXBvX25hbWUsIGQpIEdST1VQIEJZIHJlcG9fbmFtZSBPUkRFUiBCWSB0ZWFtIERFU0M= https://play.clickhouse.com/play?user=play#U0VMRUNUIHJlcG9fb... For comparison, my open-source product has around 20..30 according to the monthly stats (I want these numbers to be higher, though): https://play.clickhouse.com/play?user=play#U0VMRUNUIHRvU3RhcnRPZk1vbnRoKGQpIEFTIG1vbnRoLCBtZWRpYW4odSkgRlJPTSAoU0VMRUNUIGNyZWF0ZWRfYXQ6OkRhdGUgQVMgZCwgdW5pcShhY3Rvcl9sb2dpbikgQVMgdSBGUk9NIGdpdGh1Yl9ldmVudHMgV0hFUkUgcmVwb19uYW1lID0gJ0NsaWNrSG91c2UvQ2xpY2tIb3VzZScgQU5EIGV2ZW50X3R5cGUgPSAnUHVsbFJlcXVlc3RFdmVudCcgR1JPVVAgQlkgZCBPUkRFUiBCWSBkKSBHUk9VUCBCWSBtb250aCBPUkRFUiBCWSBtb250aA== https://play.clickhouse.com/play?user=play#U0VMRUNUIHRvU3Rhc...

eskibars 2y ago
This is significantly undercounting in at least several cases I know of. e.g. I was employed by Elastic and Kong and in both cases, the number of developers employed by the company to work on these projects was several multiples the size reported here
- eskibars 2y ago
  Ah, I now see why: I hadn't really looked at the query, but now that I have, here are some of the problems: 1. Using median is a problem for many projects because many often start off (sometimes for years) with only a few developers before they really take off. The median() number for Elasticsearch was 28, but the max() is 49, which I suspect is closer to the current number. 2. Not everybody uses a pull request flow, and not everyone working on a project is a developer. You could have product managers, technical writers, engineering managers, etc, all working on a project and not opening PRs and you can have users just directly adding commits, especially when a project is young. The original query here for the kong/kong project shows a team size of 6, but if you remove event_type = 'PullRequestEvent' and switch to max(), you get 33. 3. Sometimes, parts of the project are kind of "elsewhere." e.g. Elastic employed a number of Lucene committers to help move Lucene along, Kong employed a number of folks that would e.g. commit/maintain OpenResty plugins which got incorporated in the build system, the docs live in separate repos in both cases, etc.

eskibars 2y ago

This is significantly undercounting in at least several cases I know of. e.g. I was employed by Elastic and Kong and in both cases, the number of developers employed by the company to work on these projects was several multiples the size reported here

eskibars 2y ago
Ah, I now see why: I hadn't really looked at the query, but now that I have, here are some of the problems: 1. Using median is a problem for many projects because many often start off (sometimes for years) with only a few developers before they really take off. The median() number for Elasticsearch was 28, but the max() is 49, which I suspect is closer to the current number. 2. Not everybody uses a pull request flow, and not everyone working on a project is a developer. You could have product managers, technical writers, engineering managers, etc, all working on a project and not opening PRs and you can have users just directly adding commits, especially when a project is young. The original query here for the kong/kong project shows a team size of 6, but if you remove event_type = 'PullRequestEvent' and switch to max(), you get 33. 3. Sometimes, parts of the project are kind of "elsewhere." e.g. Elastic employed a number of Lucene committers to help move Lucene along, Kong employed a number of folks that would e.g. commit/maintain OpenResty plugins which got incorporated in the build system, the docs live in separate repos in both cases, etc.