Difference between revisions of "Platform Team"

Revision as of 17:45, 10 November 2011

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.

Team high-level projects

Sugar Doers' Kit

Sweets, Zero Install based Package Management System for Sugar.
sugar-lint, utility to lint various source files.
sugar-unit, utility to help with unit testing Python based code.
gatch, support long or ever standing, all time being on top, downstream patchset for the base branch in a Git repository.

Software distributions

Sugar via Sweets, several Sucrose versions via Sweets.
Sweets Distribution, sweet Sucrose formed as 3rd party repository of native packages for several GNU/Linux distributions.

Services

Activity Library development and integration with Sweets
Gitorious development and integration with Sweets

Subpages

@@ Line 17: / Line 17: @@
 * [[Platform_Team/Guide/Sweets_Usage#Sugar_via_Sweets|Sugar via Sweets]], several Sucrose versions via Sweets.
-* [[Community/Distributions/Sweets_Distribution|Sweets Distribution]], sweet Glucose formed as 3rd party repository of native packages for several GNU/Linux distributions.
+* [[Community/Distributions/Sweets_Distribution|Sweets Distribution]], sweet Sucrose formed as 3rd party repository of native packages for several GNU/Linux distributions.
 === Services ===