39
edits
Changes
Jump to navigation
Jump to search
mLine 32:
Line 32: + + + − + Line 44:
Line 47: − + + + Line 192:
Line 197: − + Line 240:
Line 245: + + + + + + + + + + + + + + + + + + + + + + + + + + + + − === Miscellaneous ===
Added images and small edits
==== Goal #1: Sugarizer Raspberry Pi Images and Improving the Internet-In-A-Box Ansible Installer for Sugarizer ====
==== Goal #1: Sugarizer Raspberry Pi Images and Improving the Internet-In-A-Box Ansible Installer for Sugarizer ====
:
[[File:Sugarizerschoolbox diagram.png|center|flow]]
:
:The first goal is to create a Raspberry Pi image and build scripts based on Raspbian that can serve Sugarizer to a classroom full of students. This is being :created because the Raspberry Pi is inexpensive, widely available and many such Sugarizer School Boxes can provide a cost-effective way of reaching out to :more students and communities through Sugar.
:The first goal is to create a Raspberry Pi image and build scripts based on Raspbian that can serve Sugarizer to a classroom full of students. This is being created because the Raspberry Pi is inexpensive, widely available and many such Sugarizer School Boxes can provide a cost-effective way of reaching out to more students and communities through Sugar.
:On booting, the Raspberry Pi will:
:On booting, the Raspberry Pi will:
:The second goal is to simplify the way to deploy Sugarizer in the cloud. The priority in this section is get a Heroku Button for sugarizer up and running. (https://blog.heroku.com/heroku-button).
:The second goal is to simplify the way to deploy Sugarizer in the cloud. The priority in this section is get a Heroku Button for sugarizer up and running. (https://blog.heroku.com/heroku-button).
:
[[File:Herokubuttonreadmeexample.png|center]]
:
:A Heroku Button is a simple HTML or Markdown snippet that can be added to READMEs. Clicking a Heroku Button will take you through a guided process to configure and deploy an app running the source code referenced by the button.
:A Heroku Button is a simple HTML or Markdown snippet that can be added to READMEs. Clicking a Heroku Button will take you through a guided process to configure and deploy an app running the source code referenced by the button.
|}
|}
=== Why I can finish this Project ===
=== Convince us why you can finish this project ===
:I mentioned my experience with an open-source organization called ERPNext (https://github.com/frappe) above.
:I mentioned my experience with an open-source organization called ERPNext (https://github.com/frappe) above.
::I would also recommend focusing on the rpi install before turning to Heroku or AWS as most users are without an internet connection. All I'm suggesting is that you start with Sugarizer School Box item 1 and then proceed to item 2 when it is complete.
::I would also recommend focusing on the rpi install before turning to Heroku or AWS as most users are without an internet connection. All I'm suggesting is that you start with Sugarizer School Box item 1 and then proceed to item 2 when it is complete.
'''What will you do if you get stuck on your project and your mentor isn't around?
'''If I get stuck on my project, I will first try my best to find a solution myself (Web Search, StackOverflow). I have some friends and ex-colleagues who are Open Source enthusiasts so I can ask them for guidance if I need help.
'''
How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''
In the Community Bonding period, I will create a blog for myself and I will share my weekly experiences and progress through it.
=== Miscellaneous ===
=====Setting Up a Development Environment=====
:I wasn’t sure if this project falls under the Sugar-Web projects or the Sugar projects.
:I've deployed Sugarizer on my Raspberry Pi 3 and a VPS with Docker and without it.
:It works really well and I haven’t run into any major issues.
:
[[File:Locustsugarizer.png|center|locust]]
:
=====Workload analysis for sugarizer-server=====
:I've been testing the page load times for some activities using Locust, a user load testing tool written in Python that lets you test site performance by swarming it with users.
:This will fulfill one of the tasks in the node.js performance analysis of sugarizer-server which lets us know the size of the file download per page/activity and response times as the number of users increases.This analysis will be important when I run them on the Raspberry Pi WiFi AP along with the other tasks in parallel. I will try to replace this section with a more complete analysis before the final proposal.
'''Describe a great learning experience you had as a child.'''
working-on-it
'''More questions I'd like to ask'''
I wanted to know if I should add more details about the implementation of the tasks in the proposal and I would also love to recieve any kind of feedback from the community.