Difference between revisions of "Platform Team/Mission"

From Sugar Labs
Jump to navigation Jump to search
m
Line 1: Line 1:
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 general goal is to support Sugar doers in their regular behaviors within the Sugar ecosystem by providing a seamless environment by which to follow a common strategy. In other words, it is exactly about having a platform that supports Sugar doers.
  
The key differences with the existed teams:
+
There are key differences with the existing 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.
+
* Compared to the [[Activity Team]], the Platform Team does not care about developing any particular activities, but rather provides a useful software infrastructure to help people in the activity 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.
+
* Compared with the [[Development Team]], the Platform Team does not care about developing the Sugar learning environment (Sucrose), but rather provides a useful software architecture to help as many people as possible to take part in the Sucrose development process.
* In comparing with the [[Infrastructure Team]], the Platform Team does developing of services that [[Infrastructure Team]] will administrate.
+
* Compared with the [[Infrastructure Team]], the Platform Team does develop some of the services that the [[Infrastructure Team]] administers.
  
In particular:
+
In particular, the Platform Team will
  
* 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).
+
* Support ''doing'' behaviors by providing useful [[Platform_Team/Sweets|distribution method]]s and various Sugar Doers' Kits (that really sounds better than the traditional SDK transcription, Software Developers Kit).
* Connect doers and users by developing services for seamless infrastructure, e.g., [[Activity Library]].
+
* Connect doers and other learners (users) by developing services for a seamless infrastructure for sharing software, 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.
+
* Extend the previous two goals to non-Sugar environments, not to ''sugarize'' them all, but rather to merge and promote Sugar software with and within the common [http://en.wikipedia.org/wiki/Free_software Free Software] and education ecosystems.

Revision as of 11:20, 8 September 2011

The general goal is to support Sugar doers in their regular behaviors within the Sugar ecosystem by providing a seamless environment by which to follow a common strategy. In other words, it is exactly about having a platform that supports Sugar doers.

There are key differences with the existing teams:

  • Compared to the Activity Team, the Platform Team does not care about developing any particular activities, but rather provides a useful software infrastructure to help people in the activity development process.
  • Compared with the Development Team, the Platform Team does not care about developing the Sugar learning environment (Sucrose), but rather provides a useful software architecture to help as many people as possible to take part in the Sucrose development process.
  • Compared with the Infrastructure Team, the Platform Team does develop some of the services that the Infrastructure Team administers.

In particular, the Platform Team will

  • Support doing behaviors by providing useful distribution methods and various Sugar Doers' Kits (that really sounds better than the traditional SDK transcription, Software Developers Kit).
  • Connect doers and other learners (users) by developing services for a seamless infrastructure for sharing software, e.g., Activity Library.
  • Extend the previous two goals to non-Sugar environments, not to sugarize them all, but rather to merge and promote Sugar software with and within the common Free Software and education ecosystems.