From: James Ketrenos <jketreno@linux.intel.com>
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...
Date: Wed, 25 Jul 2007 01:01:16 -0700 [thread overview]
Message-ID: <46A7034C.6070006@linux.intel.com> (raw)
In-Reply-To: <46A69359.4030201@garzik.org>
Jeff Garzik wrote:
> Intel is definitely not releasing early and often" from the LKML perspective.
I agree the cadence to >>linux-wireless<< has been lacking. But Intel
is releasing early and often. You can check their GIT logs and snapshot
history as evidence of that.
I am very hopeful that the people working on the 802.11n and HT patches,
as well as the developers working on the iwlwifi drivers, will get their
patches together and submitted to linux-wireless for inclusion.
I am also hopeful that those patches will be evaluated on the merit and
value of the functionality they enable.
<soapbox>
If people on linux-wireless don't want contributors to go off and
spend weeks / months at a time working in another sandbox, on another
mailing list, or in a different development community, maybe the
general attitude and approach of the maintainers on linux-wireless
needs to be one which facilitates those individual's contributions,
and helps in encouraging them to do more in the future. Even if those
contributors work for a Big Hardware Vendor.
Working with a community should augment development, not complicate
it or become a burden to it. People should feel better about their
contributions after engaging in a thread in a community where one
of their patches is reviewed; they should feel like progress has been
made, their contributions have been shared, and now others can benefit
from them -- they should not walk away feeling demoralized and berated
for trying.
More often than not, my time on linux-wireless has left me feeling
like the later.
<soapbox/>
James
next prev parent reply other threads:[~2007-07-25 5:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 15:02 Request for help Axj
2007-07-24 16:12 ` John W. Linville
2007-07-24 18:29 ` [ipw3945-devel] " Stephen Clark
2007-07-24 20:30 ` John W. Linville
2007-07-24 21:13 ` Jeff Garzik
2007-07-25 1:15 ` James Ketrenos
2007-07-25 0:03 ` Jeff Garzik
2007-07-25 0:30 ` Stephen Clark
2007-07-25 0:35 ` David Miller
2007-07-25 0:43 ` Stephen Clark
2007-07-25 0:46 ` David Miller
2007-07-25 1:05 ` Stephen Clark
2007-07-25 1:18 ` David Miller
2007-07-25 1:23 ` Jeff Garzik
2007-07-25 1:29 ` Stephen Clark
2007-07-25 1:40 ` Jeff Garzik
2007-07-25 1:40 ` Jeff Garzik
2007-07-25 0:45 ` Maurizio Monge
2007-07-25 1:35 ` Jeff Garzik
2007-07-25 8:01 ` James Ketrenos [this message]
2007-07-25 14:50 ` John W. Linville
2007-07-27 12:36 ` Jeff Garzik
2007-07-25 14:46 ` John W. Linville
2007-07-25 15:19 ` Jeff Garzik
2007-07-25 9:32 ` Zhu Yi
2007-07-26 15:10 ` Axj
2007-07-26 16:22 ` Pavel Roskin
2007-07-27 6:34 ` Axj
2007-07-27 7:44 ` Zhu Yi
2007-07-27 8:48 ` Axj
[not found] ` <200707270848.l6R8mqkh004526@mi1.bluebottle.com>
2007-07-27 8:56 ` Zhu Yi
2007-07-27 9:10 ` Axj
2007-07-30 0:58 ` Zhu Yi
2007-08-01 6:40 ` Axj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46A7034C.6070006@linux.intel.com \
--to=jketreno@linux.intel.com \
--cc=Stephen.Clark@seclark.us \
--cc=axjslack@bluebottle.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).