Difference between revisions of "Platform Team/Server Kit"
Jump to navigation
Jump to search
m |
|||
| Line 17: | Line 17: | ||
* [http://wiki.laptop.org/go/NEXS_-_Build_System Nepalese XS deployment] | * [http://wiki.laptop.org/go/NEXS_-_Build_System Nepalese XS deployment] | ||
* [http://wiki.laptop.org/go/Nepal_Wish_List Nepal wish list] | * [http://wiki.laptop.org/go/Nepal_Wish_List Nepal wish list] | ||
| + | |||
| + | == Subpages == | ||
| + | |||
| + | {{Special:PrefixIndex/{{PAGENAMEE}}/}} | ||
Revision as of 06:53, 16 June 2011
The purpose
An attempt to refocus the School Server paradigm from "only a School Server on a server at school" to "having tough and localized software components to use for a purpose". The core component, sugar-server, should just work after installing from packages if a school needs only basic functionality in an already set up environment. It works without close maintenance from skilled personal. But if a school or deployment needs more functionality, and they have spare servers, the additional components might be used to fulfill local needs.
Start from
Related Resources
- OLPC School Server
- Paraguayan XS deployment
- Australian XS deployment
- Nepalese XS deployment
- Nepal wish list
Subpages
- Platform Team/Server Kit/Architecture
- Platform Team/Server Kit/Architecture/The purpose
- Platform Team/Server Kit/Guide/Usage Statistics
- Platform Team/Server Kit/Mace
- Platform Team/Server Kit/sugar-client
- Platform Team/Server Kit/sugar-server
- Platform Team/Server Kit/sugar-server-templates
- Platform Team/Server Kit/sugar-unit