Google Code In 2019: Difference between revisions
| Line 78: | Line 78: | ||
# Write a review about an Activity in Sugar. (Documentation) | # Write a review about an Activity in Sugar. (Documentation) | ||
# Create a unit tests for a JavaScript activity (Quality assurance) | # Create a unit tests for a JavaScript activity (Quality assurance) | ||
# Test old Sugar activities and report any really obvious problems (Quality assurance) | |||
# Refactor Turtle graphics to adopt look of Javascript version (Code: Python) | # Refactor Turtle graphics to adopt look of Javascript version (Code: Python) | ||
# write a Python/GTK version of Music Blocks | # write a Python/GTK version of Music Blocks | ||
| Line 88: | Line 89: | ||
# Write a slicer in JavaScript to convert between SL and GCODE for 3D printing. (Code: JavaScript) | # Write a slicer in JavaScript to convert between SL and GCODE for 3D printing. (Code: JavaScript) | ||
# Resolve an open issue from https://github.com/walterbender/musicblocks/ (Code: JavaScript) | # Resolve an open issue from https://github.com/walterbender/musicblocks/ (Code: JavaScript) | ||
# Port a Sugarizer activity to Sugar (Code: Javascript) | |||
# Port an old Sugar activity to the most recent Sugar (Code: Python) | |||
Mentors: please feel free to add more tasks and/or add yourself as a potential mentor to an existing task. | Mentors: please feel free to add more tasks and/or add yourself as a potential mentor to an existing task. | ||