Changes

Jump to navigation Jump to search
587 bytes added ,  11:28, 19 November 2012
Line 38: Line 38:  
! Project !! Title !! Category !! Notes
 
! Project !! Title !! Category !! Notes
 
|-
 
|-
! i18n || [[GoogleCodeIn2012/MsgfmtChecker|Pootle helper-script]] || code || Write a new pootle-helper script for doing preventative msgfmt checks.
+
! i18n || [[GoogleCodeIn2012/MsgfmtChecker|Pootle helper-script]] || code || align=left| Write a new pootle-helper script for doing preventative msgfmt checks.
 
|-
 
|-
! i18n || [[GoogleCodeIn2012/Virtaal|Sugarize Virtaal]] || code || Sugarize Virtaal for L10n "bootstrapping"
+
! i18n || [[GoogleCodeIn2012/Virtaal|Sugarize Virtaal]] || code || align=left| Sugarize Virtaal for L10n "bootstrapping"
 
|-
 
|-
! gtk3 || [[GoogleCodeIn2012/GTK2-3|GTK2-to-GTK3 conversion]] || code || Convert Sugar activities from [[Features/GTK3/Porting|GTK-2 to GTK-3]] framework.
+
! gtk3 || [[GoogleCodeIn2012/GTK2-3|GTK2-to-GTK3 conversion]] || code || align=left|Convert Sugar activities from [[Features/GTK3/Porting|GTK-2 to GTK-3]] framework.
 
|-
 
|-
! touch || [[GoogleCodeIn2012/OSK|On-screen keyboard support]] || code || [[Features/Touch/Development|Enable touch]] for activities that use direct keyboard input.
+
! touch || [[GoogleCodeIn2012/OSK|On-screen keyboard support]] || code || align=left| [[Features/Touch/Development|Enable touch]] for activities that use direct keyboard input.
 
|-
 
|-
! sugar || [[GoogleCodeIn2012/Homeview_image|Set background image]] || code || Implement the [[Features/Background_image_on_home_view|set background image on Home View Feature]].
+
! sugar || [[GoogleCodeIn2012/Homeview_image|Set background image]] || code || align=left| Implement the [[Features/Background_image_on_home_view|set background image on Home View Feature]].
 
|-
 
|-
! sugar || [[GoogleCodeIn2012/Multiple_homeview|Multiple Homeviews]] || code || Implement the [[Features/Multiple_home_views|multiple homeview]] feature
+
! sugar || [[GoogleCodeIn2012/Multiple_homeview|Multiple Homeviews]] || code || align=left| Implement the [[Features/Multiple_home_views|multiple homeview]] feature
 
|-
 
|-
! 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].
+
! toolkit || [[GoogleCodeIn2012/Toolbar_utils|Package toolbar utils]] || code || align=left| 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 || [[GoogleCodeIn2012/Infoslicer-wikislices|Infoslicer enhancement (wikislices)]] || code || Extend the Infoslicer activity to be able to use the local content in the Wikislices project.
+
! activity || [[GoogleCodeIn2012/Infoslicer-wikislices|Infoslicer enhancement (wikislices)]] || code || align=left| Extend the Infoslicer activity to be able to use the local content in the Wikislices project.
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Infoslicer-journal-images|Infoslicer enhancement (journal images)]] || code || Extend the Infoslicer activity to be able to use images from the Sugar Journal
+
! activity || [[GoogleCodeIn2012/Infoslicer-journal-images|Infoslicer enhancement (journal images)]] || code || align=left| Extend the Infoslicer activity to be able to use images from the Sugar Journal
 
|-
 
|-
! activity || [[GoogleCodeIn2012/PyTurtle|Sugarize Python Turtle module]] || code || Will require port of the Python turtle module to GTK (currently it is QT)
+
! activity || [[GoogleCodeIn2012/PyTurtle|Sugarize Python Turtle module]] || code || align=left| Will require port of the Python turtle module to GTK (currently it is QT)
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Nutrition|Turtle Art nutrition]] || code || Further develop the prototype Turtle Nutrition plug-in into a stand-alone activity.
+
! activity || [[GoogleCodeIn2012/Nutrition|Turtle Art nutrition]] || code || align=left| Further develop the prototype Turtle Nutrition plug-in into a stand-alone activity.
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Portfolio videos|Portfolio videos]] || code || Add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation
+
! activity || [[GoogleCodeIn2012/Portfolio videos|Portfolio videos]] || code || align=left| Add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation
 
|-
 
|-
! 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
+
! sugar || [[GoogleCodeIn2012/Journal view|Unified journal view]] || code || 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
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Turtle plugins|Plugin support]] || code || Design a uniform plug-in bundle type and modify the activity installer to recognize this new type.
+
! activity || [[GoogleCodeIn2012/Turtle plugins|Plugin support]] || code || align=left| Design a uniform plug-in bundle type and modify the activity installer to recognize this new type.
 
|-
 
