Sugar Labs

Changes

Summer of Code/2018 (view source)

Revision as of 11:10, 6 March 2018

4,198 bytes removed ,  11:10, 6 March 2018
→‎Project Ideas
Line 68: Line 68:  
;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;" |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 84: Line 76:  
;Expected results: New versions of at least 25 existing Sugar activities.
 
;Expected results: New versions of at least 25 existing Sugar activities.
 
;Knowledge prerequisites: Knowledge of GTK, GST, and Python
 
;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<br>Walter Bender<br>Hrishi Patel<br/>Rishabh Thaney<br>Shivang Shekhar<br/>Samson Goddy
  −
Abdulazeez Abdulazeez
  −
| 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.
      
|-
 
|-
Line 102: Line 85:  
;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).
−
      
|-
 
|-
Line 111: Line 93:  
;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
−
      
|-
 
|-
Line 120: Line 101:  
;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!!!)
 
;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
 
;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! <br>[[File:Music-Blocks.png|90px|thumb|center]]
  −
| valign=top width="15%" | Walter Bender<br>Devin Ulibarri<br>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.
      
|-
 
|-
Line 206: Line 179:  
;Knowledge prerequisites: Literacy in reading music; Music Theory knowledge; UI knowledge; Logo and JavaScript knowledge
 
;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<br>Caryl Bigenho<br>Samson Goddy<br>Jaskirat Singh<br>perriefidelis
  −
Abdulazeez Abdulazeez
  −
| 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.
 
: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.
Retrieved from "https://wiki.sugarlabs.org/go/Special:MobileDiff/101397"