Sugar Labs - User contributions [en]

Google Code In 2019

2019-10-11T17:04:41Z

Amaan: Added myself as 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.
# Install Sugarizer on a Raspberry Pi for use by nearby computers, tablets, or phones.
# 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)
# Test old Sugar activities and report any really obvious problems (Quality assurance)
# Refactor Turtle graphics to adopt look of Javascript version (Code: Python)
# write a Python/GTK version of Music Blocks
# 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)
# Port a Sugarizer activity to Sugar (Code: Javascript)
# Port an old Sugar activity to the most recent Sugar (Code: Python)

Mentors: please feel free to add more tasks and/or add yourself as a potential mentor to an existing task.

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
* James Cameron - release manager
* Sumit Srivastava - Mentor for Coding, Design, and QA tasks.
* Jaskirat Singh - Mentor for Research, Documentation, Design and Testing tasks
* Vaibhav Aren - Mentor for Coding, Research, Documentation, Design and Testing tasks.
* Hrishi Patel - Mentor for Coding, Research, Documentation, Design and QA tasks.
* Amaan Iqbal - Mentor for Coding, Research, Documentation, Design, and Testing Tasks

Oversight Board/2018-2020-candidates/Amaan Iqbal

2018-12-14T04:56:52Z

Amaan:

Hi Everyone! I am Amaan Iqbal. I am a full stack web developer and collaborator on SugarLabs www-sugarlabs repository.

