Changes

no edit summary
Line 1: Line 1:  
== Summary ==
 
== Summary ==
   −
Sweets is a [http://en.wikipedia.org/wiki/Package_management_system Package Management System] based on [http://0install.net/ Zero Install], a decentralized cross-distribution software installation system. It is intended to distribute various software projects created in Sugar ecosystem such as libraries, sugar itself, sugar activities.
+
Sweets is a [http://en.wikipedia.org/wiki/Package_management_system Package Management System] based on [http://0install.net/ Zero Install], a decentralized cross-distribution software installation system. It is intended to distribute various software projects created in the Sugar ecosystem, such as libraries, sugar itself, and sugar activities.
   −
New distribution method is initiated assuming that:
+
This new distribution method is initiated assuming that:
    
* The method to share software projects should to be as convenient as possible.
 
* The method to share software projects should to be as convenient as possible.
* It is important to stimulate users being doers, change existed activities and share results of experiments between other people, i.e., distribution method should handle different variants of the same project.
+
* It is important to stimulate users into becoming doers, to modify existing activities, and to share the results of their experiments with other people, i.e., a distribution method should handle different variants of the same project.
 
* This distribution method is not intended to be the only one.
 
* This distribution method is not intended to be the only one.
   −
The purpose to create new distribution method instead of reusing:
+
The purpose is to create a new distribution method instead of reusing:
    
* ''.xo bundles''
 
* ''.xo bundles''
** Work smooth only for pure python activities and only if all (and the same) dependencies are installed on all systems. It stop working smooth if activities use non-standard dependencies or contain binaries.
+
** Work smoothly only for pure python activities, and only if all (and the same) dependencies are installed on all systems. They stop working smoothly if activities use non-standard dependencies or contain binaries.
 
** Users need to manually handle the variety of activity versions, e.g., sort out all local bundles or directories in {{Code|~/Activities}}.
 
** Users need to manually handle the variety of activity versions, e.g., sort out all local bundles or directories in {{Code|~/Activities}}.
 
* ''native packages''
 
* ''native packages''
 
** Not the shortest way between developers and users.
 
** Not the shortest way between developers and users.
** In most cases it doesn't support multiple versions of the same project.
+
** In most cases, they don't support multiple versions of the same project.
** It doesn't work at all for sharing results of experiments.
+
** They don't work at all for sharing results of experiments.
   −
At the same time existed distribution methods are reused in Sweets:
+
At the same time, existing distribution methods are reused in Sweets:
   −
* ''.xo bundles'' is a subset of Sweets workflow
+
* ''.xo bundles'' is a subset of the Sweets workflow
** It is possible to bundle entirely directory with sweet project to use it as a regular .xo file.
+
** It is possible to bundle an entire directory as a sweet project to use it as a regular .xo file.
 
* ''native packages''
 
* ''native packages''
** Sweets is not an intention to create one more GNU/Linux distribution. It distributes only projects people create within Sugar community, the rest of software will be reused from native packages.
+
** Sweets is not intended to create one more GNU/Linux distribution. It distributes only projects that people create within the Sugar community; all other software will be reused from native packages.
    
== Start from ==
 
== Start from ==