10,505
edits
Changes
Jump to navigation
Jump to search
Line 52:
Line 52: − + − <!-- not sure what you are trying to say here --Walter -->+ − <!-- * see followed "So, .." ~~~~ -->+ − + − − So, developers use a set of services that have their own [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|API changes based]] schedules. Glucose [[Activity Team/Services/Glucose|could be]] [[Documentation Team/Services/Native packages usage|wrapped]] to service(s) as well, glucose as a regular dependency let developers target their activity or services for particular glucose versions and warn users about outdated sugar environment.
Platform Team/Package Management System (view source)
Revision as of 11:18, 26 December 2009
, 11:18, 26 December 2009→Detailed description
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.
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, the Sugar development process will consist of:
* a variety of Sugar activities
* that use a variety of Sugar Services
* variety of Sugar activities
Developers use a set of services that have their own [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|API-changes-based]] schedules. Glucose [[Activity Team/Services/Glucose|could be]] [[Documentation Team/Services/Native packages usage|wrapped]] to service(s) as well; treating Glucose as a normal dependency lets developers target their activity or services for a particular Glucose versions and warn users about outdated Sugar environment.
* that use variety of Sugar Services
The corner stone of Sugar Services proposal is [[Activity_Team/Services/Saccharin|Saccharin]] service. This service provides installing/upgrading (via 0install) mechanism for services. The rest of services is just variety of libraries/applications/native-packages. Saccharin could be a part of glucose (some of its releases) or bundled to .xo otherwise.
The corner stone of Sugar Services proposal is [[Activity_Team/Services/Saccharin|Saccharin]] service. This service provides installing/upgrading (via 0install) mechanism for services. The rest of services is just variety of libraries/applications/native-packages. Saccharin could be a part of glucose (some of its releases) or bundled to .xo otherwise.