User:Alsroot/Sugar Architecture: Difference between revisions

Line 44:

Core Team generates ideas and is not restricted by any releases and distribution schedules (it is [[#Platform_Team|Platform Team]] task). It identifies the major trends for Sugar. The area of responsibility of the Core Team is not only a limited set of Sugar components but any project of Sugar [[#Sugar_universe|universe]]. The team takes part in discussing/improving [[Features]], the consolidated opinion of the team is critically important for [[#Tracked_projects|tracked projects]]. Particular project might agree or disagree (and follow another way or try to dissuade Core Team by their particular implementations), but the Core Team is exactly what Sugar face is for non-sugar community.

=== ~~Standard~~ Team ~~(or merge it with the Core Team)~~ ===

=== Engineering Team ===

The ~~team~~ is ~~intended~~ to ~~provide a set~~ of standards (API, DBus interface, etc) to ~~let~~ [[~~#Sugar_universe|Universe~~]] work ~~with each over in most effective way when all~~ projects might be ~~human/task/purpose sized~~.

The Engineering Team is maintaining several core projects that influence on the rest of Sugar:

* sugar-artwork

* sugar-datastore

* sugar-toolkit (would be good to merge it with sugar-base)

* sugar (Sugar shell, i.e., Sugar Window Manager)

The area of responsibility of the Engineering Team is:

* take care of technical standards (API, DBus interface, etc),

* take part in reviewing patches for one of core projects,

* take part in reviewing [[Features]].

The team consist of developers who:

* know code of core projects (some of them),

* have a time to take part in reviewing process.

So, Engineering Team members might not take active part in coding itself (this is a task for [[Features]] developers) but just do engineering work to support core projects.

The team members list might not be constant, if members don't have enough time to take active part in regular work of the team, they need request for exclusion to not mislead other participants.

=== Platform Team ===

Line 96:

Line 116:

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

~~It is critically important to have human-sized teams of developers who are gathering around particular project instead of the whole Development Team:~~

* It is impossible to make sure that all Development Team participants will be on the same track all time for all core projects. Thus, we are increasing possibility of frustration when some participants takes important decisions but other don't (because they were not be on a track at particular time). Having purpose and human sized teems/projects will let decrease number of interested in developers for one project to let them cooperate much more effective.

* [[#Standard_Team|Standard Team]] lets all these projects cooperate on more clear and obvious basis, since collaboration API is not a task for developers (of particular project) themselves.

=== Sugar universe ===

@@ Line 44: / Line 44: @@
 Core Team generates ideas and is not restricted by any releases and distribution schedules (it is [[#Platform_Team|Platform Team]] task). It identifies the major trends for Sugar. The area of responsibility of the Core Team is not only a limited set of Sugar components but any project of Sugar [[#Sugar_universe|universe]]. The team takes part in discussing/improving [[Features]], the consolidated opinion of the team is critically important for [[#Tracked_projects|tracked projects]]. Particular project might agree or disagree (and follow another way or try to dissuade Core Team by their particular implementations), but the Core Team is exactly what Sugar face is for non-sugar community.
-=== Standard Team (or merge it with the Core Team) ===
+=== Engineering Team ===
-The team is intended to provide a set of standards (API, DBus interface, etc) to let [[#Sugar_universe|Universe]] work with each over in most effective way when all projects might be human/task/purpose sized.
+The Engineering Team is maintaining several core projects that influence on the rest of Sugar:
+* sugar-artwork
+* sugar-datastore
+* sugar-toolkit (would be good to merge it with sugar-base)
+* sugar (Sugar shell, i.e., Sugar Window Manager)
+The area of responsibility of the Engineering Team is:
+* take care of technical standards (API, DBus interface, etc),
+* take part in reviewing patches for one of core projects,
+* take part in reviewing [[Features]].
+The team consist of developers who:
+* know code of core projects (some of them),
+* have a time to take part in reviewing process.
+So, Engineering Team members might not take active part in coding itself (this is a task for [[Features]] developers) but just do engineering work to support core projects.
+The team members list might not be constant, if members don't have enough time to take active part in regular work of the team, they need request for exclusion to not mislead other participants.
 === Platform Team ===
@@ Line 96: / Line 116: @@
 * [[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]].
-It is critically important to have human-sized teams of developers who are gathering around particular project instead of the whole Development Team:
-* It is impossible to make sure that all Development Team participants will be on the same track all time for all core projects. Thus, we are increasing possibility of frustration when some participants takes important decisions but other don't (because they were not be on a track at particular time). Having purpose and human sized teems/projects will let decrease number of interested in developers for one project to let them cooperate much more effective.
-* [[#Standard_Team|Standard Team]] lets all these projects cooperate on more clear and obvious basis, since collaboration API is not a task for developers (of particular project) themselves.
 === Sugar universe ===