Sugar Labs - User contributions [en]

Google Code In 2019

2019-10-11T01:48:35Z

Jaskirat:

<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

Oversight Board/2018-2020-candidates/Jaskirat Singh

2018-11-22T16:56:16Z

Jaskirat:

Hello prodigious enthusiasts, I am Jaskirat Singh from India pursuing as a volunteer in the Sugar Labs organisation.
I have been involved with Sugar Labs since 4 years but started my journey as Google Code In participant and then got officially became the community member in 2017.Serving as a Google Code In Mentor, GSOC Mentor and ceremonial contributor at the Sugar Labs.

Working apart from Google Code In, Google Summer of Code and various projects in Sugar labs I feel like that there is a need of a strong foundation for making the hands of the community to expand and span the entire world with creation and innovation.

Well I see that since long the Oversight board of Sugar Labs has not been actively participating in discussions especially SLOB meetings and Sugar Labs Outreaching goals which stand out as low as per organisation expanding growth since many times back. So we need to expand and outreach more about the Sugarlabs productivity and create a good impact on social diversity.

On behalf of this I would love to stand out as one of the delegate for the candidate seat in SLOB and helps in framing out the things in good way.
I would focus on the long term Vision by forecasting and acting accordingly that how the organisation will look to the near future with leading initiatives and various key indicators. I have contributed to the Sugar Labs in many senses and will keep on working for the betterment of the community hardly matters that sense in terms of development contribution or outreaching. So I would love to work upon those things that does not exist in the community as such one is still in progress of planing of Sugar Labs Summit as one of the annual goal within the community. Not only this but enhancing the User Experience of the products of Sugar Software will also be one of my target in the coming future.

Looking forward towards positive response on behalf of one of the delegate of candidacy seat in the SLOB.

I can be reached out at jaskiratsingh@sugarlabs.org

Oversight Board/2018-2020-candidates/Jaskirat Singh

2018-11-22T16:55:06Z

Jaskirat: Created page with "Hello prodigious enthusiasts, I am Jaskirat Singh from India pursuing as a volunteer in the Sugar Labs organisation. I have been involved with Sugar Labs since 4 years but sta..."

Summer of Code/2018

2018-03-21T08:42:27Z

Jaskirat:

== Sponsored Projects ==

