User:Alsroot/Sugar Architecture: Difference between revisions

Line 54:

* 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

* Release a product - Sugar Platform distribution.

~~Out side of the~~ Platform Team~~, Sugar is a community~~ of:

The Platform Team consist of:

* ~~Open minded educators~~, ~~designers and just thinkers who don't asked themselves, ''Am I doing right, designing/thinking-about this, so invasive for Sugar, feature?'' and free in choosing the way they think is important.~~

* Release Manager,

* ~~Open minded doers~~ of Sugar ~~[[#Sugar_universe|projects]]~~, who ~~don't asked themselves, ''Am I doing right, implementing this, so invasive for Sugar, feature?''~~ and ~~free in choosing the way they think is important.~~

* Representatives of major Sugar deployments,

* People who support and coordinate [[#Doer's_environment|doer's environment]].

~~And only inside the Platform Team:~~

* People who take part in preparing [[#Sugar_distribution]], [[Bug Squad]], [[Documentation Team]], members.

* Sugar is a product, [[#~~Sugar_distribution~~|~~Sugar distribution~~]].

* ~~Released by~~ [[#Sugar_distribution~~|distribution~~]] ~~coordinators~~, ~~not by developers of~~ [[~~#Sugar_universe|projects~~]].

* All responsibilities about how this product looks and behaves go to the Platform Team from developers of particular [[~~#Sugar_universe|project~~]].

==== Tracked projects ====

Line 128:

Line 125:

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]], [[#Doer's_environment|useful instruments]] and [[#Standard_Team|rules-how-communicate]] to Sugar [[#Sugar_universe|doers]] to let them gain an [[#Common|experience and knowledge]] during the process of implementation, and [[#Sugar_distribution|spreading]] the results within Sugar community.

When community of Sugar doers is:

* Open minded educators, designers and just thinkers who don't asked themselves, ''Am I doing right, designing/thinking-about this, so invasive for Sugar, feature?'' and free in choosing the way they think is important.

* Open minded developers of Sugar [[#Sugar_universe|projects]], who don't asked themselves, ''Am I doing right, implementing this, so invasive for Sugar, feature?'' and free in choosing the way they think is important.

* Purpose minded [[#Platform_Team|Platform Team]] that releases the [[#Sugar_distribution|product]].

@@ Line 54: / Line 54: @@
 * 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
+* Release a product - Sugar Platform distribution.
-Out side of the Platform Team, Sugar is a community of:
+The Platform Team consist of:
-* Open minded educators, designers and just thinkers who don't asked themselves, ''Am I doing right, designing/thinking-about this, so invasive for Sugar, feature?'' and free in choosing the way they think is important.
+* Release Manager,
-* Open minded doers of Sugar [[#Sugar_universe|projects]], who don't asked themselves, ''Am I doing right, implementing this, so invasive for Sugar, feature?'' and free in choosing the way they think is important.
+* Representatives of major Sugar deployments,
+* People who support and coordinate [[#Doer's_environment|doer's environment]].
-And only inside the Platform Team:
+* People who take part in preparing [[#Sugar_distribution]], [[Bug Squad]], [[Documentation Team]], members.
-* Sugar is a product, [[#Sugar_distribution|Sugar distribution]].
-* Released by [[#Sugar_distribution|distribution]] coordinators, not by developers of [[#Sugar_universe|projects]].
-* All responsibilities about how this product looks and behaves go to the Platform Team from developers of particular [[#Sugar_universe|project]].
 ==== Tracked projects ====
@@ Line 128: / Line 125: @@
 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]], [[#Doer's_environment|useful instruments]] and [[#Standard_Team|rules-how-communicate]] to Sugar [[#Sugar_universe|doers]] to let them gain an [[#Common|experience and knowledge]] during the process of implementation, and [[#Sugar_distribution|spreading]] the results within Sugar community.
+When community of Sugar doers is:
+* Open minded educators, designers and just thinkers who don't asked themselves, ''Am I doing right, designing/thinking-about this, so invasive for Sugar, feature?'' and free in choosing the way they think is important.
+* Open minded developers of Sugar [[#Sugar_universe|projects]], who don't asked themselves, ''Am I doing right, implementing this, so invasive for Sugar, feature?'' and free in choosing the way they think is important.
+* Purpose minded [[#Platform_Team|Platform Team]] that releases the [[#Sugar_distribution|product]].