Difference between revisions of "Deployments/Deployment Template"

From Sugar Labs
Jump to navigation Jump to search
(Cleanup)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
<noinclude>{{TOCright}}
 
<noinclude>{{TOCright}}
[[Category:Deployment Page Incomplete]]
 
 
[[Category:Deployment|<Deployment Name>]]
 
[[Category:Deployment|<Deployment Name>]]
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example
 
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). -->
 
 
</noinclude>
 
</noinclude>
  
Line 12: Line 9:
 
<!-- We request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
 
<!-- We request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
  
<!-- The actual name of your deployment page should look something like: Deployments/Your Deployment Name.  This keeps all features in the same namespace -->
+
<!-- The actual name of your deployment page should look something like: Deployments/Your Deployment Name.  This keeps all the deployment pages in the same namespace -->
  
 
== Summary ==
 
== Summary ==
Line 34: Line 31:
  
 
== Hardware ==
 
== Hardware ==
''Describe the number and type of computers Sugar is running on, e.g. 150 OLPC XO-1 Laptops.''
+
''Describe the number and type of computers Sugar is running on, e.g. 150 OLPC XO-1 Laptops.  Also describe any servers used and what software they run.  Additional equipment, like solar power generators, can also be included.''
  
 
== Technical Details ==
 
== Technical Details ==

Latest revision as of 17:30, 19 January 2010


Comments and Explanations:

There are comments (in italic) providing guidance to fill out each section, see also the Deployment Policy Page for a more detailed explanation of the deployment documentation process. Copy the source to a new page named Deployments/Your Deployment Name before making changes! DO NOT EDIT THIS TEMPLATE.


Summary

A sentence or two summarizing this Sugar deployment. This information is used for the deployment summary page.

Contact

This should link to one or more people who are willing to act as ambassadors between Sugar Labs and this deployment.

Include your email address that you can be reached should people want to make contact with this deployment

  • Email: <your email address so we can contact you, invite you to meetings, etc.>

Location

Describe the location of the deployment

Language

What language does the deployment use? Include the language code, e.g. en_US, if possible.

Size

Describe the number of students, teachers, and IT staff using Sugar.

Hardware

Describe the number and type of computers Sugar is running on, e.g. 150 OLPC XO-1 Laptops. Also describe any servers used and what software they run. Additional equipment, like solar power generators, can also be included.

Technical Details

This should list which version of Sugar is being used, e.g. 0.82 or SoaS Blueberry.

  • Sugar version: <SUGAR VERSION>

Describe the base operating system being used, e.g. Fedora 12.

  • OS distribution: <OS DISTRO>

Activity Usage

Describe which Sugar activities are used in the classroom.

  • <ACTIVITY 1>
  • <ACTIVITY 2>

Curriculum

Provide any notes about how Sugar is being used in the classroom.

History

Describe how and when the deployment got started, its growth and changes, etc.

Links

Provide links to deployment websites, additional wiki pages, studies, papers, etc.

Comments and Discussion