Changes

Jump to navigation Jump to search
4,359 bytes added ,  10:26, 30 November 2012
Line 36: Line 36:  
!Title !! Description !! Hours !! Mentor !! Category !! Tag
 
!Title !! Description !! Hours !! Mentor !! Category !! Tag
 
|-
 
|-
|[[GoogleCodeIn2012/MsgfmtChecker|Pootle helper-script]] || align=left | Write a new pootle-helper script for doing preventative msgfmt checks. || 20 || cjl || code || i18n
+
|Pootle helper-script || align=left | [[GoogleCodeIn2012/MsgfmtChecker|Write a new pootle-helper script for doing preventative msgfmt checks.]] || 20 || cjl || Code || i18n
 
|-
 
|-
|[[GoogleCodeIn2012/Virtaal|Sugarize Virtaal]] || align=left | Sugarize Virtaal for L10n bootstrapping || 60 || cjl || code || i18n
+
|Sugarize Virtaal || align=left | [[GoogleCodeIn2012/Virtaal|Sugarize Virtaal for L10n bootstrapping]] || 60 || cjl || Code || i18n
 
|-
 
|-
|[[GoogleCodeIn2012/GTK2-3|GTK2-to-GTK3 conversion]] || align=left | Convert Sugar activities from GTK-2 to GTK-3 framework. || 10 || || code || gtk3
+
|GTK2-to-GTK3 conversion || align=left | [[GoogleCodeIn2012/GTK2-3|Convert Sugar activities from GTK-2 to GTK-3 framework.]] || 10 || walterbender, humitos || Code || gtk3
 
|-
 
|-
|[[GoogleCodeIn2012/OSK|On-screen keyboard support]] || align=left | Enable touch for activities that use direct keyboard input. || 20 || || code || touch
+
|Set background image || align=left | [[GoogleCodeIn2012/Homeview_image|Implement the set background image on Home View Feature.]] || 40 || walterbender || Code || sugar
 
|-
 
|-
|[[GoogleCodeIn2012/Homeview_image|Set background image]] || align=left | 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
 
|-
 
|-
|[[GoogleCodeIn2012/Multiple_homeview|Multiple Homeviews]] || align=left | 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
 
|-
 
|-
|[[GoogleCodeIn2012/Toolbar_utils|Package toolbar utils]] || align=left | 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
 
|-
 
|-
|[[GoogleCodeIn2012/Infoslicer-wikislices|Infoslicer enhancement (wikislices)]] || align=left | 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
 
|-
 
|-
|[[GoogleCodeIn2012/Infoslicer-journal-images|Infoslicer enhancement (journal images)]] || align=left | 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
 
|-
 
|-
|[[GoogleCodeIn2012/PyTurtle|Sugarize Python Turtle module]] || align=left | Will require port of the Python turtle module to GTK (currently it is QT) || 60 || || 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
 
|-
 
|-
|[[GoogleCodeIn2012/Nutrition|Turtle Art nutrition]] || align=left | Further develop the prototype Turtle Nutrition plug-in into a stand-alone activity. || 60 || walterbender || 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
 
|-
 
|-
|[[GoogleCodeIn2012/Portfolio_videos|Portfolio videos]] || align=left | Add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation || 40 || 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
 
|-
 
|-
|[[GoogleCodeIn2012/Journal_view|Unified journal view]] || align=left | 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
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Turtle_plugins|Plugin support]] || align=left | Design a uniform plug-in bundle type and modify the activity installer to recognize this new type. || 80 || || 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
 
|-
 
|-
|[[GoogleCodeIn2012/End-user-mods|End-user modifications of Sugar source]] || align=left | 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
+
|Port GBrainy to Python || align=left | [[GoogleCodeIn2012/Gbrainy_port|GBrainy have many good logic games]] || 60 || gonzalo || Code || activity
 
|-
 
