Features-test

From OLPC

Revision as of 12:07, 21 December 2008 by Skierpage (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Various test queries that were or could be on

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

Contents

Querying software features

What to query

Features are in subcategories of Category:Software features, but querying on this matches many pages that aren't software features, because some feature subcategories such as Category:Network and Category:Network are already in use.

{{Feature tracking}} sets some other properties like Property:Is part of, so the trick is to pick one that is specified (not blank or default) in all software features. Probably Property:Is part of is safest.

That gives us 80 software features (a few may be tests).

So use | limit=200 | in queries to display all the features.

Result format

You could regenerate the old huge feature roadmap page by using | format=embed | , which would bring all the subpages back. But you're back to a large unwieldy page.

You could use a results display template to shorten some links (e.g. show the short name in the link to the subpage), but you lose the clickable column headings.

To avoid repeating the Software feature subcategory on each line, repeat the query for each subcategory and don't display it.

Creating a new feature

  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 an "Feature subcategory" from Category:Software features
  4. Find the requester(s)' wiki pages and the feature owner's User: wiki page
  5. Follow the OLPC:Style guide for page names, change Good feature name to your new subpage title.
  6. Ready? Click the button below to create a new meeting wikipage 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.


Default query ("Greg list")

The template's "Feature subcategory" parameter both sets a category and Property:Is part of. We can sort by the latter to present features by category.

This will replace section 2 of Feature roadmap Click on the arrows in any heading to sort by that heading.

Area Feature page Requested by Helps deployability Target for 9.1 Owner(s) Priority
Activity-related work Feature roadmap/Single sign-on from Browse Reuben 1y 1yes Gregorio 22
Activity-related work Feature roadmap/Spell checker in Write Yifan
Genessee
0n 0no Yifan 33
Activity-related work Feature roadmap/Easy "Sugarization" Wanda
David
0n 0no Gregorio 22
Activity-related work Feature roadmap/Browse update and multi-media Skierpage 0n 0no 22
Activity-related work Feature roadmap/New activities Alabama
Juliano
0n 0no 22
Activity-related work Feature roadmap/Concept maps Panama
OLPC Sur
0n 0no Gregorio 33
Activity-related work Feature roadmap/Better eBook reader Alabama
Haiti
Devel thread
0n 0no Gregorio 22
Activity-related work Feature roadmap/Sugarized color picker Juliano 0n 0no 33
Activity-related work Feature roadmap/Activity updater improvements CScott 0n 0no CScott 22
Activity-related work Feature roadmap/Terminal improvements Sayamindu 0n 0no Sayamindu 33
Collaboration Feature roadmap/Collaboration groups OLPC Peru 0n 0no Eben 22
Collaboration Feature roadmap/"Candy Bag" or "Bulletin Board" activity 0n 0no 33
Collaboration Feature roadmap/Scalable link-local presence 0n 0no Morgs
Sjoerd Simons
Elliott Fairweather
Polychronis Ypodimatopoulos
33
Collaboration Feature roadmap/Synchronous collaboration Carla and David
Teachers on OLPC-Sur
Peru technical leaders
0n 0no Gregorio 22
Collaboration Feature roadmap/Asynchronous collaboration Juliano
Cynthia
0n 0no Gregorio
Martin
22
Collaboration Feature roadmap/File sharing Peru blog 0n 0no Simon
Eben
Guillaume
22
GUI and usability Feature roadmap/Keyboard navigability Homunq 0n 0no Homunq 33
GUI and usability Feature roadmap/Journal improvements CScott 0n 0no CScott
Eben
22
GUI and usability Feature roadmap/Hardware alerts OLPC Uruguay 0n 0no 33
GUI and usability Feature roadmap/Contextual help Brianne 0n 0no 33
GUI and usability Feature roadmap/Trash can Bzg 0n 0no 33
GUI and usability Feature roadmap/GUI suggestion from SJ Emulating the XO 0n 0no Emulating the XO 33
GUI and usability Feature roadmap/Scalable zoom levels UI Team
Collabora
0n 0no Eben
Collabora
33
Hardware support Feature roadmap/Grab-scroll keys Garycmartin 0n 0no Erik Garrison 33
Hardware support Feature roadmap/Blinking lights usage Mikus 0n 0no 33
Hardware support Feature roadmap/Accurate touchpad Carla
OLPC Rwanda
OLPC Ethiopia
Haiti
0n 0no Wad
PGF
Gregorio
33
Hardware support Feature roadmap/VGA Projector OLPC Ghana 1y 0no Bjordan 33
Linux and OS Feature roadmap/Copying files between Journal and USB Bzg
OLPC Uruguay
Gregorio
Linux and OS Feature roadmap/Replace JFFS file system with better one Deepak Deepak
Linux and OS Feature roadmap/File name and directory access Gnu
Ben
Erik
Greg
Marvin
Linux and OS Feature roadmap/Rebase on Fedora 10 Ed 1y 1yes Gregorio 11
Linux and OS Feature roadmap/NAND full should not crash XO OLPC Uruguay Gregorio
Linux and OS Feature roadmap/Run Fedora applications on XO Ed
David
1y 1yes Gregorio
PBRobinson
Erik
11
Localization Feature roadmap/Spell checking Sayamindu
Sur list
Sayamindu
Localization Feature roadmap/SCIM Sayamindu 1y 1yes Sayamindu 11
Localization Feature roadmap/Language customization Sayamindu
Sur list
Localization Feature roadmap/Language pack version 3 Sayamindu Sayamindu
Localization Feature roadmap/Better Arabic Support Dubai
OLPC Palestine
Lebanon refugee camps (Sabra and Shatilla)
1y 1yes Gregorio
Marc
Martin S
11
Localization Feature roadmap/RTL support OLPC Lebanon 1y 1yes Sayamindu 22
Localization Feature roadmap/Enhanced i18n Sayamindu Sayamindu
Localization Feature roadmap/Multilanguage support Sayamindu
OLPC Bolivia
OLPC Peru
OLPC Rwanda
Others?
Sayamindu
Localization Feature roadmap/Translations OLPC Mongolia
OLPC Rwanda
All
1y 1yes Sayamindu
Gregorio
11
Network Feature roadmap/"Asynchronous internet" CScott CScott
Network Feature roadmap/Reliable access to encrypted APs XO Giving
Network Feature roadmap/XO as internet gateway (formerly called MPP) OLPC Uruguay
Kimquirk
Michailis
1y 1yes 22
Network Feature roadmap/Document and improve default network connection ?
Network Feature roadmap/802.1x support OLPC Uruguay Cjb
Network Feature roadmap/Full IPv6 support Marc Blanchet Marc Blanchet
Other Feature roadmap/Caps lock option Jg None yet.
Other Feature roadmap/Universal view-source Tomeu Tomeu
Gregorio
Other Feature roadmap/Printing support CScott
Others
Gregorio
Other Feature roadmap/Debug tool OLPC Uruguay Erik Garrison
Other Feature roadmap/Fully comply with GPLv3 FSF
Gnu
Gregorio
Other Feature roadmap/Developers Center web site None yet.
Other Feature roadmap/System clock OLPC Birmingham
Seen on devel list (anyone have time to search for the threads?)
MartinDengler
Other Feature roadmap/Backup to Internet Walter 0n 0no 44
Other Feature roadmap/Library and bundle updates Emulating the XO Emulating the XO
Other Feature roadmap/Screen zoom Gregorio Gregorio
Performance Feature roadmap/General UI sluggishness OLPC Uruguay
OLPC Peru
0n 0no MarcoPesentiGritti
Erik
Gregorio
22
Performance Feature roadmap/Faster task switching OLPC Peru
OLPC Uruguay
Erik
Performance Feature roadmap/Faster activity launch and save OLPC Peru
OLPC Uruguay
Power management Feature roadmap/Improved battery life Kimquirk
Carla
Gnu
OLPC Ethiopia
Juliano
1y 1yes Joe
Gregorio
Cjb
Wmb@firmworks.com
Deepak
11
Power management Feature roadmap/No power regressions Gregorio
OLPC Ethiopia
OLPC Rwanda
Haiti.
1y 1yes Rsmith 11
Power management Feature roadmap/Shutdown menu Haiti
OLPC Rwanda
1y 1yes PGF
Gregorio
11
Reliability Feature roadmap/Clipboard Eben Eben
Tomeu
MarcoPesentiGritti
Reliability Feature roadmap/Memory pressure Elana
OLPC Peru
Carla
Jg
Reliability Feature roadmap/Journal never loses work Everyone Tomeu
Greg^
School server XS Blueprints:Datastore Simple Backup and Restore OLPC Peru
Security, activation and deployability Feature roadmap/Theft reporting Peru?
Security, activation and deployability Feature roadmap/XO monitoring OLPC Peru Kimquirk
Security, activation and deployability Feature roadmap/Security and isolation work CScott 0n 0no CScott 33
Security, activation and deployability Feature roadmap/Activation lease security OLPC Peru
Ethiopia (especially last point)
Uruguay?
1y 1yes 11
Security, activation and deployability Feature roadmap/GUI OS updates Eben
CScott
1y 1yes 11
Security, activation and deployability Feature roadmap/Faster imaging OLPC Ethiopia
OLPC Rwanda
Haiti
1y 1yes Gregorio
Reuben
Wmb@firmworks.com
22
Security, activation and deployability Feature roadmap/Activation via wireless Kimquirk 1y 1yes 11
Security, activation and deployability Feature roadmap/Image customization OLPC Uruguay
OLPC Ethiopia
OLPC Colombia
OLPC Peru
OLPC Mexico
OLPC Mongolia
1y 1yes 11
Security, activation and deployability Feature roadmap/Image signing key delegation OLPC Uruguay 1y 1yes CScott 11
Server Feature roadmap/Scalable server-based presence Guillaume Desmottes
Dafydd Harries
Eben
Morgs
Server Feature roadmap/Automatically recognize XO on restore page Reuben Gregorio
Server Feature roadmap/School server push of XO images OLPC Peru Martin


Before you ask, you can't ask for "grouping" of results to avoid area repeated over and over; instead you would repeat the query each time querying for a different areas or subcategory.

Sort by area, then priority, then name

Sorting on a property implicitly selects pages with a value for it, so this won't display a lot of subpages until every page has a priority. Click on the arrows in any heading to sort by that heading. Nothing found in Category:Software features with Property:Short name?!

Features for 9.1.0

Just query for Property:Target for 9.1 set to yes. BUT: Because this property has a dot (period, "full stop") in its name, it looks like the trick SMW feature "property chaining". As the help says

"In the rare case that a property should contain a dot in its name, one may start the query with a space to prevent SMW from interpreting this dot in a special way."

Summary table

This query sorts by area, then priority, then Short name, so it only finds pages that have values for those properties.

Nothing found in Category:Software features with Property:Target for 9.1=true?!

Embedded

Use format=embed to include entire pages matching a query for Property:Target for 9.1 set to yes. Here it's limited to 3 matches because it's confusing. Problem is: embedding a page also pulls in its categorization; we can wrap that with noinclude but can't get this to work in a preload template.

This is better done as a separate, linked page, see Feature roadmap/Page of all features that target 9.1.0

Feature roadmap/Activation lease security

Feature subcategory Category:Security, activation and deployability
Requesters Peru, Ethiopia (especially last point), Uruguay?
Requirements =Overview=

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. This state is known as passive-kill.
  • 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ío (tiempo del arriendo) el XO va a encender (boot). Este estado se conoce como muerte-pasiva.
  • 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. This state is known as activated.
  • 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ós 30 dí y comienza el 1 de noviembre, despuéel XO arranca el 20 de noviembre y entra en contacto con el XS, écontinuaráuncionando sin entrar en contacto con el XS hasta el 20 de diciembre. Este estado se conoce como activado


  • 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. Laptops that request their new lease from the XS and find themselves in the blacklist get into a state known as active-kill.
  • 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é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áha sido entrado adentro al servidor de la escuela por su administrador. Es decir, el tiempo del arriendo de la activacióeráutomácamente cuando el XO entra en contacto con su XS que controla, a menos que no se haya inscrito en la lista negra. Laptops que contactan el XS y se encuentran en la lista negra entran en un estado llamado muerte-activa.
  • 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óor del despliegue (interfaz utilizador requerido). Es decir, pueden fijarlo por 90 dí o lo que quieren. La granulosidad debe ser en 24 horas y ser a partir de 1 dí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í).


  • 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ál 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átilizada.
