User:Alsroot/Sugar Architecture: Difference between revisions

(One intermediate revision by the same user not shown)

Line 46:

=== Platform Team ===

The mission of the Platform Team is support Sugar ecosystem from technical side:

The mission of the Platform Team is functionally support Sugar ecosystem from technical side:

* ~~Take~~ care ~~of technical standards (API, DBus interface, etc)~~ to ~~let all Sugar components/activities interact smooth~~.

* Develop new or tune existed services that might be useful for Sugar ecosystem. It is not about taking job from Infrastructure Team that does technical support for Sugar Labs servers but about taking care what functionality needs to be run on these servers.

* Providing as-unified-as-possible runtime and development time environments for all Sugar doers, regardless of what platform they are using. In other words, Platform Team makes everything to let ideas, generated by Core Team (as well as any other ideas), happen within the Sugar [[#Sugar_Universe|community]].

* Work closely with GNU/Linux distributions, that provide sugar packages, and Sugar deployments to fulfill their needs and coordinate related efforts within Sugar community.

* ~~Release a product - Sugar Platform distribution.~~

* Take care of technical standards (API, DBus interface, etc) to let all Sugar components/activities interact smooth.

~~==== Sugar Distribution ====~~

~~The major purpose~~ of ~~Sugar distribution is providing a set of core Sugar components to give people read-to-use environment where they can download and launch any Sugar activity.~~

~~There might be two types of Sugar Distributions:~~

* Stable release based model, ~~is the basis for Sugar deployment distributions when Sugar Distribution is a set of stable releases.~~

* Rolling release model, ~~is intended directly~~ to Sugar ~~doers when Sugar Distribution is the singular and all time developing (that doesn't mean ''unstable'' branch for the first model, just [http://en.wikipedia.org/wiki~~/~~Rolling_release another purpose] model) environment. It is the basis for [[#Doers environment|Doers environment]].~~

~~The content of Sugar Distribution is the Glucose and some first-time-usage~~ activities, like Terminal, Log and Browse. The Platform Team doesn't code these components, just work closely with these components maintainers to prepare the Sugar Distribution. It is all about moving responsibility from developers of particular Sugar Distribution project to Platform Team about how Sugar final environment will behave for users.

==== Doers environment ====

Line 89:

Line 78:

== The whole picture ==

As the last [[#Organizational|premise]] says, the major idea is not creating concrete vertical organizational structures for Sugar ecosystem but giving [[#Core_Team|fruitful ideas]], [[#~~Doers_Environment~~|useful instruments and rules-how-communicate]] to Sugar [[#Sugar_Universe|doers]] to let them gain an [[#Common|experience and knowledge]] during the process of implementation, and [[#Doers_Environment|spreading]] the results within Sugar community.

As the last [[#Organizational|premise]] says, the major idea is not creating concrete vertical organizational structures for Sugar ecosystem but giving [[#Core_Team|fruitful ideas]], [[#Doers_environment|useful instruments and rules-how-communicate]] to Sugar [[#Sugar_Universe|doers]] to let them gain an [[#Common|experience and knowledge]] during the process of implementation, and [[#Doers_Environment|spreading]] the results within Sugar community.

When community of Sugar doers is:

@@ Line 46: / Line 46: @@
 === Platform Team ===
-The mission of the Platform Team is support Sugar ecosystem from technical side:
+The mission of the Platform Team is functionally support Sugar ecosystem from technical side:
-* Take care of technical standards (API, DBus interface, etc) to let all Sugar components/activities interact smooth.
+* Develop new or tune existed services that might be useful for Sugar ecosystem. It is not about taking job from Infrastructure Team that does technical support for Sugar Labs servers but about taking care what functionality needs to be run on these servers.
 * Providing as-unified-as-possible runtime and development time environments for all Sugar doers, regardless of what platform they are using. In other words, Platform Team makes everything to let ideas, generated by Core Team (as well as any other ideas), happen within the Sugar [[#Sugar_Universe|community]].
 * Work closely with GNU/Linux distributions, that provide sugar packages, and Sugar deployments to fulfill their needs and coordinate related efforts within Sugar community.
-* Release a product - Sugar Platform distribution.
+* Take care of technical standards (API, DBus interface, etc) to let all Sugar components/activities interact smooth.
-==== Sugar Distribution ====
-The major purpose of Sugar distribution is providing a set of core Sugar components to give people read-to-use environment where they can download and launch any Sugar activity.
-There might be two types of Sugar Distributions:
-* Stable release based model, is the basis for Sugar deployment distributions when Sugar Distribution is a set of stable releases.
-* Rolling release model, is intended directly to Sugar doers when Sugar Distribution is the singular and all time developing (that doesn't mean ''unstable'' branch for the first model, just [http://en.wikipedia.org/wiki/Rolling_release another purpose] model) environment. It is the basis for [[#Doers environment|Doers environment]].
-The content of Sugar Distribution is the Glucose and some first-time-usage activities, like Terminal, Log and Browse. The Platform Team doesn't code these components, just work closely with these components maintainers to prepare the Sugar Distribution. It is all about moving responsibility from developers of particular Sugar Distribution project to Platform Team about how Sugar final environment will behave for users.
 ==== Doers environment ====
@@ Line 89: / Line 78: @@
 == The whole picture ==
-As the last [[#Organizational|premise]] says, the major idea is not creating concrete vertical organizational structures for Sugar ecosystem but giving [[#Core_Team|fruitful ideas]], [[#Doers_Environment|useful instruments and rules-how-communicate]] to Sugar [[#Sugar_Universe|doers]] to let them gain an [[#Common|experience and knowledge]] during the process of implementation, and [[#Doers_Environment|spreading]] the results within Sugar community.
+As the last [[#Organizational|premise]] says, the major idea is not creating concrete vertical organizational structures for Sugar ecosystem but giving [[#Core_Team|fruitful ideas]], [[#Doers_environment|useful instruments and rules-how-communicate]] to Sugar [[#Sugar_Universe|doers]] to let them gain an [[#Common|experience and knowledge]] during the process of implementation, and [[#Doers_Environment|spreading]] the results within Sugar community.
 When community of Sugar doers is: