Sugar Labs - User contributions [en]

Mentoring

2025-10-29T17:40:21Z

Sum2it: Created page with "Behind the scenes of running a mentorship program for almost two decades Author: Sumit Srivastava, Sugar Labs Imagine you have an organisation today in which some people are good at what they do, and some people are new while eager to learn. Now you want to help those new people do great work while passing on little bits of your knowledge. This is the perfect time for you to run a mentorship program. That is what I will try to explain here. We are currently running me..."

Behind the scenes of running a mentorship program for almost two decades
Author: Sumit Srivastava, Sugar Labs

Imagine you have an organisation today in which some people are good at what they do, and some people are new while eager to learn. Now you want to help those new people do great work while passing on little bits of your knowledge.

This is the perfect time for you to run a mentorship program. That is what I will try to explain here.

We are currently running mentorship programs for new contributors via 3 programs:
Google Summer of Code
Direct Mentorship Program
Sugar Summer of Code

The underlying principle of all 3 remains almost the same, constructionism.

What’s that, you ask? It says that people learn most effectively when they are actively involved in creating tangible objects in the real world, be it software, hardware, poems, stories, or anything else!

Structurally, since all 3 are running at the same time we don’t feel much of a difference except some minor reporting differences to the sponsors.

{ Task for Walter and Claudia:
What underlying principle? Are we talking about constructionism? Something else? I don’t know.
}

In this guide, I will be focusing on the general structure.

There are 3 components to the mentorship program:
- Onboarding
- Regular meetings
- Weekly progress reports from the students

Onboarding starts before the program begins, when people start contributing code.

They join our email list, introduce themselves, try to set up our coding environment, and ask questions when they are stuck.

Some of them contribute a lot with little mentorship.

After a few weeks, the program starts with some of the best contributors we found.

This is when the magic begins.

We try to set expectations on what was proposed to be done, how it could be broken down in chunks, and what would be needed every week to get it done in around 3 months.

Next comes the proposal.

We have a list of ideas that people can choose to propose to work on, and as the proposal deadline approaches, more people select their ideas, either from the list or an original idea.

We mostly focus on two things: quality of the idea and demonstrated ability of the person to implement the idea they proposed, whether from our list or their own.

Of these two things we focus on, we choose a few based on their previous contributions, the quality of their proposal, the usefulness of their idea, their activity in our community, their interactions with other members etc.

Two most important ones are their previous contributions and details of implementation in the proposal.

This is just a thumb rule, deviation is permitted.

Now, the program starts with the selected contributors.

This is when the magic begins.

We talk through two things: details of implementation and how to break it down into small chunks of effort every week.

This happens through meetings. What frequency, you ask?

Meetings for us are high frequency, but different for different mentors. Some meet daily, some bi weekly, some weekly.

The key is regular communication about what is being done, what the problems are, who needs help, where help is needed, and what should be done before the next meeting.

Meetings last between 20 to 60 minutes.

Some are 1 to 1, some are group meetings - varying by what is needed.

At the end of each week is a blog from the contributors about what was done, what is left, what are the goals for next week.

We like blogs being a tech org but it could be anything: a note, a text, etc.

Almost halfway through is a mid term review where we have to review whether the contributor is performing up to expectations and is almost halfway done for the project or task that was promised.

Then the same process is repeated for the second half of the cycle, with frequent meetings, weekly reports, and some daily progress from contributors.

Final review happens at the end of 3 months where we assess whether the contributor was successful in completing the project.

Mostly, if the process was followed and communication maintained, the answer is yes.

Some of these contributors go on to become integral parts of our organisation, mentoring more contributors continuing the chain of progress.

This was a story about looking behind the scenes of our mentorship programs.

User:Sum2it

2025-01-22T21:04:07Z

Sum2it:

I think we have something special here, and I believe we can change the world.

User:Sum2it

2025-01-22T20:51:32Z

Sum2it: Created page with "test"

test

Oversight Board/2025-2026-candidates/Sumit Srivastava

2024-11-24T12:50:46Z

Sum2it: /* Vision */

=== Sumit Srivastava as #1 preference on Sugar Labs Oversight Board ===
Dear Sugar Labs community members,
I would like you to '''choose me as your first preference in the upcoming elections'''. Here's why:
===About Me===
I've dedicated the '''past 7-8 years of my life to Sugar Labs''', working passionately on projects that I believe are transforming education globally. My most significant contribution has been with '''MusicBlocks, where I've worked closely with Devin and Walter Bender''', investing countless hours to make music education accessible to all.
What sets me apart is my complete commitment to Sugar Labs' mission - I've consistently '''donated 100% of my mentorship stipends back to the project''', demonstrating my belief that our work transcends personal gain.
===Vision===
Sugar Labs stands at a crucial juncture where traditional education meets artificial intelligence. Our sister project OLPC inspired Android (as noted by Sundar Pichai), and I believe we can achieve even greater impact.

'''My vision is to:'''

Transform Sugar Labs into the world's most influential educational project

Integrate AI capabilities thoughtfully into our educational tools

Expand our global reach through policy-level implementations

Establish Sugar Labs as a pioneer in AI-enhanced education

=== Concrete Commitments ===
If elected, I will:

'''- Personally secure computational resources for Sugar Labs' AI initiatives, leveraging my proven track record and connections in organizations I've worked with'''

'''- Lead the effort to build and maintain our AI infrastructure, ensuring Sugar Labs has the computing power needed for next-generation educational tools'''

'''- Work towards incorporating Sugar Labs' projects into national education policies across multiple countries'''

'''- Represent Sugar Labs at international conferences to build partnerships and increase our sphere of influence'''

'''- Actively promote our projects across various platforms - from academic conferences to schools to social media'''

=== Why I'm Different ===
While others talk about organizational structure, I focus on exponential impact. I have a proven record of securing computational resources and will personally '''ensure Sugar Labs has the AI infrastructure it needs to innovate'''. I've been '''actively promoting Sugar Labs everywhere - from conferences to schools, from parent meetings to YouTube discussions'''. My approach is hands-on and results-driven, proven by my years of tangible contributions to projects like MusicBlocks.
The learning mode of children is evolving rapidly, with AI at its forefront. We need leadership that understands both our rich history and the transformative potential of new technologies. With your support, I'll help Sugar Labs not just adapt to these changes but lead them, and '''I will personally help with securing the computational resources necessary for our AI initiatives and try to get Sugar Labs projects in national curriculum of as many countries as possible''' while trying to make it the most important education project in the world.

=== Please vote for me as your #1 preference. ===
Together, we can make Sugar Labs the defining force in teaching the next gen of our world.
Thank you for considering my candidacy.

Oversight Board/2025-2026-candidates/Sumit Srivastava

2024-11-24T12:50:26Z

Sum2it:

Oversight Board/2025-2026-candidates/Sumit Srivastava

2024-11-24T12:49:24Z

Sum2it: /* Sumit Srivastava as #1 preference on Sugar Labs Oversight Board */

=== Sumit Srivastava as #1 preference on Sugar Labs Oversight Board ===
Dear Sugar Labs community members,
I would like you to '''choose me as your first preference in the upcoming elections'''. Here's why:
===About Me===
I've dedicated the '''past 7-8 years of my life to Sugar Labs''', working passionately on projects that I believe are transforming education globally. My most significant contribution has been with '''MusicBlocks, where I've worked closely with Devin and Walter Bender''', investing countless hours to make music education accessible to all.
What sets me apart is my complete commitment to Sugar Labs' mission - I've consistently '''donated 100% of my mentorship stipends back to the project''', demonstrating my belief that our work transcends personal gain.
Vision
Sugar Labs stands at a crucial juncture where traditional education meets artificial intelligence. Our sister project OLPC inspired Android (as noted by Sundar Pichai), and I believe we can achieve even greater impact.

=== My vision is to: ===

Transform Sugar Labs into the world's most influential educational project

Integrate AI capabilities thoughtfully into our educational tools

Expand our global reach through policy-level implementations

Establish Sugar Labs as a pioneer in AI-enhanced education

=== Concrete Commitments ===
If elected, I will:

'''- Personally secure computational resources for Sugar Labs' AI initiatives, leveraging my proven track record and connections in organizations I've worked with'''

'''- Lead the effort to build and maintain our AI infrastructure, ensuring Sugar Labs has the computing power needed for next-generation educational tools'''

'''- Work towards incorporating Sugar Labs' projects into national education policies across multiple countries'''

'''- Represent Sugar Labs at international conferences to build partnerships and increase our sphere of influence'''

'''- Actively promote our projects across various platforms - from academic conferences to schools to social media'''

=== Why I'm Different ===
While others talk about organizational structure, I focus on exponential impact. I have a proven record of securing computational resources and will personally '''ensure Sugar Labs has the AI infrastructure it needs to innovate'''. I've been '''actively promoting Sugar Labs everywhere - from conferences to schools, from parent meetings to YouTube discussions'''. My approach is hands-on and results-driven, proven by my years of tangible contributions to projects like MusicBlocks.
The learning mode of children is evolving rapidly, with AI at its forefront. We need leadership that understands both our rich history and the transformative potential of new technologies. With your support, I'll help Sugar Labs not just adapt to these changes but lead them, and '''I will personally help with securing the computational resources necessary for our AI initiatives and try to get Sugar Labs projects in national curriculum of as many countries as possible''' while trying to make it the most important education project in the world.

=== Please vote for me as your #1 preference. ===
Together, we can make Sugar Labs the defining force in teaching the next gen of our world.
Thank you for considering my candidacy.

Oversight Board/2025-2026-candidates/Sumit Srivastava

2024-11-24T12:47:46Z

Sum2it: /* Why I'm Different */

=== Sumit Srivastava as #1 preference on Sugar Labs Oversight Board ===
Dear Sugar Labs community members,
I would like you to '''choose me as your first preference in the upcoming elections'''. Here's why:
About Me
I've dedicated the '''past 7-8 years of my life to Sugar Labs''', working passionately on projects that I believe are transforming education globally. My most significant contribution has been with '''MusicBlocks, where I've worked closely with Devin and Walter Bender''', investing countless hours to make music education accessible to all.
What sets me apart is my complete commitment to Sugar Labs' mission - I've consistently '''donated 100% of my mentorship stipends back to the project''', demonstrating my belief that our work transcends personal gain.
Vision
Sugar Labs stands at a crucial juncture where traditional education meets artificial intelligence. Our sister project OLPC inspired Android (as noted by Sundar Pichai), and I believe we can achieve even greater impact.

=== My vision is to: ===

Transform Sugar Labs into the world's most influential educational project

Integrate AI capabilities thoughtfully into our educational tools

Expand our global reach through policy-level implementations

Establish Sugar Labs as a pioneer in AI-enhanced education

=== Concrete Commitments ===
If elected, I will:

'''- Personally secure computational resources for Sugar Labs' AI initiatives, leveraging my proven track record and connections in organizations I've worked with'''

'''- Lead the effort to build and maintain our AI infrastructure, ensuring Sugar Labs has the computing power needed for next-generation educational tools'''

'''- Work towards incorporating Sugar Labs' projects into national education policies across multiple countries'''

'''- Represent Sugar Labs at international conferences to build partnerships and increase our sphere of influence'''

'''- Actively promote our projects across various platforms - from academic conferences to schools to social media'''

=== Why I'm Different ===
While others talk about organizational structure, I focus on exponential impact. I have a proven record of securing computational resources and will personally '''ensure Sugar Labs has the AI infrastructure it needs to innovate'''. I've been '''actively promoting Sugar Labs everywhere - from conferences to schools, from parent meetings to YouTube discussions'''. My approach is hands-on and results-driven, proven by my years of tangible contributions to projects like MusicBlocks.
The learning mode of children is evolving rapidly, with AI at its forefront. We need leadership that understands both our rich history and the transformative potential of new technologies. With your support, I'll help Sugar Labs not just adapt to these changes but lead them, and '''I will personally help with securing the computational resources necessary for our AI initiatives and try to get Sugar Labs projects in national curriculum of as many countries as possible''' while trying to make it the most important education project in the world.

=== Please vote for me as your #1 preference. ===
Together, we can make Sugar Labs the defining force in teaching the next gen of our world.
Thank you for considering my candidacy.

Oversight Board/2025-2026-candidates/Sumit Srivastava

2024-11-24T12:46:42Z

Sum2it: /* Sumit Srivastava as #1 preference on Sugar Labs Oversight Board */

=== Sumit Srivastava as #1 preference on Sugar Labs Oversight Board ===
Dear Sugar Labs community members,
I would like you to '''choose me as your first preference in the upcoming elections'''. Here's why:
About Me
I've dedicated the '''past 7-8 years of my life to Sugar Labs''', working passionately on projects that I believe are transforming education globally. My most significant contribution has been with '''MusicBlocks, where I've worked closely with Devin and Walter Bender''', investing countless hours to make music education accessible to all.
What sets me apart is my complete commitment to Sugar Labs' mission - I've consistently '''donated 100% of my mentorship stipends back to the project''', demonstrating my belief that our work transcends personal gain.
Vision
Sugar Labs stands at a crucial juncture where traditional education meets artificial intelligence. Our sister project OLPC inspired Android (as noted by Sundar Pichai), and I believe we can achieve even greater impact.

=== My vision is to: ===

Transform Sugar Labs into the world's most influential educational project

Integrate AI capabilities thoughtfully into our educational tools

Expand our global reach through policy-level implementations

Establish Sugar Labs as a pioneer in AI-enhanced education

=== Concrete Commitments ===
If elected, I will:

'''- Personally secure computational resources for Sugar Labs' AI initiatives, leveraging my proven track record and connections in organizations I've worked with'''

'''- Lead the effort to build and maintain our AI infrastructure, ensuring Sugar Labs has the computing power needed for next-generation educational tools'''

'''- Work towards incorporating Sugar Labs' projects into national education policies across multiple countries'''

'''- Represent Sugar Labs at international conferences to build partnerships and increase our sphere of influence'''

'''- Actively promote our projects across various platforms - from academic conferences to schools to social media'''

=== Why I'm Different ===
While others talk about organizational structure, I focus on exponential impact. I have a proven record of securing computational resources and will personally '''ensure Sugar Labs has the AI infrastructure it needs to innovate'''. I've been '''actively promoting Sugar Labs everywhere - from conferences to schools, from parent meetings to YouTube discussions'''. My approach is hands-on and results-driven, proven by my years of tangible contributions to projects like MusicBlocks.
The learning mode of children is evolving rapidly, with AI at its forefront. We need leadership that understands both our rich history and the transformative potential of new technologies. With your support, I'll help Sugar Labs not just adapt to these changes but lead them, and '''I will personally help with securing the computational resources necessary for our AI initiatives and try to get Sugar Labs projects in national curriculum of as many countries as possible''' while trying to make it the most important education project in the world.
Please vote for me as your #1 preference. Together, we can make Sugar Labs the defining force in teaching the next gen of our world.
Thank you for considering my candidacy.

Oversight Board/2025-2026-candidates/Sumit Srivastava

2024-11-24T12:46:04Z

Sum2it: /* Sumit Srivastava for #1 preference on Sugar Labs Oversight Board */

=== Sumit Srivastava as #1 preference on Sugar Labs Oversight Board ===
Dear Sugar Labs community members,
I would like you to '''choose me as your first preference in the upcoming elections'''. Here's why:
About Me
I've dedicated the '''past 7-8 years of my life to Sugar Labs''', working passionately on projects that I believe are transforming education globally. My most significant contribution has been with '''MusicBlocks, where I've worked closely with Devin and Walter Bender''', investing countless hours to make music education accessible to all.
What sets me apart is my complete commitment to Sugar Labs' mission - I've consistently '''donated 100% of my mentorship stipends back to the project''', demonstrating my belief that our work transcends personal gain.
Vision
Sugar Labs stands at a crucial juncture where traditional education meets artificial intelligence. Our sister project OLPC inspired Android (as noted by Sundar Pichai), and I believe we can achieve even greater impact. My vision is to:

Transform Sugar Labs into the world's most influential educational project
Integrate AI capabilities thoughtfully into our educational tools
Expand our global reach through policy-level implementations
Establish Sugar Labs as a pioneer in AI-enhanced education

=== Concrete Commitments ===
If elected, I will:

'''- Personally secure computational resources for Sugar Labs' AI initiatives, leveraging my proven track record and connections in organizations I've worked with'''

'''- Lead the effort to build and maintain our AI infrastructure, ensuring Sugar Labs has the computing power needed for next-generation educational tools'''

'''- Work towards incorporating Sugar Labs' projects into national education policies across multiple countries'''

'''- Represent Sugar Labs at international conferences to build partnerships and increase our sphere of influence'''

'''- Actively promote our projects across various platforms - from academic conferences to schools to social media'''

=== Why I'm Different ===
While others talk about organizational structure, I focus on exponential impact. I have a proven record of securing computational resources and will personally '''ensure Sugar Labs has the AI infrastructure it needs to innovate'''. I've been '''actively promoting Sugar Labs everywhere - from conferences to schools, from parent meetings to YouTube discussions'''. My approach is hands-on and results-driven, proven by my years of tangible contributions to projects like MusicBlocks.
The learning mode of children is evolving rapidly, with AI at its forefront. We need leadership that understands both our rich history and the transformative potential of new technologies. With your support, I'll help Sugar Labs not just adapt to these changes but lead them, and '''I will personally help with securing the computational resources necessary for our AI initiatives and try to get Sugar Labs projects in national curriculum of as many countries as possible''' while trying to make it the most important education project in the world.
Please vote for me as your #1 preference. Together, we can make Sugar Labs the defining force in teaching the next gen of our world.
Thank you for considering my candidacy.

Oversight Board/2025-2026-candidates/Sumit Srivastava

2024-11-24T12:45:28Z

Sum2it: /* Sumit Srivastava for #1 preference on Sugar Labs Oversight Board */

=== Sumit Srivastava for #1 preference on Sugar Labs Oversight Board ===
Dear Sugar Labs community members,
I would like you to '''choose me as your first preference in the upcoming elections'''. Here's why:
About Me
I've dedicated the '''past 7-8 years of my life to Sugar Labs''', working passionately on projects that I believe are transforming education globally. My most significant contribution has been with '''MusicBlocks, where I've worked closely with Devin and Walter Bender''', investing countless hours to make music education accessible to all.
What sets me apart is my complete commitment to Sugar Labs' mission - I've consistently '''donated 100% of my mentorship stipends back to the project''', demonstrating my belief that our work transcends personal gain.
Vision
Sugar Labs stands at a crucial juncture where traditional education meets artificial intelligence. Our sister project OLPC inspired Android (as noted by Sundar Pichai), and I believe we can achieve even greater impact. My vision is to:

Transform Sugar Labs into the world's most influential educational project
Integrate AI capabilities thoughtfully into our educational tools
Expand our global reach through policy-level implementations
Establish Sugar Labs as a pioneer in AI-enhanced education

=== Concrete Commitments ===
If elected, I will:

'''- Personally secure computational resources for Sugar Labs' AI initiatives, leveraging my proven track record and connections in organizations I've worked with'''

'''- Lead the effort to build and maintain our AI infrastructure, ensuring Sugar Labs has the computing power needed for next-generation educational tools'''

'''- Work towards incorporating Sugar Labs' projects into national education policies across multiple countries'''

'''- Represent Sugar Labs at international conferences to build partnerships and increase our sphere of influence'''

'''- Actively promote our projects across various platforms - from academic conferences to schools to social media'''

=== Why I'm Different ===
While others talk about organizational structure, I focus on exponential impact. I have a proven record of securing computational resources and will personally '''ensure Sugar Labs has the AI infrastructure it needs to innovate'''. I've been '''actively promoting Sugar Labs everywhere - from conferences to schools, from parent meetings to YouTube discussions'''. My approach is hands-on and results-driven, proven by my years of tangible contributions to projects like MusicBlocks.
The learning mode of children is evolving rapidly, with AI at its forefront. We need leadership that understands both our rich history and the transformative potential of new technologies. With your support, I'll help Sugar Labs not just adapt to these changes but lead them, and '''I will personally help with securing the computational resources necessary for our AI initiatives and try to get Sugar Labs projects in national curriculum of as many countries as possible''' while trying to make it the most important education project in the world.
Please vote for me as your #1 preference. Together, we can make Sugar Labs the defining force in teaching the next gen of our world.
Thank you for considering my candidacy.

Oversight Board/2025-2026-candidates/Sumit Srivastava

2024-11-24T12:44:40Z

Sum2it: /* Sumit Srivastava for #1 preference on Sugar Labs Oversight Board */

=== Sumit Srivastava for #1 preference on Sugar Labs Oversight Board ===
Dear Sugar Labs community members,
I would like you to '''choose me as your first preference in the upcoming elections'''. Here's why:
About Me
I've dedicated the '''past 7-8 years of my life to Sugar Labs''', working passionately on projects that I believe are transforming education globally. My most significant contribution has been with '''MusicBlocks, where I've worked closely with Devin and Walter Bender''', investing countless hours to make music education accessible to all.
What sets me apart is my complete commitment to Sugar Labs' mission - I've consistently '''donated 100% of my mentorship stipends back to the project''', demonstrating my belief that our work transcends personal gain.
Vision
Sugar Labs stands at a crucial juncture where traditional education meets artificial intelligence. Our sister project OLPC inspired Android (as noted by Sundar Pichai), and I believe we can achieve even greater impact. My vision is to:

Transform Sugar Labs into the world's most influential educational project
Integrate AI capabilities thoughtfully into our educational tools
Expand our global reach through policy-level implementations
Establish Sugar Labs as a pioneer in AI-enhanced education

Concrete Commitments
If elected, I will:

