Feature requests: Difference between revisions
(New page: ==Overview== ===What's on this page?=== This page provides a space for aggregating feedback from deployments, organized by country, to facilitate the planning and prioritization of featu...) |
DanielDrake (talk | contribs) No edit summary |
||
(23 intermediate revisions by 2 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}} |
|||
==Overview== |
==Overview== |
||
This page provides a space for aggregating feedback from deployments, organized by country, to facilitate the planning and prioritization of features in upcoming releases. This should include 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. As specific goals, features, bugs, and requests accumulate here, OLPC engineers will create new entries on the [[Feature_roadmap | Feature Roadmap]] to track them, linking to the raw feedback in this section as appropriate. This page goes hand-in-hand with the [[Feature roadmap]] page, as follows: |
|||
===What's on this page?=== |
|||
;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. |
|||
;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). |
|||
As specific goals, features, bugs, and requests accumulate here, OLPC engineers will create new entries on the [[Feature_roadmap | Feature Roadmap]] to track them, linking to the raw feedback in this section as appropriate. |
|||
See also: [[Deployments]] |
See also: [[Deployments]] |
||
== 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 so we know who made the edits. |
||
# Feel free to add to this page following the guidelines described above. |
# Feel free to add to this page following the guidelines described above. |
||
Line 18: | Line 23: | ||
# 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. |
||
== Greg's Top 10 Requests == |
|||
This section lists the items which I ([[User:Gregorio|Gregorio]] 19:48, 3 November 2008 (UTC)) think are most important to improving the XO experience in the school. These items were all gathered via direct input from deployments. These items are not listed in priority order. |
|||
# Activation lease management: http://wiki.laptop.org/go/Feature_roadmap#Activation_lease_security |
|||
# Better power management: http://wiki.laptop.org/go/Feature_roadmap#Power_management |
|||
# Reliable synchronous collaboration: http://wiki.laptop.org/go/9.1.0_Collaboration_Requirements |
|||
# Reliable touchpad: http://wiki.laptop.org/go/Feature_roadmap#Accurate_touchpad |
|||
# No lost files: http://wiki.laptop.org/go/Feature_roadmap#Journal_never_loses_work |
|||
# Performance improvements: http://wiki.laptop.org/go/Feature_roadmap#Performance |
|||
# Projects and asynchronous collaboration: http://wiki.laptop.org/go/Feature_roadmap#Asynchronous_collaboration |
|||
# Chinese and Amharic support: http://wiki.laptop.org/go/Feature_roadmap#Localization |
|||
# More easily run any Linux application. http://wiki.laptop.org/go/Feature_roadmap/Run_Fedora_applications_on_XO. Add the ability to run any "standard" Linux application on the XO when the XO uses a "standard" windowing manager with unmodified Linux file system and an otherwise "stock" Fedora implementation. |
|||
# Full Flash and Youtube support |
|||
==Requests by country== |
==Requests by country== |
||
=== Ghana === |
|||
- USB - VGA projector capability. Reported by Brian from country workshop. |
|||
=== Uruguay === |
=== Uruguay === |
||
Line 32: | Line 52: | ||
# Journal to USB simplification |
# Journal to USB simplification |
||
# Sugar performance improvements |
# Sugar performance improvements |
||
# Reader should not create extra copies of PDF http://www.mail-archive.com/devel@lists.laptop.org/msg14839.html |
|||
# Collaboration (?) |
# Collaboration (?) |
||
# 802.1X (target roll out in 1 month) |
# 802.1X (target roll out in 1 month) 802.11i (wireless version). |
||
# Web signed certificate |
# Web signed certificate |
||
Line 72: | Line 93: | ||
=== Peru === |
=== Peru === |
||
Peru Wiki section. |
|||
Spanish <br> |
Spanish <br> |
||
100K x XOs |
100K x XOs |
||
Line 82: | Line 104: | ||
100K XOs with build 703 |
100K XOs with build 703 |
||
Expected to update them each year at the beginning of the school year (Feb). |
|||
---- |
---- |
||
Line 89: | Line 109: | ||
Source: Kim trip from July 2008. <br> |
Source: Kim trip from July 2008. <br> |
||
Requirement - if the laptop is stolen, and doesn't contact its local |
Requirement - if the laptop is stolen, and doesn't contact its local |
||
school server within some period time (activation lease time); then it |
|||
⚫ | |||
will tell the user that it will not activate on next boot and provide |
|||
date and time. When it gets in the vicinity of the school server again, |
|||
⚫ | |||
Requirement - it is not possible to set the date on the laptop to keep |
Requirement - it is not possible 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. |
|||
''' Request number 2: Improved performance''' <br> |
''' Request number 2: Improved performance''' <br> |
||
Source: Wad trip in April 2008 |
Source: Wad trip in April 2008 |
||
Speeding up the user interface especially time to launch activities (other?) |
Speeding up the user interface especially time to launch activities (other?) |
||
''' Request number 3: Easy creation of image with Peru specific |
''' Request number 3: Easy creation of image with Peru specific |
||
activities and content'''<br> |
|||
Source: Kim trip from July 2008. <br> |
Source: Kim trip from July 2008. <br> |
||
This should allow them to add their own content and set of activities to |
This should allow them to add their own content and set of activities to |
||
a build after it is finalized and released by OLPC. The goal is for |
|||
minimal or no OLPC involvement needed. |
|||
''' Request number 4: School Server monitoring of XOs''' <br> |
''' Request number 4: School Server monitoring of XOs''' <br> |
||
Source: Kim trip from July 2008. <br> |
Source: Kim trip from July 2008. <br> |
||
I think there might be some work in the XO to make the information |
|||
I think there might be some work in the XO to make the information available; and a database and API spec from the school server. 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. |
|||
available; and a database and API spec from the school server. 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. |
|||
Requirement: Provide XS database and an API so that countries can create |
Requirement: Provide XS database and an API so that countries can create |
||
reports and monitoring for various aspects of XOs: |
|||
* Version of code |
* Version of code |
||
Line 123: | Line 158: | ||
Requirements for groups (in priority order for Peru) <br> |
Requirements for groups (in priority order for Peru) <br> |
||
# Project Groups, which can be set up on the XO. These groups might stay together for days, weeks, or months - for example to discuss growing different vegetables or flowers. Generally smaller than a classroom. These groups can be created by students. |
# Project Groups, which can be set up on the XO. These groups might stay together for days, weeks, or months - for example to discuss growing different vegetables or flowers. Generally smaller than a classroom. These groups can be created by students. |
||
# Groups per classroom, to be set up on a School Server by someone with special access (needs a UI that can be use by a teacher with password, for instance). Use case is to be able to hand out books, vocabulary lists, etc. these would be best to do within a class. |
# Groups per classroom, to be set up on a School Server by someone with special access (needs a UI that can be use by a teacher with password, for instance). Use case is to be able to hand out books, vocabulary lists, etc. these would be best to do within a class. |
||
# Groups at the grade level because each grade will have some common curriculum. This would be set up at the school server and require special access. |
# Groups at the grade level because each grade will have some common curriculum. This would be set up at the school server and require special access. |
||
''' Request number 6: Backup and restore of XO user data''' <br> |
''' Request number 6: Backup and restore of XO user data''' <br> |
||
Make it easy to backup of the laptops. Should allow backup of user data |
Make it easy to backup of the laptops. Should allow backup of user data |
||
before upgrade or clean install and then restore. Partially met by |
|||
http://wiki.laptop.org/go/XS_Blueprints:Datastore_Simple_Backup_and_Restore |
|||
''' Request number 7: Better power management and longer battery life. <br> |
''' Request number 7: Better power management and longer battery life. <br> |
||
Met by http://wiki.laptop.org/go/Feature_Longer_battery_life but needs |
Met by http://wiki.laptop.org/go/Feature_Longer_battery_life but needs |
||
to be a fully functional and supported feature. |
|||
'''Request number 8: XS server running on XO''' <br> |
'''Request number 8: XS server running on XO''' <br> |
||
Source: Kim trip from July 2008. <br> |
Source: Kim trip from July 2008. <br> |
||
Can require additional HW (e.g. SD card or USB drive) on XO. Not |
Can require additional HW (e.g. SD card or USB drive) on XO. Not |
||
completely clear how important this one is to Peru. |
|||
'''Other Requirements from Peru''' <br> |
'''Other Requirements from Peru''' <br> |
||
Source: Carla report. <br> |
Source: Carla report. <br> |
||
# Allow upgrading with Kingston USB keys |
# Allow upgrading with Kingston USB keys |
||
# Tool integrated with the XO to collect teacher feedback on trainings |
# Tool integrated with the XO to collect teacher feedback on trainings |
||
# Build training tools and enhance the training experience |
# Build training tools and enhance the training experience |
||
Line 146: | Line 185: | ||
* More/all activities in Spanish. |
* More/all activities in Spanish. |
||
* Audio issues with Speak (bug id?) |
* Audio issues with Speak (bug id?) |
||
* XO failures (HW or SW) not easily repaired. |
* XO failures (HW or SW) not easily repaired. |
||
* Many battery failures. May have been due to HW failure in the AC - DC |
* Many battery failures. May have been due to HW failure in the AC - DC |
||
adapter. |
|||
* Frowny face of death (killed XO by hitting many keys at once?). Not |
* Frowny face of death (killed XO by hitting many keys at once?). Not |
||
sure how this happened but required re-flash once it did. |
|||
* Touchpad issues. |
* Touchpad issues. |
||
* Getting everyone on the same Mesh channel was hard. Also a problem |
* Getting everyone on the same Mesh channel was hard. Also a problem |
||
when kids on one channel wanted to "chat" with kids from another channel. |
|||
Top activities: |
Top activities: |
||
Line 214: | Line 256: | ||
Lower Power Consumption P1 <br> |
Lower Power Consumption P1 <br> |
||
Touchpad P1 <br> |
Touchpad P1 <br> |
||
Amharic fix bug ID 8494 <br> |
Amharic fix bug ID 8494 P1<br> |
||
RPM install to allow Akili P2 <br> |
RPM install to allow Akili P2 <br> |
||
Power button not understood P2 <br> |
Power button not understood P2 <br> |
Latest revision as of 16:05, 10 February 2011
For current information on OLPC's feature planning process, see Release Process Home.
OverviewThis page provides a space for aggregating feedback from deployments, organized by country, to facilitate the planning and prioritization of features in upcoming releases. This should include 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. As specific goals, features, bugs, and requests accumulate here, OLPC engineers will create new entries on the Feature Roadmap to track them, linking to the raw feedback in this section as appropriate. This page goes hand-in-hand with the Feature roadmap page, as follows:
See also: Deployments Suggestions for providing input
Greg's Top 10 RequestsThis section lists the items which I (Gregorio 19:48, 3 November 2008 (UTC)) think are most important to improving the XO experience in the school. These items were all gathered via direct input from deployments. These items are not listed in priority order.
Requests by countryGhana- USB - VGA projector capability. Reported by Brian from country workshop. UruguaySpanish New formulation of requirements from Uruguay. Build customization is top priority. Order of the remaining items does not reflect priority.
Rough notes below this line. From Emiliano and Erik in e-mail: They would also like control over their developer key issuance, rather than relying on us to serve them. (Kim, 10/26/08) An efficient system upgrade method (ideally this preserves user ata, ideally it can be done in schools with minimal manual effort).
List of changes in the new build (to be used to decide the best time to upgrade their deployed systems).
Request from Uruguay for HW alerts: In e-mail to Greg S: Better Flash support. Minimum on par with FF 3 on XP. From ErikG trip:
Notes from the peanut gallery:
PeruPeru Wiki section.
Spanish http://wiki.laptop.org/go/OLPC_Peru http://wiki.laptop.org/go/Peru_activity_pack 40K XOs with 656 100K XOs with build 703 Request number 1: Activation lease security feature Requirement - if the laptop is stolen, and doesn't contact its local school server within some period time (activation lease time); then it will tell the user that it will not activate on next boot and provide date and time. When it gets in the vicinity of the school server again, it will be re-activated automatically. Requirement - it is not possible 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. Request number 2: Improved performance Speeding up the user interface especially time to launch activities (other?) Request number 3: Easy creation of image with Peru specific
activities and content This should allow them to add their own content and set of activities to a build after it is finalized and released by OLPC. The goal is for minimal or no OLPC involvement needed. Request number 4: School Server monitoring of XOs I think there might be some work in the XO to make the information available; and a database and API spec from the school server. 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. Requirement: Provide XS database and an API so that countries can create reports and monitoring for various aspects of XOs:
Request number 5: Collaboration in groups Requirements for groups (in priority order for Peru)
Request number 6: Backup and restore of XO user data Request number 7: Better power management and longer battery life. Request number 8: XS server running on XO Other Requirements from Peru
Source: Two interns back from Peru
adapter.
sure how this happened but required re-flash once it did.
when kids on one channel wanted to "chat" with kids from another channel. Top activities:
HaitiKreyol Rough feedback from Bastien. Unedited. Need prioritization and lots more details. Gregorio 20:40, 23 October 2008 (UTC)
See also: http://lumiere.ens.fr/~guerry/olpc_feedback.php Comment from Wanda:
Wanted more. Application releases that will grow with the kids, have an application release periodically. Rwanda10K x XOs with English keyboards. Raw feedback from Juliano and Brian. Needs clarification, updating and additional details:
EthiopiaAmharic 5k x XOs They need some fixes to Amharic implementation which require a piece of software called SCIM. See http://wiki.laptop.org/go/9.1.0#Localization for more details. No Internet access currently available and no school servers planned. May consider school servers if they can get critical features from them (e.g. lease activation). Top request so far is lease activation that times out if XO doesn't call home. Verbatim from Eskender:
Dan's input on top priorities from Ethiopia: ArabicLebanon? BirminghamEnglish G1G1English MexicoSpanish MongoliaMongolian? 20K x XOs Comments from Elana: http://lists.laptop.org/pipermail/devel/2008-October/019994.html Abbreviated here: |