Search results
Page title matches
- [[Category:Services/Documentation]]113 bytes (11 words) - 13:44, 25 November 2010
- #REDIRECT [[Documentation Team/Obsolete/Services Activity specific Services HOWTO]]83 bytes (9 words) - 13:44, 25 November 2010
- [[Category:Services/Documentation]]113 bytes (11 words) - 13:39, 25 November 2010
- [[Category:Services/Documentation]] Work flow for services that don't require a compilation stage, thus, they could be just packaged a676 bytes (105 words) - 13:39, 25 November 2010
- [[Category:Services/Documentation]] Work flow for services that require a compilation stage:4 KB (610 words) - 13:41, 25 November 2010
- #REDIRECT [[Documentation Team/Obsolete/Services Binary Services HOWTO]]72 bytes (8 words) - 13:40, 25 November 2010
- #REDIRECT [[Documentation Team/Obsolete/Services Binary-less Services HOWTO]]77 bytes (8 words) - 13:39, 25 November 2010
- #REDIRECT [[Documentation Team/Obsolete/Services Upstream Services HOWTO]]74 bytes (8 words) - 13:37, 25 November 2010
- 48 bytes (6 words) - 20:38, 23 October 2010
- 42 bytes (4 words) - 19:15, 24 February 2010
- #REDIRECT [[Platform Team/Sugar Packaging Management System]]61 bytes (7 words) - 10:50, 26 November 2011
- #REDIRECT [[Documentation Team/Obsolete/Services Wrap native packages HOWTO]]77 bytes (9 words) - 10:56, 26 November 2011
- #REDIRECT [[Platform Team/Guide/Activity development]]54 bytes (6 words) - 13:28, 25 November 2010
- 43 bytes (5 words) - 20:40, 23 October 2010
- #REDIRECT [[Documentation Team/Obsolete/Services Activity Packagers Guide]]75 bytes (8 words) - 13:43, 25 November 2010
- [[Category:Services/Documentation]] ...pose of this Guide is to describe how to package activities that use Sugar Services.2 KB (278 words) - 13:43, 25 November 2010
- #REDIRECT [[Documentation Team/Obsolete/Services Wrap native packages HOWTO]]77 bytes (9 words) - 13:41, 25 November 2010
- #REDIRECT [[Platform Team/Guide/Packaging]]43 bytes (5 words) - 20:39, 23 October 2010
- [[Category:Services/Documentation]] ...Team/Services/Activity Developers Guide|activity]] or [[Documentation Team/Services/Service Developers Guide|service]] ''.info'' file.5 KB (663 words) - 14:13, 3 July 2012
- 70 bytes (9 words) - 20:43, 23 February 2010
Page text matches
- <noinclude>{{TeamHeader|Infrastructure Team|home=Infrastructure Team Home}} ...Team]]. Machines are documented under the [[Machine]] hierarchy. Multiple services can run on the same machine and, in some cases, one service could span acro580 bytes (79 words) - 11:32, 10 January 2011
- #REDIRECT [[Documentation Team/Obsolete/Services Wrap native packages HOWTO]]77 bytes (9 words) - 10:56, 26 November 2011
- <noinclude>[[Category:Team]]</noinclude> ...m of projects. Team members were active in multiple areas. See [[:Category:Team]].3 KB (418 words) - 18:21, 27 November 2019
- [[Category:Activity Team]] ''For regular services:''3 KB (383 words) - 16:45, 25 November 2010
- [[Category:Activity Team]] ''For regular services:''3 KB (383 words) - 16:41, 25 November 2010
- [[Category:Activity Team]] ''For regular services:''3 KB (395 words) - 16:41, 25 November 2010
- | source = Development Team/Manual *[[Design Team | Designers]]2 KB (343 words) - 20:33, 23 February 2010
- [[Category:Activity Team]] ! Branch [http://wiki.sugarlabs.org/go/Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme]2 KB (293 words) - 16:46, 25 November 2010
- [[Category:Activity Team]] ! Branch [http://wiki.sugarlabs.org/go/Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme]2 KB (290 words) - 16:44, 25 November 2010
- [[Category:Activity Team]] This service is a [[Documentation Team/Services/Native packages usage|wrapper]] for native package thus its versions are ve2 KB (270 words) - 06:11, 18 May 2010
- [[Category:Activity Team]] ''For regular services:''3 KB (461 words) - 16:47, 25 November 2010
- [[Category:Activity Team]] ! Branch [http://wiki.sugarlabs.org/go/Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme]2 KB (330 words) - 16:43, 25 November 2010
- ...since the release process is binary—either your feature is included or not—Services offers more flexibility. For example: * some features are of arguable general benefit; Sugar Services would allow interested end users to efficiently test (and even deploy) such2 KB (337 words) - 05:11, 27 April 2012
- [[Category:Activity Team]] ...ess, upgrades dependencies in background and provides [[Documentation_Team/Services/Activity_Triggers|Activity Triggers]] infrastructure.2 KB (345 words) - 06:12, 18 May 2010
- [[Category:Services/Documentation]] ...Team/Services/Activity Developers Guide|activity]] or [[Documentation Team/Services/Service Developers Guide|service]] ''.info'' file.5 KB (663 words) - 14:13, 3 July 2012
- [[Category:Activity Team]] ...f they still work in declared sugar environments. See [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|Versioning guide]].''2 KB (343 words) - 16:45, 25 November 2010
- [[Category:Activity Team]] ...f they still work in declared sugar environments. See [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|Versioning guide]].''2 KB (348 words) - 16:47, 25 November 2010
- <noinclude>{{TeamHeader|Infrastructure Team}}</noinclude> [[Infrastructure Team/Contacts|Contact]] us if you would like to help maintaining existing2 KB (281 words) - 18:47, 30 March 2013
- ...ugar Journal toolbars and palettes in order to expose any installed online services. ...l atm: https://www.itevenworks.net/2013/05/a-backend-for-sugars-future-web-services-infrastructure/)6 KB (891 words) - 14:27, 5 November 2013
- ** infrastructure (servers, services, etc.) in in place ...t FlossManuals folks and others who have previously already contributed to documentation efforts)3 KB (505 words) - 19:10, 24 February 2010