Sugar Labs - User contributions [en]

User:Jza

2013-04-24T20:47:34Z

Jza:

[http://fbcdn-sphotos-d-a.akamaihd.net/hphotos-ak-prn1/317888_10150452891561978_333971821_n.jpg Mugshot]
;Name: Alexandro Colorado
;email: jza at oooes.org
;IRC nick: JZA
;IM: jzarecta [@] gmail.com

User:Jza

2013-04-24T20:42:57Z

Jza: update image file

[[File:Jza.jpg|thumbnail|right]]
;Name: Alexandro Colorado
;email: jza at oooes.org
;IRC nick: JZA
;IM: jzarecta [@] gmail.com

File:Jza.jpg

2013-04-24T20:42:23Z

Jza: Profile mugshot

Profile mugshot

User:Jza

2013-04-24T20:39:47Z

Jza: Created page with "right ;Name: Alexandro Colorado ;email: jza at oooes.org ;IRC nick: JZA ;IM: jzarecta [@] gmail.com"

[[File:Jza.png|thumbnail|right]]
;Name: Alexandro Colorado
;email: jza at oooes.org
;IRC nick: JZA
;IM: jzarecta [@] gmail.com

GoogleCodeIn2012/FLOSSMANUAL Sugar

2012-11-29T23:30:13Z

Jza: Added link to the full HTML.

;Background: The Sugar Manual [http://en.flossmanuals.net/sugar/_all/] was written in 2008. It is woefully out of date.

;Task: Update the Sugar Manual to reflect recent Sugar builds (0.98). User should be able to:
# Evaluate the content
# Load SugarOS on a Virtual Machine or scanned the internet for recent version screenshots
# Enhance the wording of the tasts, the new activities and update some of the screenshots of the manual.

;Contact: Sugar Documentation Team

[[Category: GCI2012]]

GoogleCodeIn2012/FLOSSMANUAL Sugar

2012-11-29T23:26:26Z

Jza: Added some information about the task.

;Background: The Sugar Manual [http://en.flossmanuals.net/sugar/] was written in 2008. It is woefully out of date.

;Task: Update the Sugar Manual to reflect recent Sugar builds (0.98). User should be able to:
# Evaluate the content
# Load SugarOS on a Virtual Machine or scanned the internet for recent version screenshots
# Enhance the wording of the tasts, the new activities and update some of the screenshots of the manual.

;Contact: Sugar Documentation Team

[[Category: GCI2012]]

GoogleCodeIn2012/Collections

2012-11-28T12:25:58Z

Jza:

;Background: The [http://activities.sugarlabs.org Sugar activity portal] has a "[http://activities.sugarlabs.org/en-US/sugar/collections collections]" section. Collections are a way for you to categorize, mix, match and mingle activities. Subscribe to collections created by other users or create your own. It was expected that teachers would make use of collections to organize Sugar activities around pedagogical goals, but there has been little use of collections.

;Task: Write a guide to using themed collections around project and curricula goals. (See [[Math4Team/Florida]] as an example of a wiki-based collection)

;Contact: Walter --at-- sugarlabs dot org

[[Category: GCI2012]]

Google Code-In 2012

2012-11-27T17:14:22Z

Jza: added to task "Update and add new content to the manual Sugar Manual", Create a guide to creating and using collections.

Sugar Labs is <strike>applying to</strike> participating in Google Code-in for 2012.

=== Message to potential participants ===

It is important that you obtain permission of your parents.

Es importante que obtengas el permiso de tus padres para participar.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page#eligibility

Please see the Contest Rules for Eligibility and Registration process.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions

'''Details regarding the required forms and paperwork are here: [[GoogleCodeIn2012/Participate#Students]].'''

=== Why we are participating ===

Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.

=== About GCI ===

[http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page Code-in FAQ]

=== Tasks ===
This [[GoogleCodeIn2012/GCI2012_Brainstorming|brainstorming]] page lists some general categories from which specific individual tasks can be specified. (Note: We had [[Summer_of_Code/2012#Project_candidates|a number of tasks]] listed in our GSOC application that may be relevant to GCI. We also have many [[Features]] that are still pending.)

;Code: Tasks related to writing or refactoring code
;Documentation/Training: Tasks related to creating/editing documents and helping others learn more
;Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
;Quality Assurance: Tasks related to testing and ensuring code is of high quality.
;User Interface: Tasks related to user experience research or user interface design and interaction

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Category !! Tag
|-
|Pootle helper-script || align=left | [[GoogleCodeIn2012/MsgfmtChecker|Write a new pootle-helper script for doing preventative msgfmt checks.]] || 20 || cjl || Code || i18n
|-
|Sugarize Virtaal || align=left | [[GoogleCodeIn2012/Virtaal|Sugarize Virtaal for L10n bootstrapping]] || 60 || cjl || Code || i18n
|-
|GTK2-to-GTK3 conversion || align=left | [[GoogleCodeIn2012/GTK2-3|Convert Sugar activities from GTK-2 to GTK-3 framework.]] || 10 || walterbender, humitos || Code || gtk3
|-
|Set background image || align=left | [[GoogleCodeIn2012/Homeview_image|Implement the set background image on Home View Feature.]] || 40 || walterbender || Code || sugar
|-
|Multiple Homeviews || align=left | [[GoogleCodeIn2012/Multiple_homeview|Implement the multiple homeview feature]] || 60 || walterbender || Code || sugar
|-
|Package toolbar utils || align=left | [[GoogleCodeIn2012/Toolbar_utils|Package Sugar activity utilities]] || 2 || walterbender || Code || toolkit
|-
|Infoslicer enhancement (wikislices) || align=left | [[GoogleCodeIn2012/Infoslicer-wikislices|Extend the Infoslicer activity to be able to use the local content in the Wikislices project.]] || 20 || humitos || Code || activity
|-
|Infoslicer enhancement (journal images) || align=left | [[GoogleCodeIn2012/Infoslicer-journal-images|Extend the Infoslicer activity to be able to use images from the Sugar Journal]] || 20 || humitos || Code || activity
|-
|Implement collaboration in Paint Activity || align=left | [[GoogleCodeIn2012/Collaborative_paint|Paint Activity does not implement collaboration yet.]] || 40 || gonzalo || Code || activity
|-
|Implement a presentation mode in Fototoon || align=left | [[GoogleCodeIn2012/Fototoon_presentations|Fototoon should have a view to edit and view one cell at a time using the full screen.]] || 40 || gonzalo || Code || activity
|-
|Sugarize Python Turtle module || align=left | [[GoogleCodeIn2012/PyTurtle|Will require port of the Python turtle module to GTK (currently it is QT)]] || 60 || walterbender || Code || activity
|-
|Turtle Art nutrition || align=left | [[GoogleCodeIn2012/Nutrition|Further develop the prototype Turtle Nutrition plug-in into a stand-alone activity.]] || 60 || walterbender || Code || activity
|-
|Portfolio videos || align=left | [[GoogleCodeIn2012/Portfolio_videos|Add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation]] || 40 || walterbender || Code || activity
|-
|Improve use of images in Fototoon || align=left | [[GoogleCodeIn2012/Fototoon_background_images|Fototoon should be able to clip a image to use it as background.]] || 40 || gonzalo || Code || activity
|-
|Port GBrainy to Python || align=left | [[GoogleCodeIn2012/Gbrainy_port|GBrainy have many good logic games]] || 60 || gonzalo || Code || activity
|-
|Stopwatch enhancement || align=left | [http://bugs.sugarlabs.org/ticket/2976 Stopwatch must use the game keys] || 5 || walterbender, humitos || Code || StopWatch
|-
|Write activity enhancement || align=left | [http://bugs.sugarlabs.org/ticket/1690 Retain font and size in Write Activity] || 5 || gonzalo || Code || Write
|-
|Jukebox activity enhancement || align=left | [http://bugs.sugarlabs.org/ticket/1961 Failing to play files with names containing spaces or @] || 5 || walterbender, humitos || Code || Jukebox
|-
|Calculate activity enhancement 1 || align=left | [http://bugs.sugarlabs.org/ticket/2134 Calculate's Plot doesn't have good axes] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 2 || align=left | [http://bugs.sugarlabs.org/ticket/2386 Calculate error point reporting] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 3 || align=left | [http://bugs.sugarlabs.org/ticket/2466 Calculate does not always return an error for incorrect plot statements] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 4 || align=left | [http://bugs.sugarlabs.org/ticket/2698 Calculate allows default variables to be redefined] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 5 || align=left | [http://bugs.sugarlabs.org/ticket/2700 Calculate significant digit calculations may be exponentializing Integer numbers one digit early] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 6 || align=left | [http://bugs.sugarlabs.org/ticket/2701 Calculate should let you export plotted graphs to the clipboard] || 5 || walterbender, humitos || Code || Calculate
|-
|Log activity enhancement || align=left | [http://bugs.sugarlabs.org/ticket/2735 Log activity should support reading previous sugar log directories] || 5 || walterbender, humitos || Code || Log
|-
|Moon activity enhancement 1 || align=left | [http://bugs.sugarlabs.org/ticket/2910 Add option to export the moon phase as an image to the Journal] || 5 || walterbender, humitos || Code || Moon
|-
|Moon activity enhancement 2 || align=left | [http://bugs.sugarlabs.org/ticket/2911 Add eclipse glyph to indicate the type of eclipse] || 5 || walterbender, humitos || Code || Moon
|-
|On-screen keyboard support || align=left | [[GoogleCodeIn2012/OSK|Enable touch for activities that use direct keyboard input.]] || 20 || walterbender || Code || touch
|-
|Unified journal view || align=left | [[GoogleCodeIn2012/Journal_view|Rather than viewing the details of a Journal entry on a separate page make the details appear in an expandable in-line format]] || 120 || || Code || sugar
|-
|Plugin support || align=left | [[GoogleCodeIn2012/Turtle_plugins|Design a uniform plug-in bundle type and modify the activity installer to recognize this new type.]] || 80 || || Code || activity
|-
|End-user modifications of Sugar source || align=left | [[GoogleCodeIn2012/End-user-mods|We have a mechanism for viewing the Sugar toolkit source but no such convenient way for making changes without risking messing up the system.]] || 120 || || Code || sugar
|-
|Implement help mechanism for activities using Mallard || align=left | [[GoogleCodeIn2012/Mallard|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 but is programmed in Mono. It would nice to have a native Python version accessed through a mechanism similar to the view source mechanism.]] || 60 || || Code || sugar
|-
|Turtle Art tutorial || align=left | [[GoogleCodeIn2012/Turtle_Art|Write a Turtle Art introductory tutorial]] || 60 || tonyforster || Documentation/Training || activity
|-
|Turtle Art with Sensors tutorial || align=left | [[GoogleCodeIn2012/Turtle_Art_Sensors|Write a Turtle Art with Sensors introductory tutorial]] || 60 || tonyforster, walterbender || Documentation/Training || activity
|-
|Make your own Sugar activity || align=left | [[GoogleCodeIn2012/MYOSA|Update and add new content to the manual Make Your Own Sugar Activities]] || 40 || nicestep || Documentation/Training || doc
|-
|OCR Document formatting (multiple task units) || align=left | [[Google_Code-In_2012/OCR_document_reformatting|The goal is to transform a 456 page image-PDF file of an Asháninka-Spanish and Spanish-Asháninka dictionary into OCR'ed digital text.]] || 120 || cjl || Documentation/Training || i18n
|-
|Wiki cleanup (multiple task units) || align=left | [http://pe.sugarlabs.org/go/Wiki_Clean_Up A somewhat mundane task, we need to clean out the spam in an affiliated project website.] || 5 || lfaraone || Documentation/Training || wiki
|-
|GTK3 conversion guide || align=left | [[GoogleCodeIn2012/GTK3_guide|Flesh out the GTK-2 to GTK-3 conversion documentation to include more comprehensive coverage of Pango.]] || 40 || || Documentation/Training || gtk3
|-
|Sugar on a Stick guide || align=left | [[GoogleCodeIn2012/SOAS_guide|Better document the process of creating and using Sugar on a Stick the LiveUSB version of Sugar.]] || 40 || satellit || Documentation/Training || soas
|-
|Create new Sugar Labs home page || align=left | [[GoogleCodeIn2012/SugarLabs.org|We have some detailed designs of a new website that need to be implemented.]] || 120 || JohnTierney || Documentation/Training || www
|-
|Sugar VM || align=left | [[GoogleCodeIn2012/VM|Better document the process of running Sugar in a virtual machine (VM).]] || 40 || satellit || Documentation/Training || soas
|-
|How-to videos || align=left | [[GoogleCodeIn2012/Videos|Create videos on how to use Sugar and how to use core Sugar activities.]] || 20 || JohnTierney || Documentation/Training || doc
|-
|How to create a collection || align=left | [[GoogleCodeIn2012/Collections|Create a guide to creating and using collections.]] || 5 || JZA || Documentation/Training || doc
|-
|Multilanguage screen-shots || align=left | [[GoogleCodeIn2012/I18n_screenshots|Identify and document a generalized (ideally automated) method for taking nearly identical screen shots with the desktop set to a selected list of different languages. (Possibly Orca?).]] || 60 || || Documentation/Training || i18n
|-
|Sugar FLOSS Manual || align=left | [[GoogleCodeIn2012/FLOSSMANUAL_Sugar|Update and add new content to the manual Sugar Manual]] || 20 || JZA || Documentation/Training || doc
|-
|Sugar assessment tools || align=left | [[GoogleCodeIn2012/Assessment_tools|Research what metadata about Sugar activity usage would be helpful to teachers for assessment purposes.]] || 40 || claudiau, walterbender || Outreach/Research || assessment
|-
|Sugar in your school (opportunities) || align=left | [[GoogleCodeIn2012/Sugar_at_your_school|Research what opportunities/roadblocks exist for running Sugar in your local schools.]] || 40 || claudiau tonyforster|| Outreach/Research || outreach
|-
|Sugar in your school (roadblocks) || align=left | [[GoogleCodeIn2012/Sugar_roadblocks|Research what is missing from Sugar that makes it unused by your local schools.]] || 40 || claudiau tonyforster|| Outreach/Research || outreach
|-
|SVG internationalization || align=left | [[GoogleCodeIn2012/SVG_images|Research internationalization of SVG images.]] || 120 || JZA || Outreach/Research || i18n
|-
|Sugar in the Cloud || align=left | [[GoogleCodeIn2012/Sugar_in_the_cloud|Research the issues involved with porting Sugar to the Cloud.]] || 60 || lglira || Outreach/Research || future
|-
|Sugar on Android || align=left | [[GoogleCodeIn2012/Sugar_on_Android|Research the issues involved with porting Sugar to Android.]] || 120 || aguirrea || Outreach/Research || future
|-
|Copyleft Games || align=left | [[GoogleCodeIn2012/Sugar_and_CGG|Research how Sugar Labs might leverage the work of copyleftgames.org and CGG might leverage the work of Sugar Labs.]] || 20 || || Outreach/Research || activity
|-
|Port to Python3 || align=left | [[GoogleCodeIn2012/Python3|Research the issues we will encounter in porting to Python 3]] || 40 || || Outreach/Research || future
|-
|Orphaned activities || align=left | [[GoogleCodeIn2012/Sugar_orphan_status|Do an analysis of which Sugar activities are are orphaned.]] || 20 || gonzalo || Quality Assurance || maintenance
|-
|Sugar Touch || align=left | [[GoogleCodeIn2012/Sugar_touch_status|Do an analysis of which Sugar activities are touch-enabled or need modifications to support touch.]] || 20 || tonyforster || Quality Assurance || maintenance
|-
|Sugar Documentation || align=left | [[GoogleCodeIn2012/Sugar_doc_status|Do an analysis of which Sugar activities are lacking in documentation (e.g. Activity wiki page).]] || 20 || tonyforster || Quality Assurance || doc
|-
|Sugar on ARM || align=left | [[GoogleCodeIn2012/Sugar_ARM_status|Do an analysis of which Sugar activities are have issues running on non-x86 architectures (e.g. ARM).]] || 20 || holt, jerryvonau || Quality Assurance || arm
|-
|Sugar i18n || align=left | [[GoogleCodeIn2012/Sugar_i18n_status|Do an analysis of which Sugar activities are lacking i18n support.]] || 20 || lfaraone || Quality Assurance || i18n
|-
|Special Needs || align=left | [[GoogleCodeIn2012/Special_needs|Analyze Sugar from the point of view of special needs and make recommendations for improvements.]] || 40 || tch || User Interface || sugar
|-
|Touch UI || align=left | [[GoogleCodeIn2012/Touch_UI|Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch).]] || 40 || tonyforster || User Interface || sugar
|-
|On-screen Keyboard || align=left | [[GoogleCodeIn2012/Maliit|Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin).]] || 20 || cjl || User Interface || sugar
|-
|Accelerometer || align=left | [[GoogleCodeIn2012/Accelerometer|Think of ways to further leverage the use of an accelerometer in Sugar (and other common sensors found in portable computing devices).]] || 40 || tonyforster || User Interface || sugar
|-
|How are we doing? || align=left | [[GoogleCodeIn2012/Assessment|Assessing how Sugar is used by students. What is being learned? Survey students and teachers. How well does it deliver its goals?]] || 120 || claudiau tonyforster|| User Interface || learning
|-
|New Features || align=left | [[GoogleCodeIn2012/Feature_requests|Survey Sugar users to find out what UI features they want from Sugar in the future.]] || 120 || JZA || User Interface || future
|-
|Manage on-line credentials || align=left | [[GoogleCodeIn2012/OnlineAccounts|What's the best way to handle on-line credentials in Sugar (i.e.: Facebook Twitter Google)]] || 120 || rgs || User Interface || future
|-
| align=left | Sugar Network Contributor Hub look&feel|| align=left | [[GoogleCodeIn2012/Contributor_Hub|Design and users experience solutions for the Contributor Hub]] || ? || [[User:alsroot|alsroot]] || User Interface || sugar-network
|}

=== Mentors ===
;NOTES TO MENTORS:
:Please refer to [[GoogleCodeIn2012/Participate#Mentors]] for details regarding enrolling as a mentor.
:Please add yourself to the table above.
:Feel free to add new tasks to the table.

Depending on the project, we will assign multiple mentors from our various development and support teams.

* Chris Leonard - also org admin for GCI
* Walter Bender - also org admin for GCI
* Andrés Aguirre Dorelo
* Claudia Urrea
* Gonzalo Odiard
* Adam Holt
* Manuel Kaufmann
* Jeffrey Elkner
* John Tierney
* JerryV
* Alan Aguiar
* Luke Faraone
* Luis Gustavo Lira
* James Simmons
* Sam Greenfeld
* Tom Gilliard
* Martín Abente Lahaye
* Tony Forster
* Alexandro Colorado

Possible additional mentors:

* Pacita Pena
* Rosamel Ramirez
* Sdenka Salas
* Simon Schampijer
* Manuel Quiñones
* Tony Forster
* Guzman Trinidad
* Sean Daly
* Mark Battley
* Bernie Innocenti
* Daniel Drake
* Raul Guttierrez Segales
* C Scott Ananian
et al.

[[Category: GCI2012]]

Google Code-In 2012

2012-11-27T16:54:09Z

Jza: /* Mentors */

Sugar Labs is <strike>applying to</strike> participating in Google Code-in for 2012.

=== Message to potential participants ===

It is important that you obtain permission of your parents.

Es importante que obtengas el permiso de tus padres para participar.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page#eligibility

Please see the Contest Rules for Eligibility and Registration process.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions

'''Details regarding the required forms and paperwork are here: [[GoogleCodeIn2012/Participate#Students]].'''

=== Why we are participating ===

Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.

=== About GCI ===

[http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page Code-in FAQ]

=== Tasks ===
This [[GoogleCodeIn2012/GCI2012_Brainstorming|brainstorming]] page lists some general categories from which specific individual tasks can be specified. (Note: We had [[Summer_of_Code/2012#Project_candidates|a number of tasks]] listed in our GSOC application that may be relevant to GCI. We also have many [[Features]] that are still pending.)

;Code: Tasks related to writing or refactoring code
;Documentation/Training: Tasks related to creating/editing documents and helping others learn more
;Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
;Quality Assurance: Tasks related to testing and ensuring code is of high quality.
;User Interface: Tasks related to user experience research or user interface design and interaction

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Category !! Tag
|-
|Pootle helper-script || align=left | [[GoogleCodeIn2012/MsgfmtChecker|Write a new pootle-helper script for doing preventative msgfmt checks.]] || 20 || cjl || Code || i18n
|-
|Sugarize Virtaal || align=left | [[GoogleCodeIn2012/Virtaal|Sugarize Virtaal for L10n bootstrapping]] || 60 || cjl || Code || i18n
|-
|GTK2-to-GTK3 conversion || align=left | [[GoogleCodeIn2012/GTK2-3|Convert Sugar activities from GTK-2 to GTK-3 framework.]] || 10 || walterbender, humitos || Code || gtk3
|-
|Set background image || align=left | [[GoogleCodeIn2012/Homeview_image|Implement the set background image on Home View Feature.]] || 40 || walterbender || Code || sugar
|-
|Multiple Homeviews || align=left | [[GoogleCodeIn2012/Multiple_homeview|Implement the multiple homeview feature]] || 60 || walterbender || Code || sugar
|-
|Package toolbar utils || align=left | [[GoogleCodeIn2012/Toolbar_utils|Package Sugar activity utilities]] || 2 || walterbender || Code || toolkit
|-
|Infoslicer enhancement (wikislices) || align=left | [[GoogleCodeIn2012/Infoslicer-wikislices|Extend the Infoslicer activity to be able to use the local content in the Wikislices project.]] || 20 || humitos || Code || activity
|-
|Infoslicer enhancement (journal images) || align=left | [[GoogleCodeIn2012/Infoslicer-journal-images|Extend the Infoslicer activity to be able to use images from the Sugar Journal]] || 20 || humitos || Code || activity
|-
|Implement collaboration in Paint Activity || align=left | [[GoogleCodeIn2012/Collaborative_paint|Paint Activity does not implement collaboration yet.]] || 40 || gonzalo || Code || activity
|-
|Implement a presentation mode in Fototoon || align=left | [[GoogleCodeIn2012/Fototoon_presentations|Fototoon should have a view to edit and view one cell at a time using the full screen.]] || 40 || gonzalo || Code || activity
|-
|Sugarize Python Turtle module || align=left | [[GoogleCodeIn2012/PyTurtle|Will require port of the Python turtle module to GTK (currently it is QT)]] || 60 || walterbender || Code || activity
|-
|Turtle Art nutrition || align=left | [[GoogleCodeIn2012/Nutrition|Further develop the prototype Turtle Nutrition plug-in into a stand-alone activity.]] || 60 || walterbender || Code || activity
|-
|Portfolio videos || align=left | [[GoogleCodeIn2012/Portfolio_videos|Add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation]] || 40 || walterbender || Code || activity
|-
|Improve use of images in Fototoon || align=left | [[GoogleCodeIn2012/Fototoon_background_images|Fototoon should be able to clip a image to use it as background.]] || 40 || gonzalo || Code || activity
|-
|Port GBrainy to Python || align=left | [[GoogleCodeIn2012/Gbrainy_port|GBrainy have many good logic games]] || 60 || gonzalo || Code || activity
|-
|Stopwatch enhancement || align=left | [http://bugs.sugarlabs.org/ticket/2976 Stopwatch must use the game keys] || 5 || walterbender, humitos || Code || StopWatch
|-
|Write activity enhancement || align=left | [http://bugs.sugarlabs.org/ticket/1690 Retain font and size in Write Activity] || 5 || gonzalo || Code || Write
|-
|Jukebox activity enhancement || align=left | [http://bugs.sugarlabs.org/ticket/1961 Failing to play files with names containing spaces or @] || 5 || walterbender, humitos || Code || Jukebox
|-
|Calculate activity enhancement 1 || align=left | [http://bugs.sugarlabs.org/ticket/2134 Calculate's Plot doesn't have good axes] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 2 || align=left | [http://bugs.sugarlabs.org/ticket/2386 Calculate error point reporting] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 3 || align=left | [http://bugs.sugarlabs.org/ticket/2466 Calculate does not always return an error for incorrect plot statements] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 4 || align=left | [http://bugs.sugarlabs.org/ticket/2698 Calculate allows default variables to be redefined] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 5 || align=left | [http://bugs.sugarlabs.org/ticket/2700 Calculate significant digit calculations may be exponentializing Integer numbers one digit early] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 6 || align=left | [http://bugs.sugarlabs.org/ticket/2701 Calculate should let you export plotted graphs to the clipboard] || 5 || walterbender, humitos || Code || Calculate
|-
|Log activity enhancement || align=left | [http://bugs.sugarlabs.org/ticket/2735 Log activity should support reading previous sugar log directories] || 5 || walterbender, humitos || Code || Log
|-
|Moon activity enhancement 1 || align=left | [http://bugs.sugarlabs.org/ticket/2910 Add option to export the moon phase as an image to the Journal] || 5 || walterbender, humitos || Code || Moon
|-
|Moon activity enhancement 2 || align=left | [http://bugs.sugarlabs.org/ticket/2911 Add eclipse glyph to indicate the type of eclipse] || 5 || walterbender, humitos || Code || Moon
|-
|On-screen keyboard support || align=left | [[GoogleCodeIn2012/OSK|Enable touch for activities that use direct keyboard input.]] || 20 || walterbender || Code || touch
|-
|Unified journal view || align=left | [[GoogleCodeIn2012/Journal_view|Rather than viewing the details of a Journal entry on a separate page make the details appear in an expandable in-line format]] || 120 || || Code || sugar
|-
|Plugin support || align=left | [[GoogleCodeIn2012/Turtle_plugins|Design a uniform plug-in bundle type and modify the activity installer to recognize this new type.]] || 80 || || Code || activity
|-
|End-user modifications of Sugar source || align=left | [[GoogleCodeIn2012/End-user-mods|We have a mechanism for viewing the Sugar toolkit source but no such convenient way for making changes without risking messing up the system.]] || 120 || || Code || sugar
|-
|Implement help mechanism for activities using Mallard || align=left | [[GoogleCodeIn2012/Mallard|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 but is programmed in Mono. It would nice to have a native Python version accessed through a mechanism similar to the view source mechanism.]] || 60 || || Code || sugar
|-
|Turtle Art tutorial || align=left | [[GoogleCodeIn2012/Turtle_Art|Write a Turtle Art introductory tutorial]] || 60 || tonyforster || Documentation/Training || activity
|-
|Turtle Art with Sensors tutorial || align=left | [[GoogleCodeIn2012/Turtle_Art_Sensors|Write a Turtle Art with Sensors introductory tutorial]] || 60 || tonyforster, walterbender || Documentation/Training || activity
|-
|Make your own Sugar activity || align=left | [[GoogleCodeIn2012/MYOSA|Update and add new content to the manual Make Your Own Sugar Activities]] || 40 || nicestep || Documentation/Training || doc
|-
|OCR Document formatting (multiple task units) || align=left | [[Google_Code-In_2012/OCR_document_reformatting|The goal is to transform a 456 page image-PDF file of an Asháninka-Spanish and Spanish-Asháninka dictionary into OCR'ed digital text.]] || 120 || cjl || Documentation/Training || i18n
|-
|Wiki cleanup (multiple task units) || align=left | [http://pe.sugarlabs.org/go/Wiki_Clean_Up A somewhat mundane task, we need to clean out the spam in an affiliated project website.] || 5 || lfaraone || Documentation/Training || wiki
|-
|GTK3 conversion guide || align=left | [[GoogleCodeIn2012/GTK3_guide|Flesh out the GTK-2 to GTK-3 conversion documentation to include more comprehensive coverage of Pango.]] || 40 || || Documentation/Training || gtk3
|-
|Sugar on a Stick guide || align=left | [[GoogleCodeIn2012/SOAS_guide|Better document the process of creating and using Sugar on a Stick the LiveUSB version of Sugar.]] || 40 || satellit || Documentation/Training || soas
|-
|Create new Sugar Labs home page || align=left | [[GoogleCodeIn2012/SugarLabs.org|We have some detailed designs of a new website that need to be implemented.]] || 120 || JohnTierney || Documentation/Training || www
|-
|Sugar VM || align=left | [[GoogleCodeIn2012/VM|Better document the process of running Sugar in a virtual machine (VM).]] || 40 || satellit || Documentation/Training || soas
|-
|How-to videos || align=left | [[GoogleCodeIn2012/Videos|Create videos on how to use Sugar and how to use core Sugar activities.]] || 20 || JohnTierney || Documentation/Training || doc
|-
|How to create a collection || align=left | [[GoogleCodeIn2012/Collections|Create a guide to creating and using collections.]] || 5 || || Documentation/Training || doc
|-
|Multilanguage screen-shots || align=left | [[GoogleCodeIn2012/I18n_screenshots|Identify and document a generalized (ideally automated) method for taking nearly identical screen shots with the desktop set to a selected list of different languages. (Possibly Orca?).]] || 60 || || Documentation/Training || i18n
|-
|Sugar FLOSS Manual || align=left | [[GoogleCodeIn2012/FLOSSMANUAL_Sugar|Update and add new content to the manual Sugar Manual]] || 20 || || Documentation/Training || doc
|-
|Sugar assessment tools || align=left | [[GoogleCodeIn2012/Assessment_tools|Research what metadata about Sugar activity usage would be helpful to teachers for assessment purposes.]] || 40 || claudiau, walterbender || Outreach/Research || assessment
|-
|Sugar in your school (opportunities) || align=left | [[GoogleCodeIn2012/Sugar_at_your_school|Research what opportunities/roadblocks exist for running Sugar in your local schools.]] || 40 || claudiau tonyforster|| Outreach/Research || outreach
|-
|Sugar in your school (roadblocks) || align=left | [[GoogleCodeIn2012/Sugar_roadblocks|Research what is missing from Sugar that makes it unused by your local schools.]] || 40 || claudiau tonyforster|| Outreach/Research || outreach
|-
|SVG internationalization || align=left | [[GoogleCodeIn2012/SVG_images|Research internationalization of SVG images.]] || 120 || JZA || Outreach/Research || i18n
|-
|Sugar in the Cloud || align=left | [[GoogleCodeIn2012/Sugar_in_the_cloud|Research the issues involved with porting Sugar to the Cloud.]] || 60 || lglira || Outreach/Research || future
|-
|Sugar on Android || align=left | [[GoogleCodeIn2012/Sugar_on_Android|Research the issues involved with porting Sugar to Android.]] || 120 || aguirrea || Outreach/Research || future
|-
|Copyleft Games || align=left | [[GoogleCodeIn2012/Sugar_and_CGG|Research how Sugar Labs might leverage the work of copyleftgames.org and CGG might leverage the work of Sugar Labs.]] || 20 || || Outreach/Research || activity
|-
|Port to Python3 || align=left | [[GoogleCodeIn2012/Python3|Research the issues we will encounter in porting to Python 3]] || 40 || || Outreach/Research || future
|-
|Orphaned activities || align=left | [[GoogleCodeIn2012/Sugar_orphan_status|Do an analysis of which Sugar activities are are orphaned.]] || 20 || gonzalo || Quality Assurance || maintenance
|-
|Sugar Touch || align=left | [[GoogleCodeIn2012/Sugar_touch_status|Do an analysis of which Sugar activities are touch-enabled or need modifications to support touch.]] || 20 || tonyforster || Quality Assurance || maintenance
|-
|Sugar Documentation || align=left | [[GoogleCodeIn2012/Sugar_doc_status|Do an analysis of which Sugar activities are lacking in documentation (e.g. Activity wiki page).]] || 20 || tonyforster || Quality Assurance || doc
|-
|Sugar on ARM || align=left | [[GoogleCodeIn2012/Sugar_ARM_status|Do an analysis of which Sugar activities are have issues running on non-x86 architectures (e.g. ARM).]] || 20 || holt, jerryvonau || Quality Assurance || arm
|-
|Sugar i18n || align=left | [[GoogleCodeIn2012/Sugar_i18n_status|Do an analysis of which Sugar activities are lacking i18n support.]] || 20 || lfaraone || Quality Assurance || i18n
|-
|Special Needs || align=left | [[GoogleCodeIn2012/Special_needs|Analyze Sugar from the point of view of special needs and make recommendations for improvements.]] || 40 || tch || User Interface || sugar
|-
|Touch UI || align=left | [[GoogleCodeIn2012/Touch_UI|Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch).]] || 40 || tonyforster || User Interface || sugar
|-
|On-screen Keyboard || align=left | [[GoogleCodeIn2012/Maliit|Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin).]] || 20 || cjl || User Interface || sugar
|-
|Accelerometer || align=left | [[GoogleCodeIn2012/Accelerometer|Think of ways to further leverage the use of an accelerometer in Sugar (and other common sensors found in portable computing devices).]] || 40 || tonyforster || User Interface || sugar
|-
|How are we doing? || align=left | [[GoogleCodeIn2012/Assessment|Assessing how Sugar is used by students. What is being learned? Survey students and teachers. How well does it deliver its goals?]] || 120 || claudiau tonyforster|| User Interface || learning
|-
|New Features || align=left | [[GoogleCodeIn2012/Feature_requests|Survey Sugar users to find out what UI features they want from Sugar in the future.]] || 120 || JZA || User Interface || future
|-
|Manage on-line credentials || align=left | [[GoogleCodeIn2012/OnlineAccounts|What's the best way to handle on-line credentials in Sugar (i.e.: Facebook Twitter Google)]] || 120 || rgs || User Interface || future
|-
| align=left | Sugar Network Contributor Hub look&feel|| align=left | [[GoogleCodeIn2012/Contributor_Hub|Design and users experience solutions for the Contributor Hub]] || ? || [[User:alsroot|alsroot]] || User Interface || sugar-network
|}

=== Mentors ===
;NOTES TO MENTORS:
:Please refer to [[GoogleCodeIn2012/Participate#Mentors]] for details regarding enrolling as a mentor.
:Please add yourself to the table above.
:Feel free to add new tasks to the table.

Depending on the project, we will assign multiple mentors from our various development and support teams.

* Chris Leonard - also org admin for GCI
* Walter Bender - also org admin for GCI
* Andrés Aguirre Dorelo
* Claudia Urrea
* Gonzalo Odiard
* Adam Holt
* Manuel Kaufmann
* Jeffrey Elkner
* John Tierney
* JerryV
* Alan Aguiar
* Luke Faraone
* Luis Gustavo Lira
* James Simmons
* Sam Greenfeld
* Tom Gilliard
* Martín Abente Lahaye
* Tony Forster
* Alexandro Colorado

Possible additional mentors:

* Pacita Pena
* Rosamel Ramirez
* Sdenka Salas
* Simon Schampijer
* Manuel Quiñones
* Tony Forster
* Guzman Trinidad
* Sean Daly
* Mark Battley
* Bernie Innocenti
* Daniel Drake
* Raul Guttierrez Segales
* C Scott Ananian
et al.

[[Category: GCI2012]]

Google Code-In 2012

2012-11-27T16:53:16Z

Jza: added myself to some tasks

Sugar Labs is <strike>applying to</strike> participating in Google Code-in for 2012.

=== Message to potential participants ===

It is important that you obtain permission of your parents.

Es importante que obtengas el permiso de tus padres para participar.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page#eligibility

Please see the Contest Rules for Eligibility and Registration process.

http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions

'''Details regarding the required forms and paperwork are here: [[GoogleCodeIn2012/Participate#Students]].'''

=== Why we are participating ===

Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.

=== About GCI ===

[http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page Code-in FAQ]

=== Tasks ===
This [[GoogleCodeIn2012/GCI2012_Brainstorming|brainstorming]] page lists some general categories from which specific individual tasks can be specified. (Note: We had [[Summer_of_Code/2012#Project_candidates|a number of tasks]] listed in our GSOC application that may be relevant to GCI. We also have many [[Features]] that are still pending.)

;Code: Tasks related to writing or refactoring code
;Documentation/Training: Tasks related to creating/editing documents and helping others learn more
;Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
;Quality Assurance: Tasks related to testing and ensuring code is of high quality.
;User Interface: Tasks related to user experience research or user interface design and interaction

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title !! Description !! Hours !! Mentor !! Category !! Tag
|-
|Pootle helper-script || align=left | [[GoogleCodeIn2012/MsgfmtChecker|Write a new pootle-helper script for doing preventative msgfmt checks.]] || 20 || cjl || Code || i18n
|-
|Sugarize Virtaal || align=left | [[GoogleCodeIn2012/Virtaal|Sugarize Virtaal for L10n bootstrapping]] || 60 || cjl || Code || i18n
|-
|GTK2-to-GTK3 conversion || align=left | [[GoogleCodeIn2012/GTK2-3|Convert Sugar activities from GTK-2 to GTK-3 framework.]] || 10 || walterbender, humitos || Code || gtk3
|-
|Set background image || align=left | [[GoogleCodeIn2012/Homeview_image|Implement the set background image on Home View Feature.]] || 40 || walterbender || Code || sugar
|-
|Multiple Homeviews || align=left | [[GoogleCodeIn2012/Multiple_homeview|Implement the multiple homeview feature]] || 60 || walterbender || Code || sugar
|-
|Package toolbar utils || align=left | [[GoogleCodeIn2012/Toolbar_utils|Package Sugar activity utilities]] || 2 || walterbender || Code || toolkit
|-
|Infoslicer enhancement (wikislices) || align=left | [[GoogleCodeIn2012/Infoslicer-wikislices|Extend the Infoslicer activity to be able to use the local content in the Wikislices project.]] || 20 || humitos || Code || activity
|-
|Infoslicer enhancement (journal images) || align=left | [[GoogleCodeIn2012/Infoslicer-journal-images|Extend the Infoslicer activity to be able to use images from the Sugar Journal]] || 20 || humitos || Code || activity
|-
|Implement collaboration in Paint Activity || align=left | [[GoogleCodeIn2012/Collaborative_paint|Paint Activity does not implement collaboration yet.]] || 40 || gonzalo || Code || activity
|-
|Implement a presentation mode in Fototoon || align=left | [[GoogleCodeIn2012/Fototoon_presentations|Fototoon should have a view to edit and view one cell at a time using the full screen.]] || 40 || gonzalo || Code || activity
|-
|Sugarize Python Turtle module || align=left | [[GoogleCodeIn2012/PyTurtle|Will require port of the Python turtle module to GTK (currently it is QT)]] || 60 || walterbender || Code || activity
|-
|Turtle Art nutrition || align=left | [[GoogleCodeIn2012/Nutrition|Further develop the prototype Turtle Nutrition plug-in into a stand-alone activity.]] || 60 || walterbender || Code || activity
|-
|Portfolio videos || align=left | [[GoogleCodeIn2012/Portfolio_videos|Add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation]] || 40 || walterbender || Code || activity
|-
|Improve use of images in Fototoon || align=left | [[GoogleCodeIn2012/Fototoon_background_images|Fototoon should be able to clip a image to use it as background.]] || 40 || gonzalo || Code || activity
|-
|Port GBrainy to Python || align=left | [[GoogleCodeIn2012/Gbrainy_port|GBrainy have many good logic games]] || 60 || gonzalo || Code || activity
|-
|Stopwatch enhancement || align=left | [http://bugs.sugarlabs.org/ticket/2976 Stopwatch must use the game keys] || 5 || walterbender, humitos || Code || StopWatch
|-
|Write activity enhancement || align=left | [http://bugs.sugarlabs.org/ticket/1690 Retain font and size in Write Activity] || 5 || gonzalo || Code || Write
|-
|Jukebox activity enhancement || align=left | [http://bugs.sugarlabs.org/ticket/1961 Failing to play files with names containing spaces or @] || 5 || walterbender, humitos || Code || Jukebox
|-
|Calculate activity enhancement 1 || align=left | [http://bugs.sugarlabs.org/ticket/2134 Calculate's Plot doesn't have good axes] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 2 || align=left | [http://bugs.sugarlabs.org/ticket/2386 Calculate error point reporting] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 3 || align=left | [http://bugs.sugarlabs.org/ticket/2466 Calculate does not always return an error for incorrect plot statements] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 4 || align=left | [http://bugs.sugarlabs.org/ticket/2698 Calculate allows default variables to be redefined] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 5 || align=left | [http://bugs.sugarlabs.org/ticket/2700 Calculate significant digit calculations may be exponentializing Integer numbers one digit early] || 5 || walterbender, humitos || Code || Calculate
|-
|Calculate activity enhancement 6 || align=left | [http://bugs.sugarlabs.org/ticket/2701 Calculate should let you export plotted graphs to the clipboard] || 5 || walterbender, humitos || Code || Calculate
|-
|Log activity enhancement || align=left | [http://bugs.sugarlabs.org/ticket/2735 Log activity should support reading previous sugar log directories] || 5 || walterbender, humitos || Code || Log
|-
|Moon activity enhancement 1 || align=left | [http://bugs.sugarlabs.org/ticket/2910 Add option to export the moon phase as an image to the Journal] || 5 || walterbender, humitos || Code || Moon
|-
|Moon activity enhancement 2 || align=left | [http://bugs.sugarlabs.org/ticket/2911 Add eclipse glyph to indicate the type of eclipse] || 5 || walterbender, humitos || Code || Moon
|-
|On-screen keyboard support || align=left | [[GoogleCodeIn2012/OSK|Enable touch for activities that use direct keyboard input.]] || 20 || walterbender || Code || touch
|-
|Unified journal view || align=left | [[GoogleCodeIn2012/Journal_view|Rather than viewing the details of a Journal entry on a separate page make the details appear in an expandable in-line format]] || 120 || || Code || sugar
|-
|Plugin support || align=left | [[GoogleCodeIn2012/Turtle_plugins|Design a uniform plug-in bundle type and modify the activity installer to recognize this new type.]] || 80 || || Code || activity
|-
|End-user modifications of Sugar source || align=left | [[GoogleCodeIn2012/End-user-mods|We have a mechanism for viewing the Sugar toolkit source but no such convenient way for making changes without risking messing up the system.]] || 120 || || Code || sugar
|-
|Implement help mechanism for activities using Mallard || align=left | [[GoogleCodeIn2012/Mallard|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 but is programmed in Mono. It would nice to have a native Python version accessed through a mechanism similar to the view source mechanism.]] || 60 || || Code || sugar
|-
|Turtle Art tutorial || align=left | [[GoogleCodeIn2012/Turtle_Art|Write a Turtle Art introductory tutorial]] || 60 || tonyforster || Documentation/Training || activity
|-
|Turtle Art with Sensors tutorial || align=left | [[GoogleCodeIn2012/Turtle_Art_Sensors|Write a Turtle Art with Sensors introductory tutorial]] || 60 || tonyforster, walterbender || Documentation/Training || activity
|-
|Make your own Sugar activity || align=left | [[GoogleCodeIn2012/MYOSA|Update and add new content to the manual Make Your Own Sugar Activities]] || 40 || nicestep || Documentation/Training || doc
|-
|OCR Document formatting (multiple task units) || align=left | [[Google_Code-In_2012/OCR_document_reformatting|The goal is to transform a 456 page image-PDF file of an Asháninka-Spanish and Spanish-Asháninka dictionary into OCR'ed digital text.]] || 120 || cjl || Documentation/Training || i18n
|-
|Wiki cleanup (multiple task units) || align=left | [http://pe.sugarlabs.org/go/Wiki_Clean_Up A somewhat mundane task, we need to clean out the spam in an affiliated project website.] || 5 || lfaraone || Documentation/Training || wiki
|-
|GTK3 conversion guide || align=left | [[GoogleCodeIn2012/GTK3_guide|Flesh out the GTK-2 to GTK-3 conversion documentation to include more comprehensive coverage of Pango.]] || 40 || || Documentation/Training || gtk3
|-
|Sugar on a Stick guide || align=left | [[GoogleCodeIn2012/SOAS_guide|Better document the process of creating and using Sugar on a Stick the LiveUSB version of Sugar.]] || 40 || satellit || Documentation/Training || soas
|-
|Create new Sugar Labs home page || align=left | [[GoogleCodeIn2012/SugarLabs.org|We have some detailed designs of a new website that need to be implemented.]] || 120 || JohnTierney || Documentation/Training || www
|-
|Sugar VM || align=left | [[GoogleCodeIn2012/VM|Better document the process of running Sugar in a virtual machine (VM).]] || 40 || satellit || Documentation/Training || soas
|-
|How-to videos || align=left | [[GoogleCodeIn2012/Videos|Create videos on how to use Sugar and how to use core Sugar activities.]] || 20 || JohnTierney || Documentation/Training || doc
|-
|How to create a collection || align=left | [[GoogleCodeIn2012/Collections|Create a guide to creating and using collections.]] || 5 || || Documentation/Training || doc
|-
|Multilanguage screen-shots || align=left | [[GoogleCodeIn2012/I18n_screenshots|Identify and document a generalized (ideally automated) method for taking nearly identical screen shots with the desktop set to a selected list of different languages. (Possibly Orca?).]] || 60 || || Documentation/Training || i18n
|-
|Sugar FLOSS Manual || align=left | [[GoogleCodeIn2012/FLOSSMANUAL_Sugar|Update and add new content to the manual Sugar Manual]] || 20 || || Documentation/Training || doc
|-
|Sugar assessment tools || align=left | [[GoogleCodeIn2012/Assessment_tools|Research what metadata about Sugar activity usage would be helpful to teachers for assessment purposes.]] || 40 || claudiau, walterbender || Outreach/Research || assessment
|-
|Sugar in your school (opportunities) || align=left | [[GoogleCodeIn2012/Sugar_at_your_school|Research what opportunities/roadblocks exist for running Sugar in your local schools.]] || 40 || claudiau tonyforster|| Outreach/Research || outreach
|-
|Sugar in your school (roadblocks) || align=left | [[GoogleCodeIn2012/Sugar_roadblocks|Research what is missing from Sugar that makes it unused by your local schools.]] || 40 || claudiau tonyforster|| Outreach/Research || outreach
|-
|SVG internationalization || align=left | [[GoogleCodeIn2012/SVG_images|Research internationalization of SVG images.]] || 120 || JZA || Outreach/Research || i18n
|-
|Sugar in the Cloud || align=left | [[GoogleCodeIn2012/Sugar_in_the_cloud|Research the issues involved with porting Sugar to the Cloud.]] || 60 || lglira || Outreach/Research || future
|-
|Sugar on Android || align=left | [[GoogleCodeIn2012/Sugar_on_Android|Research the issues involved with porting Sugar to Android.]] || 120 || aguirrea || Outreach/Research || future
|-
|Copyleft Games || align=left | [[GoogleCodeIn2012/Sugar_and_CGG|Research how Sugar Labs might leverage the work of copyleftgames.org and CGG might leverage the work of Sugar Labs.]] || 20 || || Outreach/Research || activity
|-
|Port to Python3 || align=left | [[GoogleCodeIn2012/Python3|Research the issues we will encounter in porting to Python 3]] || 40 || || Outreach/Research || future
|-
|Orphaned activities || align=left | [[GoogleCodeIn2012/Sugar_orphan_status|Do an analysis of which Sugar activities are are orphaned.]] || 20 || gonzalo || Quality Assurance || maintenance
|-
|Sugar Touch || align=left | [[GoogleCodeIn2012/Sugar_touch_status|Do an analysis of which Sugar activities are touch-enabled or need modifications to support touch.]] || 20 || tonyforster || Quality Assurance || maintenance
|-
|Sugar Documentation || align=left | [[GoogleCodeIn2012/Sugar_doc_status|Do an analysis of which Sugar activities are lacking in documentation (e.g. Activity wiki page).]] || 20 || tonyforster || Quality Assurance || doc
|-
|Sugar on ARM || align=left | [[GoogleCodeIn2012/Sugar_ARM_status|Do an analysis of which Sugar activities are have issues running on non-x86 architectures (e.g. ARM).]] || 20 || holt, jerryvonau || Quality Assurance || arm
|-
|Sugar i18n || align=left | [[GoogleCodeIn2012/Sugar_i18n_status|Do an analysis of which Sugar activities are lacking i18n support.]] || 20 || lfaraone || Quality Assurance || i18n
|-
|Special Needs || align=left | [[GoogleCodeIn2012/Special_needs|Analyze Sugar from the point of view of special needs and make recommendations for improvements.]] || 40 || tch || User Interface || sugar
|-
|Touch UI || align=left | [[GoogleCodeIn2012/Touch_UI|Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch).]] || 40 || tonyforster || User Interface || sugar
|-
|On-screen Keyboard || align=left | [[GoogleCodeIn2012/Maliit|Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin).]] || 20 || cjl || User Interface || sugar
|-
|Accelerometer || align=left | [[GoogleCodeIn2012/Accelerometer|Think of ways to further leverage the use of an accelerometer in Sugar (and other common sensors found in portable computing devices).]] || 40 || tonyforster || User Interface || sugar
|-
|How are we doing? || align=left | [[GoogleCodeIn2012/Assessment|Assessing how Sugar is used by students. What is being learned? Survey students and teachers. How well does it deliver its goals?]] || 120 || claudiau tonyforster|| User Interface || learning
|-
|New Features || align=left | [[GoogleCodeIn2012/Feature_requests|Survey Sugar users to find out what UI features they want from Sugar in the future.]] || 120 || JZA || User Interface || future
|-
|Manage on-line credentials || align=left | [[GoogleCodeIn2012/OnlineAccounts|What's the best way to handle on-line credentials in Sugar (i.e.: Facebook Twitter Google)]] || 120 || rgs || User Interface || future
|-
| align=left | Sugar Network Contributor Hub look&feel|| align=left | [[GoogleCodeIn2012/Contributor_Hub|Design and users experience solutions for the Contributor Hub]] || ? || [[User:alsroot|alsroot]] || User Interface || sugar-network
|}

=== Mentors ===
;NOTES TO MENTORS:
:Please refer to [[GoogleCodeIn2012/Participate#Mentors]] for details regarding enrolling as a mentor.
:Please add yourself to the table above.
:Feel free to add new tasks to the table.

Depending on the project, we will assign multiple mentors from our various development and support teams.

* Chris Leonard - also org admin for GCI
* Walter Bender - also org admin for GCI
* Andrés Aguirre Dorelo
* Claudia Urrea
* Gonzalo Odiard
* Adam Holt
* Manuel Kaufmann
* Jeffrey Elkner
* John Tierney
* JerryV
* Alan Aguiar
* Luke Faraone
* Luis Gustavo Lira
* James Simmons
* Sam Greenfeld
* Tom Gilliard
* Martín Abente Lahaye
* Tony Forster

Possible additional mentors:

* Pacita Pena
* Rosamel Ramirez
* Sdenka Salas
* Simon Schampijer
* Manuel Quiñones
* Tony Forster
* Guzman Trinidad
* Sean Daly
* Mark Battley
* Bernie Innocenti
* Daniel Drake
* Raul Guttierrez Segales
* C Scott Ananian
et al.

[[Category: GCI2012]]

Google Code-In 2012/GCI2012 Brainstorming

2012-11-15T07:41:56Z

Jza: User experience

These are general concepts and areas of opportunity from which individual GCI2012 tasks can be developed and submitted. We need at least 5 tasks in each category, but beyond that we can have as many as we can think up.

The GCI categories are:

;Code: Tasks related to writing or refactoring code

;Documentation/Training: Tasks related to creating/editing documents and helping others learn more

;Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions

;Quality Assurance: Tasks related to testing and ensuring code is of high quality.

;User Interface: Tasks related to user experience research or user interface design and interaction

Examples of tasks created by other organizations participating in GCI2011 can be found here:

http://www.google-melange.com/gci/homepage/google/gci2011

=== Your ideas here ===

1) Activity Rescue (code)

There are abandoned activities that need to be ported to gtk3 or generally resuscitated. For example, some have been left behind on https://dev.laptop.org/git and not migrated to Sugar Labs hosting. Any migration should include i18n (if not already done). The spreadsheet linked below would be a good place to look for specific activities from ASLO.

2) Activity internationalization (code)

There are a number of activities in [activities.sugarlabs.org ASLO] that are either English only or Spanish only. Each one could of these could be listed as an individual task to refactor for i18n and submit for Pootle hosting. See [[File:ASLO_spreadheet_Oct_2012.ods]]

This idea is being fleshed out so it can be broken into individual taks on this page [[Google_Code-In_2012/Activity_i18n]].

3) Sugarizing good Python (or other) programs (code)

There are nice packages out there that could be readily ported to run as Sugar Activities by various means. Identifying a number of candidate packages to be sugarized as a GCI task would enhance the Sugar user experience in ways we have not had adequate time to do.

For example, it would be wonderful to empower "bootstrapping" of L10n on the XO from within Sugar itself by porting a version [http://translate.sourceforge.net/wiki/virtaal/index| Virtaal] as a Sugar Activity capable of reading and writing the PO/MO files already present in the source code (if coupled with glibc locale availability),

4) Infrastructure tasks (QA)

For example, I'll be creating a task for a new pootle-helper script to do msgfmt checks on PO files as part fo our regular Pootle cron jobs to prevent build-breakers in PO files from going unnoticed for more than 24 hours.

5) GTK-3 conversion (code, documentation)

We have migrated Sugar to GTK-3 and introspection, but many activities still use the old GTK-2 framework. Migrating these activities would help to stabilize our code base and make long-term maintenance more tractable. Any port should include i18n (if not already done). Also writing documentation about Sugar-specific issues with the porting process would be of great benefit. Rewriting out [[Development_Team/Almanac|Sugar Almanac]] to reflect GTK-3 would be a task as well. And updating [http://en.flossmanuals.net/make-your-own-sugar-activities/ Make Your Own Sugar Activities].

6) GST-1 conversion (code, documentation)

We are also migrating to Gstreamer 1.0, which better supports introspection. Lots of coding to be done to refactor existing programs. Also documentation about Sugar-specific issues.

6) User eXperience (code, documentation)

Visual improvements on some of the flagship activities such as enhancing the display with new graphics, visual aids functionality and improved sound effects.

[[Category: GCI2012]]