Google Code In 2016: Difference between revisions
| (26 intermediate revisions by 8 users not shown) | |||
| Line 74: | Line 74: | ||
Sugar Web Framework is the JavaScript Framework for Sugar [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md]. Sugarizer [http://sugarizer.org] is a subset of Sugar that allow runing activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App. | Sugar Web Framework is the JavaScript Framework for Sugar [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md]. Sugarizer [http://sugarizer.org] is a subset of Sugar that allow runing activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App. | ||
== This is a stub for 25+ example tasks new for GCI 2016. == | |||
# Investigate Google Fuzzing tool (Research) | |||
# Decimal places in Calculate activity (Code: Pyhton) | |||
# Music Blocks examples (Documentation/Training) | |||
# Space team activity (Code: Python) | |||
# Bugzilla clean up (QA) | |||
# Teach me how to draw activity (Code: Javascript) | |||
# Manage order of blocks in Turtle plugins (Code: Javascript) | |||
# Plugin manager for Turtle JS (Code: Javascript) | |||
# Refactor pitch-time matrix code (Code: Javascript) | |||
# Fix scrolling problem with pitch-time matrix (Code: Javascript) | |||
# Refactor Training activity to be non-specific to Australia (Code: Python) | |||
# Refactor Turtle graphics to adopt look of Javascript version (Code: Python) | |||
# Improvements to Lilypond interface (Code: Javascript) | |||
# Add drum icons in Music Blocks (Design) | |||
# Add more synths/sound fonts to Music Blocks (Research) | |||
# Add ABC import to Music Blocks (Code: Javascript) | |||
# Add ABC export to Music Blocks (Code: Javascript) | |||
# Add Lilypond import to Music Blocks (Code: Javascript) | |||
# Refactor Planet server for Turtle Blocks (Code: Python) | |||
# Research graphics caching in Turtle (Research) | |||
# Wiki cleanup (Documentation) | |||
# Make trash areas smaller on Turtle (Code: Javascript) | |||
# Write a Turtle plugin (Code: Javascript) | |||
# Write a Pinetrest plugin for the Sugar Journal (Code: Python) | |||
# Investigate CSound/Python version of Music Blocks (Code: Python) | |||
# Add synth lab widget to Music Blocks (Code: Javascript) | |||
# Backport a web plugin from Turtle Blocks JS to Python (Code: Python) | |||
# Turtle write directly to the canvas instead of using Easel (Code: Javascript) | |||
# Visualize turtle movements in Pitch-Time Matrix (Code: Javascript) | |||
# Visualize turtle pitch in Music Blocks project (Code: Music Blocks) | |||
# Visualize turtle pitch in Music Blocks widget (Code: Javascript) | |||
# Synonym-Antonym activity to classify them correctly (Code: Javascript) | |||
# Create a zoo activity - Differentiate between animals, birds, reptiles etc (Code: Javascript) | |||
# Laser mirror reflection game activity | |||
<!-- Begin comment out this section | <!-- Begin comment out this section | ||
| Line 93: | Line 119: | ||
Tasks must fall within one of these five categories: [[#Documentation/Training]]; [[#Outreach/Research]]; [[#User Interface]]; [[#Quality Assurance]]; and [[#Code]]. | Tasks must fall within one of these five categories: [[#Documentation/Training]]; [[#Outreach/Research]]; [[#User Interface]]; [[#Quality Assurance]]; and [[#Code]]. | ||
End of commented out section --> | |||
===Beginner Tasks=== | ===Beginner Tasks=== | ||
| Line 137: | Line 165: | ||
|- | |- | ||
|Sugarizer wiki page||Write a Sugarizer page in the SugarLabs wiki || 24 || Lionel || Documentation | |Sugarizer wiki page||Write a Sugarizer page in the SugarLabs wiki || 24 || Lionel || Documentation | ||
|- | |||
|Sugarizer wiki page||Create a Sugarizer entry in Wikipedia|| 48 || All || Documentation | |||
|} | |} | ||
| Line 218: | Line 248: | ||
|Unit tests for JS activities||We have no unit tests for our Javascript activities. This task is to investigate approaches to unit testing in Javascript||72||Walter||QA | |Unit tests for JS activities||We have no unit tests for our Javascript activities. This task is to investigate approaches to unit testing in Javascript||72||Walter||QA | ||
|- | |- | ||
|Test Sugar on a Stick || Help test the latest Sugar on a Stick on Fedora ( | |Test Sugar on a Stick || Help test the latest Sugar on a Stick on Fedora (F25). See https://wiki.sugarlabs.org/go/Fedora_25#fedora_25, https://wiki.sugarlabs.org/go/Sugar_on_a_Stick [http://dl.fedoraproject.org/pub/alt/stage/25_RC-1.3/] #fedora-qa (freenode IRC). Deliverable is a report of the major Sugar features, e.g., desktop, journal, collaboration, and the core activities, e.g., Write, Browse, Turtle, Chat, Speak, etc. || 48 || Satellit || QA, SoaS | ||
|- | |||
|Update fedora sugar to latest version|| Provide a tarball to allow update of sugar 0.108.1 to latest version of sugar in fedora #fedora-qa (freenode IRC). | Deliverable is a tarball allowing update of sugar on a stick to latest sugar|| 72 || ? || QA, SoaS | |||
|- | |- | ||
|Interview a teacher|| Ultimately the quality of our work is determined by our end users. Interview a classroom teacher who is using Sugar and solicit feedback about what works, what doesn't. || 72 || Walter || QA | |Interview a teacher|| Ultimately the quality of our work is determined by our end users. Interview a classroom teacher who is using Sugar and solicit feedback about what works, what doesn't. || 72 || Walter || QA | ||
| Line 225: | Line 257: | ||
|} | |} | ||
<!-- Begin comment out this section | |||
===Code=== | ===Code=== | ||
Tasks related to writing or refactoring code | Tasks related to writing or refactoring code | ||
| Line 289: | Line 322: | ||
* Ignacio Rodriguez | * Ignacio Rodriguez | ||
* Lionel Laské | * Lionel Laské | ||
* Batchu Venkat Vishal | |||
* Ibiam Chihurumnaya | |||
* Utkarsh Tiwari | |||
* Abhijit Patel | |||
* Julio Reyes | |||
* Ezequiel Pereira | |||