5,705
edits
Changes
Jump to navigation
Jump to search
Line 26:
Line 26: − + + + + + + + + + + + + + +
Platform Team/Package Management System (view source)
Revision as of 07:08, 14 December 2009
, 07:08, 14 December 2009→Detailed Description
== Detailed Description ==
== Detailed Description ==
The major idea is to have a solid core (with stable release cycle) <=> dbus-API/sugar-toolkit-API (ideally, only dbus) <=> unlimited number of activities that use core functionality and do not follow 6 months release cycle (which could be overmuch for activity).
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 major idea is instead of having 6 months to have a solid core (with stable release cycle) <=> dbus-API/sugar-toolkit-API (ideally, only dbus) <=> unlimited number of activities that use core functionality and do not follow 6 months release cycle (which could be overmuch for activity).
It could looks like:
It could looks like: