XS Community Edition/Features/management gui
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.
Comments and Explanations:
Copy the source of this template to a new page named Feature/Your Feature Name before making changes! DO NOT EDIT THIS TEMPLATE BY MISTAKE.
Contents
Summary
Administration and Management GUI
Owner
This should link to your home wiki page so we know who you are
- Name: Miguel González Álvarez
- Email: migonzalvar@activitycentral.com
Current status
- Targeted release: 0.5
- Last updated: October 21, 2013
- Percentage of completion: 50%
Detailed Description
A UI for administering the school server has been a big requirement over the years. This feature implements the UI using a service called Ajenti.
Benefit to XSCE
Ajenti enables the control of various aspects of the school server through a user interface. It also enables the creation of a framework through which services can be added scalably (Ajenti is written in python and is quite actively developed and maintained)
Scope
The codebase needs to be moved from the dextrose server (https://github.com/activitycentral/dxs) to the XSCE. The playbooks already exist so it should just be a matter of porting and testing.
See the Ajenti folder: https://github.com/activitycentral/dxs/tree/master/roles/ajenti
UI Design
See screenshots here: http://ajenti.org/
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.
