mikas blog

Wer die LKML nicht mitliest, aber am Workflow von Open-Source-Entwicklung interessiert ist, sollte unbedingt in den Thread "Slow DOWN, please!!!" hineinlesen. Ausgelöst von David ‘Mr. SPARC and Network’ S. Miller, geht es um die Frage, wie man die enorm vielen Patches und damit einhergehende Bugs/Regressionen im Merge-Window besser in den Begriff bekommen könnte.

Natürlich ist das teilweise sehr spezifisch für das Entwicklungsmodell “wohlwollender Diktator” (engl: benevolent dictator) beim Linux-Kernel, aber gerade wenn man den Kontext zur Entwicklung rund um OpenSolaris herstellen kann, verstecken sich einige sehr interessante Aussagen in der Diskussion.

Als Anregung ein kleines Best-Of:

Linus:

I don’t think quality and speed of development are related. In fact,
I think quality and speed often go hand-in-hand: the same way
some of the best programmers are also the most productive,
I think some of the most productive flows are likely to generate
the best code!

Al ‘code-auditor’ Viro:

On Wed, Apr 30, 2008 at 06:40:39PM -0700, Linus Torvalds wrote:

> Now, we do know that open-source code tends to be higher
> quality (along a number of metrics) than closed source code,
> and my argument is that it’s not because of bike-shedding
> (aka code review), but simply because the code is out there
> and available and visible.

Really? And how, pray tell, being out there will magically improve the
code? “With enough eyes all bugs are shallow” stuff out of ESR’s arse?

Andrew Morton:

On Wed, 30 Apr 2008 15:31:22 -0700 (PDT) Linus Torvalds wrote:

> Any suggestions on how to convince people that their code
> is not worth merging?

Raise the quality. Then the volume will automatically decrease.

Ich bin ja gespannt, ob und wie es das Thema bis in die Mainstream-IT-Medien (heise & CO) schafft…

This entry was posted by mika on Thursday, May 1st, 2008 at 13:50 and is filed under Computer, Links. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.