Sugar Labs - User contributions [en]

Summer of Code/2012

2012-03-02T17:53:36Z

Dogi: /* Project Sharing Website */

Our application page is [http://www.google-melange.com/gsoc/org/application/google/gsoc2012/7284202].

== Project candidates ==

A list of projects potential participants might contribute within GSoC program. Every project is shortly described with mentioning secondary skills for possible participants (the primal skill is desire to do something useful).

'''Note:''' Potential mentors, please feel free to add ideas to this list. Also, feel free to add your name to a project you'd be willing to co-mentor.

'''Note:''' Potential students, more project ideas can be found on our [[Features]] page.

{{TOCright}}

=== Turtle Art Nutrition ===

Working with the maintainer of [[Activities/TurtleArt|Turtle Blocks]] to further develop the prototype [[Activities/TurtleArt#Nutrition|Turtle Nutrition plug-in]] into a stand-alone activity. In its current state, Turtle Nutrition is a plug-in to the Turtle Blocks application. The plug-in aims to raise awareness of nutritional values through visual programming elements.

[[File:Food-plugin.png|300px]]

This project will involve more designing and testing than coding. But a working knowledge of Python is a must. Spanish-language skills is a plus, as we will most likely be testing the tool in one of our Latin American deployments.

''Contact'': [[User:Walter]]

=== Portfolio Videos ===

Working with the maintainer of [[Activities/Portfolio|Portfolio]] to add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation. This is a request that has come from deployments: they'd like to be able to post videos of student work, which is currently available as a slide show with audio voice-over.

[[File:Portfolio-Tool.png|300px]]

A working knowlewdge of Python and some gstreamer skills are a must.

''Contact'': [[User:Walter]]

=== Unified Journal View ===

Rather than viewing the details of a Journal entry on a separate page, the idea is to make the details appear in an expandabe in-line format on the main Journal view. The look and feel would be more like Google+ or Facebook. Performance will be a major challenge.

[[File:Journal-02.jpeg|300px]]

This project requires some working knowledge of the low-level Sugar Journal and datastore code.

''Contact'': [[User:Walter]]

=== Sugar "Sweets" Trisquel GNU/Linux Distro ===

What we need to get Sugar into classrooms and community centers is a software distribution that works "out of the box" with both Sugar and Gnome. The Trisquel GNU/Linux distribution is the most promising of the efforts to make this a reality. I'd like to pilot it in my ICT lab in Arlington, Virginia, and would love to mentor a GSOCer to hack the packages needed to make it work.

''Contact'': [[User:Jelkner]]

=== Background Image on Home View ===

Since we are replacing Hippo, it is relatively trivial to add a background image to the Home View. The image could be set from the Sugar control panel.

Benefit: Deployments could customize backgrounds for l12n purposes. Uses could customize the look of their machines. Background could add some structure to the Home View. The example below, just for fun, was generated in Turtle Art.

[[File:Background-spiral.png|300px]]

Decent Python skills required and some familiarity with GTK.

''Contact'': [[User:Walter]]

=== Multi-touch Sugar ===

With the advent of a number touch-enabled devices capable of running Sugar and with the port to GTK-3, it is time to take seriously the issue of multitouch. How should we be exploiting touch in the interface? How will be circumvent some of the current UI affordances that either reply on the keyboard or hover, e.g., invoking the Sugar Frame?

Strong Python skills and experience with GTK-3 required.

''Contact'': [[User:Walter]]

=== Plugin Support ===

A number of activities, notably [[Activities/TurtleArt#Plugins|Turtle Art]], are supporting plugins -- the ability to extend features by downloading additional modules. However, [[Activities/TurtleArt#How_to_install_a_plugin|the mechanism for installing plugins]] is anything but friendly. It would be nice to design a uniform plugin bundle type and modify the activity installer to recognize this new type. Caveats include dependencies -- presumably the plugin would take care of that -- and version control -- plugins are often incumbent upon a specific version of an activity. [http://activities.sugarlabs.org ASLO hosting]] should also be considered.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== End-user Modifications of Sugar Source ===

We have an existing mechanism for duplicating and modifying Sugar activities: a copy of the bundle can be creaed in ~/Activities, where it can be modified by the end user. We also have a mechanism for viewing the Sugar toolkit source, but no such convenient way for making changes without risking messing up the system. While it should be easy enough to make a duplicate copy in the user's home directory, and to change the Python paths to use the modified code, we need some mechanism -- presumably at boot -- to choose which version to run: the installed version or the modified version.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== Project Sharing Website ===
Create a Project Hosting Site similar to the Scratch website where kids can share the projects they have created using various Sugar Activities. The site should foster collaboration and sharing of projects. The Web Site should be built using a free web framework so that it can be installed at deployment sites. Some features include:

* Ability to engage and connect with friends and classmates using various Social Networking sites/techniques.
* Ability to post projects from various Sugar Activities (ex: Turtle Blocks, Etoys, Memorize, Physics, etc.)
* Separate landing pages for different audiences (kids, teachers, parents, etc)
* Section to share kid created art from projects
* Ability for users to create galleries (of their own projects, favorite projects, subject specific topics, etc).
* Ability to have “private classroom spaces”
* Tools to support community management of the site
* Multi-language support

''Contact'': [[User:MrSteve]]

''Co-mentor'': [[User:dogi]]

=== Sugar as a Service Website ===
Create a Site for managing multiple "Sugar in a Browser" sessions like [https://one.treehouse.su/gar treehouse] or [http://cscott.net/junk/ta-broadway.png broadway gnome]
Some features include:
* Ability of integration of [https://chrome.google.com/webstore/detail/gbchcmhmhahfdphkhkmpfmihenigjmpp Chrome Remote Desktop]
* Ability to share or to allow other user watch this session
* Ability to scale the infrastructure onto local (virtualbox}, private (kvm) and other public clouds (http://fedoraproject.org/wiki/Cloud_SIG, http://xvm.mit.edu/ or http://cloud.ubuntu.com/)

''Contact'': [[User:dogi]]

=== Learn to program -- in Turtle Art ===

In much the same way that [http://www.codecademy.com/courses/programming-intro/0#!/exercises/0] walks newbies through the basics of programming in Javascript, it would be nice to walk newbies through the basics of Turtle Art. There is already a provision within Turtle Art for programatically creating and moving blocks and executing program stacks. So it would be a matter of developing the exercises.

Requires some familiarity with Logo programming and Python.

''Contact'': [[User:Walter]]

''Co-mentor'': [[User:tonyforster]]

=== Implement collaboration in Paint Activity ===

Paint Activity does not implement collaboration yet. The easy part is send the mouse positions and draw in the different machines, but you need have the status of the different tools used, copy/paste operations and undo/redo. Another task to do is port the graphics operations to cairo.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

=== Implement a presentation mode in Fototoon ===

Fototoon allow the user to work with all the boxes in the same screen, but should be good have a view to edit one box using the full screen.
We need implement a way to display the comic created one box after another, maybe adding sound saved for every box.
The presentation can be saved in a pdf, one box by page or exported as a video.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

=== Implement a robotics plugin for Turtle Art ===

Numerous efforts have been made to made a robotics plugin for TA,
but these are not yet completed and rely upon specific platforms,
a new plugin is needed that recognize different platforms like Arduino, Lego nxt. Lego WeDo and Butia. As this work is only for the summer I'll recommend that the plugin only supports Arduino and some Lego robotics family, The main improvement is that the plugin is fully functional, and could be integrated to upstream TA.

''Contact'': [[User:RafaelOrtiz]]

''Co-mentor'': [[User:Hpachas]]

=== Implement help mechanism for activities using Mallard ===

[http://projectmallard.org/ Mallard] is a markup language that makes it easy to provide user help. It would be a nice feature to add Mallard-like help to activities, accessed through a mechanism similar to the view source mechanism. We need to sort through two issues: integration into Sugar and intergration into out i18n system.

''Contact'': [[User:Walter]]

== Proposals Template ==

Put and fill your proposal template at a page like:

'''http://wiki.sugarlabs.org/go/Summer_of_Code/2012/YourProposal'''

====About you====

* '''What is your name?'''
* '''What is your email address?'''
* '''What is your Sugar Labs wiki username?'''
* '''What is your IRC nickname?'''
* '''What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)'''
* '''Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)'''
* '''Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?'''

====About your project====

* '''What is the name of your project?'''
* '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''

* '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 21 - August 13; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 9-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''

* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

====You and the community====
* '''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.'''

* '''What will you do if you get stuck on your project and your mentor isn't around?'''
* '''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''

====Miscellaneous====
* '''We want to make sure that you can set up a [[Development Team#Development_systems|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.'''

* '''What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)'''

* '''Describe a great learning experience you had as a child.'''

* '''Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?'''

Please include the catagory tag at the bottom of your page:
<pre>[[Category:2012 GSoC applications]]</pre>

==Subpages==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Summer of Code/2012

2012-03-02T17:32:42Z

Dogi: /* Project Sharing Website */

Our application page is [http://www.google-melange.com/gsoc/org/application/google/gsoc2012/7284202].

== Project candidates ==

A list of projects potential participants might contribute within GSoC program. Every project is shortly described with mentioning secondary skills for possible participants (the primal skill is desire to do something useful).

'''Note:''' Potential mentors, please feel free to add ideas to this list. Also, feel free to add your name to a project you'd be willing to co-mentor.

'''Note:''' Potential students, more project ideas can be found on our [[Features]] page.

{{TOCright}}

=== Turtle Art Nutrition ===

Working with the maintainer of [[Activities/TurtleArt|Turtle Blocks]] to further develop the prototype [[Activities/TurtleArt#Nutrition|Turtle Nutrition plug-in]] into a stand-alone activity. In its current state, Turtle Nutrition is a plug-in to the Turtle Blocks application. The plug-in aims to raise awareness of nutritional values through visual programming elements.

[[File:Food-plugin.png|300px]]

This project will involve more designing and testing than coding. But a working knowledge of Python is a must. Spanish-language skills is a plus, as we will most likely be testing the tool in one of our Latin American deployments.

''Contact'': [[User:Walter]]

=== Portfolio Videos ===

Working with the maintainer of [[Activities/Portfolio|Portfolio]] to add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation. This is a request that has come from deployments: they'd like to be able to post videos of student work, which is currently available as a slide show with audio voice-over.

[[File:Portfolio-Tool.png|300px]]

A working knowlewdge of Python and some gstreamer skills are a must.

''Contact'': [[User:Walter]]

=== Unified Journal View ===

Rather than viewing the details of a Journal entry on a separate page, the idea is to make the details appear in an expandabe in-line format on the main Journal view. The look and feel would be more like Google+ or Facebook. Performance will be a major challenge.

[[File:Journal-02.jpeg|300px]]

This project requires some working knowledge of the low-level Sugar Journal and datastore code.

''Contact'': [[User:Walter]]

=== Sugar "Sweets" Trisquel GNU/Linux Distro ===

What we need to get Sugar into classrooms and community centers is a software distribution that works "out of the box" with both Sugar and Gnome. The Trisquel GNU/Linux distribution is the most promising of the efforts to make this a reality. I'd like to pilot it in my ICT lab in Arlington, Virginia, and would love to mentor a GSOCer to hack the packages needed to make it work.

''Contact'': [[User:Jelkner]]

=== Background Image on Home View ===

Since we are replacing Hippo, it is relatively trivial to add a background image to the Home View. The image could be set from the Sugar control panel.

Benefit: Deployments could customize backgrounds for l12n purposes. Uses could customize the look of their machines. Background could add some structure to the Home View. The example below, just for fun, was generated in Turtle Art.

[[File:Background-spiral.png|300px]]

Decent Python skills required and some familiarity with GTK.

''Contact'': [[User:Walter]]

=== Multi-touch Sugar ===

With the advent of a number touch-enabled devices capable of running Sugar and with the port to GTK-3, it is time to take seriously the issue of multitouch. How should we be exploiting touch in the interface? How will be circumvent some of the current UI affordances that either reply on the keyboard or hover, e.g., invoking the Sugar Frame?

Strong Python skills and experience with GTK-3 required.

''Contact'': [[User:Walter]]

=== Plugin Support ===

A number of activities, notably [[Activities/TurtleArt#Plugins|Turtle Art]], are supporting plugins -- the ability to extend features by downloading additional modules. However, [[Activities/TurtleArt#How_to_install_a_plugin|the mechanism for installing plugins]] is anything but friendly. It would be nice to design a uniform plugin bundle type and modify the activity installer to recognize this new type. Caveats include dependencies -- presumably the plugin would take care of that -- and version control -- plugins are often incumbent upon a specific version of an activity. [http://activities.sugarlabs.org ASLO hosting]] should also be considered.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== End-user Modifications of Sugar Source ===

We have an existing mechanism for duplicating and modifying Sugar activities: a copy of the bundle can be creaed in ~/Activities, where it can be modified by the end user. We also have a mechanism for viewing the Sugar toolkit source, but no such convenient way for making changes without risking messing up the system. While it should be easy enough to make a duplicate copy in the user's home directory, and to change the Python paths to use the modified code, we need some mechanism -- presumably at boot -- to choose which version to run: the installed version or the modified version.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== Project Sharing Website ===
Create a Project Hosting Site similar to the Scratch website where kids can share the projects they have created using various Sugar Activities. The site should foster collaboration and sharing of projects. The Web Site should be built using a free web framework so that it can be installed at deployment sites. Some features include:

* Ability to engage and connect with friends and classmates using various Social Networking sites/techniques.
* Ability to post projects from various Sugar Activities (ex: Turtle Blocks, Etoys, Memorize, Physics, etc.)
* Separate landing pages for different audiences (kids, teachers, parents, etc)
* Section to share kid created art from projects
* Ability for users to create galleries (of their own projects, favorite projects, subject specific topics, etc).
* Ability to have “private classroom spaces”
* Tools to support community management of the site
* Multi-language support

''Contact'': [[User:MrSteve]] [[User:dogi]]

=== Sugar as a Service Website ===
Create a Site for managing multiple "Sugar in a Browser" sessions like [https://one.treehouse.su/gar treehouse] or [http://cscott.net/junk/ta-broadway.png broadway gnome]
Some features include:
* Ability of integration of [https://chrome.google.com/webstore/detail/gbchcmhmhahfdphkhkmpfmihenigjmpp Chrome Remote Desktop]
* Ability to share or to allow other user watch this session
* Ability to scale the infrastructure onto local (virtualbox}, private (kvm) and other public clouds (http://fedoraproject.org/wiki/Cloud_SIG, http://xvm.mit.edu/ or http://cloud.ubuntu.com/)

''Contact'': [[User:dogi]]

=== Learn to program -- in Turtle Art ===

In much the same way that [http://www.codecademy.com/courses/programming-intro/0#!/exercises/0] walks newbies through the basics of programming in Javascript, it would be nice to walk newbies through the basics of Turtle Art. There is already a provision within Turtle Art for programatically creating and moving blocks and executing program stacks. So it would be a matter of developing the exercises.

Requires some familiarity with Logo programming and Python.

''Contact'': [[User:Walter]]

=== Implement collaboration in Paint Activity ===

Paint Activity does not implement collaboration yet. The easy part is send the mouse positions and draw in the different machines, but you need have the status of the different tools used, copy/paste operations and undo/redo. Another task to do is port the graphics operations to cairo.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

=== Implement a presentation mode in Fototoon ===

Fototoon allow the user to work with all the boxes in the same screen, but should be good have a view to edit one box using the full screen.
We need implement a way to display the comic created one box after another, maybe adding sound saved for every box.
The presentation can be saved in a pdf, one box by page or exported as a video.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

=== Implement a robotics plugin for Turtle Art ===

Numerous efforts have been made to made a robotics plugin for TA,
but these are not yet completed and rely upon specific platforms,
a new plugin is needed that recognize different platforms like Arduino, Lego nxt. Lego WeDo and Butia. As this work is only for the summer I'll recommend that the plugin only supports Arduino and some Lego robotics family, The main improvement is that the plugin is fully functional, and could be integrated to upstream TA.

''Contact'': [[User:RafaelOrtiz]]

''Co-mentor'': [[User:Hpachas]]

=== Implement help mechanism for activities using Mallard ===

[http://projectmallard.org/ Mallard] is a markup language that makes it easy to provide user help. It would be a nice feature to add Mallard-like help to activities, accessed through a mechanism similar to the view source mechanism. We need to sort through two issues: integration into Sugar and intergration into out i18n system.

''Contact'': [[User:Walter]]

== Proposals Template ==

Put and fill your proposal template at a page like:

'''http://wiki.sugarlabs.org/go/Summer_of_Code/2012/YourProposal'''

====About you====

* '''What is your name?'''
* '''What is your email address?'''
* '''What is your Sugar Labs wiki username?'''
* '''What is your IRC nickname?'''
* '''What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)'''
* '''Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)'''
* '''Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?'''

====About your project====

* '''What is the name of your project?'''
* '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''

* '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 21 - August 13; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 9-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''

* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

====You and the community====
* '''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.'''

* '''What will you do if you get stuck on your project and your mentor isn't around?'''
* '''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''

====Miscellaneous====
* '''We want to make sure that you can set up a [[Development Team#Development_systems|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.'''

* '''What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)'''

* '''Describe a great learning experience you had as a child.'''

* '''Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?'''

Please include the catagory tag at the bottom of your page:
<pre>[[Category:2012 GSoC applications]]</pre>

==Subpages==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Summer of Code/2012

2012-03-02T16:38:38Z

Dogi: Reverted edits by Dogi (talk) to last revision by Walter

Our application page is [http://www.google-melange.com/gsoc/org/application/google/gsoc2012/7284202].

== Project candidates ==

A list of projects potential participants might contribute within GSoC program. Every project is shortly described with mentioning secondary skills for possible participants (the primal skill is desire to do something useful).

'''Note:''' Potential mentors, please feel free to add ideas to this list. Also, feel free to add your name to a project you'd be willing to co-mentor.

'''Note:''' Potential students, more project ideas can be found on our [[Features]] page.

{{TOCright}}

=== Turtle Art Nutrition ===

Working with the maintainer of [[Activities/TurtleArt|Turtle Blocks]] to further develop the prototype [[Activities/TurtleArt#Nutrition|Turtle Nutrition plug-in]] into a stand-alone activity. In its current state, Turtle Nutrition is a plug-in to the Turtle Blocks application. The plug-in aims to raise awareness of nutritional values through visual programming elements.

[[File:Food-plugin.png|300px]]

This project will involve more designing and testing than coding. But a working knowledge of Python is a must. Spanish-language skills is a plus, as we will most likely be testing the tool in one of our Latin American deployments.

''Contact'': [[User:Walter]]

=== Portfolio Videos ===

Working with the maintainer of [[Activities/Portfolio|Portfolio]] to add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation. This is a request that has come from deployments: they'd like to be able to post videos of student work, which is currently available as a slide show with audio voice-over.

[[File:Portfolio-Tool.png|300px]]

A working knowlewdge of Python and some gstreamer skills are a must.

''Contact'': [[User:Walter]]

=== Unified Journal View ===

Rather than viewing the details of a Journal entry on a separate page, the idea is to make the details appear in an expandabe in-line format on the main Journal view. The look and feel would be more like Google+ or Facebook. Performance will be a major challenge.

[[File:Journal-02.jpeg|300px]]

This project requires some working knowledge of the low-level Sugar Journal and datastore code.

''Contact'': [[User:Walter]]

=== Sugar "Sweets" Trisquel GNU/Linux Distro ===

What we need to get Sugar into classrooms and community centers is a software distribution that works "out of the box" with both Sugar and Gnome. The Trisquel GNU/Linux distribution is the most promising of the efforts to make this a reality. I'd like to pilot it in my ICT lab in Arlington, Virginia, and would love to mentor a GSOCer to hack the packages needed to make it work.

''Contact'': [[User:Jelkner]]

=== Background Image on Home View ===

Since we are replacing Hippo, it is relatively trivial to add a background image to the Home View. The image could be set from the Sugar control panel.

Benefit: Deployments could customize backgrounds for l12n purposes. Uses could customize the look of their machines. Background could add some structure to the Home View. The example below, just for fun, was generated in Turtle Art.

[[File:Background-spiral.png|300px]]

Decent Python skills required and some familiarity with GTK.

''Contact'': [[User:Walter]]

=== Multi-touch Sugar ===

With the advent of a number touch-enabled devices capable of running Sugar and with the port to GTK-3, it is time to take seriously the issue of multitouch. How should we be exploiting touch in the interface? How will be circumvent some of the current UI affordances that either reply on the keyboard or hover, e.g., invoking the Sugar Frame?

Strong Python skills and experience with GTK-3 required.

''Contact'': [[User:Walter]]

=== Plugin Support ===

A number of activities, notably [[Activities/TurtleArt#Plugins|Turtle Art]], are supporting plugins -- the ability to extend features by downloading additional modules. However, [[Activities/TurtleArt#How_to_install_a_plugin|the mechanism for installing plugins]] is anything but friendly. It would be nice to design a uniform plugin bundle type and modify the activity installer to recognize this new type. Caveats include dependencies -- presumably the plugin would take care of that -- and version control -- plugins are often incumbent upon a specific version of an activity. [http://activities.sugarlabs.org ASLO hosting]] should also be considered.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== End-user Modifications of Sugar Source ===

We have an existing mechanism for duplicating and modifying Sugar activities: a copy of the bundle can be creaed in ~/Activities, where it can be modified by the end user. We also have a mechanism for viewing the Sugar toolkit source, but no such convenient way for making changes without risking messing up the system. While it should be easy enough to make a duplicate copy in the user's home directory, and to change the Python paths to use the modified code, we need some mechanism -- presumably at boot -- to choose which version to run: the installed version or the modified version.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== Project Sharing Website ===
Create a Project Hosting Site similar to the Scratch website where kids can share the projects they have created using various Sugar Activities. The site should foster collaboration and sharing of projects. The Web Site should be built using a free web framework so that it can be installed at deployment sites. Some features include:

* Ability to engage and connect with friends and classmates using various Social Networking sites/techniques.
* Ability to post projects from various Sugar Activities (ex: Turtle Blocks, Etoys, Memorize, Physics, etc.)
* Separate landing pages for different audiences (kids, teachers, parents, etc)
* Section to share kid created art from projects
* Ability for users to create galleries (of their own projects, favorite projects, subject specific topics, etc).
* Ability to have “private classroom spaces”
* Tools to support community management of the site
* Multi-language support

''Contact'': [[User:MrSteve]]

=== Learn to program -- in Turtle Art ===

In much the same way that [http://www.codecademy.com/courses/programming-intro/0#!/exercises/0] walks newbies through the basics of programming in Javascript, it would be nice to walk newbies through the basics of Turtle Art. There is already a provision within Turtle Art for programatically creating and moving blocks and executing program stacks. So it would be a matter of developing the exercises.

Requires some familiarity with Logo programming and Python.

''Contact'': [[User:Walter]]

=== Implement collaboration in Paint Activity ===

Paint Activity does not implement collaboration yet. The easy part is send the mouse positions and draw in the different machines, but you need have the status of the different tools used, copy/paste operations and undo/redo. Another task to do is port the graphics operations to cairo.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

=== Implement a presentation mode in Fototoon ===

Fototoon allow the user to work with all the boxes in the same screen, but should be good have a view to edit one box using the full screen.
We need implement a way to display the comic created one box after another, maybe adding sound saved for every box.
The presentation can be saved in a pdf, one box by page or exported as a video.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

=== Implement a robotics plugin for Turtle Art ===

Numerous efforts have been made to made a robotics plugin for TA,
but these are not yet completed and rely upon specific platforms,
a new plugin is needed that recognize different platforms like Arduino, Lego nxt. Lego WeDo and Butia. As this work is only for the summer I'll recommend that the plugin only supports Arduino and some Lego robotics family, The main improvement is that the plugin is fully functional, and could be integrated to upstream TA.

''Contact'': [[User:RafaelOrtiz]]

''Co-mentor'': [[User:Hpachas]]

=== Implement help mechanism for activities using Mallard ===

[http://projectmallard.org/ Mallard] is a markup language that makes it easy to provide user help. It would be a nice feature to add Mallard-like help to activities, accessed through a mechanism similar to the view source mechanism. We need to sort through two issues: integration into Sugar and intergration into out i18n system.

''Contact'': [[User:Walter]]

== Proposals Template ==

Put and fill your proposal template at a page like:

'''http://wiki.sugarlabs.org/go/Summer_of_Code/2012/YourProposal'''

====About you====

* '''What is your name?'''
* '''What is your email address?'''
* '''What is your Sugar Labs wiki username?'''
* '''What is your IRC nickname?'''
* '''What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)'''
* '''Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)'''
* '''Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?'''

====About your project====

* '''What is the name of your project?'''
* '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''

* '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 21 - August 13; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 9-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''

* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

====You and the community====
* '''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.'''

* '''What will you do if you get stuck on your project and your mentor isn't around?'''
* '''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''

====Miscellaneous====
* '''We want to make sure that you can set up a [[Development Team#Development_systems|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.'''

* '''What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)'''

* '''Describe a great learning experience you had as a child.'''

* '''Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?'''

Please include the catagory tag at the bottom of your page:
<pre>[[Category:2012 GSoC applications]]</pre>

==Subpages==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

User:Dogi

2012-03-02T15:49:21Z

Dogi:

[http://wiki.laptop.org/go/User:Dogi my page on laptop.org]

{{Special:WhatLinksHere/User:Dogi}}

[http://one.treehouse.su try sugarbush]

Summer of Code/2012

2012-03-02T15:47:22Z

Dogi: /* Project Sharing Website */

Our application page is [http://www.google-melange.com/gsoc/org/application/google/gsoc2012/7284202].

== Project candidates ==

A list of projects potential participants might contribute within GSoC program. Every project is shortly described with mentioning secondary skills for possible participants (the primal skill is desire to do something useful).

'''Note:''' Potential mentors, please feel free to add ideas to this list. Also, feel free to add your name to a project you'd be willing to co-mentor.

'''Note:''' Potential students, more project ideas can be found on our [[Features]] page.

{{TOCright}}

=== Turtle Art Nutrition ===

Working with the maintainer of [[Activities/TurtleArt|Turtle Blocks]] to further develop the prototype [[Activities/TurtleArt#Nutrition|Turtle Nutrition plug-in]] into a stand-alone activity. In its current state, Turtle Nutrition is a plug-in to the Turtle Blocks application. The plug-in aims to raise awareness of nutritional values through visual programming elements.

[[File:Food-plugin.png|300px]]

This project will involve more designing and testing than coding. But a working knowledge of Python is a must. Spanish-language skills is a plus, as we will most likely be testing the tool in one of our Latin American deployments.

''Contact'': [[User:Walter]]

=== Portfolio Videos ===

Working with the maintainer of [[Activities/Portfolio|Portfolio]] to add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation. This is a request that has come from deployments: they'd like to be able to post videos of student work, which is currently available as a slide show with audio voice-over.

[[File:Portfolio-Tool.png|300px]]

A working knowlewdge of Python and some gstreamer skills are a must.

''Contact'': [[User:Walter]]

=== Unified Journal View ===

Rather than viewing the details of a Journal entry on a separate page, the idea is to make the details appear in an expandabe in-line format on the main Journal view. The look and feel would be more like Google+ or Facebook. Performance will be a major challenge.

[[File:Journal-02.jpeg|300px]]

This project requires some working knowledge of the low-level Sugar Journal and datastore code.

''Contact'': [[User:Walter]]

=== Sugar "Sweets" Trisquel GNU/Linux Distro ===

What we need to get Sugar into classrooms and community centers is a software distribution that works "out of the box" with both Sugar and Gnome. The Trisquel GNU/Linux distribution is the most promising of the efforts to make this a reality. I'd like to pilot it in my ICT lab in Arlington, Virginia, and would love to mentor a GSOCer to hack the packages needed to make it work.

''Contact'': [[User:Jelkner]]

=== Background Image on Home View ===

Since we are replacing Hippo, it is relatively trivial to add a background image to the Home View. The image could be set from the Sugar control panel.

Benefit: Deployments could customize backgrounds for l12n purposes. Uses could customize the look of their machines. Background could add some structure to the Home View. The example below, just for fun, was generated in Turtle Art.

[[File:Background-spiral.png|300px]]

Decent Python skills required and some familiarity with GTK.

''Contact'': [[User:Walter]]

=== Multi-touch Sugar ===

With the advent of a number touch-enabled devices capable of running Sugar and with the port to GTK-3, it is time to take seriously the issue of multitouch. How should we be exploiting touch in the interface? How will be circumvent some of the current UI affordances that either reply on the keyboard or hover, e.g., invoking the Sugar Frame?

Strong Python skills and experience with GTK-3 required.

''Contact'': [[User:Walter]]

=== Plugin Support ===

A number of activities, notably [[Activities/TurtleArt#Plugins|Turtle Art]], are supporting plugins -- the ability to extend features by downloading additional modules. However, [[Activities/TurtleArt#How_to_install_a_plugin|the mechanism for installing plugins]] is anything but friendly. It would be nice to design a uniform plugin bundle type and modify the activity installer to recognize this new type. Caveats include dependencies -- presumably the plugin would take care of that -- and version control -- plugins are often incumbent upon a specific version of an activity. [http://activities.sugarlabs.org ASLO hosting]] should also be considered.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== End-user Modifications of Sugar Source ===

We have an existing mechanism for duplicating and modifying Sugar activities: a copy of the bundle can be creaed in ~/Activities, where it can be modified by the end user. We also have a mechanism for viewing the Sugar toolkit source, but no such convenient way for making changes without risking messing up the system. While it should be easy enough to make a duplicate copy in the user's home directory, and to change the Python paths to use the modified code, we need some mechanism -- presumably at boot -- to choose which version to run: the installed version or the modified version.

Strong Python skills and experience with Sugar toolkit required.

''Contact'': [[User:Walter]]

=== Project Sharing Website ===
Create a Project Hosting Site similar to the Scratch website where kids can share the projects they have created using various Sugar Activities. The site should foster collaboration and sharing of projects. The Web Site should be built using a free web framework so that it can be installed at deployment sites. Some features include:

* Ability to engage and connect with friends and classmates using various Social Networking sites/techniques.
* Ability to post projects from various Sugar Activities (ex: Turtle Blocks, Etoys, Memorize, Physics, etc.)
* Separate landing pages for different audiences (kids, teachers, parents, etc)
* Section to share kid created art from projects
* Ability for users to create galleries (of their own projects, favorite projects, subject specific topics, etc).
* Ability to have “private classroom spaces”
* Tools to support community management of the site
* Multi-language support

''Contact'': [[User:dogi]]

=== Learn to program -- in Turtle Art ===

In much the same way that [http://www.codecademy.com/courses/programming-intro/0#!/exercises/0] walks newbies through the basics of programming in Javascript, it would be nice to walk newbies through the basics of Turtle Art. There is already a provision within Turtle Art for programatically creating and moving blocks and executing program stacks. So it would be a matter of developing the exercises.

Requires some familiarity with Logo programming and Python.

''Contact'': [[User:Walter]]

=== Implement collaboration in Paint Activity ===

Paint Activity does not implement collaboration yet. The easy part is send the mouse positions and draw in the different machines, but you need have the status of the different tools used, copy/paste operations and undo/redo. Another task to do is port the graphics operations to cairo.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

=== Implement a presentation mode in Fototoon ===

Fototoon allow the user to work with all the boxes in the same screen, but should be good have a view to edit one box using the full screen.
We need implement a way to display the comic created one box after another, maybe adding sound saved for every box.
The presentation can be saved in a pdf, one box by page or exported as a video.

Requires familiarity with Python.

''Contact'': [[User:Godiard]]

=== Implement a robotics plugin for Turtle Art ===

Numerous efforts have been made to made a robotics plugin for TA,
but these are not yet completed and rely upon specific platforms,
a new plugin is needed that recognize different platforms like Arduino, Lego nxt. Lego WeDo and Butia. As this work is only for the summer I'll recommend that the plugin only supports Arduino and some Lego robotics family, The main improvement is that the plugin is fully functional, and could be integrated to upstream TA.

''Contact'': [[User:RafaelOrtiz]]

''Co-mentor'': [[User:Hpachas]]

=== Implement help mechanism for activities using Mallard ===

[http://projectmallard.org/ Mallard] is a markup language that makes it easy to provide user help. It would be a nice feature to add Mallard-like help to activities, accessed through a mechanism similar to the view source mechanism. We need to sort through two issues: integration into Sugar and intergration into out i18n system.

''Contact'': [[User:Walter]]

== Proposals Template ==

Put and fill your proposal template at a page like:

'''http://wiki.sugarlabs.org/go/Summer_of_Code/2012/YourProposal'''

====About you====

* '''What is your name?'''
* '''What is your email address?'''
* '''What is your Sugar Labs wiki username?'''
* '''What is your IRC nickname?'''
* '''What is your primary language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)'''
* '''Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)'''
* '''Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?'''

====About your project====

* '''What is the name of your project?'''
* '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''

* '''What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 21 - August 13; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 9-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''

* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

====You and the community====
* '''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.'''

* '''What will you do if you get stuck on your project and your mentor isn't around?'''
* '''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''

====Miscellaneous====
* '''We want to make sure that you can set up a [[Development Team#Development_systems|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.'''

* '''What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)'''

* '''Describe a great learning experience you had as a child.'''

* '''Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?'''

Please include the catagory tag at the bottom of your page:
<pre>[[Category:2012 GSoC applications]]</pre>

==Subpages==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Machine/anno

2012-02-03T16:01:29Z

Dogi: Created page with "couchdb 5243 0.0 0.0 4148 668 ? S 2011 0:00 /bin/sh -e /usr/bin/couchdb -a /etc/couchdb/default.ini -a /etc/couchdb/local.ini -b -r 5 -p /var/run/couchdb/cou..."

couchdb 5243 0.0 0.0 4148 668 ? S 2011 0:00 /bin/sh -e /usr/bin/couchdb -a /etc/couchdb/default.ini -a /etc/couchdb/local.ini -b -r 5 -p /var/run/couchdb/couchdb.pid -o /dev/null -e /dev/null -R
couchdb 5269 0.0 0.0 4148 348 ? S 2011 0:00 \_ /bin/sh -e /usr/bin/couchdb -a /etc/couchdb/default.ini -a /etc/couchdb/local.ini -b -r 5 -p /var/run/couchdb/couchdb.pid -o /dev/null -e /dev/null -R
couchdb 5270 6.1 2.5 94980 26012 ? Sl 2011 28973:14 \_ /usr/lib/erlang/erts-5.7.4/bin/beam -Bd -K true -A 4 -- -root /usr/lib/erlang -progname erl -- -home /var/lib/couchdb -- -noshell -noinput -sasl errlog_type error -couch_ini /etc/couchdb/default.ini /etc/couchdb/local.ini /etc/couchdb/default.ini /etc/couchdb/local.ini -s couch -pidfile /var/run/couchdb/couchdb.pid -heart
couchdb 5278 0.0 0.0 3912 312 ? Ss 2011 12:49 \_ heart -pid 5270 -ht 11
couchdb 16922 0.0 0.3 83524 3120 ? Ssl 2011 0:00 \_ /usr/lib/couchdb/bin/couchjs /usr/share/couchdb/server/main.js
couchdb 10731 0.0 0.3 83524 3160 ? Ssl 2011 0:02 \_ /usr/lib/couchdb/bin/couchjs /usr/share/couchdb/server/main.js
couchdb 15934 0.0 0.0 4148 668 ? S 2011 0:00 /bin/sh -e /usr/bin/couchdb -a /etc/couchdb/default.ini -a /etc/couchdb/local.ini -b -r 5 -p /var/run/couchdb/couchdb.pid -o /dev/null -e /dev/null -R
couchdb 15964 0.0 0.0 4148 344 ? S 2011 0:00 \_ /bin/sh -e /usr/bin/couchdb -a /etc/couchdb/default.ini -a /etc/couchdb/local.ini -b -r 5 -p /var/run/couchdb/couchdb.pid -o /dev/null -e /dev/null -R
couchdb 15965 0.0 1.0 45788 11044 ? Sl 2011 30:00 \_ /usr/lib/erlang/erts-5.7.4/bin/beam -Bd -K true -A 4 -- -root /usr/lib/erlang -progname erl -- -home /var/lib/couchdb -- -noshell -noinput -sasl errlog_type error -couch_ini /etc/couchdb/default.ini /etc/couchdb/local.ini /etc/couchdb/default.ini /etc/couchdb/local.ini -s couch -pidfile /var/run/couchdb/couchdb.pid -heart
couchdb 15973 0.0 0.0 3912 312 ? Ss 2011 6:18 \_ heart -pid 15965 -ht 11
root 25233 0.0 1.3 231172 13292 ? Ss 2011 16:52 /usr/sbin/apache2 -k start
www-data 18158 0.0 0.6 231172 6920 ? S Jan29 0:00 \_ /usr/sbin/apache2 -k start
www-data 18159 0.0 0.6 231496 7152 ? S Jan29 0:00 \_ /usr/sbin/apache2 -k start
www-data 18161 0.0 0.7 231496 7164 ? S Jan29 0:00 \_ /usr/sbin/apache2 -k start
www-data 18162 0.0 0.6 231172 6920 ? S Jan29 0:00 \_ /usr/sbin/apache2 -k start
www-data 18164 0.0 0.7 231632 7344 ? S Jan29 0:00 \_ /usr/sbin/apache2 -k start
www-data 28070 0.0 0.6 231172 6424 ? S Feb02 0:00 \_ /usr/sbin/apache2 -k start

Machine/booki

2012-02-03T07:48:01Z

Dogi: /* Location */

{{TOCright}}

== Description ==

This VM is build as a Webservice to create and store "textbooks".
Technially this service is build on top of django and the [[http://download.booki.cc/ booki]] - plugins/extensions.

== OS ==

[[Machine/template-maverick|Ubuntu 10.10]]

== Services ==

* [[Service/zzz_template|TEMPLATE_SERVICE]]

== Hardware ==

* KVM Virtual Machine

== Location ==

[[Machine/housetree|housetree]]

== Admins ==

* [[User:Mokurai|Mokurai]]
* [[User:dogi|Stefan Unterhauser]]

== ToDo ==
* use apache for http delivery ... right now this service is provided by the django /python command "django-admin runserver 0.0.0.0:80" which has to be excuted in a screen session ...

== known problems ==
from time to time django has to be restarted ... grrrrr.
ssh mokurai@book.treehouse.su
sudo -s
screen -R
[CTRL-C] #to terminate the blocked/slow/running django
django-admin runserver 0.0.0.0:80 #start again
[CTRL-A followed by D] # detach screen session without terminating ...

== variables which have to be set ==
declare -x PYTHONPATH=":/var/www/:/var/www/booki/lib/:/srv/booki/lib:/var/www/:/var/www/booki/lib/:/srv/booki/lib:/srv/booki/lib/booki:/var/www/:/var/www/mybooki/lib/:/srv/booki/lib:/var/www/:/var/www/mybooki/lib/:/srv/booki/lib"
root@booki:/var/www/mybooki# export|grep SETTINGS
declare -x DJANGO_SETTINGS_MODULE="mybooki.settings"

Machine/schooltool

2012-01-31T19:56:12Z

Dogi: moved Machine/treehouse/schooltool to Machine/schooltool

== Info ==

This is the server for the [http://www.schooltool.org/ SchoolTool] pilot in El Salvador.

Currently, two schools are participating in the pilot:

* [http://esaes.edicypages.com/ Escuela Santaneca de Enseñanza Especializada]

* [http://cecec.iespana.es/ Centro Escolar Cantón El Calvario]

== Demo ==

A demo of SchoolTool is available at: [http://schooltool.sugarlabs.org:7080/schoolyears/2010-2011 schooltool in sugarlabs colors]

''Sample data creates a school of 1000 students, 50 teachers and two years of section enrollments. Users are either “student” or “teacher” followed by a three digit number, for example, “'''student001'''” or “'''teacher001'''“.''

For example, you can log in using the username "'''teacher001'''" and password "'''teacher001'''" or using the username "'''student021'''" and password "'''student021'''", and so on.

You can also log in with administrative privileges using the username "'''manager'''" and password "'''schooltool'''"

== Hostnames ==

* [http://schooltool.sugarlabs.org/ schooltool.sugarlabs.org]

== Hosted on ==

[[Machine/treehouse]]

== Administrative contact ==

dogi AT sugarlabs DOT org

douglascerna AT yahoo DOT com

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:dogi|Stefan Unterhauser]]

== Notes ==

Running on:

* Ubuntu Lucid 10.04.1

* [https://code.launchpad.net/~replaceafill/schooltool/schooltool.sugarlabs Custom version of latest SchoolTool egg]

* Python 2.6.5

== Upgrade notes ==

There's a script to manage the service:

* /etc/init.d/schooltool-sugarlabs {start|stop|restart|status}

The custom branch and instance is located at:

* /home/replaceafill/opt/instances/schooltool.sugarlabs

Updates for this branch can be pulled from Launchpad:

* bzr pull

== See Also ==

* [http://book.schooltool.org/ SchoolTool Book]

* [https://launchpad.net/~schooltoolers SchoolTool Users mailing list]

* [https://launchpad.net/~schooltool-developers SchoolTool Developers mailing list]

* [https://launchpad.net/~schooltool-owners/+archive/ppa SchoolTool PPA]

* [http://ftp.schooltool.org/schooltool/trunk/ Latest SchoolTool eggs]

[[Category:Service|schooltool]]

Machine/booki

2012-01-31T19:49:33Z

Dogi: moved Machine/treehouse/booki to Machine/booki

{{TOCright}}

== Description ==

This VM is build as a Webservice to create and store "textbooks".
Technially this service is build on top of django and the [[http://download.booki.cc/ booki]] - plugins/extensions.

== OS ==

[[Machine/template-maverick|Ubuntu 10.10]]

== Services ==

* [[Service/zzz_template|TEMPLATE_SERVICE]]

== Hardware ==

* KVM Virtual Machine

== Location ==

[[Machine/treehouse|treehouse]]

== Admins ==

* [[User:Mokurai|Mokurai]]
* [[User:dogi|Stefan Unterhauser]]

== ToDo ==
* use apache for http delivery ... right now this service is provided by the django /python command "django-admin runserver 0.0.0.0:80" which has to be excuted in a screen session ...

== known problems ==
from time to time django has to be restarted ... grrrrr.
ssh mokurai@book.treehouse.su
sudo -s
screen -R
[CTRL-C] #to terminate the blocked/slow/running django
django-admin runserver 0.0.0.0:80 #start again
[CTRL-A followed by D] # detach screen session without terminating ...

Machine/identity

2012-01-31T19:36:43Z

Dogi: moved Machine/treehouse/identity to Machine/identity

== Description ==

<code>identity</code> is a 64bit VM running Debian Squeeze for the client certificate based OpenID provider.

== Installation ==

=== Base system ===

sudo virsh vol-create-as treehouse identity-root 8G
sudo virt-install --ram=512 --name=identity --arch=x86_64 --vcpus=1 --hvm \
--accelerate --disk vol=treehouse/identity-root --network=network:default \
--nographics --extra-args='console=tty0 console=ttyS0,115200n8 expert' \
--location=http://ftp.us.debian.org/debian/dists/squeeze/main/installer-amd64/

This will create a new VM and run the Debian installer inside it, with an emulated serial console attached to stdio.

Config options:
* english, US, US keyboard
* identity, sugarlabs.org
* use entire disk, all in one, remove swap, recreate / (full size), noatime + user_xattr
* user "administrator" (not used) with root password (manually removed later)
* package sets: "Standard system", "SSH server"

After reboot:
* Log in as root with password (still via emulated serial console)
* <code>passwd -d root</code>
* <code>aptitude install etckeeper monkeysphere</code>
* Set up monkeysphere as usual (host key, user authentication, keyserver)
* Set up second network interface with static IPv4 address, IPv6 tunnel
* Shutdown and (re)start VM (needed for libvirtd to create the network interface - <code>attach-interface</code> didn't do it)

Machine/zatoichi

2012-01-31T19:35:56Z

Dogi: moved Machine/treehouse/zatoichi to Machine/zatoichi

<noinclude>{{TOCright}}</noinclude>

== Hostnames ==

* [http://zatoichi.sugarlabs.org/ zatoichi.sugarlabs.org]
* [http://encuestas.paraguayeduca.org/ encuestas.paraguayeduca.org]
* [http://presentaciones.paraguayeduca.org/ presentaciones.paraguayeduca.org]
* [http://zatoichi.paraguayeduca.org/ zatoichi.paraguayeduca.org]

== Hardware ==

* KVM on [[Machine/treehouse|treehouse]]

== Location ==
Hosted by the [http://www.fsf.org/ Free Software Foundation] at the [http://www.gnaps.com/ Global NAPs] collocation facility.

== Admins ==
* [[User:Rgs|Raul Gutierrez S.]], rgs_ on #sugar Freenode
* Car|0s|Carlos Garay, Car|0s on #sugar Freenode

== Notes ==

=== Passenger and Rails apps ===

Passenger has been installed to host Rails apps (mainly our inventory system). Its the first time I've installed Passenger via a package manager so I am not sure if it'll "just work". I need help from Bernie to package our inventory system (for Ubuntu) and give it a try.

=== Limesurvey (encuestas.paraguayeduca.org) ===

This PHP webapp uses a MySQL db as backend. Nothing special about its config.

Machine/dextrose

2012-01-31T19:34:36Z

Dogi: moved Machine/treehouse/dextrose to Machine/dextrose

{{TOCright}}

== Description ==

Short descrition of machine purpose

== OS ==

Distro and version.

== Services ==

* [[Service/zzz_template|TEMPLATE_SERVICE]]

== Hardware ==

* KVM Virtual Machine

== Location ==

[[Machine/HOST|HOST]]

== Admins ==

* [[User:bernie|Bernie Innocenti]]

== Backup ==

* Daily system-full-backup on [[Machine/backup]]. Ask admins for encryption password.

== Notes ==

Dextrose/Building

2012-01-31T19:34:10Z

Dogi:

<noinclude>{{TeamHeader|Dextrose|home=Dextrose|xbgColor=ffe792|join_label=Get Involved}}</noinclude>

== Dextrose build system ==

Dextrose uses [http://wiki.laptop.org/go/OS_Builder olpc-os-builder], a tool create by OLPC to build official and customized system images. The Dextrose git repository contains, olpc-os-builder, local customizations specific to Dextrose, and fixes and enhancements waiting to be pushed upstream.

== Build host requirements ==

The Dextrose build system is known to work on '''Fedora 14 x86_64''' and '''Fedora 16 x86_64'''. The OS on the host system ''shouldn't'' matter because the build runs in a chroot environment. olpc-os-builder does not yet run on Ubuntu due to a missing dependency (bitfrost).

The initial build requires about '''700MB''' of rpm packages and Sugar activity bundles. The packages and bundles are cached for futures builds.

== Initial setup ==

* If sudo isn't configured to work with your account, add yourself to the '''wheel''' group. Alternatively, you can become root with <code>su -</code>.

* Install build dependencies (you need to be root to do this)

yum upgrade
yum install libtomcrypt-devel bitfrost crcimg make gcc mtd-utils python-imgcreate zip unzip zlib-devel lzma

* Install the olpc-bootanim-tools package:

rpm -i http://download.sugarlabs.org/dextrose/testing/dx3/rpms/x86_64/os/olpc-bootanim-tools-2.14-1.bernie1.fc16.x86_64.rpm

If you have a 32bit machine:

rpm -i http://download.sugarlabs.org/dextrose/testing/dx3/rpms/i386/os/olpc-bootanim-tools-2.14-1.bernie1.fc16.i686.rpm

Alternatively, you could rebuild the olpc-bootanim package from source:

yum install rpm-build netpbm-progs
wget http://download.sugarlabs.org/dextrose/testing/dx3/rpms/source/olpc-bootanim-2.14-1.bernie1.fc16.src.rpm
rpmbuild --rebuild olpc-bootanim-2.14-1.bernie1.fc16.src.rpm
rpm -U ~/rpmbuild/RPMS/*/olpc-bootanim-tools-*.rpm

* Checkout the Dextrose build system

git clone git://git.sugarlabs.org/dextrose/mainline.git dextrose

* Compile build helper programs

cd dextrose
make

* Generate initial sequence number for the builds (42 is just an example)

echo 42 >buildnr-dx

== Creating a build ==

* Become root and run the build system:

time sudo ./osbuilder.py config/dextrose3-xo1-nognome.ini

The initial build may take several hours, depending on available bandwidth.
Subsequent builds will take about 15-20 minutes on average desktop machines.

Upon completion, the new image will be available in <tt>build/output</tt>.
Now copy it on a USB stick and test it on your target.

== Debugging ==

Because several build tools (olpc-os-builder, imgcreate and yum) run chrooted
and nested into each other, error output is often obscure or misleading.
Before digging into the code, try asking on IRC in case someone has already seen
the same problem.

== Publishing the images ==

Please do not publish signed builds unless they implement the [http://wiki.laptop.org/go/Antitheft_HowTo OLPC anti-theft system].

== Customizing your build ==

olpc-os-builder is documented at
[http://git.sugarlabs.org/projects/dextrose/repos/mainline/trees/master/doc/README README]
in the olpc-os-builder tree. The modules are documented in <tt>README</tt> files in the
[http://git.sugarlabs.org/projects/dextrose/repos/mainline/trees/master/modules modules] directory.

=== Upstream Code ===

Dextrose is based on [http://dev.laptop.org/git/projects/olpc-os-builder/ olpc-os-builder] by Daniel Drake. You can fetch the latest source code into your Dextrose repository:

git remote add olpc git://dev.laptop.org/projects/olpc-os-builder
git fetch olpc
git log olpc/master

=== Customizing the core RPMs ===

* Go to the <tt>rpms/PACKAGENAME</tt> in the dextrose tree

* Edit the spec file. Typically this involves adding a new patch, which is done by adding a <tt>PatchNN:</tt> tag and a corresponding <tt>%patchNN</tt> rule in <tt>%setup</tt>. Some of the intricacies of RPM spec files are unveiled in the [http://fedoraproject.org/wiki/Packaging/Guidelines Fedora Packaging Guidelines].

* Increase the release number after each change.

=== building the Custom RPM ===

If you have a Fedora 11 i386 system, just type:

make i586

Otherwise, you need to build in a [http://fedoraproject.org/wiki/Projects/Mock mock] chroot:

make srpm
sudo mock -r fedora-11-i386 --resultdir=. --rebuild mypackage.src.rpm

=== Uploading the Custom RPM ===

* Upload rpm to a yum repository and add it to the ini file used by the OLPC OS builder.

* To automate this step, we have a rule <tt>make uploadrpm</tt> which points at the Dextrose repository. Edit <tt>rpms/common/Makefile.common</tt> or <tt>rpms/common/uploadrpm</tt> to retarget this rule to your repository.

=== Building custom kernels ===

$ git clone http://dev.laptop.org/git/olpc-2.6/
$ cd olpc-2.6
$ setarch i386 make ARCH=i386 xo_1-kernel-rpm

== Resources ==

* [[Machine/dextrose|Dextrose VM]] hosted by [[Machine/treehouse|treehouse]]

* [[Development_Team/Jhbuild|Sugar-jhbuild]] - The Sugar build system

* [http://www.rpm.org/wiki/Docs RPM] - The Red Hat package manager

* [http://fedoraproject.org/wiki/Packaging/Guidelines Fedora packaging] - Fedora packaging workflow and conventions

* [http://createrepo.baseurl.org/ createrepo] - the yum package repositories builder

* [http://activities.sugarlabs.org ASLO] - The Sugar Labs Activities Library

* General understanding of the Linux system plumbing infrastructure: [http://www.kernel.org/ kernel],
[http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html udev], [http://www.freedesktop.org/wiki/Software/dbus dbus], [http://www.freedesktop.org/wiki/Software/DeviceKit DeviceKit], [http://www.freedesktop.org/wiki/NetworkManager NetworkManager],
[http://www.x.org/wiki/ Xorg]...

* Flashing laptops and debugging any problems

* Interaction with the Sugar and OLPC community to solve issues and minimize our divergence from the official builds.

Machine/dextrose

2012-01-31T19:32:57Z

Dogi: /* Admins */

{{TOCright}}

== Description ==

Short descrition of machine purpose

== OS ==

Distro and version.

== Services ==

* [[Service/zzz_template|TEMPLATE_SERVICE]]

== Hardware ==

* KVM Virtual Machine

== Location ==

[[Machine/HOST|HOST]]

== Admins ==

* [[User:bernie|Bernie Innocenti]]

== Backup ==

* Daily system-full-backup on [[Machine/backup]]. Ask admins for encryption password.

== Notes ==

User:Alsroot

2012-01-31T19:28:53Z

Dogi: /* Background tasks */

<noinclude>{{TOCright}}</noinclude>

== Hi ==

A short bio:

{|
|-
|'''Name'''
|Aleksey Lim
|-
|'''Birth'''
|1977
|-
|'''Residence'''
|Russia
|-
|'''Education'''
|University college, USSR, 1994-1999, software developer
|-
|'''Career'''
|1999-2008, C/C++ developer for various commercial companies
|-
|
|2008-2010, the first experience of being a FOSS contributor, full time Sugar Labs contributor and volunteer
|-
|
|2011-2011, [http://activitycentral.org/ Activity Central]
|-
|}

== Contacts ==

* Nick ''alsroot''
* [[Special:Emailuser/alsroot|Email me]] to my nick in ''sugarlabs.org'' domain
* Timezone UTC

== Roadmap ==

=== Foreground tasks ===

* [[Sugar Network]] development
* [[Sugar Server Kit]] development
* [[Platform_Team/Sweets|Sweets, Packaging Management System]] development

=== Background tasks ===

* Maintain Sugar Labs servers:
** [[Machine/jita|jita]]
** [[Machine/aslo-web|aslo-web]]
* Maintain Sugar Labs services:
** [[Service/cgit|cgit]]
** [[Service/git|git]]
** [[Service/meeting|meeting]]
** [[Service/chat|chat]]
** [[Service/activities|activities]]
** [[Service/jabber|jabber]]
** [[Service/meeting|meeting]]
** [[Service/translate|translate]]
** [[Service/obs|obs]]
* Develop projects:
** [[Activity_Team/gst-plugins-espeak|gst-plugins-espeak]]
* Develop activities:
** [[Activities/Cartoon_Builder|Cartoon Builder]]
** [[Activities/Flip_Sticks|Flip Sticks]]
** [[Activities/Speak|Speak]]
** [[Activities/Tam_Tam|Tam Tam]]
** [[Activities/Chat|Chat]]
* Maintain activities:
** [[Activities/Image_Viewer|Image Viewer]]
** [[Activities/Jigsaw Puzzle|Jigsaw_Puzzle]]
** [[Activities/Joke_Machine|Joke Machine]]
** [[Activities/Slider_Puzzle|Slider_Puzzle]]
** [[Activities/Story_Builder|Story Builder]]
* Maintain activities for upstream projects:
** [http://activities.sugarlabs.org/en-US/sugar/addon/4284 GeoGebra]
** [[Activities/GCompris|GCompris]]
** [[Activities/Tux_Paint|Tux Paint]]
* Packaging
** [[Community/Distributions/Sweets_Distribution|Sweets Distribution]]

=== In perspective ===

* Sugarize OOo4Kids
** journal integration
** OOo4Kids builds
* Life in sugar! - support full time being online in sugar
** Sugar Daemons, all time beeing online servers that provide useful shared instances for broad collaboration e.g. Chat instances per purposes ("Ask your nub question", "How to hack sugar" etc.)
** Library instance via Sugar Daemon to provide server sharing model
** Сheck notification system in shell if it works well in "all time being in sugar" workflow
** Сreate [[Collab_mockup|Collab]] activity
** Collab instance via Sugar Daemon to have global collaboration portal for all sugar contributors/requesters.
* standalone mode for activities thus more close merge sugar with other education software e.g. ASLO could be not just portal of sugar activities but portal of education software(non-sugar users could run particular activity w/o need to install sugar)

== Resources ==

* [[Deployment Team/jhconvert|Tool to generate sugar packages]]
* [[Community/Distributions/Gentoo|Sugar on Gentoo overlay]]
* [[Community/Distributions/ALTLinux|Sugar on ALT Linux]]
* http://www.gentoo.org/
* http://en.altlinux.org/

Service/activities

2012-01-31T19:28:08Z

Dogi:

== Description ==

* Activities distribution, similar to [http://addons.mozilla.org addons.mozilla.org] [http://www.gnomefiles.org gnomefiles.org].
* An implementation of the upstream project, [https://wiki.mozilla.org/Update:Remora Remora], the underlying technology supporting [http://addons.mozilla.org addons.mozilla.org].
* Supports [[Activity Library]].

== Hostnames ==

* http://activities.sugarlabs.org/
* http://aslo-web.sugarlabs.org/ (second ASLO node)

== Hosted on ==

* [[Machine/sunjammer]]
* [[Machine/aslo-web]] second node.

== Administrative contact ==

activities AT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:alsroot|Aleksey Lim]], server maintenance
* [[User:RafaelOrtiz|Rafael Ortiz]], content maintenance

== Notes ==

ASLO is in process of [[Platform Team/Activity Library/5|moving]] to the new [https://wiki.mozilla.org/AMO:Developers AMO] code base.

== Upgrade notes ==

''TODO''

== See Also ==

''TODO''

Machine/aslo-web

2012-01-31T19:27:49Z

Dogi: moved Machine/treehouse/aslo-web to Machine/aslo-web

== Hostnames ==

* http://aslo-web.sugarlabs.org

== Hardware ==

* KVM VM

== Location ==

[[Machine/housetree|Housetree]]

== Admins ==

* [[User:alsroot|Aleksey Lim]]

== Backups ==



== Setup ==

===Install required php modules===
pear config-set preferred_state beta
pear install Archive_Zip

===Create user to run scripts===
Make sure that all files in /srv/activities
* has apache(web-data) user
* ''activities'' group
* group write access
* umask is 002

===Switch to activities user===

sudo -i -u activities

===Set up NFS mount points===

Create directories
mkdir -p ~/files
mkdir -p ~/staging

Add the following lines to the end of `/etc/fstab'

sunjammer.sugarlabs.org:/srv/nfs/activities/files /srv/activities/files nfs rsize=8192,wsize=8192,timeo=14,intr
sunjammer.sugarlabs.org:/srv/nfs/activities/staging /srv/activities/staging nfs rsize=8192,wsize=8192,timeo=14,intr

===Clone ASLO repository===

git clone git://git.sugarlabs.org/slo-activities/mainline.git -b production .

===Checkout dependencies===

cd ~/site/vendors/
svn co http://svn.mozilla.org/libs/product-details
svn co http://svn.mozilla.org/libs/fizzypop.mozdev fizzypop
svn co http://svn.mozilla.org/libs/phorms
svn co http://svn.mozilla.org/libs/zxtm-api

==ASLO configuration==

Using ''~/aslo/config.php'' as template, setup ASLO settings in file ''~/site/app/config/config.php''. Template file was configured for ''dev'' environment, switch it to production by setting ''SITE_STATE'' variable to ''production''.

Setup other env defines in file ''~/site/app/config/config-local.php''
define('DEBUG', 0);
define('DEV', false);
define('QUERY_CACHE', true);

All local configuration should happen in files
~/site/app/config/config.php
~/site/app/config/config-local.php

==Update ASLO repository==

git pull origin production

Machine/pootle

2012-01-31T19:26:14Z

Dogi: moved Machine/treehouse/pootle to Machine/pootle

== Hostnames ==

* http://translate.sugarlabs.org/

== Services ==

* [[Service/translate]]

== General Information ==

This machine hosts exclusivelty Pootle.

== Location ==

KVM virtual machine hosted on [[Machine/treehouse]]

== Admins ==

* [[User:தங்கமணி_அருண்|தங்கமணி அருண்(Thangamani Arun)]], thangam_arun on #sugar Freenode
* [[User:Bernie|Bernie Innocenti]], bernie on #sugar Freenode (only machine-level issues)

Service/translate

2012-01-31T19:25:49Z

Dogi:

== Hostnames ==

* http://translate.sugarlabs.org/

Additional urls:

* http://translate.sugarlabs.org/status, status page
* http://translate.sugarlabs.org/langpacks, language packs

== Hosted on ==

[[Machine/pootle]]

== Administrative contact ==

* translate AT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:Cjl|Chris Leonard]] has Pootle administrator privs.
* [[User:RafaelOrtiz | Rafael Ortiz]] has system admin and Pootle admin privs.
* [[User:Bernie|Bernie Innocenti]] has system admin and Pootle administrator privs, but takes care only of OS-level administration.
* [[User:SayaminduDasgupta|Sayamindu Dasgupta]] is the former admin. He still has an emeritus sysadmin account and he can be very helpful if contacted by email.

== Language Administrators ==

Language administrators are typically native speakers of a given language that take on responsibility (granted by a Pootle administrator after a request to the Localization list) for reviewing and committing PO files for a given language. Contacting language administrators is generally done by posting to the Localization list.

More information on language administrator duties can be found on [[Translation_Team/Administration_QuickStart|this page]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | Home
|{{Code|/var/lib/pootle}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/apache2}} 
{{Code|/etc/init.d/pootle}}
|-
!scope="row" | Logs
|{{Code|/var/log/apache2}}
|-
!scope="row" | Config
|
{{Code|/etc/apache2/sites-enabled/000-default}} 
{{Code|/etc/cron.d/pootle}} 
|-
!scope="row" | Ports
|
{{Code|80}} HTTP server
|-
|}

== Upgrade notes ==

*A backup of the DB and pootle localsettings.py must be done also.
*Backup of the /var/lib/pootle structure
*New versions of Django and Translate toolkit must be installed first
*Restore localsettings and DB backup

== Mantainance Notes ==

Pootle in Sugar is maintained. (dirakx has step-up to be maint)

We (godiard / martin_xsa / erikos / dirakx / Bernie / Dogi)  are trying to resolve the pending issues because we need working translations.

To date translations are working, we are working in a new VM pootle-devel to test upgrades of the Pootle/Django/Translate-toolkit stack.

The last maintainer was Sayamindu Dasgupta and we asked he our doubts, i am putting here this information.

== Files ==

Important files and directories in the root directory, {{Code|/var/lib/pootle}}.

{{Code|'''checkouts'''}} 
Sources are checked out in this directory and being used to keep final {{Code|.pot}} and {{Code|.po}} files. The hierarchy is:

checkouts/''pootle-project''/''pootle-po-filename-without-po-suffix''/''sources''

{{Code|'''translations'''}} 
Pootle uses this directory as a sources of files to translate, it contains symlinks to files from the {{Code|checkouts}} directory. The hierarchy is:

translations/''pootle-project''/''lang''/''symlinks-to-po-files''

{{Code|'''maintenance'''}} 
Contains some sugar-specific scripts to help maintain our Pootle instance, they are managed in http://git.sugarlabs.org/projects/pootle-helpers.

{{Code|'''maintenance/helpers/potupdater/project_list.ini'''}} 
This is an Ini file that contains configuration for all used sources repositories. Each section describes one sources repository, where section name is full path, in form of {{Code|/var/lib/pootle/checkouts/''pootle-project''/''pootle-filename''/''some-path-within-sources''/''pot-file''}}, to the {{Code|.pot}} file, and contains following options:

* {{Code|project}} required, meaning-less project name;
* {{Code|vcs}} required, the type of VCS for; supported values are: {{Code|git}};
* {{Code|method}} required, the method how to generate {{Code|.pot}} files from sources; supported values are: {{Code|bundlebuilder}} for activities, {{Code|intltool}} for intltool based projects;
* {{Code|layout}} required, ?;
* {{Code|ignore-files}} optional, the semicolon separated list of file paths that are relative to the sources root; if {{Code|method}} is {{Code|bundlebuilder}} this value will be used to ignore while producing {{Code|.pot files}};

== Tools ==

* {{Code|potupdater/pogenerator.py}} pulls from git and svn so we have updated sources, then it generates a new .pot file from them. Translated strings get reflected in the .po files in each module, and when the language maintainer clicks the Commit to VCS link, get pushed back to the upstream module.
* {{Code|admin/pootlepopulator.py}} checkout sources.
* {{Code|misc/pootle.cron}} all daily basis routines.
* ''...''

== Tips ==

=== Create new Pootle project ===

* Create new project in Pootle admin menu, ''admin->projects'';
* Add all needed langs;
* Checkout all sources using command:

sudo -u pootle -i python maintenance/helpers/admin/pootlepopulator.py ''pootle-project'' ''git-clone-url'' ''pootle-filename-wo-po-suffix'' ''git-branch''

Example:

To checkout the sugar in the branch sucrose-0.94 (in pootle is in the project glucose94) we sshould do:

cd /var/lib/pootle/
sudo -u pootle -i python maintenance/helpers/admin/pootlepopulator.py glucose94 gitorious@git.sugarlabs.org:sugar/mainline.git sugar sucrose-0.94

* Add new sections to the [[#Files|project_list.ini]] file to describe new {{Code|.pot}} locations;
* Run {{Code|misc/pootle.cron}} script from {{Code|pootle}} user to generate all sufficient files;
* Click ''rescan the project files'' in ''Templates->Project->Files'' to reveal newly created {{Code|.pot}} files;
* Click ''Update from templates'' for all languages in newly created project to peek up {{Code|.po}} files symlinked by {{Code|misc/pootle.cron}} script.

=== Adding activities ===

Before registering new activity on http://translate.sugarlabs.org, make sure that:

* New activity is being hosted on http://git.sugarlabs.org;
* The {{Code|pootle}} user was added to the repository with commit access rights;
* You have a proper {{Code|GIT_URL}} to clone repository from with commit permissions, e.g., {{Code|gitorious@git.sugarlabs.org:cartoon-builder/mainline.git}}; that might be found on home page in Gitorious, e.g., http://git.sugarlabs.org/cartoon-builder, in ''Clone & push urls'' field with selector ''SSH'';
* You know the proper {{Code|CATEGORY}} name to register the project in;
* There is an unique {{Code|NAME}} of activity, this name will be used as a name of project in Pootle and directory name;
* You know the proper {{Code|BRANCH}} in Git repository to use for translation; by default, it is {{Code|master}}.

To process the registration, login to translate.sugarlabs.org and enter:

sudo -u pootle python /var/lib/pootle/maintenance/helpers/admin/pootlepopulator.py ''<CATEGORY>'' ''<GIT_URL>'' /var/lib/pootle/checkouts/''<CATEGORY>''/''<NAME>'' [''<BRANCH>'']

After that, for [http://git.sugarlabs.org/pootle-helpers pootle-helper] project in {{Code|potupdater/project_list.ini}}, add the following strings:

[/var/lib/pootle/checkouts/''<CATEGORY>''/''<NAME>''/po/''<.pot-filename>'']
project = ''<NAME>''
vcs = git
method = bundlebuilder
layout = gnu

Commit new changes, and pull from on pootle VM:

(cd /var/lib/pootle/maintenance/helpers; sudo -u pootle git pull origin master)

Do ''update from templates'' on the ''templates'' project on Pootle's frontend. And wait until daily cron job will populate languages for newly registered project, or run it immediately:

sudo -u pootle python /var/lib/pootle/maintenance/helpers/admin/add_langs.py

Then your activity must be in place to be translated and ''commit to VCS/update from VCS'' links must be activated.

=== Working with git in the pootle server ===

The git operations must be done by the pootle user:

sudo -u pootle git log

sudo -u pootle git push origin sucrose-0.82

This script tell you when you can update different clones of activities, when new strings are added via gettext in each repo.

/var/lib/pootle/maintenance/helpers/potupdater/check_unmerged_translations.sh

Other important script is pogenerator.py this script re-generates pot in each repo.

=== Resolving conflicts ===

If the maintainer did a commit with a file in the po directory we will have a conflict, and Pootle can not do a pull.

Pootle build the pot file from the sources, if we compare and the translations are updated in pootle
we can do a pull preserving the info in pootle:

sudo -u pootle git pull -s ours

=== Checking that pootle is working ===

* When commiting from pootle interface, repos in git reflect the commit as something similar to:

pootle pushed 3fd0cf7b to taportfolio/mainline:master
on March 04, 2011 01:32
Commit from Sugar Labs: Translation System by user cjl.: 2 of 25 messages translated (0 fuzzy).

* Pogenerator.py (in cronjob), it's also giving mails with info like:

Already up-to-date. or
####### Checking POT for Write (master) ######

=== Tips ===

* How to manipulate users:

django-admin shell --settings=pootle.settings
>>> from django.contrib.auth.models import User
>>> u = User.objects.get(username='bernie')
>>> u.is_superuser = True
>>> u.save()

* Refresh stats, needed when the database and the checked out modules get out of sync:

sudo -u pootle django-admin refresh_stats --settings=pootle.settings

* If you have a commit error file because of only read git url, please rm the old '''/var/lib/pootle/checkouts/''' files related with that activity or project and re run pootlepopulator.

* Also if there are errors related with git add, is likely that some lang.po files are not versionated on pootle server, please run '''git add .''' inside the activity or project.

* When there are '''commit to cvs/update to cvs''' links missing in activities or projects please check git url in .git/config , this URL must be writable by pootle.

== References ==

* http://translate.sourceforge.net/wiki/pootle/installation
* http://lists.laptop.org/listinfo/localization
* http://git.sugarlabs.org/pootle-helpers
* /usr/lib/python2.6/dist-packages/translate/storage/versioncontrol/git.py (Translate)

[[Category:Service|translate]]

Machine/serendipity

2012-01-31T19:24:09Z

Dogi: moved Machine/housetree/serendipity to Machine/serendipity

{{TOCright}}

== Description ==

This machine is used by [[User:Rgs|rgs]] for some testing and running his blog (itevenworks.net).

== OS ==

== Services ==

== Hardware ==

* KVM Virtual Machine

== Location ==

== Admins ==

* [[User:rgs|Raul Gutierrez Segales]]
* [[User:bernie|Bernie Innocenti]]

== Backup ==

* Daily system-full-backup on [[Machine/backup]]. Ask admins for encryption password.

== Notes ==

Machine/serendipity

2012-01-31T19:23:11Z

Dogi:

Service/blacklist

2012-01-31T19:18:24Z

Dogi:

== Hostnames ==

* None

== Hosted on ==

[[Machine/jita]]

== Administrative contact ==

See [[#Sysadmins|Sysadmins]] section.

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:alsroot|Aleksey Lim]]

== Notes ==

{| class="wikitable"
|-
!scope="row" | User
|{{Code|blacklist}}
|-
!scope="row" | Home
|{{Code|/srv/blacklist}}
|-
!scope="row" | Cron
|{{Code|/etc/cron.daily/blacklist}}
|-
!scope="row" | Config
|{{Code|/srv/blacklist/.config/sweets/config}}
|-
|}

This is an infra to keep [[Sugar_Server_Kit/sugar-server-blacklist|sugar-server-blacklist]] package up-to-date. The cron task will trigger checking if upstream blacklist was changed, and it it is, new package will be uploaded to https://obs.sugarlabs.org by calling [[Platform_Team/Guide/Sweets_Usage|sweets]] command. The sources of sweets is cloned to blacklist user's home directory.

== Upgrade notes ==

{| class="wikitable"
|-
!scope="row" | git
|{{Code|/srv/blacklist/site}}
|-
|}

Service/cgit

2012-01-31T19:18:06Z

Dogi:

== Hostnames ==

* http://cgit.sugarlabs.org/

== Hosted on ==

[[Machine/jita]]

== Administrative contact ==

cgit AT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:alsroot|Aleksey Lim]]

== Notes ==

[http://hjemli.net/git/cgit/ cgit] interface to git repositories managed by [[Service/git|gitorious]].

{| class="wikitable"
|-
!scope="row" | Home
|{{Code|/srv/cgit}}
|-
!scope="row" | Config
|
{{Code|/etc/cgitrc}} 
{{Code|/etc/httpd/conf.d/cgit.sugarlabs.org.conf}}
|-
|}

== Upgrade notes ==

{| class="wikitable"
!scope="row" | yum
|
{{Code|cgit}}
|-
|}

Obsolete Service/cas

2012-01-31T19:17:52Z

Dogi:

== Hostnames ==

* https://cas.sugarlabs.org/

== Hosted on ==

[[Machine/jita]]

== Administrative contact ==

cas AT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:alsroot|Aleksey Lim]]

== Notes ==

[http://code.google.com/p/rubycas-server/ CAS] server to handle SL common login using [http://ldap.sugarlabs.org ldap.sugarlabs.org] as a source of users directory.

{| class="wikitable"
|-
!scope="row" | Home
|{{Code|/srv/cas}}
|-
!scope="row" | Logs
|{{Code|/srv/gitorious/app/log}}
|-
!scope="row" | Config
|
{{Code|/etc/rubycas-server/config.yml}} 
{{Code|/etc/httpd/conf.d/cas.sugarlabs.org.conf}} 
{{Code|/etc/logrotate.d/cas}}
|-
!scope="row" | SSL certificates
|
{{Code|/etc/ssl/private/cas.sugarlabs.org.key}} 
{{Code|/etc/ssl/certs/cas.sugarlabs.org.pem}}
|-
!scope="row" | Sources
| http://git.sugarlabs.org/sl-tweaks/rubycas-server
|-
|}

Configuration links:
* [https://code.google.com/p/rubycas-server/wiki/QuickStart QuickStart]

== Upgrade notes ==

{| class="wikitable"
!scope="row" | git
|
{{Code|/srv/cas}}
|-
|}

== Links ==
[[CAS Sites]] (Services to integrate in CAS).

Service/chat

2012-01-31T19:17:34Z

Dogi:

== Hostnames ==

* https://chat.sugarlabs.org/
* http://chat.sugarlabs.org/

== Hosted on ==

[[Machine/jita]]

== Administrative contact ==

chat AT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:alsroot|Aleksey Lim]]

== Notes ==

This is an instance of [http://qwebirc.org/ qwebirc].

{| class="wikitable"
|-
!scope="row" | Home
|{{Code|/srv/qwebirc}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/qwebirc}} 
{{Code|/etc/init.d/qwebirc-ssl}}
|-
!scope="row" | Logs
|{{Code|syslog}}
|-
!scope="row" | Config
|
{{Code|/srv/qwebirc/config.py}} 
{{Code|/srv/qwebirc/header.html}} 
{{Code|/srv/qwebirc/lingva_bot.py}} 
{{Code|/etc/httpd/conf.d/chat.sugarlabs.org.conf}}
|-
!scope="row" | SSL certificates
|
{{Code|/etc/ssl/private/chat.sugarlabs.org.pem}} 
{{Code|/etc/ssl/private/chat.sugarlabs.org.key}}
|-
!scope="row" | Ports
|
{{Code|9090}}, not secure chatting 
{{Code|9091}}, secure chatting
|-
|}

== Upgrade notes ==

{| class="wikitable"
!scope="row" | git
|
{{Code|/srv/qwebirc}}
|-
|}

== Usage ==

{{:{{PAGENAME}}/Usage}}

Obsolete Service/obs

2012-01-31T19:17:17Z

Dogi:

== Hostnames ==

* obs.sugarlabs.org
* packages.sugarlabs.org
* sweets.sugarlabs.org

== Hosted on ==

[[Machine/jita]]

== Administrative contact ==

* obs AT sugarlabs DOT org

== Sysadmins ==

* [[User:alsroot|Aleksey Lim]]

== Notes ==

[http://build.opensuse.org/ OBS] instance with sugar related changes.

{| class="wikitable"
|-
!scope="row" | Home
|{{Code|/srv/obs}}
|-
!scope="row" | Daemon
|
{{Code|/etc/init.d/obs}} 
{{Code|/etc/init.d/obs-worker}}
|-
!scope="row" | Config
|
{{Code|/srv/obs/app/src/backend/BSConfig.pm}} 
{{Code|/srv/obs/app/src/api/config/}} 
{{Code|/srv/obs/app/src/webui/config/}}
|-
!scope="row" | Logs
|{{Code|/srv/obs/site/log}}
|-
!scope="row" | SSL certificates
|
{{Code|/etc/ssl/private/obs.sugarlabs.org.key}} 
{{Code|/etc/ssl/certs/obs.sugarlabs.org.pem}} 
{{Code|/etc/ssl/private/packages.sugarlabs.org.key}} 
{{Code|/etc/ssl/certs/packages.sugarlabs.org.pem}} 
|-
|}

{{Note/warning|Caution|Since python OBS clients can't handle SNI, default vhost needs to provide {{Code|obs.sugarlabs.org}} SSL certificate.}}

== Upgrade notes ==
{| class="wikitable"
!scope="row" | git
|
{{Code|/srv/obs/app}}
|-
|}

Service/meeting

2012-01-31T19:16:58Z

Dogi:

<noinclude>
[[Category:Service|IRC]]
</noinclude>

== Hostnames ==

* meeting.sugarlabs.org
* meeting.treehouse.su

== Hosted on ==

[[Machine/jita]]

== Administrative contact ==

* meeting AT sugarlabs DOT org

== Sysadmins ==

* [[User:alsroot|Aleksey Lim]]
* [[User:dogi|Stefan Unterhauser]]

== Notes ==

[http://sourceforge.net/projects/supybot/ IRC] bot with plugins and perl CGI access to IRC logs in local MySQL db using [http://git.sugarlabs.org/projects/ilbot modified] ilbot webui.

=== IRC bot ===

This new bot replaces the older [http://wiki.laptop.org/go/User:Dogi/meeting Mootbot] with Supybot.

{| class="wikitable"
|-
!scope="row" | Home
|{{Code|/srv/supybot}}
|-
!scope="row" | Daemon
|{{Code|/etc/init.d/supybot}}
|-
!scope="row" | Logs
|{{Code|/srv/supybot/log}}
|-
!scope="row" | Config
|{{Code|/srv/supybot/bot.conf}}
{{Code|/etc/logrotate.d/supybot}}
|-
|}

Everything, except owner related configuration, should happen via [http://supybook.fealdia.org/devel/#_administrative_tasks IRC interface] with using {{Code|flush}} command to save changes immediately.

Supybot plugins:

* [http://git.sugarlabs.org/sl-tweaks/meetbot MeetBot] in {{Code|/srv/supybot/plugins/MeetBot}} Handle meetings.
* [http://git.sugarlabs.org/sl-tweaks/supybot-mylogger MyLogger] in {{Code|/srv/supybot/plugins/MyLogger}} Keep IRC logs in MySQL database.
* [http://git.sugarlabs.org/sl-tweaks/supybot-lingvo Lingvo] in {{Code|/srv/supybot/plugins/Lingvo}} Online translation on IRC.

=== Web logs ===

{| class="wikitable"
|-
!scope="row" | Home
|{{Code|/srv/ilbot}}
|-
!scope="row" | Config
|
{{Code|/etc/httpd/conf.d/meeting.sugarlabs.org.conf}} 
{{Code|/etc/httpd/conf.d/meeting.treehouse.su.conf}} 
{{Code|/srv/ilbot/cgi/database.conf}}
|-
!scope="row" | Source
|http://git.sugarlabs.org/sl-tweaks/ilbot
|-
|}

== Upgrade notes ==

{| class="wikitable"
|-
!scope="row" | yum
|{{Code|supybot}}
|-
!scope="row" | git
|
{{Code|/srv/supybot/plugins/MeetBot}} 
{{Code|/srv/supybot/plugins/MyLogger}} 
{{Code|/srv/supybot/plugins/Lingvo}} 
{{Code|/srv/ilbot}}
|-
|}

== Usage ==

{{:{{PAGENAME}}/Usage}}

Obsolete Service/jabber

2012-01-31T19:16:42Z

Dogi:

== Hostnames ==

* jabber.sugarlabs.org

== Hosted on ==

[[Machine/jita]]

== Administrative contact ==

jabber AT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:alsroot|Aleksey Lim]]

== Notes ==

Jabber server for development needs to test cutting edge sugar core components.

It runs [http://prosody.im/ Prosody] jabber server with additional sugar [http://git.sugarlabs.org/server/prosody-sugar plugins].

{| class="wikitable"
|-
!scope="row" | Daemon
|{{Code|prosody}}
|-
!scope="row" | Config
|{{Code|/srv/prosody/prosody.cfg.lua}}
|-
!scope="row" | Logs
|{{Code|/srv/prosody/log}}
|-
!scope="row" | Ports
|{{Code|5222}} {{Code|5223}} {{Code|5000}}
|-
|}

Runtime configuration and monitoring might happen via [http://prosody.im/doc/console telnet]:
telnet localhost 5582

== Upgrade notes ==

{| class="wikitable"
|-
!scope="row" | git
|{{Code|/srv/prosody}}
|-
|}

Service/git

2012-01-31T19:15:59Z

Dogi:

== Hostnames ==

* http://git.sugarlabs.org

== Hardware ==

[[Machine/jita]]

== Administrative contact ==

git AT sugarlabs DOT org

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:alsroot|Aleksey Lim]]

== Notes ==

[http://gitorious.org/ Gitorious] hosting.

{| class="wikitable"
|-
!scope="row" | Home
|{{Code|/srv/gitorious}}
|-
!scope="row" | Daemon
|{{Code|/etc/init.d/gitorious}}
|-
!scope="row" | Logs
|{{Code|/srv/gitorious/app/log}}
|-
!scope="row" | Config
|
{{Code|/srv/gitorious/app/config/database.yml}} 
{{Code|/srv/gitorious/app/config/gitorious.yml}} 
{{Code|/etc/cron.daily/gitorious}} 
{{Code|/etc/logrotate.d/gitorious}} 
{{Code|/etc/httpd/conf.d/git.sugarlabs.org.conf}}
|-
!scope="row" | SSL certificates
|
{{Code|/etc/ssl/private/git.sugarlabs.org.key}} 
{{Code|/etc/ssl/certs/git.sugarlabs.org.pem}}
|-
!scope="row" | Ports
|
{{Code|9418}} git server
|-
!scope="row" | Sources
| http://gitorious.org/~alsroot/sugarlabs-org
|-
|}

=== Plugins ===

Sugar Labs Gitorious instance uses downstream several plugins. All of them are enabled from {{Code|app/processors/push_event_processor.rb}} file and placed to {{code|lib/}} directory.

==== CIA ====

Notify http://cia.vc about all commits.

Plugin file:

lib/cia.rb

{{Code|gitorious.yml}} configuration:

cia: true

==== Patchwork ====

[http://patchwork.sugarlabs.org/ Patchwork] integration.

Plugin file:

lib/patchwork.rb

{{Code|gitorious.yml}} configuration:

patchwork:
sugar:
url: "https://git.sugarlabs.org:0000000000000000000000000@patchwork.sugarlabs.org/xmlrpc/"
linkname: sugar
repositories:
- mainline
set_state: Accepted
find_states:
- New
- Under Review

==== Pootle commits ====

Send notification emails on every pootle commit.

Plugin file:

lib/emailer.rb

{{Code|gitorious.yml}} configuration:

emailer: true

=== Database tips ===

To make runtime changes in Gitorious database, follow regular Rails workflow - run {{Code|scripts/console}}:

cd /srv/gitorious/app
sudo -u gitorious RAILS_ENV=production script/console

It is regular Ruby console and all feature like {{Code|TAB}} completion work. To tweak Gitorious data, just use its [http://gitorious.org/gitorious/mainline/trees/master/app/models model classes], e.g.:

# search of particular object by its attributes
user = User.find_by_login("user")
project = Project.find_by_title("project")

# get object attributes
user.email

# change object attributes
project.owner = User.find_by_email("foo@bar")
project.save!

# destroy object and all its dependencies
user.destroy

# reset user password
user = User.find_by_email("user")
password_key = user.forgot_password!
Mailer.deliver_forgotten_password(user, password_key)

# add repository committer
committer = User.find_by_login("user")
repo = Repository::find_by_path("sugar/mainline")
repo.committerships.create_with_permissions!({:committer => committer}, (Committership::CAN_COMMIT))

# delete repository committer
committer = User.find_by_login("user")
repo = Repository::find_by_path("sugar/mainline")
repo.committerships = repo.committerships.select {|i| !i.members.include? committer }

# change repository owner
new_owner = User.find_by_login("user")
repo = Repository::find_by_path("sugar/mainline")
cs = repo.committerships.select {|i| i.committer == new_owner}.pop
cs.permissions = (Committership::CAN_ADMIN | Committership::CAN_COMMIT | Committership::CAN_REVIEW)
cs.save!
repo.owner = new_owner
repo.save!

# move repository to another project
new_project = Project.find_by_title('sl-tweaks')
repo = Repository::find_by_path("sat-solver/mainline")
repo.project = new_project
repo.name = "sat-solver"
repo.save!

=== TODO ===

Current gitorious patch doesn't handle renaming repositories properly and doesn't update symliks in {{Code|/srv/gitorious/repos-by-name}}. For now, run code to recreate symlinks:

Repository::find_each {|i| s='/srv/gitorious/repos/' + i.real_gitdir; d='/srv/gitorious/repos-by-name/' + i.gitdir; FileUtils.makedirs(File.dirname(d)) if !File.exist?(File.dirname(d)); File.symlink(s, d) if !File.exists? d}

== Upgrade notes ==

{| class="wikitable"
!scope="row" | git
|
{{Code|/srv/gitorious/app}}
|-
|}

After pulling new sources, migrate database:

cd /srv/gitorious/app/
sudo -u gitorious RAILS_ENV=production rake db:migrate

Machine/booki

2011-06-17T18:31:36Z

Dogi:

{{TOCright}}

== Description ==

This VM is build as a Webservice to create and store "textbooks".
Technially this service is build on top of django and the [[http://download.booki.cc/ booki]] - plugins/extensions.

== OS ==

[[Machine/template-maverick|Ubuntu 10.10]]

== Services ==

* [[Service/zzz_template|TEMPLATE_SERVICE]]

== Hardware ==

* KVM Virtual Machine

== Location ==

[[Machine/treehouse|treehouse]]

== Admins ==

* [[User:Mokurai|Mokurai]]
* [[User:dogi|Stefan Unterhauser]]

== ToDo ==
* use apache for http delivery ... right now this service is provided by the django /python command "django-admin runserver 0.0.0.0:80" which has to be excuted in a screen session ...

== known problems ==
from time to time django has to be restarted ... grrrrr.
ssh mokurai@book.treehouse.su
sudo -s
screen -R
[CTRL-C] #to terminate the blocked/slow/running django
django-admin runserver 0.0.0.0:80 #start again
[CTRL-A followed by D] # detach screen session without terminating ...

Machine/booki

2011-06-17T18:25:52Z

Dogi: Created page with "{{TOCright}} == Description == Short descrition of machine purpose == OS == Distro and version. == Services == * TEMPLATE_SERVICE == Hardware == ..."

{{TOCright}}

== Description ==

Short descrition of machine purpose

== OS ==

Distro and version.

== Services ==

* [[Service/zzz_template|TEMPLATE_SERVICE]]

== Hardware ==

* KVM Virtual Machine

== Location ==

[[Machine/treehouse|treehouse]]

== Admins ==

* [[User:Mokurai|Mokurai]]
* [[User:dogi|Stefan Unterhauser]]

== Notes ==
This VM is build as a Webservice to create and store "textbooks".
Technialy this service is build on top of django and the [[http://download.booki.cc/ booki]] - plugins/extensions.

== Todo ==
* use apache for http delivery ... right now this service is provided by the django /python command "django-admin runserver 0.0.0.0:80" which has to be excuted in a screen session ...

== known problems =
from time to time django has to be restarted ... grrrrr.
ssh mokurai@book.treehouse.su
sudo -s
screen -R
[CTRL-C] #to terminate the blocked/slow/running django
django-admin runserver 0.0.0.0:80
[CTRL-A followed by D]

Service/meeting

2011-04-26T18:23:35Z

Dogi:

<noinclude>
[[Category:Service|IRC]]
</noinclude>

== Hostnames ==

* meeting.sugarlabs.org
* meeting.treehouse.su

== Hosted on ==

[[Machine/housetree/jita]]

== Administrative contact ==

* meeting AT sugarlabs DOT org

== Sysadmins ==

* [[User:alsroot|Aleksey Lim]]
* [[User:dogi|Stefan Unterhauser]]

== Notes ==

[http://sourceforge.net/projects/supybot/ IRC] bot with plugins and perl CGI access to IRC logs in local MySQL db using [http://git.sugarlabs.org/projects/ilbot modified] ilbot webui.

=== IRC bot ===

This new bot replaces the older [http://wiki.laptop.org/go/User:Dogi/meeting Mootbot] with Supybot.

{| class="wikitable"
|-
!scope="row" | Home
|{{Code|/srv/supybot}}
|-
!scope="row" | Daemon
|{{Code|/etc/init.d/supybot}}
|-
!scope="row" | Logs
|{{Code|/srv/supybot/log}}
|-
!scope="row" | Config
|{{Code|/srv/supybot/bot.conf}}
{{Code|/etc/logrotate.d/supybot}}
|-
|}

Everything, except owner related configuration, should happen via [http://supybook.fealdia.org/devel/#_administrative_tasks IRC interface] with using {{Code|flush}} command to save changes immediately.

Supybot plugins:

* [http://git.sugarlabs.org/sl-tweaks/meetbot MeetBot] in {{Code|/srv/supybot/plugins/MeetBot}} Handle meetings.
* [http://git.sugarlabs.org/sl-tweaks/supybot-mylogger MyLogger] in {{Code|/srv/supybot/plugins/MyLogger}} Keep IRC logs in MySQL database.
* [http://git.sugarlabs.org/sl-tweaks/supybot-lingvo Lingvo] in {{Code|/srv/supybot/plugins/Lingvo}} Online translation on IRC.

=== Web logs ===

{| class="wikitable"
|-
!scope="row" | Home
|{{Code|/srv/ilbot}}
|-
!scope="row" | Config
|
{{Code|/etc/httpd/conf.d/meeting.sugarlabs.org.conf}} 
{{Code|/etc/httpd/conf.d/meeting.treehouse.su.conf}} 
{{Code|/srv/ilbot/cgi/database.conf}}
|-
!scope="row" | Source
|http://git.sugarlabs.org/sl-tweaks/ilbot
|-
|}

== Upgrade notes ==

{| class="wikitable"
|-
!scope="row" | yum
|{{Code|supybot}}
|-
!scope="row" | git
|
{{Code|/srv/supybot/plugins/MeetBot}} 
{{Code|/srv/supybot/plugins/MyLogger}} 
{{Code|/srv/supybot/plugins/Lingvo}} 
{{Code|/srv/ilbot}}
|-
|}

== Usage ==

{{:{{PAGENAME}}/Usage}}

Dextrose/Building

2011-04-04T20:49:23Z

Dogi: /* Resources */

<noinclude>{{TeamHeader|Dextrose|home=Dextrose|xbgColor=ffe792|join_label=Get Involved}}</noinclude>

== Dextrose build system ==

Dextrose uses [http://wiki.laptop.org/go/OS_Builder olpc-os-builder], a tool create by OLPC to build official and customized system images. The Dextrose git repository contains, olpc-os-builder, local customizations specific to Dextrose, and fixes and enhancements waiting to be pushed upstream.

== Build host requirements ==

The Dextrose build system runs on '''Fedora 11 i386''' through '''Fedora 14 x86_64'''. What the host system runs '''shouldn't''' matter, because the build runs in a chroot environment. olpc-os-builder does not yet run on Ubuntu due to a missing dependency (bitfrost).

The initial build requires about '''700MB''' of rpm packages and Sugar activity bundles. The packages and bundles are cached for futures builds.

== Initial setup ==

* Install dependencies (you need to be root to do this)

yum upgrade
yum install libtomcrypt-devel bitfrost make gcc mtd-utils python-imgcreate zip unzip zlib-devel

* Checkout Dextrose build system

git clone git://git.sugarlabs.org/dextrose/mainline.git dextrose

* Compile build helper programs

cd dextrose
make

* Generate initial sequence number for the builds (42 is just an example)

echo 42 >buildnr-dx

== Creating a build ==

* Run the build system as root:

time sudo ./osbuilder.py examples/dextrose2-xo1.ini

(if <code>sudo</code> isn't configured for your user, become root beforehand)

The initial build may take several hours, depending on available bandwith.
Subsequent builds will take about 15-20 minutes on average machines.

Upon completion the new image will be available in <tt>build/output</tt>.

Because several build tools (olpc-os-builder, imgcreate and yum) run chrooted
and nested into each other, error output could be misleading or obscure.
Before digging into code, you can ask on IRC in case someone has already seen the same problem.

== Publishing the images ==

Please do not publish signed builds unless they implement the [http://wiki.laptop.org/go/Antitheft_HowTo OLPC anti-theft system].

== Customizing your build ==

olpc-os-builder is documented at
[http://git.sugarlabs.org/projects/dextrose/repos/mainline/trees/master/doc/README README]
in the olpc-os-builder tree. The modules are documented in <tt>README</tt> files in the
[http://git.sugarlabs.org/projects/dextrose/repos/mainline/trees/master/modules modules] directory.

=== Upstream Code ===

Dextrose is based on upstream olpc code located at dev.laptop.org.

git remote add olpc git://dev.laptop.org/projects/olpc-os-builder
git fetch olpc
git log olpc/master

=== Customizing the core RPMs ===

* Go to the <tt>rpms/PACKAGENAME</tt> in the dextrose tree

* Edit the spec file. Typically this involves adding a new patch, which is done by adding a <tt>PatchNN:</tt> tag and a corresponding <tt>%patchNN</tt> rule in <tt>%setup</tt>. Some of the intricacies of RPM spec files are unveiled in the [http://fedoraproject.org/wiki/Packaging/Guidelines Fedora Packaging Guidelines].

* Increase the release number after each change.

=== building the Custom RPM ===

If you have a Fedora 11 i386 system, just type:

make i586

Otherwise, you need to build in a [http://fedoraproject.org/wiki/Projects/Mock mock] chroot:

make srpm
sudo mock -r fedora-11-i386 --resultdir=. --rebuild mypackage.src.rpm

=== Uploading the Custom RPM ===

* Upload rpm to a yum repository and add it to the ini file used by the OLPC OS builder.

* To automate this step, we have a rule <tt>make uploadrpm</tt> which points at the Dextrose repository. Edit <tt>rpms/common/Makefile.common</tt> or <tt>rpms/common/uploadrpm</tt> to retarget this rule to your repository.

=== Building custom kernels ===

$ git clone http://dev.laptop.org/git/olpc-2.6/
$ cd olpc-2.6
$ setarch i386 make ARCH=i386 xo_1-kernel-rpm

== Resources ==

* [http://wiki.sugarlabs.org/go/Machine/treehouse/dextrose dextroseVM] hosted by [http://wiki.sugarlabs.org/go/Machine/treehouse treehouse]

* [http://wiki.sugarlabs.org/go/Development_Team/Jhbuild Sugar-jhbuild] - The Sugar Labs build system

* [http://www.rpm.org/wiki/Docs RPM] - The RedHat package manager

* [http://fedoraproject.org/wiki/Packaging/Guidelines Fedora packaging] - Fedora packaging workflow and conventions

* [http://createrepo.baseurl.org/ createrepo] - the yum package repositories builder

* [http://activities.sugarlabs.org ASLO] - The Sugar Labs Activities Library

* General understanding of the Linux system plumbing infrastructure: [http://www.kernel.org/ kernel],
[http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html udev], [http://www.freedesktop.org/wiki/Software/dbus dbus], [http://www.freedesktop.org/wiki/Software/DeviceKit DeviceKit], [http://www.freedesktop.org/wiki/NetworkManager NetworkManager],
[http://www.x.org/wiki/ Xorg]...

* Flashing laptops and debugging any problems

* Interaction with the Sugar and OLPC community to solve issues and minimize our divergence from the official builds.

Machine/treehouse

2011-04-04T20:46:04Z

Dogi:

<noinclude>{{TOCright}}</noinclude>

[[Image:Sunjammer.jpg|right|320px]]

== Hostnames ==
* treehouse.treehouse.su
* treehouse.sugarlabs.org

=== Info ===

Treehouse is a KVM host owned by to [[User:dogi|Stefan Unterhauser]], who kindly made 50% of its
capacity available to Sugar Labs.

Treehouse has an identical twin: [[Machine/housetree|Housetree]].

== Hardware ==
* 2U rack-mountable case
* Motherboard ASUS KFSN5-D
* 2x dual-core Opteron 2214 HE @ 1GHz
* 64GB RAM
* 3x1TB RAID1

== Software ==
* Ubuntu Jaunty amd64

== Location ==
Hosted by the [http://www.fsf.org/ Free Software Foundation] at the [http://www.gnaps.com/ Global NAPs] collocation facility.

== Admins ==
* [[User:Bernie|Bernie Innocenti]], bernie on #sugar Freenode
* [[User:Dogi|Stefan Unterhauser]], dogi on #sugar or [http://mibbit.com/?channel=%23treehouse&server=irc.oftc.net #treehouse]

== Network configuration ==

Treehouse is globally accessible through public, static IPv4 as well as
an IPv6 /64 subnet (6to4).

IPs 140.186.70.100 to 140.186.70.150 are available for hosted VMs.

== Hosted VMs ==
All KVM virtual machines are managed by libvirtd. Yes, that's scary.

See [[Sysadmin/Add virtual machine]] for creating new VMs.

{{Special:PrefixIndex/{{PAGENAME}}/}}

Infrastructure Team/TODO

2011-03-16T20:14:23Z

Dogi: /* High priority tasks */

<noinclude>{{TeamHeader|Infrastructure Team}}</noinclude>
{{TOCright}}

=== high priority tasks ===

* main webpage redesign (www.sugarlabs.org)
* new css/template for planet.sugarlabs.org ... or an entirely new rss aggregator

=== wished services ===

* try out [http://groupserver.org/ groupserver] and, if it works, migrate our mailing lists to it
* try out Question/Answer Plattform [http://shapado.com/ shapado]
* change google analytics to [http://piwik.org/ piwik]

[[Category:TODO]]

Internet Relay Chat

2011-03-16T18:42:10Z

Dogi: /* irc.oftc.net channels */

<noinclude>[[Category:Contact]][[Category:Resource]]
</noinclude>== IRC, [[Internet Relay Chat]] ==
Most Sugar Labs chat takes place on IRC (see [[wikipedia:IRC|Internet Relay Chat]]).
* The [[Activities/IRC|'''IRC activity''']] allows access to IRC from within the Sugar environment.
* You can use a computer-based client to log in to IRC, such as [http://www.pidgin.im/ Pidgin] or [[wikipedia:X-Chat|X-Chat]]. This link should work for such clients: irc://irc.freenode.net#sugar
* Or, use a browser add-on (like [http://addons.mozilla.org/en-US/firefox/addon/16 ChatZilla] for the FireFox web browser, where the above link will also work).
* Easiest, might be this web browser-based service provided by freenode through qwebirc to [http://chat.sugarlabs.org chat on #sugar now].

IRC is mainly designed for group communication in discussion 'channels', but allows for personal chat and data transfer as well.

The Sugar Labs Community uses a series of ''channels'' in the '''<tt>irc.freenode.net</tt>''' network.

==== irc.freenode.net channels ====


{|
| colspan=2 style="background:lightyellow; border:1px solid black;" | '''General:'''
|- valign="top"
|<tt>[http://webchat.freenode.net/?randomnick=1&channels=olpc-help&prompt=1 #olpc-help] or irc://irc.freenode.net#olpc-help</tt> || Community help. If you need help using an XO or with Sugar, and you haven't asked anywhere else: try here first.
|- valign="top"
|<tt>[http://webchat.freenode.net/?randomnick=1&channels=sugar-newbies&prompt=1 #sugar-newbies] or irc://irc.freenode.net#sugar-newbies</tt> || New developer help. If you're starting to develop in Sugar, you can ask here and help contribute to the new developers manual and FAQ. The [http://jita.sugarlabs.org/freenode/%23sugar-newbies/index.html channel is logged] and its history searchable.
|-
|- valign="top"
|<tt>[http://webchat.freenode.net/?randomnick=1&channels=sugar&prompt=1 #sugar]</tt> or <tt>irc://irc.freenode.net#sugar</tt> || For day-to-day [[What is Sugar? | Sugar]] development—a casual, friendly place where Sugar developers collaborate.
|- valign="top"
| <tt>[http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1 #sugar-meeting]</tt> or <tt>irc://irc.freenode.net#sugar-meeting</tt>|| A channel for scheduled Sugar Labs meetings. See the [[Sugar Labs/Events | Sugar Labs event calendar]].
|- valign="top"
| <tt>[http://webchat.freenode.net/?randomnick=1&channels=fedora-olpc&prompt=1 #fedora-olpc]</tt> or <tt>irc://irc.freenode.net#fedora-olpc</tt> || A channel for the Fedora development project for OLPC XOs and a Sugar distribution. See the [http://fedoraproject.org/wiki/OLPC project page].

|}

==== irc.oftc.net channels ====
{|
|-
| colspan=2 style="background:lightyellow; border:1px solid black;" | '''General:'''
|- valign="top"
|- valign="top"
| <tt>[http://embed.mibbit.com/?server=irc.oftc.net&channel=%23schoolserver&noServerTab=false #schoolserver]</tt> or <tt>irc://irc.oftc.net#schoolserver</tt> || The meeting channel for the XS, the '''X'''O school '''S'''erver. (Not active in September 2009.)
|- valign="top"
| <tt>[http://embed.mibbit.com/?server=irc.oftc.net&channel=%23treehouse&noServerTab=false #treehouse]</tt> or <tt>irc://irc.oftc.net#treehouse</tt> || The meeting channel for the [http://monitoring.treehouse.su/munin/DOMs/comparison-day.html#virtual%20machines Treehouse] - Hosting
|}

* See also [[OLPC:Communication channels]].

=== How to use IRC channels ===
* A web-based chat for freenode.net channels is [http://webchat.freenode.net qwebirc], with nickname: (whatever you like), and channel: #sugar (or whatever other channel you're trying to get into).
* A web-based chat for other channels is [http://www.mibbit.com Mibbit], with nickname: (whatever you like), server: irc.oftc.net, and channel: #schoolserver (or whatever other channel you're trying to get into). It also includes an in-line '''translation''' service that is helpful when other languages are used. (Connections via mibbit are no longer supported on freenode. You may wish to consider using http://webchat.freenode.net instead. Further information over at http://bit.ly/19JILF.)
* Some helpful resources are [http://www.mirc.com/irc.html here], and [http://www.irchelp.org/irchelp/irctutorial.html this tutorial], which also includes basic commands.
* Learn about IRC etiquette. Try [http://www.ircbeginner.com/ircinfo/etiquette.html here], [http://www.livinginternet.com/r/ru_chatq.htm here], or [http://www.wxwidgets.org/wiki/index.php/IRC_Etiquette here].
* For IRC under sugar, install the latest '''[[Activities/IRC|Sugar IRC activity]]'''.
* In Pidgin you can configure IRC and then Add a Chat to your Buddy list. Select the IRC channel from the drop-down menu, and enter the name of the channel. You can set Pidgin to open channels automatically whenever it starts up.
* In a traditional IRC client, you join a channel with the /join command, for example, enter <code>/join #sugar</code> in the input box.
* Connect to one of the above channels, and say hello. You will see a list of the handles (on-line names) of the people in the channel, and the conversation will appear in a scrolling window. Type your message in the command entry area, and press return.
* Instructions for using the meeting log robot are [[OLPC:User:Dogi/meeting | here]].

Internet Relay Chat

2011-03-16T18:39:07Z

Dogi: /* irc.oftc.net channels */

<noinclude>[[Category:Contact]][[Category:Resource]]
</noinclude>== IRC, [[Internet Relay Chat]] ==
Most Sugar Labs chat takes place on IRC (see [[wikipedia:IRC|Internet Relay Chat]]).
* The [[Activities/IRC|'''IRC activity''']] allows access to IRC from within the Sugar environment.
* You can use a computer-based client to log in to IRC, such as [http://www.pidgin.im/ Pidgin] or [[wikipedia:X-Chat|X-Chat]]. This link should work for such clients: irc://irc.freenode.net#sugar
* Or, use a browser add-on (like [http://addons.mozilla.org/en-US/firefox/addon/16 ChatZilla] for the FireFox web browser, where the above link will also work).
* Easiest, might be this web browser-based service provided by freenode through qwebirc to [http://chat.sugarlabs.org chat on #sugar now].

IRC is mainly designed for group communication in discussion 'channels', but allows for personal chat and data transfer as well.

The Sugar Labs Community uses a series of ''channels'' in the '''<tt>irc.freenode.net</tt>''' network.

==== irc.freenode.net channels ====


{|
| colspan=2 style="background:lightyellow; border:1px solid black;" | '''General:'''
|- valign="top"
|<tt>[http://webchat.freenode.net/?randomnick=1&channels=olpc-help&prompt=1 #olpc-help] or irc://irc.freenode.net#olpc-help</tt> || Community help. If you need help using an XO or with Sugar, and you haven't asked anywhere else: try here first.
|- valign="top"
|<tt>[http://webchat.freenode.net/?randomnick=1&channels=sugar-newbies&prompt=1 #sugar-newbies] or irc://irc.freenode.net#sugar-newbies</tt> || New developer help. If you're starting to develop in Sugar, you can ask here and help contribute to the new developers manual and FAQ. The [http://jita.sugarlabs.org/freenode/%23sugar-newbies/index.html channel is logged] and its history searchable.
|-
|- valign="top"
|<tt>[http://webchat.freenode.net/?randomnick=1&channels=sugar&prompt=1 #sugar]</tt> or <tt>irc://irc.freenode.net#sugar</tt> || For day-to-day [[What is Sugar? | Sugar]] development—a casual, friendly place where Sugar developers collaborate.
|- valign="top"
| <tt>[http://webchat.freenode.net/?randomnick=1&channels=sugar-meeting&prompt=1 #sugar-meeting]</tt> or <tt>irc://irc.freenode.net#sugar-meeting</tt>|| A channel for scheduled Sugar Labs meetings. See the [[Sugar Labs/Events | Sugar Labs event calendar]].
|- valign="top"
| <tt>[http://webchat.freenode.net/?randomnick=1&channels=fedora-olpc&prompt=1 #fedora-olpc]</tt> or <tt>irc://irc.freenode.net#fedora-olpc</tt> || A channel for the Fedora development project for OLPC XOs and a Sugar distribution. See the [http://fedoraproject.org/wiki/OLPC project page].

|}

==== irc.oftc.net channels ====
{|
|-
| colspan=2 style="background:lightyellow; border:1px solid black;" | '''General:'''
|- valign="top"
|- valign="top"
| <tt>[http://embed.mibbit.com/?server=irc.oftc.net&channel=%23schoolserver&noServerTab=false #schoolserver]</tt> or <tt>irc://irc.oftc.net#schoolserver</tt> || The meeting channel for the XS, the '''X'''O school '''S'''erver. (Not active in September 2009.)
|- valign="top"
| <tt>[http://embed.mibbit.com/?server=irc.oftc.net&channel=%23treehouse&noServerTab=false #treehouse]</tt> or <tt>irc://irc.oftc.net#treehouse</tt> || The meeting channel for the [http://monitoring.treehouse.su/munin/ Treehouse] - Hosting
|}

* See also [[OLPC:Communication channels]].

=== How to use IRC channels ===
* A web-based chat for freenode.net channels is [http://webchat.freenode.net qwebirc], with nickname: (whatever you like), and channel: #sugar (or whatever other channel you're trying to get into).
* A web-based chat for other channels is [http://www.mibbit.com Mibbit], with nickname: (whatever you like), server: irc.oftc.net, and channel: #schoolserver (or whatever other channel you're trying to get into). It also includes an in-line '''translation''' service that is helpful when other languages are used. (Connections via mibbit are no longer supported on freenode. You may wish to consider using http://webchat.freenode.net instead. Further information over at http://bit.ly/19JILF.)
* Some helpful resources are [http://www.mirc.com/irc.html here], and [http://www.irchelp.org/irchelp/irctutorial.html this tutorial], which also includes basic commands.
* Learn about IRC etiquette. Try [http://www.ircbeginner.com/ircinfo/etiquette.html here], [http://www.livinginternet.com/r/ru_chatq.htm here], or [http://www.wxwidgets.org/wiki/index.php/IRC_Etiquette here].
* For IRC under sugar, install the latest '''[[Activities/IRC|Sugar IRC activity]]'''.
* In Pidgin you can configure IRC and then Add a Chat to your Buddy list. Select the IRC channel from the drop-down menu, and enter the name of the channel. You can set Pidgin to open channels automatically whenever it starts up.
* In a traditional IRC client, you join a channel with the /join command, for example, enter <code>/join #sugar</code> in the input box.
* Connect to one of the above channels, and say hello. You will see a list of the handles (on-line names) of the people in the channel, and the conversation will appear in a scrolling window. Type your message in the command entry area, and press return.
* Instructions for using the meeting log robot are [[OLPC:User:Dogi/meeting | here]].

Sysadmin/Add virtual machine

2011-03-10T16:26:51Z

Dogi:

=== Create new VM on [[Machine/treehouse]] ===

This procedure creates a clone of the [[Sysadmin/Template virtual machine]].

virsh vol-create-as treehouse FOOBAR-root 10G
virt-clone --prompt -o template-lucid --file=/dev/treehouse/FOOBAR-root -n FOOBAR
virsh start --console FOOBAR

* Add A and AAAA records for the new host in the sugarlabs.org zone file (See [[Sysadmin/Nameservers]]).

* Now login as root from the console (there should be no password)

* setup both IPv4 and IPv6 addresses

vi /etc/network/interfaces

* change machine fqdn

sed -i -e s/template-lucid/FOOBAR/ /etc/hostname /etc/postfix/main.cf

* fix /etc/hosts

vim /etc/hosts

* activate new IP and hostname

/etc/init.d/networking restart

* install latest security/stability updates

aptitude update
aptitude full-upgrade

* generate host keys and a key for root

ssh-keygen -N "" -f /etc/ssh/ssh_host_rsa_key -t rsa
ssh-keygen -N "" -f /etc/ssh/ssh_host_dsa_key -t dsa
ssh-keygen -N "" -f /root/.ssh/id_rsa -t rsa

* Install <code>/root/.ssh/id_rsa.pub</code> key on <code>sugarbackup@backup.sugarlabs.org</code>

* Setup backups

vi /etc/system-full-backup.conf

* Log in for the first time on backup server to accept ssh fingerprint

ssh sugarbackup@backup.sugarlabs.org

* Move daily, weekly, monthly cronjobs to a unique timeslot to avoid cpu/net storms

vi /etc/crontab

* The most important thing: come up with a funny quip for this machine

vi /etc/motd.tail

* Taa--daah!

reboot

* Add the machine to <code>/etc/munin/munin.conf</code> on [[Machine/sunjammer]] for monitoring.

[housetree.sugarlabs.org]
address housetree.sugarlabs.org

See also: [[Sysadmin/Delete virtual machine]], [[Sysadmin/Migrate_virtual_machine]].

Machine/serendipity

2011-02-23T13:39:49Z

Dogi: Created page with "{{TOCright}} == Description == Short descrition of machine purpose == OS == Distro and version. == Services == * TEMPLATE_SERVICE == Hardware == ..."

Machine/dextrose

2011-02-23T13:34:21Z

Dogi: Created page with "{{TOCright}} == Description == Short descrition of machine purpose == OS == Distro and version. == Services == * TEMPLATE_SERVICE == Hardware == ..."

IT

2011-02-15T17:48:40Z

Dogi: Redirected page to Infrastructure Team

#redirect [[Infrastructure_Team]]

User:Dogi

2011-02-08T23:38:05Z

Dogi:

[http://wiki.laptop.org/go/User:Dogi my page on laptop.org]

{{Special:WhatLinksHere/User:Dogi}}

[http://dextra.media.mit.edu:6080/vnc.html?host=dextra.media.mit.edu&port=6080 try sugarbush]

Downloads

2011-02-03T19:07:13Z

Dogi:

<noinclude>{{ Translations | [[Downloads|english]] | [[Downloads/lang-es|español]] | [[Downloads/lang-fr|français]] | [[Downloads/lang-no|norsk]] }}__NOEDITSECTION__</noinclude>
{{:Downloads/Landing_page}}
__NOTOC__

 
==Are you new to Sugar?==

The easiest way to get started is to use [[Sugar on a Stick]]. Basic instructions are found below. A more detailed [http://download.sugarlabs.org/soas/docs/creation-kit/ Sugar-on-a-Stick Creation Guide] is also available. (If you already use GNU/Linux, you may want to install the [[#Do_you_use_GNU.2FLinux.3F|Sugar packages]] available from your distro.)
----
=== MS Windows ===

{|
|-
|width="160px" valign="top"|[[File:Windows.gif|left|link=Sugar on a Stick/Windows]]
 
[[File:Download Mirabell.png|left|link=http://spins.fedoraproject.org/soas/#downloads]]
[[File:USB flash drive.jpg|left|156px|link=http://spins.fedoraproject.org/soas/#downloads]]
|valign=top|
# '''Prepare''': [http://fedorahosted.org/liveusb-creator/#Download Download] the Fedora Live USB Creator from [http://fedorahosted.org/liveusb-creator/#Download FedoraHosted] 
# '''Download''': [http://spins.fedoraproject.org/soas/#downloads Download] the Sugar-on-a-Stick iso. 
# '''Load''': Insert a USB flash drive (or SD Card) with 1 GB or more of free space into your computer and launch Fedora Live USB Creator to create a Sugar-on-a-Stick bootable image. '''Note''': Be sure to set the ''persistent storage'' slider to a non-zero value. 
# '''Boot''': Insert the USB stick into a USB port on your computer. Set the option to "boot from USB" in your computer's <abbr title="Basic Input/Output System">BIOS</abbr> setup, and then start up the computer.
|}

Detailed [[Sugar on a Stick/Windows|installation instructions for Windows]] and [[Sugar on a Stick/Boot|booting instructions]] are available. There is also a [[Sugar on a Stick/Explore|guide to exploring Sugar on a Stick]].
----
=== GNU/Linux ===
GNU/Linux users may want to install the [[#Do_you_use_GNU.2FLinux.3F|Sugar packages]] on their favorite distro.

{|
|-
|width="160px"|[[File:Gnulinux.png|link=Sugar on a Stick/Linux]]
 
[[File:Download Mirabell.png|left|link=http://spins.fedoraproject.org/soas/#downloads]]
[[File:USB flash drive.jpg|156px|link=http://spins.fedoraproject.org/soas/#downloads]]
|valign=top|
# '''Prepare''': Use this script http://bit.ly/livecd-iso-to-disk to create a bootable image. (Run {{Code|chmod +x livecd-iso-to-disk.sh}} after you download the script to make it executable.) 
# '''Download''': [http://spins.fedoraproject.org/soas/#downloads Download] the Sugar-on-a-Stick iso. 
# '''Load''': Execute, as the root user, in one command with arguments, the following:
#:{{Code|./livecd-iso-to-disk.sh --reset-mbr --overlay-size-mb 300 --home-size-mb 175 --delete-home --unencrypted-home /path/to/source.iso /dev/sd'''?'''1}}
#: where '{{Code|'''?'''}}' in the final parameter represents the target bootable device node, such as {{Code|sdb1}} or {{Code|sdc1}}, etc. 
# '''Boot''': Insert the USB stick into a USB port on your computer. Set the option to "boot from USB" in your computer's <abbr title="Basic Input/Output System">BIOS</abbr> setup, and then start up the computer.
|}

Detailed [[Sugar on a Stick/Linux|installation instructions for GNU/Linux]] and [[Sugar on a Stick/Boot|booting instructions]] are available. There is also a [[Sugar on a Stick/Explore|guide to exploring Sugar on a Stick]].
----
=== Apple Mac OS X ===
'''DRAFT''': These instructions are incomplete. Please help with testing and documentation. In the meantime, we recommend the '''[[#Virtual Machines on all platforms|Virtual Machines instructions]]''' below.
{|
|-
|width="160px" valign="top"|[[File:Apple.gif|link=Sugar_on_a_Stick/Mac]]
 
[[File:Download Mirabell.png|left|link=http://spins.fedoraproject.org/soas/#downloads]]
[[File:USB flash drive.jpg|156px|link=http://spins.fedoraproject.org/soas/#downloads]]
|valign=top|
# '''Prepare''': These instructions are only for '''64-bit''' processor machines. (To identify the processor type, choose Apple menu > About This Mac. A small window will appear titled ''About This Mac''. The processor type is displayed in this window. Sugar on a Stick is for the Intel processor only.) 
# '''Download''': [http://spins.fedoraproject.org/soas/#downloads Download] the Sugar-on-a-Stick iso. Be sure to download a '''64-bit''' image. 
# '''Load''': [[File:question.png|link=|middle]] '''Help: Does someone have a simple way to load a Live USB on a Mac?''' Here is a simple way to recognize a bootable USB on a Mac. Go to rEFIt (http://refit.sourceforge.net/) and make a bootable cd. There is no need to install rEFIt on your mac. In fact installing rEFIt may make it impossible to upgrade the Mac OS to a newer version later on (personal experience, I had to do a clean install). Put the rEFIt CD in and hold the option key after turning the computer on. The Mac will recognize the CD because it uses EFI and then the CD will recognize the bootable USB. 
:::'''[http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Building_a_bootable_USB Building and Booting_a_live_USB on a Mac]'''
# '''Boot''': Insert the USB stick into a USB port on your computer. '''Is this correct?''': During the startup sound, press and hold the '''c''' key. If the Apple logo appears, Sugar is not booting. Restart and try again.
#* the '''c''' key must be pressed during the startup sound and you must continue to hold it down.
#* you may release the '''c''' key once the Sugar logo appears.
* Have a MAC Book Air? See
: '''NEW''' [http://wiki.sugarlabs.org/go/Talk:Downloads#Bootable_DVD_of_f14_for_MacBook_Air Bootable_DVD_of_f14_for_MacBook_Air]
: '''NEW''' [http://wiki.sugarlabs.org/go/Talk:Downloads#Bootable_CD_of_Trisquel_4.5_for_MacBook_Air Bootable_CD_of_Trisquel_4.5_for_MacBook_Air]
: [http://wiki.sugarlabs.org/go/Mac_OS_X-Boot_USB_with_Virtualbox#Running_Soas_files_on_a_2nd_USB_in_Virtualbox_3.2_installed_on_the_MacBook_Air Running_Soas_files_on_a_2nd_USB_in_Virtualbox_3.2_installed_on_the_MacBook_Air]
: [http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Building_a_bootable_USB Building_a_bootable_USB]
: [http://lists.sugarlabs.org/archive/iaep/2010-November/012019.html Soas-v4 on a MacBook Air]
: [http://wiki.sugarlabs.org/go/Mac_OS_X-Boot_USB_with_Virtualbox#Mac_OSX-F14-desktop_with_Virtualbox_Boot_USB Mac_OSX-F14-desktop_with_Virtualbox_Boot_4GB USB]
:: Opens a 2nd USB with a Soas-v3 virtual appliance. Note that the 2nd USB can be exchanged for use by another student, who can eject his USB and keep it till his next session.
|}

Alternative [[Sugar on a Stick/Mac|installation instructions for Mac OS X]]. Also, [[Sugar_on_a_Stick/Blueberry#For_Mac_OS_X_Users|these older installation instructions]] and [[Sugar on a Stick/Boot|booting instructions]] may be consulted. There is also a [[Sugar on a Stick/Explore|guide to exploring Sugar on a Stick]].
----
=== Advanced users ===

{|
|-
|width="174px"|[[File:Sugar Creation Kit.png|link=Sugar Creation Kit]]
|valign=top|
* '''Explore''' the [[Sugar Creation Kit]]

* '''Try''' [[Sugar_on_a_Stick/Installation/Variations|customizing]] Sugar on a Stick;

* '''Read''' the [http://download.sugarlabs.org/soas/docs/customization-guide/ detailed Customization Guide]; and

* '''Read''' additional instructions for using [[VirtualBox]] and other virtual machines.
|}

 
==Do you have an OLPC XO?==

{|
|-
|width="174px"|[[File:OLPCXO.png|middle|link=Dextrose]]
|valign=top|
* '''Upgrade''' to the latest ''[[olpc:OS_images#Stable_builds|stable OS release]]'' from OLPC (includes Sugar 0.84 and GNOME 2.26)

* '''Upgrade''' to ''[[Dextrose |Dextrose Sugar 0.88 with Fedora 11 and GNOME]]'' (requires a [[olpc:Activation_and_developer_keys|developer key]])

* '''Load ''' another one of the [[OLPC:OS images]]

* '''Test''' Sugar 0.90 on Fedora 14 [[OLPC:F14 for XO]]
*: See this [http://www.mail-archive.com/devel@lists.laptop.org/msg25313.html discussion thread].

* '''Experiment''' with [[Sugar_on_a_Stick/Installation/OLPC|Updating XOs]] to the latest ''Sugar on a Stick'' release.
|}

 

==Do you use GNU/Linux?==

{|
|-
|width="178px" valign="top"|Select your favorite distribution [[File:Gnulinux.png|link=Community/Distributions]]||
{|
|-
|[[Image:Fedora-small.jpg|link=Community/Distributions/Fedora]] [[Community/Distributions/Fedora|Fedora]]
|-
|[[Image:Debian-small.jpg|link=Community/Distributions/Debian]] [[Community/Distributions/Debian|Debian]]
|[[File:Trisquel_icon.png|link=Community/Distributions/Trisquel]] [[Community/Distributions/Trisquel|Trisquel]]
|[[Image:Ubuntu-small.jpg|link=Community/Distributions/Ubuntu]] [[Community/Distributions/Ubuntu|Ubuntu]]
|align="center"|[[Image:Ubuntu-small.jpg|link=http://wiki.ubuntu.com/Sugar]] [http://wiki.ubuntu.com/Sugar '''U'''buntu '''S'''ugar '''R'''emix]
|-
|align="center"|[[Image:Mandriva-small.png|link=Community/Distributions/Mandriva]] [[Community/Distributions/Mandriva|Mandriva]]
|align="center"|[[Image:Caixa_M%C3%A1gica-small.jpg|link=Community/Distributions/Magalhães]] [[Community/Distributions/Magalhães|Caixa Mágica]]
|-
|align="center"|[[Image:Suse-small.jpg|link=Community/Distributions/OpenSUSE]] [[Community/Distributions/OpenSUSE| openSUSE]]
|[[Image:Suse-small.jpg|link=http://en.opensuse.org/Sugar]] [http://en.opensuse.org/Sugar openSUSE]||
|-
|align="center"|[[Image:Arch-logo.png|link=http://wiki.archlinux.org/index.php/Sugar]] [http://wiki.archlinux.org/index.php/Sugar Archlinux]||
|-
|[[Image:Debian-small.jpg|link=Community/Distributions/Linux_Mint_Debian]] [[Community/Distributions/Linux_Mint_Debian|Linux_Mint_Debian]]
|-
|[[Image:Altlinux-small.png|link=Community/Distributions/ALTLinux]] [[Community/Distributions/ALTLinux|AltLinux]]
|}
|-
|width="180px" valign="top"|Or try a Live USB version of Sugar
|[[File:Soas-mango-lassi.png|middle|200px|link=http://spins.fedoraproject.org/soas/#downloads]], Mango Lassi with Sugar 0.90.3 and Fedora 14 (Laughlin) or, for brave pioneers, [[Sugar_on_a_Stick/Beta | v5 alpha with Sugar 0.90.3 and Fedora 15 (Lovelock)]] [[File:Trisquel_icon.png|link=Trisquel On A Sugar Toast]] Trisquel on a Sugar Toast (Trisquel 3.0 ''Dwyn'') [[File:Suse-small.jpg|link=http://en.opensuse.org/Education/Live|Education/Live]] OpenSuse Live USB
|}

 
== Virtual Machines on all platforms ==

{|
|-
|width="160px"|[[File:VirtualBox.png|100px|left|link=http://www.virtualbox.org/wiki/Downloads]]
|valign=top|
* '''Appliance of Sugar on a Stick v4-Mango Lassi'''
:Note: This appliance has a maximum 1024x768 screen size as VirtualBox extensions were compiled into the kernel.
:'''Sugar 0.90.1

:user=sugar
:password=sugaruser
: '''root=sugarroot'''
:How Built:
: 8-GB VirtualBox hard disc
:English and English keyboard
:USA-Los Angeles (Pacific timezone)
:'''download and import 2 files:'''
http://download.sugarlabs.org/images/VirtualBox/Fedora-14-i686-Live-SoaS-2.ovf 12K
http://download.sugarlabs.org/images/VirtualBox/Fedora-14-i686-Live-SoaS-2-disk1.vmdk 606M

;Note 1:had to modify the .ovf to get the image running on a X60 with ubuntu maverick and virtualbox 3.1.6
http://people.sugarlabs.org/dogi/virtualbox/Fedora-14-i686-Live-SoaS-2.1.ovf 12K

* '''Appliance of Sugar on a Stick v3-Mirabelle'''
::Note: This appliance has a maximum 800x640 screensize available as VirtualBox extensions were NOT compiled into the kernel.

::firstboot has not yet run; so a new user name and password will be set for the gdm login on start up for the first time

:How Built:
: '''root=sugarroot'''
: 8-GB VirtualBox hard disc
:English and English keyboard
:USA-Los Angeles (Pacific timezone)
:'''download and import 2 files:'''
http://download.sugarlabs.org/images/VirtualBox/Fedora-13-i686-Live-SoaS-sugaruser.vmdk 533M
http://download.sugarlabs.org/images/VirtualBox/Fedora-13-i686-Live-SoaS-sugaruser.ovf 12K

;Note 1:Use the latest version of Oracle VM VirtualBox (3.2_10.8-64453 or later). Some appliances have multiple hard disc controllers and the earlier Sun VirtualBox 3.1 version does not support them.
;Note 2: All appliances were built on a MacBook Air with Oracle VM VirtualBox (3.2.10-r66523) then tested on a Ubuntu installation on an Acer Aspire One Netbook imported into VirtualBox (3.2.10 r66523)
;Note 3:Set ControlPanel/Frame "Edge" slider to far left for easier access to sugar-frame features

:(Note that on some browsers on Mac OS X, the file extensions are reset upon download. You may have to modify them to match those shown above.) 

:If you run into problems, you may want to consult the [[Talk:VirtualBox]] page for help.
|-
|colspan="2"|'''[[Emulator_image_files#Other_virtual_machines|More Virtual Appliances]]''' Sugar included in other linux operating systems, and older versions.
|}

 
==Are you a developer?==

{|
|-
|width="174px" valign=top|[[File:Gear.png|link=Supported_systems]]
|Learn how to get setup on the [[Supported systems]] page.

Some additional references you may find useful:
* [[Development Team/Jhbuild | jhbuild]]
* [[Platform_Team/Guide/Core_development|sweet build]]
* [http://git.sugarlabs.org Gitorious source code repository]
* [[Emulator image files|Virtual machine or emulator image files]]
* Adding Sugar to your [[Supported systems|favorite distro...]]
|}

 
==Are you preparing a deployment without Internet access?==

{|
|-
|style="width: 180px"|[[File:Sugar Creation Kit.png|left|link=Sugar Creation Kit]]
|valign="top"|See [[Sugar Creation Kit]]
|}

 

==Are you looking for Sugar Activities?==

{|
|-
|width="170px" valign="top"|Visit the [http://activities.sugarlabs.org Sugar Activity Library]||<imagemap>
File:Sugarlabs_mainpage_02.png
rect 14 14 38 47 [[sal:4076|Calculate]]
rect 74 15 107 44 [[sal:4069|Chat]]
rect 137 16 171 43 [[sal:4086|Implode]]
rect 201 14 238 46 [[sal:4264|Distance]]
rect 265 12 298 47 [[sal:4030|Etoys]]
rect 11 79 41 108 [[sal:4034|Moon]]
rect 74 78 106 110 [[sal:4082|Paint]]
rect 140 78 170 109 [[sal:4041|Pippy]]
rect 201 80 235 108 [[sal:4028|Read]]
rect 266 82 298 107 [[sal:4081|Record]]
rect 11 143 41 172 [[sal:4062|TamTam Synth Lab]]
rect 75 146 105 169 [[sal:4043|Terminal]]
rect 142 140 166 173 [[sal:4027|Turtle Blocks]]
rect 201 144 235 171 [[olpc:WikiBrowse|WikiBrowse]]
rect 269 142 299 173 [[sal:4201|Write]]
default [http://activities.sugarlabs.org Sugar Activity Library]
desc none
</imagemap>
|}

Downloads

2011-02-03T19:05:13Z

Dogi:

<noinclude>{{ Translations | [[Downloads|english]] | [[Downloads/lang-es|español]] | [[Downloads/lang-fr|français]] | [[Downloads/lang-no|norsk]] }}__NOEDITSECTION__</noinclude>
{{:Downloads/Landing_page}}
__NOTOC__

 
==Are you new to Sugar?==

The easiest way to get started is to use [[Sugar on a Stick]]. Basic instructions are found below. A more detailed [http://download.sugarlabs.org/soas/docs/creation-kit/ Sugar-on-a-Stick Creation Guide] is also available. (If you already use GNU/Linux, you may want to install the [[#Do_you_use_GNU.2FLinux.3F|Sugar packages]] available from your distro.)
----
=== MS Windows ===

{|
|-
|width="160px" valign="top"|[[File:Windows.gif|left|link=Sugar on a Stick/Windows]]
 
[[File:Download Mirabell.png|left|link=http://spins.fedoraproject.org/soas/#downloads]]
[[File:USB flash drive.jpg|left|156px|link=http://spins.fedoraproject.org/soas/#downloads]]
|valign=top|
# '''Prepare''': [http://fedorahosted.org/liveusb-creator/#Download Download] the Fedora Live USB Creator from [http://fedorahosted.org/liveusb-creator/#Download FedoraHosted] 
# '''Download''': [http://spins.fedoraproject.org/soas/#downloads Download] the Sugar-on-a-Stick iso. 
# '''Load''': Insert a USB flash drive (or SD Card) with 1 GB or more of free space into your computer and launch Fedora Live USB Creator to create a Sugar-on-a-Stick bootable image. '''Note''': Be sure to set the ''persistent storage'' slider to a non-zero value. 
# '''Boot''': Insert the USB stick into a USB port on your computer. Set the option to "boot from USB" in your computer's <abbr title="Basic Input/Output System">BIOS</abbr> setup, and then start up the computer.
|}

Detailed [[Sugar on a Stick/Windows|installation instructions for Windows]] and [[Sugar on a Stick/Boot|booting instructions]] are available. There is also a [[Sugar on a Stick/Explore|guide to exploring Sugar on a Stick]].
----
=== GNU/Linux ===
GNU/Linux users may want to install the [[#Do_you_use_GNU.2FLinux.3F|Sugar packages]] on their favorite distro.

{|
|-
|width="160px"|[[File:Gnulinux.png|link=Sugar on a Stick/Linux]]
 
[[File:Download Mirabell.png|left|link=http://spins.fedoraproject.org/soas/#downloads]]
[[File:USB flash drive.jpg|156px|link=http://spins.fedoraproject.org/soas/#downloads]]
|valign=top|
# '''Prepare''': Use this script http://bit.ly/livecd-iso-to-disk to create a bootable image. (Run {{Code|chmod +x livecd-iso-to-disk.sh}} after you download the script to make it executable.) 
# '''Download''': [http://spins.fedoraproject.org/soas/#downloads Download] the Sugar-on-a-Stick iso. 
# '''Load''': Execute, as the root user, in one command with arguments, the following:
#:{{Code|./livecd-iso-to-disk.sh --reset-mbr --overlay-size-mb 300 --home-size-mb 175 --delete-home --unencrypted-home /path/to/source.iso /dev/sd'''?'''1}}
#: where '{{Code|'''?'''}}' in the final parameter represents the target bootable device node, such as {{Code|sdb1}} or {{Code|sdc1}}, etc. 
# '''Boot''': Insert the USB stick into a USB port on your computer. Set the option to "boot from USB" in your computer's <abbr title="Basic Input/Output System">BIOS</abbr> setup, and then start up the computer.
|}

Detailed [[Sugar on a Stick/Linux|installation instructions for GNU/Linux]] and [[Sugar on a Stick/Boot|booting instructions]] are available. There is also a [[Sugar on a Stick/Explore|guide to exploring Sugar on a Stick]].
----
=== Apple Mac OS X ===
'''DRAFT''': These instructions are incomplete. Please help with testing and documentation. In the meantime, we recommend the '''[[#Virtual Machines on all platforms|Virtual Machines instructions]]''' below.
{|
|-
|width="160px" valign="top"|[[File:Apple.gif|link=Sugar_on_a_Stick/Mac]]
 
[[File:Download Mirabell.png|left|link=http://spins.fedoraproject.org/soas/#downloads]]
[[File:USB flash drive.jpg|156px|link=http://spins.fedoraproject.org/soas/#downloads]]
|valign=top|
# '''Prepare''': These instructions are only for '''64-bit''' processor machines. (To identify the processor type, choose Apple menu > About This Mac. A small window will appear titled ''About This Mac''. The processor type is displayed in this window. Sugar on a Stick is for the Intel processor only.) 
# '''Download''': [http://spins.fedoraproject.org/soas/#downloads Download] the Sugar-on-a-Stick iso. Be sure to download a '''64-bit''' image. 
# '''Load''': [[File:question.png|link=|middle]] '''Help: Does someone have a simple way to load a Live USB on a Mac?''' Here is a simple way to recognize a bootable USB on a Mac. Go to rEFIt (http://refit.sourceforge.net/) and make a bootable cd. There is no need to install rEFIt on your mac. In fact installing rEFIt may make it impossible to upgrade the Mac OS to a newer version later on (personal experience, I had to do a clean install). Put the rEFIt CD in and hold the option key after turning the computer on. The Mac will recognize the CD because it uses EFI and then the CD will recognize the bootable USB. 
:::'''[http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Building_a_bootable_USB Building and Booting_a_live_USB on a Mac]'''
# '''Boot''': Insert the USB stick into a USB port on your computer. '''Is this correct?''': During the startup sound, press and hold the '''c''' key. If the Apple logo appears, Sugar is not booting. Restart and try again.
#* the '''c''' key must be pressed during the startup sound and you must continue to hold it down.
#* you may release the '''c''' key once the Sugar logo appears.
* Have a MAC Book Air? See
: '''NEW''' [http://wiki.sugarlabs.org/go/Talk:Downloads#Bootable_DVD_of_f14_for_MacBook_Air Bootable_DVD_of_f14_for_MacBook_Air]
: '''NEW''' [http://wiki.sugarlabs.org/go/Talk:Downloads#Bootable_CD_of_Trisquel_4.5_for_MacBook_Air Bootable_CD_of_Trisquel_4.5_for_MacBook_Air]
: [http://wiki.sugarlabs.org/go/Mac_OS_X-Boot_USB_with_Virtualbox#Running_Soas_files_on_a_2nd_USB_in_Virtualbox_3.2_installed_on_the_MacBook_Air Running_Soas_files_on_a_2nd_USB_in_Virtualbox_3.2_installed_on_the_MacBook_Air]
: [http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Building_a_bootable_USB Building_a_bootable_USB]
: [http://lists.sugarlabs.org/archive/iaep/2010-November/012019.html Soas-v4 on a MacBook Air]
: [http://wiki.sugarlabs.org/go/Mac_OS_X-Boot_USB_with_Virtualbox#Mac_OSX-F14-desktop_with_Virtualbox_Boot_USB Mac_OSX-F14-desktop_with_Virtualbox_Boot_4GB USB]
:: Opens a 2nd USB with a Soas-v3 virtual appliance. Note that the 2nd USB can be exchanged for use by another student, who can eject his USB and keep it till his next session.
|}

Alternative [[Sugar on a Stick/Mac|installation instructions for Mac OS X]]. Also, [[Sugar_on_a_Stick/Blueberry#For_Mac_OS_X_Users|these older installation instructions]] and [[Sugar on a Stick/Boot|booting instructions]] may be consulted. There is also a [[Sugar on a Stick/Explore|guide to exploring Sugar on a Stick]].
----
=== Advanced users ===

{|
|-
|width="174px"|[[File:Sugar Creation Kit.png|link=Sugar Creation Kit]]
|valign=top|
* '''Explore''' the [[Sugar Creation Kit]]

* '''Try''' [[Sugar_on_a_Stick/Installation/Variations|customizing]] Sugar on a Stick;

* '''Read''' the [http://download.sugarlabs.org/soas/docs/customization-guide/ detailed Customization Guide]; and

* '''Read''' additional instructions for using [[VirtualBox]] and other virtual machines.
|}

 
==Do you have an OLPC XO?==

{|
|-
|width="174px"|[[File:OLPCXO.png|middle|link=Dextrose]]
|valign=top|
* '''Upgrade''' to the latest ''[[olpc:OS_images#Stable_builds|stable OS release]]'' from OLPC (includes Sugar 0.84 and GNOME 2.26)

* '''Upgrade''' to ''[[Dextrose |Dextrose Sugar 0.88 with Fedora 11 and GNOME]]'' (requires a [[olpc:Activation_and_developer_keys|developer key]])

* '''Load ''' another one of the [[OLPC:OS images]]

* '''Test''' Sugar 0.90 on Fedora 14 [[OLPC:F14 for XO]]
*: See this [http://www.mail-archive.com/devel@lists.laptop.org/msg25313.html discussion thread].

* '''Experiment''' with [[Sugar_on_a_Stick/Installation/OLPC|Updating XOs]] to the latest ''Sugar on a Stick'' release.
|}

 

==Do you use GNU/Linux?==

{|
|-
|width="178px" valign="top"|Select your favorite distribution [[File:Gnulinux.png|link=Community/Distributions]]||
{|
|-
|[[Image:Fedora-small.jpg|link=Community/Distributions/Fedora]] [[Community/Distributions/Fedora|Fedora]]
|-
|[[Image:Debian-small.jpg|link=Community/Distributions/Debian]] [[Community/Distributions/Debian|Debian]]
|[[File:Trisquel_icon.png|link=Community/Distributions/Trisquel]] [[Community/Distributions/Trisquel|Trisquel]]
|[[Image:Ubuntu-small.jpg|link=Community/Distributions/Ubuntu]] [[Community/Distributions/Ubuntu|Ubuntu]]
|align="center"|[[Image:Ubuntu-small.jpg|link=http://wiki.ubuntu.com/Sugar]] [http://wiki.ubuntu.com/Sugar '''U'''buntu '''S'''ugar '''R'''emix]
|-
|align="center"|[[Image:Mandriva-small.png|link=Community/Distributions/Mandriva]] [[Community/Distributions/Mandriva|Mandriva]]
|align="center"|[[Image:Caixa_M%C3%A1gica-small.jpg|link=Community/Distributions/Magalhães]] [[Community/Distributions/Magalhães|Caixa Mágica]]
|-
|align="center"|[[Image:Suse-small.jpg|link=Community/Distributions/OpenSUSE]] [[Community/Distributions/OpenSUSE| openSUSE]]
|[[Image:Suse-small.jpg|link=http://en.opensuse.org/Sugar]] [http://en.opensuse.org/Sugar openSUSE]||
|-
|align="center"|[[Image:Arch-logo.png|link=http://wiki.archlinux.org/index.php/Sugar]] [http://wiki.archlinux.org/index.php/Sugar Archlinux]||
|-
|[[Image:Debian-small.jpg|link=Community/Distributions/Linux_Mint_Debian]] [[Community/Distributions/Linux_Mint_Debian|Linux_Mint_Debian]]
|-
|[[Image:Altlinux-small.png|link=Community/Distributions/ALTLinux]] [[Community/Distributions/ALTLinux|AltLinux]]
|}
|-
|width="180px" valign="top"|Or try a Live USB version of Sugar
|[[File:Soas-mango-lassi.png|middle|200px|link=http://spins.fedoraproject.org/soas/#downloads]], Mango Lassi with Sugar 0.90.3 and Fedora 14 (Laughlin) or, for brave pioneers, [[Sugar_on_a_Stick/Beta | v5 alpha with Sugar 0.90.3 and Fedora 15 (Lovelock)]] [[File:Trisquel_icon.png|link=Trisquel On A Sugar Toast]] Trisquel on a Sugar Toast (Trisquel 3.0 ''Dwyn'') [[File:Suse-small.jpg|link=http://en.opensuse.org/Education/Live|Education/Live]] OpenSuse Live USB
|}

 
== Virtual Machines on all platforms ==

{|
|-
|width="160px"|[[File:VirtualBox.png|100px|left|link=http://www.virtualbox.org/wiki/Downloads]]
|valign=top|
* '''Appliance of Sugar on a Stick v4-Mango Lassi'''
:Note: This appliance has a maximum 1024x768 screen size as VirtualBox extensions were compiled into the kernel.
:'''Sugar 0.90.1

:user=sugar
:password=sugaruser
: '''root=sugarroot'''
:How Built:
: 8-GB VirtualBox hard disc
:English and English keyboard
:USA-Los Angeles (Pacific timezone)
:'''download and import 2 files:'''
http://download.sugarlabs.org/images/VirtualBox/Fedora-14-i686-Live-SoaS-2.ovf 12K
http://download.sugarlabs.org/images/VirtualBox/Fedora-14-i686-Live-SoaS-2-disk1.vmdk 606M

Note 1: had to modify the .ovf to get the image running on a X60 with ubuntu maverick and virtualbox 3.1.6
http://people.sugarlabs.org/dogi/virtualbox/Fedora-14-i686-Live-SoaS-2.1.ovf 12K

* '''Appliance of Sugar on a Stick v3-Mirabelle'''
::Note: This appliance has a maximum 800x640 screensize available as VirtualBox extensions were NOT compiled into the kernel.

::firstboot has not yet run; so a new user name and password will be set for the gdm login on start up for the first time

:How Built:
: '''root=sugarroot'''
: 8-GB VirtualBox hard disc
:English and English keyboard
:USA-Los Angeles (Pacific timezone)
:'''download and import 2 files:'''
http://download.sugarlabs.org/images/VirtualBox/Fedora-13-i686-Live-SoaS-sugaruser.vmdk 533M
http://download.sugarlabs.org/images/VirtualBox/Fedora-13-i686-Live-SoaS-sugaruser.ovf 12K

;Note 1:Use the latest version of Oracle VM VirtualBox (3.2_10.8-64453 or later). Some appliances have multiple hard disc controllers and the earlier Sun VirtualBox 3.1 version does not support them.
;Note 2: All appliances were built on a MacBook Air with Oracle VM VirtualBox (3.2.10-r66523) then tested on a Ubuntu installation on an Acer Aspire One Netbook imported into VirtualBox (3.2.10 r66523)
;Note 3:Set ControlPanel/Frame "Edge" slider to far left for easier access to sugar-frame features

:(Note that on some browsers on Mac OS X, the file extensions are reset upon download. You may have to modify them to match those shown above.) 

:If you run into problems, you may want to consult the [[Talk:VirtualBox]] page for help.
|-
|colspan="2"|'''[[Emulator_image_files#Other_virtual_machines|More Virtual Appliances]]''' Sugar included in other linux operating systems, and older versions.
|}

 
==Are you a developer?==

{|
|-
|width="174px" valign=top|[[File:Gear.png|link=Supported_systems]]
|Learn how to get setup on the [[Supported systems]] page.

Some additional references you may find useful:
* [[Development Team/Jhbuild | jhbuild]]
* [[Platform_Team/Guide/Core_development|sweet build]]
* [http://git.sugarlabs.org Gitorious source code repository]
* [[Emulator image files|Virtual machine or emulator image files]]
* Adding Sugar to your [[Supported systems|favorite distro...]]
|}

 
==Are you preparing a deployment without Internet access?==

{|
|-
|style="width: 180px"|[[File:Sugar Creation Kit.png|left|link=Sugar Creation Kit]]
|valign="top"|See [[Sugar Creation Kit]]
|}

 

==Are you looking for Sugar Activities?==

{|
|-
|width="170px" valign="top"|Visit the [http://activities.sugarlabs.org Sugar Activity Library]||<imagemap>
File:Sugarlabs_mainpage_02.png
rect 14 14 38 47 [[sal:4076|Calculate]]
rect 74 15 107 44 [[sal:4069|Chat]]
rect 137 16 171 43 [[sal:4086|Implode]]
rect 201 14 238 46 [[sal:4264|Distance]]
rect 265 12 298 47 [[sal:4030|Etoys]]
rect 11 79 41 108 [[sal:4034|Moon]]
rect 74 78 106 110 [[sal:4082|Paint]]
rect 140 78 170 109 [[sal:4041|Pippy]]
rect 201 80 235 108 [[sal:4028|Read]]
rect 266 82 298 107 [[sal:4081|Record]]
rect 11 143 41 172 [[sal:4062|TamTam Synth Lab]]
rect 75 146 105 169 [[sal:4043|Terminal]]
rect 142 140 166 173 [[sal:4027|Turtle Blocks]]
rect 201 144 235 171 [[olpc:WikiBrowse|WikiBrowse]]
rect 269 142 299 173 [[sal:4201|Write]]
default [http://activities.sugarlabs.org Sugar Activity Library]
desc none
</imagemap>
|}

Downloads

2011-01-27T22:45:22Z

Dogi:

<noinclude>{{ Translations | [[Downloads|english]] | [[Downloads/lang-es|español]] | [[Downloads/lang-fr|français]] | [[Downloads/lang-no|norsk]] }}__NOEDITSECTION__</noinclude>
{{:Downloads/Landing_page}}
__NOTOC__

 
==Are you new to Sugar?==

The easiest way to get started is to use [[Sugar on a Stick]]. Basic instructions are found below. A more detailed [http://download.sugarlabs.org/soas/docs/creation-kit/ Sugar-on-a-Stick Creation Guide] is also available. (If you already use GNU/Linux, you may want to install the [[#Do_you_use_GNU.2FLinux.3F|Sugar packages]] available from your distro.)
----
=== MS Windows ===

{|
|-
|width="160px" valign="top"|[[File:Windows.gif|left|link=Sugar on a Stick/Windows]]
 
[[File:Download Mirabell.png|left|link=http://spins.fedoraproject.org/soas/#downloads]]
[[File:USB flash drive.jpg|left|156px|link=http://spins.fedoraproject.org/soas/#downloads]]
|valign=top|
# '''Prepare''': [http://fedorahosted.org/liveusb-creator/#Download Download] the Fedora Live USB Creator from [http://fedorahosted.org/liveusb-creator/#Download FedoraHosted] 
# '''Download''': [http://spins.fedoraproject.org/soas/#downloads Download] the Sugar-on-a-Stick iso. 
# '''Load''': Insert a USB flash drive (or SD Card) with 1 GB or more of free space into your computer and launch Fedora Live USB Creator to create a Sugar-on-a-Stick bootable image. '''Note''': Be sure to set the ''persistent storage'' slider to a non-zero value. 
# '''Boot''': Insert the USB stick into a USB port on your computer. Set the option to "boot from USB" in your computer's <abbr title="Basic Input/Output System">BIOS</abbr> setup, and then start up the computer.
|}

Detailed [[Sugar on a Stick/Windows|installation instructions for Windows]] and [[Sugar on a Stick/Boot|booting instructions]] are available. There is also a [[Sugar on a Stick/Explore|guide to exploring Sugar on a Stick]].
----
=== GNU/Linux ===
GNU/Linux users may want to install the [[#Do_you_use_GNU.2FLinux.3F|Sugar packages]] on their favorite distro.

{|
|-
|width="160px"|[[File:Gnulinux.png|link=Sugar on a Stick/Linux]]
 
[[File:Download Mirabell.png|left|link=http://spins.fedoraproject.org/soas/#downloads]]
[[File:USB flash drive.jpg|156px|link=http://spins.fedoraproject.org/soas/#downloads]]
|valign=top|
# '''Prepare''': Use this script http://bit.ly/livecd-iso-to-disk to create a bootable image. (Run {{Code|chmod +x livecd-iso-to-disk.sh}} after you download the script to make it executable.) 
# '''Download''': [http://spins.fedoraproject.org/soas/#downloads Download] the Sugar-on-a-Stick iso. 
# '''Load''': Execute, as the root user, in one command with arguments, the following:
#:{{Code|./livecd-iso-to-disk.sh --reset-mbr --overlay-size-mb 300 --home-size-mb 175 --delete-home --unencrypted-home /path/to/source.iso /dev/sd'''?'''1}}
#: where '{{Code|'''?'''}}' in the final parameter represents the target bootable device node, such as {{Code|sdb1}} or {{Code|sdc1}}, etc. 
# '''Boot''': Insert the USB stick into a USB port on your computer. Set the option to "boot from USB" in your computer's <abbr title="Basic Input/Output System">BIOS</abbr> setup, and then start up the computer.
|}

Detailed [[Sugar on a Stick/Linux|installation instructions for GNU/Linux]] and [[Sugar on a Stick/Boot|booting instructions]] are available. There is also a [[Sugar on a Stick/Explore|guide to exploring Sugar on a Stick]].
----
=== Apple Mac OS X ===
'''DRAFT''': These instructions are incomplete. Please help with testing and documentation. In the meantime, we recommend the '''[[#Virtual Machines on all platforms|Virtual Machines instructions]]''' below.
{|
|-
|width="160px" valign="top"|[[File:Apple.gif|link=Sugar_on_a_Stick/Mac]]
 
[[File:Download Mirabell.png|left|link=http://spins.fedoraproject.org/soas/#downloads]]
[[File:USB flash drive.jpg|156px|link=http://spins.fedoraproject.org/soas/#downloads]]
|valign=top|
# '''Prepare''': These instructions are only for '''64-bit''' processor machines. (To identify the processor type, choose Apple menu > About This Mac. A small window will appear titled ''About This Mac''. The processor type is displayed in this window. Sugar on a Stick is for the Intel processor only.) 
# '''Download''': [http://spins.fedoraproject.org/soas/#downloads Download] the Sugar-on-a-Stick iso. Be sure to download a '''64-bit''' image. 
# '''Load''': [[File:question.png|link=|middle]] '''Help: Does someone have a simple way to load a Live USB on a Mac?''' Here is a simple way to recognize a bootable USB on a Mac. Go to rEFIt (http://refit.sourceforge.net/) and make a bootable cd. There is no need to install rEFIt on your mac. In fact installing rEFIt may make it impossible to upgrade the Mac OS to a newer version later on (personal experience, I had to do a clean install). Put the rEFIt CD in and hold the option key after turning the computer on. The Mac will recognize the CD because it uses EFI and then the CD will recognize the bootable USB. 
:::'''[http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Building_a_bootable_USB Building and Booting_a_live_USB on a Mac]'''
# '''Boot''': Insert the USB stick into a USB port on your computer. '''Is this correct?''': During the startup sound, press and hold the '''c''' key. If the Apple logo appears, Sugar is not booting. Restart and try again.
#* the '''c''' key must be pressed during the startup sound and you must continue to hold it down.
#* you may release the '''c''' key once the Sugar logo appears.
* Have a MAC Book Air? See
: [http://wiki.sugarlabs.org/go/Mac_OS_X-Boot_USB_with_Virtualbox#Running_Soas_files_on_a_2nd_USB_in_Virtualbox_3.2_installed_on_the_MacBook_Air Running_Soas_files_on_a_2nd_USB_in_Virtualbox_3.2_installed_on_the_MacBook_Air]
: [http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Building_a_bootable_USB Building_a_bootable_USB]
: [http://lists.sugarlabs.org/archive/iaep/2010-November/012019.html Soas-v4 on a MacBook Air]
: [http://wiki.sugarlabs.org/go/Mac_OS_X-Boot_USB_with_Virtualbox#Mac_OSX-F14-desktop_with_Virtualbox_Boot_USB Mac_OSX-F14-desktop_with_Virtualbox_Boot_4GB USB]
:: Opens a 2nd USB with a Soas-v3 virtual appliance. Note that the 2nd USB can be exchanged for use by another student, who can eject his USB and keep it till his next session.
|}

Alternative [[Sugar on a Stick/Mac|installation instructions for Mac OS X]]. Also, [[Sugar_on_a_Stick/Blueberry#For_Mac_OS_X_Users|these older installation instructions]] and [[Sugar on a Stick/Boot|booting instructions]] may be consulted. There is also a [[Sugar on a Stick/Explore|guide to exploring Sugar on a Stick]].
----
=== Advanced users ===

{|
|-
|width="174px"|[[File:Sugar Creation Kit.png|link=Sugar Creation Kit]]
|valign=top|
* '''Explore''' the [[Sugar Creation Kit]]

* '''Try''' [[Sugar_on_a_Stick/Installation/Variations|customizing]] Sugar on a Stick;

* '''Read''' the [http://download.sugarlabs.org/soas/docs/customization-guide/ detailed Customization Guide]; and

* '''Read''' additional instructions for using [[VirtualBox]] and other virtual machines.
|}

 
==Do you have an OLPC XO?==

{|
|-
|width="174px"|[[File:OLPCXO.png|middle|link=Dextrose]]
|valign=top|
* '''Upgrade''' to the latest ''[[olpc:OS_images#Stable_builds|stable OS release]]'' from OLPC (includes Sugar 0.84 and GNOME 2.26)

* '''Upgrade''' to ''[[Dextrose |Dextrose Sugar 0.88 with Fedora 11 and GNOME]]'' (requires a [[olpc:Activation_and_developer_keys|developer key]])

* '''Load ''' another one of the [[OLPC:OS images]]

* '''Test''' Sugar 0.90 on Fedora 14 [[OLPC:F14 for XO]]
*: See this [http://www.mail-archive.com/devel@lists.laptop.org/msg25313.html discussion thread].

* '''Experiment''' with [[Sugar_on_a_Stick/Installation/OLPC|Updating XOs]] to the latest ''Sugar on a Stick'' release.
|}

 

==Do you use GNU/Linux?==

{|
|-
|width="178px" valign="top"|Select your favorite distribution [[File:Gnulinux.png|link=Community/Distributions]]||
{|
|-
|[[Image:Fedora-small.jpg|link=Community/Distributions/Fedora]] [[Community/Distributions/Fedora|Fedora]]
|-
|[[Image:Debian-small.jpg|link=Community/Distributions/Debian]] [[Community/Distributions/Debian|Debian]]
|[[File:Trisquel_icon.png|link=Community/Distributions/Trisquel]] [[Community/Distributions/Trisquel|Trisquel]]
|[[Image:Ubuntu-small.jpg|link=Community/Distributions/Ubuntu]] [[Community/Distributions/Ubuntu|Ubuntu]]
|align="center"|[[Image:Ubuntu-small.jpg|link=http://wiki.ubuntu.com/Sugar]] [http://wiki.ubuntu.com/Sugar '''U'''buntu '''S'''ugar '''R'''emix]
|-
|align="center"|[[Image:Mandriva-small.png|link=Community/Distributions/Mandriva]] [[Community/Distributions/Mandriva|Mandriva]]
|align="center"|[[Image:Caixa_M%C3%A1gica-small.jpg|link=Community/Distributions/Magalhães]] [[Community/Distributions/Magalhães|Caixa Mágica]]
|-
|align="center"|[[Image:Suse-small.jpg|link=Community/Distributions/OpenSUSE]] [[Community/Distributions/OpenSUSE| openSUSE]]
|[[Image:Suse-small.jpg|link=http://en.opensuse.org/Sugar]] [http://en.opensuse.org/Sugar openSUSE]||
|-
|align="center"|[[Image:Arch-logo.png|link=http://wiki.archlinux.org/index.php/Sugar]] [http://wiki.archlinux.org/index.php/Sugar Archlinux]||
|-
|[[Image:Debian-small.jpg|link=Community/Distributions/Linux_Mint_Debian]] [[Community/Distributions/Linux_Mint_Debian|Linux_Mint_Debian]]
|-
|[[Image:Altlinux-small.png|link=Community/Distributions/ALTLinux]] [[Community/Distributions/ALTLinux|AltLinux]]
|}
|-
|width="180px" valign="top"|Or try a Live USB version of Sugar
|[[File:Soas-mango-lassi.png|middle|200px|link=http://spins.fedoraproject.org/soas/#downloads]], Mango Lassi with Sugar 0.90.3 and Fedora 14 (Laughlin) or, for brave pioneers, [[Sugar_on_a_Stick/Beta | v5 alpha with Sugar 0.90.3 and Fedora 15 (Lovelock)]] [[File:Trisquel_icon.png|link=Trisquel On A Sugar Toast]] Trisquel on a Sugar Toast (Trisquel 3.0 ''Dwyn'') [[File:Suse-small.jpg|link=http://en.opensuse.org/Education/Live|Education/Live]] OpenSuse Live USB
|}

 
== Virtual Machines on all platforms ==

{|
|-
|width="160px"|[[File:VirtualBox.png|100px|left|link=http://www.virtualbox.org/wiki/Downloads]]
|valign=top|
* '''Appliance of Sugar on a Stick v4-Mango Lassi'''
:Note: This appliance has a maximum 1024x768 screen size as VirtualBox extensions were compiled into the kernel.
:'''Sugar 0.90.1

:user=sugar
:password=sugaruser
: '''root=sugarroot'''
:How Built:
: 8-GB VirtualBox hard disc
:English and English keyboard
:USA-Los Angeles (Pacific timezone)
:'''download and import 2 files:'''
http://download.sugarlabs.org/images/VirtualBox/Fedora-14-i686-Live-SoaS-2.ovf 12K
http://download.sugarlabs.org/images/VirtualBox/Fedora-14-i686-Live-SoaS-2-disk1.vmdk 606M

:'''had to modify the .ovf to get the image running on a X60 with ubuntu maverick:'''
http://people.sugarlabs.org/dogi/virtualbox/Fedora-14-i686-Live-SoaS-2.1.ovf 12K

* '''Appliance of Sugar on a Stick v3-Mirabelle'''
::Note: This appliance has a maximum 800x640 screensize available as VirtualBox extensions were NOT compiled into the kernel.

::firstboot has not yet run; so a new user name and password will be set for the gdm login on start up for the first time

:How Built:
: '''root=sugarroot'''
: 8-GB VirtualBox hard disc
:English and English keyboard
:USA-Los Angeles (Pacific timezone)
:'''download and import 2 files:'''
http://download.sugarlabs.org/images/VirtualBox/Fedora-13-i686-Live-SoaS-sugaruser.vmdk 533M
http://download.sugarlabs.org/images/VirtualBox/Fedora-13-i686-Live-SoaS-sugaruser.ovf 12K

;Note 1:Use the latest version of Oracle VM VirtualBox (3.2_10.8-64453 or later). Some appliances have multiple hard disc controllers and the earlier Sun VirtualBox 3.1 version does not support them.
;Note 2: All appliances were built on a MacBook Air with Oracle VM VirtualBox (3.2.10-r66523) then tested on a Ubuntu installation on an Acer Aspire One Netbook imported into VirtualBox (3.2.10 r66523)
;Note 3:Set ControlPanel/Frame "Edge" slider to far left for easier access to sugar-frame features

:(Note that on some browsers on Mac OS X, the file extensions are reset upon download. You may have to modify them to match those shown above.) 

:If you run into problems, you may want to consult the [[Talk:VirtualBox]] page for help.
|-
|colspan="2"|'''[[Emulator_image_files#Other_virtual_machines|More Virtual Appliances]]''' Sugar included in other linux operating systems, and older versions.
|}

 
==Are you a developer?==

{|
|-
|width="174px" valign=top|[[File:Gear.png|link=Supported_systems]]
|Learn how to get setup on the [[Supported systems]] page.

Some additional references you may find useful:
* [[Development Team/Jhbuild | jhbuild]]
* [[Platform_Team/Guide/Core_development|sweet build]]
* [http://git.sugarlabs.org Gitorious source code repository]
* [[Emulator image files|Virtual machine or emulator image files]]
* Adding Sugar to your [[Supported systems|favorite distro...]]
|}

 
==Are you preparing a deployment without Internet access?==

{|
|-
|style="width: 180px"|[[File:Sugar Creation Kit.png|left|link=Sugar Creation Kit]]
|valign="top"|See [[Sugar Creation Kit]]
|}

 

==Are you looking for Sugar Activities?==

{|
|-
|width="170px" valign="top"|Visit the [http://activities.sugarlabs.org Sugar Activity Library]||<imagemap>
File:Sugarlabs_mainpage_02.png
rect 14 14 38 47 [[sal:4076|Calculate]]
rect 74 15 107 44 [[sal:4069|Chat]]
rect 137 16 171 43 [[sal:4086|Implode]]
rect 201 14 238 46 [[sal:4264|Distance]]
rect 265 12 298 47 [[sal:4030|Etoys]]
rect 11 79 41 108 [[sal:4034|Moon]]
rect 74 78 106 110 [[sal:4082|Paint]]
rect 140 78 170 109 [[sal:4041|Pippy]]
rect 201 80 235 108 [[sal:4028|Read]]
rect 266 82 298 107 [[sal:4081|Record]]
rect 11 143 41 172 [[sal:4062|TamTam Synth Lab]]
rect 75 146 105 169 [[sal:4043|Terminal]]
rect 142 140 166 173 [[sal:4027|Turtle Blocks]]
rect 201 144 235 171 [[olpc:WikiBrowse|WikiBrowse]]
rect 269 142 299 173 [[sal:4201|Write]]
default [http://activities.sugarlabs.org Sugar Activity Library]
desc none
</imagemap>
|}

User:Dogi

2011-01-27T21:55:05Z

Dogi:

[http://wiki.laptop.org/go/User:Dogi my page on laptop.org]

{{Special:WhatLinksHere/User:Dogi}}

Meetings

2011-01-27T21:43:28Z

Dogi:

== Meeting bot ==
An instance of the old [http://wiki.debian.org/MeetBot meetbot] (eggdrop based), run by [[User:Dogi|dogi]] and [[User:alsroot|alsroot]], lives in the #sugar-meeting channel. See the [http://wiki.laptop.org/go/User:Dogi/meeting link] for more detailed instructions, but you should be able to get by if you just say "#startmeeting" (no quotes) at the start of the meeting, and "#endmeeting" (no quotes) at the end of the meeting. This will cause meeting logs to automatically be generated and posted at http://meeting.sugarlabs.org/

== Meeting pages ==
{{Iframe|collapsed=|See [[:Category:Meetings]] for the meeting pages of the various Sugar Labs teams and projects. |http://wiki.sugarlabs.org/go/Category:Meetings|900|700|1}}

Infrastructure Team

2011-01-27T21:35:48Z

Dogi: /* Resources */

<noinclude>{{TeamHeader|Infrastructure Team}} </noinclude>

==Mission ==
{{:Infrastructure Team/Mission}}

== Resources ==

Consult the [[Infrastructure_Team/Resources|Resources]] page for the complete list of Sugar Labs' web and development [[Service|Services]] and
of the individual [[Machine|Machines]] hosting them. See also our [[Sysadmin]] procedures.

== Contacts ==
To contact us, please visit the [[Infrastructure Team/Contacts|contacts]] page.

== Subpages ==

{{Special:PrefixIndex/{{PAGENAME}}/}}

== Sysop Prime Directives ==
# Protect the Innocent
# Uphold the Law''
# Reboot Sparingly
# and join [http://mibbit.com/?channel=%23treehouse&server=irc.oftc.net irc://irc.oftc.net/treehouse]

[[Image:BOFH Keyboard.gif]]

[[Category:Team]]

Machine/schooltool

2011-01-27T17:25:19Z

Dogi: /* Info */

== Info ==

This is the server for the [http://www.schooltool.org/ SchoolTool] pilot in El Salvador.

A demo of SchoolTool is available at: [http://schooltool.sugarlabs.org:7080 schooltool in sugarlabs colors] and [http://schooltool.sugarlabs.org:60020 El Calvario].

== Hostnames ==

* [http://schooltool.sugarlabs.org/ schooltool.sugarlabs.org]

== Hosted on ==

[[Machine/treehouse]]

== Administrative contact ==

dogi AT sugarlabs DOT org

douglascerna AT yahoo DOT com

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:dogi|Stefan Unterhauser]]

== Notes ==

Running on:

* Ubuntu Lucid 10.04.1

* SchoolTool 1.0.3 (Python 2.6.5)

== Upgrade notes ==

* [https://launchpad.net/~schooltool-owners/+archive/ppa SchoolTool PPA]

== See Also ==

* [https://launchpad.net/~schooltoolers SchoolTool Users mailing list]

* [https://launchpad.net/~schooltool-developers SchoolTool Developers mailing list]

[[Category:Service|schooltool]]

Machine/schooltool

2011-01-27T17:24:55Z

Dogi: /* Info */

== Info ==

This is the server for the [http://www.schooltool.org/ SchoolTool] pilot in El Salvador.

A demo of SchoolTool is available at: http://schooltool.sugarlabs.org:7080 schooltool in sugarlabs colors] and [http://schooltool.sugarlabs.org:60020 El Calvario].

== Hostnames ==

* [http://schooltool.sugarlabs.org/ schooltool.sugarlabs.org]

== Hosted on ==

[[Machine/treehouse]]

== Administrative contact ==

dogi AT sugarlabs DOT org

douglascerna AT yahoo DOT com

== Sysadmins ==

For non-emergency calls, preferably send email to the administrative contact.

* [[User:dogi|Stefan Unterhauser]]

== Notes ==

Running on:

* Ubuntu Lucid 10.04.1

* SchoolTool 1.0.3 (Python 2.6.5)

== Upgrade notes ==

* [https://launchpad.net/~schooltool-owners/+archive/ppa SchoolTool PPA]

== See Also ==

* [https://launchpad.net/~schooltoolers SchoolTool Users mailing list]

* [https://launchpad.net/~schooltool-developers SchoolTool Developers mailing list]

[[Category:Service|schooltool]]