linux-kernel - Re: [madwifi-project] [RFC] Closing the project

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1226609316.2904.18.camel@dv>
Date:	Thu, 13 Nov 2008 15:48:36 -0500
From:	Pavel Roskin <proski@....org>
To:	"Luis R. Rodriguez" <mcgrof@...il.com>
Cc:	Michael Renzmann <mrenzmann@...wifi-project.org>,
	madwifi-project@...ts.madwifi-project.org,
	linux-wireless <linux-wireless@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [madwifi-project] [RFC] Closing the project

On Thu, 2008-11-13 at 11:42 -0800, Luis R. Rodriguez wrote:

> We will be working on DFS on mac80211, I will start first with STA
> DFS. Also expect a lot of work from us on AP support.

That's great news!

> >> I think MadWifi has become a big bureaucratic entity and this large
> >> bureaucracy is simply not needed.
> >
> > I agree that we have a lot of documentation that is becoming irrelevant.
> > I prefer to keep documentation to the minimum, as it stimulates
> > developers to write software that just works, without lengthy
> > instructions.
> >
> > But the bug tracking system has some important information that we still
> > may need.
> >
> > 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
would be useful for other projects.  I'm short on time to do it right
now, but I may do it later.

I think we should have done more to prevent incomplete or broken changes
from being committed.  The reason I cannot backport SMP fixes is because
they were committed as series of commits that involved other issues as
well.  Such sloppiness should have been prevented.

> 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.

-- 
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/