Changes

2,362 bytes added ,  08:47, 18 November 2012
Line 25: Line 25:     
;Code: Tasks related to writing or refactoring code
 
;Code: Tasks related to writing or refactoring code
# Write a new pootle-helper script for doing preventative [[GoogleCodeIn2012/MsgfmtChecker|msgfmt checks]].
  −
# Sugarize [[GoogleCodeIn2012/Virtaal|Virtaal]] for L10n "bootstrapping".
  −
# Convert Sugar activities from [[Features/GTK3/Porting|GTK-2 to GTK-3]] framework.
  −
# [[Features/Touch/Development|Enable touch]] for activities that use direct keyboard input.
  −
# Implement the [[Features/Background_image_on_home_view|set background image on Home View Feature]].
  −
# 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].
  −
# Extend the Infoslicer activity to be able to leverage the local content in the Wikislices project.
  −
# Port the Python turtle module to GTK (currently it is QT)
  −
   
;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.
  −
# 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.
  −
# 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)]].
  −
# Create videos on how to use Sugar and how to use core Sugar activities.
  −
# Update and add new content to the manual [http://en.flossmanuals.net/make-your-own-sugar-activities/index/ Make Your Own Sugar Activities]! (details [[GoogleCodeIn2012/MYOSA|here]]).
  −
   
;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 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 is missing from Sugar that makes it unused by your local schools.
  −
# Research the issues involved with porting Sugar to "the Cloud".
  −
# Research the issues involved with porting Sugar to Android.
  −
# Research how Sugar Labs might leverage the work of [copyleftgames.org CGG] and CGG might leverage the work of Sugar Labs.
  −
   
;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 are orphaned.
+
;User Interface: Tasks related to user experience research or user interface design and interaction
# 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
+
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
# Analyze Sugar from the point of view of special needs and make recommendations for improvements.
+
|-style="background:#787878; color: white;"
# Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch).
+
! Project !! Title !! Category !! Notes
# 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 (and other common sensors found in portable computing devices).
+
! i18n || Pootle helper-script || code || Write a new pootle-helper script for doing preventative [[GoogleCodeIn2012/MsgfmtChecker|msgfmt checks]].
# 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.
+
! i18n || Sugarize Virtaal || code || Sugarize [[GoogleCodeIn2012/Virtaal|Virtaal]] for L10n "bootstrapping"
 +
|-
 +
! gtk3 || GTK2-to-GTK3 conversion || code || Convert Sugar activities from [[Features/GTK3/Porting|GTK-2 to GTK-3]] framework.
 +
|-
 +
! touch || On-screen keyboard support || code || [[Features/Touch/Development|Enable touch]] for activities that use direct keyboard input.
 +
|-
 +
! ui || Set background image || code || Implement the [[Features/Background_image_on_home_view|set background image on Home View Feature]].
 +
|-
 +
! toolkit || 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].
 +
|-
 +
! activity || Infoslicer enhancement (wikislices) || code || Extend the Infoslicer activity to be able to use the local content in the Wikislices project.
 +
|-
 +
! activity || Infoslicer enhancement (journal images) || code || Extend the Infoslicer activity to be able to use images from the Sugar Journal
 +
|-
 +
! activity || Sugarize Python Turtle module || code || Will require port of the Python turtle module to GTK (currently it is QT)
 +
|-
 +
! activity || Turtle Art tutorial || documentation/training || Write a [[GoogleCodeIn2012/Turtle Art|Turtle Art]] introductory tutorial
 +
|-
 +
! i18n || 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?).
 +
|-
 +
! gtk3 || 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.
 +
|-
 +
! soas || 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.
 +
|-
 +
! www || Create new Sugar Labs home page || documentation/training || We have some detailed designs of a new website that need to be implemented.
 +
|-
 +
! soas || Sugar VM || documentation/training || Better document the process of running Sugar in a [[Sugar_Creation_Kit/VirtualBox|virtual machine (VM)]].
 +
|-
 +
! doc || How to videos || documentation/training || Create videos on how to use Sugar and how to use core Sugar activities.
 +
|-
 +
! doc || How to create a collection || documentation/training || Create a guide to creating and using collections.
 +
|-
 +
! doc || Sugar FLOSS Manual || 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]! (details [[GoogleCodeIn2012/MYOSA|here]]).
 +
|-
 +
! i18n || SVG internationalization || outreach/research || Research internationalization of [[GoogleCodeIn2012/SVG images| SVG images]].
 +
|-
 +
! assessment || Sugar assessment tools || outreach/research || Research what [[Platform_Team/sugar-stats|metadata about Sugar activity usage]] would be helpful to teachers for assessment purposes.
 +
|-
 +
! outreach || Sugar in your school (opportunities) || outreach/research || Research what opportunities/roadblocks exist for running Sugar in your local schools.
 +
|-
 +
! outreach || Sugar in your school (roadblocks) || outreach/research || Research what is missing from Sugar that makes it unused by your local schools.
 +
|-
 +
! future || Sugar in the Cloud || outreach/research || Research the issues involved with porting Sugar to "the Cloud".
 +
|-
 +
! future || Sugar on Android || outreach/research || Research the issues involved with porting Sugar to Android.
 +
|-
 +
! 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.
 +
|-
 +
! maintenance || Orphaned activities || quality assurance || Do an analysis of which Sugar activities are are orphaned.
 +
|-
 +
! maintenance || Sugar Touch || quality assurance || Do an analysis of which Sugar activities are touch-enabled or need modifications to support touch.
 +
|-
 +
! doc || Sugar Documentation || quality assurance || Do an analysis of which Sugar activities are lacking in documentation (e.g. [[Activities|Activity wiki page]]).
 +
|-
 +
! arm || Sugar on ARM || quality assurance || Do an analysis of which Sugar activities are have issues running on non-x86 architectures (e.g. ARM).
 +
|-
 +
! i18n || Sugar i18n || quality assurance || Do an analysis of which Sugar activities are lacking i18n support.
 +
|-
 +
! ui || Special Needs || user interface || Analyze Sugar from the point of view of special needs and make recommendations for improvements.
 +
|-
 +
! ui || Touch || user interface || Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch).
 +
|-
 +
! ui || On-screen Keyboard || user interface || Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin).
 +
|-
 +
! ui || 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).
 +
|-
 +
! ui || Assessment || user interface || Assessing how Sugar is used by students. What is learnt? Survey students and teachers. How well does it deliver its goals?
 +
|-
 +
! ui || New Features || user interface || Survey Sugar users to find out what UI features they want from Sugar in the future.
 +
|}
    
=== Mentors ===
 
=== Mentors ===