Difference between revisions of "Ideas for Projects"

Latest revision as of 16:35, 24 February 2014

This list was brainstormed as ideas for High School student groups, however, its totally appropriate for everyone from teens to grannies. Use this as a starting point and follow your own interests and skills.

See also these project ideas: Summer of Code/2014 | Google Code In 2013 | Summer of Code/2012

Documentation

Create instructions, tutorials or videos for the hundreds of activities for Sugar that currently lack them.
Translate existing documentation.
Scavenger hunt for what documentation and information there is about an activity and how its used and bring all that information together. This is especially good for Spanish speakers/learners as much of the usage is in South America.

Language

Translate documentation and activities to your own language, perhaps with the help of others such as parents with better language skills.
Translate an interesting post from the Spanish speaking list and post it on the English speaking list, or vice versa.

Get Sugar on a Stick to work on your computers

Document what you did and any problems.
Document what your computer is: chipsets, specs, etc.
Test performance on different types of equipment and help us find out what are the limiting factors.

Take Sugar on a Stick to your old elementary school

Do a lesson in the computer lab.
Work with a teacher and create a lesson aligned with the curriculum. Post the lesson plan, how it went and what curriculum standards it aligns to - Just imagine if we could get thousands of high school students doing a dozen of these each!
Make a documentary of kids using Sugar.

Programming

To sugarize means taking a program like Tux Paint or GCompris and making it use Sugar's special features of saving automatically to the Journal, sharing and collaboration. Many programs need sugarizing:

All the different GCompris pieces
TuxPaint
Scratch
Many others that I don't know off the top of my head

Moodle Integration - Sugar already has single sign-on but there is so much more to do:

Launching a Sugar activity from Moodle
Letting a teacher create a Moodle activity that launches an activity in Sugar and then automatically saves to the Moodle drop box
What-you-Paint-is-What-you-Get (wypiwig) plug-in for Moodle

School server:

Set up an XS and document what you did.
Test scalability of XS and Jabber

Printing

Work out how to print with software-locked XOs and school servers in locked cages, where no software can be installed by school personnel, and printers may not be attached to the XSs. This is the situation in Uruguay.

We can transfer files on USB drives for printing. We would like a networked solution.

Contact Mokurai to join this project.

@@ Line 1: / Line 1: @@
-This list was brainstormed as ideas for High School student groups, however, its totally appropriate for teens to grannies.  Use this as a starting point and follow your own interests and skills.
+<noinclude>[[Category:Idea]]</noinclude>
+This list was brainstormed as ideas for High School student groups, however, its totally appropriate for everyone from teens to grannies.  Use this as a starting point and follow your own interests and skills.
+See also these project ideas: [[Summer of Code/2014]] | [[Google Code In 2013]] | [[Summer of Code/2012]]
 ===Documentation===
-* There are hundreds of activities for Sugar, almost none of them have any documentation, tutorials for videos.
+* Create instructions, tutorials or videos for the hundreds of activities for Sugar that currently lack them.
-* Translate documentation.
+* Translate existing documentation.
-* Scavenger hunt for what documentation and information there is about an activity and how its used and bring all that information together. This is especially good for Spanish speakers/learners as much of the usage is in south America.
+* Scavenger hunt for what documentation and information there is about an activity and how its used and bring all that information together. This is especially good for Spanish speakers/learners as much of the usage is in South America.
-===Language==
+===Language===
-* Translate documentation and interface, especially with the help of their parents when they are native speakers.
+* Translate documentation and activities to your own language, perhaps with the help of others such as parents with better language skills.
-* Translate an interesting post from the Spanish speaking list and post it on the English speaking list
+* Translate an interesting post from the Spanish speaking list and post it on the English speaking list, or vice versa.
-===Get Sugar on a Stick to work on their computers===
+===Get Sugar on a Stick to work on your computers===
-* Document what they did and any problems.
+* Document what you did and any problems.
-* Document what their computer is, chipsets, spec
+* Document what your computer is: chipsets, specs, etc.
-* Test performance on different types of equipment and help us find out what are the limiting factors
+* Test performance on different types of equipment and help us find out what are the limiting factors.
-===Take Sugar on a Stick to their old elementary school===
+===Take Sugar on a Stick to your old elementary school===
-* Do a lesson in the computer lab
+* Do a lesson in the computer lab.
-* Work with a teacher and create a lesson aligned wit the curriculum. Post the lesson plan, how it went and what curriculum standards it aligns to - Just image if we could get thousands of high school students doing a doze of these each!
+* Work with a teacher and create a lesson aligned with the curriculum. Post the lesson plan, how it went and what curriculum standards it aligns to - Just imagine if we could get thousands of high school students doing a dozen of these each!
-* Make a documentary of kids using Sugar
+* Make a documentary of kids using Sugar.
 ===Programming===
+''To sugarize'' means taking a program like Tux Paint or GCompris and making it use Sugar's special features of saving automatically to the Journal, sharing and collaboration.  Many programs need sugarizing:
+* All the different GCompris pieces
+* TuxPaint
+* Scratch
+* Many others that I don't know off the top of my head
+Moodle Integration - Sugar already has single sign-on but there is so much more to do:
+* Launching a Sugar activity from Moodle
+* Letting a teacher create a Moodle activity that launches an activity in Sugar and then automatically saves to the Moodle drop box
+* What-you-Paint-is-What-you-Get (wypiwig) plug-in for Moodle
-Sugarize means taking a program like Tux Paint or GCompris and have it use Sugar's special features of saving automatically to the Journal and sharing and collaboration.  Many programs need Sugarizing.
+School server:
+* Set up an XS and document what you did.
+* Test scalability of XS and Jabber
-    * All the different GCompris pieces
+===Printing===
-    * TuxPaint
-    * Scratch
-    * Many others that I don't know off the top of my head
-Moodle Integration - Sugar already has single sign on but there is so much more to do.
+* Work out how to print with software-locked XOs and school servers in locked cages, where no software can be installed by school personnel, and printers may not be attached to the XSs. This is the situation in Uruguay.
-    * Launch a Sugar app from Moodle
+* We can transfer files on USB drives for printing. We would like a networked solution.
-    * Let a teacher create a Moodle activity that launches an app in Sugar  and then automatically saves to the Moodle drop box
-    * What you Paint is What you Get plug in for Moodle
-Set up an XS and document what you did.
+* Contact [mailto:mokurai@sugarlabs Mokurai] to join this project.
-Scalability test of XS and Jabber