5,705
edits
Changes
Jump to navigation
Jump to search
Line 30:
Line 30: − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − # rename Development Team to Platform Team, "development" confuses − # new Platform Team release a sugar product, snapshot of (maybe not all) core(and not core) components − # LTS sugar releases − # sugar-toolkit as a stabilizing instrument within several (non-LTS) core releases − # modularizing sugar core
User:Alsroot/Sugar Architecture (view source)
Revision as of 13:03, 29 October 2010
, 13:03, 29 October 2010→Implementation
* Before arguing with implementation details, check if you are agree with [[#Premises|premisses]].
* 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).
* 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.
* Implementation might take several core releases, it is exactly the path of step-by-step Sugar evolution.
* It is just details of implementation and might lack of important details and be changed in process.
* Please, improve it.
=== Core Team ===
Core Team is a team of architects of Sugar ecosystem.
The team should contain at least one person for each followed category (list sorted from the most important categories to the least):
* Experienced educators. It is fine to have unskilled developers, maybe fine to have unskilled designers, but it is really wrong to have unskilled educators. To throw in ideas and methodology.
* Designers and Human Interface specialists. To think how implementation might look and behave.
* Developers, to limit educators and designers in their dreams.
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. Particular [[#The_Sugar_World|projects]] 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.
=== No Development Team ===
The word ''development'' is quite confusing. Is it about any development within sugar community, how about Activity Team, etc. Glucose projects will flow to the rest of Sugar [[#The_Sugar_World|projects]] and will, by default, [[#Tracked_projects|tracked projects]] of [[#Platform_Team|Platform Team]].
=== Platform Team ===
Platform Team missions:
* 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, happen within sugar [[#The_Sugar_World|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.
==== Sugar Platform distribution ====
* Regular per 6 month releases synced with regular releases of major GNU/Linux distributions
* Long Time Supporting (LTS) releases that coordinated with LTS releases of GNU/Linux distributions (if possible), that should simplify sugar supporting in the field
# new Platform Team release a sugar product, snapshot of (maybe not all) core(and not core) components
# modularizing sugar core
# sugar-toolkit as a stabilizing instrument within several (non-LTS) core releases
==== Tracked projects ====
# the key is priorities
# original Platform Team purposes are natural for new Platform+Development team
# original Platform Team purposes are natural for new Platform+Development team
# new Platform Team is more a ream of coordinators rather than core developers
# new Platform Team is more a ream of coordinators rather than core developers
# core components have its own [self]organized maintaining/developing teams
# core components have its own [self]organized maintaining/developing teams
# ...
# ...