Difference between revisions of "Platform Team/Package Management System"

Revision as of 11:55, 15 December 2009

Summary

Provides transparent for users and convenient for activity developers, method to support various activity dependencies.

Work flows

How it looks like for:

Users

In case of pure internet connection(and implemented Zero Install integration feature), user can switch to offline mode and won't encounter any changes in regular workflow. Switching to online mode brings additional progress bar for startup dialog for activities that have pending/not-yet-downloaded/out-dated activity dependencies.

Activity developers

Sugar Services makes sense only for activities that have non Sugar Platform dependencies and support more then one Sucrose release cycles.

For such activities focus is shifting from Sucrose to API of services they are using. More over activity could be stuck to particular service API version(of course if service developers still support this branch) and Sugar Services will support many branches for the same service simultaneously.

To utilize services benefits, activity developer just need to add xml file with all services that activity uses and(if activity targeted to sugars w/o Zero Install integration) startup pure python library to initial launch of Services infrastructure.

Service developers

Detailed Description

This proposal assumes that the core of sugar development(in common sense) is variety of developers rather then developers who are taking part in sugar core(glucose) development. So, it's all about seeing from activity/3rd-party developers.

From such new core POV, sugar development process will look like:

variety of sugar activities
that use Sugar Services

So, developers use a set of services that have theirs own API changes based schedules. Existed glucose could be treated as a big service and splited to several components but thats not a task for this proposal. Instead, it's about proposing basic infrastructure of Sugar Services and several services that are not part of glucose.

The corner stone of Sugar Services proposal is Saccharin service. This service provides installing/upgrading(via Zero Install integration) mechanism for all other services. The rest of services is just variety of libraries/applications.

Technically, service could be a part of glucose(or some of its releases) but from activity POV it doesn't make much sense, if activity requires some service, Saccharin will do nothing if requested service/version is a part of installed glucose or install proper service(via 0install). Various activities on the same system could use various versions of the same service, in that case Saccharin(via 0install) will just provide proper version to particular activity.

Versioning scheme

Each service has API changes based versioning scheme

<major-version>.<minor-version>

the major version starts from 0(premature state) and describes API backwards compatibility breakage
the minor version is for bugfixes and features that don't break backwards compatibility

List of services

@@ Line 21: / Line 21: @@
 For such activities focus is shifting from Sucrose to API of services they are using. More over activity could be stuck to particular service API version(of course if service developers still support this branch) and Sugar Services will support many branches for the same service simultaneously.
-To utilize services benefits, activity developer just need to add xml file with all services that activity uses and(if activity targeted to sugars w/o [[Features/Zero_Install_integration|Zero Install integration]]) startup pure python library to initiate Services infrastructure.
+To utilize services benefits, activity developer just need to add xml file with all services that activity uses and(if activity targeted to sugars w/o [[Features/Zero_Install_integration|Zero Install integration]]) startup pure python library to initial launch of Services infrastructure.
 === Service developers ===