Difference between revisions of "Platform Team/Server Kit"
Jump to navigation
Jump to search
(→The purpose: be more explanatory for core purposes) |
|||
| Line 5: | Line 5: | ||
The Server initiative is an attempt to achieve three major goals: | The Server initiative is an attempt to achieve three major goals: | ||
| − | * Provide a split between the community level project (Sugar Server) and | + | * Provide a split between the community level project (Sugar Server) and any number of downstream solutions based on the community project. This should stimulate the downstream community to contribute to this upstream community project, facilitating reuse of its experience in all other downstreams; |
| − | * Treat the community project as a collection of useful tools that might be composed into a final deployment solution on purpose, i.e., Sugar Server is not an OS or final solution but a bunch of tools that might be launched on | + | * Treat the community project as a collection of useful tools that might be composed into a final deployment solution on purpose, i.e., Sugar Server is not an OS or a final solution, but rather a bunch of tools that might be launched on any major GNU/Linux distribution at the deployment level. And because some of these tools might be implemented in several ways, it should make the acceptance process of new features by upstream more flexible; |
* The whole system should be as reliable as possible. Thus, the community project will provide a decent testing environment (several levels of automatic and human driven tests at the top level), which might be used not only for Sugar Server itself, but for deployment solutions as well. | * The whole system should be as reliable as possible. Thus, the community project will provide a decent testing environment (several levels of automatic and human driven tests at the top level), which might be used not only for Sugar Server itself, but for deployment solutions as well. | ||
Revision as of 11:51, 8 July 2011
The purpose
The Server initiative is an attempt to achieve three major goals:
- Provide a split between the community level project (Sugar Server) and any number of downstream solutions based on the community project. This should stimulate the downstream community to contribute to this upstream community project, facilitating reuse of its experience in all other downstreams;
- Treat the community project as a collection of useful tools that might be composed into a final deployment solution on purpose, i.e., Sugar Server is not an OS or a final solution, but rather a bunch of tools that might be launched on any major GNU/Linux distribution at the deployment level. And because some of these tools might be implemented in several ways, it should make the acceptance process of new features by upstream more flexible;
- The whole system should be as reliable as possible. Thus, the community project will provide a decent testing environment (several levels of automatic and human driven tests at the top level), which might be used not only for Sugar Server itself, but for deployment solutions as well.
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