Sugar Labs - User contributions [en]

Google Code In 2019

2019-10-12T13:01:59Z

Rishabh42: Added Rishabh Thaney to the list

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

Sugar Labs community members: please feel free to add tasks below.

== Message to potential participants ==

It is important that you obtain permission of your parents.

Es importante que obtengas el permiso de tus padres para participar.

Please see the Contest Rules for Eligibility and Registration process.

https://codein.withgoogle.com/student-terms/

Also, you will likely need to set up the Sugar development environment. See http://developer.sugarlabs.org/dev-environment.md.html for details. Further information about contributing to the project can be found here: http://developer.sugarlabs.org/

Please don't hesitate to ask questions on our IRC channel (#sugar on irc.freenode.net) or on the sugar-devel list: sugar-devel AT lists.sugarlabs DOT org
(See [[Google_Code_In_2019#Getting_set_up_on_IRC|below]] for details regarding setting up an IRC account.)

== Why Sugar Labs is participating ==

Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.

== Some background from GCI ==

[See https://developers.google.com/open-source/gci/resources/getting-started]

===Open Source Fundamentals ===

You can contribute without being a coder!
You do not have to be a coder to contribute to open source. There are many different skill sets needed to help an open source community thrive:
;Documentation: If you are a good writer and enjoy attention to detail then you might want to contribute by writing or editing documentation. Documentation is a huge part of a successful open source project. Organizations need documentation to help attract new contributors as it helps them see what the codebase looks like and where things are and what the plan is for the project.
;Research: An organization may need help crunching numbers or sorting through pages of documents to better understand what the users want or need. There are many different types of tasks that students could work on that are very important to the health of the project.
;Outreach: If you have an outgoing personality and like being around and talking to people, take a look at the outreach tasks. Outreach tasks often include hosting meetups in your local community or creating a plan on how people around the globe can host a meetup about the project in their local communities.
;Training: You could create a YouTube video discussing a new feature of the project or maybe some basics on what the project does so people who haven’t heard about it can understand the project and get involved.
;User Interface: User interface can include many types of tasks including designing new aspects of a web page or creating a new logo for the project. It may also include various accessibility opportunities to help make the project easier for people who are blind.
;Other: If you have an idea that may help an organization, reach out to them and let them know! Sometimes the best task is one that the organization hasn’t even considered yet.
=== Collaboration===
Open source is not just about coding but working with other people to find the best solution. Being a part of the community is an essential part of success in Google Code-in. Mentors tell us every year that their best students were the ones who worked hard on their projects but also participated on IRC and helped answer questions other students had. Collaborate with the community and mentors on the #sugar channel in the irc.freenode.net network.

=== Quality over Quantity ===

It’s not about being the student who completes the most tasks, that only gets you to the top 10 to be reviewed, it doesn’t mean you will be a grand prize winner. We have had quite a few students who completed the most tasks for their organization yet were not named as Grand Prize Winners because they did everything solo and didn’t get involved in the community or think about the health of the project as a whole, they just kept completing task after task like a machine. If you actively participate in the community then you not only feel the camaraderie that comes with working as a team but you become committed to making the project better for everyone.

== Some basics about Sugar Labs and Sugar development ==

For some basics about the project, see [http://people.sugarlabs.org/walter/docs/Learning-to-Change-the-World-Chapter-4.pdf Chapter 4 of Learning to Change the World].

{{:Google Code In 2018/background}}

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

Note, more detailed task descriptions will be available once the contest begins.

=== Beginner tasks ===
# Install the Sugar development environment by following the instruction at [http://developer.sugarlabs.org/dev-environment.md.html].
# Install Sugar in a virtual machine.
# Install Sugar packages on Ubuntu, Debian, or Fedora.
# Install Sugarizer on a Raspberry Pi for use by nearby computers, tablets, or phones.
# Create an example program in Turtle Blocks (See [https://www.pinterest.com/walterbender/turtle-art/] for some ideas).
# Create an example program in Music Blocks.
# Create a simple machine in Physics.

=== General tasks ===
# Organize a Turtle Art Day (or Music Blocks Day) in your community (Outreach)
# Create a 60 second promotional video on Sugar and its community (Outreach)
# Host a Question and Answer (Q&A)/Information session about Sugar on Google Hangouts. (Outreach)
# DIY Sugar on a Stick||Organize and host a Sugar on a Stick party where you show people how to make their own Sugar on a Stick. (Outreach)
# Find an educator who is using open-source educational software to teach. Interview the educator about their experience as an educator and why they are using open-source software to teach. (Outreach)
# Write a blog post about your experience as a GCI participant for Sugar Labs. (Outreach)
# Create a 10-minute presentation celebrating at least three women within the Sugar community and/or the open-source community at large. (Research/Outreach)
# Gather information on who could benefit from using or knowing about Sugar. (Research)
# Find the resources that people are using throughout the world to learn about or teach Sugar Activities. (Research)
# Find the missing repo: we've lost track of the source repository of some Sugar activities: help us find them (Research)
# Wiki cleanup (Documentation)
# Music Blocks examples (Documentation/Training)
# Write a review about an Activity in Sugar. (Documentation)
# Create a unit tests for a JavaScript activity (Quality assurance)
# Test old Sugar activities and report any really obvious problems (Quality assurance)
# Refactor Turtle graphics to adopt look of Javascript version (Code: Python)
# write a Python/GTK version of Music Blocks
# Investigate CSound/Python version of Music Blocks (Code: Python)
# Resolve an open issue from https://github.com/sugarlabs/ (Code: Python)
# Plugin manager for Turtle JS (Code: Javascript)
# Add Lilypond import to Music Blocks (Code: Javascript)
# Write a Turtle plugin (Code: Javascript)
# Write a extruder in JavaScript to convert from SVG to STL for 3D printing. (Code: JavaScript)
# Write a slicer in JavaScript to convert between SL and GCODE for 3D printing. (Code: JavaScript)
# Resolve an open issue from https://github.com/walterbender/musicblocks/ (Code: JavaScript)
# Port a Sugarizer activity to Sugar (Code: Javascript)
# Port an old Sugar activity to the most recent Sugar (Code: Python)

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

Tasks must fall within one of these five categories: [[#Documentation/Training]]; [[#Outreach/Research]]; [[#User Interface]]; [[#Quality Assurance]]; and [[#Code]].

== Mentors ==
;NOTES TO MENTORS:
:Please note that not all tasks are coding tasks so please consider participating even if you are not a coder (there are research, outreach, design, and documentation tasks as well).
:But also note that prior participation in the Sugar Labs community is a requirement for mentoring.

Send an email to one of the Org Admins (this year they are Walter and TBD). You will then receive an invitation by email.
Follow the instructions in the email to sign up as a Sugar Labs mentor.
:Please add yourself to the list below.
:Feel free to add new tasks to the table above.

Depending on the task, we will assign multiple mentors from our various development and support teams.

* Walter Bender - co-administrator
* James Cameron - release manager
* Sumit Srivastava - Mentor for Coding, Design, and QA tasks.
* Jaskirat Singh - Mentor for Research, Documentation, Design and Testing tasks
* Vaibhav Aren - Mentor for Coding, Research, Documentation, Design and Testing tasks.
* Hrishi Patel - Mentor for Coding, Research, Documentation, Design and QA tasks.
* Amaan Iqbal - Mentor for Coding, Research, Documentation, Design, and Testing Tasks
* Pratul Kumar - Mentor for Coding, Beginner First Issues, Git and Github, Documentation.
* Rishabh Thaney - Mentor for Coding, Research, Documentation, Design and Testing tasks.

Summer of Code/2018

2018-02-02T14:42:30Z

Rishabh42: Added my name to some of the ideas

== Sponsored Projects ==

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

== Project Ideas ==

{| border="1" cellpadding="3" style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
!Title
!Mentor
!Project
|-
| valign=top width="15%" style="background:#e3e4e5;" |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:#f3f4f5;"|GTK-4 exploration
| valign=top width="15%" style="background:#f3f4f5;"|Devel Team
| align=left valign=top style="background:#f3f4f5;"|
;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:#e3e4e5;" |Internationalization and Localization
| valign=top width="15%" |Chris Leonard
| 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:#f3f4f5;"|Full-color icons
| valign=top width="15%" style="background:#f3f4f5;"|Design team Jaskirat Singh
| align=left valign=top style="background:#f3f4f5;"|
;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:#e3e4e5;" |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:#f3f4f5;"|Going Beyond Equal Temperament in Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f3f4f5;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top style="background:#f3f4f5;"|
;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:#e3e4e5;" |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:#f3f4f5;"|Lesson Plans for Music Blocks [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f3f4f5;"| Walter Bender Devin Ulibarri Sachiko Nakajima Hrishi Patel
| align=left valign=top style="background:#f3f4f5;"|
;Brief explanation: We have a [https://github.com/walterbender/musicblocks/blob/master/guide/README.md Guide], but we really need some more scaffolding in the form of lesson plans.
;Expected results: A website and PDF document that can be bound.
;Knowledge prerequisites: Knowledge of music theory, writing skills

|-
| valign=top width="15%" style="background:#e3e4e5;" |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:#f3f4f5;"|Updating a new design of Sugarlabs wiki
| valign=top width="15%" style="background:#f3f4f5;"| Jaskirat Singh Walter bender
Hrishi Patel

Rishabh Thaney
| align=left valign=top style="background:#f3f4f5;"|
;Brief explanation: we are lacking in look of wiki.sugarlabs.org page. It looks ugly and unfriendly and need to be updated with a good design
;Expected results: New design of Wiki page of Sugarlabs
;Knowledge prerequisites: Knowledge of mediawiki and use of some basic languages

|-
|valign=top width="15%" style="background:#e3e4e5;" |Outreach
| valign=top width="15%" | Walter Bender
| align=left valign=top |
;Brief explanation: We don't have a very friendly approach to outreach to new contributors. It would be great to make it easier to get involved and to navigate the path towards contributing to Sugar Labs. The goal of this project is to revamp our approach to outreach.
;Expected results: A set of pages similar to [https://publiclab.github.io/community-toolbox/] and [https://publiclab.org/wiki/software-outreach]
;Knowledge prerequisites: community outreach experience; some coding experience (to create requisite artifacts)

|-
|valign=top width="15%" style="background:#f3f4f5;"|Making a Beginner Guide
| valign=top width="15%" style="background:#f3f4f5;"| Jaskirat Singh Walter Bender
Hrishi Patel

Rishabh Thaney
| align=left valign=top style="background:#f3f4f5;"|
;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? " . [http://api.coala.io/en/latest/Developers/Newcomers_Guide.html Example] The goal of this project is to Help newcomers to get introduce in easy way to the world of Sugar Labs
;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 ( HTML, CSS )

|-
| valign=top width="15%" style="background:#e3e4e5;" |New Social Sugarlabs website [[File:Social Site.jpg|90px|thumb|center]]
| valign=top width="15%" | Jaskirat Singh Samson Goddy
Hrishi Patel
| align=left valign=top |
;Brief explanation: Its a social website that can be used to attract maximum users and everything ( Blogs, New projects, Softwares, Activities, etc) can be uploaded on it which will attract more user and create their interest
;Expected results: It should have user logins, feed and a blog thst can be over viewed by people around the world
;Knowledge prerequisites: Good Layout designing and coding experience

|-
| valign=top width="15%" style="background:#f3f4f5;"|Making a marketing animated website page of sugarlabs
| valign=top width="15%" style="background:#f3f4f5;"| Jaskirat Singh Samson Goddy
Hrishi Patel
| align=left valign=top style="background:#f3f4f5;"|
;Brief explanation:We need to develop a link that is website-page that will include a page with animations explaining all the things we have in Sugarlabs (as a marketing) like these examples [http://meta-liquid.com/ See[1] ], [http://education.iceandsky.com/ See [2] ]
;Expected results: A UI/UX layout and a main page that can be used to market the things in an animated way
;Knowledge prerequisites: Knowledge of marketing and use of some basic languages ( HTML, CSS styling, PHP)

|-
| valign=top width="15%" style="background:#e3e4e5;" |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:#f3f4f5;"|<strike>Migrating Planet Sugar to Medium</strike>
| valign=top width="15%" style="background:#f3f4f5;"| Jaskirat Singh Samson Goddy
| align=left valign=top style="background:#f3f4f5;"|
;Brief explanation:We need to change the look of [http://planet.sugarlabs.org/ Planet Sugar] by embedding [[https://medium.com/|Medium (a blogger)]] into it by using Medium API but design should be changed> Better and interactive layout.
;Expected results: A UI/UX layout and an interactive design which can be easy to use and outreach more.
;Knowledge prerequisites: Knowledge of web designing and use of some basic languages ( HTML, CSS styling, JavaScript, PHP)

|-
| valign=top width="15%" style="background:#e3e4e5;" |Making Testimonials page on Sugar Labs website
| valign=top width="15%" | Jaskirat Singh Walter Bender
| align=left valign=top |
;Brief explanation:Well, Develop a testimonal webpage on Sugarlabs website by making a good research about the users who have experienced the world of Sugar. That should include videos, blog posts and many more things. For such type of layout example visit ( https://www.chownow.com/testimonials-reviews ) and ( https://www.codecademy.com/stories )
;Expected results: A good layout with more views about sugar Users
;Knowledge prerequisites: Make a research about people using Sugar ...get interaction with them ; know about Sugarlabs and use of some basic languages ( HTML, CSS styling, JavaScript, PHP)

|-
| valign=top width="15%" style="background:#f3f4f5;"|Music Blocks' First Steps for Robotics [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f3f4f5;"| Walter Bender Devin Ulibarri
Hrishi Patel

Rishabh Thaney
| align=left valign=top style="background:#f3f4f5;"|
;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); demonstratable documentation and self-management skills; NOTE: we value quality, clear ideas over expensive or pretty robots

|-
| valign=top width="15%" style="background:#e3e4e5;" |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 program; A good proposal is one that has a well-thought out and detailed list of music projects for each day of GSoC (timeframes, blocks used, musical styles, name of music to be transcribed); experience with music and composition/theory is a definate plus.

|-
| valign=top width="15%" style="background:#f3f4f5;"|Music Blocks UI Improvements and Implementation [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f3f4f5;"| Walter Bender Devin Ulibarri
Hrishi Patel Jaskirat Singh
| align=left valign=top style="background:#f3f4f5;"|
;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:#e3e4e5;" |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
| 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 a future (or current) developer could read and implement.

|-
| valign=top width="15%" style="background:#f3f4f5;"|Create UI features for music analysis and visualization [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f3f4f5;"| Walter Bender Devin Ulibarri Sachiko Nakajima
| align=left valign=top style="background:#f3f4f5;"|
;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:#e3e4e5;" |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:#f3f4f5;"|Music Blocks Widget Improvements [[File:Music-Blocks.png|90px|thumb|center]]
| valign=top width="15%" style="background:#f3f4f5;"| Walter Bender Devin Ulibarri Sachiko Nakajima Marnen Laibow-Koser
| align=left valign=top style="background:#f3f4f5;"|
;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:#e3e4e5;" |Sugarizer School Box [[File:Sugarizerschoolbox.jpg|90px|thumb|center]]
|valign=top width="15%" |Michaël Ohayon Lionel Laské
Hrishi Patel

Rishabh Thaney
| 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:#f3f4f5;"|Sugarizer Exerciser activity [[File:Sugarizerexerciser.jpg|90px|thumb|center]]
|valign=top width="15%" style="background:#f3f4f5;"|Lionel Laské Michaël Ohayon
| align=left valign=top style="background:#f3f4f5;"|
;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]
|}

Google Code In 2017

2017-10-13T02:55:27Z

Rishabh42: Added my name to the list of mentors

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

This is the project page for the Sugar Labs application to [https://developers.google.com/open-source/gci/ Google Code In 2017]. Sugar Labs community members: please feel free to add tasks below. We'll do an edit before final applications are due the fourth week of October 2017.

== 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.

https://developers.google.com/open-source/gci/resources/contest-rules

Please see the Contest Rules for Eligibility and Registration process.

https://developers.google.com/open-source/gci/resources/contest-rules

'''Details regarding the required forms and paperwork are here: [[Google Code In 2017/Participate#Students]].'''

Also, you will likely need to set up the Sugar development environment. See http://developer.sugarlabs.org/dev-environment.md.html for details. Further information about contributing to the project can be found here: http://developer.sugarlabs.org/

Please don't hesitate to ask questions on our irc channel (#sugar on irc.freenode.net) or on the sugar-devel list: sugar-devel AT lists.sugarlabs DOT org

== Why Sugar Labs is participating ==

Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.

== Some background from GCI ==

[See https://developers.google.com/open-source/gci/resources/getting-started]

===Open Source Fundamentals ===

You can contribute without being a coder!
You do not have to be a coder to contribute to open source. There are many different skill sets needed to help an open source community thrive:
;Documentation: If you are a good writer and enjoy attention to detail then you might want to contribute by writing or editing documentation. Documentation is a huge part of a successful open source project. Organizations need documentation to help attract new contributors as it helps them see what the codebase looks like and where things are and what the plan is for the project.
;Research: An organization may need help crunching numbers or sorting through pages of documents to better understand what the users want or need. There are many different types of tasks that students could work on that are very important to the health of the project.
;Outreach: If you have an outgoing personality and like being around and talking to people, take a look at the outreach tasks. Outreach tasks often include hosting meetups in your local community or creating a plan on how people around the globe can host a meetup about the project in their local communities.
;Training: You could create a YouTube video discussing a new feature of the project or maybe some basics on what the project does so people who haven’t heard about it can understand the project and get involved.
;User Interface: User interface can include many types of tasks including designing new aspects of a webpage or creating a new logo for the project. It may also include various accessibility opportunities to help make the project easier for people who are blind.
;Other: If you have an idea that may help an organization, reach out to them and let them know! Sometimes the best task is one that the organization hasn’t even considered yet.
=== Collaboration===
Open source is not just about coding but working with other people to find the best solution. Being a part of the community is an essential part of success in Google Code-in. Mentors tell us every year that their best students were the ones who worked hard on their projects but also participated on IRC and helped answer questions other students had. Collaborate with the community and mentors on the #sugar channel in the irc.freenode.net network.

=== Quality over Quantity ===

It’s not about being the student who completes the most tasks, that only gets you to the top 10 to be reviewed, it doesn’t mean you will be a grand prize winner. We have had quite a few students who completed the most tasks for their organization yet were not named as Grand Prize Winners because they did everything solo and didn’t get involved in the community or think about the health of the project as a whole, they just kept completing task after task like a machine. If you actively participate in the community then you not only feel the camaraderie that comes with working as a team but you become committed to making the project better for everyone.

== Some basics about Sugar Labs and Sugar development ==

For some basics about the project, see [http://people.sugarlabs.org/walter/docs/Learning-to-Change-the-World-Chapter-4.pdf Chapter 4 of Learning to Change the World].

{{:Google Code In 2017/background}}

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

Note, more detailed task descriptions will be available once the contest begins.

=== beginner tasks ===
# Install the Sugar development environment by following the instruction at [http://developer.sugarlabs.org/dev-environment.md.html].
# Install Sugar in a virtual machine.
# Install Sugar packages on Ubuntu, Debian, or Fedora.
# Create an example program in Turtle Blocks (See [https://www.pinterest.com/walterbender/turtle-art/] for some ideas).
# Create an example program in Music Blocks.
# Create a simple machine in Physics.

=== general tasks ===
# Organize a Turtle Art Day (or Music Blocks Day) in your community (Outreach)
# Create a 60 second promotional video on Sugar and its community (Outreach)
# Host a Question and Answer (Q&A)/Information session about Sugar on Google Hangouts. (Outreach)
# DIY Sugar on a Stick||Organize and host a Sugar on a Stick party where you show people how to make their own Sugar on a Stick. (Outreach)
# Find an educator who is using open-source educational software to teach. Interview the educator about their experience as an educator and why they are using open-source software to teach. (Outreach)
# Write a blog post about your experience as a GCI participant for Sugar Labs. (Outreach)
# Create a 10-minute presentation celebrating at least three women within the Sugar community and/or the open-source community at large. (Research/Outreach)
# Gather information on who could benefit from using or knowing about Sugar. (Research)
# Find the resources that people are using throughout the world to learn about or teach Sugar Activities. (Research)
# Find the missing repo: we've lost track of the source repository of some Sugar activities: help us find them (Research)
# Investigate Google Fuzzing tool (Research)
# Add more synths/sound fonts to Music Blocks (Research)
# Design the music equivalent of Turtle Confusion for Music Blocks (Research)
# Wiki cleanup (Documentation)
# Music Blocks examples (Documentation/Training)
# Write a review about an Activity in Sugar. (Documentation)
# How should the Sugar UI change to accommodate a small screen? (User interface)
# What else should be made easier to customize in Sugar with minimal programming? (User interface)
# Create a unit tests for a JavaScript activity (Quality assurance)
# Bugzilla clean up (Quality assurance)
# Refactor Turtle graphics to adopt look of Javascript version (Code: Python)
# Refactor Planet server for Turtle Blocks (Code: Python)
# Write a Pinetrest plugin for the Sugar Journal (Code: Python)
# Investigate CSound/Python version of Music Blocks (Code: Python)
# Resolve an open issue from https://github.com/sugarlabs/ (Code: Python)
# Teach me how to draw activity (Code: Javascript)
# Plugin manager for Turtle JS (Code: Javascript)
# Improvements to Lilypond interface (Code: Javascript)
# Add ABC import to Music Blocks (Code: Javascript)
# Add Lilypond import to Music Blocks (Code: Javascript)
# Write a Turtle plugin (Code: Javascript)
# Visualize turtle movements in Pitch-Time Matrix (Code: Javascript)
# Visualize turtle pitch in Music Blocks widget (Code: Javascript)
# Write a JavaScript version of [http://activities.sugarlabs.org/en-US/sugar/addon/4450 Turtle Confusion] (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)
# Rewrite turtleblocksjs server (https://github.com/tchx84/turtleblocksjs-server) using NodeJS, express (https://www.npmjs.com/package/express) may be a good module to use (Code: Javascript)

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

Tasks must fall within one of these five categories: [[#Documentation/Training]]; [[#Outreach/Research]]; [[#User Interface]]; [[#Quality Assurance]]; and [[#Code]].

== Mentors ==
;NOTES TO MENTORS:
:Please refer to [[Google Code In 2017/Participate#Mentors]] for details regarding enrolling as a mentor.
:Please add yourself to the list below.
:Feel free to add new tasks to the table above.

Depending on the project, we will assign multiple mentors from our various development and support teams.

* Walter Bender - co-administrator
* Ignacio Rodriguez -co-administrator
* Hrishi Patel
* Tayba Wasim(Tabs16)
* Ibiam Chihurumnaya
* Rishabh Thaney

Debian/Raspberry Pi

2017-08-24T18:16:14Z

Rishabh42: Updated the page with auto login's current status

== Download ==

Rishabh Thaney has made builds for Raspberry Pi using Debian;

* [https://people.sugarlabs.org/rishabh/ https://people.sugarlabs.org/rishabh/],

See also:

* [[Summer_of_Code/2017|GSoC 2017 Project Ideas]] by Sugar Labs,
* [[Summer_of_Code/Rishabh_Thaney|GSoC 2017 Proposal]] by Rishabh, and;
* [https://sugaronraspberrypi.wordpress.com/ GSoC 2017 Blog] by Rishabh.

== Testing ==

Starts at color gender age home view as user "pi",
wireless works; showing ad-hoc and wireless Access points.

Home View (F3 key) screenshot:

[[File:Screenshot_of_"Home".png | 700px | 600px]]

Does not auto-mount an inserted USB.

== Reproducing ==

This was reproduced on Debian ''stretch'' platform which was set up in an ''schroot'' shell on Ubuntu.

=== Setup Schroot ===

Set up a ''schroot'' environment like this:
* Install the ''schroot'' and ''debootstrap'' packages,
sudo apt install schroot debootstrap
* Create the ''stretch'' filesystem,
sudo mkdir -p /srv/chroot/stretch
sudo debootstrap stretch /srv/chroot/stretch
* Make a file /etc/schroot/chroot.d/stretch,
[stretch]
type=directory
personality=linux
directory=/srv/chroot/stretch
* Log into your ''schroot'' shell from the terminal,
sudo schroot -c stretch

See https://wiki.debian.org/Schroot for alternate methods.

=== Setup Builder ===

Setup the builder within the ''schroot'' shell like this;
* Clone the repository
git clone <nowiki>https://github.com/sugarlabs/rpi23-gen-image</nowiki>
* Install dependencies by going through the README.md file and executing the commands described,

=== Run Builder ===

* Change your directory to the cloned repo and run this command to start the building process:
sh rpi23-gen-image.sh
This takes some time as the scripts start downloading and configuring packages to build an image.
* Once the process is complete in the terminal, navigate to this directory:
~/rpi23-gen-image/images/stretch
to find the image that was built.

Some changes have been made to the original repo: <nowiki>https://github.com/drtyhlpr/rpi23-gen-image</nowiki> which can be viewed in the commit history.

=== Adding the automatic login feature ===
[ Update(24/08/17): Automatic login feature has been made reproducible in the image builder's repo]
* While the image is building, navigate to the following directory:
~/rpi23-gen-image/images/stretch/build/chroot/etc
and depending on the stage of the build process wait for a folder named 'lightdm' to appear.
* Then open this file with nano/gedit and with root priviledges:
~/rpi23-gen-image/images/stretch/build/chroot/etc/lightdmlightdm.conf.dpkg-new
* Add/uncomment the following lines and configure them as shown below:
autologin-session = sugar
[Seat:*]
#type=xlocal
pam-service=lightdm
pam-autologin-service=lightdm-autologin
autologin-user=pi #(change this if you have configured a different user)
autologin-password=raspberry #(change this if you have configured a different password)
autologin-user-timeout=0
session-wrapper=/etc/X11/Xsession
greeter-session=lightdm-greeter
* Save the file and wait for the build process to complete.
* Boot into your image with this configuration and autologin should work fine.

Debian/Raspberry Pi

2017-07-07T09:40:11Z

Rishabh42: Removed the broken link and added my sunjammer account's link

== Download ==

Rishabh Thaney has made a build for Raspberry Pi using Debian;

*[https://drive.google.com/file/d/0B1YK6wpv2W0eUlMzWUgta1NuQW8/view 2017-06-26-rpi3-stretch.img.zip] on Google Drive,

:On around 4th July there was mention on IRC of two later builds which add automatic login, but no information yet as to what else they include, and there have been [https://github.com/Rishabh42/rpi23-gen-image no new commits]. Contact Rishabh if more information needed. --[[User:Quozl|Quozl]] ([[User talk:Quozl|talk]]) 20:05, 4 July 2017 (EDT)

See also: [[Summer_of_Code/2017|GSoC 2017 Project Ideas]] by Sugar Labs, [[Summer_of_Code/Rishabh_Thaney|GSoC 2017 Proposal]] by Rishabh, and [https://sugaronraspberrypi.wordpress.com/ GSoC 2017 Blog] by Rishabh.
* [Update: 07/07/2017] The latest images for RPi 2 & 3 with the automatic login fix can be found on this page: https://people.sugarlabs.org/rishabh/

== Testing ==

Report issues to https://github.com/sugarlabs/rpi23-gen-image

On images dated before 2017-07-04, select "sugar" in top right bar at login.

=== 2017-06-26 ===

Home View (F3 key).

[[File:RaspberryPiDebianStretchHomeView.png | 700px | 600px]]

== Comparison ==

Please also compare against the Fedora 26 SoaS image, as it has many more working activities.

Fedora SoaS does not include wireless firmware, see the [https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi?rd=Raspberry_Pi#Wifi: FAQ] for a fix.

=== 2017-07-03 ===

*[https://dl.fedoraproject.org/pub/alt/stage/26_RC-1.3/Spins/armhfp/images/Fedora-SoaS-armhfp-26-1.3-sda.raw.xz Fedora-SoaS-armhfp-26-1.3-sda.raw.xz] at Fedora Project.
*[https://dl.fedoraproject.org/pub/alt/stage/26_RC-1.5/Spins/armhfp/images/Fedora-SoaS-armhfp-26-1.5-sda.raw.xz Fedora-SoaS-armhfp-26-1.5-sda.raw.xz] final Release
Home View (F3 key).

[[File:Screenshot_of_Home_.png | 700px | 600px]]

Neighborhood View (F1 key).

[[File:Screenshot_of_Mesh_.png | 700px | 600px]]

My Settings, Network, Collaboration Server was set to jabber.sugarlabs.org before this screenshot. The default in Sugar 0.110 is not to use jabber.sugarlabs.org unless configured.

Rishabh used Etcher but his rpi3 [http://lists.sugarlabs.org/archive/sugar-devel/2017-July/054458.html did not boot]. James and Rishabh confirmed four partitions on the card of the correct size. James suggested checking for write corruption by reading back the exact number of blocks written and comparing md5sum.

===== Suggested Installation =====

Thomas suggested writing to microSD card using [https://github.com/MartinBriza/MediaWriter/releases Fedora Media Writer] (FMW), which is available for Mac OS X, Microsoft Windows, Fedora Linux, and Ubuntu Linux. Here are his test steps;

* download Fedora-SoaS-armhfp-26-1.3-sda.raw.xz
* select and extract
* start FMW
* select "Custom"
* select Fedora-SoaS-armhfp-26-1.3-sda.raw
* Choose rpi3 from drop-down in FMW
* Insert micro SD in Mini Card Reader and insert in USB port
* Choose rpi3 from drop-down in FMW
* Write micro SD
* Insert in rpi3 slot and power up

== Reproducing ==

This was reproduced on Debian ''stretch'' platform which was set up in an ''schroot'' shell on Ubuntu.

=== Setup Schroot ===

Set up a ''schroot'' environment like this:
* Install the ''schroot'' and ''debootstrap'' packages,
sudo apt install schroot debootstrap
* Create the ''stretch'' filesystem,
sudo mkdir -p /srv/chroot/stretch
sudo debootstrap stretch /srv/chroot/stretch
* Make a file /etc/schroot/chroot.d/stretch,
[stretch]
type=directory
personality=linux
directory=/srv/chroot/stretch
* Log into your ''schroot'' shell from the terminal,
sudo schroot -c stretch

See https://wiki.debian.org/Schroot for alternate methods.

=== Setup Builder ===

Setup the builder within the ''schroot'' shell like this;
* Clone the repository
git clone <nowiki>https://github.com/sugarlabs/rpi23-gen-image</nowiki>
* Install dependencies by going through the README.md file and executing the commands described,

=== Run Builder ===

* Change your directory to the cloned repo and run this command to start the building process:
sh rpi23-gen-image.sh
This takes some time as the scripts start downloading and configuring packages to build an image.
* Once the process is complete in the terminal, navigate to this directory:
~/rpi23-gen-image/images/stretch
to find the image that was built.

Some changes have been made to the original repo: <nowiki>https://github.com/drtyhlpr/rpi23-gen-image</nowiki> which can be viewed in the commit history.

=== '''Adding the automatic login feature''' ===
* While the image is building, navigate to the following directory:
~/rpi23-gen-image/images/stretch/build/chroot/etc
and depending on the stage of the build process wait for a folder named 'lightdm' to appear.

* Then open this file with nano/gedit and with root priviledges:
~/rpi23-gen-image/images/stretch/build/chroot/etc/lightdmlightdm.conf.dpkg-new
* Add/uncomment the following lines and configure them as shown below:
autologin-session = sugar

[Seat:*]

#type=xlocal

pam-service=lightdm

pam-autologin-service=lightdm-autologin

autologin-user=pi #(change this if you have configured a different user)

autologin-password=raspberry #(change this if you have configured a different password)

autologin-user-timeout=0

session-wrapper=/etc/X11/Xsession

greeter-session=lightdm-greeter
* Save the file and wait for the build process to complete.
* Boot into your image with this configuration and autologin should work fine.

Debian/Raspberry Pi

2017-07-07T09:31:11Z

Rishabh42: Steps to add the autologin feature

== Download ==

Rishabh Thaney has made a build for Raspberry Pi using Debian;

*[https://people.sugarlabs.org/rishabh/2017-06-26-rpi3-stretch.img.zip 2017-06-26-rpi3-stretch.img.zip] at Sugar Labs.
*[https://drive.google.com/file/d/0B1YK6wpv2W0eUlMzWUgta1NuQW8/view 2017-06-26-rpi3-stretch.img.zip] on Google Drive,

:On around 4th July there was mention on IRC of two later builds which add automatic login, but no information yet as to what else they include, and there have been [https://github.com/Rishabh42/rpi23-gen-image no new commits]. Contact Rishabh if more information needed. --[[User:Quozl|Quozl]] ([[User talk:Quozl|talk]]) 20:05, 4 July 2017 (EDT)

See also: [[Summer_of_Code/2017|GSoC 2017 Project Ideas]] by Sugar Labs, [[Summer_of_Code/Rishabh_Thaney|GSoC 2017 Proposal]] by Rishabh, and [https://sugaronraspberrypi.wordpress.com/ GSoC 2017 Blog] by Rishabh.

== Testing ==

Report issues to https://github.com/sugarlabs/rpi23-gen-image

On images dated before 2017-07-04, select "sugar" in top right bar at login.

=== 2017-06-26 ===

Home View (F3 key).

[[File:RaspberryPiDebianStretchHomeView.png | 700px | 600px]]

== Comparison ==

Please also compare against the Fedora 26 SoaS image, as it has many more working activities.

Fedora SoaS does not include wireless firmware, see the [https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi?rd=Raspberry_Pi#Wifi: FAQ] for a fix.

=== 2017-07-03 ===

*[https://dl.fedoraproject.org/pub/alt/stage/26_RC-1.3/Spins/armhfp/images/Fedora-SoaS-armhfp-26-1.3-sda.raw.xz Fedora-SoaS-armhfp-26-1.3-sda.raw.xz] at Fedora Project.
*[https://dl.fedoraproject.org/pub/alt/stage/26_RC-1.5/Spins/armhfp/images/Fedora-SoaS-armhfp-26-1.5-sda.raw.xz Fedora-SoaS-armhfp-26-1.5-sda.raw.xz] final Release
Home View (F3 key).

[[File:Screenshot_of_Home_.png | 700px | 600px]]

Neighborhood View (F1 key).

[[File:Screenshot_of_Mesh_.png | 700px | 600px]]

My Settings, Network, Collaboration Server was set to jabber.sugarlabs.org before this screenshot. The default in Sugar 0.110 is not to use jabber.sugarlabs.org unless configured.

Rishabh used Etcher but his rpi3 [http://lists.sugarlabs.org/archive/sugar-devel/2017-July/054458.html did not boot]. James and Rishabh confirmed four partitions on the card of the correct size. James suggested checking for write corruption by reading back the exact number of blocks written and comparing md5sum.

===== Suggested Installation =====

Thomas suggested writing to microSD card using [https://github.com/MartinBriza/MediaWriter/releases Fedora Media Writer] (FMW), which is available for Mac OS X, Microsoft Windows, Fedora Linux, and Ubuntu Linux. Here are his test steps;

* download Fedora-SoaS-armhfp-26-1.3-sda.raw.xz
* select and extract
* start FMW
* select "Custom"
* select Fedora-SoaS-armhfp-26-1.3-sda.raw
* Choose rpi3 from drop-down in FMW
* Insert micro SD in Mini Card Reader and insert in USB port
* Choose rpi3 from drop-down in FMW
* Write micro SD
* Insert in rpi3 slot and power up

== Reproducing ==

This was reproduced on Debian ''stretch'' platform which was set up in an ''schroot'' shell on Ubuntu.

=== Setup Schroot ===

Set up a ''schroot'' environment like this:
* Install the ''schroot'' and ''debootstrap'' packages,
sudo apt install schroot debootstrap
* Create the ''stretch'' filesystem,
sudo mkdir -p /srv/chroot/stretch
sudo debootstrap stretch /srv/chroot/stretch
* Make a file /etc/schroot/chroot.d/stretch,
[stretch]
type=directory
personality=linux
directory=/srv/chroot/stretch
* Log into your ''schroot'' shell from the terminal,
sudo schroot -c stretch

See https://wiki.debian.org/Schroot for alternate methods.

=== Setup Builder ===

Setup the builder within the ''schroot'' shell like this;
* Clone the repository
git clone <nowiki>https://github.com/sugarlabs/rpi23-gen-image</nowiki>
* Install dependencies by going through the README.md file and executing the commands described,

=== Run Builder ===

* Change your directory to the cloned repo and run this command to start the building process:
sh rpi23-gen-image.sh
This takes some time as the scripts start downloading and configuring packages to build an image.
* Once the process is complete in the terminal, navigate to this directory:
~/rpi23-gen-image/images/stretch
to find the image that was built.

Some changes have been made to the original repo: <nowiki>https://github.com/drtyhlpr/rpi23-gen-image</nowiki> which can be viewed in the commit history.

=== '''Adding the automatic login feature''' ===
* While the image is building, navigate to the following directory:
~/rpi23-gen-image/images/stretch/build/chroot/etc
and depending on the stage of the build process wait for a folder named 'lightdm' to appear.

* Then open this file with nano/gedit and with root priviledges:
~/rpi23-gen-image/images/stretch/build/chroot/etc/lightdmlightdm.conf.dpkg-new
* Add/uncomment the following lines and configure them as shown below:
autologin-session = sugar

[Seat:*]

#type=xlocal

pam-service=lightdm

pam-autologin-service=lightdm-autologin

autologin-user=pi #(change this if you have configured a different user)

autologin-password=raspberry #(change this if you have configured a different password)

autologin-user-timeout=0

session-wrapper=/etc/X11/Xsession

greeter-session=lightdm-greeter
* Save the file and wait for the build process to complete.
* Boot into your image with this configuration and autologin should work fine.

Debian/Raspberry Pi

2017-06-25T07:01:07Z

Rishabh42: replaced "schroot -c stretch" with "sudo schroot -c test"

== 2017-06-22 ==

Sucrose images for the Raspberry Pi 3 can be created by using this fork repository:
* https://github.com/Rishabh42/rpi23-gen-image

This was tested on Debian ''stretch'' platform which was set up in an ''schroot'' shell on Ubuntu.

The method is:
* Set up an ''schroot'' environment by following the instructions: https://wiki.debian.org/Schroot,
* Log into your ''schroot'' shell from the terminal,
sudo schroot -c test
* Clone the repository
git clone <nowiki>https://github.com/Rishabh42/rpi23-gen-image</nowiki>
* Install dependencies by going through the readme file in the repo and executing the commands described,
* Change your directory to the cloned repo and run this command to start the building process:
sh rpi23-gen-image.sh
This takes some time as the scripts start downloading and configuring packages to build an image.
* Once the process is complete in the terminal, navigate to this directory:
~/rpi23-gen-image/images/stretch
to find the image that was built.

Some changes have been made to the original repo: <nowiki>https://github.com/drtyhlpr/rpi23-gen-image</nowiki> which can be viewed in the commit history of the fork mentioned above.

== 2017-06-21 ==

== Sugar on RPI image ==

This image can be considered still in beta. This is not the final build.

Here is the link : [https://drive.google.com/file/d/0B1YK6wpv2W0eQUJrRldiVU1fczQ/view Download]

Repository : [https://github.com/drtyhlpr/rpi23-gen-image here]

Fork used: [https://github.com/hrishi1999/rpi23-gen-image here]

If the image does not work on the first boot (or fails to login), please restart your RPI and try again.
--[[User:HrishiP|HrishiP]] ([[User talk:HrishiP|talk]]) 10:49, 21 June 2017 (IST)

Debian/Raspberry Pi

2017-06-22T16:09:48Z

Rishabh42: Added instructions to create an image for the RPi 3 with Sucrose

Sucrose images for the Raspberry pi 3 can be created by using this repository: <nowiki>https://github.com/Rishabh42/rpi23-gen-image</nowiki>

This fork was tested on Debian stretch platform which was set up in an schroot shell.

The method is described as follows:
1. Set up an schroot environment by following the instructions on this page: <nowiki>https://wiki.debian.org/Schroot</nowiki> and replacing "wheezy" with "stretch" in the instructions to install Debian stretch which is crucial to build images using this repo.
2. Log into your schroot shell from the terminal.
3. Clone the <nowiki>https://github.com/Rishabh42/rpi23-gen-image</nowiki> repository.
4. Build dependencies by going through the readme file in the repo and executing the commands described.
5. Change your directory to the cloned repo and run this command to start the building process: "sh rpi23-gen-image.sh", without quotes. This step takes some time as the scripts start downloading and configuring packages to build an image.
6. Once the proces is complete in the terminal, navigate to this directory: ~/rpi23-gen-image/images/stretch to find the image that was built.

Some changes have been made to the original repo found here: <nowiki>https://github.com/drtyhlpr/rpi23-gen-image</nowiki> which can be viewed in the commit history of the fork mentioned above.