|-
|[[GoogleCodeIn2012/Collaborative_paint|Implement collaboration in Paint Activity]] || align=left | Paint Activity does not implement collaboration yet. || 40 || gonzalo || code || activity
+
|Stopwatch enhancement || align=left | [http://bugs.sugarlabs.org/ticket/2976 Stopwatch must use the game keys] || 5 || walterbender, humitos || Code  || StopWatch
 
|-
 
|-
|[[GoogleCodeIn2012/Fototoon_presentations|Implement a presentation mode in Fototoon]] || align=left | Fototoon should have a view to edit and view one cell at a time using the full screen. || 40 || gonzalo || code || activity
+
|Write activity enhancement || align=left | [http://bugs.sugarlabs.org/ticket/1690 Retain font and size in Write Activity] || 5 || gonzalo || Code  || Write
 
|-
 
|-
|[[GoogleCodeIn2012/Gbrainy_port|Port GBrainy to Python]] || align=left | GBrainy have many good logic games || 60 || || code || activity
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Mallard|Implement help mechanism for activities using Mallard]] || align=left | 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
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Turtle_Art|Turtle Art tutorial]] || align=left | Write a Turtle Art introductory tutorial || 60 || walterbender || documentation/training || activity
+
|Calculate activity enhancement 2 || align=left | [http://bugs.sugarlabs.org/ticket/2386 Calculate error point reporting] || 5 || walterbender, humitos || Code  || Calculate
 
|-
 
|-
|[[GoogleCodeIn2012/I18n_screeshots|Multilanguage screen-shots]] || align=left | 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
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/GTK3_guide|GTK3 conversion guide]] || align=left | Flesh out the GTK-2 to GTK-3 conversion documentation to include more comprehensive coverage of Pango. || 40 || || documentation/training || gtk3
+
|Calculate activity enhancement 4 || align=left | [http://bugs.sugarlabs.org/ticket/2698 Calculate allows default variables to be redefined] || 5 || walterbender, humitos || Code  || Calculate
 
|-
 
|-
|[[GoogleCodeIn2012/SOAS_guide|Sugar on a Stick guide]] || align=left | Better document the process of creating and using Sugar on a Stick the LiveUSB version of Sugar. || 40 || || documentation/training || soas
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/SugarLabs.org|Create new Sugar Labs home page]] || align=left | We have some detailed designs of a new website that need to be implemented. || 120 || || documentation/training || www
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/VM|Sugar VM]] || align=left | Better document the process of running Sugar in a virtual machine (VM). || 40 || || documentation/training || soas
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Videos|How-to videos]] || align=left | Create videos on how to use Sugar and how to use core Sugar activities. || 20 || || documentation/training || doc
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Collections|How to create a collection]] || align=left | Create a guide to creating and using collections. || 5 || || documentation/training || doc
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/FLOSSMANUAL_Sugar|Sugar FLOSS Manual]] || align=left | Update and add new content to the manual Sugar Manual || 20 || || documentation/training || doc
+
|On-screen keyboard support || align=left | [[GoogleCodeIn2012/OSK|Enable touch for activities that use direct keyboard input.]] || 20 || walterbender || Code || touch
 
|-
 
|-
|[[GoogleCodeIn2012/MYOSA|Make your own Sugar activity]] || align=left | Update and add new content to the manual Make Your Own Sugar Activities || 40 || nicestep || documentation/training || doc
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/SVG_images|SVG internationalization]] || align=left | Research internationalization of SVG images. || 120 ||  || outreach/research || i18n
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Assessment_tools|Sugar assessment tools]] || align=left | Research what metadata about Sugar activity usage would be helpful to teachers for assessment purposes. || 40 || claudiau, walterbender || outreach/research || assessment
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Sugar_at_your_school|Sugar in your school (opportunities)]] || align=left | Research what opportunities/roadblocks exist for running Sugar in your local schools. || 40 || claudiau || outreach/research || outreach
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Sugar_roadblocks|Sugar in your school (roadblocks)]] || align=left | Research what is missing from Sugar that makes it unused by your local schools. || 40 || claudiau || outreach/research || outreach
+
|Palette doesn't appear bug || align=left | [http://bugs.sugarlabs.org/ticket/4284 Activity Palette does not appear] || 48 || walterbender || Code || sugar
 
|-
 
