Difference between revisions of "Platform Team"

From Sugar Labs
Jump to navigation Jump to search
(Created page with "<noinclude>{{TeamHeader|Platform Team}}{{TOCright}}</noinclude> ==Mission== {{:Platform Team/Mission}} == Subpages == {{Special:PrefixIndex/Platform_Team/}} [[Category:Platf...")
 
Line 1: Line 1:
 
<noinclude>{{TeamHeader|Platform Team}}{{TOCright}}</noinclude>
 
<noinclude>{{TeamHeader|Platform Team}}{{TOCright}}</noinclude>
 +
 +
{{Merge|Packaging Team}}
  
 
==Mission==
 
==Mission==

Revision as of 06:41, 23 October 2010

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings


Mission

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.

Subpages