Changes

Jump to navigation Jump to search
4,986 bytes added ,  10:26, 30 November 2012
Line 12: Line 12:     
http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions
 
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 ===
 
=== Why we are participating ===
Line 23: Line 25:  
=== Tasks ===
 
=== 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.)
 
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.)
  −
'''Key''':
      
;Code: Tasks related to writing or refactoring code
 
;Code: Tasks related to writing or refactoring code
Line 31: Line 31:  
;Quality Assurance: Tasks related to testing and ensuring code is of high quality.
 
;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
 
;User Interface: Tasks related to user experience research or user interface design and interaction
  −
([[File:GCI.csv|CSV version of the Task List]] Please make your edits below, they will be migrated to the CSV list and uploaded to the GCI site.)
      
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
 
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
+
|-style="background:#787878; color: white;"
! Project !! Title !! Category !! Notes
+
!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
 
|-
 
|-
! i18n || [[GoogleCodeIn2012/MsgfmtChecker|Pootle helper-script]] || code || Write a new pootle-helper script for doing preventative msgfmt checks.
+
|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
 
|-
 
|-
! i18n || [[GoogleCodeIn2012/Virtaal|Sugarize Virtaal]] || code || Sugarize Virtaal for L10n "bootstrapping"
+
|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
 
|-
 
|-
! gtk3 || [[GoogleCodeIn2012/GTK2-3|GTK2-to-GTK3 conversion]] || code || Convert Sugar activities from [[Features/GTK3/Porting|GTK-2 to GTK-3]] framework.
+
|Port GBrainy to Python || align=left | [[GoogleCodeIn2012/Gbrainy_port|GBrainy have many good logic games]] || 60 || gonzalo || Code || activity
 
|-
 
|-
! touch || [[GoogleCodeIn2012/OSK|On-screen keyboard support]] || code || [[Features/Touch/Development|Enable touch]] for activities that use direct keyboard input.
+
|Stopwatch enhancement || align=left | [http://bugs.sugarlabs.org/ticket/2976 Stopwatch must use the game keys] || 5 || walterbender, humitos || Code  || StopWatch
 
|-
 
|-
! sugar || [[GoogleCodeIn2012/Homeview_image|Set background image]] || code || Implement the [[Features/Background_image_on_home_view|set background image on Home View Feature]].
+
|Write activity enhancement || align=left | [http://bugs.sugarlabs.org/ticket/1690 Retain font and size in Write Activity] || 5 || gonzalo || Code  || Write
 
|-
 
|-
! sugar || [[GoogleCodeIn2012/Multiple_homeview|Multiple Homeviews]] || code || Implement the [[Features/Multiple_home_views|multiple homeview]] feature
+
|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
 
|-
 
|-
! toolkit || [[GoogleCodeIn2012/Toolbar_utils|Package toolbar utils]] || code || Package Sugar activity utilities (e.g. [http://git.sugarlabs.org/portfolio/portfolio/blobs/master/toolbar_utils.py]) for inclusion in the [http://git.sugarlabs.org/sugar-toolkit-gtk3 Sugar toolkit].
+
|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
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Infoslicer-wikislices|Infoslicer enhancement (wikislices)]] || code || Extend the Infoslicer activity to be able to use the local content in the Wikislices project.
+
|Calculate activity enhancement 2 || align=left | [http://bugs.sugarlabs.org/ticket/2386 Calculate error point reporting] || 5 || walterbender, humitos || Code  || Calculate
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Infoslicer-journal-images|Infoslicer enhancement (journal images)]] || code || Extend the Infoslicer activity to be able to use images from the Sugar Journal
+
|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
 
|-
 
|-
! activity || [[GoogleCodeIn2012/PyTurtle|Sugarize Python Turtle module]] || code || Will require port of the Python turtle module to GTK (currently it is QT)
+
|Calculate activity enhancement 4 || align=left | [http://bugs.sugarlabs.org/ticket/2698 Calculate allows default variables to be redefined] || 5 || walterbender, humitos || Code  || Calculate
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Nutrition|Turtle Art nutrition]] || code || Further develop the prototype Turtle Nutrition plug-in into a stand-alone activity.
+
|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
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Portfolio videos|Portfolio videos]] || code || Add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation
+
|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
 
