Difference between revisions of "Deployments/Policy"
Jump to navigation
Jump to search
RafaelOrtiz (talk | contribs) m |
(categorize) |
||
| Line 1: | Line 1: | ||
| + | <noinclude>[[Category:Policy]]</noinclude> | ||
== Why should I document my deployment? == | == Why should I document my deployment? == | ||
The main goal of listing deployments on the SugarLabs wiki is to increase communication between the development community and the users. Ultimately, this communication will serve to enhance the Sugar learning platform. | The main goal of listing deployments on the SugarLabs wiki is to increase communication between the development community and the users. Ultimately, this communication will serve to enhance the Sugar learning platform. | ||
Latest revision as of 10:13, 1 November 2011
Why should I document my deployment?
The main goal of listing deployments on the SugarLabs wiki is to increase communication between the development community and the users. Ultimately, this communication will serve to enhance the Sugar learning platform.
By providing a basic description of each deployment and its needs, Sugar developers are motivated to working on making Sugar a great learning experience.
How to document a deployment
To document a deployment, copy the deployment template page into a new Wiki page named Deployments/Your Deployment Name.
Edit the new page, replacing the template comments in italics with the appropriate details.
From time to time, please update the page with new information.
Also you can send a mail to sugar-devel mail list telling us about your process.