Difference between revisions of "Platform Team/Mission"
Jump to navigation
Jump to search
m |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | The general goal is | + | The general goal is to support Sugar communities 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 a Sugar community. |
| − | + | 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 to the [[Education Team]], the Platform Team does not care about non-technical aspects, but rather provides useful technical instruments to help educators and researchers. |
| + | * 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 | + | * 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]]. |
| − | * | + | * 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. |
Latest revision as of 17:05, 8 December 2011
The general goal is to support Sugar communities 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 a Sugar community.
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 to the Education Team, the Platform Team does not care about non-technical aspects, but rather provides useful technical instruments to help educators and researchers.
- 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.