Note: XO-1 hardware is limited to 1 RTC clock so we cannot really do this.
  • 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.
  • Soporte los mismos requerimientos mencionados en el ultimo punto pero permita la activacion contra un servidor conectado a Internet. El servidor puede estar en un centro de datos manejado por NOC local 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.
  • Soporte 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, é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
Server side "Blueprint" at: http://wiki.laptop.org/go/XS_Blueprints:Lease_and_update_server

Specification * <trac>4043</trac>
Owners Please indicate developers or champions supporting this request
Priority 1
Helps deployability? yes
Target for 9.1? yes

Feature roadmap/Activation via wireless

Feature subcategory Category:Security, activation and deployability
Requesters User:Kimquirk
Requirements
  • Must allow activation of XOs via wireless AP connection to a School Server
  • Must work with all APs which the XO can work with. In particular, must work with open, WEP, WPA and WPAv2 APs.
  • Should allow activation of many receiver XOs from a source XO. That is, the same as above but with the "server" being an XO.
  • Must allow addition of activation keys to the Activation Server via USB.
  • Should allow addition of activation keys to the Activation Server via network access.
  • Should make it possible for the deployment to perform all activation tasks without OLPC intervention.
  • See also image customization feature.
Specification See <trac>8976</trac> Need to add wireless AP support and/or add XO as activation server support.
Owners Please indicate developers or champions supporting this request
Priority 1
Helps deployability? yes
Target for 9.1? yes

