Platform Team/Package Management System: Difference between revisions

Line 46:

== 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~~.

This proposal assumes that the core of Sugar development (in common sense) is a wide variety of developers, not just those developers who are taking part in Sugar core (glucose) development. It is all about seeing Sugar activity development from an activity/3rd-party developer's point of view.

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

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

* variety of ~~sugar~~ activities

* 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.

Developers use a set of services that have their own API changes based schedules. Existed glucose packages will be treated as a big service (split to several components, but thats not a task for this proposal). This proposal is about proposing basic infrastructure of Sugar Services and several services that are not part of glucose.

The corner stone of Sugar Services proposal is [[Activity_Team/Services/Saccharin|Saccharin]] service. This service provides installing/upgrading(via 0install) mechanism for all other services. The rest of services is just variety of libraries/applications.

The corner stone of Sugar Services proposal is [[Activity_Team/Services/Saccharin|Saccharin]] service. This service provides installing/upgrading (via 0install) 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, [[Activity_Team/Services/Saccharin|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 [[Activity_Team/Services/Saccharin|Saccharin]](via 0install) will just provide proper version to particular activity.

Technically, Sugar Services could be a part of glucose (or some of its releases) but from activity POV it doesn't make much sense. If an activity requires some service, [[Activity_Team/Services/Saccharin|Saccharin]] will do nothing if requested service/version is already a part of the 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 [[Activity_Team/Services/Saccharin|Saccharin]](via 0install) will just provide proper version to particular activity.

== List of services ==

@@ Line 46: / Line 46: @@
 == 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.
+This proposal assumes that the core of Sugar development (in common sense) is a wide variety of developers, not just those developers who are taking part in Sugar core (glucose) development. It is all about seeing Sugar activity development from an activity/3rd-party developer's point of view.
-From such new core POV, sugar development process will look like:
+From such new core POV, sugar development process will look like: <!-- not sure what you are trying to say here --~~~~ -->
-* variety of sugar activities
+* 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.
+Developers use a set of services that have their own API changes based schedules. Existed glucose packages will be treated as a big service (split to several components, but thats not a task for this proposal). This proposal is about proposing basic infrastructure of Sugar Services and several services that are not part of glucose.
-The corner stone of Sugar Services proposal is [[Activity_Team/Services/Saccharin|Saccharin]] service. This service provides installing/upgrading(via 0install) mechanism for all other services. The rest of services is just variety of libraries/applications.
+The corner stone of Sugar Services proposal is [[Activity_Team/Services/Saccharin|Saccharin]] service. This service provides installing/upgrading (via 0install) 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, [[Activity_Team/Services/Saccharin|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 [[Activity_Team/Services/Saccharin|Saccharin]](via 0install) will just provide proper version to particular activity.
+Technically, Sugar Services could be a part of glucose (or some of its releases) but from activity POV it doesn't make much sense. If an activity requires some service, [[Activity_Team/Services/Saccharin|Saccharin]] will do nothing if requested service/version is already a part of the 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 [[Activity_Team/Services/Saccharin|Saccharin]](via 0install) will just provide proper version to particular activity.
 == List of services ==