'''- Personally secure computational resources for Sugar Labs' AI initiatives, leveraging my proven track record and connections in organizations I've worked with

- Lead the effort to build and maintain our AI infrastructure, ensuring Sugar Labs has the computing power needed for next-generation educational tools

- Work towards incorporating Sugar Labs' projects into national education policies across multiple countries

- Represent Sugar Labs at international conferences to build partnerships and increase our sphere of influence

- Actively promote our projects across various platforms - from academic conferences to schools to social media'''

Why I'm Different
While others talk about organizational structure, I focus on exponential impact. I have a proven record of securing computational resources and will personally '''ensure Sugar Labs has the AI infrastructure it needs to innovate'''. I've been '''actively promoting Sugar Labs everywhere - from conferences to schools, from parent meetings to YouTube discussions'''. My approach is hands-on and results-driven, proven by my years of tangible contributions to projects like MusicBlocks.
The learning mode of children is evolving rapidly, with AI at its forefront. We need leadership that understands both our rich history and the transformative potential of new technologies. With your support, I'll help Sugar Labs not just adapt to these changes but lead them, and '''I will personally help with securing the computational resources necessary for our AI initiatives and try to get Sugar Labs projects in national curriculum of as many countries as possible''' while trying to make it the most important education project in the world.
Please vote for me as your #1 preference. Together, we can make Sugar Labs the defining force in teaching the next gen of our world.
Thank you for considering my candidacy.

Oversight Board/2025-2026-candidates/Sumit Srivastava

2024-11-24T12:44:16Z

Sum2it: Summary

=== Sumit Srivastava for #1 preference on Sugar Labs Oversight Board ===
Dear Sugar Labs community members,
I would like you to '''choose me as your first preference in the upcoming elections'''. Here's why:
About Me
I've dedicated the '''past 7-8 years of my life to Sugar Labs''', working passionately on projects that I believe are transforming education globally. My most significant contribution has been with '''MusicBlocks, where I've worked closely with Devin and Walter Bender''', investing countless hours to make music education accessible to all.
What sets me apart is my complete commitment to Sugar Labs' mission - I've consistently '''donated 100% of my mentorship stipends back to the project''', demonstrating my belief that our work transcends personal gain.
Vision
Sugar Labs stands at a crucial juncture where traditional education meets artificial intelligence. Our sister project OLPC inspired Android (as noted by Sundar Pichai), and I believe we can achieve even greater impact. My vision is to:

Transform Sugar Labs into the world's most influential educational project
Integrate AI capabilities thoughtfully into our educational tools
Expand our global reach through policy-level implementations
Establish Sugar Labs as a pioneer in AI-enhanced education

Concrete Commitments
If elected, I will:

'''- Personally secure computational resources for Sugar Labs' AI initiatives, leveraging my proven track record and connections in organizations I've worked with
- Lead the effort to build and maintain our AI infrastructure, ensuring Sugar Labs has the computing power needed for next-generation educational tools
- Work towards incorporating Sugar Labs' projects into national education policies across multiple countries
- Represent Sugar Labs at international conferences to build partnerships and increase our sphere of influence
- Actively promote our projects across various platforms - from academic conferences to schools to social media'''

