User:DanielDrake/11.3.0 goals

These are my personal goals/plans for 11.3.0, for discussion.

Budget: 10-12 hours per week

Image size reduction - particularly for XO-1

• Remove mesa-dri-drivers
• Remove cracklib dicts? linux-firmware?
• Move to ubifs again, but use zlib compression
• In boot partition on signed images, use signed files even in unsigned mode, no need to store unsigned copies

Network stability

• XO-1 not connecting on reboot, consistently need to click once
• Check for optimal programming speed of encryption keys, needed for reliable WPA1 (revisit the libertas work from 8.2.1 that was never carried forward)
• usb_reset() needlessly called on XO-1 wifi during resume - causes light to blink
• <trac>11062</trac>: XO-1 actrd can't connect to some access points
• <trac>9153</trac>: XO no longer tries to connect wlan after resume from suspend
• <trac>10971</trac>: Failure to automatically reconnect to Sugar Ad-hoc network
• <trac>10725</trac>: Sugar Ad-hoc network: reconnect after suspend
• <trac>10366</trac>: idle suspend causes network connection in progress to fail
• <trac>10543</trac>: Wireless disabled but Sugar Ad-hoc icons present when switching back from GNOME
• <trac>10549</trac>: Disabling the "Radio" in Sugar disables ability to use any networking adapter
• <trac>10694</trac>: After XO-1 sleep, there is a 3-4min delay before wireless access points appear
• <trac>10780</trac>: Sugar Network view looses track of available networks but iwlist is fine
• <trac>10232</trac>: WiFi dies on suspended XO-1, os300
• <trac>10375</trac>: Lid close/open turns on WiFi on suspended XO-1
• <trac>10627</trac>: os5, XO-1: Network fails to reconnect after suspend
• (many of the above tickets overlap greatly)

Misc low-level

• <trac>10967</trac>: Synaptics touchpad may result in spurious PS/2 mouse data upon resume
• <trac>10568</trac>: XO-1 graphical boot hangs if SISUSB VGA adapter attached

Release management, deployment and community engagement

• Continue weekly triage meetings, even if not so triage-orientated
• Invite Chris Leonard to weekly meetings for better coordination with localization efforts
• Document out how localization interacts with the release process (when do string freezes happen? who announces them? etc.)
• Try to get a couple of teams meeting on a weekly basis for testing and awareness (Nicaragua & La Rioja?)
• Look closely and prioritise pending requests from responsive deployments, encourage more of this