Feature roadmap: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
 
(111 intermediate revisions by 5 users not shown)
Line 1: Line 1:
<b><font color=red><big>For current information on OLPC's feature planning process, see [[Release Process Home]].</big></font></b>

{{Deprecated}}
{{RightTOC}}
{{RightTOC}}
{{OLPC}}


= Overview =
= Overview =
This page goes hand-in-hand with the [[Feature requests]] page, as follows:
This page intends to layout a long term strategy for prioritizing software development on the XO. Feature lists for individual releases will appear on their respective pages as listed features get prioritized, scoped and a targeted. In addition to outlining goals and strategies, an extensive feature roadmap is maintained on this page. This page goes hand-in-hand with the [[Feature requests]] page, as follows:


;1. [[Feature requests]] : Features, requirements and requests by country. This page contains verbatim requests from technical leads or translated and reviewed rewrites of initial feedback. Only items specifically requested by a qualified technical lead, administrator, teacher or student in the country should go in this section. See also: [[Deployments]]
;1. [[Feature requests]] : Features, requirements and requests by country. This page contains verbatim requests from technical leads or translated and reviewed rewrites of initial feedback. Only items specifically requested by a qualified technical lead, administrator, teacher or student in the country should go in this section. See also: [[Deployments]]


;2. [[Feature roadmap]] : Feature suggestions by technical strategy. Each item on this page should include reference to the;Requester: (e.g. country or engineer or URLs to relevant discussions and sites). It should also include a reference to which element of the strategy it fits in to (if available).
;2. [[Feature roadmap]] : Feature suggestions by technical strategy. Each item on this page should include reference to the;Requester: (e.g. country or engineer or URLs to relevant discussions and sites). It should also include a reference to which element of the strategy it fits in to (if available).

Features are prioritized based solely on their value towards achieving the goals and executing the strategy. The amount of effort required and the availability of engineers to expend such effort is not included in the prioritization decision. The engineering and test work, the availability of relevant software and the available resources will be added as critical decision factors when determining what features are delivered in each release. This page is meant to be abstracted from releases and it should therefore include a superset of priorities for any given release.


== Suggestions for providing input ==
== Suggestions for providing input ==
# Please sign in to the wiki when updating this page so we know who made the edits.
# Please sign in to the wiki when updating this page and its subpages so we know who made the edits.
# Raw, unfiltered feedback from countries and deployments should go on the [[Feature requests]] page.
# Raw, unfiltered feedback from countries and deployments should go on the [[Feature requests]] page.
# Feel free to add to this page following the guidelines described above.
# Feel free to add to this page following the guidelines described above. You can add a subsection to [[#General comments]] below, or add to [[Talk:{{PAGENAME}}|this page's discussion page]].
# To comment on a particular feature, click the feature's title to go to its subpage, then comment on its discussion page.
# Comments on the submissions of others are best provided on the [[Talk:Feature_roadmap| discussion page]], or the discussion page for that particular section.
# Edits to original submissions should be discussed with the original poster beforehand.
# Before editing the subpage for a particular feature, , discuss your edits with the original poster /owner beforehand.
# You must use the template correctly when requesting features or enhancements, otherwise your feature won't show up. Follow [[#Adding to the roadmap]] carefully
# Follow the template when [[Feature roadmap#Adding_to_the_roadmap|Requesting Features or Enhancements]].
# Use the [[Template:Trac|trac template]] when referencing tickets/bugs.
# Use <nowiki><trac></nowiki> when referencing tickets/bugs.
# Additional suggestions for providing input are welcome.
# Additional suggestions for providing input are welcome.
# Create a new section (At the <nowiki>== header 2 ==</nowiki> level) for your country or request if none present are adequate.
# Create a new section (At the <nowiki>== header 2 ==</nowiki> level) for your country or request if none present are adequate.
Line 25: Line 25:
= Roadmap =
= Roadmap =


This section lists major features to be added to XO software over time.
==Adding to the roadmap==

This section lists major features to be added to Sugar over time. Each request should use the [[Template:Feature request| feature request template]] (you can copy/paste from below), providing as much information as possible. Direct feedback from countries and deployments should be provided on the [[Feature requests]] page instead.
<br>''Please sign in to the wiki before adding or editing feature requests.''


== All features ==
<pre>
Click on the arrows in any heading to re-sort by that heading.
{{Feature_request
{{#ask:
|Name=
[[Category:Software features]] [[Is part of::+]]
|Requesters=
|?Is part of=Area
|Requirements=
|?=Feature
|Specification=
|?Requested by=Requested by
|Owners=
|?Helps deployability#yes,-=Helps deploy
|?Target for 9.1#yes,no
|?Contact person=Owner(s)
|?Priority
|sort=Is part of
|mainlabel=-
|limit=200
|default=Nothing found in [[:Category:Software features]] with [[Property:Is part of]]?!
}}
}}
</pre>


== Other queries ==
The elements of such a request are described below. The text for these elements may be listed on the same line as the parameter, just after the equals (=) sign, or on the following line(s). Where appropriate, please use numbered or bulleted lists to identify individual requirements or specification ideas.
[[{{PAGENAME}}/Page of all features that target 9.1.0]] embeds all the pages with [[Property:Target for 9.1|Target for 9.1]] set to "yes".


See [[Features-test]] for other queries, you can add your own to it or copy them to other pages.
; Name : A brief, one-line summary of the feature, used as the title on the page
; Requesters : Deployments, engineers, or both who support the request
; Requirements : User level requirement definition; Links to detailed wiki pages, mailing list threads, or other resources are welcome
; Specification : Design and technical implementation ideas; Links to detailed wiki pages, mailing list threads, or other resources are welcome
; Owners : Names of developers and/or champions of the request who will ensure that progress is made


