Rishabhnambia
Joined 10 March 2018
| (3 intermediate revisions by the same user not shown) | |||
| Line 126: | Line 126: | ||
|05 | |05 | ||
|June 12 - June 20 | |June 12 - June 20 | ||
| | |Phase I Evaluation | ||
| | | | ||
*Formulate a robust upgrade process to ensure that Sugarizer updates are installed successfully without losing any data to instances that have been deployed. | *Formulate a robust upgrade process to ensure that Sugarizer updates are installed successfully without losing any data to instances that have been deployed. | ||
| Line 149: | Line 149: | ||
|08 | |08 | ||
|July 09 - July 13 | |July 09 - July 13 | ||
| | |Phase II Evaluation | ||
| | | | ||
*If the Turtle/Music Blocks release is on schedule, I will add it to the Sugarizer Pi Image build. | *If the Turtle/Music Blocks release is on schedule, I will add it to the Sugarizer Pi Image build. | ||
| Line 178: | Line 178: | ||
|12 | |12 | ||
|6 Aug - August 14 | |6 Aug - August 14 | ||
| | |Final Evaluation | ||
| | | | ||
*Keep a final buffer week for added tasks. | *Keep a final buffer week for added tasks. | ||
| Line 188: | Line 188: | ||
| | | | ||
|- | |- | ||
|} | |} | ||
| Line 227: | Line 223: | ||
::4) I think you can start thinking on your proposal. You can continue to discuss with us to talk about the project but also the community and the impact of that project. | ::4) I think you can start thinking on your proposal. You can continue to discuss with us to talk about the project but also the community and the impact of that project. | ||
::5) For the deployment part we have two options that would be nice to have. | ::5) For the deployment part we have two options that would be nice to have. | ||
::* a really simple automation like heroku single click deploy (https://blog.heroku.com/heroku-button). This is the killer feature we should definitely have. | ::* a really simple automation like heroku single click deploy (https://blog.heroku.com/heroku-button). | ||
:::'''This is the killer feature we should definitely have.''' | |||
::* the devops way using tools like Ansible and Terraform and Packer. | ::* the devops way using tools like Ansible and Terraform and Packer. | ||
::'''One major thing for all platforms is to think about the upgrade processes, how can we update the devices/server without losing data.''' | ::'''One major thing for all platforms is to think about the upgrade processes, how can we update the devices/server without losing data.''' | ||
| Line 255: | Line 252: | ||
:I've deployed Sugarizer on my Raspberry Pi 3 and a VPS with Docker and without it. | :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. | :It works really well and I haven’t run into any major issues. | ||
====Tell us something about yourself that will make us like you more.==== | |||
:*I believe I’m a good candidate for this project because I’m an avid distro-hopper. The process of merely installing new Linux distributions and setting them up the way I like takes a large chunk of my time. So, the Sugarizer School Box isn’t just some project I’d like to do for GSoC, it’s something I’ll actually enjoy building! | |||
:*I come from a family of musicians so I’ve turned into an amateur singer and guitar player as I’ve grown up. I also know my way around recording instruments and vocals. If the Sugarizer School Box project didn’t exist, I would have picked a Music Blocks project for sure. Maybe I can work on it sometime in the future! | |||
====Describe a great learning experience you had as a child.==== | ====Describe a great learning experience you had as a child.==== | ||
| Line 264: | Line 265: | ||
:Now, I just use that concept to try learning whatever I need to. It’s all about getting your hands dirty and putting in the work. | :Now, I just use that concept to try learning whatever I need to. It’s all about getting your hands dirty and putting in the work. | ||
[[Category:2018 GSoC applications]] | [[Category:2018 GSoC applications]] | ||