Difference between revisions of "Platform Team/Server Kit"

Revision as of 08:13, 6 July 2011

The Server initiative is an attempt to achieve three major goals:

Make a split to community level project (Sugar Server) and a bunch of downstream solutions based on community project;
Treating community project as a collection of useful tools that might be composed to the final deployment solution on purpose, i.e., Sugar Server is not an OS but a bunch of tools that might be launched on all major GNU/Linux distributions on deployment level;
The whole system should reliable as much as possible. Thus, community project will provide decent testing environment (several levels of automatic tests and human driven on the top level) that might be used not only for Sugar Server itself but for deployment solutions as well.

@@ Line 3: / Line 3: @@
 == 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.
+The Server initiative is an attempt to achieve three major goals:
+* Make a split to community level project (Sugar Server) and a bunch of downstream solutions based on community project;
+* Treating community project as a collection of useful tools that might be composed to the final deployment solution on purpose, i.e., Sugar Server is not an OS but a bunch of tools that might be launched on all major GNU/Linux distributions on deployment level;
+* The whole system should reliable as much as possible. Thus, community project will provide decent testing environment (several levels of automatic tests and human driven on the top level) that might be used not only for Sugar Server itself but for deployment solutions as well.
 == Start from ==