From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "Pavel Roskin" <proski@gnu.org>
Cc: "Michael Renzmann" <mrenzmann@madwifi-project.org>,
madwifi-project@venema.h4ckr.net,
linux-wireless <linux-wireless@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [madwifi-project] [RFC] Closing the project
Date: Thu, 13 Nov 2008 12:54:07 -0800 [thread overview]
Message-ID: <43e72e890811131254q35ff4f48xf58c7c26d5c9a5a4@mail.gmail.com> (raw)
In-Reply-To: <1226609316.2904.18.camel@dv>
On Thu, Nov 13, 2008 at 12:48 PM, Pavel Roskin <proski@gnu.org> wrote:
> On Thu, 2008-11-13 at 11:42 -0800, Luis R. Rodriguez wrote:
>
>> > I think the biggest impediment to MadWifi development was not
>> > bureaucracy. It was the non-free HAL.
>>
>> Not really, even with an alternative people are still used to coding
>> with it and find it easier to commit into an svn repository than
>> submit patches upstream. Maybe our process is move involved but there
>> its also why Linux code has a certain quality in it. We tend to frown
>> upon crap. If MadWifi ever were to touch Linux it would be tainted
>> with CRAP.
>
> OK, HAL was not the only reason. Let's say there is good bureaucracy
> and bad bureaucracy. The difference is the former is helpful and the
> later is not. The kernel is an excellent example of good bureaucracy
> that we should learn from.
>
> It would be great to have a detailed analysis why MadWifi failed.
It didn't fail, it was just not the best approach to support Linux
from the start, that's why *today* its just silly to go on with it,
specially since the vendor involved is *contributing* and helping to
implement support the right way.
>> Just my advice: let MadWifi die already, stop wasting your time.
>
> I understand what you mean, but I have to deal with MadWifi anyway. As
> I said before, I'd rather share my fixes that keep them to myself.
Understood -- but perhaps you can identify what is lacking that you
need to better help push what is required and missing.
Luis
next prev parent reply other threads:[~2008-11-13 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2576.194.45.26.221.1226491274.squirrel@webmail.madwifi.org>
[not found] ` <1226511194.9952.38.camel@dv>
[not found] ` <43e72e890811121224w4fc53e1s29080a42111186e9@mail.gmail.com>
[not found] ` <1226547092.11785.49.camel@dv>
2008-11-13 19:42 ` Luis R. Rodriguez
2008-11-13 20:21 ` Stephen Clark
2008-11-13 20:38 ` Luis R. Rodriguez
2008-11-13 20:48 ` Pavel Roskin
2008-11-13 20:54 ` Luis R. Rodriguez [this message]
2008-11-13 21:11 ` Pavel Roskin
2008-11-13 23:26 ` Derek Smithies
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=43e72e890811131254q35ff4f48xf58c7c26d5c9a5a4@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=madwifi-project@venema.h4ckr.net \
--cc=mrenzmann@madwifi-project.org \
--cc=proski@gnu.org \
/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
all inboxes | Powered by JetHome®