2.3.51 tulip broken

[Jeff Garzik]

David Ford wrote:
> 
> Jeff Garzik wrote:
> 
> > Donald, I, and others all seem to agree that having his drivers and
> > the kernel drivers diverge is a poor situation.  However, while Donald
> > continues closed source development with periodic code drops, and does
> > not work with other kernel developers when creating infrastructure, I do
> > not see a resolution to the situation any time soon.
> 
> Please explain how his code development is closed source?  This is totally BS
> and you know it.  All the code is available, all the list discussion is
> available, and patches and requests are accepted all the time.
> 
> Quit it.  His development is quite open.  Resolutions come when the mud stops
> being thrown.

Donald's development is not open AT ALL.  Read Donald's own description
of how he developed the 2.3 network drivers and interface (pci-netif). 
He disappears for many months, creates a design without interfacing with
kernel developers, and then appears again with a code drop.

It is classic cathedral style of development.  Read Eric Raymond's paper
on why the bazaar method is far, far superior.  The Linux kernel is the
bazaar method, and this is the central conflict which forced the kernel
and Donald drivers to diverge.

Yes, the end result of Donald's work is open source, but his development
is not open at all.  And therein lies the problem [which existed far
longer than I have been hacking on the net drivers...]

	Jeff



-- 
Jeff Garzik              | My to-do list is a function
Building 1024            | which approaches infinity.
MandrakeSoft, Inc.       |
-------------------------------------------------------------------
To unsubscribe send a message body containing "unsubscribe"
to linux-tulip-request@beowulf.org