[https://summerofcode.withgoogle.com/organizations/6193990685163520/ Sugar Labs at GSoC 2018]

== Project Ideas ==

'''GSoC projects must involve some coding. Non-coding projects have been moved to the [[Summer of Code/2018/Archive|Non-Coding Projects Page]].'''

{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #f7effc;"
|-style="background:#7409bc; color: white;"
!Title
!Mentor
!Project
|-
| valign=top width="15%" style="background:#fcfcfc;"|Python 3 port
| valign=top width="15%" style="background:#fcfcfc;"|Devel Team
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Python 3 has been here for quite some time. We've investigated how to migrate and now it is time to do it.
;Expected results: A Python 3 version of the Sugar toolkit, as well as the Sugar Desktop and a few activities.
;Knowledge prerequisites: Strong Python and GTK experience

|-
| valign=top width="15%" style="background:#f7effc;" |Migration of wiki activity pages to git
| valign=top width="15%" |Activity team
| align=left valign=top |
;Brief explanation: We have 345 pages under [[Activities]] in this wiki. It would be more sustainable in the long run if these pages were embedded (in Markdown format) in their corresponding git repositories.
;Expected results: Definition of migration process; migration of the majority of these pages
;Knowledge prerequisites: Knowledge of Markdown and Mediawiki markup; experience with git.

|-
| valign=top width="15%" style="background:#fcfcfc;"|GTK-4 exploration
| valign=top width="15%" style="background:#fcfcfc;"|Devel Team
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: GTK-4 is coming soon [https://mclasen.fedorapeople.org/gtk4-devconf2018.pdf]: probably in 2018. We need to be better prepared for the transition than we were for GTK-3.
;Expected results: Design of a workflow for transitioning from GTK-3 to GTK-4
;Knowledge prerequisites: Strong Python and GTK experience

|-
| valign=top width="15%" style="background:#f7effc;" |Internationalization and Localization
| valign=top width="15%" |Chris Leonard
Shivang Shekhar
| align=left valign=top |
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details. See [[Translation Team]] for framework description.
;Expected results: Work flow improvements for i18n
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript

|-
| valign=top width="15%" style="background:#fcfcfc;"|Full-color icons
| valign=top width="15%" style="background:#fcfcfc;"|Design team Jaskirat Singh perriefidelis
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: We have been discussing the implications of removing the duo-tone restriction on Sugar icons, allowing for full-color icons. We can likely use badges to compensate for any functionality we'd lose. (See [https://medium.com/@sidhant/designing-interfaces-for-education-systems-with-sugar-labs-rethinking-icons-on-sugar-614120e7ec6f] as one example of how we might proceed.). Like if an activity has not closed yet so it will be shown through a badge appearing on an icon. Repo can be found here https://github.com/sugarlabs/sugar-toolkit-gtk3/tree/master/src/sugar3
;Expected results: A patch to Sugar that uses badges to manage the icon notifications such as activity, sharing, achievements and much more.
;Knowledge prerequisites: Knowledge of GTK; Python.

|-
| valign=top width="15%" style="background:#fcfcfc;"|Learn to program in Turtle Blocks
| valign=top width="15%" style="background:#fcfcfc;"|Walter Bender Jaskirat Singh 
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: In much the same way that [https://www.codecademy.com/courses/programming-intro/0/1#!/exercises/0 ( example here )] walks newbies through the basics of programming in Javascript, it would be nice to walk newbies through the basics of Turtle Blocks. There is already a provision within Turtle Blocks for programatically creating and moving blocks and executing program stacks. So it would be a matter of developing the exercises.
;Expected results: Website for teaching and having exercises with Turtle Blocks.
;Knowledge prerequisites: Requires some familiarity with Logo programming and Python.

|-
| valign=top width="15%" style="background:#f7effc;" |Music Blocks optimizations [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;Brief explanation: Music Blocks has never been optimized in any way. It would be helpful to review the tone.js optimization recommendations, as well as build some unit tests to measure and improve the program itself.
;Expected results: A more robust and responsive Music Blocks.
;Knowledge prerequisites: Knowledge of JavaScript, unit testing

|-
| valign=top width="15%" style="background:#fcfcfc;"|Going Beyond Equal Temperament in Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics. See also [https://github.com/walterbender/musicblocks/labels/temperament MB issues for temperament], [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF Articles about temperament, scales, and tuning] and [https://owncloud.libretools.com/index.php/s/PmPfZ1yMhimQomG various materials related to temperament (.tb files that achieve temperament with existing MB features, videos of those files being performed, notes)]
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.
;Knowledge prerequisites: Knowledge of JavaScript, music theory

|-
| valign=top width="15%" style="background:#f7effc;" |Just say no to GTK2
| valign=top width="15%" style="background:#f7effc;"| Ignacio Rodriguez Cristian Garcia Abhijit Patel Ibiam Chihurumnaya Hrishi Patel
| align=left valign=top style="background:#f7effc;"|
;Brief explanation: GTK2 and GST0.10 are end of life. We need to upgrade the remaining activities with these dependencies.
;Expected results: New versions of at least 25 existing Sugar activities.
;Knowledge prerequisites: Knowledge of GTK, GST, and Python

|-
| valign=top width="15%" style="background:#fcfcfc;" |Sugar Labs Social [[File:Social Site.jpg|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Jaskirat Singh Samson Goddy Hrishi Patel Shivang Shekhar perriefidelis
Abdulazeez Abdulazeez
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: '''[https://github.com/geekrypter/Sugar-Labs-Social Sugar Labs Social]''' is a website project which should serve a purpose to help people understand and discuss project(s) around Sugar Labs. The goal of this project is to attract Teachers, Parents, Developers and fully communicate together in one platform. : It's a social website that can be used to attract maximum users and everything ( Blogs, New projects, Software, Activities, etc) can be uploaded on it which will attract more user and create their interest. : A competitive proposal must include some evidence that the approach taken will result in some use -- just because we build it doesn't mean they will come.
;Expected results: It should have user logins, feed and a blog([https://medium.com/ medium] like) that can be over viewed by people around the world
;Knowledge prerequisites: Good Layout designing and coding experience with backend (Django, JavaScript, HTML/CSS, Mongo).

|-
| valign=top width="15%" style="background:#f7effc;" |Lilypond Methodical Improvements to how Music Blocks generates Lilypond output [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Marnen Laibow-Koser
| align=left valign=top |
;Brief explanation: Music Blocks is capable of exporting [https://www.lilypond.org Lilypond] code of which general instructions can be found [https://github.com/walterbender/musicblocks/tree/master/guide#BEYOND-MUSIC-BLOCKS here in the Music Blocks guide] and its [https://github.com/walterbender/musicblocks/ source code can be found here]. We would like to improve existing code where needed and implement needed features in a methodical way, which means we must 1) document how the Music Blocks source code works for current and future developers to learn and benefit from and 2) project manage this portion of Music Blocks development (e.g. "what works" and "what needs to be done". [https://owncloud.libretools.com/index.php/s/tgJAX5yMEzQsENf An example of a draft of a simple type of this analysis exists for you to start from.]), as well as 3) implement and improve features.
;Expected results: Implement and improve lilypond export features; Detailed documentation created for developer audience that details how Music Blocks exports to Lilypond; documentation to help manage what needs to be completed.
;Knowledge prerequisites: Literacy in reading music; functional knowledge of Lilypond code (some of your own scores would be nice); Organizational and Project Management Skills; JavaScript

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks' First Steps for Robotics [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Hrishi Patel Rishabh Thaney
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: What is needed to integrate Music Blocks with Robotics? This project is 1) to experiment with existing technologies to see what is already possible, 2) develop features (e.g. plugins, hardware modifications) needed to make interfacing possible, and 3) document the entire process and next steps
;Expected results: A working method for interfacing with a simple robot; additional features within MB to ease interfacing; and full documentation of how to recreate successful projects (that a classroom could use); communication (we do not want to guess what experiments you are doing by yourself--do not be shy to send emails, videos, pictures DAILY!!!)
;Knowledge prerequisites: Understanding of JavaScript (Music Blocks source code) and robotics (no particular method requested, just make sure it is free/libre); demonstrable documentation and self-management skills; NOTE: we value quality, clear ideas over expensive or pretty robots

|-
| valign=top width="15%" style="background:#f7effc;" |Create Examples, Compositions, and New Experiments Every Day! [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima
| align=left valign=top |
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has some examples already, but it would be nice to have one ambitious student really work for the summer to make new creative, thoughtful code everyday. (You will be expected to code in the Music Blocks language on a daily basis.) Secondary, but important goals, are bug reports when bugs are found, feature suggestions, and overall good and frequent communication with the Music Blocks team.
;Expected results: Quality examples sent daily; variety of styles; runs entire gamut in terms of blocks used (we want a number of great examples for each and every block feature); organized documentation of all examples created, which can be finalized in the final weeks of GSoC
;Knowledge prerequisites: Understanding of Music Blocks as a programming language; A good proposal is one that has a well-thought out and detailed list of music projects for each day of GSoC (time-frames, blocks used, musical styles, name of music to be transcribed); experience with music and composition/theory is a definite plus.

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks UI Improvements and Implementation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Hrishi Patel Jaskirat Singh perriefidelis
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has a good enough UI, but there are open issues remaining and it would be nice if a person with a high level of understanding of graphics and style were to proposal and implement changes that unify the entire look and feel of Music Blocks.
;Expected results: Visually unified, beautiful and intuitive Music Blocks interface. Documentation to benefit future contributors to understand "what Music Blocks style is" (obviously this may change in the future, but a thoughtful rationale for the new style is expected).
;Knowledge prerequisites: Understanding of CSS, JavaScript, and HTML. Published work on UI (links to code, websites, etc)

|-
| valign=top width="15%" style="background:#f7effc;" |Scales/Modes/Keys Design Improvements and Implementation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Marnen Laibow-Koser Sachiko Nakajima perriefidelis Jaskirat Singh
| align=left valign=top |
;Brief explanation: There are features in [https://github.com/walterbender/musicblocks/tree/master/guide#3213-setting-voice-and-keys MB for exploring modes/scales/keys which can are referenced in the guide]. However, we suspect that there are better ways to organize keys. This project would be to reimagine how MB organizes pitches. We recommend that you read the discussions that have taken place already on GitHub as well as research how keys work as well as [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF scholarly articles about temperament, scales, and tuning]. Keep in mind that we would like to prepare for the possibility of chromatic pitch spaces that are not 12--for example, a chroma of 5 or 7 or 13, etc. What features and widgets are needed?
;Expected results: Detailed documentation created for developer audience that specifies 1) proposed features and overall design, 2) purpose of design choices, 3) audit of code (e.g. What changes to our current approach may be necessary? Are there libraries that may be useful?) 4) widget design proposal as well as MB code design proposal.
;Knowledge prerequisites: Understanding of Music Theory and/or group (or set) theory. Please read the articles at https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF We are looking for candidates that can make a simple and effective design that can be implemented in JavaScript.

|-
| valign=top width="15%" style="background:#fcfcfc;"|Create UI features for music analysis and visualization [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima perriefidelis
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Music Blocks does not yet have a robust set of tools to help the user analyze their music (e.g. highest pitch, lowest pitch, pitches used, keys, musical form, intervals etc.). Additionally, users would very much benefit from features to help them visualize the way their music is constructed. Perhaps we could even create some features to help the user choose a style of music and the analysis highlights movements that violate that style's particular rules.
;Expected results: New Features.
;Knowledge prerequisites: Literacy in reading music; Music Theory knowledge; UI knowledge; JavaScript knowledge

|-
| valign=top width="15%" style="background:#f7effc;" |Music Blocks Musical Ornaments Features [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top |
;Brief explanation: The neighbor block feature is the first of a series of musical ornament features. There are many more possibilities, some of which are described [https://github.com/walterbender/musicblocks/issues/909 in issue 909]. The project would be to implement and document these features as well as to create example programs.
;Expected results: New Features, documentation, and new example programs for each new feature.
;Knowledge prerequisites: Music Theory knowledge; JavaScript knowledge; knowledge of Music Blocks and tone.js internals (please research)

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks Widget Improvements [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Music Blocks has a number of features to help users conceptualize musical concepts, which also help to create code. Please see [https://github.com/walterbender/musicblocks/tree/master/guide#widgets the guide for more]. There are a number of widgets that have not been integrated at all as well. This project would be to 1) fix widget bugs, 2) implement unfinished features ([https://github.com/walterbender/musicblocks/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+widgets+ see issues]), and 3) document and fully integrate these new features and improve existing features. [https://github.com/walterbender/musicblocks/issues/663 is also a related feature]
;Expected results: New Features, fixes, documentation, and new example programs for each new feature.
;Knowledge prerequisites: Music Theory knowledge; JavaScript knowledge; knowledge of Music Blocks and tone.js internals (please research)

|-
|valign=top width="15%" style="background:#f7effc;" |Sugarizer School Box [[File:Sugarizerschoolbox.jpg|90px|thumb|center]]
|valign=top width="15%" |Michaël Ohayon Lionel Laské Hrishi Patel Rishabh Thaney
Shivang Shekhar
| align=left valign=top|
;Brief explanation
:[https://sugarizer.org Sugarizer] is the JavaScript version of Sugar, making education available of many platforms from web to mobile.:The app is composed by both a client side and a server side.
:The idea of this project is to develop a package to simplify deployment of Sugarizer in schools.
: This package will take two forms:
: 1 - An image for Raspberry Pi that could be flashed on a sd card that could automatically start a sugarizer server at boot and displays sugarizer client on the Pi. The server will be accessible by other devices from the local network. So the teacher has just to plug the RaspberryPI to expose a WiFi and the Sugarizer Server API/WebApp. So any computer connected to this WiFi could use Sugarizer Server WebApp and any tablet with Sugarizer App connected to this WiFi could benefit to collaboration, presence and backup its content on the server.
: 2 - Create one click to deploy scripts, to deploy a full Sugarizer stack on popular providers such as Amazon AWS or Heroku. So anyone could deploy a new Sugarizer Server instance on one of popular cloud platform without the need to dig into a complex setup process.
;Expected results:Raspberry Pi image files. Deployment scripts.
;Knowledge prerequisites:[https://github.com/llaske/sugarizer-server Sugarizer Server] knowledge, Linux system administration knowledge, bash scripting capabilities, Docker enthusiasm. (This project may require to download many system files)

|-
|valign=top width="15%" style="background:#fcfcfc;"|Sugarizer Exerciser activity [[File:Sugarizerexerciser.jpg|90px|thumb|center]]
|valign=top width="15%" style="background:#fcfcfc;"|Lionel Laské Michaël Ohayon Jaskirat Singh
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation
:[https://sugarizer.org Sugarizer] is the JavaScript version of Sugar, making education available of many platforms from web to mobile.
:The idea of this project is to create a new Sugarizer activity to allow users to create exercise and let other users play to this exercise.
:The activity will propose different templates for exercises. Typical exercises could be multiple-choice question, reordering a list of items, cloze text, group assignment, ...
:Once created, the exercise could be played locally or shared on the network using Sugarizer presence. At the end of the exercise a graph will give results for each participants.
:The activity should allow to integrate multimedia element (images, sounds, videos) coming from the Journal. The activity should as simple as possible so even a child should be able to create an exercise and share it.
:Like all Sugarizer activity, the activity should: adopt the Sugar UI, be responsive (work on any screen size), work with the keyboard and with the mouse (to support touch screen), use journal and use localization.
:Features inspiration could be found on [https://learningapps.org LearningApps], [https://www.google.com/forms/ Google Forms], [https://www.limesurvey.org LimeSurvey], ...
;Expected results:A Sugarizer activity.
;Knowledge prerequisites: HTML/JavaScript, UI Design, [https://github.com/llaske/sugarizer/blob/dev/docs/tutorial.md Sugarizer Development Tutorial]

|-
| valign=top width="15%" style="background:#f7effc;"|Music Blocks export [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f7effc"| Walter Bender Devin Ulibarri Sachiko Nakajima
| align="left" valign="top" style="background:#f7effc;" |
;Brief explanation: Music Blocks is essentially a Logo interpreter. It would be great to be able to export Logo from Music Blocks. (We need to find a Logo that can handle the basic synthesizer needs to make it relevant.)
;Expected results: A Logo export that is coupled to a music-enabled Logo interpreter.
;Knowledge prerequisites: Literacy in reading music; Music Theory knowledge; UI knowledge; Logo and JavaScript knowledge

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks inline documentation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc"| Walter Bender Devin Ulibarri Sachiko Nakajima
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: There are three types of documentation for Music Blocks: documentation about how individual blocks work; short coding examples; and lesson plans. This project is about the first two. We can add inline comments to each block as it is defined in basicblocks.js from which help can be autogenerated for each block. And we can utilize the "make block" mechanism to generate on-the-fly examples of how to use blocks in combination to achieve different musical goals. The former will require some JavaScript programming; the latter, Music Blocks programming.
;Expected results: In-line documentation for each block as well as in-line Music Blocks-coded examples of the core music ideas.
;Knowledge prerequisites: UI knowledge; JavaScript knowledge; some background in music.

|-
|valign=top width="15%" style="background:#f7effc;"|Making a Beginner Guide
| valign=top width="15%" style="background:#f7effc;"| Jaskirat Singh Hrishi Patel Rishabh Thaney Shivang Shekhar Samson Goddy Abdulazeez Abdulazeez
| align=left valign=top style="background:#f7effc;"|
;Brief explanation: We don't have a beginner guide for the newcomers to the Sugar labs Community. It would be great to guide them by guiding them how to contribute through making these "form where to start? , What to start? , How to start? , Where to submit? " . An example is the Coala [http://api.coala.io/en/latest/Developers/Newcomers_Guide.html Newcomers' Guide] which is built from [https://github.com/coala/coala/blob/6dae06082017587a260189a787db9cfdc84a148b/docs/Developers/Newcomers_Guide.rst markdown source]. The goal of this task is to Help newcomers to get introduce in easy way to the world of Sugar Labs also make a dasboard for the users so they can get about developed and developing areas. Their contribution can be seen also their presence can be seen with the community.
;Expected results: A set of website pages and also documentation in Pdf form with this the problems of newcomers about their contribution will be solved and they can work easily. It is essential to this project that there is a credible maintenance regime to ensure it is easy to keep it up to date after GSoC is completed.
;Knowledge prerequisites: HTML, CSS, JavaScript(interactive) , BootStrap(responsive nav compatible on mobile devices also), PHP(dashboard), Github workflow, Markdown/up for documentation.

|}
{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #f7effc;"
|-
| valign="top" width="15%" style="background:#fcfcfc;" |Scratch 3.0 to Sugar Desktop [[File:Scratch.png|centre|thumb|99x99px]]
| valign="top" width="15%" style="background:#fcfcfc" | Walter Bender Samson Goddy
Hrishi Patel Ibiam Chihurumnaya
| align="left" valign="top" style="background:#fcfcfc;" |
;Brief explanation: [https://scratch.mit.edu/ Scratch] is a programming environment for kids. The goal of this project is to make bring back the [[Activities/Scratch|Scratch activity]] to the Sugar Desktop. Scratch 3.0 was created with HTML 5 using [https://developers.google.com/blockly/ Google’s blocky].
:# Port scratch 3.0 as a Sugar activity using method [https://github.com/sugarlabs/sugar-docs/blob/master/src/web-activity.md 1] or [https://github.com/walterbender/turtle-blocks-embedded-activity 2]. Method 1, a web activity that can run on the Sugar Desktop. While method 2, an embedded activity that can run inside browser activity. There have been some development of [https://github.com/EmilyOng/embedded-scratch-activity scratch to sugar] and a yet to release version of [https://github.com/EmilyOng/Scratch.activity scratch in Sugarizer].
:# Make the scratch libraries to work completely offline, so a user can import sprite without have issues of internet connection. A possible way is to fork the [https://github.com/LLK/scratch-storage scratch-storage] and [https://github.com/LLK/scratch-gui scratch-gui] modules to make them work offline by linking the libraries to local assets on the filesystem. https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API/Using_Service_Workers https://hackernoon.com/service-worker-one-fallback-offline-image-for-any-aspect-ratio-b427c0f897fb
;Expected results: A stable working Scratch 3 on Sugar Desktop.: User to "save project" within the scratch activity into the journal, making it easy to resume project.
: Make the Scratch activity work completely offline stated at 2.
;Knowledge prerequisites: Python, GTK, JavaScript knowledge
|}
{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #f7effc;"
|-
| valign="top" width="15%" style="background:#f7effc;" |Sugarizer Primero (Sugarizer1°)
| valign="top" width="15%" style="background:#f7effc;" | Caryl Bigenho
Samson Goddy
| align="left" valign="top" style="background:#f7effc;" |
;Brief explanation: Sugarizer is a large collection of many Activities suitable for general audiences on many devices. The goal of this project is to package a subset of the Sugarizer Activities (Maximum of 5) for children 4-7 (grades Pre-K-2) with a young child-friendly UI/UX experience suitable devices. Many of the graphics in the interfaces will be re-designed to accommodate non-readers and very young children who are still developing their fine motor skills. One new Activity for intuitive math concepts will also be developed similar to [https://en.wikipedia.org/wiki/Cuisenaire_rods Cuisenaire Rods]. Sugarizer1° will be non-language dependent so translations will not be needed.
;Expected results: At the end of the summer project, a prototype of Sugarizer1° will be ready for beta testing by children, parents, and educators. .
;Knowledge prerequisites: Javascript, HTML, CSS and some knowledge of layout and design. A familiarity of how young children play and learn will also be helpful.

|}

Summer of Code/2018

2018-03-19T16:00:35Z

Jaskirat:

== Sponsored Projects ==

[https://summerofcode.withgoogle.com/organizations/6193990685163520/ Sugar Labs at GSoC 2018]

== Project Ideas ==

'''GSoC projects must involve some coding. Non-coding projects have been moved to the [[Summer of Code/2018/Archive|Non-Coding Projects Page]].'''

{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #f7effc;"
|-style="background:#7409bc; color: white;"
!Title
!Mentor
!Project
|-
| valign=top width="15%" style="background:#fcfcfc;"|Python 3 port
| valign=top width="15%" style="background:#fcfcfc;"|Devel Team
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Python 3 has been here for quite some time. We've investigated how to migrate and now it is time to do it.
;Expected results: A Python 3 version of the Sugar toolkit, as well as the Sugar Desktop and a few activities.
;Knowledge prerequisites: Strong Python and GTK experience

|-
| valign=top width="15%" style="background:#f7effc;" |Migration of wiki activity pages to git
| valign=top width="15%" |Activity team
| align=left valign=top |
;Brief explanation: We have 345 pages under [[Activities]] in this wiki. It would be more sustainable in the long run if these pages were embedded (in Markdown format) in their corresponding git repositories.
;Expected results: Definition of migration process; migration of the majority of these pages
;Knowledge prerequisites: Knowledge of Markdown and Mediawiki markup; experience with git.

|-
| valign=top width="15%" style="background:#fcfcfc;"|GTK-4 exploration
| valign=top width="15%" style="background:#fcfcfc;"|Devel Team
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: GTK-4 is coming soon [https://mclasen.fedorapeople.org/gtk4-devconf2018.pdf]: probably in 2018. We need to be better prepared for the transition than we were for GTK-3.
;Expected results: Design of a workflow for transitioning from GTK-3 to GTK-4
;Knowledge prerequisites: Strong Python and GTK experience

|-
| valign=top width="15%" style="background:#f7effc;" |Internationalization and Localization
| valign=top width="15%" |Chris Leonard
Shivang Shekhar
| align=left valign=top |
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details. See [[Translation Team]] for framework description.
;Expected results: Work flow improvements for i18n
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript

|-
| valign=top width="15%" style="background:#fcfcfc;"|Full-color icons
| valign=top width="15%" style="background:#fcfcfc;"|Design team Jaskirat Singh perriefidelis
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: We have been discussing the implications of removing the duo-tone restriction on Sugar icons, allowing for full-color icons. We can likely use badges to compensate for any functionality we'd lose. (See [https://medium.com/@sidhant/designing-interfaces-for-education-systems-with-sugar-labs-rethinking-icons-on-sugar-614120e7ec6f] as one example of how we might proceed.). Like if an activity has not closed yet so it will be shown through a badge appearing on an icon. Repo can be found here https://github.com/sugarlabs/sugar-toolkit-gtk3/tree/master/src/sugar3
;Expected results: A patch to Sugar that uses badges to manage the icon notifications such as activity, sharing, achievements and much more.
;Knowledge prerequisites: Knowledge of GTK; Python.

|-
| valign=top width="15%" style="background:#fcfcfc;"|Learn to program in Turtle Art
| valign=top width="15%" style="background:#fcfcfc;"|Walter Bender Jaskirat Singh 
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: In much the same way that [https://www.codecademy.com/courses/programming-intro/0/1#!/exercises/0 ( example here )] walks newbies through the basics of programming in Javascript, it would be nice to walk newbies through the basics of Turtle Art. There is already a provision within Turtle Art for programatically creating and moving blocks and executing program stacks. So it would be a matter of developing the exercises.
;Expected results: Website for teaching and having exercises with Turtle Art.
;Knowledge prerequisites: Requires some familiarity with Logo programming and Python.

|-
| valign=top width="15%" style="background:#f7effc;" |Music Blocks optimizations [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;Brief explanation: Music Blocks has never been optimized in any way. It would be helpful to review the tone.js optimization recommendations, as well as build some unit tests to measure and improve the program itself.
;Expected results: A more robust and responsive Music Blocks.
;Knowledge prerequisites: Knowledge of JavaScript, unit testing

|-
| valign=top width="15%" style="background:#fcfcfc;"|Going Beyond Equal Temperament in Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics. See also [https://github.com/walterbender/musicblocks/labels/temperament MB issues for temperament], [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF Articles about temperament, scales, and tuning] and [https://owncloud.libretools.com/index.php/s/PmPfZ1yMhimQomG various materials related to temperament (.tb files that achieve temperament with existing MB features, videos of those files being performed, notes)]
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.
;Knowledge prerequisites: Knowledge of JavaScript, music theory

|-
| valign=top width="15%" style="background:#f7effc;" |Just say no to GTK2
| valign=top width="15%" style="background:#f7effc;"| Ignacio Rodriguez Cristian Garcia Abhijit Patel Ibiam Chihurumnaya Hrishi Patel
| align=left valign=top style="background:#f7effc;"|
;Brief explanation: GTK2 and GST0.10 are end of life. We need to upgrade the remaining activities with these dependencies.
;Expected results: New versions of at least 25 existing Sugar activities.
;Knowledge prerequisites: Knowledge of GTK, GST, and Python

|-
| valign=top width="15%" style="background:#fcfcfc;" |Sugar Labs Social [[File:Social Site.jpg|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Jaskirat Singh Samson Goddy Hrishi Patel Shivang Shekhar perriefidelis
Abdulazeez Abdulazeez
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: '''[https://github.com/geekrypter/Sugar-Labs-Social Sugar Labs Social]''' is a website project which should serve a purpose to help people understand and discuss project(s) around Sugar Labs. The goal of this project is to attract Teachers, Parents, Developers and fully communicate together in one platform. : It's a social website that can be used to attract maximum users and everything ( Blogs, New projects, Software, Activities, etc) can be uploaded on it which will attract more user and create their interest. : A competitive proposal must include some evidence that the approach taken will result in some use -- just because we build it doesn't mean they will come.
;Expected results: It should have user logins, feed and a blog([https://medium.com/ medium] like) that can be over viewed by people around the world
;Knowledge prerequisites: Good Layout designing and coding experience with backend (Django, JavaScript, HTML/CSS, Mongo).

|-
| valign=top width="15%" style="background:#f7effc;" |Lilypond Methodical Improvements to how Music Blocks generates Lilypond output [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Marnen Laibow-Koser
| align=left valign=top |
;Brief explanation: Music Blocks is capable of exporting [https://www.lilypond.org Lilypond] code of which general instructions can be found [https://github.com/walterbender/musicblocks/tree/master/guide#BEYOND-MUSIC-BLOCKS here in the Music Blocks guide] and its [https://github.com/walterbender/musicblocks/ source code can be found here]. We would like to improve existing code where needed and implement needed features in a methodical way, which means we must 1) document how the Music Blocks source code works for current and future developers to learn and benefit from and 2) project manage this portion of Music Blocks development (e.g. "what works" and "what needs to be done". [https://owncloud.libretools.com/index.php/s/tgJAX5yMEzQsENf An example of a draft of a simple type of this analysis exists for you to start from.]), as well as 3) implement and improve features.
;Expected results: Implement and improve lilypond export features; Detailed documentation created for developer audience that details how Music Blocks exports to Lilypond; documentation to help manage what needs to be completed.
;Knowledge prerequisites: Literacy in reading music; functional knowledge of Lilypond code (some of your own scores would be nice); Organizational and Project Management Skills; JavaScript

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks' First Steps for Robotics [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Hrishi Patel Rishabh Thaney
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: What is needed to integrate Music Blocks with Robotics? This project is 1) to experiment with existing technologies to see what is already possible, 2) develop features (e.g. plugins, hardware modifications) needed to make interfacing possible, and 3) document the entire process and next steps
;Expected results: A working method for interfacing with a simple robot; additional features within MB to ease interfacing; and full documentation of how to recreate successful projects (that a classroom could use); communication (we do not want to guess what experiments you are doing by yourself--do not be shy to send emails, videos, pictures DAILY!!!)
;Knowledge prerequisites: Understanding of JavaScript (Music Blocks source code) and robotics (no particular method requested, just make sure it is free/libre); demonstrable documentation and self-management skills; NOTE: we value quality, clear ideas over expensive or pretty robots

|-
| valign=top width="15%" style="background:#f7effc;" |Create Examples, Compositions, and New Experiments Every Day! [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima
| align=left valign=top |
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has some examples already, but it would be nice to have one ambitious student really work for the summer to make new creative, thoughtful code everyday. (You will be expected to code in the Music Blocks language on a daily basis.) Secondary, but important goals, are bug reports when bugs are found, feature suggestions, and overall good and frequent communication with the Music Blocks team.
;Expected results: Quality examples sent daily; variety of styles; runs entire gamut in terms of blocks used (we want a number of great examples for each and every block feature); organized documentation of all examples created, which can be finalized in the final weeks of GSoC
;Knowledge prerequisites: Understanding of Music Blocks as a programming language; A good proposal is one that has a well-thought out and detailed list of music projects for each day of GSoC (time-frames, blocks used, musical styles, name of music to be transcribed); experience with music and composition/theory is a definite plus.

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks UI Improvements and Implementation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Hrishi Patel Jaskirat Singh perriefidelis
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has a good enough UI, but there are open issues remaining and it would be nice if a person with a high level of understanding of graphics and style were to proposal and implement changes that unify the entire look and feel of Music Blocks.
;Expected results: Visually unified, beautiful and intuitive Music Blocks interface. Documentation to benefit future contributors to understand "what Music Blocks style is" (obviously this may change in the future, but a thoughtful rationale for the new style is expected).
;Knowledge prerequisites: Understanding of CSS, JavaScript, and HTML. Published work on UI (links to code, websites, etc)

|-
| valign=top width="15%" style="background:#f7effc;" |Scales/Modes/Keys Design Improvements and Implementation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Marnen Laibow-Koser Sachiko Nakajima perriefidelis Jaskirat Singh
| align=left valign=top |
;Brief explanation: There are features in [https://github.com/walterbender/musicblocks/tree/master/guide#3213-setting-voice-and-keys MB for exploring modes/scales/keys which can are referenced in the guide]. However, we suspect that there are better ways to organize keys. This project would be to reimagine how MB organizes pitches. We recommend that you read the discussions that have taken place already on GitHub as well as research how keys work as well as [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF scholarly articles about temperament, scales, and tuning]. Keep in mind that we would like to prepare for the possibility of chromatic pitch spaces that are not 12--for example, a chroma of 5 or 7 or 13, etc. What features and widgets are needed?
;Expected results: Detailed documentation created for developer audience that specifies 1) proposed features and overall design, 2) purpose of design choices, 3) audit of code (e.g. What changes to our current approach may be necessary? Are there libraries that may be useful?) 4) widget design proposal as well as MB code design proposal.
;Knowledge prerequisites: Understanding of Music Theory and/or group (or set) theory. Please read the articles at https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF We are looking for candidates that can make a simple and effective design that can be implemented in JavaScript.

|-
| valign=top width="15%" style="background:#fcfcfc;"|Create UI features for music analysis and visualization [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima perriefidelis
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Music Blocks does not yet have a robust set of tools to help the user analyze their music (e.g. highest pitch, lowest pitch, pitches used, keys, musical form, intervals etc.). Additionally, users would very much benefit from features to help them visualize the way their music is constructed. Perhaps we could even create some features to help the user choose a style of music and the analysis highlights movements that violate that style's particular rules.
;Expected results: New Features.
;Knowledge prerequisites: Literacy in reading music; Music Theory knowledge; UI knowledge; JavaScript knowledge

|-
| valign=top width="15%" style="background:#f7effc;" |Music Blocks Musical Ornaments Features [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top |
;Brief explanation: The neighbor block feature is the first of a series of musical ornament features. There are many more possibilities, some of which are described [https://github.com/walterbender/musicblocks/issues/909 in issue 909]. The project would be to implement and document these features as well as to create example programs.
;Expected results: New Features, documentation, and new example programs for each new feature.
;Knowledge prerequisites: Music Theory knowledge; JavaScript knowledge; knowledge of Music Blocks and tone.js internals (please research)

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks Widget Improvements [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Music Blocks has a number of features to help users conceptualize musical concepts, which also help to create code. Please see [https://github.com/walterbender/musicblocks/tree/master/guide#widgets the guide for more]. There are a number of widgets that have not been integrated at all as well. This project would be to 1) fix widget bugs, 2) implement unfinished features ([https://github.com/walterbender/musicblocks/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+widgets+ see issues]), and 3) document and fully integrate these new features and improve existing features. [https://github.com/walterbender/musicblocks/issues/663 is also a related feature]
;Expected results: New Features, fixes, documentation, and new example programs for each new feature.
;Knowledge prerequisites: Music Theory knowledge; JavaScript knowledge; knowledge of Music Blocks and tone.js internals (please research)

|-
|valign=top width="15%" style="background:#f7effc;" |Sugarizer School Box [[File:Sugarizerschoolbox.jpg|90px|thumb|center]]
|valign=top width="15%" |Michaël Ohayon Lionel Laské Hrishi Patel Rishabh Thaney
Shivang Shekhar
| align=left valign=top|
;Brief explanation
:[https://sugarizer.org Sugarizer] is the JavaScript version of Sugar, making education available of many platforms from web to mobile.:The app is composed by both a client side and a server side.
:The idea of this project is to develop a package to simplify deployment of Sugarizer in schools.
: This package will take two forms:
: 1 - An image for Raspberry Pi that could be flashed on a sd card that could automatically start a sugarizer server at boot and displays sugarizer client on the Pi. The server will be accessible by other devices from the local network. So the teacher has just to plug the RaspberryPI to expose a WiFi and the Sugarizer Server API/WebApp. So any computer connected to this WiFi could use Sugarizer Server WebApp and any tablet with Sugarizer App connected to this WiFi could benefit to collaboration, presence and backup its content on the server.
: 2 - Create one click to deploy scripts, to deploy a full Sugarizer stack on popular providers such as Amazon AWS or Heroku. So anyone could deploy a new Sugarizer Server instance on one of popular cloud platform without the need to dig into a complex setup process.
;Expected results:Raspberry Pi image files. Deployment scripts.
;Knowledge prerequisites:[https://github.com/llaske/sugarizer-server Sugarizer Server] knowledge, Linux system administration knowledge, bash scripting capabilities, Docker enthusiasm. (This project may require to download many system files)

|-
|valign=top width="15%" style="background:#fcfcfc;"|Sugarizer Exerciser activity [[File:Sugarizerexerciser.jpg|90px|thumb|center]]
|valign=top width="15%" style="background:#fcfcfc;"|Lionel Laské Michaël Ohayon Jaskirat Singh
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation
:[https://sugarizer.org Sugarizer] is the JavaScript version of Sugar, making education available of many platforms from web to mobile.
:The idea of this project is to create a new Sugarizer activity to allow users to create exercise and let other users play to this exercise.
:The activity will propose different templates for exercises. Typical exercises could be multiple-choice question, reordering a list of items, cloze text, group assignment, ...
:Once created, the exercise could be played locally or shared on the network using Sugarizer presence. At the end of the exercise a graph will give results for each participants.
:The activity should allow to integrate multimedia element (images, sounds, videos) coming from the Journal. The activity should as simple as possible so even a child should be able to create an exercise and share it.
:Like all Sugarizer activity, the activity should: adopt the Sugar UI, be responsive (work on any screen size), work with the keyboard and with the mouse (to support touch screen), use journal and use localization.
:Features inspiration could be found on [https://learningapps.org LearningApps], [https://www.google.com/forms/ Google Forms], [https://www.limesurvey.org LimeSurvey], ...
;Expected results:A Sugarizer activity.
;Knowledge prerequisites: HTML/JavaScript, UI Design, [https://github.com/llaske/sugarizer/blob/dev/docs/tutorial.md Sugarizer Development Tutorial]

|-
| valign=top width="15%" style="background:#f7effc;"|Music Blocks export [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f7effc"| Walter Bender Devin Ulibarri Sachiko Nakajima
| align="left" valign="top" style="background:#f7effc;" |
;Brief explanation: Music Blocks is essentially a Logo interpreter. It would be great to be able to export Logo from Music Blocks. (We need to find a Logo that can handle the basic synthesizer needs to make it relevant.)
;Expected results: A Logo export that is coupled to a music-enabled Logo interpreter.
;Knowledge prerequisites: Literacy in reading music; Music Theory knowledge; UI knowledge; Logo and JavaScript knowledge

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks inline documentation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc"| Walter Bender Devin Ulibarri Sachiko Nakajima
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: There are three types of documentation for Music Blocks: documentation about how individual blocks work; short coding examples; and lesson plans. This project is about the first two. We can add inline comments to each block as it is defined in basicblocks.js from which help can be autogenerated for each block. And we can utilize the "make block" mechanism to generate on-the-fly examples of how to use blocks in combination to achieve different musical goals. The former will require some JavaScript programming; the latter, Music Blocks programming.
;Expected results: In-line documentation for each block as well as in-line Music Blocks-coded examples of the core music ideas.
;Knowledge prerequisites: UI knowledge; JavaScript knowledge; some background in music.

|-
|valign=top width="15%" style="background:#f7effc;"|Making a Beginner Guide
| valign=top width="15%" style="background:#f7effc;"| Jaskirat Singh Hrishi Patel Rishabh Thaney Shivang Shekhar Samson Goddy Abdulazeez Abdulazeez
| align=left valign=top style="background:#f7effc;"|
;Brief explanation: We don't have a beginner guide for the newcomers to the Sugar labs Community. It would be great to guide them by guiding them how to contribute through making these "form where to start? , What to start? , How to start? , Where to submit? " . An example is the Coala [http://api.coala.io/en/latest/Developers/Newcomers_Guide.html Newcomers' Guide] which is built from [https://github.com/coala/coala/blob/6dae06082017587a260189a787db9cfdc84a148b/docs/Developers/Newcomers_Guide.rst markdown source]. The goal of this task is to Help newcomers to get introduce in easy way to the world of Sugar Labs also make a dasboard for the users so they can get about developed and developing areas. Their contribution can be seen also their presence can be seen with the community.
;Expected results: A set of website pages and also documentation in Pdf form with this the problems of newcomers about their contribution will be solved and they can work easily. It is essential to this project that there is a credible maintenance regime to ensure it is easy to keep it up to date after GSoC is completed.
;Knowledge prerequisites: HTML, CSS, JavaScript(interactive) , BootStrap(responsive nav compatible on mobile devices also), PHP(dashboard), Github workflow, Markdown/up for documentation.

|}
{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #f7effc;"
|-
| valign="top" width="15%" style="background:#fcfcfc;" |Scratch 3.0 to Sugar Desktop [[File:Scratch.png|centre|thumb|99x99px]]
| valign="top" width="15%" style="background:#fcfcfc" | Walter Bender Samson Goddy
Hrishi Patel Ibiam Chihurumnaya
| align="left" valign="top" style="background:#fcfcfc;" |
;Brief explanation: [https://scratch.mit.edu/ Scratch] is a programming environment for kids. The goal of this project is to make bring back the [[Activities/Scratch|Scratch activity]] to the Sugar Desktop. Scratch 3.0 was created with HTML 5 using [https://developers.google.com/blockly/ Google’s blocky].
:# Port scratch 3.0 as a Sugar activity using method [https://github.com/sugarlabs/sugar-docs/blob/master/src/web-activity.md 1] or [https://github.com/walterbender/turtle-blocks-embedded-activity 2]. Method 1, a web activity that can run on the Sugar Desktop. While method 2, an embedded activity that can run inside browser activity. There have been some development of [https://github.com/EmilyOng/embedded-scratch-activity scratch to sugar] and a yet to release version of [https://github.com/EmilyOng/Scratch.activity scratch in Sugarizer].
:# Make the scratch libraries to work completely offline, so a user can import sprite without have issues of internet connection. A possible way is to fork the [https://github.com/LLK/scratch-storage scratch-storage] and [https://github.com/LLK/scratch-gui scratch-gui] modules to make them work offline by linking the libraries to local assets on the filesystem. https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API/Using_Service_Workers https://hackernoon.com/service-worker-one-fallback-offline-image-for-any-aspect-ratio-b427c0f897fb
;Expected results: A stable working Scratch 3 on Sugar Desktop.: User to "save project" within the scratch activity into the journal, making it easy to resume project.
: Make the Scratch activity work completely offline stated at 2.
;Knowledge prerequisites: Python, GTK, JavaScript knowledge
|}

Summer of Code/2018

2018-03-19T15:55:59Z

Jaskirat:

== Sponsored Projects ==

[https://summerofcode.withgoogle.com/organizations/6193990685163520/ Sugar Labs at GSoC 2018]

== Project Ideas ==

'''GSoC projects must involve some coding. Non-coding projects have been moved to the [[Summer of Code/2018/Archive|Non-Coding Projects Page]].'''

{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #f7effc;"
|-style="background:#7409bc; color: white;"
!Title
!Mentor
!Project
|-
| valign=top width="15%" style="background:#fcfcfc;"|Python 3 port
| valign=top width="15%" style="background:#fcfcfc;"|Devel Team
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Python 3 has been here for quite some time. We've investigated how to migrate and now it is time to do it.
;Expected results: A Python 3 version of the Sugar toolkit, as well as the Sugar Desktop and a few activities.
;Knowledge prerequisites: Strong Python and GTK experience

|-
| valign=top width="15%" style="background:#f7effc;" |Migration of wiki activity pages to git
| valign=top width="15%" |Activity team
| align=left valign=top |
;Brief explanation: We have 345 pages under [[Activities]] in this wiki. It would be more sustainable in the long run if these pages were embedded (in Markdown format) in their corresponding git repositories.
;Expected results: Definition of migration process; migration of the majority of these pages
;Knowledge prerequisites: Knowledge of Markdown and Mediawiki markup; experience with git.

|-
| valign=top width="15%" style="background:#fcfcfc;"|GTK-4 exploration
| valign=top width="15%" style="background:#fcfcfc;"|Devel Team
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: GTK-4 is coming soon [https://mclasen.fedorapeople.org/gtk4-devconf2018.pdf]: probably in 2018. We need to be better prepared for the transition than we were for GTK-3.
;Expected results: Design of a workflow for transitioning from GTK-3 to GTK-4
;Knowledge prerequisites: Strong Python and GTK experience

|-
| valign=top width="15%" style="background:#f7effc;" |Internationalization and Localization
| valign=top width="15%" |Chris Leonard
Shivang Shekhar
| align=left valign=top |
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details. See [[Translation Team]] for framework description.
;Expected results: Work flow improvements for i18n
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript

|-
| valign=top width="15%" style="background:#fcfcfc;"|Full-color icons
| valign=top width="15%" style="background:#fcfcfc;"|Design team Jaskirat Singh perriefidelis
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: We have been discussing the implications of removing the duo-tone restriction on Sugar icons, allowing for full-color icons. We can likely use badges to compensate for any functionality we'd lose. (See [https://medium.com/@sidhant/designing-interfaces-for-education-systems-with-sugar-labs-rethinking-icons-on-sugar-614120e7ec6f] as one example of how we might proceed.). Like if an activity has not closed yet so it will be shown through a badge appearing on an icon. Repo can be found here https://github.com/sugarlabs/sugar-toolkit-gtk3/tree/master/src/sugar3
;Expected results: A patch to Sugar that uses badges to manage the icon notifications such as activity, sharing, achievements and much more.
;Knowledge prerequisites: Knowledge of GTK; Python.

|-
| valign=top width="15%" style="background:#fcfcfc;"|Learn to program in Turtle Art
| valign=top width="15%" style="background:#fcfcfc;"|Walter Bender Jaskirat Singh 
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: In much the same way that [3] walks newbies through the basics of programming in Javascript, it would be nice to walk newbies through the basics of Turtle Art. There is already a provision within Turtle Art for programatically creating and moving blocks and executing program stacks. So it would be a matter of developing the exercises.
;Expected results: Website for teaching and having exercises with Turtle Art.
;Knowledge prerequisites: Requires some familiarity with Logo programming and Python.

|-
| valign=top width="15%" style="background:#f7effc;" |Music Blocks optimizations [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;Brief explanation: Music Blocks has never been optimized in any way. It would be helpful to review the tone.js optimization recommendations, as well as build some unit tests to measure and improve the program itself.
;Expected results: A more robust and responsive Music Blocks.
;Knowledge prerequisites: Knowledge of JavaScript, unit testing

|-
| valign=top width="15%" style="background:#fcfcfc;"|Going Beyond Equal Temperament in Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics. See also [https://github.com/walterbender/musicblocks/labels/temperament MB issues for temperament], [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF Articles about temperament, scales, and tuning] and [https://owncloud.libretools.com/index.php/s/PmPfZ1yMhimQomG various materials related to temperament (.tb files that achieve temperament with existing MB features, videos of those files being performed, notes)]
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.
;Knowledge prerequisites: Knowledge of JavaScript, music theory

|-
| valign=top width="15%" style="background:#f7effc;" |Just say no to GTK2
| valign=top width="15%" style="background:#f7effc;"| Ignacio Rodriguez Cristian Garcia Abhijit Patel Ibiam Chihurumnaya Hrishi Patel
| align=left valign=top style="background:#f7effc;"|
;Brief explanation: GTK2 and GST0.10 are end of life. We need to upgrade the remaining activities with these dependencies.
;Expected results: New versions of at least 25 existing Sugar activities.
;Knowledge prerequisites: Knowledge of GTK, GST, and Python

|-
| valign=top width="15%" style="background:#fcfcfc;" |Sugar Labs Social [[File:Social Site.jpg|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Jaskirat Singh Samson Goddy Hrishi Patel Shivang Shekhar perriefidelis
Abdulazeez Abdulazeez
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: '''[https://github.com/geekrypter/Sugar-Labs-Social Sugar Labs Social]''' is a website project which should serve a purpose to help people understand and discuss project(s) around Sugar Labs. The goal of this project is to attract Teachers, Parents, Developers and fully communicate together in one platform. : It's a social website that can be used to attract maximum users and everything ( Blogs, New projects, Software, Activities, etc) can be uploaded on it which will attract more user and create their interest. : A competitive proposal must include some evidence that the approach taken will result in some use -- just because we build it doesn't mean they will come.
;Expected results: It should have user logins, feed and a blog([https://medium.com/ medium] like) that can be over viewed by people around the world
;Knowledge prerequisites: Good Layout designing and coding experience with backend (Django, JavaScript, HTML/CSS, Mongo).

|-
| valign=top width="15%" style="background:#f7effc;" |Lilypond Methodical Improvements to how Music Blocks generates Lilypond output [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Marnen Laibow-Koser
| align=left valign=top |
;Brief explanation: Music Blocks is capable of exporting [https://www.lilypond.org Lilypond] code of which general instructions can be found [https://github.com/walterbender/musicblocks/tree/master/guide#BEYOND-MUSIC-BLOCKS here in the Music Blocks guide] and its [https://github.com/walterbender/musicblocks/ source code can be found here]. We would like to improve existing code where needed and implement needed features in a methodical way, which means we must 1) document how the Music Blocks source code works for current and future developers to learn and benefit from and 2) project manage this portion of Music Blocks development (e.g. "what works" and "what needs to be done". [https://owncloud.libretools.com/index.php/s/tgJAX5yMEzQsENf An example of a draft of a simple type of this analysis exists for you to start from.]), as well as 3) implement and improve features.
;Expected results: Implement and improve lilypond export features; Detailed documentation created for developer audience that details how Music Blocks exports to Lilypond; documentation to help manage what needs to be completed.
;Knowledge prerequisites: Literacy in reading music; functional knowledge of Lilypond code (some of your own scores would be nice); Organizational and Project Management Skills; JavaScript

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks' First Steps for Robotics [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Hrishi Patel Rishabh Thaney
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: What is needed to integrate Music Blocks with Robotics? This project is 1) to experiment with existing technologies to see what is already possible, 2) develop features (e.g. plugins, hardware modifications) needed to make interfacing possible, and 3) document the entire process and next steps
;Expected results: A working method for interfacing with a simple robot; additional features within MB to ease interfacing; and full documentation of how to recreate successful projects (that a classroom could use); communication (we do not want to guess what experiments you are doing by yourself--do not be shy to send emails, videos, pictures DAILY!!!)
;Knowledge prerequisites: Understanding of JavaScript (Music Blocks source code) and robotics (no particular method requested, just make sure it is free/libre); demonstrable documentation and self-management skills; NOTE: we value quality, clear ideas over expensive or pretty robots

|-
| valign=top width="15%" style="background:#f7effc;" |Create Examples, Compositions, and New Experiments Every Day! [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima
| align=left valign=top |
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has some examples already, but it would be nice to have one ambitious student really work for the summer to make new creative, thoughtful code everyday. (You will be expected to code in the Music Blocks language on a daily basis.) Secondary, but important goals, are bug reports when bugs are found, feature suggestions, and overall good and frequent communication with the Music Blocks team.
;Expected results: Quality examples sent daily; variety of styles; runs entire gamut in terms of blocks used (we want a number of great examples for each and every block feature); organized documentation of all examples created, which can be finalized in the final weeks of GSoC
;Knowledge prerequisites: Understanding of Music Blocks as a programming language; A good proposal is one that has a well-thought out and detailed list of music projects for each day of GSoC (time-frames, blocks used, musical styles, name of music to be transcribed); experience with music and composition/theory is a definite plus.

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks UI Improvements and Implementation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Hrishi Patel Jaskirat Singh perriefidelis
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has a good enough UI, but there are open issues remaining and it would be nice if a person with a high level of understanding of graphics and style were to proposal and implement changes that unify the entire look and feel of Music Blocks.
;Expected results: Visually unified, beautiful and intuitive Music Blocks interface. Documentation to benefit future contributors to understand "what Music Blocks style is" (obviously this may change in the future, but a thoughtful rationale for the new style is expected).
;Knowledge prerequisites: Understanding of CSS, JavaScript, and HTML. Published work on UI (links to code, websites, etc)

|-
| valign=top width="15%" style="background:#f7effc;" |Scales/Modes/Keys Design Improvements and Implementation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Marnen Laibow-Koser Sachiko Nakajima perriefidelis Jaskirat Singh
| align=left valign=top |
;Brief explanation: There are features in [https://github.com/walterbender/musicblocks/tree/master/guide#3213-setting-voice-and-keys MB for exploring modes/scales/keys which can are referenced in the guide]. However, we suspect that there are better ways to organize keys. This project would be to reimagine how MB organizes pitches. We recommend that you read the discussions that have taken place already on GitHub as well as research how keys work as well as [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF scholarly articles about temperament, scales, and tuning]. Keep in mind that we would like to prepare for the possibility of chromatic pitch spaces that are not 12--for example, a chroma of 5 or 7 or 13, etc. What features and widgets are needed?
;Expected results: Detailed documentation created for developer audience that specifies 1) proposed features and overall design, 2) purpose of design choices, 3) audit of code (e.g. What changes to our current approach may be necessary? Are there libraries that may be useful?) 4) widget design proposal as well as MB code design proposal.
;Knowledge prerequisites: Understanding of Music Theory and/or group (or set) theory. Please read the articles at https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF We are looking for candidates that can make a simple and effective design that can be implemented in JavaScript.

|-
| valign=top width="15%" style="background:#fcfcfc;"|Create UI features for music analysis and visualization [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima perriefidelis
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Music Blocks does not yet have a robust set of tools to help the user analyze their music (e.g. highest pitch, lowest pitch, pitches used, keys, musical form, intervals etc.). Additionally, users would very much benefit from features to help them visualize the way their music is constructed. Perhaps we could even create some features to help the user choose a style of music and the analysis highlights movements that violate that style's particular rules.
;Expected results: New Features.
;Knowledge prerequisites: Literacy in reading music; Music Theory knowledge; UI knowledge; JavaScript knowledge

|-
| valign=top width="15%" style="background:#f7effc;" |Music Blocks Musical Ornaments Features [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top |
;Brief explanation: The neighbor block feature is the first of a series of musical ornament features. There are many more possibilities, some of which are described [https://github.com/walterbender/musicblocks/issues/909 in issue 909]. The project would be to implement and document these features as well as to create example programs.
;Expected results: New Features, documentation, and new example programs for each new feature.
;Knowledge prerequisites: Music Theory knowledge; JavaScript knowledge; knowledge of Music Blocks and tone.js internals (please research)

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks Widget Improvements [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Music Blocks has a number of features to help users conceptualize musical concepts, which also help to create code. Please see [https://github.com/walterbender/musicblocks/tree/master/guide#widgets the guide for more]. There are a number of widgets that have not been integrated at all as well. This project would be to 1) fix widget bugs, 2) implement unfinished features ([https://github.com/walterbender/musicblocks/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+widgets+ see issues]), and 3) document and fully integrate these new features and improve existing features. [https://github.com/walterbender/musicblocks/issues/663 is also a related feature]
;Expected results: New Features, fixes, documentation, and new example programs for each new feature.
;Knowledge prerequisites: Music Theory knowledge; JavaScript knowledge; knowledge of Music Blocks and tone.js internals (please research)

|-
|valign=top width="15%" style="background:#f7effc;" |Sugarizer School Box [[File:Sugarizerschoolbox.jpg|90px|thumb|center]]
|valign=top width="15%" |Michaël Ohayon Lionel Laské Hrishi Patel Rishabh Thaney
Shivang Shekhar
| align=left valign=top|
;Brief explanation
:[https://sugarizer.org Sugarizer] is the JavaScript version of Sugar, making education available of many platforms from web to mobile.:The app is composed by both a client side and a server side.
:The idea of this project is to develop a package to simplify deployment of Sugarizer in schools.
: This package will take two forms:
: 1 - An image for Raspberry Pi that could be flashed on a sd card that could automatically start a sugarizer server at boot and displays sugarizer client on the Pi. The server will be accessible by other devices from the local network. So the teacher has just to plug the RaspberryPI to expose a WiFi and the Sugarizer Server API/WebApp. So any computer connected to this WiFi could use Sugarizer Server WebApp and any tablet with Sugarizer App connected to this WiFi could benefit to collaboration, presence and backup its content on the server.
: 2 - Create one click to deploy scripts, to deploy a full Sugarizer stack on popular providers such as Amazon AWS or Heroku. So anyone could deploy a new Sugarizer Server instance on one of popular cloud platform without the need to dig into a complex setup process.
;Expected results:Raspberry Pi image files. Deployment scripts.
;Knowledge prerequisites:[https://github.com/llaske/sugarizer-server Sugarizer Server] knowledge, Linux system administration knowledge, bash scripting capabilities, Docker enthusiasm. (This project may require to download many system files)

|-
|valign=top width="15%" style="background:#fcfcfc;"|Sugarizer Exerciser activity [[File:Sugarizerexerciser.jpg|90px|thumb|center]]
|valign=top width="15%" style="background:#fcfcfc;"|Lionel Laské Michaël Ohayon Jaskirat Singh
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation
:[https://sugarizer.org Sugarizer] is the JavaScript version of Sugar, making education available of many platforms from web to mobile.
:The idea of this project is to create a new Sugarizer activity to allow users to create exercise and let other users play to this exercise.
:The activity will propose different templates for exercises. Typical exercises could be multiple-choice question, reordering a list of items, cloze text, group assignment, ...
:Once created, the exercise could be played locally or shared on the network using Sugarizer presence. At the end of the exercise a graph will give results for each participants.
:The activity should allow to integrate multimedia element (images, sounds, videos) coming from the Journal. The activity should as simple as possible so even a child should be able to create an exercise and share it.
:Like all Sugarizer activity, the activity should: adopt the Sugar UI, be responsive (work on any screen size), work with the keyboard and with the mouse (to support touch screen), use journal and use localization.
:Features inspiration could be found on [https://learningapps.org LearningApps], [https://www.google.com/forms/ Google Forms], [https://www.limesurvey.org LimeSurvey], ...
;Expected results:A Sugarizer activity.
;Knowledge prerequisites: HTML/JavaScript, UI Design, [https://github.com/llaske/sugarizer/blob/dev/docs/tutorial.md Sugarizer Development Tutorial]

|-
| valign=top width="15%" style="background:#f7effc;"|Music Blocks export [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f7effc"| Walter Bender Devin Ulibarri Sachiko Nakajima
| align="left" valign="top" style="background:#f7effc;" |
;Brief explanation: Music Blocks is essentially a Logo interpreter. It would be great to be able to export Logo from Music Blocks. (We need to find a Logo that can handle the basic synthesizer needs to make it relevant.)
;Expected results: A Logo export that is coupled to a music-enabled Logo interpreter.
;Knowledge prerequisites: Literacy in reading music; Music Theory knowledge; UI knowledge; Logo and JavaScript knowledge

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks inline documentation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc"| Walter Bender Devin Ulibarri Sachiko Nakajima
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: There are three types of documentation for Music Blocks: documentation about how individual blocks work; short coding examples; and lesson plans. This project is about the first two. We can add inline comments to each block as it is defined in basicblocks.js from which help can be autogenerated for each block. And we can utilize the "make block" mechanism to generate on-the-fly examples of how to use blocks in combination to achieve different musical goals. The former will require some JavaScript programming; the latter, Music Blocks programming.
;Expected results: In-line documentation for each block as well as in-line Music Blocks-coded examples of the core music ideas.
;Knowledge prerequisites: UI knowledge; JavaScript knowledge; some background in music.

|-
|valign=top width="15%" style="background:#f7effc;"|Making a Beginner Guide
| valign=top width="15%" style="background:#f7effc;"| Jaskirat Singh Hrishi Patel Rishabh Thaney Shivang Shekhar Samson Goddy Abdulazeez Abdulazeez
| align=left valign=top style="background:#f7effc;"|
;Brief explanation: We don't have a beginner guide for the newcomers to the Sugar labs Community. It would be great to guide them by guiding them how to contribute through making these "form where to start? , What to start? , How to start? , Where to submit? " . An example is the Coala [http://api.coala.io/en/latest/Developers/Newcomers_Guide.html Newcomers' Guide] which is built from [https://github.com/coala/coala/blob/6dae06082017587a260189a787db9cfdc84a148b/docs/Developers/Newcomers_Guide.rst markdown source]. The goal of this task is to Help newcomers to get introduce in easy way to the world of Sugar Labs also make a dasboard for the users so they can get about developed and developing areas. Their contribution can be seen also their presence can be seen with the community.
;Expected results: A set of website pages and also documentation in Pdf form with this the problems of newcomers about their contribution will be solved and they can work easily. It is essential to this project that there is a credible maintenance regime to ensure it is easy to keep it up to date after GSoC is completed.
;Knowledge prerequisites: HTML, CSS, JavaScript(interactive) , BootStrap(responsive nav compatible on mobile devices also), PHP(dashboard), Github workflow, Markdown/up for documentation.

|}
{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #f7effc;"
|-
| valign="top" width="15%" style="background:#fcfcfc;" |Scratch 3.0 to Sugar Desktop [[File:Scratch.png|centre|thumb|99x99px]]
| valign="top" width="15%" style="background:#fcfcfc" | Walter Bender Samson Goddy
Hrishi Patel Ibiam Chihurumnaya
| align="left" valign="top" style="background:#fcfcfc;" |
;Brief explanation: [https://scratch.mit.edu/ Scratch] is a programming environment for kids. The goal of this project is to make bring back the [[Activities/Scratch|Scratch activity]] to the Sugar Desktop. Scratch 3.0 was created with HTML 5 using [https://developers.google.com/blockly/ Google’s blocky].
:# Port scratch 3.0 as a Sugar activity using method [https://github.com/sugarlabs/sugar-docs/blob/master/src/web-activity.md 1] or [https://github.com/walterbender/turtle-blocks-embedded-activity 2]. Method 1, a web activity that can run on the Sugar Desktop. While method 2, an embedded activity that can run inside browser activity. There have been some development of [https://github.com/EmilyOng/embedded-scratch-activity scratch to sugar] and a yet to release version of [https://github.com/EmilyOng/Scratch.activity scratch in Sugarizer].
:# Make the scratch libraries to work completely offline, so a user can import sprite without have issues of internet connection. A possible way is to fork the [https://github.com/LLK/scratch-storage scratch-storage] and [https://github.com/LLK/scratch-gui scratch-gui] modules to make them work offline by linking the libraries to local assets on the filesystem. https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API/Using_Service_Workers https://hackernoon.com/service-worker-one-fallback-offline-image-for-any-aspect-ratio-b427c0f897fb
;Expected results: A stable working Scratch 3 on Sugar Desktop.: User to "save project" within the scratch activity into the journal, making it easy to resume project.
: Make the Scratch activity work completely offline stated at 2.
;Knowledge prerequisites: Python, GTK, JavaScript knowledge
|}

2018-02-18T13:20:14Z

Jaskirat:

== Sponsored Projects ==

[https://summerofcode.withgoogle.com/organizations/6193990685163520/ Sugar Labs at GSoC 2018]

== Project Ideas ==

GSoC projects must involve some coding. Non-coding projects have been removed and saved into [[/Archive]].

{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #f7effc;"
|-style="background:#7409bc; color: white;"
!Title
!Mentor
!Project
|-
| valign=top width="15%" style="background:#fcfcfc;"|Python 3 port
| valign=top width="15%" style="background:#fcfcfc;"|Devel Team
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Python 3 has been here for quite some time. We've investigated how to migrate and now it is time to do it.
;Expected results: A Python 3 version of the Sugar toolkit, as well as the Sugar Desktop and a few activities.
;Knowledge prerequisites: Strong Python and GTK experience

|-
| valign=top width="15%" style="background:#f7effc;" |Migration of wiki activity pages to git
| valign=top width="15%" |Activity team
| align=left valign=top |
;Brief explanation: We have 345 pages under [[Activities]] in this wiki. It would be more sustainable in the long run if these pages were embedded (in Markdown format) in their corresponding git repositories.
;Expected results: Definition of migration process; migration of the majority of these pages
;Knowledge prerequisites: Knowledge of Markdown and Mediawiki markup; experience with git.

|-
| valign=top width="15%" style="background:#fcfcfc;"|GTK-4 exploration
| valign=top width="15%" style="background:#fcfcfc;"|Devel Team
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: GTK-4 is coming soon [https://mclasen.fedorapeople.org/gtk4-devconf2018.pdf]: probably in 2018. We need to be better prepared for the transition than we were for GTK-3.
;Expected results: Design of a workflow for transitioning from GTK-3 to GTK-4
;Knowledge prerequisites: Strong Python and GTK experience

|-
| valign=top width="15%" style="background:#f7effc;" |Internationalization and Localization
| valign=top width="15%" |Chris Leonard
Shivang Shekhar
| align=left valign=top |
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details. See [[Translation Team]] for framework description.
;Expected results: Work flow improvements for i18n
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python and JavaScript

|-
| valign=top width="15%" style="background:#fcfcfc;"|Full-color icons
| valign=top width="15%" style="background:#fcfcfc;"|Design team Jaskirat Singh perriefidelis
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: We have been discussing the implications of removing the duo-tone restriction on Sugar icons, allowing for full-color icons. We can likely use badges to compensate for any functionality we'd lose. (See [https://medium.com/@sidhant/designing-interfaces-for-education-systems-with-sugar-labs-rethinking-icons-on-sugar-614120e7ec6f] as one example of how we might proceed.)
;Expected results: A patch to Sugar that uses badges to manage the icon notifications such as activity and sharing
;Knowledge prerequisites: Knowledge of GTK; Python.

|-
| valign=top width="15%" style="background:#f7effc;" |Music Blocks optimizations [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;Brief explanation: Music Blocks has never been optimized in any way. It would be helpful to review the tone.js optimization recommendations, as well as build some unit tests to measure and improve the program itself.
;Expected results: A more robust and responsive Music Blocks.
;Knowledge prerequisites: Knowledge of JavaScript, unit testing

|-
| valign=top width="15%" style="background:#fcfcfc;"|Going Beyond Equal Temperament in Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics. See also [https://github.com/walterbender/musicblocks/labels/temperament MB issues for temperament], [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF Articles about temperament, scales, and tuning] and [https://owncloud.libretools.com/index.php/s/PmPfZ1yMhimQomG various materials related to temperament (.tb files that achieve temperament with existing MB features, videos of those files being performed, notes)]
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.
;Knowledge prerequisites: Knowledge of JavaScript, music theory

|-
| valign=top width="15%" style="background:#f7effc;" |Maintenance of activities.sugarlabs.org (ASLO)
| valign=top width="15%" | Sam CG
| align=left valign=top |
;Brief explanation: http://activities.sugarlabs.org/ is the Sugar Labs app store, where activities are hosted and downloaded. During GSoC 2017 we built ASLO v3 to address a number of deficiencies. But we have a few odds and ends that need to be addressed to bring the new site on line.
;Expected results: Update missing license and repository info on the activities found in the Sugar Labs github repository. Popular the database for the new ASLO. Do extensive testing (including creating some test suites.) Document future maintenance on the Wiki.
;Knowledge prerequisites: PHP, MySQL, Python, Apache, cron, PHP-Cake, JavaScript, HTML, CSS, and git. See [https://github.com/sugarlabs/aslo-v3].

|-
| valign=top width="15%" style="background:#f7effc;" |Just say no to GTK2
| valign=top width="15%" | Ignacio Rodriguez Cristian Garcia Abhijit Patel Ibiam Chihurumnaya Hrishi Patel
| align=left valign=top |
;Brief explanation: GTK2 and GST0.10 are end of life. We need to upgrade the remaining activities with these dependencies.
;Expected results: New versions of at least 25 existing Sugar activities.
;Knowledge prerequisites: Knowledge of GTK, GST, and Python

|-
|valign=top width="15%" style="background:#fcfcfc;"|Making a Beginner Guide
| valign=top width="15%" style="background:#fcfcfc;"| Jaskirat Singh Walter Bender Hrishi Patel Rishabh Thaney Shivang Shekhar Samson Goddy
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: We don't have a beginner guide for the newcomers to the Sugar labs Community. It would be great to guide them by guiding them how to contribute through making these "form where to start? , What to start? , How to start? , Where to submit? " . An example is the Coala [http://api.coala.io/en/latest/Developers/Newcomers_Guide.html Newcomers' Guide] which is built from [https://github.com/coala/coala/blob/6dae06082017587a260189a787db9cfdc84a148b/docs/Developers/Newcomers_Guide.rst markdown source]. The goal of this task is to Help newcomers to get introduce in easy way to the world of Sugar Labs also make a dasboard for the users so they can get about developed and developing areas. Their contribution can be seen also their presence can be seen with the community.
;Expected results: A set of website pages and also documentation in Pdf form with this the problems of newcomers about their contribution will be solved and they can work easily
;Knowledge prerequisites: community research, GitHub, coding experience (Markdown, HTML/CSS) for the guide and javascipt, PHP for making dasboard.

|-
| valign=top width="15%" style="background:#f7effc;" |Sugar Labs Social [[File:Social Site.jpg|90px|thumb|center]]
| valign=top width="15%" | Jaskirat Singh Samson Goddy Hrishi Patel Shivang Shekhar perriefidelis
| align=left valign=top |
;Brief explanation: '''Sugar Labs Social''' is a website project which should serve a purpose to help people understand and discuss project(s) around Sugar Labs. The goal of this project is to attract Teachers, Parents, Developers and fully communicate together in one platform. : It's a social website that can be used to attract maximum users and everything ( Blogs, New projects, Software, Activities, etc) can be uploaded on it which will attract more user and create their interest. : A competitive proposal must include some evidence that the approach taken will result in some use -- just because we build it doesn't mean they will come.
;Expected results: It should have user logins, feed and a blog([https://medium.com/ medium] like) that can be over viewed by people around the world
;Knowledge prerequisites: Good Layout designing and coding experience with backend (Django, JavaScript, HTML/CSS, Mongo).

|-
| valign=top width="15%" style="background:#f7effc;" |Lilypond Methodical Improvements to how Music Blocks generates Lilypond output [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Marnen Laibow-Koser
| align=left valign=top |
;Brief explanation: Music Blocks is capable of exporting [https://www.lilypond.org Lilypond] code of which general instructions can be found [https://github.com/walterbender/musicblocks/tree/master/guide#BEYOND-MUSIC-BLOCKS here in the Music Blocks guide] and its [https://github.com/walterbender/musicblocks/ source code can be found here]. We would like to improve existing code where needed and implement needed features in a methodical way, which means we must 1) document how the Music Blocks source code works for current and future developers to learn and benefit from and 2) project manage this portion of Music Blocks development (e.g. "what works" and "what needs to be done". [https://owncloud.libretools.com/index.php/s/tgJAX5yMEzQsENf An example of a draft of a simple type of this analysis exists for you to start from.]), as well as 3) implement and improve features.
;Expected results: Implement and improve lilypond export features; Detailed documentation created for developer audience that details how Music Blocks exports to Lilypond; documentation to help manage what needs to be completed.
;Knowledge prerequisites: Literacy in reading music; functional knowledge of Lilypond code (some of your own scores would be nice); Organizational and Project Management Skills; JavaScript

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks' First Steps for Robotics [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Hrishi Patel Rishabh Thaney
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: What is needed to integrate Music Blocks with Robotics? This project is 1) to experiment with existing technologies to see what is already possible, 2) develop features (e.g. plugins, hardware modifications) needed to make interfacing possible, and 3) document the entire process and next steps
;Expected results: A working method for interfacing with a simple robot; additional features within MB to ease interfacing; and full documentation of how to recreate successful projects (that a classroom could use); communication (we do not want to guess what experiments you are doing by yourself--do not be shy to send emails, videos, pictures DAILY!!!)
;Knowledge prerequisites: Understanding of JavaScript (Music Blocks source code) and robotics (no particular method requested, just make sure it is free/libre); demonstrable documentation and self-management skills; NOTE: we value quality, clear ideas over expensive or pretty robots

|-
| valign=top width="15%" style="background:#f7effc;" |Create Examples, Compositions, and New Experiments Every Day! [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima
| align=left valign=top |
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has some examples already, but it would be nice to have one ambitious student really work for the summer to make new creative, thoughtful code everyday. Secondary, but important goals, are bug reports when bugs are found, feature suggestions, and overall good and frequent communication with the Music Blocks team.
;Expected results: Quality examples sent daily; variety of styles; runs entire gamut in terms of blocks used (we want a number of great examples for each and every block feature); organized documentation of all examples created, which can be finalized in the final weeks of GSoC
;Knowledge prerequisites: Understanding of Music Blocks as a programming language; A good proposal is one that has a well-thought out and detailed list of music projects for each day of GSoC (time-frames, blocks used, musical styles, name of music to be transcribed); experience with music and composition/theory is a definite plus.

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks UI Improvements and Implementation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Hrishi Patel Jaskirat Singh perriefidelis
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: [https://walterbender.github.io/musicblocks/ Music Blocks] has a good enough UI, but there are open issues remaining and it would be nice if a person with a high level of understanding of graphics and style were to proposal and implement changes that unify the entire look and feel of Music Blocks.
;Expected results: Visually unified, beautiful and intuitive Music Blocks interface. Documentation to benefit future contributors to understand "what Music Blocks style is" (obviously this may change in the future, but a thoughtful rationale for the new style is expected).
;Knowledge prerequisites: Understanding of CSS, JavaScript, and HTML. Published work on UI (links to code, websites, etc)

|-
| valign=top width="15%" style="background:#f7effc;" |Scales/Modes/Keys Design Improvements and Implementation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Marnen Laibow-Koser Sachiko Nakajima perriefidelis Jaskirat Singh
| align=left valign=top |
;Brief explanation: There are features in [https://github.com/walterbender/musicblocks/tree/master/guide#3213-setting-voice-and-keys MB for exploring modes/scales/keys which can are referenced in the guide]. However, we suspect that there are better ways to organize keys. This project would be to reimagine how MB organizes pitches. We recommend that you read the discussions that have taken place already on GitHub as well as research how keys work as well as [https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF scholarly articles about temperament, scales, and tuning]. Keep in mind that we would like to prepare for the possibility of chromatic pitch spaces that are not 12--for example, a chroma of 5 or 7 or 13, etc. What features and widgets are needed?
;Expected results: Detailed documentation created for developer audience that specifies 1) proposed features and overall design, 2) purpose of design choices, 3) audit of code (e.g. What changes to our current approach may be necessary? Are there libraries that may be useful?) 4) widget design proposal as well as MB code design proposal.
;Knowledge prerequisites: Understanding of Music Theory and/or group (or set) theory. Please read the articles at https://owncloud.libretools.com/index.php/s/2GtAhkvQpt3fYfF We are looking for candidates that can make a simple and effective design that can be implemented in JavaScript.

|-
| valign=top width="15%" style="background:#fcfcfc;"|Create UI features for music analysis and visualization [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima perriefidelis
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Music Blocks does not yet have a robust set of tools to help the user analyze their music (e.g. highest pitch, lowest pitch, pitches used, keys, musical form, intervals etc.). Additionally, users would very much benefit from features to help them visualize the way their music is constructed. Perhaps we could even create some features to help the user choose a style of music and the analysis highlights movements that violate that style's particular rules.
;Expected results: New Features.
;Knowledge prerequisites: Literacy in reading music; Music Theory knowledge; UI knowledge; JavaScript knowledge

|-
| valign=top width="15%" style="background:#f7effc;" |Music Blocks Musical Ornaments Features [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top |
;Brief explanation: The neighbor block feature is the first of a series of musical ornament features. There are many more possibilities, some of which are described [https://github.com/walterbender/musicblocks/issues/909 in issue 909]. The project would be to implement and document these features as well as to create example programs.
;Expected results: New Features, documentation, and new example programs for each new feature.
;Knowledge prerequisites: Music Theory knowledge; JavaScript knowledge; knowledge of Music Blocks and tone.js internals (please research)

|-
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks Widget Improvements [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: Music Blocks has a number of features to help users conceptualize musical concepts, which also help to create code. Please see [https://github.com/walterbender/musicblocks/tree/master/guide#widgets the guide for more]. There are a number of widgets that have not been integrated at all as well. This project would be to 1) fix widget bugs, 2) implement unfinished features ([https://github.com/walterbender/musicblocks/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+widgets+ see issues]), and 3) document and fully integrate these new features and improve existing features. [https://github.com/walterbender/musicblocks/issues/663 is also a related feature]
;Expected results: New Features, fixes, documentation, and new example programs for each new feature.
;Knowledge prerequisites: Music Theory knowledge; JavaScript knowledge; knowledge of Music Blocks and tone.js internals (please research)

|-
|valign=top width="15%" style="background:#f7effc;" |Sugarizer School Box [[File:Sugarizerschoolbox.jpg|90px|thumb|center]]
|valign=top width="15%" |Michaël Ohayon Lionel Laské Hrishi Patel Rishabh Thaney
Shivang Shekhar
| align=left valign=top|
;Brief explanation
:[https://sugarizer.org Sugarizer] is the JavaScript version of Sugar, making education available of many platforms from web to mobile.:The app is composed by both a client side and a server side.
:The idea of this project is to develop a package to simplify deployment of Sugarizer in schools.
: This package will take two forms:
: 1 - An image for Raspberry Pi that could be flashed on a sd card that could automatically start a sugarizer server at boot and displays sugarizer client on the Pi. The server will be accessible by other devices from the local network. So the teacher has just to plug the RaspberryPI to expose a WiFi and the Sugarizer Server API/WebApp. So any computer connected to this WiFi could use Sugarizer Server WebApp and any tablet with Sugarizer App connected to this WiFi could benefit to collaboration, presence and backup its content on the server.
: 2 - Create one click to deploy scripts, to deploy a full Sugarizer stack on popular providers such as Amazon AWS or Heroku. So anyone could deploy a new Sugarizer Server instance on one of popular cloud platform without the need to dig into a complex setup process.
;Expected results:Raspberry Pi image files. Deployment scripts.
;Knowledge prerequisites:[https://github.com/llaske/sugarizer-server Sugarizer Server] knowledge, Linux system administration knowledge, bash scripting capabilities, Docker enthusiasm. (This project may require to download many system files)

|-
|valign=top width="15%" style="background:#fcfcfc;"|Sugarizer Exerciser activity [[File:Sugarizerexerciser.jpg|90px|thumb|center]]
|valign=top width="15%" style="background:#fcfcfc;"|Lionel Laské Michaël Ohayon
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation
:[https://sugarizer.org Sugarizer] is the JavaScript version of Sugar, making education available of many platforms from web to mobile.
:The idea of this project is to create a new Sugarizer activity to allow users to create exercise and let other users play to this exercise.
:The activity will propose different templates for exercises. Typical exercises could be multiple-choice question, reordering a list of items, cloze text, group assignment, ...
:Once created, the exercise could be played locally or shared on the network using Sugarizer presence. At the end of the exercise a graph will give results for each participants.
:The activity should allow to integrate multimedia element (images, sounds, videos) coming from the Journal. The activity should as simple as possible so even a child should be able to create an exercise and share it.
:Like all Sugarizer activity, the activity should: adopt the Sugar UI, be responsive (work on any screen size), work with the keyboard and with the mouse (to support touch screen), use journal and use localization.
:Features inspiration could be found on [https://learningapps.org LearningApps], [https://www.google.com/forms/ Google Forms], [https://www.limesurvey.org LimeSurvey], ...
;Expected results:A Sugarizer activity.
;Knowledge prerequisites: HTML/JavaScript, UI Design, [https://github.com/llaske/sugarizer/blob/dev/docs/tutorial.md Sugarizer Development Tutorial]

|-
| valign=top width="15%" style="background:#f7effc;"|Music Blocks exporrt [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f7effc"| Walter Bender Devin Ulibarri Sachiko Nakajima
| align=left valign=top style="background:#f7effc;"|
;Brief explanation: Music Blocks is essentially a Logo interpreter. It would be great to be able to export Logo from Music Blocks. (We need to find a Logo that can handle the basic synthesizer needs to make it relevant.)
;Expected results: A Logo export that is coupled to a music-enabled Logo interpreter.
;Knowledge prerequisites: Literacy in reading music; Music Theory knowledge; UI knowledge; Logo and JavaScript knowledge

|-
| valign=top width="15%" style="background:#fcfcfc"|Sugarizer Primero (Sugarizer1°)
| valign=top width="15%" style="background:#fcfcfc;"|Education Team Caryl Bigenho Samson Goddy Jaskirat Singh perriefidelis
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation: [https://github.com/llaske/sugarizer Sugarizer] is a large collection of many Activities suitable for general audiences. This project will package a subset of the Activities (Minimum of 10 activites) suitable for children with a target age of 4-7 (grades Pre-K-2) and with a friendly UI/UX experience.

:Some new activity development will be required, e.g., The original TamTam had a keyboard that the user could use to play songs with their choice of instrumental sounds. Currently the version of TamTam in Sugarizer only allows the user to make a sound of one note on their chosen instrument. TamTam for Sugar Primero will have a keyboard option that will permit the playing of simple songs.

:A user's guide with suggestions for using them to meet educational goals while having fun.

;Expected results: Sugar Primero will be available for free from all of the app stores
;Knowledge prerequisites: Knowledge of JavaScript, some knowledge of Primary school curriculum.
|}

User:Jaskirat

2018-02-17T18:10:59Z

Jaskirat:

2018-01-23T16:22:57Z

2018-01-20T16:25:27Z

Jaskirat:

File:Lt15142 1.jpg

2018-01-20T16:25:12Z

Jaskirat: