John W. Linville wrote:
On Tue, Jul 24, 2007 at 02:29:23PM -0400, Stephen Clark wrote:
Just being a user I am not sure what you mean by come back to working
with community? None of
their stuff is hidden is it? Does "the community" make it so hard to get
stuff included that it is
not worth the pain for Intel?
Very simple -- conduct mac80211 development in public on a mailing
list appropriate to discussion of an in-kernel component rather than
hiding on a mailing list that is ostensibly for development of a
specific driver. As the authors of the patches it is incumbent on
Intel to post them for inclusion upstream. That is the price of good
citizenship in the Linux community.
Not just that... it's good engineering.
Wireless driver patches that don't make it rapidly to linux-wireless and
upstream rapidly fester. It becomes a real engineering challenge to
sync up with upstream, if you don't make that your primary task to begin
with.
There is a reason why we say "release early, release often." If
wireless developers don't hear from Intel on a regular basis, the
codebases will diverge, wireless hackers will not get the useful
feedback they need, and Intel hackers will not get the useful feedback
they need.
Open source isn't just about a source code license. This is an
-engineering process-. Post -> [merge | revise based on feedback ] ->
<infinity>. The lower the frequency of posting and community
interaction, the less you are actually participating in key portions of
the engineering process.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
