Difference between revisions of "Platform Team"

From Sugar Labs
Jump to navigation Jump to search
 
(18 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
{{:Platform Team/Mission}}
 
{{:Platform Team/Mission}}
  
== Team high-level projects ==
+
== Team projects ==
  
=== Sugar Doers' Kit ===
+
=== Top projects ===
  
* [[Platform Team/Sweets|Sweets]], Zero Install based Package Management System for Sugar.
+
* [[Activity Library]].
* [[Platform Team/Sugar_Lint|sugar-lint]], utility to lint various source files.
+
* [[Sugar Network]].
* [[Platform Team/Sugar_Unit|sugar-unit]], utility to help with unit testing Python based code.
+
* [[Sweets Distribution]].
* [http://git.sugarlabs.org/sdk/gatch gatch], support long or ever standing, all time being on top, downstream patchset for the base branch in a Git repository.
+
* [[Deployment Platform]].
  
=== Services ===
+
=== Upstream services ===
  
* [[Platform Team/Activity Library|Activity Library]] development and integration with Sweets
+
Adapt upstream services for Sugar community needs:
* [[Service/git|Gitorious]] development and integration with Sweets
+
 
 +
* [[Platform Team/Activity Library|Mozilla Addons]].
 +
* [[Service/git|Gitorious]].
 +
* [[Platform_Team/Open_Build_Service|Open Build Service]].
  
 
== Subpages ==
 
== Subpages ==

Latest revision as of 23:18, 10 May 2013

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 projects

Top projects

Upstream services

Adapt upstream services for Sugar community needs:

Subpages