Why I'm Different
While others talk about organizational structure, I focus on exponential impact. I have a proven record of securing computational resources and will personally '''ensure Sugar Labs has the AI infrastructure it needs to innovate'''. I've been '''actively promoting Sugar Labs everywhere - from conferences to schools, from parent meetings to YouTube discussions'''. My approach is hands-on and results-driven, proven by my years of tangible contributions to projects like MusicBlocks.
The learning mode of children is evolving rapidly, with AI at its forefront. We need leadership that understands both our rich history and the transformative potential of new technologies. With your support, I'll help Sugar Labs not just adapt to these changes but lead them, and '''I will personally help with securing the computational resources necessary for our AI initiatives and try to get Sugar Labs projects in national curriculum of as many countries as possible''' while trying to make it the most important education project in the world.
Please vote for me as your #1 preference. Together, we can make Sugar Labs the defining force in teaching the next gen of our world.
Thank you for considering my candidacy.

Oversight Board/2025-2026-candidates/Sumit Srivastava

2024-11-24T12:08:20Z

Sum2it: Summary of Sumit's candidature

Creating a page right now, will update my manifesto and candidate profile next.

Google Code In 2019

2019-10-10T22:04:18Z

Sum2it: /* Mentors */added mentor

<noinclude>[[Category:Trac Reference]][[Category:Idea]]
[[Category: GCI2019]]</noinclude>

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://codein.withgoogle.com/student-terms/

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
(See [[Google_Code_In_2019#Getting_set_up_on_IRC|below]] for details regarding setting up an IRC account.)

== 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 web page 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 [http://people.sugarlabs.org/walter/docs/Learning-to-Change-the-World-Chapter-4.pdf Chapter 4 of Learning to Change the World].

{{:Google Code In 2018/background}}

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

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)
# Wiki cleanup (Documentation)
# Music Blocks examples (Documentation/Training)
# Write a review about an Activity in Sugar. (Documentation)
# 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)
# write a Python/GTK version of Music Blocks
# 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)
# Plugin manager for Turtle JS (Code: Javascript)
# Add Lilypond import to Music Blocks (Code: Javascript)
# Write a Turtle plugin (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)
# Resolve an open issue from https://github.com/walterbender/musicblocks/ (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 note that not all tasks are coding tasks so please consider participating even if you are not a coder (there are research, outreach, design, and documentation tasks as well).
:But also note that prior participation in the Sugar Labs community is a requirement for mentoring.

Send an email to one of the Org Admins (this year they are Walter and TBD). You will then receive an invitation by email.
Follow the instructions in the email to sign up as a Sugar Labs 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
* Sumit Srivastava - Mentor for Coding, Design, and QA tasks.

GSoC/2019/Accepted Proposals

2019-06-02T20:41:49Z

Sum2it: /* Performance in MusicBlocks */Added hyperlinks

== Port Sugar to Python 3 ==
* Student: Aniket Mahur
* Mentors: [https://github.com/pro-panda Rahul Bothra], [https://github.com/quozl James Cameron]
* [https://summerofcode.withgoogle.com/projects/#6684133143609344 project description at GSoC]

== Create a Sugar Dashboard ==
* Student: [https://github.com/Hrishi1999 Hrishi Patel]
** [https://medium.com/@hrishipatel99 Hrishi's Project Blog]
* Mentors: [https://github.com/pro-panda Rahul Bothra], [https://github.com/perriefidelis Peace Ojemeh], [https://github.com/chimosky Chihurumnaya Ibiam]

== Performance in MusicBlocks ==
* Student: [https://github.com/fakela Favour Kelvin]
* Mentors: [https://github.com/sum2it Sumit Srivastava], [https://github.com/pikurasa Devin Ulibarri], [https://github.com/walterbender Walter Bender]

== Improve and Maintain 25 Sugar Activities ==
* Student: [https://github.com/nswarup14 Swarup N]'s [https://nswarup14.github.io/ blog]
* Mentors: Rahul Bothra, [https://github.com/chimosky Chihurumnaya Ibiam], [https://github.com/quozl James Cameron]

== Reconciling rhythm with pitch in Music Blocks widgets ==
* Student: Sparsh Agarwal
* Mentors: [https://github.com/sum2it Sumit Srivastava], [https://github.com/pikurasa Devin Ulibarri], [https://github.com/walterbender Walter Bender]

== Performance in Music Blocks ==
* Student: [https://github.com/ankur-bambharoliya Ankur Bambharoliya]
* Mentors: [https://github.com/sum2it Sumit Srivastava], [https://github.com/pikurasa Devin Ulibarri], [https://github.com/walterbender Walter Bender]

== Expand Sugarizer’s Exerciser Activity ==
* Student: [https://github.com/AvinashAgarwal14 Avinash Agarwal]'s
** [https://medium.com/@agarwalavinash14 Avinash's Project Blog]
* Mentors: [https://github.com/mikklfr Michaël Ohayon], [https://github.com/llaske Lionel Laské]

== Create Write Activity for Sugarizer ==
* Student: [https://github.com/ashish0910 Ashish Aggarwal]
* Mentors: [https://github.com/mikklfr Michaël Ohayon], [https://github.com/tarun-singhal Tarun Kumar Singhal]

== Improve Sugarizer Server Dashboard ==
* Student: [https://github.com/NikhilM98 Nikhil Mehra]
* Mentors: [https://github.com/llaske Lionel Laské], [https://github.com/tarun-singhal Tarun Kumar Singhal]

Google Code In 2018

2018-09-27T21:53:05Z

Sum2it: /* Beginner tasks: */

<noinclude>[[Category:Trac Reference]][[Category:Idea]]
[[Category: GCI2018]]</noinclude>

This is the project page for the Sugar Labs [https://opensource.googleblog.com/2018/10/welcoming-25-mentor-organizations-for.html application] to [https://developers.google.com/open-source/gci/ Google Code In 2018]. 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 2018/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 [http://people.sugarlabs.org/walter/docs/Learning-to-Change-the-World-Chapter-4.pdf Chapter 4 of Learning to Change the World].

{{:Google Code In 2018/background}}

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

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)
# 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)
# 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)
# 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)
# Plugin manager for Turtle JS (Code: Javascript)
# Improvements to Lilypond interface (Code: Javascript)
# Add ABC import to Music Blocks (Code: Javascript)
# Add Lilypond import to Music Blocks (Code: Javascript)
# Write a Turtle plugin (Code: Javascript)
# Visualize turtle movements in Pitch-Time Matrix (Code: Javascript)
# Visualize turtle pitch in Music Blocks widget (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)
# Resolve an open issue from https://github.com/walterbender/musicblocks/ (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 2018/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
* [mailto:sumitsrisumit@gmail.com Sumit Srivastava]
* [mailto:rrbothra@gmail.com Rahul Bothra]
* Ignacio Rodriguez
* Hrishi Patel
* Tayba Wasim (Tabs16)
* Ibiam Chihurumnaya - co-administrator
* Rishabh Thaney
* Samson Goddy
* Jaskirat Singh
* Peace Ojemeh

Google Code In 2018

2018-09-27T21:52:27Z

Sum2it: /* beginner tasks */

<noinclude>[[Category:Trac Reference]][[Category:Idea]]
[[Category: GCI2018]]</noinclude>

This is the project page for the Sugar Labs [https://opensource.googleblog.com/2018/10/welcoming-25-mentor-organizations-for.html application] to [https://developers.google.com/open-source/gci/ Google Code In 2018]. 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 2018/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 [http://people.sugarlabs.org/walter/docs/Learning-to-Change-the-World-Chapter-4.pdf Chapter 4 of Learning to Change the World].

{{:Google Code In 2018/background}}

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

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)
# 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)
# 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)
# 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)
# Plugin manager for Turtle JS (Code: Javascript)
# Improvements to Lilypond interface (Code: Javascript)
# Add ABC import to Music Blocks (Code: Javascript)
# Add Lilypond import to Music Blocks (Code: Javascript)
# Write a Turtle plugin (Code: Javascript)
# Visualize turtle movements in Pitch-Time Matrix (Code: Javascript)
# Visualize turtle pitch in Music Blocks widget (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)
# Resolve an open issue from https://github.com/walterbender/musicblocks/ (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 2018/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
* [mailto:sumitsrisumit@gmail.com Sumit Srivastava]
* [mailto:rrbothra@gmail.com Rahul Bothra]
* Ignacio Rodriguez
* Hrishi Patel
* Tayba Wasim (Tabs16)
* Ibiam Chihurumnaya - co-administrator
* Rishabh Thaney
* Samson Goddy
* Jaskirat Singh
* Peace Ojemeh

Google Code In 2018

2018-09-25T15:26:47Z

Sum2it:

<noinclude>[[Category:Trac Reference]][[Category:Idea]]
[[Category: GCI2018]]</noinclude>

This is the project page for the Sugar Labs [https://opensource.googleblog.com/2018/10/welcoming-25-mentor-organizations-for.html application] to [https://developers.google.com/open-source/gci/ Google Code In 2018]. 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 2018/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 [http://people.sugarlabs.org/walter/docs/Learning-to-Change-the-World-Chapter-4.pdf Chapter 4 of Learning to Change the World].

{{:Google Code In 2018/background}}

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

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)
# 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)
# 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)
# 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)
# Plugin manager for Turtle JS (Code: Javascript)
# Improvements to Lilypond interface (Code: Javascript)
# Add ABC import to Music Blocks (Code: Javascript)
# Add Lilypond import to Music Blocks (Code: Javascript)
# Write a Turtle plugin (Code: Javascript)
# Visualize turtle movements in Pitch-Time Matrix (Code: Javascript)
# Visualize turtle pitch in Music Blocks widget (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)
# Resolve an open issue from https://github.com/walterbender/musicblocks/ (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 2018/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
* [mailto:sumitsrisumit@gmail.com Sumit Srivastava]
* [mailto:rrbothra@gmail.com Rahul Bothra]
* Ignacio Rodriguez
* Hrishi Patel
* Tayba Wasim (Tabs16)
* Ibiam Chihurumnaya - co-administrator
* Rishabh Thaney
* Samson Goddy
* Jaskirat Singh
* Peace Ojemeh