|-
! 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.
+
! sugar || [[GoogleCodeIn2012/End-user-mods|End-user modifications of Sugar source]] || code || 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.
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Collaborative paint|Implement collaboration in Paint Activity]] || code || Paint Activity does not implement collaboration yet.
+
! activity || [[GoogleCodeIn2012/Collaborative paint|Implement collaboration in Paint Activity]] || code || align=left| Paint Activity does not implement collaboration yet.
 
|-
 
|-
! 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.
+
! activity || [[GoogleCodeIn2012/Fototoon presentations|Implement a presentation mode in Fototoon]] || code || align=left|  Fototoon should have a view to edit and view one cell at a time using the full screen.
 
|-
 
|-
! 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.
+
! activity || [[GoogleCodeIn2012/Gbrainy port|Port GBrainy to Python]] || code || align=left| GBrainy have many good logic games, but is programmed in Mono. It would nice to have a native Python version.
 
|-
 
|-
! 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.
+
! sugar || [[GoogleCodeIn2012/Mallard|Implement help mechanism for activities using Mallard]] || code || align=left| [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.
 
|-
 
|-
! activity || [[GoogleCodeIn2012/Turtle Art|Turtle Art tutorial]] || documentation/training || Write a Turtle Art introductory tutorial
+
! activity || [[GoogleCodeIn2012/Turtle Art|Turtle Art tutorial]] || documentation/training || align=left| Write a Turtle Art introductory tutorial
 
|-
 
|-
! 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?).
+
! i18n || [[GoogleCodeIn2012/I18n_screeshots|Multilanguage screenshots]] || documentaton/training || 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?).
 
|-
 
|-
! 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.
+
! gtk3 || [[GoogleCodeIn2012/GTK3_guide|GTK3 conversion guide]] || documentation/training || align=left| Flesh out the [[Features/GTK3/Porting|GTK-2 to GTK-3]] conversion documentation to include more comprehensive coverage of Pango.
 
|-
 
|-
! 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.
+
! soas || [[GoogleCodeIn2012/SOAS_guide|Sugar on a Stick guide]] || documentation/training || align=left| Better document the process of creating and using [[Sugar_on_a_Stick|Sugar on a Stick]] the LiveUSB version of Sugar.
 
|-
 
|-
! 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.
+
! www || [[GoogleCodeIn2012/SugarLabs.org|Create new Sugar Labs home page]] || documentation/training || align=left| We have some detailed designs of a new website that need to be implemented.
 
|-
 
|-
! soas || [[GoogleCodeIn2012/VM|Sugar VM]] || documentation/training || Better document the process of running Sugar in a [[Sugar_Creation_Kit/VirtualBox|virtual machine (VM)]].
+
! soas || [[GoogleCodeIn2012/VM|Sugar VM]] || documentation/training || align=left| Better document the process of running Sugar in a [[Sugar_Creation_Kit/VirtualBox|virtual machine (VM)]].
 
|-
 
|-
! doc || [[GoogleCodeIn2012/Videos|How-to videos]] || documentation/training || Create videos on how to use Sugar and how to use core Sugar activities.
+
! doc || [[GoogleCodeIn2012/Videos|How-to videos]] || documentation/training || align=left| Create videos on how to use Sugar and how to use core Sugar activities.
 
|-
 
|-
! doc || [[GoogleCodeIn2012/Collections|How to create a collection]] || documentation/training || Create a guide to creating and using collections.
+
! doc || [[GoogleCodeIn2012/Collections|How to create a collection]] || documentation/training || align=left| Create a guide to creating and using collections.
 
|-
 
