Message-ID: <46A6A447.2080903@linux.intel.com>
Date: Tue, 24 Jul 2007 18:15:51 -0700
From: James Ketrenos <jketreno@linux.intel.com>
MIME-Version: 1.0
To: Jeff Garzik <jeff@garzik.org>
CC: "John W. Linville" <linville@tuxdriver.com>,
	Stephen Clark <Stephen.Clark@seclark.us>,
	ipw3945-devel@lists.sourceforge.net,
	linux-wireless@vger.kernel.org, Axj <axjslack@bluebottle.com>
Subject: Re: [ipw3945-devel] Request for help...
References: <1185289332.46a61474a444c@mail.bluebottle.com>	<20070724161226.GA24344@tuxdriver.com>	<46A64503.1080003@seclark.us>	<20070724203035.GG24344@tuxdriver.com> <46A66B63.6030006@garzik.org>
In-Reply-To: <46A66B63.6030006@garzik.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Sender: linux-wireless-owner@vger.kernel.org

Jeff Garzik wrote:

> There is a reason why we say "release early, release often."  If 
> wireless developers don't hear from Intel on a regular basis,

The "community" vs. "Intel" slant is really getting old.  

*WE* are part of the community.  *WE* have submitted patches.  
*WE* have done work to bring wireless forward.  *WE* are wireless 
developers.

It isn't Intel's fault that certain people have historically 
made it so difficult to get code to into wireless-dev's mac80211 
(and eventually *maybe* upstream) that contributors have decided 
to focus on getting their code out to users through other means.

A version of mac80211 being available out-of-tree with features 
not found in wireless-dev isn't the problem.  The problem is that 
people have made it too difficult to innovate and develop in 
wireless-dev.

*That* needs to change.

James