Hi Leo, Leo Famulari <l...@famulari.name> skribis:
> Growth of active committers: > ------ > $ git shortlog -ncs v0.8..v0.9.0 | wc -l # ~23 months > 20 > $ git shortlog -ncs v1.4.0..HEAD | wc -l # ~25 months > 51 > ------ > > Growth of contributors in the same time period: > ------ > $ git shortlog -ns v0.8..v0.9.0 | wc -l > 47 > $ git shortlog -ns v1.4.0..HEAD | wc -l > 570 > ------ > > So, we are not growing our base of committers in proportion to > contributors, and I think we've lost contributors as a result. I believe we want to keep the number of committers relatively small, for security reasons. For Nixpkgs, we get: --8<---------------cut here---------------start------------->8--- $ git shortlog -ns --since=two-years|wc -l 5675 $ git shortlog -ns --since=last-year|wc -l 4048 --8<---------------cut here---------------end--------------->8--- Using ‘-ncs’ won’t give us the real number of committers to Nixpkgs (since everyone who makes a pull request is a committer from Git’s perspective). So I asked fellow NixOS hackers on Mastodon and there’s at the moment 255 committers to Nixpkgs (ratio of 1 to 16). The way to get there is by automating things so that committers have little more to do than press a button to merge changes. My understanding is that Nixpkgs now allows merges by package maintainers, who are usually not committers, by sending commands to a merge bot: https://github.com/NixOS/nixpkgs-merge-bot https://github.com/NixOS/rfcs/pull/172/files#diff-d44ac0cd941ca5ce5e56388cd1a97171b299feed94aae4a405b3cc56b26d8b0c This is the kind of workflow we need to improve scalability IMO. Ludo’.
