Talk:Feature roadmap

Comments and suggestions welcome!

Record of items moved from Priorities from Engineering section

The following items were deleted from the engineering section. The resolution of them is noted here. In most cases I found a home for them in the main feature section.

#4662 needed for better activity capabilities.
GS - now covered in Trac as bug.

#2447 caps lock
GS - created feature request for this.

#1997 flashing in writer
GS - now covered in Trac as bug.

NAND Full
GS - moved to a feature in OS section.

http://lists.laptop.org/pipermail/devel/2008-July/016994.html new file sytem
GS - covered in file system requirement.

Fix all GPL issues and get sign off from FSF that we are fully compliant.
GS - Created new section and noted one bug ID.

Debug tool that easily allows plug of diagnostic USB stick which analyzes and reports back detailed status.
GS - Created new feature for this. Owner = Erik

GS - Moved suggestions from Jim and Gary re: preventing memory crashes to out of memory requirement.

GS - Folded two clipboard redesign URLs in to single place.

GS - Deleted point 6 (power) from Ben's e-mail as its covered in power section.

GS - Removed point 2 (OS updates) from Ben's e-mail. Its covered in http://wiki.laptop.org/go/Feature_roadmap#Security.2C_activation_and_deployability section.

Easy update for G1G1
GS - Covered in GUI OS Updates feature.

Replacement file system
GS - Created new feature in OS section.

GS - Moved S page XUL Runner update suggestion to feature in activity section: browse multimedia.

SCIM from Sayamindu to do list
GS - Moved to SCIM feature in localization section.

eBook reader suggestions from Sayamindu GS - covered in better ebook reader requirement.

Improved battery life

"battery life" has two meanings and it would be best to separate them so as to not give the impression that a given usage pattern will see improvement:

1. how long will the battery operate the XO while it is doing useful work (backlight on at -- say -- middle intensity setting and continuous user interaction in -- for example -- write).
2. how long will the battery allow the XO to retain work (or state or however you want to say it) while the XO is suspended.

These are questions which impact different parts of the XO hardware/software implementation and one is more or less important than the other in each deployment. (Example: if a school has intermittent electrical power, it may be possible to gang-charge batteries but not to operate the XOs from the power line for the entire school day. In that case, doing useful work from battery power for as long as possible is critical. In some other deployment, the XO might only be used in the class for a few minutes at a time throughout the day but needs to be instant-on. In that case, suspend time improvements are critical.) -- Davewa 17:09, 20 October 2008 (UTC)