See also: [[Feature_roadmap#Suggestions for providing input|general suggestions for providing input]].


== Activity-related work ==


==Adding to the roadmap==
{{Feature_request
When adding a new feature please follow these guidelines.
|Name=New activities
|Requesters=Birmingham, Juliano
|Requirements=
From Birmingham:
*Firefox, Flash, mplayer
*A spreadsheet (I'm going to use gnumeric until Socialcalc is ready for production)
*A more full featured pdf reader (yes, I know there's the Read activity, but I'm planning on installing the full evince and making sure Firefox can open PDFs with it)
*A document editor the user can insert images into (the full Abiword would be great for this, but the current workaround [after editing a file] is to open write, then hit ctrl+n)
From Juliano:
*More development environments.
*Better Flash support. Minimum on par with FF on XP. From test report by Emiliano and thread on sur list.
|Specification=
|Owners=
}}


# Make sure the feature doesn't already exist
{{Feature_request
# Read the Usage section of [[Template:Feature tracking]] for help filling out the template on the new page
|Name=Browse update and multi-media
# Pick a "Feature subcategory" from [[:Category:Software features]]
|Requesters=[[User:Skierpage]]
# Find the requester(s)' wiki pages and the feature owner's User: wiki page
|Requirements=
# Change ''Good feature name'' to your new subpage title, following the [[OLPC:Style guide]] for page names
* Wikipedia articles and thus [[Wikislices]] can take advantage of this, and richer multimedia in Browse becomes practical.
# Ready? Click the button below to create a new wiki subpage with the right title convention that's prefilled from [[Template:Feature tracking/Preload]], edit it to suit, then save. After a delay (due to wiki query and page caching), your new subpage will appear in lists of features.
<inputbox>
type=create
preload=Template:Feature tracking/Preload
buttonlabel=Create a new Feature roadmap subpage.
default=Feature roadmap/Good feature name
width=40
bgcolor=#f0f0ff
</inputbox>


A description of each field is listed here: <br>
|Specification=
; Requesters : Deployments, engineers, or both who support the request
* [[XULRunner]] 1.9.1, the Mozilla code powering [http://developer.mozilla.org/en/Firefox_3.1_for_developers Firefox 3.1], should be released in the 9.1.0 timeframe.
; Requirements : User level requirement definition; Links to detailed wiki pages, mailing list threads, or other resources are welcome
; Specification : Design and technical implementation ideas; Links to detailed wiki pages, mailing list threads, or other resources are welcome
; Owners : Names of developers and/or champions of the request who will ensure that progress is made
; Priority : 1-5 (1 = Critical, 2 = High, 3 = Medium, 4 = Low, 5 = not needed)
; Helps deployability : yes or no Better deployability is the goal of [[9.1.0]]. Set to "yes" if the feature helps that goal, regardless of its "target 9.1.0" status.
; Target for 9.1 : yes or no "yes" means that an OLPC engineer is (or will be) assigned to work on this for 9.1.0 release.


See also: [[#Suggestions for providing input|general suggestions for providing input]].
* Activities and content can use its new features, at the risk of incompatibility with earlier Sugar releases.


=== Adding a category ===
* XULRunner 1.9.1 supports the HTML5 <audio> and <video> tags, providing the ability to play [[OGG]] audio and video files natively in the browser.
Only do this with careful forethought and a confirmation on the wiki gang list http://lists.laptop.org/pipermail/wiki-gang/>
This will probably improve performance and reduce memory footprint compared with embedding the [[Totem plugin]], the trade-off needs to be tested and Browse configured accordingly.


1. Mention the new category name in the template:
|Owners=
|Feature subcategory=''Easter eggs''
}}
2. Be sure to create the subcategory: edit the category's page (Category:''Easter eggs'') and add
<tt><nowiki>[[Category:Software features]]</nowiki></tt> to it.


If you forget #2, some queries will omit the page and people may have a hard time finding your new feature subcategory.
{{Feature_request
|Name=Single Sign on from Browse
|Requesters=Reuben
|Requirements=
* Must allow XOs to pass their identity to the XS so that the XS recognizes them without the need for them to login.
* Must pass that info in Browse in such a way that the XS HTTP server can recognize and extract the info for use in CGI scripting.
* Must be encrypted and unique information so that other browsers can't "spoof" and appear to be the XO.
* Must work with the back and restore feature so an XO and only the relevant XO "automatically" see and restore their own backed up files.
|Specification=
|Owners=Greg
}}


=== Documentation on semantic templates ===
{{Feature_request
{{SMW for software features}}
|Name=Better eBook reader
|Requesters=Birmingham, Haiti, Devel thread
|Requirements=
* Description of challenges here: http://lists.laptop.org/pipermail/devel/2008-October/020662.html See the rest of the thread too.
*A more full featured pdf reader (yes, I know there's the Read activity, but I'm planning on installing the full evince and making sure Firefox can open PDFs with it) (comment from Birmingham)
* Must not copy the PDF or other book format so that it takes up twice the NADN space.
* Must support PDF, plain text and .cbr files (any other must have formats?)
* Must open book directly from Journal
* Must "remember" the page you are on when restarting.
* Must allow opening the reader then browsing available books (can do this in web browser but needs the ability to look at the NAND to see what is available).


When you fill in [[Template:Feature tracking]] on one of the feature roadmap sub-pages, the template both ''displays'' the feature's information in a basic table (using {{tl|Definition table}}) and makes ''semantic annotations'' for many of the template fields &mdash; assigning values to properties such as [[Property:Requested by]]. That allows this page and others (such as [[Features-test]]) to query for and display these properties.
Desired improvements
* ability to do page mode as well as continuous mode (move an entire page at a time)
* ability to specify columns and move through a document down the columns
* ability to specify the amount of overlap when paging in continuous mode
* ability to zoom to 'fit text on screen' as opposed to 'fit page on screen' to eliminate borders from pages.

|Specification=
Possible support eVince:
http://live.gnome.org/Evince/SupportedDocumentFormats per Jim e-mail: http://lists.laptop.org/pipermail/devel/2008-October/020719.html
?
|Owners=
Greg
}}


{{Feature_request
|Name=Sugarized color picker
|Requesters=Juliano
|Requirements=
A better color picker in Paint & Write. Current one "...is made for professionals to get the HTML code of the color, but it also leads to error since people need to select the color in the circle and then in the triangle. It is giving bad time to people around here [Rwanda]". ''From Juliano in e-mail 9/1''
|Specification=
|Owners=
}}

{{Feature_request
|Name=Easy "Sugarization"
|Requesters=Wanda, David
|Requirements=
* Support for standard desktop applications in Sugar
* Make it easy to sugarize third party applications. It should be trivial to take an existing application which runs on Fedora (or other Linux too?) and install and run it on the XO. The basic sugarization interface for that should be usable by a non-programmer. Not all sugar features need to be enabled (will define exact list if this gets to requirements definition stage). Additional sugar capability may require programming (e.g. collaboration). The goal is to allow deployments to use any state of the art application available in Linux/Fedora.
* Secondarily, make it easy to do the same for web based applications (Google Gears, Picasa, etc.). tbd if this needs to include client side Java support.
* Allow easy creation of content bundles out of PDFs and HTML (other?). Should be as easy for a non-programmer as that described above.
* Must "work well" in Sugar. There may be some applications that work but don't use the journal (e.g. Scratch) and that may be acceptable. A definition of how well an activity works or a definition of "well sugarized" is needed. First comments on this are at: http://wiki.laptop.org/go/Educational_activity_guidelines
* Product management and Learning teams must come up with 5 - 10 applications which will be the first targets.

|Specification=
* See related X-windows threads on devel (links and references appreciated). This may also impact datastore and other areas.
* Replace matchbox with something more friendlier to standard desktop applications
* Support for .desktop files in the launcher list
* Support startup-notification
* Support standard application icons on the frame

|Owners=Greg^
}}

{{Feature_request
|Name=Concept Maps
|Requesters=Panama and OLPC Sur
|Requirements=
* Support a concept maps making application. Can be on XS or Internet or XO only
* First choice is CMap Tools, but other Concept Map options are welcome too if CMap can't be easily implemented.

|Specification=
* See some of the options and available tools at: http://lists.laptop.org/pipermail/devel/2008-September/018811.html

|Owners=
Greg
}}

{{Feature_request
|Name=Terminal improvements
|Requesters=Sayamindu
|Requirements=
* Copy paste and drag and drop support enhancements
* Pippyfication (ticket #5543)
* Better handling of "Run as root in the UI"

|Specification=

|Owners=
Sayamindu
}}

== Power management ==

{{Feature_request
|Name=Improved battery life
|Requesters=Kim, Carla, Gnu, Ethiopia, Juliano
|Requirements=A list of UI actions which may affect power usage: [[Requirements#Power Management Requirements]] Our job is to increase battery life in as many modes as possible.
|Specification=
Background on power draw including a break down watts used in different modes:
* [[XO Power Draw#The Numbers]]
* [[Per-Activity Power Usage]]

Significant technical actions (as suggested by John/Gnu) that could reduce the laptop's power draw:

* Allow users to disable the mesh: reduces power consumption of the WiFi chip, allows the WiFi chip to enter power-save mode, and most importantly, allows lid-closed suspend to totally power off the WiFi chip. <trac>6955</trac>

* Put the EC into deep sleep when in a lid-closed suspend. This will cut its power from about 60ma to about 20ma (check with rsmith), which would further increase the duration of a lid-closed suspend before the battery drains.

* Speed up Resume, which currently takes more than 1000 ms. A cheap shot at this is to unload the USB bus modules. The Extreme power management setting was supposed to do this ("USB-disabling") but it doesn't yet. This would make auto-suspends much less visible to the interactive performance of the laptop, probably cutting the resume time to 500ms, which would let us enable auto-suspend in more circumstances. Beyond this cheap hack, we should actually fix the USB drivers so that you CAN be using the USB -- the wifi/mesh in particular -- and still not hang for half a second uselessly on every resume. <trac>8916</trac>, <trac>7384</trac>

* Fix serious bugs in resume and networking. These have so far prevented us from turning on autosuspend by default for three major releases (650, update.1, and 8.2.0), and in each release, we decide at the last minute that we can't fix these bugs because it's too late in the release cycle and we didn't fix them earlier. Multicast, ARP, mDNS, the Presence Service, and collaboration must all work in the presence of autosuspend. Much work has gone into fixing these, but neither the final nits, nor polish, nor system-level testing in a network testbed, has occurred.

* Reduce packet traffic during sharing -- particularly multicast traffic, which loads many machines (and wakes them up from autosuspend). This will require diagnosis and improvement of the presence and collaboration protocols. Some work was done on this, after the high packet traffic melted the WiFi bandwidth in early deployments (e.g. turn on 30 laptops in the mesh, none of them can usefully get anything done), but our main response was to tell later deployments "Don't use the mesh, use access points" -- a significant reversal that we should keep working to fix.

* Allow the kernel to set a timer and wake up from suspend after a pre-set interval. The lack of this prevents autosuspend from being able to power down and then power back up to meet a deadline (set by ohm or by any ordinary process). This may require EC work. <trac>4606</trac>

* Improve cpu idle detection. Currently we can't auto-suspend very often (only after >1 minute of no user interaction) because suspend is so heavy-handed. The cpuidle infrastructure in the kernel should be able to tell us when it's safe to suspend because no process wants access to the CPU for the next few seconds. Most of the pieces are there.

* Reduce useless polling by kernel, daemons, and activities. There's still a major Python bug that causes multi-threaded pyGTK2 programs to poll uselessly once a second (<trac>4680</trac>, <trac>4677</trac>). Much work was done to close it, but there is still a small sprint required to get it done. This not only reduces power use directly, but also allows the system to suspend because it doesn't appear that activities need to do some work soon.

|Owners=Gnu, Chris, Greg^
}}

{{Feature_request
|Name=Shutdown menu
|Requesters=Haiti, Rwanda
|Requirements=The power button is currently underutilized. It should allow either shutdown or suspend of the laptop, with the help of an on-screen dialog or menu.
|Specification= See thread at: http://lists.laptop.org/pipermail/devel/2008-October/020530.html

|Owners=PGF, Greg^
}}


{{Feature_request
|Name=No power regressions
|Requesters=Greg, Ethiopia, Rwanda, Haiti. Also make sure that EC draws the minimum possible power when XO is actually shutdown.
|Requirements=Make sure power usage is not worse (needs more careful description) in next release.
|Specification= Tinderbox testing?

|Owners=Richard
}}

== Hardware support ==

{{Feature_request
|Name=Accurate touchpad
|Requesters=Carla, Rwanda, Ethiopia, Haiti
|Requirements=[[User talk:Gregorio#Priorities from Carla]].
* Must not move the cursor when the user is not interacting with the touchpad.
* Must move the cursor the same distance for each drag across the pad.
* Must not recalibrate too often.
* Must enable a debug mode which shows when the touchpad is recalibrating and allows identification of XOs which are recalibrating too often.
|Specification= ?
|Owners=Wad, PGF, Greg^
}}

{{Feature_request
|Name= Grab/scroll keys
|Requesters= [[User:Garycmartin|Garycmartin]]
|Requirements=Provide view scrolling functionality with the grab/scroll hardware keys as documented in [http://wiki.laptop.org/go/OLPC_Human_Interface_Guidelines/The_Sugar_Interface/Input_Systems#Description_of_Keys Human interface guidelines].
|Specification= See [http://dev.laptop.org/ticket/447 trac 447] for a likely solution and patch.
|Owners=ericg?
}}

== Collaboration ==

{{Feature_request
|Name=Synchronous Collaboration
|Requesters= Carla and David, Teachers on OLPC-Sur, Peru technical leaders
|Requirements=See detailed collaboration requirements here: [[9.1.0 Collaboration Requirements]]
*Allow for intuitive mesh connection and activity-sharing.
*Must support first two use cases defined at: [[Use Cases#Collaboration Examples]]
*[[Requirements#Mesh / Connectivity_Requirements]]
*[[Requirements#AbiWord Sharing Requirements]]
* http://lists.laptop.org/pipermail/sugar/2008-July/007407.html
* May need to include that link in developer section below, tbd
|Specification=
* Ensure Gadget is correctly integrated and deployed in Sugar so we can avoid the troublesome shared roster haxks on the XMPP server
* Fix tubes so that peer to peer data is sent with peer to peer connections on the network where possible
* Fix the way JIDs are allocated to be more coherent and based on the child's nickname (also would benefit a lot from having hierachical DNS naming on the school server so each JID is globally unique)
* Expose JIDs in the UI and allow them to be typed in and approved by normal subscription requests, allowing collaboration with anyone whose JID you know
* Implement the Telepathy file transfer spec to enable that feature in Sugar
* Enable avatars in Sugar (although maybe not if we're doing link-local multicast on an XO mesh network) and maybe some UI for taking a photo and setting that as your avatar

See also: http://sugarlabs.org/go/DevelopmentTeam/0.84/Ideas#Glucose
|Owners= ^Greg
}}

{{Feature_request
|Name=Asynchronous collaboration
|Requesters= Juliano, Cynthia
|Requirements=

* Must allow students to post and work on projects together. One student can create something and share it with other students who edit it and save etc.
* Must allow development of projects using multiple applications (e.g. write documents, pictures, HTML, etc. needs full list). Juliano - "There is no way for group work for a couple of months in the same project using different activities."
* Must allow creation of project groups with edit and view privileges based on group membership.
* Must allow viewing of all projects and of projects filtered by various (needs definition) views. e.g. Juliano - "Even if the Neighborhood View show the currently shared projects, it will just show a subset of them, and just the ones that are currently being used"
* Must keep a history of who did what and when. Must include which groups worked on each project at different times.
* Must allow posting for viewing end result in school and publicly on the internet.
* Must allow "submitting" completed projects to teacher or otherwise setting a "completed" milestone.
* Must include out of band communication mechanisms. e.g. leave a message for other students saying "I updated frog project with new picture". This could be Chat, e-mail or other synchronous and asynchronous tools.
* Must allow working at home on XO and then synching up work with the latest shared version.
* Should included server based and non-server based solutions. That is, should not require a server in all cases.
* Provide a way to publish material to the world. related slightly to how edublog works now? see also robson's and juliano's interests here (from SJ).

* See related thread at: http://lists.laptop.org/pipermail/devel/2008-October/020588.html

|Specification=
|Owners= Greg^, Martin
}}

{{Feature_request
|Name=Scalable server-based presence
|Requesters=
|Requirements=Improve scalability of (ejabberd) server-based presence
* Complete [[Gadget]] implementation, which should hopefully fix our current scalabity issues and offer new features as activity and buddies search. '''(cassidy)'''
* Integrate Gadget in glucose. It will require work on several modules, including sugar-presence-service, sugar-toolkit and sugar. '''(cassidy, morgs)'''
* Integrate gadget in the Sugar UI. <trac>7711</trac> '''(erikos, eben)'''
|Specification=See [[Gadget integration TODO]] for more details.
|Owners=Guillaume Desmottes, Dafydd Harries, Eben Eliason, Morgan Collett
}}

{{Feature_request
|Name=Scalable Link-local presence
|Requesters=
|Requirements=Improve scalability of non server based presence
* Integrate Cerebro into Telepathy framework (Collabora)
* Extend Cerebro API to fit activity sharing requirements better (ypod)
* Drop into stack in place of Salut
|Specification=
|Owners=Morgan Collett, Sjoerd Simons, Elliott Fairweather, Polychronis Ypodimatopoulos
}}

{{Feature_request
|Name=Collaboration Groups
|Requesters=Peru
|Requirements={{trac|4043|Group support in gabble and salut}}
|Specification=
|Owners=Eben
}}

{{Feature_request
|Name=File sharing
|Requesters=Peru blog http://blog.stone-head.org/olpc-peru-a-silent-revolution/
|Requirements=A way to send objects from one XO to another without a USB key, and without sharing the activity. <br>
See also: http://wiki.laptop.org/go/Network_principles#Direct_XO-to-XO_serverless_communication. <br>
Greg's requirements definition: <br>
* Must allow moving an "object" (usually thought of as a file) from one XO to another.
* Must support all available network environments (e.g. Mesh, AP only, XS eJabberd)
* Should allow transferring files using the existing Sugar Neighborhood tools (e.g. put a file on the journal of any other user visible in the network neighborhood).
* Should allow moving an object to any XO visible over the network (AKA pingable) regardless of whether they are visible in the Neighborhood (due to bugs in collaboration or someone not collaborating or any other barrier which does not prevent ping).
* Should support queuing a file for transfer later. That is, add support for asynchronous sharing over time : the sharing of an effort should not require everyone to be online at once.
* Using file transfer must work in both Salut and Gabble,
* Allow Journal objects to be shared between buddies over link-local or Jabber
* Enable automatic activity downloading for shared activities that aren't installed on the joining machine
* Students and teachers have no good way to distribute files directly from one person's Journal to another. If all Activities that open a file do not implement Collaboration, then there is simply no way to transfer that file over the network.

|Specification=
* [[Specifications/Object_Transfers|XO to XO object transfer system]]. [[User:Eben|Eben]] 19:40, 19 September 2008 (UTC)
* Noted by SJ, possibly related to [[bundle (activity)]].
* A number of technical proof-of-concept programs have been written for distributing files, using methods like HTTP over stream tubes and Cerebro's Teleport. There is an excellent set of [[Specifications/Object_Transfers|UI mockups for this]] functionality.
* Additional links from Ben S.
** [[Read]]
** [http://lists.laptop.org/pipermail/sugar/2008-March/004499.html Distribute]
** [[Summer_of_Code/Ideas#Publication_and_Journal_sharing|A Summer of Code application]]
|Owners=Simon, Eben, Guillaume
}}

{{Feature_request
|Name="Candy Bag" or "Bulletin Board" activity
|Requesters=
|Requirements=Idea for a new activity: Candy Bag. You open a bag (i.e. you launch the CandyBag activity), then you put journal entries in it, then sharing this activity means that your friends can grab a candy in your bag. From: http://lists.laptop.org/pipermail/devel/2008-July/017459.html
|Specification=I'd be curious to see if there is a benefit to having a task like this manifested as an activity. It might work well. In fact, this might be the "Bulletin board" activity we've been wanting all along. There's also a design for a more embedded [[Specifications/Object_Transfers|XO to XO object transfer system]]. [[User:Eben|Eben]] 19:40, 19 September 2008 (UTC)
|Owners=
}}

== Performance ==

{{Feature_request
|Name=Faster activity launch and save
|Requesters=Peru, Uruguay
|Requirements=
* Must show glowing splash image which is seen after a click on an activity and before it launches in less than 300ms. This will increase performance and help prevent people from accidentally launching two instances of an activity.
* Must start all G1G1 activities (http://wiki.laptop.org/go/Activities/G1G1) from Home or the Journal in less than 5 seconds. Start means the the activity Menu bar is show and the cursor or other input device is active. May allow an additional 3 seconds if the activity is launched with a document (e.g. from the Journal).

|Specification=<trac>6472</trac>
|Owners=
}}

{{Feature_request
|Name=Faster task switching
|Requesters=Peru, Uruguay
|Requirements=
* Must change from one activity to another via keyboard (e.g. alt-tab) or via the Frame in less than 2 seconds.

|Specification=
|Owners=Erik
}}

{{Feature_request
|Name=General UI sluggishness
|Requesters=Uruguay, Peru
|Requirements=
* For all of the following, the times measured should apply when the XO is connected to a wireless AP and running Write with a file of less than 1 MB. This is used as a sample "state of the machine" definition. Other definitions of state of the machine are welcome and the performance when the XO is doing more (e.g. more activities open or moving data over the Wireless) should not degrade precipitously.
* The time between when the user interacts (e.g. clicks or enters a key stroke) when the result is visible on the screen should be less than 100ms. Specific cases are listed below and when the absolute number above is not achievable, a target percentage improvement is listed.

* The following are examples where think release 8.2 does not meet this requirement.
* Must be 80% faster than in 8.2 to show or hide the Frame.
* Must begin showing scroll operation results in the Journal 50% faster than we do now. That is from the time I click on the scroll bar until the image on the screen starts to move.
* Must copy and paste to the clipboard and show the clipboard icon in the Frame with the right type (text or image) of object 75% faster.
* Must open a Journal detail page 50% faster.
* Must show all icons when switching from one view to another (e.g. from Home to Neighborhood etc) 75% faster.
|Specification=From: http://lists.laptop.org/pipermail/sugar/2008-July/007471.html
|Owners=Marco, Erik
}}

== Reliability ==

{{Feature_request
|Name=Memory Pressure
|Requesters=Elana, Peru, Carla
|Requirements=
* http://sugarlabs.org/go/DevelopmentTeam/0.84/Reliability#Memory_bloat
* Should show the user how much memory is being used in the GUI.
|Specification=
* Stability suggestion from Albert C (and his children) re. protecting against out of RAM conditions.
http://lists.laptop.org/pipermail/devel/2008-September/019575.html
* We provide no end user feedback on memory usage, either. We should investigate whether revisiting our previous attempt to give such feedback, now that Linux can provide much better information than it could when we abandoned our previous donut attempt. The users could really help, if only we let them know a bit about what was going on... From Jim e-mail to devel: http://lists.laptop.org/pipermail/devel/2008-September/018944.html
|Owners=Jim
}}

{{Feature_request
|Name=Journal never loses work
|Requesters=Everyone
|Requirements=
* Sugar must never lose data. Activities must save on exit and leave an item in the journal. Once an item is ion the journal it must remain there until the user removes it.
* http://sugarlabs.org/go/DevelopmentTeam/0.84/Reliability#Datastore_rework
|Specification= http://sugarlabs.org/go/ReleaseTeam/Releases/Sucrose/0.83.1#sugar-datastore
|Owners= Tomeu, Greg^
}}

{{Feature_request
|Name=Clipboard
|Requesters=Eben
|Requirements=
* http://sugarlabs.org/go/DevelopmentTeam/0.84/Reliability#Solid_clipboard
* [[Specifications/Clipboard|specification]]
|Specification=
|Owners=Eben, Tomeu, Marco
}}



== Localization ==
[http://lists.laptop.org/pipermail/devel/2008-June/015838.html Translation Technology] (See an earlier post, [http://lists.laptop.org/pipermail/devel/2006-March/000000.html Scaling and localization in package management], for background.)

{{Feature_request
|Name=Language Pack version 3
|Requesters=Sayamindu
|Requirements=

|Specification= <br>
* Packs should be as RPMs
* Utilize patches from Ubuntu for Python and Glibc to define a separate install location/search path for PO files installed via the packs

|Owners=Sayamindu
}}


{{Feature_request
|Name=Spell checking
|Requesters=Sayamindu, Sur list
|Requirements=
|Specification=
|Owners=Sayamindu
}}

{{Feature_request
|Name=Enhanced i18n
|Requesters=Sayamindu

|Requirements=
* Better support for translation of content

|Specification=
* Investigation of the possibility of using native digits for translations <trac>7857</trac>

|Owners=Sayamindu
}}


{{Feature_request
|Name=Language customization
|Requesters=Sayamindu, Sur list
|Requirements=An ability customize language (and related settings) without OLPC intervention
|Specification=
|Owners=
}}


{{Feature_request
|Name=RTL support
|Requesters=Lebanon
|Requirements=
* Must support Arabic in Sugar, Write and all activities.
* Must start the cursor on the right and move to the left as characters are typed in Sugar, write and other activities.
|Specification=
|Owners=
}}

{{Feature_request
|Name=SCIM
|Requesters=Sayamindu
|Requirements=
* We need to migrate to SCIM for our input method needs. Our current input method (XKB with XIM) does not work with languages like Chinese, and there are enhancement requests from existing deployments (eg: <trac>8494</trac>) which can only be handled via SCIM.
* Must completely support Simplified Chinese, Nepali and Amharic.

|Specification=
* Conversion of all existing layouts to [http://www.m17n.org/common/m17n-docs-en/m17nDBFormat.html m17n db format ], along with refinements and better support for modifiers whenever possible (<trac>6280</trac>
* Modification of relevant startup and configuration scripts for SCIM support
* User experience for keyboard layout switching should not change
* Proper handling of Amharic characters (<trac>8494</trac>)
* Implementation of [[OLPC_Nepal_Keyboard]]
|Owners=Sayamindu
}}

{{Feature_request
|Name=Multilanguage Support
|Requesters=Sayamindu, Bolivia, Peru, Rwanda, others?
|Requirements=An ability choose multiple languages in order of preference (eg: an Aymara speaker would choose Aymara followed by Spanish)
|Specification=Mockup for the Sugar control Panel has been created by Eben at http://interdimensionmedia.com/scratch/settings-10.jpg . The feature is <trac>8875</trac>
|Owners=Sayamindu
}}

== Security, activation and deployability ==

{{Feature_request
|Name=GUI OS Updates
|Requesters=Eben, Scott
|Requirements=Easy GUI update of OS over net or from USB; Mostly for G1G1 but useful for all.
|Specification=
(I believe this needs to be divided into 'customization key' and initial install. The install has to do with the logistics, USB keys and wireless downloads. Customization has to do with how the image is created before the logistics of how to get it on laptops. [[User:Kimquirk|Kimquirk]] 17:25, 9 October 2008 (UTC))

Many deployments have noted how hard it is to install or upgrade, especially on thousands of XOs. One issue is that inevitably, the Xos ship from the factory with an older build and countries need to upgrade them before deploying. I call that "upgrade in a warehouse". In other cases the XOs get deployed but there is little or no WAN available to upgrade.
|Owners=
}}

{{Feature_request
|Name=Faster imaging
|Requesters=Ethiopia, Rwanda, Haiti
|Requirements=
This feature request is needed to minimize the time to install a custom image over a wireless or wired network. It will be used when an XO comes from the factory with an older release. The deployment then needs to upgrade to the latest release and possibly install some customizations (e.g. content, language pack, activities, see also separate customization requirement below). The solution must be faster than imaging via USB sticks for imaging more than 1,000 XOs. Must allow install of new image via wireless or wired network. Possibly sub-variants of in school case for Mesh, Wireless AP, XS.

Workflow example for the network case above: <br>
# XOs leave the factory with an older image (e.g. 8.2.1) which includes this OFW code.
# A custom image based on the same or a later release including activities, content, language and maybe other customizations is prepared and loaded on the XS.
# An AP is setup and wired to the server.
# The XOs are turned on, as many as they have power jacks for. On boot up we can require that they hold down some special keys (game keys).
# Release the keys and the XOs find the AP and start listening on preconfigured multicast broadcast address.
# The XS broadcasts on the preconfigured address and each XO starts receiving.
# In case of errors which are more than what can be recovered by error correction the XOs, pick up again on the second broadcast or third or up to ... n (where is configurable or they just turn t he server off).
# When the XO has a complete image it notifies by putting a special image on the screen.
# On next reboot of the XO its running the new image. Subsequent boots do not do this multicast listening unless configured specifically by the user.
|Specification=
See also: [[Multicast NAND FLASH Update]]<br>

Some open issues to be addressed by the design proposal:
* Do we pre-configure an ESSID and multicast addresses and hard code those in the factory?
* Can we get it down to no intervention of hold down games keys only?
* What happens if you turn on "too many" XOs? Can we just let them turn on as many as they want and we'll fill them in some order or should we
limit it to set # of XOs at a time? Can we scale it by using more "channels" or more APs?
* Any other security points?

|Owners=Greg, Reuben, Mitch
}}

{{Feature_request
|Name=Image customization
|Requesters=Uruguay, Ethiopia, Colombia,Peru, Mexico (the last two especially for startup image customization). See source thread from Colombia at: http://lists.laptop.org/pipermail/devel/2008-July/017299.html
|Requirements=
When imaging a new laptop or upgrading a laptop we must allow the deployment to create a custom image. This special image will allow XOs to be re-imaged via USB or over a network (via olpc-update to internet, via olpc-update to XS, via Quicker Imaging feature above). The customized image must allow configuration of the following items. These should be settable when creating a new image or when upgrading unless otherwise noted.

Cuando haciendo un imagen nuevo para el XO o haciendo una actualizacion del Software debe permitir que el despliegue cree una imagen de encargo. Esta imagen especial permitirá que XOs sea puesto vía el USB o sobre una red (vía la olpc-update del Internet, vía la olpc-update de un XS, o via Quicker Imaging definido arriba). La imagen modificada para requisitos particulares debe permitir la configuración de los puntos siguientes. Éstos deben ser configurable al crear una nueva imagen o al aumentar a menos que se indicare en forma diferente.

* When installing a custom image, must not require any user interaction with the keyboard. Can require holding down a game key on startup.
* Al instalar una imagen de encargo, no debe requerir cualquier interacción del usuario con el teclado. Puede requerir el mantenimiento de una llave del juego en arranque.

* Must allow setting the language
* Debe permitir el fijar de la lengua

* Must allow inclusion of the activities and content bundles chosen by the deployment.
* Debe permitir la inclusión de las actividades y el contenido lía elegido por el despliegue.

* Must allow installing a language pack
* Debe permitir el instalar de un paquete de la lengua

* Must allow configuring the keyboard for a language
* Debe permitir el configurar del teclado para una lengua

* Must allow installing an RPM (Ethiopia)
* Debe permitir el instalar de una RPM (Etiopía)

* Must allow setting Time, Date Timezone
* Debe permitir deinicion del tiempo y Timezone

* Must allow setting of all elements of the sugar-control panel, CLI and GUI versions.
* Debe permitir el ajuste de todos los elementos del panel del azúcar-control, de las versiones del CLI y del GUI.

* Must work with activated XOs and non-activated XOs. In the non-activated case must activate them so the XO is ready for use in the school when done.
* Debe trabajar con XOs activado y XOs no activado. En el caso no activado debe activarlos así que el XO es pronto para usar en la escuela cuando está hecho.

* Must no require more than one reboot.
* No debe requirer mas que on "reboot"

* Should turn off when its done or show "success" screen then one key stroke and shutdown.

* Must allow changing startup picture by copying an image to the XO.
* Debe permitir el cambiar del cuadro de lanzamiento copiando una imagen al XO.

* Must not require that deployments request a new signed build from OLPC. This can be addressed by allowing them to sign their own builds or by allowing all the customizations listed to be made on a signed build without requiring that it be re-signed. We can require that this feature is only available to specially designated users.
* Necesidad no requerir que los despliegues pidan una nueva estructura firmada de OLPC. Esto puede ser tratada permitiendo que firmen sus propias estructuras o permitiendo todos los arreglos para requisitos particulares enumerados para ser hecho en una estructura firmada sin requerir que re-signed. Podemos requerir que esta característica esté solamente disponible para los usuarios especialmente señalados.

See also:
* <trac>7878</trac>
* <trac>6689</trac>
* <trac>6432</trac>

The following two points need redefinition and clarification:
* Must work with activated XOs and non-activated XOs. In the non-activated case must activate them so the XO is ready for use in the school when done. (rewrite to cover pre-activated and lease feature disabled cases).
* When imaging in a warehouse must activate the laptop

* Note, follow up on issues with open firmware.

|Specification=
* http://lists.laptop.org/pipermail/devel/2008-March/011553.html
* http://lists.laptop.org/pipermail/devel/2008-July/016417.html

|Owners=
}}

{{Feature_request
|Name=School server push of XO images
|Requesters=Peru
|Requirements=
* The XO should be able to get the latest build from the school server
* The administrator makes the desired build available in the designated directory. When ready, the administrator requests to 'push' the build to all laptops as they come on line. Both of these activities should be an easy-to-use UI at the school server.
* A test requirement is the ability to create a white list of serial numbers that should be upgraded with the push.
|Specification=
|Owners=Martin
}}

{{Feature_request
|Name=Image Signing Key delegation
|Requesters=Uruguay
|Requirements=
* Must all a deployment to generate an image with their own key. See Trac ID: 9045
* After a key has been generated for a country, must not require them to contact OLPC for any further information to make the signed image.
* Can allow deployments to sign with their own key or with a key delegated from us.
* Must allow the deploymet
|Specification=
|Owners=Scott
}}

{{Feature_request
|Name=Activation lease security
|Requesters=Peru, Ethiopia (especially last point), Uruguay?
|Requirements=

'''Overview''' <br>
The controlling idea is that when an XO is stolen it will stop working after a time (activation lease time) unless it contacts a re-leasing server (usually a School Server). For example, if an XO is stolen and taken away from its school server, after the expiration of the lease time it will no longer boot up. If the XO is stolen but still comes within range of its school server, it can still be prevented from booting if the XO information (probably serial number) has been added to a black list on the XS.

* If the laptop is stolen, and doesn't contact its local school server within some period time (activation lease time) the XO will no longer boot (I call this "deactivated").
* Si se roba el XO y el XO no se contacta a su servidor (XS) local de la escuela dentro de una cierta hora del período (tiempo del arriendo) el XO va a encender (boot) (llamo este " deactivated").


* When the XO boots up and contacts the XS, its lease time is extended. e.g. if the activation lease time is 30 days and it starts on November 1, then the XO boots up on November 20 and contacts the XS, it will continue functioning without contacting the XS until December 20.
* Cuando el XO arranca y entra en contacto con el XS, su tiempo del arriendo es extendido. e.g. si el tiempo del arriendo de la activación es 30 días y comienza el 1 de noviembre, después el XO arranca el 20 de noviembre y entra en contacto con el XS, él continuará funcionando sin entrar en contacto con el XS hasta el 20 de diciembre.


* Optionally as set by the administrator, if an XO is deactivated and tries to boot up when in the vicinity of its controlling school server, then it will boot unless it has been added to a blacklist. The blacklist is a list of XOs (by serial number?) which has been entered in to the school server by its administrator. That is, the activation lease time will be automatically extended whenever the XO contacts its controlling XS, unless it has been entered in the black list.
* Opcionalmente como fija por el administrador, si un XO se desactiva e intenta boot cuando esta en la vecindad de su servidor de la escuela que controla, después boot a menos que se haya agregado a una lista negra. La lista negra es una lista de XOs (por número de serie?) cuál ha sido entrado adentro al servidor de la escuela por su administrador. Es decir, el tiempo del arriendo de la activación será automáticamente cuando el XO entra en contacto con su XS que controla, a menos que no se haya inscrito en la lista negra.


* Must allow setting of the activation lease time by the deployment lead (user interface required). That is, they can set it for 90 days or whatever they want. The granularity should be at 24 hours and be from 1 day to never expire. Must allow setting this once for a recurring interval (e.g. XO leases expire every 60 days).
* Debe permitir el ajuste del tiempo del arriendo de la activación por del despliegue (interfaz utilizador requerido). Es decir, pueden fijarlo por 90 días o lo que quieren. La granulosidad debe ser en 24 horas y ser a partir de 1 día nunca a expirar. Debe permitir el fijar de esto una vez para un intervalo el repetirse (e.g. los arriendos de XO expiran cada 60 días).


* Must not be possible for the user to set the date on the laptop to keep it within the lease period or to force it to outside the lease management. This might mean you cannot change the date or there is no root access, or it might mean an alternate time source is used.
* Necesidad no ser posible para que el usuario fije la fecha en el ordenador portátil para guardarlo dentro del período del arriendo o para forzarlo fuera de la gerencia del arriendo. Esto pudo significar usted no puede cambiar la fecha o no hay acceso a root, o puede ser que signifique que una fuente alterna del tiempo está utilizada.


* Must support the same as described above but allow the server which determines the activation to be across the Internet. The lease management server can be in a data center managed by the deployment or on a server managed by OLPC.
* Apoye iguales como se describe anteriormente pero permita el servidor que determina la activación para estar a través del Internet. El servidor de la gerencia del arriendo puede estar en un centro de datos manejado por el despliegue o en un servidor manejado por OLPC.


* Must support the same requirement as described above but allow the reset of the activation to be done via USB key. That is, when an XO's lease expires, it must be booted with the USB key containing a special code. This can be done before it expires to extend the lease.
* Apoye el mismo requisito como se describe anteriormente pero permita que el reajuste de la activación sea hecho vía llave del USB. Es decir, cuando el arriendo de un XO se expira, él se debe boot con la llave del USB que contiene un código especial. Esto puede ser hecha antes de que expire para extender el arriendo.


* Should support the ability for an XS to continuously generate new leases every nnn time as set by the user (e.g. every 2 weeks). This will allow an XS to be placed in a school and then it does not need Internet access or anyone from outside the school to continuously update the lease times.


* Should support a GUI accessible from the XO which is password protected and encrypted (aka no passwords in the clear across the network/wireless). This GUI will allow a user in the school to enter an XO by serial number or better by name and have that XO added to the blacklist (see above, essentially its lease is not renewed).


See also write up on "Actual security requirements": [[User:Mstone/Commentaries/Security_1]] and <br>
Server side "Blueprint" at: http://wiki.laptop.org/go/XS_Blueprints:Lease_and_update_server

|Specification=
* <trac>4043</trac>
* [[Firmware Key and Signature Formats#Version 2]]
* http://dev.laptop.org/~cscott/joyride-api/bitfrost.leases.crypto-module.html
* http://lists.laptop.org/pipermail/security/2008-June/000441.html
|Owners=
}}

{{Feature_request
|Name=Theft reporting
|Requesters=Peru?
|Requirements=
Sometimes known as 'active kill'. If the laptop is stolen, the serial number can be added to a 'stolen laptop' list so the laptop's activation can be turned off the next time it finds either a local school server or a global tracking server.

* A trusted administrator can log into a central system (either regionally controlled or OLPC controlled) and add a serial number to the 'Stolen' list.

* Any laptop that connects to a local or global server that finds a match on the 'Stolen' list, and it was originally activated with an activation key, will be de-activated.

* The security must ensure that the person adding the stolen laptop is a person who has been given that access; and that the server causing the de-activation is a server that has been given that right.

* Re-activating the laptop again requires the same procedure as initial activation or lease management.
|Specification=
|Owners=
}}

{{Feature_request
|Name=XO Monitoring
|Requesters=Peru
|Requirements=Provide XS database and an API so that countries can create reports and monitoring for various aspects of XOs such as:
* Version of code
* Which laptops are being seen each day
* Total number of laptops being seen per day
* Number of laptops accessing the internet
* List of URLs being accessed
* List of URLs per laptop
* Which activities are being used per laptop
* Number of minutes in each activity per laptop; can we determine (and subtract) idle time?
* Number of minutes in each activity within and outside of school hours (perhaps this means we capture the 'start' time of each activity and allow the reporting to decide if this is during or outside of school hours).

This is not as high priority for their deployment as the passive lease management, but I believe this feature will be important for any deployment. We should try to get feedback from other deployments as to the information we want to collect.
|Specification=
I (Kim) think there might be some work in the XO to make the information available; and a database and API spec from the school server.
|Owners=Kim
}}

== Network ==

{{Feature_request
|Name=802.1x Support
|Requesters=Uruguay
|Requirements=
* Must allow association with APs running 802.1x
|Specification=http://en.wikipedia.org/wiki/IEEE_802.11#Standard_and_amendments
|Owners= Chris
}}

{{Feature_request
|Name=Reliable access to encrypted APs
|Requesters=G1G1
|Requirements=Must reliably (better definition needed) associate with APs running WEP, WPA and WPAv2
|Specification=
|Owners=
}}

{{Feature_request
|Name=Network Manager GUI
|Requesters=
|Requirements=
* What needs to be done, is a way (via the control panel), to be able to select which interface Salut is going to use. That can be accomplished by
only enabling multicast on the interface selected and turn it of on the other. This is always needed for XOs that have internet sharing enabled b.t.w.

* Without a control panel, a good default choice would be to disable multicast on the mesh interface (ifconfig msh0 -multicast) if eth0 is associated.

* Enable Internet sharing (with pull down menus from which interface to what interface - eth0 to msh0 being the default)

* disabling the mesh interface completely (for backwards AP compatibility)

|Specification=
|Owners=
}}

{{Feature_request
|Name=Document and Improve default network connection
|Requesters=?
|Requirements=
Better default network connection choice algorithm (e.g. if USB - Ethernet is connected, use it first source: A Callahan).
: This already happens, but perhaps there are bugs. -[[User:DanielDrake|DanielDrake]] 16:37, 3 October 2008 (UTC)
This algorithm should be "smart" in its first choice but should also be adjustable in the GUI.
* Must include choosing wired over wireless, choosing one AP vs. another and choosing Mesh vs. AP.
* Must minimize time trying to connect to an AP not desired (e.g. must not try to connect to mesh when user expected AP).

Needs further definition.
|Specification=
|Owners=
}}


{{Feature_request
|Name=XO as Internet Gateway (formerly called MPP)
|Requesters= Uruguay, Kim, Michailis
|Requirements=
|Specification=
|Owners=
}}


{{Feature_request
|Name=Full IPv6 support
|Requesters= Marc Blanchet
|Requirements=
Verify, test and add whatever needed to support IPv6 on OS, apps, etc...
|Specification=
|Owners=Marc Blanchet
}}

== GUI, Usability ==

{{Feature_request
|Name=Remove the "frame" feature
|Requesters=Joe
|Requirements=Remove the "frame" feature.
|Specification=Remove the "frame" feature altogether. Concentrate all icons either in the bottom or the top of the screen, make them much smaller, also reassign the related to "frame" keyboard's key to do something more useful. Benefits: more useful screen's real estate, no delay currently experienced while switching the frame, especially by using a cursor. Simpler is better, isn't it?
|Owners=
}}


{{Feature_request
|Name=Hardware alerts
|Requesters=Uruguay
|Requirements=http://lists.laptop.org/pipermail/sugar/2008-July/007086.html
|Specification=Designs ideas from Scott and Eben in thread. e.g. I hope our alert system will use the freedesktop.org standard: http://www.galago-project.org/specs/notification/index.php There is a visual design for the [[Designs/Activity_Management|notification system]] as well.
|Owners=
}}

{{Feature_request
|Name=Contextual help
|Requesters=Brianne
|Requirements=
One idea from Eben. From: http://lists.laptop.org/pipermail/sugar/2008-August/007547.html <br>
All of our initial discussions on help focused around a contextual help system, and I still hope that this is where we'll be taking this in the future. By embedding (?) icons within the secondary palette menus for various devices, objects, activities, and even individual buttons and controls, we can provide a way to launch into the help activity and dive directly to the relevant info for the activity, control, etc. selected. In addition, I'd like to support a community driven help system by which, in addition to the activity/olpc provided help, it's possible for kids to add tips, tricks, images, tutorials, and other info to these sections for later consumption by peers.

This is a noble, but ambitious goal, which is why a simple and static help activity is the present solution, and why it's only integrated into the system at a single point - the activity itself.
|Specification=
|Owners=
}}

{{Feature_request
|Name=Trash can
|Requesters=Bastien
|Requirements=http://lists.laptop.org/pipermail/sugar/2008-August/007889.html
|Specification=
|Owners=
}}

{{Feature_request
|Name=Scalable zoom levels
|Requesters=UI Team, Collabora
|Requirements=We need to support a mechanism for auto-filtering the view to a "reasonable" set of activities and XOs, and provide rich mechanisms (search and filters) for adjusting one's perspective on the view to find items of interest.
|Specification=Gadget is the core of this effort. We need some additional UI work to hook it up. One aspect of the solution is the addition of list views to all zoom levels, making it possible to list the entire set of people, activities, access points etc, see their icon and name at a glance, sort alphabetically or by type, and also filter as desired.
|Owners=Eben, Collabora
}}


{{Feature_request
|Name=Keyboard navigability
|Requesters=Homunq
|Requirements=All options in the menu and frame should be accessible from the keyboard (ctrl-xxx). There should be some way to see what key is associated with a given option, both when using it and when "looking for the key". This should require a minimum (ideally, zero) programming from activity developers. This is a key part of the strategy for improving the situation of bad trackpads; it is unrealistic to expect the trackpad problem to be 100% resolved.
|Specification=Holding the control (or frame) key should show semitransparent letters/numbers over any menu (or frame) gadget visible. These letters should also appear for ~150 ms when an option is chosen. Default letters should be chosen by the relevant python classes if not specified by developer. Any specification should be localizable. Ideally, contextual menu options should be accessible with multiple keystrokes.
|Owners=Homunq, ??
}}

== Server ==
Full list of Trac IDs for server roadmap is here: <br>
https://dev.laptop.org/query?status=assigned&status=new&status=reopened&group=milestone&component=school+server&order=priority&col=id&col=summary&col=status&col=priority&type=enhancement

=== Backup and Restore ===
{{Feature_request
|Name= Automatically recognize XO on restore page
|Requesters= Reuben
|Requirements=
* Must allow XO to see their own files when going to the URL representing the backed up files from that XO.
* Must not require the user to type in the name or serial number of their XO.
* See related single sign on feature.

|Specification=
|Owners= Greg
}}

== Linux and OS ==


{{Feature_request
|Name= Rebase on Fedora 10
|Requesters= Ed
|Requirements=
* XO release 8.2 contains a list of packages (some forked and some not). For must 9.1.0 we must update all packages to their Fedora 10 versions and re-apply XO specific changes, as needed, to the new Fedora 10 package.
* Every package should also be included upstream. If that has not been completed in time for this release, every package must at a minimum have a plan for how it will get included upstream. This must include at a minimum an e-mail exchange with the package.
* Must measure the NAND and memory usage vs 8.2. Any significant (not precisely defined as >1%) change in memory or NAND space in comparison to 8.2, must be reviewed.
* Must not include any Fedora 9 or earlier packages (unless they haven't changed).

|Specification=

|Owners=None yet.
}}

{{Feature_request
|Name= Run any Fedora application on XO
|Requesters= Ed
|Requirements=
* Only needs to run Fedora applications which fit in the available NAND space, memory and CPU.
* Must run as well on the XO as they would on any other computer 433Mhz 256 MB RAM.
* Must allow switching between Fedora 10 and a conventional desktop manager and sugar, and back.

|Specification=

|Owners=None yet.
}}


{{Feature_request
|Name= NAND Full should not crash XO
|Requesters= Uruguay
|Requirements=
* Must allow access to the journal and other parts of the file system to delete items, even when the NAND is full
* Must allow the user to choose which items get deleted to clear space.

|Specification=
{{ticket|7590}} Must allow deleting files when the NAND is full.

|Owners=Greg
}}


{{Feature_request
|Name= Replace JFFS file system with better one
|Requesters= Deepak
|Requirements=
* End users will see faster boot up time and will not see (as much) performance degradation as the file system fills up.

|Specification=
The current file system used on the XO ([[http://en.wikipedia.org/wiki/JFFS2 JFFS2]]) was developed in the days of 32/64MiB NOR flash devices and does not scale well to the 1GiB NAND devices we are using today and certainly will not deal well with larger devices in gen 1.5 and gen 2 systems. The main issues are that JFFS2 needs to scan all blocks at mount time and that the garbage collection algorithm increasingly consumes CPU cycles as the system fills up. The first issue manifests itself as large delays at boot up to mount the file system as it is full (need to quantify this), and the second issue simply means less CPU cycles can be dedicated to user task processing. In the last few years, there has been much activity in the embedded Linux world on alternatives to JFFS2 and we need to investigate these to determine which one best fits our needs:

* [http://www.yaffs.net/ YAFFS2] : Has been around for several years and in active use in the embedded space. It does not provide compression out of the box as the devices that use it often carry already compressed data such as MP3 and MPG files.

* [http://www.linux-mtd.infradead.org/doc/ubifs.html UBIFS]: A new file system recently merged into the kernel designed for use on large flash devices. Supports compression out of the box and supports disabling compression on a per-inode basis, which is something we desire.

* [http://logfs.org/logfs/ LogFS] : Another JFFS2 replacement designed for fast operation and scalability. Still fairly new and not in very active use AFAIK.

* [http://btrfs.wiki.kernel.org/index.php/Main_Page Btrfs] : A very new file system that is primarily targeted for large storage systems with features such as snapshotting, RAID support, and online fsck. David Woodhouse has expressed that he will look into getting this to work on NAND, but it is too new of a code base to consider for 9.1

* Managed NAND : (Not an option for existing XO machines, but might be a direction for future hardware) The industry seems to be moving away from raw NAND in favor of a NAND-chip plus microcontroller solution. The microcontroller implements a Flash Translation Layer that hides the low level NAND details, presenting a higher level interface that looks like an ordinary hard disk, so an ordinary filesystem layout like ext3 could be used. The driving force behind managed NAND is rapid hardware evolution toward multi-level-cell NAND chips and smaller process geometries, which change important NAND parameters like page sizes and ECC. The situation is similar to what happened with hard disks in the 80's, where raw-disk interfaces gave way to SCSI and IDE, which hide the ugly low-level details that changed every technology generation. Managed NAND options include LBA-NAND from Toshiba (pin-compatible with NAND chips), eMMC from multiple vendors (with an SD/MMC-compatible hardware interface), and various "disk on chip" products (IDE-compatible interface).

'''Development process''' <br>

* Analyze and quantify the use patterns that trigger issues with JFFS2.
* Gather requirements for a new file system that go beyond solving above issues.
* Develop/integrate a set of tests for FS performance and reliability that take into account our use patterns, the above issues, and any other features we wish to validate.
* Study the three main alternatives (YAFFS, UbiFS, LogFS) to determine what requirements they meet
* Run our FS test suite on above alternatives
* Analyze test results and requirements study and make a decision on which alternative to use.

'''Deployment process''' <br>
Once a file system is chosen from the above process, we will have to: <br>
* Integrate the file system into our kernel if it is not upstream (YAFFS2 or Logfs)
* Integrate the file system support packages into our build system and file system images
* Update our build scripts to generate the proper image type for

'''Activity impact''' <br>
This change should not have any impact on activity developers as it is at a very low level of the stack.

'''End-user impact''' <br>
End users will see faster boot up time and will not see (as much) performance degradation as the file system fills up.

|Owners=Deepak
}}


{{Feature_request
|Name=Copying files between Journal and USB
|Requesters=Bastien, Uruguay
|Requirements=As close to one click to copy files from Journal to USB.
|Specification=
|Owners=
}}

{{Feature_request
|Name=File name and directory access
|Requesters=Gnu, Ben, Erik, Greg, Marvin
|Requirements=Allow listing, copying and finding files with standard Unix commands in the terminal view. See also point #1 at: [[9.1.0#e-mail from Ben S]]
|Specification=
|Owners=
}}

== Other ==

{{Feature_request
|Name=System clock
|Requesters=Birmingham and seen on devel list (anyone have time to search for the threads?)
|Requirements=
* Must have a clock on the XO. Can be visible in the frame or built as an activity. If built in to the frame, must be configurable in graphical control panel to show it or not.
* Must allow analog (aka hands) or digital time.
* Must allow setting the time. (also sets the XO's time Linux? if so allow configuring NTP?).
* Should include an alarm clock and a stop watch mode.
|Specification=
|Owners=Greg
}}


{{Feature_request
|Name=Library and Bundle Updates
|Requesters=SJ
|Requirements=
* '''thought experiment''' : how does one present an activity (has its own isolation-friendly code) that includes a library bundle (its own browser-browsable static content, help and supplemental materials) and a generic resource bundle (a repository of sounds and images) look like? How do other parts of the system (the Journal, Browse, other activities) see and interact with these three collections of material (to browse and copy the code, to view the static content, to aggregate the resource collections with other collections)?
* a [[Dynamic library]] implementation
* coordination of a unified help interface building on top of the library bundles defined for each activity on the system.
** integration of some way to update and share this. related to how to leave a comment on/about an activity or file/resource
* coordination of local library bundles, and regional caches of viewed material, school server caches of bundles, and web caches.
* cleaner display of available bundles via a bundle updater; relatd to but not the same as the current software upgrade function, which has a strong emphasis on olpc-stamped/signed materials

|Specification=
* API and .info unification across content and activity bundles. Making both and a general [[generic bundle]] clearly described within an overarching bundle format.

|Owners=SJ
}}

{{Feature_request
|Name=Screen Zoom
|Requesters=Greg
|Requirements=
This idea came from watching kids and grownups gathering around an XO and trying to see what someone else is doing. <br>
* Must allow zooming the screen in so that a portion of the screen is "magnified"
* Must allow centering the zoom on different parts of the screen. Possibly chosen by centering where the cursor is or possibly selecting a box with drag or keyboard input.
* Must allow several zoom (magnification not sugar zoom levels) levels, preferably a smooth range from 1x to 10x
* Must allow scrolling to move the magnified image to see things otherwise off screen. Preferably a smooth scroll but can be discrete steps if needed. Must allow scrolling via cursor or keyboard input (keyboard needed in case XO has a gimpy cursor). Must allow user choice of scroll input by user configuration (cursor or keyboard).
* Should allow one touch snap back to 1:1.
* Should have as clean interpolation as possible.

|Specification=
Ben said that the Geode has HW scaling with interpolation. This feature should come at no/bare minimum cost to CPU cycles and performance.

|Owners=Greg
}}

{{Feature_request
|Name=Universal view source
|Requesters=Tomeu
|Requirements=One more step towards implementing the original vision of the [[OLPC_Human_Interface_Guidelines/The_Laptop_Experience/View_Source|"View source" key]]. <br/>
* Must work on all activities deployed in well-formed [[Activity_bundle|activity bundles]].
* Must display all files inside the activity bundle and provide a means to show the source code that there may be.
* Must open in a window local to the activity displayed, so doesn't interfere with other activities not the Sugar Shell.
* Must allow for activities to override this default behaviour and implement their own, specific source viewers.
|Specification=See [http://lists.laptop.org/pipermail/sugar/2008-October/009495.html this thread] for an implementation proposal.
|Owners=Tomeu
}}

{{Feature_request
|Name= Developers Center w/ documentation for users and developers
|Requesters=[[User:Mchua|Mel]]
|Requirements=
Strictly speaking, this is not a technical feature; however, like technical features, this would require developer time in exchange for enhancing our capabilities to implement and (commercially) support technical features, so I am including it here.

* A separate, non-community-maintained, website for formal user and developer documentation (Precedents: [http://www.redhat.com/developers/ Fedora/Red Hat], [https://help.ubuntu.com/ Ubuntu]), posted in a publicly viewable but edit-protected place. (i.e. not publicwiki as it now stands.)
* On this site, a canonical list of all the technical subcomponents that make up the OLPC system that the organization supports.
* For each subcomponent, a howto/code-tour for the kind of developers we want to have working on that portion of the project.
** Note that this could be "Code is available for download, but community development is not officially supported by the OLPC organization," and a link to the all-community wiki (or appropriate pages as on SugarLabs).
* Intended audience: developers with code experience but no OLPC-specific project background
* Put a link in the library on the XO which links to GIT or other relevant source. (added by Gnu)


|Specification= If this were implemented mainly by developers, it would be a large task for the developer responsible for each subcomponent to take responsibility for creating this section. So instead, I would suggest putting the load on a single editor who would be in charge of talking with developers, asking them questions, and formatting their (objective: minimize the workload on developers as much as possible). I could see this being half-time contract work, maybe for 2-3 months during 9.1 development, to create and release a first version of a "developers' center" with an infrastructure that can be easily updated for future releases.

|Owners=None yet.
}}

{{Feature_request
|Name= Caps lock option
|Requesters= Jim
|Requirements=
#2447 make it easier to set caps lock to on
|Specification=

|Owners=None yet.
}}

{{Feature_request
|Name=Fully comply with GPLv3
|Requesters=FSF and Gnu
|Requirements=
* Must audit and confirm GPL compliance before release
* Many possible Trac IDs. One example: http://dev.laptop.org/ticket/6892

|Specification=
|Owners=Greg
}}


{{Feature_request
|Name=Debug tool
|Requesters=Uruguay
|Requirements=
* Debug tool that easily allows plug of diagnostic USB stick which analyzes and reports back detailed status.

|Specification=
|Owners=ErikG
}}

= Priorities from Engineering =
'''The following is maintained here for the history and a look at what people want to do by engineer. However, I hope that everything in this section will also have a place in the Feature list above. If you added something here, please also find a home for it in the section above.''' <br>
Thanks [[User:Gregorio|Gregorio]] 13:13, 23 October 2008 (UTC)

*{{ticket|2188}} sharing files and resources between activities
*{{ticket|1496}} Switch to real public keys - Scott
*{{ticket|8170}}
*{{ticket|8171}}
*{{ticket|8177}}

Upgrade journal per: [[OLPC Human Interface Guidelines/The Laptop Experience/The Journal]]
Less flickering in starting activities and other screen changes - Michael

Ensure the blinking of the lights is meaningful. <br>
http://lists.laptop.org/pipermail/sugar/2008-September/008237.html

Backup to Internet idea from Walter: <br>
http://lists.laptop.org/pipermail/sugar/2008-September/008340.html



== Sugar architecture ideas ==
From thread started by Michael S <br>
http://lists.laptop.org/pipermail/sugar/2008-July/007304.html

== e-mail from Ben S ==
http://lists.laptop.org/pipermail/sugar/2008-July/007390.html

=== 1. The datastore ===
Sugar's design calls for a centralized rich data storage system, the
datastore. The datastore provides secure, limited file access to
Activities, manages file metadata, maintains a differentially compressed
history of all work, ensures reliable backups to a trusted server, and
mediates the connection to removable media. Every one of these features
is crucial to Sugar's functioning, and almost none are really working at
this time. We cannot afford another release based on the present
datastore, as it fails to implement the features we require, and is
unreliable even in the features it supposedly implements.

Solution: <br>
There have, at this point, been at least five distinct proposals for a
next-generation datastore design, all differing in underlying
implementation and user-facing functionality. We need to have a Once And
For All datastore summit, draw up a compromise datastore design, and
implement it. We can do this by 9.1.0, if we are willing to make it a
priority.

Additional Links:
* [[Sugar.datastore.datastore|The current datastore]]
* [[Olpcfs]]
* [http://lists.laptop.org/pipermail/community-news/2008-January/000095.html Sugar Datastore Summit in January] (item 10).
* [http://dev.laptop.org/git?p=users/mstone/sds;a=blob;f=README;hb=HEAD SDS] (stands for Simple Data Store or possibly something else)
* [http://lists.laptop.org/pipermail/devel/2008-March/012047.html Git-based] datastore design

- Expose the file system on save, open and in the journal. Source: Marvin Minsky





=== 4. Activity Modification ===
A keystone of the Sugar design has always been the user's ability to edit
any Activity, and to cement this a "View Source" key was designed right
into the hardware. This functionality is simply missing, and that
prevents us from making our principal claim regarding an emphasis on user
modification.

Solution: <br>
"Develop" must be polished, finished, and included by default. This will
require modifications to the core system, in order to support an endless
variety of slightly modified Activities. It will also require work on the
Develop program itself. If volunteer efforts are not moving fast enough, OLPC
must ensure that someone is working on the problem as a professional.

Additional links:
* [[Develop]]
* [[Old_Develop_activity|Previous, stalled attempt at Develop]]
* [[View_Source|Current status of "view source"]]
* [[OLPC_Human_Interface_Guidelines/The_Laptop_Experience/View_Source]]
* [[EAG_The_Laptop_Experience:_View_Source]]

=== 5. Bitfrost ===
Sugar, as it currently stands, is among the least secure operating systems
ever, far less secure than any modern Linux or Windows OS. I can easily
write an Activity that, when run by the user, escalates to root privileges
and does anything I like with the system. Given Sugar's competitive
status against Windows XO, this failing threatens the very existence of
the project. The Sugar designs have long stated that safely running
untrusted code from a classmate is a key goal for learning, but the
current software accomplishes precisely the opposite.

Solution:<br>
NO ONE IS WORKING ON BITFROST. That's right. Everyone who was working on
Sugar security (after activation) has either left OLPC or moved into
another role. Someone must be assigned to continue the security work, or
it will certainly never make progress. Anyone who _does_ take on this
challenge will start from a much better position than previously,
because many of the Vserver features have moved into the mainline kernel
over the last few versions. The kernel now contains a number of new,
powerful isolation and control primitives.



== Suggestions from [[User:CScott]] ==
Moved to [[User:CScott#Desiderata_for_9.1.0]]. Crib proposals from there. The canonical source for my 9.1.0 proposals is now the postings to devel@ I made, with subject lines beginning, "9.1 Proposal:".



== Thoughts from [[User:cjb]] ==
* Translation of Sugar inside Sugar?
* A working Distribute activity for journal objects (could be in the Journal)

== Thoughts from [[User:Mstone]] ==

* [[Security]] already contains my immediate security roadmap.
* My [[User:Mstone|user page]] links to several of my other ideas, many of which are procedural improvements with software components.
* My largest ongoing concern is that we have not yet smoothly carried a deployment through an update to a new major stable release. (Peru may become our first exception to this rule, but this remains to be seen.)

== Notes from [[user:sj|sj]] ==

Adding basic interface pieces that we want to support in the long term, and making them do something familiar, reliably, every time they are at hand. "escape", "stop/start", "share", "view source", "keep", "cut" and "paste" should all do fairly reliable things across activities. Make them do something recognizable even when the activity developer hasn't provided an app-specific hook for same.

=Template proposal=
A proposed template for managing this page:[[Template:Feature_request]]. In addition to looking nice, use of a template makes it easy to update or adjust the appearance of all feature requests easily in the future.

{{Feature_request|Name=My cool feature
|Requesters=
Some countries

|Requirements=
Some requirements
*or
*a
*list
*of
*them

|Specification=
Detailed specification
*or a list
*of relevant links

|Owners=
Some developers
}}

Latest revision as of 16:05, 10 February 2011

For current information on OLPC's feature planning process, see Release Process Home.

Stop hand.png WARNING:
The content of this section is considered
DEPRECATED and OBSOLETE
It is preserved for historical or documenting reasons.


Overview

This page goes hand-in-hand with the Feature requests page, as follows:

1. Feature requests
Features, requirements and requests by country. This page contains verbatim requests from technical leads or translated and reviewed rewrites of initial feedback. Only items specifically requested by a qualified technical lead, administrator, teacher or student in the country should go in this section. See also: Deployments
2. Feature roadmap
Feature suggestions by technical strategy. Each item on this page should include reference to the;Requester: (e.g. country or engineer or URLs to relevant discussions and sites). It should also include a reference to which element of the strategy it fits in to (if available).

Suggestions for providing input

  1. Please sign in to the wiki when updating this page and its subpages so we know who made the edits.
  2. Raw, unfiltered feedback from countries and deployments should go on the Feature requests page.
  3. Feel free to add to this page following the guidelines described above. You can add a subsection to #General comments below, or add to this page's discussion page.
  4. To comment on a particular feature, click the feature's title to go to its subpage, then comment on its discussion page.
  5. Before editing the subpage for a particular feature, , discuss your edits with the original poster /owner beforehand.
  6. You must use the template correctly when requesting features or enhancements, otherwise your feature won't show up. Follow #Adding to the roadmap carefully
  7. Use <trac> when referencing tickets/bugs.
  8. Additional suggestions for providing input are welcome.
  9. Create a new section (At the == header 2 == level) for your country or request if none present are adequate.
  10. Make sure all ideas have a very solid basis for being valuable to customers. Including links to blogs, reports or other data that proves users really need your feature will make a big difference.

Roadmap

This section lists major features to be added to XO software over time.

All features

Click on the arrows in any heading to re-sort by that heading. {{#ask: Is part of::+

?Is part of=Area ?=Feature ?Requested by=Requested by ?Helps deployability#yes,-=Helps deploy ?Target for 9.1#yes,no ?Contact person=Owner(s) ?Priority sort=Is part of mainlabel=- limit=200 default=Nothing found in Category:Software features with Property:Is part of?!

}}

Other queries

Feature roadmap/Page of all features that target 9.1.0 embeds all the pages with Target for 9.1 set to "yes".

See Features-test for other queries, you can add your own to it or copy them to other pages.


Adding to the roadmap

When adding a new feature please follow these guidelines.

  1. Make sure the feature doesn't already exist
  2. Read the Usage section of Template:Feature tracking for help filling out the template on the new page
  3. Pick a "Feature subcategory" from Category:Software features
  4. Find the requester(s)' wiki pages and the feature owner's User: wiki page
  5. Change Good feature name to your new subpage title, following the OLPC:Style guide for page names
  6. Ready? Click the button below to create a new wiki subpage with the right title convention that's prefilled from Template:Feature tracking/Preload, edit it to suit, then save. After a delay (due to wiki query and page caching), your new subpage will appear in lists of features.

<inputbox> type=create preload=Template:Feature tracking/Preload buttonlabel=Create a new Feature roadmap subpage. default=Feature roadmap/Good feature name width=40 bgcolor=#f0f0ff </inputbox>

A description of each field is listed here:

Requesters
Deployments, engineers, or both who support the request
Requirements
User level requirement definition; Links to detailed wiki pages, mailing list threads, or other resources are welcome
Specification
Design and technical implementation ideas; Links to detailed wiki pages, mailing list threads, or other resources are welcome
Owners
Names of developers and/or champions of the request who will ensure that progress is made
Priority
1-5 (1 = Critical, 2 = High, 3 = Medium, 4 = Low, 5 = not needed)
Helps deployability
yes or no Better deployability is the goal of 9.1.0. Set to "yes" if the feature helps that goal, regardless of its "target 9.1.0" status.
Target for 9.1
yes or no "yes" means that an OLPC engineer is (or will be) assigned to work on this for 9.1.0 release.

See also: general suggestions for providing input.

Adding a category

Only do this with careful forethought and a confirmation on the wiki gang list http://lists.laptop.org/pipermail/wiki-gang/>

1. Mention the new category name in the template:

Feature subcategory=Easter eggs

2. Be sure to create the subcategory: edit the category's page (Category:Easter eggs) and add [[Category:Software features]] to it.

If you forget #2, some queries will omit the page and people may have a hard time finding your new feature subcategory.

Documentation on semantic templates

Enables a dynamic Feature roadmap — see Semantic MediaWiki#For software features.

When you fill in Template:Feature tracking on one of the feature roadmap sub-pages, the template both displays the feature's information in a basic table (using {{Definition table}}) and makes semantic annotations for many of the template fields — assigning values to properties such as Property:Requested by. That allows this page and others (such as Features-test) to query for and display these properties.

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Feature_roadmap&oldid=252748"