Changes

Google Code-In 2012 (view source)

Revision as of 16:15, 20 November 2012

77 bytes added , 16:15, 20 November 2012

Line 98: Line 98:

|[[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

|-

−

|[[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

+

|[[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 tonyforster|| outreach/research || outreach

|-

−

|[[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

+

|[[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 tonyforster|| outreach/research || outreach

|-

|[[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

Line 114: Line 114:

|[[GoogleCodeIn2012/Sugar_orphan_status|Orphaned activities]] || align=left | Do an analysis of which Sugar activities are are orphaned. || 20 || || quality assurance || maintenance

|-

−

|[[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

+

|[[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 || tonyforster || quality assurance || maintenance

|-

−

|[[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

+

|[[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 || tonyforster || quality assurance || doc

|-

|[[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

Line 124: Line 124:

|[[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

|-

−

|[[GoogleCodeIn2012/Touch_UI|Touch UI]] || align=left | Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch). || 40 || || user interface || sugar

+

|[[GoogleCodeIn2012/Touch_UI|Touch UI]] || align=left | Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch). || 40 || tonyforster || user interface || sugar

|-

|[[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

|-

−

|[[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

+

|[[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 || tonyforster || user interface || sugar

|-

−

|[[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

+

|[[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 tonyforster|| user interface || learning

|-

|[[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

Tonyforster

2,486

edits