Platform Team/Server Kit: Difference between revisions

Line 5:

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;

* Provide a split between the community level project (Sugar Server) and a bunch of downstream solutions based on the 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;

* 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;

* 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.

* 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 ==

@@ Line 5: / Line 5: @@
 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;
+* Provide a split between the community level project (Sugar Server) and a bunch of downstream solutions based on the 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;
+* 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;
-* 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.
+* 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 ==