Difference between revisions of "Platform Team/Mission"
Jump to navigation
Jump to search
m |
|||
| Line 4: | Line 4: | ||
* In comparing with the [[Activity Team]], the Platform Team does not care about developing particular activities but rather provides useful infrastructure to help people in activity developing process. | * In comparing with the [[Activity Team]], the Platform Team does not care about developing particular activities but rather provides useful infrastructure to help people in activity developing process. | ||
| − | * In comparing with the [[Development Team]], the Platform Team does not care about developing Sugar Desktop Environment (Sucrose) but rather provides useful infrastructure to help, as many as possible, people take part in Sucrose development process. | + | * In comparing with the [[Development Team]], the Platform Team does not care about developing Sugar Desktop Environment (Sucrose) but rather provides useful infrastructure to help, as many as possible, people to take part in Sucrose development process. |
* In comparing with the [[Infrastructure Team]], the Platform Team does developing of services that [[Infrastructure Team]] will administrate. | * In comparing with the [[Infrastructure Team]], the Platform Team does developing of services that [[Infrastructure Team]] will administrate. | ||
In particular: | In particular: | ||
| − | * Support doing behavior by providing useful [[Platform_Team/Sweets|distribution method]] and various Sugar Doers Kits (that really sounds better | + | * Support doing behavior by providing useful [[Platform_Team/Sweets|distribution method]] and various Sugar Doers Kits (that really sounds better than another SDK transcription, Software Developers Kit). |
* Connect doers and users by developing services for seamless infrastructure, e.g., [[Activity Library]]. | * Connect doers and users by developing services for seamless infrastructure, e.g., [[Activity Library]]. | ||
* Prolong the previous two goals to the non-Sugar environments, not to ''sugarize'' them all but rather to emerge Sugar software to the common [http://en.wikipedia.org/wiki/Free_software Free Software] and educational ecosystem. | * Prolong the previous two goals to the non-Sugar environments, not to ''sugarize'' them all but rather to emerge Sugar software to the common [http://en.wikipedia.org/wiki/Free_software Free Software] and educational ecosystem. | ||
Revision as of 09:39, 8 September 2011
The general goal is supporting Sugar doers in their regular behavior within Sugar ecosystem by following the common strategy to provide seamless environment. In other words, it is exactly about having a platform that Sugar doers can stand on.
The key differences with the existed teams:
- In comparing with the Activity Team, the Platform Team does not care about developing particular activities but rather provides useful infrastructure to help people in activity developing process.
- In comparing with the Development Team, the Platform Team does not care about developing Sugar Desktop Environment (Sucrose) but rather provides useful infrastructure to help, as many as possible, people to take part in Sucrose development process.
- In comparing with the Infrastructure Team, the Platform Team does developing of services that Infrastructure Team will administrate.
In particular:
- Support doing behavior by providing useful distribution method and various Sugar Doers Kits (that really sounds better than another SDK transcription, Software Developers Kit).
- Connect doers and users by developing services for seamless infrastructure, e.g., Activity Library.
- Prolong the previous two goals to the non-Sugar environments, not to sugarize them all but rather to emerge Sugar software to the common Free Software and educational ecosystem.