I may have missed the point on this as I have not experienced non-functional wifi in antiX.anticapitalista wrote: 2. Include more development libraries/applications for users that need to build for wifi and don't have any other way to connect.
That would mean including for example build-essential fakeroot (adds about 20MB to live iso).
Scenario
An unskilled user, via another OS, downloads antiX to try. Bootable media is created and used to boot a machine with only a wifi adaptor. Following a successful bootup, network connectivity is not available. At this point, due to lack of knowledge, the user is stumped and requires guidance. The issue becomes a question of how easy it is to find the guidance, the clarity of the advice it provides and how easy it is to conduct. (See Note:1)
The guidance might steer the user through using apps such as using Ceni, Wicd Network Manager and Windows Wireless Drivers, which might not produce optimal performance. If all these fail to produce a working result, the next step might be to try building a driver from source.
If building is required, any additional development libraries/applications are not useful until the source files are obtained.
Suggestions
The additional development libraries/applications are not included in the ISO but are packaged as a .deb.
The guidance is included within the ISO.
Having reached the point within the guidance that building a driver from source is required, it might suggest obtaining the most recent sources from the manufacturer's website via the other working OS. It could continue by offering antiX specific advice such as:
* How to identify the adaptor chipset
* How to download the .deb containing the additional development libraries/applications
* How to install the .deb via GDebi Package Installer
* How to start the building process
* How to use resulting driver
All of the above is likely to occupy less than 20MB in the ISO.
How well antiX is perceived in terms of out-of-the-box wifi support also depends on the range of devices supported within the kernel. I would prefer that drivers within the staging area are not included as by definition, they are deemed not to have reached a suitable quality standard and are still undergoing testing. Regular antiX kernel updates that include drivers which have been fully tested and moved out of the staging area will help provide the most reliable user experience.
Notes:
1. The guidance will be most effective if it is able to be followed by the widest readership. To this end I suggest that they are written:
* at a very basic level
* using non technical languge
* in an overtly friendly style
* aimed at a target reader with no Linux experience