User:Alsroot/Sugar Architecture: Difference between revisions

(20 intermediate revisions by the same user not shown)

Line 46:

=== Platform Team ===

The mission of the Platform Team is ~~creating infrastructure for~~ Sugar ecosystem:

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

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

==== ~~Tracked projects~~ ====

==== Doers environment ====

Tracked projects are analogs of Sucrose components. The key difference is that Sucrose project itself is not a core project any more, it is an independent project (like other [[#Sugar_Universe|ones]]) and Platform Team is just tracking its life cycle to consider possibility of including its particular release to the [[#Sugar_distribution|distribution]]. It looks how GNU/Linux distributions package upstream projects.

Stable Sugar Distribution is a startup kit for Sugar doers. The real doing starts where new code is involved, e.g., by getting new versions of activities or preparing and sharing new code. Thus, where read-only nature of Stable Sugar Distribution is insufficient.

~~Platform Team may consider possibility to support particular branches of tracked projects to fulfil deployments' needs.~~

~~==== Sugar distribution ====~~

The major purpose of Sugar distribution is providing a set of releases of tracked projects that are being well tested in particular environment (a set of versioned dependencies). That should help Sugar distributors to deploy Sugar. In ideal situation, they need test Sugar distribution only on their hardware.

~~There are two types of Sugar distributions:~~

* Regular, per 6 months, releases that are synced with regular releases of major GNU/Linux distributions.

* Long Term Support (LTS) releases that are synced with LTS releases of major GNU/Linux distributions (if possible).

~~Having LTS releases should simplify sugar deployments since, in most cases, 6 months is too short major releases cycle.~~

~~==== Doer's environment ====~~

Sugar ~~distribution~~ is a startup kit for Sugar doers. The real doing starts where new code is involved, e.g., by getting new versions of activities or preparing and sharing new code. Thus, where read-only nature of Sugar ~~distribution~~ is insufficient.

The key features that any Sugar doer needs, are:

Line 79:

Line 64:

* share the code on more regular basis, i.e., uploading changed code to the server.

~~These features are critically important and should as simple as possible. It is exactly the purpose behind Zero Sugar initiative (except coding tools, i.e., code editors and IDEs):~~

=== Sugar Universe ===

* [[Activity_Team/Zero_Sugar|Overview]]

* [[Platform_Team/Overview|Bazaar]]

~~=== No Development Team ===~~

The word ''development'' is quite confusing. Is it about any development within sugar community, how about Activity Team, etc. Sucrose projects will flow to the rest of Sugar [[#Sugar_universe|universe]] and will be, by default, [[#Tracked_projects|tracked projects]] of [[#Platform_Team|Platform Team]].

=== Sugar ~~universe~~ ===

Thats the matter of Sugar, i.e., what makes Sugar useful. The variety of Sugar software projects, Glucose projects, libraries and activities.

~~Most of them are being developed and supported by individuals~~ (~~mostly activities~~)~~, the rest are using management model which is most useful for them. All of them are self organized structures~~ and ~~have their own release schedules and roadmaps, though [[#Tracked_projects|tracked project]] work in close interaction~~ with the Platform Team.

Sugar projects work closely with the Core Team (that generates ideas) and with the Platform Team (that provides the technical floor).

~~=== Collaboration ===~~

Most of them are being developed and supported by individuals (mostly activities), the rest are using management model which is most useful for them. All of them are self organized structures and have their own release schedules and roadmaps, though [[#Sugar Distribution|Sugar Distribution]] projects release new versions in close interaction with the Platform Team.

~~It would be good to make clear [[Best_Collaboration_Practices|some statements]], using existed experience, about how collaboration might happen within Sugar community.~~

=== Progress ===

~~=== Questions ===~~

* [[Platform_Team/Roadmap|Initial release of Doers Environment]]

~~'''To designers'''~~

== The whole picture ==

* Should Core Team be a home team for ~~designers instead~~ of ~~Design Team?~~

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.

~~'''To distributors'''~~

When community of Sugar doers is:

* Should Platform Team be a home team for distributors instead of ~~Deployment Team?~~

* Should incremental Sugar ~~distribution releases of the same LTS release contain new users visible features?~~

~~== 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~~]] ~~and [[#Doer~~'~~s_environment|useful instruments]] 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~~.

* 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 46: / Line 46: @@
 === Platform Team ===
-The mission of the Platform Team is creating infrastructure for Sugar ecosystem:
+The mission of the Platform Team is functionally support Sugar ecosystem from technical side:
+* 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.
-==== Tracked projects ====
+==== Doers environment ====
-Tracked projects are analogs of Sucrose components. The key difference is that Sucrose project itself is not a core project any more, it is an independent project (like other [[#Sugar_Universe|ones]]) and Platform Team is just tracking its life cycle to consider possibility of including its particular release to the [[#Sugar_distribution|distribution]]. It looks how GNU/Linux distributions package upstream projects.
+Stable Sugar Distribution is a startup kit for Sugar doers. The real doing starts where new code is involved, e.g., by getting new versions of activities or preparing and sharing new code. Thus, where read-only nature of Stable Sugar Distribution is insufficient.
-Platform Team may consider possibility to support particular branches of tracked projects to fulfil deployments' needs.
-==== Sugar distribution ====
-The major purpose of Sugar distribution is providing a set of releases of tracked projects that are being well tested in particular environment (a set of versioned dependencies). That should help Sugar distributors to deploy Sugar. In ideal situation, they need test Sugar distribution only on their hardware.
-There are two types of Sugar distributions:
-* Regular, per 6 months, releases that are synced with regular releases of major GNU/Linux distributions.
-* Long Term Support (LTS) releases that are synced with LTS releases of major GNU/Linux distributions (if possible).
-Having LTS releases should simplify sugar deployments since, in most cases, 6 months is too short major releases cycle.
-==== Doer's environment ====
-Sugar distribution is a startup kit for Sugar doers. The real doing starts where new code is involved, e.g., by getting new versions of activities or preparing and sharing new code. Thus, where read-only nature of Sugar distribution is insufficient.
 The key features that any Sugar doer needs, are:
@@ Line 79: / Line 64: @@
 * share the code on more regular basis, i.e., uploading changed code to the server.
-These features are critically important and should as simple as possible. It is exactly the purpose behind Zero Sugar initiative (except coding tools, i.e., code editors and IDEs):
+=== Sugar Universe ===
-* [[Activity_Team/Zero_Sugar|Overview]]
-* [[Platform_Team/Overview|Bazaar]]
-=== No Development Team ===
-The word ''development'' is quite confusing. Is it about any development within sugar community, how about Activity Team, etc. Sucrose projects will flow to the rest of Sugar [[#Sugar_universe|universe]] and will be, by default, [[#Tracked_projects|tracked projects]] of [[#Platform_Team|Platform Team]].
-=== Sugar universe ===
 Thats the matter of Sugar, i.e., what makes Sugar useful. The variety of Sugar software projects, Glucose projects, libraries and activities.
-Most of them are being developed and supported by individuals (mostly activities), the rest are using management model which is most useful for them. All of them are self organized structures and have their own release schedules and roadmaps, though [[#Tracked_projects|tracked project]] work in close interaction with the Platform Team.
+Sugar projects work closely with the Core Team (that generates ideas) and with the Platform Team (that provides the technical floor).
-=== Collaboration ===
+Most of them are being developed and supported by individuals (mostly activities), the rest are using management model which is most useful for them. All of them are self organized structures and have their own release schedules and roadmaps, though [[#Sugar Distribution|Sugar Distribution]] projects release new versions in close interaction with the Platform Team.
-It would be good to make clear [[Best_Collaboration_Practices|some statements]], using existed experience, about how collaboration might happen within Sugar community.
+=== Progress ===
-=== Questions ===
+* [[Platform_Team/Roadmap|Initial release of Doers Environment]]
-'''To designers'''
+== The whole picture ==
-* Should Core Team be a home team for designers instead of Design Team?
+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.
-'''To distributors'''
+When community of Sugar doers is:
-* Should Platform Team be a home team for distributors instead of Deployment Team?
-* Should incremental Sugar distribution releases of the same LTS release contain new users visible features?
-== 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]] and [[#Doer's_environment|useful instruments]] 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.
+* 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]].