Feature roadmap/Better Arabic Support

Feature subcategory Category:Localization
Requesters Dubai, Palestine, Lebanon refugee camps (Sabra and Shatilla)
Requirements
  • Must support Right to left (RTL) in all Sugar GUI elements.
  • Must support Right to left in Write
  • Must include at least two good Arabic fonts
  • Must support shaping in Write and in Sugar.
Specification https://dev.laptop.org/ticket/6808

Test cases:

Owners User:Gregorio, User:Marc, User:Martin S
Priority 1
Helps deployability? yes
Target for 9.1? yes
… further results

What features did a country request?

Query for ([[Requested by::{{FULLPAGENAME}}]]), e.g. here's one showing what OLPC Peru requested.

OLPC Peru wants Category Technology/subsystem Target for 9.1 Requested by
Feature roadmap/Activation lease security Security, activation and deployability Security, activation and deployability 1true OLPC Peru
Ethiopia (especially last point)
Uruguay?
Feature roadmap/Collaboration groups Collaboration
Trac references
Collaboration 0false OLPC Peru
Feature roadmap/Faster activity launch and save Performance Performance OLPC Peru
OLPC Uruguay
Feature roadmap/Faster task switching Performance Performance OLPC Peru
OLPC Uruguay
Feature roadmap/General UI sluggishness Performance Performance 0false OLPC Uruguay
OLPC Peru
Feature roadmap/Image customization Security, activation and deployability Security, activation and deployability 1true OLPC Uruguay
OLPC Ethiopia
OLPC Colombia
OLPC Peru
OLPC Mexico
OLPC Mongolia
Feature roadmap/Memory pressure Reliability Reliability Elana
OLPC Peru
Carla
Feature roadmap/Multilanguage support Localization Localization Sayamindu
OLPC Bolivia
OLPC Peru
OLPC Rwanda
Others?
Feature roadmap/School server push of XO images Server Server OLPC Peru
Feature roadmap/XO monitoring Security, activation and deployability Security, activation and deployability OLPC Peru
XS Blueprints:Datastore Simple Backup and Restore Developers
SchoolServer
Software features
School server OLPC Peru


