The content of this page is considered
DEPRECATED and OBSOLETE
It is preserved for historical research, along with its talk page.
corresponding project was never created
A privileged service which supervises activity run cycle, exposes startup progress, upgrades dependencies in background and provides Activity Triggers infrastructure.
How many branches are stable, note that some activities could be stuck to particular stable branch, so do not delete your stable branches if they still work in declared sugar environments. See Versioning guide.
| Branch 
|| Sugar range
|| Support status/Notes
|| is comming
Expand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better.
What other services or 0install packages depend on this service? Are there changes outside the developers' control on which completion of this service depends? In other words, does your service depend on completion of another service owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?
Is there upstream documentation on this service, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.
How To Test
Activity Team/Obsolete/Services Supervisor/Testing
Comments and Discussion
Link to source repositoryRepositories on http://git.sugarlabs.org/ in service category are welcome.