Talk:Platform Team/Package Management System

Sugar developers

Services are intended to decentralize Sugar development process. If you have some idea in mind, you can start pushing it through the Sucrose release queue to get it in the next (maybe not nearest) release. However, since the release process is binary—either your feature is included or not—Services offers more flexibility. For example:

• some features are of arguable general benefit; Sugar Services would allow interested end users to efficiently test (and even deploy) such features;
• some feature are only stable in limited environments; Sugar Services would allow deployment in limited environmets without the risk of destabilizing the rest of Sugar.

A developer benefits from 0install features by:

• letting users of all deployed Sucrose releases benefit from your new feature instead of having it only in a specific (latest) Sucrose release; for example Activity Triggers services;

Are not these following benefits for activity developers?

• providing libraries or applications that are not intended to be included to Sugar Platform
  • including libraries that are used by only a few activities; or
  • have shorter or longer release/support schedules than Sucrose;
• deploying dependencies that are specific to particular activity; for example, some Python activities include C libraries—by using Services, an activity developer need not bundle all the binaries that Sugar supports; links can be provided links to any binaries that have been build, Services will build additional C libraries from source on user side where they are required.

added to activity developers section alsroot 14:21, 26 December 2009 (UTC)

See Service Developers Guide to learn how to create Sugar Services.