I am one of the active mentors for SugarLabs at GCI 2018 and had meaningful on time interaction with 119/559 tasks. Some of the major tasks which I authored apart from bug fixes were :
* Finding redundancy in website code. A Pull Request with significant change was [https://github.com/sugarlabs/www-sugarlabs/pull/263 this]
* Plan for updating the website to Bootstrap 4.1 with the removal of several components that would be redundant including owl-carousel
* Plan for Chatbot functionality in place of IRC which was currently removed

I am excited towards the mission of SugarLabs of providing educational opportunities to children through the Sugar Learning Platform. Being one of the major Open Source Organization, underutilization of the strengths of the contributors willing to help is also one of the biggest problems which are preventing us from significant improvements. We have failed significantly to communicate effectively with them and understanding their mindset behind their way and type of contribution. And as a result, the contributors lacked proper guidance towards their area of interest i.e., towards those repositories/components in which they can help a lot with their skillset.

One of the major problem for lack of participation in the development team meeting and the SLOBs meeting is due to the timings of the meeting. Its 22:00 UTC and 20:00 UTC i.e., 3:30 A.M. IST and 1:30 A.M. IST respectively. It's too much for any South Asian contributor to join at that time regularly. We must find a proper matching timing for SLOBs meeting so that SLOBs member and regular contributors would not face much difficulties.

I strongly believe for the proper maintenance of Sugar and related repositories, it's better to divide the tasks/components on some basis among different Oversight Board members and their maintenance should be done separately. In this way, we can clearly see the progress on any particular domain starting from design to maintenance of activities and there would not be any unnecessary dependency or expectation from other members which I have seen to happen quite frequently so far with us. This will also help in identifying how we are going on a predefined roadmap. Though there must be some consensus before taking some important decision.

If elected :
* I agree to handle slight email load throughout the year and major load during GSoC, GCI, and other open source programs
* I agree to attend all meetings provided we try to match the timings accordingly among SLOB members and regular contributors
* I agree to create a proper road map of how SugarLabs will function especially how SugarLabs website will look content and design wise depending upon consensus between the board members and will communicate effectively in coming out with improvised designs of Sugar Activities.
* I agree to break down design tasks in proper chunks such that any basic designer can contribute effectively, resulting in maximized contributions

Oversight Board/2018-2020-candidates/Amaan Iqbal

2018-12-14T04:56:09Z

Amaan:

Hi Everyone! I am Amaan Iqbal. I am a full stack web developer and collaborator on SugarLabs www-sugarlabs repository.

I am one of the active mentors for SugarLabs at GCI 2018 and had meaningful on-time interaction with 119/559 tasks. Some of the major tasks which I authored apart from bug fixes were :
* Finding redundancy in website code. A Pull Request with significant change was [https://github.com/sugarlabs/www-sugarlabs/pull/263 this]
* Plan for updating the website to Bootstrap 4.1 with the removal of several components that would be redundant including owl-carousel
* Plan for Chatbot functionality in place of IRC which was currently removed

I am excited towards the mission of SugarLabs of providing educational opportunities to children through the Sugar Learning Platform. Being one of the major Open Source Organization, underutilization of the strengths of the contributors willing to help is also one of the biggest problems which are preventing us from significant improvements. We have failed significantly to communicate effectively with them and understanding their mindset behind their way and type of contribution. And as a result, the contributors lacked proper guidance towards their area of interest i.e., towards those repositories/components in which they can help a lot with their skillset.

One of the major problem for lack of participation in the development team meeting and the SLOBs meeting is due to the timings of the meeting. Its 22:00 UTC and 20:00 UTC i.e., 3:30 A.M. IST and 1:30 A.M. IST respectively. It's too much for any South Asian contributor to join at that time regularly. We must find a proper matching timing for SLOBs meeting so that SLOBs member and regular contributors would not face much difficulties.

I strongly believe for the proper maintenance of Sugar and related repositories, it's better to divide the tasks/components on some basis among different Oversight Board members and their maintenance should be done separately. In this way, we can clearly see the progress on any particular domain starting from design to maintenance of activities and there would not be any unnecessary dependency or expectation from other members which I have seen to happen quite frequently so far with us. This will also help in identifying how we are going on a predefined roadmap. Though there must be some consensus before taking some important decision.

If elected :
* I agree to handle slight email load throughout the year and major load during GSoC, GCI, and other open source programs
* I agree to attend all meetings provided we try to match the timings accordingly among SLOB members and regular contributors
* I agree to create a proper road map of how SugarLabs will function especially how SugarLabs website will look content and design wise depending upon consensus between the board members and will communicate effectively in coming out with improvised designs of Sugar Activities.
* I agree to break down design tasks in proper chunks such that any basic designer can contribute effectively, resulting in maximized contributions

Oversight Board/2018-2020-candidates/Amaan Iqbal

2018-12-13T09:57:24Z

Amaan:

Oversight Board/2018-2020-candidates/Amaan Iqbal

2018-12-07T15:03:38Z

Amaan:

Hi Everyone! I am Amaan Iqbal. I am a full stack web developer and collaborator on SugarLabs www-sugarlabs repository.

I am one of the active mentors for SugarLabs at GCI 2018 and had meaningful on time interaction with 81/462 tasks(except in 2 in which my review took slightly more than a day). Some of the major tasks which I authored apart from bug fixes were :
* Finding redundancy in website code. A Pull Request with significant change was [https://github.com/sugarlabs/www-sugarlabs/pull/263 this]
* Plan for updating the website to Bootstrap 4.1 with the removal of several components that would be redundant including owl-carousel
* Plan for Chatbot functionality in place of IRC which was currently removed

I am excited towards the mission of SugarLabs of providing educational opportunities to children through the Sugar Learning Platform. Being one of the major Open Source Organization, underutilization of the strengths of the contributors willing to help is also one of the biggest problems which are preventing us from significant improvements. We have failed significantly to communicate effectively with them and understanding their mindset behind their way and type of contribution. And as a result, the contributors lacked proper guidance towards their area of interest i.e., towards those repositories/components in which they can help a lot with their skillset.

One of the major problem for lack of participation in the development team meeting and the SLOBs meeting is due to the timings of the meeting. Its 22:00 UTC and 20:00 UTC i.e., 3:30 A.M. IST and 1:30 A.M. IST respectively. It's too much for any South Asian contributor to join at that time regularly. We must find a proper matching timing for SLOBs meeting so that SLOBs member and regular contributors would not face much difficulties.

I strongly believe for the proper maintenance of Sugar and related repositories, it's better to divide the tasks/components on some basis among different Oversight Board members and their maintenance should be done separately. In this way, we can clearly see the progress on any particular domain starting from design to maintenance of activities and there would not be any unnecessary dependency or expectation from other members which I have seen to happen quite frequently so far with us. This will also help in identifying how we are going on a predefined roadmap. Though there must be some consensus before taking some important decision.

If elected :
* I agree to handle slight email load throughout the year and major load during GSoC, GCI, and other open source programs
* I agree to attend all meetings provided we try to match the timings accordingly among SLOB members and regular contributors
* I agree to create a proper road map of how SugarLabs will function especially how SugarLabs website will look content and design wise depending upon consensus between the board members and will communicate effectively in coming out with improvised designs of Sugar Activities.
* I agree to break down design tasks in proper chunks such that any basic designer can contribute effectively, resulting in maximized contributions

Oversight Board/2018-2020-candidates/Amaan Iqbal

2018-12-07T15:02:35Z

Amaan:

Hi Everyone! I am Amaan Iqbal. I am a full stack web developer and collaborator on SugarLabs www-sugarlabs repository.

I am one of the active mentors for SugarLabs at GCI 2018 and had meaningful on time interaction with 81/462 tasks(except in 2 in which my review took slightly more than a day). Some of the major tasks which I authored apart from bug fixes were :
* Finding redundancy in website code. A Pull Request with significant change was [https://github.com/sugarlabs/www-sugarlabs/pull/263 this]
* Plan for updating the website to Bootstrap 4.1 with the removal of several components that would be redundant including owl-carousel
* Plan for Chatbot functionality in place of IRC which was currently removed

I am excited towards the mission of SugarLabs of providing educational opportunities to children through the Sugar Learning Platform. Being one of the major Open Source Organization, underutilization of the strengths of the contributors willing to help is also one of the biggest problems which are preventing us from significant improvements. We have failed significantly to communicate effectively with them and understanding their mindset behind their way and type of contribution. And as a result, the contributors lacked proper guidance towards their area of interest i.e., towards those repositories/components in which they can help a lot with their skillset.

One of the major problem for lack of participation in the development team meeting and the SLOBs meeting is due to the timings of the meeting. Its 10 P.M. UTC and 20:00 UTC i.e., 3:30 A.M. IST and 1:30 P.M. IST respectively. It's too much for any South Asian contributor to join at that time regularly. We must find a proper matching timing for SLOBs meeting so that SLOBs member and regular contributors would not face much difficulties.

I strongly believe for the proper maintenance of Sugar and related repositories, it's better to divide the tasks/components on some basis among different Oversight Board members and their maintenance should be done separately. In this way, we can clearly see the progress on any particular domain starting from design to maintenance of activities and there would not be any unnecessary dependency or expectation from other members which I have seen to happen quite frequently so far with us. This will also help in identifying how we are going on a predefined roadmap. Though there must be some consensus before taking some important decision.

If elected :
* I agree to handle slight email load throughout the year and major load during GSoC, GCI, and other open source programs
* I agree to attend all meetings provided we try to match the timings accordingly among SLOB members and regular contributors
* I agree to create a proper road map of how SugarLabs will function especially how SugarLabs website will look content and design wise depending upon consensus between the board members and will communicate effectively in coming out with improvised designs of Sugar Activities.
* I agree to break down design tasks in proper chunks such that any basic designer can contribute effectively, resulting in maximized contributions

Oversight Board/2018-2020-candidates/Amaan Iqbal

2018-12-02T18:37:41Z

Amaan:

Hi Everyone! I am Amaan Iqbal. I am a full stack web developer and collaborator on SugarLabs www-sugarlabs repository.

I am one of the active mentors for SugarLabs at GCI 2018 and had meaningful on time interaction with 81/462 tasks(except in 2 in which my review took slightly more than a day). Some of the major tasks which I authored apart from bug fixes were :
* Finding redundancy in website code. A Pull Request with significant change was [https://github.com/sugarlabs/www-sugarlabs/pull/263 this]
* Plan for updating the website to Bootstrap 4.1 with the removal of several components that would be redundant including owl-carousel
* Plan for Chatbot functionality in place of IRC which was currently removed

I am excited towards the mission of SugarLabs of providing educational opportunities to children through the Sugar Learning Platform. Being one of the major Open Source Organization, underutilization of the strengths of the contributors willing to help is also one of the biggest problems which are preventing us from significant improvements. We have failed significantly to communicate effectively with them and understanding their mindset behind their way and type of contribution. And as a result, the contributors lacked proper guidance towards their area of interest i.e., towards those repositories/components in which they can help a lot with their skillset.

One of the major problem for lack of participation in the SLOBs meeting is due to the timings of the meeting. Its 10 P.M. UTC i.e., 3:30 A.M. IST. It's too much for any South Asian contributor to join at that time regularly. We must find a proper matching timing for SLOBs meeting so that SLOBs member and regular contributors would not face much difficulties.

I strongly believe for the proper maintenance of Sugar and related repositories, it's better to divide the tasks/components on some basis among different Oversight Board members and their maintenance should be done separately. In this way, we can clearly see the progress on any particular domain starting from design to maintenance of activities and there would not be any unnecessary dependency or expectation from other members which I have seen to happen quite frequently so far with us. This will also help in identifying how we are going on a predefined roadmap. Though there must be some consensus before taking some important decision.

If elected :
* I agree to handle slight email load throughout the year and major load during GSoC, GCI, and other open source programs
* I agree to attend all meetings provided we try to match the timings accordingly among SLOB members and regular contributors
* I agree to create a proper road map of how SugarLabs will function especially how SugarLabs website will look content and design wise depending upon consensus between the board members and will communicate effectively in coming out with improvised designs of Sugar Activities.
* I agree to break down design tasks in proper chunks such that any basic designer can contribute effectively, resulting in maximized contributions

Oversight Board/2018-2020-candidates/Amaan Iqbal

2018-12-01T09:53:10Z

Amaan: Final small updates

Hi Everyone! I am Amaan Iqbal. I am a full stack web developer and contributor for SugarLabs www-sugarlabs repository.

I am one of the active mentors for SugarLabs at GCI 2018 and had meaningful on time interaction with 81/462 tasks(except in 2 in which my review took slightly more than a day). Some of the major tasks which I authored apart from bug fixes were :
* Finding redundancy in website code. A Pull Request with significant change was [https://github.com/sugarlabs/www-sugarlabs/pull/263 this]
* Plan for updating the website to Bootstrap 4.1 with the removal of several components that would be redundant including owl-carousel
* Plan for Chatbot functionality in place of IRC which was currently removed

I am excited towards the mission of SugarLabs of providing educational opportunities to children through the Sugar Learning Platform. Being one of the major Open Source Organization, underutilization of the strengths of the contributors willing to help is also one of the biggest problems which are preventing us from significant improvements. We have failed significantly to communicate effectively with them and understanding their mindset behind their way and type of contribution. And as a result, the contributors lacked proper guidance towards their area of interest i.e., towards those repositories/components in which they can help a lot with their skillset.

One of the major problem for lack of participation in the SLOBs meeting is due to the timings of the meeting. Its 10 P.M. UTC i.e., 3:30 A.M. IST. It's too much for any South Asian contributor to join at that time regularly. We must find a proper matching timing for SLOBs meeting so that SLOBs member and regular contributors would not face much difficulties.

I strongly believe for the proper maintenance of Sugar and related repositories, it's better to divide the tasks/components on some basis among different Oversight Board members and their maintenance should be done separately. In this way, we can clearly see the progress on any particular domain starting from design to maintenance of activities and there would not be any unnecessary dependency or expectation from other members which I have seen to happen quite frequently so far with us. This will also help in identifying how we are going on a predefined roadmap. Though there must be some consensus before taking some important decision.

If elected :
* I agree to handle slight email load throughout the year and major load during GSoC, GCI, and other open source programs
* I agree to attend all meetings provided we try to match the timings accordingly among SLOB members and regular contributors
* I agree to create a proper road map of how SugarLabs will function especially how SugarLabs website will look content and design wise depending upon consensus between the board members and will communicate effectively in coming out with improvised designs of Sugar Activities.
* I agree to break down design tasks in proper chunks such that any basic designer can contribute effectively, resulting in maximized contributions

Oversight Board/2018-2020-candidates/Amaan Iqbal

2018-11-28T18:04:21Z

Amaan:

Hi Everyone! I am Amaan Iqbal. I am a full stack web developer and contributor for SugarLabs www-sugarlabs repository.

I am one of the active mentors for SugarLabs at GCI 2018 and had meaningful on time interaction with 81/462 tasks(except in 2 in which my review took slightly more than a day). Some of the major tasks which I authored apart from bug fixes were :
* Finding redundancy in website code. A Pull Request with significant change was [https://github.com/sugarlabs/www-sugarlabs/pull/263 this]
* Plan for updating the website to Bootstrap 4.1 with the removal of several components that would be redundant including owl-carousel
* Plan for Chatbot functionality in place of IRC which was currently removed

I am excited towards the mission of SugarLabs of providing educational opportunities to children through the Sugar Learning Platform. Being one of the major Open Source Organization, underutilization of the strengths of the contributors willing to help is also one of the biggest problems which are preventing us from significant improvements. We have failed significantly to communicate effectively with them and understanding their mindset behind their way and type of contribution. And as a result, the contributors lacked proper guidance towards their area of interest i.e., towards those repositories/components in which they can help a lot with their skillset.

One of the major problem for lack of participation in the SLOBs meeting is due to the timings of the meeting. Its 10 P.M. UTC i.e., 3:30 A.M. IST. It's too much for any South Asian contributor to join at that time regularly. We must find a proper matching timing for SLOBs meeting so that SLOBs member and regular contributors would not face much difficulties.

I strongly believe for the proper maintenance of Sugar and related repositories, it's better to divide the tasks/components on some basis among different Oversight Board members and their maintenance should be done separately. In this way, we can clearly see the progress on any particular domain starting from design to maintenance of activities and there would not be any unnecessary dependency or expectation from other members which I have seen to happen quite frequently so far with us. This will also help in identifying how we are going on a predefined roadmap. Though there must be some consensus before taking some important decision.

If elected :
* I agree to handle slight email load throughout the year and major load during GSoC, GCI, and other open source programs
* I agree to attend meetings provided we try to match the timings accordingly among SLOB members and regular contributors
* I agree to create a proper road map of how SugarLabs will function especially how SugarLabs website will look content and design wise depending upon consensus between the board members and will communicate effectively in coming out with improvised designs of Sugar Activities.
* I agree to break down design tasks in proper chunks such that any basic designer can contribute effectively, resulting in maximized contributions

Oversight Board/2018-2020-candidates/Amaan Iqbal

2018-11-28T14:48:44Z

Amaan: Amaan Iqbal Board Election Proposal

Hi Everyone! I am Amaan Iqbal. I am a full stack web developer and contributor for SugarLabs www-sugarlabs repository.

I am one of the active mentors for SugarLabs at GCI 2018 and had meaningful on time interaction with 81/462 tasks(except in 2 in which my review took slightly more than a day). Some of the major tasks which I authored apart from bug fixes were :
* Finding redundancy in website code. A Pull Request with significant change was [https://github.com/sugarlabs/www-sugarlabs/pull/263 this]
* Plan for updating the website to Bootstrap 4.1 with the removal of several components that would be redundant including owl-carousel
* Plan for Chatbot functionality in place of IRC which was currently removed

I am excited towards the mission of SugarLabs of providing educational opportunities to children through the Sugar Learning Platform. Being one of the major Open Source Organization, underutilization of the strengths of the contributors willing to help is also one of the biggest problems which are preventing us from significant improvements. We have failed significantly to communicate effectively with them and understanding their mindset behind their way and type of contribution. And as a result, the contributors lacked proper guidance towards their area of interest i.e., towards those repositories/components in which they can help a lot with their skillset.

One of the major problem for lack of participation in the SLOBs meeting is due to the timings of the meeting. Its 10 P.M. UTC i.e., 3:30 A.M. IST. It's too much for any South Asian contributor to join at that time regularly.

I strongly believe for the proper maintenance of Sugar and related repositories, it's better to divide the tasks/components on some basis among different Oversight Board members and their maintenance should be done separately. In this way, we can clearly see the progress on any particular domain starting from design to maintenance of activities and there would not be any unnecessary dependency or expectation from other members which I have seen to happen quite frequently so far with us. This will also help in identifying how we are going on a predefined roadmap. Though there must be some consensus before taking some important decision.

If elected :
* I agree to handle slight email load throughout the year and major load during GSoC, GCI, and other open source programs
* I agree to attend meetings provided we try to match the timings accordingly among SLOB members and regular contributors
* I agree to create a proper road map of how SugarLabs will function especially how SugarLabs website will look content and design wise depending upon consensus between the board members and will communicate effectively in coming out with improvised designs of Sugar Activities.
* I agree to break down design tasks in proper chunks such that any basic designer can contribute effectively, resulting in maximized contributions

Google Code In 2018

2018-10-03T17:54:15Z

Amaan: /* Mentors */

<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
* [mailto:anmolmishra.jiit@gmail.com Anmol Mishra]
* Amaan Iqbal