|-
 
|-
! sugar || [[GoogleCodeIn2012/Journal view|Unified journal view]] || code || Rather than viewing the details of a Journal entry on a separate page, make the details appear in an expandable in-line format
+
|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
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Turtle plugins|Plugin support]] || code || Dsign a uniform plug-in bundle type and modify the activity installer to recognize this new type.
+
|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
 
|-
 
|-
! sugar || [[GoogleCodeIn2012/End-user-mods|End-user modifications of Sugar source]] || code || We have a mechanism for viewing the Sugar toolkit source, but no such convenient way for making changes without risking messing up the system.
+
|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
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Collaborative paint|Implement collaboration in Paint Activity]] || code || Paint Activity does not implement collaboration yet.
+
|On-screen keyboard support || align=left | [[GoogleCodeIn2012/OSK|Enable touch for activities that use direct keyboard input.]] || 20 || walterbender || Code || touch
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Fototoon presentations|Implement a presentation mode in Fototoon]] || code ||  Fototoon should have a view to edit and view one cell at a time using the full screen.
+
|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
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Gbrainy port|Port GBrainy to Python]] || code || GBrainy have many good logic games, but is programmed in Mono. It would nice to have a native Python version.
+
|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
 
|-
 
|-
! sugar || [[GoogleCodeIn2012/Mallard|Implement help mechanism for activities using Mallard]] || code || [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.
+
|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
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Turtle Art|Turtle Art tutorial]] || documentation/training || Write a Turtle Art introductory tutorial
+
|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
 
|-
 
|-
! i18n || [[GoogleCodeIn2012/I18n_screeshots|Multilanguage screenshots]] || documentaton/training || 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?).
+
|Palette doesn't appear bug || align=left | [http://bugs.sugarlabs.org/ticket/4284 Activity Palette does not appear] || 48 || walterbender || Code || sugar
 
|-
 
