Re:Linus on keeping a clean git history (2009)
by exDM69 on Thursday October 04, 2012 @11:09AM
(#4612650)
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.
Re:Linus on keeping a clean git history (2009)
by mcgwiz on Thursday October 04, 2012 @02:08PM
(#4613531)
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.
Re:Linus on keeping a clean git history (2009)
by qznc on Thursday October 04, 2012 @11:08AM
(#4612643)
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.
Re:Linus on keeping a clean git history (2009)
by mattdeboard on Thursday October 04, 2012 @11:04AM
(#4612619)
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.
Re:Linus on keeping a clean git history (2009)
by qznc on Thursday October 04, 2012 @11:09AM
(#4612648)
Linus is the single gatekeeper of Linux.
Re:Linus on keeping a clean git history (2009)
by EternalLight on Thursday October 04, 2012 @11:22AM
(#4612729)
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.
Re:Linus on keeping a clean git history (2009)
by dfc on Thursday October 04, 2012 @12:35PM
(#4613111)
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
Re:Linus on keeping a clean git history (2009)
by jrochkind1 on Friday October 05, 2012 @12:06AM
(#4615641)
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.
It's low-tech, but a human gatekeeper's really your only hope for enforcing whatever conventions your project has.