Changes

Jump to navigation Jump to search
46 bytes added ,  10:26, 3 November 2012
Line 15: Line 15:     
;Code: Tasks related to writing or refactoring code
 
;Code: Tasks related to writing or refactoring code
# New pootle-helper script for doing preventative [[GoogleCodeIn2012/MsgfmtChecker|msgfmt checks]]
+
# Write a new pootle-helper script for doing preventative [[GoogleCodeIn2012/MsgfmtChecker|msgfmt checks]].
# Sugarizing [[GoogleCodeIn2012/Virtaal|Virtaal]] for L10n "bootstrapping"
+
# Sugarize [[GoogleCodeIn2012/Virtaal|Virtaal]] for L10n "bootstrapping".
# Converting Sugar activities from [[Features/GTK3/Porting|GTK-2 to GTK-3]] framework
+
# Convert Sugar activities from [[Features/GTK3/Porting|GTK-2 to GTK-3]] framework.
# [[Features/Touch/Development|Enabling touch]] for activities that use direct keyboard input
+
# [[Features/Touch/Development|Enable touch]] for activities that use direct keyboard input.
# 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]
+
# 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].
    
;Documentation/Training: Tasks related to creating/editing documents and helping others learn more
 
;Documentation/Training: Tasks related to creating/editing documents and helping others learn more
# Write a [[GoogleCodeIn2012/Turtle Art|Turtle Art]] introductory tutorial
+
# Write a [[GoogleCodeIn2012/Turtle Art|Turtle Art]] introductory tutorial.
 
# 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?).
 
# 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?).
# Flesh out the [[Features/GTK3/Porting|GTK-2 to GTK-3]] conversion documentation to include more comprehensive coverage of Pango
+
# Flesh out the [[Features/GTK3/Porting|GTK-2 to GTK-3]] conversion documentation to include more comprehensive coverage of Pango.
# Better document the process of creating and using [[Sugar_on_a_Stick|Sugar on a Stick]], the LiveUSB version of Sugar
+
# Better document the process of creating and using [[Sugar_on_a_Stick|Sugar on a Stick]], the LiveUSB version of Sugar.
# Better document the process of running Sugar in a [[Sugar_Creation_Kit/VirtualBox|virtual machine (VM)]]
+
# Better document the process of running Sugar in a [[Sugar_Creation_Kit/VirtualBox|virtual machine (VM)]].
# Create videos on how to use Sugar and how to use core Sugar activities
+
# Create videos on how to use Sugar and how to use core Sugar activities.
    
;Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
 
;Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
 
# Research internationalization of [[GoogleCodeIn2012/SVG images| SVG images]].
 
# Research internationalization of [[GoogleCodeIn2012/SVG images| SVG images]].
# Research what metadata about Sugar activity usage would be helpful to teachers for assessment purposes.
+
# Research what [[Platform_Team/sugar-stats|metadata about Sugar activity usage]] would be helpful to teachers for assessment purposes.
# Research what opportunities/roadblocks exist for running Sugar in your local schools
+
# Research what opportunities/roadblocks exist for running Sugar in your local schools.
# Research the issues involved with porting Suagr to "the Cloud"
+
# Research the issues involved with porting Suagr to "the Cloud".
# Research the issues involved with porting Sugar to Android
+
# Research the issues involved with porting Sugar to Android.
    
;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.
# Do an analysis of which Sugar activities are being cared for; are orphaned
+
# Do an analysis of which Sugar activities are are orphaned.
# Do an analysis of which Sugar activities are touch-enabled or need modifications to support touch
+
# Do an analysis of which Sugar activities are touch-enabled or need modifications to support touch.
# Do an analysis of which Sugar activities are lacking in documentation (e.g., [[Activities|Activity wiki page]])
+
# Do an analysis of which Sugar activities are lacking in documentation (e.g., [[Activities|Activity wiki page]]).
# Do an analysis of which Sugar activities are have issues running on non-x86 architectures (e.g. ARM)
+
# Do an analysis of which Sugar activities are have issues running on non-x86 architectures (e.g. ARM).
# Do an analysis of which Sugar activities are lacking i18n support
+
# Do an analysis of which Sugar activities are lacking i18n support.
    
;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
# Sugar Touch: help us design the Sugar affordances for Sugar on tablet computers
+
# Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch).
# Development of a new Maliit keyboard files for additional languages (beyond those already developed by garycmartin)
+
# Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin).
# Think of ways to further leverage the use of an accelerometer in Sugar (a common sensor in many portable devices)
+
# Think of ways to further leverage the use of an accelerometer in Sugar (and other common sensors found in portable computing devices).
# Assessing how Sugar is used by students. What is learnt? Survey students and teachers. How well does it deliver its goals.
+
# Assessing how Sugar is used by students. What is learnt? Survey students and teachers. How well does it deliver its goals?
 
# Survey Sugar users to find out what UI features they want from Sugar in the future.
 
# Survey Sugar users to find out what UI features they want from Sugar in the future.
       
[[Category: GCI2012]]
 
[[Category: GCI2012]]

Navigation menu