Changes

Jump to navigation Jump to search
no edit summary
Line 24: Line 24:  
# '''Change the minds'''<br>Once Sugar might be a product, it is critically important to understand the unoriginality of this fact. Deploying the Sugar gives only the first push (technical possibility to run Sugar). The major behaviour (including sharing various sugar components to run) happens within the community; in class, school, region, around the world.
 
# '''Change the minds'''<br>Once Sugar might be a product, it is critically important to understand the unoriginality of this fact. Deploying the Sugar gives only the first push (technical possibility to run Sugar). The major behaviour (including sharing various sugar components to run) happens within the community; in class, school, region, around the world.
 
# '''Organized chaos'''<br>Keeping in mind all premisses, any trying to create a concrete organizational structure for Sugar itself (but not for its particular components when concrete organization makes sense, e.g., for deployments) is defected by design. On high level, ecosystem might be a set of self-organized components that need only rules to interact with each other.
 
# '''Organized chaos'''<br>Keeping in mind all premisses, any trying to create a concrete organizational structure for Sugar itself (but not for its particular components when concrete organization makes sense, e.g., for deployments) is defected by design. On high level, ecosystem might be a set of self-organized components that need only rules to interact with each other.
 +
 +
== Implementation ==
 +
 +
Start key points:
 +
* Before arguing with implementation details, check if you are agree with [[#Premises|premisses]].
 +
* For the first time, nothing will be changed for, e.g., Sugar deployments (if it will be changed at all).
 +
* Implementation might take several core releases, it is exactly about step-by-step Sugar evolution.
 +
 +
 +
# LTS sugar releases
 +
# modularizing sugar core
 +
# ...

Navigation menu