Google Code-In 2012: Difference between revisions

Line 31:

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

# 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 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 Sugar to Android

;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 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 have issues running on non-x86 architectures (e.g. ARM)

#

# 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

# Sugar Touch

# Sugar Touch: help us design the Sugar affordances for Sugar on tablet computers

# Development of a new Maliit keyboard files for additional languages (beyond those already developed by garycmartin)

# ~~Leveraging~~ accelerometer ~~???~~

# Think of ways to further leverage the use of an accelerometer in Sugar (a common sensor in many portable devices)

# 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.

[[Category: GCI2012]]

@@ Line 31: / Line 31: @@
 ;Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
 # 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 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 Sugar to Android
 ;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 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 have issues running on non-x86 architectures (e.g. ARM)
-#
+# 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
-# Sugar Touch
+# Sugar Touch: help us design the Sugar affordances for Sugar on tablet computers
-# Development of a new Maliit keyboard files for additional languages  (beyond those already developed by garycmartin)
+# Development of a new Maliit keyboard files for additional languages (beyond those already developed by garycmartin)
-# Leveraging accelerometer ???
+# Think of ways to further leverage the use of an accelerometer in Sugar (a common sensor in many portable devices)
 # 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.
 [[Category: GCI2012]]