Changes between Version 44 and Version 45 of HardwareInfo/WirelessFirmwares

Timestamp:

Dec 31, 2009, 10:55:16 PM (15 years ago)

Author:

colin

Comment:

Finalizing first draft of mailing list proposal

HardwareInfo/WirelessFirmwares

@@ -118 +118 @@
  * Putting license into HAIKU_TOP/data/system/data/licenses/
  * Putting license in firmware directory /system/data/firmware/<driver name>/
- * Adding entry in AboutSystem
+ * Adding one entry per driver to the AboutSystem
 
 ==== Common firmware rules ====
@@ -127 +127 @@
 ==== Proposed handling of group 1 ====
  * Main issue is that the license requires that end users are taking notice of the license before using the firmware. [[BR]]
- * Colin, mmadia discussed the topic on distributing the firmware along with Haiku. 
+ * Mmadia and colin discussed the topic on distributing the firmware along with Haiku:
    * Based on the [http://www.intellinuxwireless.org/?n=faq&s=license#license_1 3 bullets] we are consensing that distributing and using the firmware out of the box is feasible. 
    * But installing and using it right during boot is problematic. The user *must* have a chance reading the license first. 
@@ -140 +140 @@
 
 ==== Proposed handling of group 3 ====
- * Main issue is that redistribution is forbidden. The proposed solution is to download and install the firmware once Haiku has booted. A script automating this process will be included in Haiku. 
- * TODO: How to trigger execution of this script? manual vs. automatic triggering
+ * Main issue is that redistribution is forbidden. 
+ * '''Proposed solution''': Shipping a script for downloading, preparing and installing the firmware. Thus allowing the user to install the firmware when he wants to.
+
+=== One to rule them all ===
+ * For a smooth user experience mmadia and colin are proposing a "super" script for installing firmware with a single click. It merges the scripts described for group 1 and 3.
+ * Advantages: 
+   * User doesn't need to know the difference between an Intel 2100, 2200, 2225,...
+   * Reuse script code be merging 4 scripts into one
+ * Disadvantages:
+   * You need to educate users about where to find this script. 
+     * '''Proposed solution''': Adding an "Installing more driver" section to the Welcome page.
+