Date: Sat, 13 Mar 2004 17:13:49 -0800
From: Andrew Morton <akpm@osdl.org>
To: "Woodruff, Robert J" <woody@co.intel.com>
Cc: torvalds@osdl.org, sam@ravnborg.org, greg@kroah.com, miller@techsource.com,
       riel@redhat.com, matti.aarnio@zmailer.org, hch@infradead.org,
       woody@jf.intel.com, linux-kernel@vger.kernel.org, sean.hefty@intel.com,
       jerrie.l.coffman@intel.com, arlin.r.davis@intel.com,
       marcelo.tosatti@cyclades.com
Subject: Re: PATCH - InfiniBand Access Layer (IBAL)
Message-Id: <20040313171349.07349e4a.akpm@osdl.org>
In-Reply-To: <1AC79F16F5C5284499BB9591B33D6F000B6306@orsmsx408.jf.intel.com>
References: <1AC79F16F5C5284499BB9591B33D6F000B6306@orsmsx408.jf.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1710
Lines: 34

"Woodruff, Robert J" <woody@co.intel.com> wrote:
>
> The Mellanox and Topspin folks along with some people from some of
>  the national labs are trying to start up a website called openib.org,
>  with data bases, email lists, etc. where people can submit code for
>  this "best of breed" stack and discuss it. As long as it is truly 
>  open, the linux community is allowed to participate, and the code
>  is evaluated on it's technical merits, rather than one companies
>  personal
>  agenda, this forum might serve as a way for us to sort through this
>  without
>  taking every issue to lkml. 

That is, of course, an excellent approach.

But beware of being *too* disconnected from the lists@vger.kernel.org.  We
don't want to get in the situation where you pop up with a couple of
person-years' worth of work and other kernel developers have major issues
with it.  Please find a balance - some way of regularly checkpointing.

Also, beware of aiming for a finished product.  We would *much* prefer that
a simple, minimal core, maybe with just a single device driver be merged
into the mainline kernel.  The IBAL developers then proceed to enhance
that, sending regular updates.  Every couple of weeks would suit.

That way everyone else can see the code evolving, and can help, and can
understand.  And other people will fix your bugs for you, and update your
code as kernel-wide changes are implemented.  And we all avoid nasty
surprises and extensive rework.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/