XS Community Edition/Features/user portal: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (moved XS Community Edition/feature/user portal to XS Community Edition/Features/user portal: match Community Edition style and pluralize)
 
Line 20: Line 20:


== Current status ==
== Current status ==
* Targeted release: 0.5
* Targeted release: 0.6
* Last updated: October 21, 2013
* Last updated: October 21, 2013
* Percentage of completion: 0%
* Percentage of completion: 0%

Latest revision as of 15:08, 3 November 2013

This IIAB XSCE content does not reflect the opinion of OLPC. These pages were created by members of a volunteer community supporting OLPC and deployments.



Summary

A user portal shown when XO client connects to the server.

Owner

Current status

  • Targeted release: 0.6
  • Last updated: October 21, 2013
  • Percentage of completion: 0%

Detailed Description

These are the features we would like to have present on the portal:

  • Show a different portal page when the client is not connected to the server
  • Multilingual support
  • Capability for a deployment to modify based on their needs
  • Ability to discover installed services and render links

Benefit to XSCE

What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will XSCE become a better platform or project because of this feature?

Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.

Scope

What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?

UI Design

Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.

How To Test

Testing notes go here

User Experience

If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.

Dependencies

What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?

Contingency Plan

If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.

Documentation

Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.

Release Notes

The XSCE Release Notes inform end-users about what is new in the release. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.

Comments and Discussion