193
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + + + + + + + + + + + + + + + + + + + + − + + Line 47:
Line 67: − + − + − + + + + + + + + + Line 68:
Line 96: − − |- − | 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]. − + − + Line 86:
Line 106: − + − + + − + − ;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<br>[[File:Social Site.jpg|90px|thumb|center]] − | valign=top width="15%" | Jaskirat Singh<br>Samson Goddy<br>Hrishi Patel<br>Shivang Shekhar<br>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. − Line 109:
Line 121: − Line 123:
Line 134: − + Line 129:
Line 140: − + − Line 138:
Line 148: − + Line 146:
Line 156: − + Line 184:
Line 194: − + Line 198:
Line 208: − + − + Line 206:
Line 216: − + − + − + − + + + + + + + + + + + + − + + + + + + + + + + + + + + + + + + + − + + + + + − ;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.
no edit summary
== Sponsored Projects ==
== Selected Projects for summer 2018 ==
;Rahul Bothra | Pro-Panda: Port Sucrose from Python 2 to Python 3 ([http://www.pro-panda.tech blog])
;Riya Lohia: Going Beyond Equal Temperament in Music Blocks ([https://medium.com/gsoc18-with-sugar-labs blog])
;Ritwik Abhishek: Music Blocks Widget Improvement ([https://musicblocks18.wordpress.com/ blog])
;Vaibhav Aren: Interactive Exercises for Turtle Blocks ([https://vaibhavdaren.wordpress.com/ blog])
;Aman Sharma: Sugarizer School Box ([https://amansharmablogblog.wordpress.com/2018/04/26/introduction-to-the-community/ blog])
;Vipul Gupta: Activity Migration ([https://mixstersite.wordpress.com/gsoc2018/ blog])
;Anmol Mishra: Port to Python 3 ([https://medium.com/anmolmishra-jiit blog])
;Iqra Muhammad: Sugarizer Primero ([https://iqragsoc.wordpress.com/ blog])
;Mankirat Singh: Sugarizer Exerciser Activity ([https://mankiratsinghtech.wordpress.com/2018/04/27/google-summer-of-code-2018/ blog])
;Rudra Sadhu: [https://wiki.sugarlabs.org/go/Summer_of_Code/2018/attentive_migration_of_wiki_activity_pages_to_git Migration of activity wiki-pages to GitHub (and simultaneously help-activity)] ([https://rdrsadhu.github.io/blog/gsoc2018/ blog])
;Yash Aragwal:Just say no to GTK+ 2 ([https://medium.com/@yashagrawal3/gsoc-18-with-sugar-labs-2d9bc733cf59 blog])
;Pratul Kumar:Beginner's Guide ([https://medium.com/@pratulkumar/gsoc-introduction-to-the-community-ed47e04e3051 blog])
[https://summerofcode.withgoogle.com/organizations/6193990685163520/ Sugar Labs at GSoC 2018]
[https://summerofcode.withgoogle.com/organizations/6193990685163520/ Sugar Labs at GSoC 2018]
=== Meetings ===
We meet as a group in IRC every Friday at 22IST, 12:30ET, 16:30UTC. The meetings are logged at http://meeting.sugarlabs.org/sugar-meeting/meetings
----
== Project Ideas ==
== Project Ideas ==
GSoC projects must involve some coding. Non-coding projects have been removed and saved into [[/Archive]].
'''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;"
{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #f7effc;"
|-
|-
| valign=top width="15%" style="background:#fcfcfc;"|Full-color icons
| valign=top width="15%" style="background:#fcfcfc;"|Full-color icons
| valign=top width="15%" style="background:#fcfcfc;"|Design team<br> Jaskirat Singh<br>perriefidelis
| valign=top width="15%" style="background:#fcfcfc;"|Design team<br> Jaskirat Singh<br>Peace Ojemeh
| align=left valign=top style="background:#fcfcfc;"|
| 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.)
;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 and sharing
;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.
;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 <br> Jaskirat Singh<br>
| 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.
|-
|-
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.
;Knowledge prerequisites: Knowledge of JavaScript, music theory
;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;" |Just say no to GTK2
| valign=top width="15%" | Ignacio Rodriguez<br>Cristian Garcia<br/>Abhijit Patel<br>Ibiam Chihurumnaya<br/>Hrishi Patel
| valign=top width="15%" style="background:#f7effc;"| Ignacio Rodriguez<br>Cristian Garcia<br/>Abhijit Patel<br>Ibiam Chihurumnaya<br/>Hrishi Patel
| align=left valign=top |
| 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.
;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.
;Expected results: New versions of at least 25 existing Sugar activities.
|-
|-
|valign=top width="15%" style="background:#fcfcfc;"|Making a Beginner Guide
| valign=top width="15%" style="background:#fcfcfc;" |Sugar Labs Social<br>[[File:Social Site.jpg|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Jaskirat Singh<br>Walter Bender<br>Hrishi Patel<br/>Rishabh Thaney<br>Shivang Shekhar<br/>Samson Goddy
| valign=top width="15%" style="background:#fcfcfc;"| Jaskirat Singh<br>Samson Goddy<br>Hrishi Patel<br>Shivang Shekhar<br>Peace Ojemeh
Abdulazeez Abdulazeez
| align=left valign=top style="background:#fcfcfc;"|
| 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.
;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
;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).
;Knowledge prerequisites: Good Layout designing and coding experience with backend (Django, JavaScript, HTML/CSS, Mongo).
|-
|-
;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.
;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
;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%" | Walter Bender<br>Devin Ulibarri<br>Sachiko Nakajima
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri<br>Sachiko Nakajima
| align=left valign=top |
| 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.
;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
;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.
;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 <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks UI Improvements and Implementation <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender<br>Devin Ulibarri<br>perriefidelis
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender<br>Devin Ulibarri<br>Hrishi Patel<br> Jaskirat Singh<br>Peace Ojemeh
Hrishi Patel<br> Jaskirat Singh
| align=left valign=top style="background:#fcfcfc;"|
| 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.
;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.
|-
|-
| valign=top width="15%" style="background:#f7effc;" |Scales/Modes/Keys Design Improvements and Implementation <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f7effc;" |Scales/Modes/Keys Design Improvements and Implementation <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri<br>Marnen Laibow-Koser<br>Sachiko Nakajima<br>perriefidelis
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri<br>Marnen Laibow-Koser<br>Sachiko Nakajima<br>Peace Ojemeh<br>Jaskirat Singh
| align=left valign=top |
| 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?
;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?
|-
|-
| valign=top width="15%" style="background:#fcfcfc;"|Create UI features for music analysis and visualization <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"|Create UI features for music analysis and visualization <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender<br>Devin Ulibarri<br>Sachiko Nakajima<br>perriefidelis
| valign=top width="15%" style="background:#fcfcfc;"| Walter Bender<br>Devin Ulibarri<br>Sachiko Nakajima<br>Peace Ojemeh
| align=left valign=top style="background:#fcfcfc;"|
| 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.
;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.
|-
|-
|valign=top width="15%" style="background:#fcfcfc;"|Sugarizer Exerciser activity<br>[[File:Sugarizerexerciser.jpg|90px|thumb|center]]
|valign=top width="15%" style="background:#fcfcfc;"|Sugarizer Exerciser activity<br>[[File:Sugarizerexerciser.jpg|90px|thumb|center]]
|valign=top width="15%" style="background:#fcfcfc;"|Lionel Laské<br>Michaël Ohayon
|valign=top width="15%" style="background:#fcfcfc;"|Lionel Laské<br>Michaël Ohayon<br>Jaskirat Singh
| align=left valign=top style="background:#fcfcfc;"|
| align=left valign=top style="background:#fcfcfc;"|
;Brief explanation
;Brief explanation
|-
|-
| valign=top width="15%" style="background:#f7effc;"|Music Blocks exporrt <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f7effc;"|Music Blocks export <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f7effc"| Walter Bender<br>Devin Ulibarri<br>Sachiko Nakajima
| valign=top width="15%" style="background:#f7effc"| Walter Bender<br>Devin Ulibarri<br>Sachiko Nakajima
| align=left valign=top style="background:#f7effc;"|
| 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.)
;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.
;Expected results: A Logo export that is coupled to a music-enabled Logo interpreter.
|-
|-
| valign=top width="15%" style="background:#fcfcfc"|Sugarizer Primero (Sugarizer1°)
| valign=top width="15%" style="background:#fcfcfc;"|Music Blocks inline documentation <br>[[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#fcfcfc;"|Education Team<br>Caryl Bigenho<br>Samson Goddy<br>Jaskirat Singh<br>perriefidelis
| valign=top width="15%" style="background:#fcfcfc"| Walter Bender<br>Devin Ulibarri<br>Sachiko Nakajima
| align=left valign=top style="background:#fcfcfc;"|
| 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.
;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<br/>Hrishi Patel<br/>Rishabh Thaney<br/>Shivang Shekhar<br/>Samson Goddy<br/>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.
: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.
|}
{| 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<br>[[File:Scratch.png|centre|thumb|99x99px]]
| valign="top" width="15%" style="background:#fcfcfc" | Walter Bender<br>Samson Goddy
Hrishi Patel<br>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
:A user's guide with suggestions for using them to meet educational goals while having fun.
Peace Ojemeh
| 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.
|}
|}