|-
|[[GoogleCodeIn2012/Sugar_in_the_cloud|Sugar in the Cloud]] || align=left | Research the issues involved with porting Sugar to the Cloud. || 60 || || outreach/research || future
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Sugar_on_Android|Sugar on Android]] || align=left | Research the issues involved with porting Sugar to Android. || 120 || aguirrea || outreach/research || future
+
|Turtle Art tutorial || align=left | [[GoogleCodeIn2012/Turtle_Art|Write a Turtle Art introductory tutorial]] || 60 || tonyforster || Documentation/Training || activity
 
|-
 
|-
|[[GoogleCodeIn2012/Sugar_and_CGG|Copyleft Games]] || align=left | Research how Sugar Labs might leverage the work of copyleftgames.org and CGG might leverage the work of Sugar Labs. || 20 || || outreach/research || 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
 
|-
 
|-
|[[GoogleCodeIn2012/Python3|Port to Python3]] || align=left | Research the issues we will encounter in porting to Python 3 || 40 || || outreach/research || future
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/OnlineAccounts|Manage on-line credentials]] || align=left | What's the best way to handle on-line credentials in Sugar (i.e.: Facebook Twitter Google) || 120 || || outreach/research || future
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Sugar_orphan_status|Orphaned activities]] || align=left | Do an analysis of which Sugar activities are are orphaned. || 20 || || quality assurance || maintenance
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Sugar_touch_status|Sugar Touch]] || align=left | Do an analysis of which Sugar activities are touch-enabled or need modifications to support touch. || 20 ||  || quality assurance || maintenance
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Sugar_doc_status|Sugar Documentation]] || align=left | Do an analysis of which Sugar activities are lacking in documentation (e.g. Activity wiki page). || 20 || || quality assurance || doc
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Sugar_ARM_status|Sugar on ARM]] || align=left | Do an analysis of which Sugar activities are have issues running on non-x86 architectures (e.g. ARM). || 20 || holt, jerryvonau || quality assurance || arm
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Sugar_i18n_status|Sugar i18n]] || align=left | Do an analysis of which Sugar activities are lacking i18n support. || 20 || || quality assurance || i18n
+
|Sugar VM || align=left | [[GoogleCodeIn2012/VM|Better document the process of running Sugar in a virtual machine (VM).]] || 40 || satellit || Documentation/Training || soas
 
|-
 
|-
|[[GoogleCodeIn2012/Special_needs|Special Needs]] || align=left | Analyze Sugar from the point of view of special needs and make recommendations for improvements. || 40 || || user interface || sugar
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Touch_UI|Touch UI]] || align=left | Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch). || 40 ||  || user interface || sugar
+
|How to create a collection || align=left | [[GoogleCodeIn2012/Collections|Create a guide to creating and using collections.]] || 5 || JZA || Documentation/Training || doc
 
|-
 
|-
|[[GoogleCodeIn2012/Maliit|On-screen Keyboard]] || align=left | Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin). || 20 || cjl, garymartin || user interface || sugar
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Accelerometer|Accelerometer]] || align=left | Think of ways to further leverage the use of an accelerometer in Sugar (and other common sensors found in portable computing devices). || 40 || || user interface || sugar
+
|Sugar FLOSS Manual || align=left | [[GoogleCodeIn2012/FLOSSMANUAL_Sugar|Update and add new content to the manual Sugar Manual]] || 20 || JZA || Documentation/Training || doc
 
|-
 
|-
|[[GoogleCodeIn2012/Assessment|How are we doing?]] || align=left | Assessing how Sugar is used by students. What is being learned? Survey students and teachers. How well does it deliver its goals? || 120 || claudiau || user interface || learning
+
|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
 
|-
 
|-
|[[GoogleCodeIn2012/Feature_requests|New Features]] || align=left | Survey Sugar users to find out what UI features they want from Sugar in the future. || 120 || || user interface || future
+
|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
 
|}
 
|}
   Line 142: Line 180:     
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
+
 
* Walter Bender
+
* Chris Leonard - also org admin for GCI
 +
* Walter Bender - also org admin for GCI
 +
* 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