Features Download
From: Michael Renzmann <madwifi <at> nospam.otaku42.de>
Subject: HEADS UP: Important project changes
Newsgroups: gmane.linux.drivers.madwifi.user
Date: Friday 21st October 2005 21:10:31 UTC (over 12 years ago)
Hi all.

Please read this mail carefully. It is going to be a long text, but it
contains a lot of important information about changes to the project
that immediately take effect.

Summary of changes:
1. The project will move most of its services away from sourceforge.net.
Our new home is http://madwifi.org [1], which has been
launched today.

2. We re-introduce web-based project management. Tracking bug reports,
submitted patches and feature requests will be handled by Trac [2] from
now on. The Trac interface also consolidate web access to the code
repository and the documentation wiki.

3. The code repository has been switched from CVS to Subversion.

4. The long awaited code from Atheros is now publically available and
will be used for all further developments from now on. The old codebase
will be phased out as soon as the new code has been stabilized and
missing features have been ported.

Now for a more verbose explanation.

Madwifi's new home
As has been discussed [3] a few weeks ago on madwifi-devel, this project
is facing several problems: lack of project management, lack of
documentation, lack of transparency, lack of developers, lack of

It has been decided to free up otherwise bound resources by
(re-)introducing a bunch of tools to ease project management: Trac [2].
While Sourceforge also offers tools for this purpose, the functions
provided by Trac seem to be by far superiour and easier to use. Refer to
the above mentioned thread for a more detailed description.

The move is now finished. We like to thank the sponsor of the server and
bandwidth (true global communications GmbH [4]) and of the domain name
(Alvin Olga [5]) for their support.

Better project management facility
As mentioned above, Trac and Subversion proofed to be a great set of
tools, worth the work to switch a project over to both.

By now, we asked users to work with the mailing lists in order to
provide bug reports, patches or feature requests. But mailing lists make
it hard to track the current status of any of these submissions - for
the users as well as the developers. You most probably noticed this in
various ways, by not getting replies to your reports for example. A very
unsatisfying situtation, we understand that.

The new website offers web-based trackers for bug reports, patches and
feature requests. It will be much easier to check the current status of
any reported item, to tell if anyone (and who) is working on them, and
so on.

The currently open tickets (a ticket is an items in the tracker
facility) can be checked at [7]. More information about how to use the
trackers are available at [8].

Most parts of the documentation wiki have already been ported to the
Trac wiki, see [9]. The missing parts will be moved soon - please be

The project still is out of any documentation for developers. A first
meassure to help newbies getting used to the driver source might be the
new cross reference [10]. This reference is automatically generated once
per hour, based on the bleeding edge code of the driver.

Tarballs of the current code are now offered at
http://snapshots.madwifi.org. These
tarballs are for the new codebase
(see below). The CVS snapshot archive [11] will be available for some
time, but will be regarded as being deprecated.

Transition from CVS to Subversion
Subversion is often said to be the successor of CVS. While this isn't
correct, Subversion has already proofed to be superiour over CVS, making
it worth to switch over to it.

This transition has been completed sucessfully. The new repository can
be found at [6], and the repository layout basically follows the
suggestions given here [12] (main development happens in trunk/,
branches are stored in branches/, tags are stored in tags/).

Web access to the full repository is provided via Trac, see [13].

The old CVS repository over at SourceForge is still available, but
deprecated. Write access to that repository has been turned off a few
days ago. The complete (old) madwifi source base, including the history,
has been imported to the Subversion repository, and can be found at
cvs-import/ (see also: [14]).

Switching to the new code
Last but not least something that already has caused some confusion (and
probably will continue to cause confusion for a few days - I'm very
sorry for that).

Much has been spoken about the new code that Atheros announced a few
months ago. The new functions and the extended support for all currently
known Atheros chipsets are features eagerly awaited by a lot of people.

A few weeks ago half-public testing of this code was started. The
purpose of this phase was to find the most obvious bugs and remove them
before making the code publically available.

Then, by the beginning of this week, I decided to publish the new code.
In the announcement that I've sent to this list I spoke of "madwifi-ng",
the next generation of Madwifi. After sending out this mail, Bruno
convinced me that it would be better to finalize the outstanding work
for madwifi.org, in order to allow a proper switch to the new code.
Which is what we worked on during the last days.

This means:
The new code, which has been refered to as madwifi-ng, becomes the new
codebase for Madwifi. All future development will be based on this code.
Missing features will be ported from the "old code". This code has been
put in the trunk/ of the new Subversion repository.

The old code, that's basically the code that has been hosted in the CVS
repository up to now, will be freezed. Apart from fixing severe bugs no
changes will be applied to it. This code has been put in the
"madwifi-old" branch, available at branches/madwifi-old in the new
Subversion repository.

People who use Madwifi in a productive environment should stick with
madwifi-old for now, until the new code stabilized enough for production
use. Anyone else is encouraged to try the new code, which will help us
to weed out remaining bugs. We hope to come to a stable state soon,
which will end up in the first production release of Madwifi.

In case you're still confused you might want to take a look at [15].
This hopefully clears things up. If not, feel free to ask.

Final words
We hope that the new website will improve the productivity of users as
well as of developers, and that it will become a lot easier for
interested parties to contribute to the driver. We're sorry for any
inconvenience that these steps might cause to anyone, but we're also
convinced that the result will compensate that.

Last but not least: we want to hear about your oppinion. What do you
think about madwifi.org? Do you have any ideas for further improvements?
Would you like to help out? Please, speak up!

[1] http://madwifi.org
[2] http://www.edgewall.com/trac/
[3] http://article.gmane.org/gmane.linux.drivers.madwifi.devel/1421
[4] http://www.tgc.de
[5] http://madwifi.net/
[6] http://svn.madwifi.net
[7] http://madwifi.org/report/1
[8] http://madwifi.org/wiki/TracReports
[9] http://madwifi.org/wiki
[10] http://lxr.madwifi.org
[11] http://madwifi.otaku42.de
[12] http://svnbook.red-bean.com/en/1.1/ch04s07.html#svn-ch-4-sect-7.1
[13] http://madwifi.org/browser
[14] http://madwifi.org/browser/cvs-import
[15] http://madwifi.org/wiki/NewCodebase

Thanks for your attention.

Bye, Mike

PS: I'll be offline until monday, so answers from me might take a little
longer. Sorry, but I need to take a break now :)
Sign EDRI petition against data retention:
My key: http://keys.indymedia.org/cgi-bin/lookup?op=get&search=62C29B94
Fingerprint: BC2E 79BF 0C8F 0282 864B 9CEC 8343 5169 62C2 9B94

This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
CD: 3ms