Other sample queries

Features showing category list

This queries for anything in Category:Software features, it shows category to try to show feature. (Only displays 10 results.)

in the following categories Requested by
Feature roadmap/"Asynchronous internet" Network CScott
Feature roadmap/"Candy Bag" or "Bulletin Board" activity Collaboration
Feature roadmap/802.1x support Network OLPC Uruguay
Feature roadmap/Accurate touchpad Hardware support
Touchpad
Carla
OLPC Rwanda
OLPC Ethiopia
Haiti
Feature roadmap/Activation lease security Security, activation and deployability OLPC Peru
Ethiopia (especially last point)
Uruguay?
Feature roadmap/Activation via wireless Security, activation and deployability Kimquirk
Feature roadmap/Activity updater improvements Activity-related work CScott
Feature roadmap/Asynchronous collaboration Collaboration Juliano
Cynthia
Feature roadmap/Automatically recognize XO on restore page Server Reuben
Feature roadmap/Backup to Internet Other Walter
… further results


But, as you see below you can't sort on category display! Maybe have to have Property:Feature subcategory, like Property:Test subcategory, or use Is part of::Power management, Is_part_of::Journal , etc. Nothing found in Category:Software features with Property:Is part of when we try to sort by Category.

Personal tools
  • Log in
  • Login with OpenID
About OLPC
About the laptop
About the tablet
Projects
OLPC wiki
Toolbox