Difference between revisions of "Platform Team/Server Kit"

Revision as of 10:26, 8 July 2011

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

Provide a split between the community level project (Sugar Server) and a bunch of downstream solutions based on the community project. That should stimulate a downstream to contribute to the upstream community project to reuse 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 all major GNU/Linux distributions at the deployment level. Besides, some of these tools might be implemented using several ways, i.e., it should make acceptance process of new features to 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.

@@ Line 5: / Line 5: @@
 The Server initiative is an attempt to achieve three major goals:
-* Provide a split between the community level project (Sugar Server) and a bunch of downstream solutions based on the community project;
+* Provide a split between the community level project (Sugar Server) and a bunch of downstream solutions based on the community project. That should stimulate a downstream to contribute to the upstream community project to reuse 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 but a bunch of tools that might be launched on all major GNU/Linux distributions at the deployment level;
+* 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 all major GNU/Linux distributions at the deployment level. Besides, some of these tools might be implemented using several ways, i.e., it should make acceptance process of new features to 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.