|-
! gtk3 || [[GoogleCodeIn2012/GTK3_guide|GTK3 conversion guide]] || documentation/training || Flesh out the [[Features/GTK3/Porting|GTK-2 to GTK-3]] conversion documentation to include more comprehensive coverage of Pango.
+
|Web lightbox feature || align=left | As part of our new website design, we need a "lightbox" feature. This task is to program that feature. See [//www.christianmarcschmidt.com/projects/sugarlabs/index.html] for details || 60 || walterbender || Code || www
 
|-
 
|-
! soas || [[GoogleCodeIn2012/SOAS_guide|Sugar on a Stick guide]] || documentation/training || Better document the process of creating and using [[Sugar_on_a_Stick|Sugar on a Stick]] the LiveUSB version of Sugar.
+
|Turtle Art tutorial || align=left | [[GoogleCodeIn2012/Turtle_Art|Write a Turtle Art introductory tutorial]] || 60 || tonyforster || Documentation/Training || activity
 
|-
 
|-
! www || [[GoogleCodeIn2012/SugarLabs.org|Create new Sugar Labs home page]] || documentation/training || We have some detailed designs of a new website that need to be implemented.
+
|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
 
|-
 
|-
! soas || [[GoogleCodeIn2012/VM|Sugar VM]] || documentation/training || Better document the process of running Sugar in a [[Sugar_Creation_Kit/VirtualBox|virtual machine (VM)]].
+
|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
 
|-
 
|-
! doc || [[GoogleCodeIn2012/Videos|How-to videos]] || documentation/training || Create videos on how to use Sugar and how to use core Sugar activities.
+
|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
 
|-
 
|-
! doc || [[GoogleCodeIn2012/Collections|How to create a collection]] || documentation/training || Create a guide to creating and using collections.
+
|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
 
|-
 
|-
! doc || [[GoogleCodeIn2012/FLOSSMANUAL_Sugar|Sugar FLOSS Manual]] || documentation/training || Update and add new content to the manual [http://en.flossmanuals.net/sugar/index/ Sugar Manual]
+
|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
 
|-
 
|-
! doc || [[GoogleCodeIn2012/MYOSA|Make your own Sugar activityl]] || documentation/training || Update and add new content to the manual [http://en.flossmanuals.net/make-your-own-sugar-activities/index/ Make Your Own Sugar Activities]
+
|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
 
|-
 
|-
! i18n || [[GoogleCodeIn2012/SVG images|SVG internationalization]] || outreach/research || Research internationalization of SVG images.
+
|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
 
|-
 
|-
! assessment || [[GoogleCodeIn2012/Assessment_tools|Sugar assessment tools]] || outreach/research || Research what [[Platform_Team/sugar-stats|metadata about Sugar activity usage]] would be helpful to teachers for assessment purposes.
+
|Sugar VM || align=left | [[GoogleCodeIn2012/VM|Better document the process of running Sugar in a virtual machine (VM).]] || 40 || satellit || Documentation/Training || soas
 
|-
 
|-
! outreach || [[GoogleCodeIn2012/Sugar_at_your_school|Sugar in your school (opportunities)]] || outreach/research || Research what opportunities/roadblocks exist for running Sugar in your local schools.
+
|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
 
|-
 
|-
! outreach || [[GoogleCodeIn2012/Sugar_roadblocks|Sugar in your school (roadblocks)]] || outreach/research || Research what is missing from Sugar that makes it unused by your local schools.
+
|How to create a collection || align=left | [[GoogleCodeIn2012/Collections|Create a guide to creating and using collections.]] || 5 || JZA || Documentation/Training || doc
 
|-
 
|-
! future || [[GoogleCodeIn2012/Sugar_in_the_cloud|Sugar in the Cloud]] || outreach/research || Research the issues involved with porting Sugar to "the Cloud".
+
|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
 
|-
 
|-
! future || [[GoogleCodeIn2012/Sugar_on_Android|Sugar on Android]] || outreach/research || Research the issues involved with porting Sugar to Android.
+
|Sugar FLOSS Manual || align=left | [[GoogleCodeIn2012/FLOSSMANUAL_Sugar|Update and add new content to the manual Sugar Manual]] || 20 || JZA || Documentation/Training || doc
 
|-
 
|-
! cgg || [[GoogleCodeIn2012/Sugar_and_CGG|Copyleft Games]] || outreach/research || Research how Sugar Labs might leverage the work of [copyleftgames.org CGG] and CGG might leverage the work of Sugar Labs.
+
|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
|-py3kPy
  −
! future || [[GoogleCodeIn2012/Python3|Port to Python3]] || outreach/research || Research the issues we will encounter in [http://lwn.net/Articles/523465/ porting to Python 3]
   
|-
 
|-
! future || [[GoogleCodeIn2012/OnlineAccounts|Manage online credentials]] || outreach/research || What's the best way to handle online credentials in Sugar (i.e.: Facebook, Twitter, Google Plus, accounts)? [http://developer.gnome.org/goa/stable/ Gnome Online Accounts] maybe?
+
|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
 
|-
 
|-
! maintenance || [[GoogleCodeIn2012/Sugar_orphan_status|Orphaned activities]] || quality assurance || Do an analysis of which Sugar activities are are orphaned.
+
|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
 
|-
 
|-
! maintenance || [[GoogleCodeIn2012/Sugar_touch_status|Sugar Touch]] || quality assurance || Do an analysis of which Sugar activities are touch-enabled or need modifications to support touch.
+
|SVG internationalization || align=left | [[GoogleCodeIn2012/SVG_images|Research internationalization of SVG images.]] || 120 || JZA || Outreach/Research || i18n
 
|-
 
|-
! doc || [[GoogleCodeIn2012/Sugar_doc_status|Sugar Documentation]] || quality assurance || Do an analysis of which Sugar activities are lacking in documentation (e.g. [[Activities|Activity wiki page]]).
+
|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
 
|-
 
|-
! arm || [[GoogleCodeIn2012/Sugar_ARM_status|Sugar on ARM]] || quality assurance || Do an analysis of which Sugar activities are have issues running on non-x86 architectures (e.g. ARM).
+
|Sugar on Android || align=left | [[GoogleCodeIn2012/Sugar_on_Android|Research the issues involved with porting Sugar to Android.]] || 120 || aguirrea || Outreach/Research || future
 
|-
 
|-
! i18n || [[GoogleCodeIn2012/Sugar_i18n_status|Sugar i18n]] || quality assurance || Do an analysis of which Sugar activities are lacking i18n support.
+
|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
 
|-
 
|-
! ui || [[GoogleCodeIn2012/Special_needs|Special Needs]] || user interface || Analyze Sugar from the point of view of special needs and make recommendations for improvements.
+
|Port to Python3 || align=left | [[GoogleCodeIn2012/Python3|Research the issues we will encounter in porting to Python 3]] || 40 || || Outreach/Research || future
 
|-
 
|-
! ui || [[GoogleCodeIn2012/Touch_UI|Touch UI]] || user interface || Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch).
+
|Orphaned activities || align=left | [[GoogleCodeIn2012/Sugar_orphan_status|Do an analysis of which Sugar activities are are orphaned.]] || 20 || gonzalo || Quality Assurance || maintenance
 
|-
 
|-
! ui || [[GoogleCodeIn2012/Maliit|On-screen Keyboard]] || user interface || Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin).
+
|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
 
|-
 
|-
! ui || [[GoogleCodeIn2012/Accelerometer|Accelerometer]] || user interface || Think of ways to further leverage the use of an accelerometer in Sugar (and other common sensors found in portable computing devices).
+
|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
 
|-
 
|-
! ui || [[GoogleCodeIn2012/Assessment|Assessment]] || user interface || Assessing how Sugar is used by students. What is being learned? Survey students and teachers. How well does it deliver its goals?
+
|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
 
|-
 
|-
! ui || [[GoogleCodeIn2012/Feature_requests|New Features]] || user interface || Survey Sugar users to find out what UI features they want from Sugar in the future.
+
|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 ===
 
=== 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.
   −
'''NOTE TO MENTORS: Please create an account on [https://google-melange.appspot.com/gci/homepage/google/gci2012] and fill out the Request to be a Mentor form.'''
+
Depending on the project, we will assign multiple mentors from our various development and support teams.
   −
Depending on the project, we will assign multiple mentors from our various development and support teams.
+
* Chris Leonard - also org admin for GCI
* Chris Leonard
+
* Walter Bender - also org admin for GCI
* Walter Bender
+
* Andrés Aguirre Dorelo
 
* Claudia Urrea
 
* 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
 
* Pacita Pena
 
* Rosamel Ramirez
 
* Rosamel Ramirez
 
* Sdenka Salas
 
* Sdenka Salas
* Sam Greenfeld
  −
* Gonzalo Odiard
   
* Simon Schampijer
 
* Simon Schampijer
 
* Manuel Quiñones
 
* Manuel Quiñones
 
* Tony Forster
 
* Tony Forster
 
* Guzman Trinidad
 
* Guzman Trinidad
* Adam Holt
   
* Sean Daly
 
* Sean Daly
* Manuel Kaufmann
   
* Mark Battley
 
* Mark Battley
* Alan Aguiar
   
* Bernie Innocenti
 
* Bernie Innocenti
 
* Daniel Drake
 
* Daniel Drake
* Martin Abente
   
* Raul Guttierrez Segales
 
* Raul Guttierrez Segales
 
* C Scott Ananian
 
* C Scott Ananian
* James Simmons
  −
* Luis Gustavo Lira
  −
* Andres Aguirre
   
et al.
 
et al.
 +
       
[[Category: GCI2012]]
 
[[Category: GCI2012]]

Navigation menu