10,502
edits
Changes
Jump to navigation
Jump to search
Line 2:
Line 2: − + Line 9:
Line 9: − − https://developers.google.com/open-source/gci/resources/contest-rules Line 22:
Line 20: − + Line 58:
Line 56: − + − + − + − + − + − + + + + + + + + + + + + + + − + + + + + + + + + + − # Refactor Turtle graphics to adopt look of Javascript version (Code: Python) − # Add more synths/sound fonts to Music Blocks (Research) − # Refactor Planet server for Turtle Blocks (Code: Python) − # Wiki cleanup (Documentation) − # Write a Pinetrest plugin for the Sugar Journal (Code: Python) − # Investigate CSound/Python version of Music Blocks (Code: Python) − # Organize a Turtle Art Day (or Music Blocks Day) in your community (Outreach) − # Create a 60 second promotional video on Sugar and its community (Outreach) − # Host a Question and Answer (Q&A)/Information session about Sugar on Google Hangouts. (Outreach) − # DIY Sugar on a Stick||Organize and host a Sugar on a Stick party where you show people how to make their own Sugar on a Stick. (Outreach) − # Gather information on who could benefit from using or knowing about Sugar. (Research) − # Find the resources that people are using throughout the world to learn about or teach Sugar Activities. (Research) − # Find an educator who is using open-source educational software to teach. Interview the educator about their experience as an educator and why they are using open-source software to teach. (Outreach) − # Write a review about an Activity in Sugar. (Documentation) − # Create a 10-minute presentation celebrating at least three women within the Sugar community and/or the open-source community at large. (Outreach) − # Write a blog post about your experience as a GCI participant for Sugar Labs. (Outreach) − # How should the Sugar UI change to accommodate a small screen? (User interface) − # What else should be made easier to customize in Sugar with minimal programming? (User interface) − # Create a unit tests for a JavaScript activity (Quality assurance) + + Line 110:
Line 113: − + − + + + + + + +
no edit summary
[[Category: GCI2017]]</noinclude>
[[Category: GCI2017]]</noinclude>
This is the project page for the Sugar Labs application to [https://developers.google.com/open-source/gci/ Google Code In 2017]. Sugar Labs community members: please feel free to add tasks below. We'll do an edit before final applications are due the fourth week of October 2017.
This is the project page for the Sugar Labs [https://opensource.googleblog.com/2017/10/welcoming-25-mentor-organizations-for.html application] to [https://developers.google.com/open-source/gci/ Google Code In 2017]. Sugar Labs community members: please feel free to add tasks below.
== Message to potential participants ==
== Message to potential participants ==
Es importante que obtengas el permiso de tus padres para participar.
Es importante que obtengas el permiso de tus padres para participar.
Please see the Contest Rules for Eligibility and Registration process.
Please see the Contest Rules for Eligibility and Registration process.
Please don't hesitate to ask questions on our irc channel (#sugar on irc.freenode.net) or on the sugar-devel list: sugar-devel AT lists.sugarlabs DOT org
Please don't hesitate to ask questions on our irc channel (#sugar on irc.freenode.net) or on the sugar-devel list: sugar-devel AT lists.sugarlabs DOT org
== Why we are participating ==
== Why Sugar Labs is participating ==
Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.
Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.
=== beginner tasks ===
=== beginner tasks ===
# Install the Sugar development environment||Following the instruction at [http://developer.sugarlabs.org/dev-environment.md.html]
# Install the Sugar development environment by following the instruction at [http://developer.sugarlabs.org/dev-environment.md.html].
# Install Sugar in a virtual machine
# Install Sugar in a virtual machine.
# Install Sugar packages on Ubuntu, Debian, or Fedora
# Install Sugar packages on Ubuntu, Debian, or Fedora.
# Create an example program in Turtle Blocks
# Create an example program in Turtle Blocks (See [https://www.pinterest.com/walterbender/turtle-art/] for some ideas).
# Create an example program in Music Blocks
# Create an example program in Music Blocks.
# Create a simple machine in Physics
# Create a simple machine in Physics.
=== general tasks ===
=== general tasks ===
# Organize a Turtle Art Day (or Music Blocks Day) in your community (Outreach)
# Create a 60 second promotional video on Sugar and its community (Outreach)
# Host a Question and Answer (Q&A)/Information session about Sugar on Google Hangouts. (Outreach)
# DIY Sugar on a Stick||Organize and host a Sugar on a Stick party where you show people how to make their own Sugar on a Stick. (Outreach)
# Find an educator who is using open-source educational software to teach. Interview the educator about their experience as an educator and why they are using open-source software to teach. (Outreach)
# Write a blog post about your experience as a GCI participant for Sugar Labs. (Outreach)
# Create a 10-minute presentation celebrating at least three women within the Sugar community and/or the open-source community at large. (Research/Outreach)
# Gather information on who could benefit from using or knowing about Sugar. (Research)
# Find the resources that people are using throughout the world to learn about or teach Sugar Activities. (Research)
# Find the missing repo: we've lost track of the source repository of some Sugar activities: help us find them (Research)
# Investigate Google Fuzzing tool (Research)
# Investigate Google Fuzzing tool (Research)
# Add more synths/sound fonts to Music Blocks (Research)
# Design the music equivalent of Turtle Confusion for Music Blocks (Research)
# Wiki cleanup (Documentation)
# Music Blocks examples (Documentation/Training)
# Music Blocks examples (Documentation/Training)
# Bugzilla clean up (QA)
# Write a review about an Activity in Sugar. (Documentation)
# How should the Sugar UI change to accommodate a small screen? (User interface)
# What else should be made easier to customize in Sugar with minimal programming? (User interface)
# Create a unit tests for a JavaScript activity (Quality assurance)
# Bugzilla clean up (Quality assurance)
# Refactor Turtle graphics to adopt look of Javascript version (Code: Python)
# Refactor Planet server for Turtle Blocks (Code: Python)
# Write a Pinetrest plugin for the Sugar Journal (Code: Python)
# Investigate CSound/Python version of Music Blocks (Code: Python)
# Resolve an open issue from https://github.com/sugarlabs/ (Code: Python)
# Teach me how to draw activity (Code: Javascript)
# Teach me how to draw activity (Code: Javascript)
# Plugin manager for Turtle JS (Code: Javascript)
# Plugin manager for Turtle JS (Code: Javascript)
# Improvements to Lilypond interface (Code: Javascript)
# Improvements to Lilypond interface (Code: Javascript)
# Add ABC import to Music Blocks (Code: Javascript)
# Add ABC import to Music Blocks (Code: Javascript)
# Add Lilypond import to Music Blocks (Code: Javascript)
# Add Lilypond import to Music Blocks (Code: Javascript)
# Write a Turtle plugin (Code: Javascript)
# Write a Turtle plugin (Code: Javascript)
# Visualize turtle movements in Pitch-Time Matrix (Code: Javascript)
# Visualize turtle movements in Pitch-Time Matrix (Code: Javascript)
# Visualize turtle pitch in Music Blocks widget (Code: Javascript)
# Visualize turtle pitch in Music Blocks widget (Code: Javascript)
# Write a JavaScript version of [http://activities.sugarlabs.org/en-US/sugar/addon/4450 Turtle Confusion] (Code: JavaScript)
# Write a JavaScript version of [http://activities.sugarlabs.org/en-US/sugar/addon/4450 Turtle Confusion] (Code: JavaScript)
# Write a extruder in JavaScript to convert from SVG to STL for 3D printing. (Code: JavaScript)
# Write a extruder in JavaScript to convert from SVG to STL for 3D printing. (Code: JavaScript)
# 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)
# Rewrite turtleblocksjs server (https://github.com/tchx84/turtleblocksjs-server) using NodeJS, express (https://www.npmjs.com/package/express) may be a good module to use (Code: Javascript)
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.
:Feel free to add new tasks to the table above.
:Feel free to add new tasks to the table above.
Depending on the project, we will assign multiple mentors from our various development and support teams.
Depending on the task, we will assign multiple mentors from our various development and support teams.
* Walter Bender - co-administrator
* Walter Bender - co-administrator
* Ignacio Rodriguez -co-administrator
* Ignacio Rodriguez - co-administrator
* Hrishi Patel
* Tayba Wasim (Tabs16)
* Ibiam Chihurumnaya
* Rishabh Thaney
* Samson Goddy
*Maluchukwu Nebeolisa (Malus)