On 2010-09-14 at 03:41:13 [+0200], Enrico Weigelt <weigelt@xxxxxxxx> wrote: > * Alex von Gluck <kallisti5@xxxxxxxxxxx> schrieb: > > > I personally like this workflow (it's how the linux kernel is run): > > http://whygitisbetterthanx.com/images/workflow-c.png > > > > You have lower level commiters and upper level commiters and the code > > trickles upward. Given git has an "author" and a "commiter" field this > > workflow works well with a git repo and would suit the need for more > > 'lower-level' commiters well. > > ACK. This seems to be a very fine workflow for OS development. There are tremendous differences between Linux and Haiku: The changes of a single Linux (2.6.x) release challenge the complete code base of Haiku. Linux' patch stream is probably almost 2 orders of magnitude greater. Linux has benevolent dictator who is permanently full time employed to be just that. I suspect at least some of the subsystem maintainers are, too. Given how our patch reviewing has worked so far, changing the workflow in such a way that one or some people who aren't full time employees are the bottle necks would certainly not be an improvement. CU, Ingo