Difference between revisions of "Google Code In 2017"

From Sugar Labs
Jump to: navigation, search
(Beginner Tasks)
 
(22 intermediate revisions by 11 users not shown)
Line 2: Line 2:
 
[[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 ==
Line 9: Line 9:
  
 
Es importante que obtengas el permiso de tus padres para participar.
 
Es importante que obtengas el permiso de tus padres para participar.
 
https://developers.google.com/open-source/gci/resources/contest-rules
 
  
 
Please see the Contest Rules for Eligibility and Registration process.
 
Please see the Contest Rules for Eligibility and Registration process.
Line 22: Line 20:
 
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.
Line 55: Line 53:
 
== This is a stub for 25+ example tasks new for GCI 2017. ==
 
== This is a stub for 25+ example tasks new for GCI 2017. ==
  
 +
Note, more detailed task descriptions will be available once the contest begins.
 +
 +
=== beginner tasks ===
 +
# 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 packages on Ubuntu, Debian, or Fedora.
 +
# 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 a simple machine in Physics.
 +
 +
=== 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)
# Refactor Turtle graphics to adopt look of Javascript version (Code: Python)
 
 
# Improvements to Lilypond interface (Code: Javascript)
 
# Improvements to Lilypond interface (Code: Javascript)
# Add more synths/sound fonts to Music Blocks (Research)
 
 
# 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)
# Refactor Planet server for Turtle Blocks (Code: Python)
 
# Wiki cleanup (Documentation)
 
 
# Write a Turtle plugin (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)
 
 
# 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)
<!-- Begin comment out this section
+
# 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)
== Tasks ==
+
# Resolve an open issue from https://github.com/walterbender/musicblocks/ (Code: JavaScript)
'''Note:''' This is our preliminary list of tasks. We can add more as the contest progresses.
+
# 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.
  
 
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===
 
We have several tasks that are targeting people new to Sugar and Sugar development. You are only allowed to complete two beginner tasks.
 
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
 
|-style="background:#787878; color: white;"
 
!Title !! Description !! Hours !! Mentor !! Tag
 
|-
 
|Install the Sugar development environment||Following the instruction at [http://developer.sugarlabs.org/dev-environment.md.html], set up the Sugar development environment. Submit a screen-shot of the development environment running to complete this task. You can get help on our irc channel should you run into any difficulties.|| 48 || all || beginner
 
|-
 
|Install Sugar in a virtual machine||If your intention is to focus on documentation and training or outreach, then you may want to install Sugar in a virtual machine. Following the instructions at [http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#Tutorials][http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Virtual_machines][http://wiki.sugarlabs.org/go/Downloads#Virtual_Machines_on_all_platforms], set up the Sugar development environment. Submit a screen-shot of the development environment running to complete this task. You can get help on our irc channel should you run into any difficulties.|| 48 || all || beginner
 
|-
 
|Create an example program in Turtle Blocks||We distribute examples with the Turtle Blocks programming environment. Create your example -- some art, some geometry, some multimedia, a simple game -- to be included with the package. Deliverable is a Turtle Blocks project file to be reviewed by Sugar Labs designers and educators. (Use either the Python version bundled with Sugar or the Javascript version at [http://turtle.sugarlabs.org Turtle Blocks JS]) One source of inspiration might be [https://www.pinterest.com/walterbender/turtle-art/]. || 48 || all || beginner
 
|-
 
|Create an example program in Music Blocks||We distribute examples with the [http://walterbender.github.io/musicblocks Music Blocks] programming environment. Create your example -- some music (and art) -- to be included with the package. Deliverable is a Music Blocks project file to be reviewed by Sugar Labs designers and educators. || 48 || all || beginner
 
|-
 
|Create a simple machine in Physics||We distribute examples with the [http://activities.sugarlabs.org/en-US/sugar/addon/4193 Physics Activity]. Create a simple machine we can include in the examples collection -- some interesting mechanical device. Deliverable is a Physics activity project file to be reviewed by Sugar Labs designers and educators. (Note: you should have completed the "Install Sugar" task before attemping to complete this task.) || 48 || all || beginner
 
|}
 
 
===Documentation/Training===
 
Tasks related to creating/editing documents and helping others learn more
 
 
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
 
|-style="background:#787878; color: white;"
 
!Title !! Description !! Hours !! Mentor !! Tag
 
|-
 
|Update the Sugar Labs entry in Wikipedia|| The Sugar Labs entry in Wikipedia could use some TLC. Please bring it up to date. || 48 || Walter || Documentation
 
|-
 
|Update the Sugar Labs wiki page on git||The [[Activity Team/Git Tutorial]] is out of date: we have migrated to GitHub. Please update the page to reflect the GitHub workflow. See http://developer.sugarlabs.org/contributing.md.html for more details || 48 || Walter || Documentation
 
|-
 
|Turtle Blocks Programming Guide 1|| Add live examples missing from the [https://github.com/walterbender/turtleblocksjs/blob/master/guide/README.md Guide to Programming with Turtle Blocks]. || 48 || Walter || Documentation
 
|-
 
|Turtle Blocks Programming Guide 2|| Extend the [https://github.com/walterbender/turtleblocksjs/blob/master/guide/README.md Guide to Programming with Turtle Blocks] to include more examples. || 48 || Walter || Documentation
 
|-
 
|Music Blocks Programming Guide|| Extend the [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide to Programming with Music Blocks] to include more examples. || 48 || Walter || Documentation
 
|-
 
|Turtle Blocks Classroom Guide||Write a guide on how to use Turtle Blocks in the classroom -- a manual for teachers who might want to engage in programming. Please consult with a classroom teacher when creating the guide.|| 96 || Walter || Documentation
 
|-
 
|Music Blocks Classroom Guide||Write a guide on how to use Music Blocks in the classroom -- a manual for teachers who might want to engage in programming with Music. Please consult with a music teacher when creating the guide.|| 96 || Walter || Documentation
 
|-
 
|Sugarizer Server API Documentation||Write a documentation for the REST API for Sugarizer Server. Include some GET/POST/DELETE sample inside || 48|| Lionel || Documentation
 
|-
 
|Sugarizer Server Collaboration Tutorial||Write a tutorial on how to connect a Sugarizer Client to a Sugarizer Server and how to use it to do Journal sharing and collaboration || 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
 
|}
 
 
For information about how to create help pages for activities
 
 
http://wiki.sugarlabs.org/go/Activities/Help/Contribute
 
 
https://github.com/godiard/help-activity/blob/master/source/restructuredtext.rst
 
 
https://github.com/godiard/help-activity/blob/master/source/collaborating.rst
 
 
===Outreach/Research===
 
Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
 
 
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
 
|-style="background:#787878; color: white;"
 
!Title !! Description !! Hours !! Mentor !! Tag
 
|-
 
|Turtle Art Day||Organize a Turtle Art Day in your community. Details at [http://people.sugarlabs.org/walter/Guia_Ingles_10-08-2013.pdf]||96||Walter||Outreach
 
|-
 
|Promo Video||Create a 60 second promotional video on Sugar and its community.||96||Mariah||Outreach
 
|-
 
|Hangout Q&A||Host a Question and Answer (Q&A)/Information session about Sugar on Google Hangouts. Invite friends, family, peers, as well as academic and community leaders.||96||Mariah||Outreach
 
|-
 
|Local Lab Wiki||Create/update a "Local Lab" page for your area/country. Fill in the page with information on the Sugar community in your area. This could include contact information, mailing lists, events and any other information that may be relevant. ||96||Mariah||Research
 
|-
 
|How-To Guide||Create a guide for how to host your own DIY Sugar on a Stick party. The guide should include at least two promotional item designs (like a sticker, brochure, flyer). Feel free to change the name to something else. ||96||Mariah||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. Then, hold a workshop on the basics of using Sugar. Take pictures to document the experience. Post a blog about it.||96||Mariah||Outreach
 
|-
 
|Potential Users||Gather information on who could benefit from using or knowing about Sugar. Look at non-profit organizations, academic institutions, the home-school community. Build a database including contact information, website URLS, social media profiles, and any other relevant information.||96||Mariah||Research
 
|-
 
|Sugar Tools & Resources||Find the resources that people are using throughout the world to learn about or teach Sugar Activities. This can include manuals, teacher guides, YouTube videos, blogs, etc. Document what type of resource it is, the URL for the resource, the target audience of the resource and whether it is up-to-date.||96||Mariah||Research
 
|-
 
|Introduce Yourself||Write a blog post about why you are participating in Google Code-In, what you hope to learn from the GCI and how Sugar Labs can help you. Include a picture. Share blog post through social media.||48||Mariah||Outreach
 
|-
 
|Interview a GCI Peer||Interview another Sugar Labs GCI participant. Ask them questions about how they are selecting/completing tasks, any successes/struggles they are having, etc. Post on participant blog. Share blog post through social media.||48||Mariah||Outreach
 
|--
 
|Interview an Educator||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. Post about it on the blog, include a picture. Share the blog post through social media and with the educator.||48||Mariah||Outreach|
 
|-
 
|Review an Activity||Write a review about an Activity in Sugar. Explain how you use it, what kind of project you could do with it, any bugs it might have, etc. Post your review. The review can be a video review or a written review with screenshots. Share the blog post through social media.||48||Mariah||Outreach
 
|-
 
|Women in the Sugar Community||Create a 10-minute presentation celebrating at least three women within the Sugar community and/or the open-source community at large. Write a blog post about what you learned when making this presentation and include a link to the presentation.||48||Mariah||Outreach
 
|-
 
|Wrap-Up||Write a blog post about your experience as a GCI participant for Sugar Labs. Share your thoughts on what was successful and what can be improved for next year's participants. Feel free to include pictures, videos, links to work that you are most proud of. Share the post through social media.||48||Mariah||Outreach
 
|}
 
 
===User Interface===
 
Tasks related to user experience research or user interface design and interaction
 
 
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
 
|-style="background:#787878; color: white;"
 
!Title !! Description !! Hours !! Mentor !! Tag
 
|-
 
|Programming on a small screen|| We put an emphasis on programming in Sugar. One popular programming environment is Turtle Blocks. Recently we made a Javascript version that can run in a browser (and hence on a smart phone). How should the UI change to accommodate that form-factor? A series of annotated sketches should be made as part of completing this task. || 72 || Walter || UI
 
|-
 
|End-user customization||We try to encourage our users to re-imagine Sugar as they'd like it. Users can change the icon layout, the background screen, and the XO avatar. What else should be made easier to customize with minimal programming? || 72 || Walter || UI
 
|-
 
|Sugarizer marketing web page||Create a marketing web page to explain what is Sugarizer and  replace the [http://sugarizer.org current one] || 40 || Lionel || UI
 
|}
 
 
===Quality Assurance===
 
Tasks related to testing and ensuring code is of high quality.
 
 
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
 
|-style="background:#787878; color: white;"
 
!Title !! Description !! Hours !! Mentor !! Tag
 
|-
 
|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 (F26). See https://wiki.sugarlabs.org/go/Fedora_26#fedora_26,  https://wiki.sugarlabs.org/go/Sugar_on_a_Stick [http://dl.fedoraproject.org/pub/alt/stage/26_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
 
|-
 
|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 student|| Ultimately the quality of our work is determined by our end users. Interview a student who is using Sugar in school and solicit feedback about what works, what doesn't. || 72 || Walter || QA
 
|}
 
 
<!-- Begin comment out this section
 
===Code===
 
Tasks related to writing or refactoring code
 
 
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
 
|-style="background:#787878; color: white;"
 
!Title !! Description !! Hours !! Mentor !! Tag
 
|-
 
| Turtle Confusion in Javascript || [http://activities.sugarlabs.org/en-US/sugar/addon/4450 Turtle Confusion] presents 40 shape challenges to the learner that must be completed using basic Logo-blocks. The challenges as based on Barry Newell's 1988 book, Turtle Confusion: Logo Puzzles and Riddles. This task is to implement Turtle Confusion within the framework of the [http://turtle.sugarlabs.org JavaScript version of Turtle Blocks].|| 72 || Walter || Code, JavaScript
 
|}
 
 
End of commented out section -->
 
 
<!--
 
== Unsorted tasks ==
 
=== Sugar enhancements from bugs.sugarlabs.org ===
 
Each of these open tickets is potential task-worthy.
 
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
 
|-style="background:#787878; color: white;"
 
!Ticket !! Description !! Type !! Component
 
|-
 
| [http://bugs.sugarlabs.org/ticket/1646 1646] || No way to force-close (kill) an activity || enhancement || Sugar
 
|}
 
 
=== Sugar bugs from bugs.sugarlabs.org ===
 
Each of these open tickets is potential task-worthy.
 
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
 
|-style="background:#787878; color: white;"
 
!Ticket !! Description !! Type !! Component
 
|-
 
| [http://bugs.sugarlabs.org/ticket/4307 4307] || clipboard.set_with_data/set_with_owner is not introspectable || defect || Sugar
 
|}
 
 
=== Activity enhancements from bugs.sugarlabs.org ===
 
Each of these open tickets is potential task-worthy.
 
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
 
|-style="background:#787878; color: white;"
 
!Ticket !! Description !! Component
 
|-
 
| [http://bugs.sugarlabs.org/ticket/758 758] || Port to new tube API || Read
 
|}
 
-->
 
  
 
== Mentors ==
 
== Mentors ==
Line 254: Line 113:
 
: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)

Latest revision as of 07:03, 16 October 2018


This is the project page for the Sugar Labs application to Google Code In 2017. Sugar Labs community members: please feel free to add tasks below.

Message to potential participants

It is important that you obtain permission of your parents.

Es importante que obtengas el permiso de tus padres para participar.

Please see the Contest Rules for Eligibility and Registration process.

https://developers.google.com/open-source/gci/resources/contest-rules

Details regarding the required forms and paperwork are here: Google Code In 2017/Participate#Students.

Also, you will likely need to set up the Sugar development environment. See http://developer.sugarlabs.org/dev-environment.md.html for details. Further information about contributing to the project can be found here: http://developer.sugarlabs.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 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.

Some background from GCI

[See https://developers.google.com/open-source/gci/resources/getting-started]

Open Source Fundamentals

You can contribute without being a coder! You do not have to be a coder to contribute to open source. There are many different skill sets needed to help an open source community thrive:

Documentation
If you are a good writer and enjoy attention to detail then you might want to contribute by writing or editing documentation. Documentation is a huge part of a successful open source project. Organizations need documentation to help attract new contributors as it helps them see what the codebase looks like and where things are and what the plan is for the project.
Research
An organization may need help crunching numbers or sorting through pages of documents to better understand what the users want or need. There are many different types of tasks that students could work on that are very important to the health of the project.
Outreach
If you have an outgoing personality and like being around and talking to people, take a look at the outreach tasks. Outreach tasks often include hosting meetups in your local community or creating a plan on how people around the globe can host a meetup about the project in their local communities.
Training
You could create a YouTube video discussing a new feature of the project or maybe some basics on what the project does so people who haven’t heard about it can understand the project and get involved.
User Interface
User interface can include many types of tasks including designing new aspects of a webpage or creating a new logo for the project. It may also include various accessibility opportunities to help make the project easier for people who are blind.
Other
If you have an idea that may help an organization, reach out to them and let them know! Sometimes the best task is one that the organization hasn’t even considered yet.

Collaboration

Open source is not just about coding but working with other people to find the best solution. Being a part of the community is an essential part of success in Google Code-in. Mentors tell us every year that their best students were the ones who worked hard on their projects but also participated on IRC and helped answer questions other students had. Collaborate with the community and mentors on the #sugar channel in the irc.freenode.net network.

Quality over Quantity

It’s not about being the student who completes the most tasks, that only gets you to the top 10 to be reviewed, it doesn’t mean you will be a grand prize winner. We have had quite a few students who completed the most tasks for their organization yet were not named as Grand Prize Winners because they did everything solo and didn’t get involved in the community or think about the health of the project as a whole, they just kept completing task after task like a machine. If you actively participate in the community then you not only feel the camaraderie that comes with working as a team but you become committed to making the project better for everyone.

Some basics about Sugar Labs and Sugar development

For some basics about the project, see Chapter 4 of Learning to Change the World.

Basics: Attribution and Licensing

Read Attribution and Licensing, as both are important for all submissions.

Setting up a Sugarizer environment

Use your computer. See also #Getting started with Sugarizer.

Setting up a Sugar desktop environment

There are several options for setting up the Sugar desktop environment for development, depending on what equipment you have;

Your Equipment Your Operating System Our Recommendation
You have only one computer and don't want to erase it Linux, Windows, macOS, or iOS Install virtualisation software, make a new virtual machine and install Sugar Live Build, Sugar on a Stick, Ubuntu, Fedora, or Debian.
Linux Install Sugar packages from your distribution, see Ubuntu, Fedora or Debian. For other distributions, contact your distribution community.
You have another computer that can be erased Doesn't matter Install Sugar Live Build, Sugar on a Stick, Ubuntu, Fedora, or Debian.

What's the difference between Live Build, Sugar on a Stick and the various Linux options?

Live Build (based on Debian) Sugar on a Stick (based on Fedora) Ubuntu, Debian or Fedora
Sugar desktop user experience on startup yes, 0.112 yes, 0.110 no, must install packages
Good for Sugar activity development yes no, must install packages no, must install packages
Good for Sugar desktop module development yes, source code included no, must install git and use rpmbuild no, must install packages
Works on a spare computer yes yes yes
Works as a Virtual Machine yes yes yes

See also Setup a development environment.

Getting started with coding in Sugar

Sugar development is in either Python or JavaScript languages.

Python programmers, you must run pep8 and pyflakes on your code before submitting your patches.

Getting started with GIT

Some knowledge of git is important as your work will be submitted to our git repositories. The basic mechanism is a pull-request (PR), which is explained in Contributing.

It is required that you follow the steps outlined on the Contributing page when doing coding and documentation tasks in GCI.

GitHub provides a tutorial. There are many other guides to GIT as well.

Our old bug tracker is https://bugs.sugarlabs.org, but these days, we mostly report bugs using the issues feature of GitHub. (See https://guides.github.com/features/issues/ for details on GitHub Issues.)

Getting started with Sugarizer

Sugar Web Framework is the JavaScript Framework for Sugar. Sugarizer is a subset of Sugar that allow running activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App.

Getting a wiki account

Some tasks require that you make edits to this wiki for which you'll need an account. Please email walter @ sugarlabs . org to request an account.

Getting help

Got a problem? Ask your mentors, ask other students, or ask the Sugar Labs community.

The Sugar Labs community is large, and there are people who are not mentors in the contest. Mentors are listed. Everyone else you talk with may be a non-mentor.

As part of Sugar Labs community, non-mentors are to treat students in accord with the Code of Conduct, and as if they are new to Sugar Labs.

Students should keep in mind that some people are non-mentors, and cannot see the contest tasks, contest progress, dates, or information about students. When communicating widely, be sure to;

  • introduce yourself, the first time;
  • tell us what your task is, without relying on a link to the task (because we probably can't see it);
  • talk about the task as if you want to do it yourself, not because of the contest; and,
  • defend your technical decisions without using the contest as a defence.

Non-mentors may give good guidance on technical decisions, but bad guidance on how they think a task is judged. Always consult with your mentors as well.

This is a stub for 25+ example tasks new for GCI 2017.

Note, more detailed task descriptions will be available once the contest begins.

beginner tasks

  1. Install the Sugar development environment by following the instruction at [1].
  2. Install Sugar in a virtual machine.
  3. Install Sugar packages on Ubuntu, Debian, or Fedora.
  4. Create an example program in Turtle Blocks (See [2] for some ideas).
  5. Create an example program in Music Blocks.
  6. Create a simple machine in Physics.

general tasks

  1. Organize a Turtle Art Day (or Music Blocks Day) in your community (Outreach)
  2. Create a 60 second promotional video on Sugar and its community (Outreach)
  3. Host a Question and Answer (Q&A)/Information session about Sugar on Google Hangouts. (Outreach)
  4. 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)
  5. 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)
  6. Write a blog post about your experience as a GCI participant for Sugar Labs. (Outreach)
  7. Create a 10-minute presentation celebrating at least three women within the Sugar community and/or the open-source community at large. (Research/Outreach)
  8. Gather information on who could benefit from using or knowing about Sugar. (Research)
  9. Find the resources that people are using throughout the world to learn about or teach Sugar Activities. (Research)
  10. Find the missing repo: we've lost track of the source repository of some Sugar activities: help us find them (Research)
  11. Investigate Google Fuzzing tool (Research)
  12. Add more synths/sound fonts to Music Blocks (Research)
  13. Design the music equivalent of Turtle Confusion for Music Blocks (Research)
  14. Wiki cleanup (Documentation)
  15. Music Blocks examples (Documentation/Training)
  16. Write a review about an Activity in Sugar. (Documentation)
  17. How should the Sugar UI change to accommodate a small screen? (User interface)
  18. What else should be made easier to customize in Sugar with minimal programming? (User interface)
  19. Create a unit tests for a JavaScript activity (Quality assurance)
  20. Bugzilla clean up (Quality assurance)
  21. Refactor Turtle graphics to adopt look of Javascript version (Code: Python)
  22. Refactor Planet server for Turtle Blocks (Code: Python)
  23. Write a Pinetrest plugin for the Sugar Journal (Code: Python)
  24. Investigate CSound/Python version of Music Blocks (Code: Python)
  25. Resolve an open issue from https://github.com/sugarlabs/ (Code: Python)
  26. Teach me how to draw activity (Code: Javascript)
  27. Plugin manager for Turtle JS (Code: Javascript)
  28. Improvements to Lilypond interface (Code: Javascript)
  29. Add ABC import to Music Blocks (Code: Javascript)
  30. Add Lilypond import to Music Blocks (Code: Javascript)
  31. Write a Turtle plugin (Code: Javascript)
  32. Visualize turtle movements in Pitch-Time Matrix (Code: Javascript)
  33. Visualize turtle pitch in Music Blocks widget (Code: Javascript)
  34. Write a JavaScript version of Turtle Confusion (Code: JavaScript)
  35. Write a extruder in JavaScript to convert from SVG to STL for 3D printing. (Code: JavaScript)
  36. Write a slicer in JavaScript to convert between SL and GCODE for 3D printing. (Code: JavaScript)
  37. Resolve an open issue from https://github.com/walterbender/musicblocks/ (Code: JavaScript)
  38. 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.

Tasks must fall within one of these five categories: #Documentation/Training; #Outreach/Research; #User Interface; #Quality Assurance; and #Code.

Mentors

NOTES TO MENTORS
Please refer to Google Code In 2017/Participate#Mentors for details regarding enrolling as a mentor.
Please add yourself to the list below.
Feel free to add new tasks to the table above.

Depending on the task, we will assign multiple mentors from our various development and support teams.

  • Walter Bender - co-administrator
  • Ignacio Rodriguez - co-administrator
  • Hrishi Patel
  • Tayba Wasim (Tabs16)
  • Ibiam Chihurumnaya
  • Rishabh Thaney
  • Samson Goddy
  • Maluchukwu Nebeolisa (Malus)