|-
! 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]
+
! doc || [[GoogleCodeIn2012/FLOSSMANUAL_Sugar|Sugar FLOSS Manual]] || documentation/training || align=left| Update and add new content to the manual [http://en.flossmanuals.net/sugar/index/ Sugar Manual]
 
|-
 
|-
! 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]
+
! doc || [[GoogleCodeIn2012/MYOSA|Make your own Sugar activityl]] || documentation/training || align=left| Update and add new content to the manual [http://en.flossmanuals.net/make-your-own-sugar-activities/index/ Make Your Own Sugar Activities]
 
|-
 
|-
! i18n || [[GoogleCodeIn2012/SVG images|SVG internationalization]] || outreach/research || Research internationalization of SVG images.
+
! i18n || [[GoogleCodeIn2012/SVG images|SVG internationalization]] || outreach/research || align=left| Research internationalization of SVG images.
 
|-
 
|-
! 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.
+
! assessment || [[GoogleCodeIn2012/Assessment_tools|Sugar assessment tools]] || outreach/research || align=left| Research what [[Platform_Team/sugar-stats|metadata about Sugar activity usage]] would be helpful to teachers for assessment purposes.
 
|-
 
|-
! 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.
+
! outreach || [[GoogleCodeIn2012/Sugar_at_your_school|Sugar in your school (opportunities)]] || outreach/research || align=left| Research what opportunities/roadblocks exist for running Sugar in your local schools.
 
|-
 
|-
! 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.
+
! outreach || [[GoogleCodeIn2012/Sugar_roadblocks|Sugar in your school (roadblocks)]] || outreach/research || align=left| Research what is missing from Sugar that makes it unused by your local schools.
 
|-
 
|-
! future || [[GoogleCodeIn2012/Sugar_in_the_cloud|Sugar in the Cloud]] || outreach/research || Research the issues involved with porting Sugar to "the Cloud".
+
! future || [[GoogleCodeIn2012/Sugar_in_the_cloud|Sugar in the Cloud]] || outreach/research || align=left| Research the issues involved with porting Sugar to "the Cloud".
 
|-
 
|-
! future || [[GoogleCodeIn2012/Sugar_on_Android|Sugar on Android]] || outreach/research || Research the issues involved with porting Sugar to Android.
+
! future || [[GoogleCodeIn2012/Sugar_on_Android|Sugar on Android]] || outreach/research || align=left| Research the issues involved with porting Sugar to Android.
 
|-
 
|-
! activity || [[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.
+
! activity || [[GoogleCodeIn2012/Sugar_and_CGG|Copyleft Games]] || outreach/research || align=left| Research how Sugar Labs might leverage the work of [copyleftgames.org CGG] and CGG might leverage the work of Sugar Labs.
 
|-
 
|-
! 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/Python3|Port to Python3]] || outreach/research || align=left| 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?  
+
! future || [[GoogleCodeIn2012/OnlineAccounts|Manage online credentials]] || outreach/research || align=left| 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?  
 
|-
 
|-
! maintenance || [[GoogleCodeIn2012/Sugar_orphan_status|Orphaned activities]] || quality assurance || Do an analysis of which Sugar activities are are orphaned.
+
! maintenance || [[GoogleCodeIn2012/Sugar_orphan_status|Orphaned activities]] || quality assurance || align=left| Do an analysis of which Sugar activities are are orphaned.
 
|-
 
|-
! 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.
+
! maintenance || [[GoogleCodeIn2012/Sugar_touch_status|Sugar Touch]] || quality assurance || align=left| Do an analysis of which Sugar activities are touch-enabled or need modifications to support touch.
 
|-
 
|-
! 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]]).
+
! doc || [[GoogleCodeIn2012/Sugar_doc_status|Sugar Documentation]] || quality assurance || align=left| Do an analysis of which Sugar activities are lacking in documentation (e.g. [[Activities|Activity wiki page]]).
 
|-
 
|-
! 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).
+
! arm || [[GoogleCodeIn2012/Sugar_ARM_status|Sugar on ARM]] || quality assurance || align=left| Do an analysis of which Sugar activities are have issues running on non-x86 architectures (e.g. ARM).
 
|-
 
|-
! i18n || [[GoogleCodeIn2012/Sugar_i18n_status|Sugar i18n]] || quality assurance || Do an analysis of which Sugar activities are lacking i18n support.
+
! i18n || [[GoogleCodeIn2012/Sugar_i18n_status|Sugar i18n]] || quality assurance || align=left| Do an analysis of which Sugar activities are lacking i18n support.
 
|-
 
|-
! sugar || [[GoogleCodeIn2012/Special_needs|Special Needs]] || user interface || Analyze Sugar from the point of view of special needs and make recommendations for improvements.
+
! sugar || [[GoogleCodeIn2012/Special_needs|Special Needs]] || user interface || align=left| Analyze Sugar from the point of view of special needs and make recommendations for improvements.
 
|-
 
|-
! sugar || [[GoogleCodeIn2012/Touch_UI|Touch UI]] || user interface || Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch).
+
! sugar || [[GoogleCodeIn2012/Touch_UI|Touch UI]] || user interface || align=left| Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch).
 
|-
 
|-
! sugar || [[GoogleCodeIn2012/Maliit|On-screen Keyboard]] || user interface || Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin).
+
! sugar || [[GoogleCodeIn2012/Maliit|On-screen Keyboard]] || user interface || align=left| Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin).
 
|-
 
|-
! sugar || [[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 || [[GoogleCodeIn2012/Accelerometer|Accelerometer]] || user interface || align=left| Think of ways to further leverage the use of an accelerometer in Sugar (and other common sensors found in portable computing devices).
 
|-
 
|-
! learning || [[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?
+
! learning || [[GoogleCodeIn2012/Assessment|Assessment]] || user interface || align=left| Assessing how Sugar is used by students. What is being learned? Survey students and teachers. How well does it deliver its goals?
 
|-
 
|-
! future || [[GoogleCodeIn2012/Feature_requests|New Features]] || user interface || Survey Sugar users to find out what UI features they want from Sugar in the future.
+
! future || [[GoogleCodeIn2012/Feature_requests|New Features]] || user interface || align=left| Survey Sugar users to find out what UI features they want from Sugar in the future.
 
|}
 
|}
  

Navigation menu