Hacker News new | ask | show | jobs
by LnxPrgr3 5001 days ago
On a repo I've been maintaining, I'm horribly tempted to revoke almost everyone's commit access, for two reasons: to add a code review step to the process, and to be able to keep the commit history reasonably clean.

It's low-tech, but a human gatekeeper's really your only hope for enforcing whatever conventions your project has.
4 comments
exDM69 5001 days ago
It makes a lot of sense to require that a commit must go through at least 1-2 human reviewers before getting merged to master. In addition to going through automated builds and tests, if applicable.

You need more than one person who can commit to master and is responsible for the merges, but you most certainly don't need every contributor to have commit access.

link
mcgwiz 5001 days ago
No it's not your only hope. Your other hopes are:

- hiring developers that appreciate and obey the conventions, or

- reducing the weight of the conventions.

Simply put, if you have conventions that the developers aren't following, you're organization is dysfunctional in some way. Management should include the team when crafting the conventions, and management should take efforts to give the team time/resources to obey them.

link
qznc 5001 days ago
Well, git should be excellent in this case, because it is essentially the same work flow as Linus. Everybody just pulls from each others repo.
link
mattdeboard 5001 days ago
Based on what I've seen from popular open-source Python projects I've used in the past (Fabric, Haystack and basically anything else by daniel lindsley) having a single human gatekeeper is the express lane to hell. If you do that make sure you have at least a few core contribs who can approve commits.
link
qznc 5001 days ago
Linus is the single gatekeeper of Linux.
link
EternalLight 5001 days ago
No, he isn't. He's the final gatekeeper but there are several of lower level gatekeepers/maintainers for different parts.

At least according to rumors, I've never invested the time to get involved myself.

link
dfc 5001 days ago
There are an awful lot of maintainers for smaller individual pieces/subsytems of the kernel. Take a look at the MAINTAINERS file to see who is responsible for the smaller chunks:

  grep -B1 ^M: /usr/src/linux-kernel/MAINTAINERS
link
jrochkind1 5000 days ago
I've never even looked at any linux source code, but I still know there's too much of it to believe Linus reviews and signs off on every single commit personally.
link