13
edits
Changes
Jump to navigation
Jump to search
Line 75:
Line 75: − * What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (end of June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.+ + Line 206:
Line 207: − + − ===Successful completion===+ − + + + + + + + + + − ===Getting stuck=== Line 218:
Line 226: − ===Keeping informed===+ + + +
Summer of Code/2016/Sugarizer Activity Set (view source)
Revision as of 14:10, 25 March 2016
, 14:10, 25 March 2016no edit summary
* [https://github.com/kangax/fabric.js/ fabric.js] - Fototoon activity
* [https://github.com/kangax/fabric.js/ fabric.js] - Fototoon activity
'''What is the timeline for development of your project? The Summer of Code work period is from mid-May to mid-August; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (end of June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''
{| class="wikitable"
{| class="wikitable"
|-
|-
[https://github.com/DVM-S/astrocytes Code.Fun.Do project] - Qualified for the Microsoft Code.Fun.Do Finalist Forums (Nationals)
[https://github.com/DVM-S/astrocytes Code.Fun.Do project] - Qualified for the Microsoft Code.Fun.Do Finalist Forums (Nationals)
==The community==
===You and the community===
When an OS level application is ported onto web, it becomes much easier to access it. All that is needed is a browser and internet. Moon, Sugar and Fototoon are activities that nurture curiosity and creativity. By making these webapps, I can introduce larger number of children to these technologies.
'''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.'''
'''My thought''': When an OS level application is ported onto web, it becomes much easier to access it. All that is needed is a browser and internet. Moon, Sugar and Fototoon are activities that nurture curiosity and creativity. By making these webapps, I can introduce larger number of children to these technologies.
'''Lionel Laské''': Activities in the Sugarizer Activity Set are 3 of most famous Sugar activities. It's very important to have a full experience of Sugar on any device that these activities must be available into Sugar-Web. Plus these activities was proven during deployment to be very attractive for children using Sugar and at least Speak and Fototoon allow them to express their creativity.
'''Walter Bender''': Sugarizer OS is an attempt to spread the core ideas of Sugar to learners who do not have access to the Sugar Desktop. While we have made a lt of progress on the basic functionality, we still have just begun to scratch the surface regarding offering a rich collection of Apps. This project should go a long ways towards realizing a more complete offering.
'''What will you do if you get stuck on your project and your mentor isn't around?'''
If I do get stuck, there are a few things that I can do:
If I do get stuck, there are a few things that I can do:
* Drop a mail to the mentors.
* Drop a mail to the mentors.
* On the off chance that all my attempts fail, I will move on to a different part of the project - one that is not affected by the problem.
* On the off chance that all my attempts fail, I will move on to a different part of the project - one that is not affected by the problem.
'''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?'''
* A follow up page on the wiki, containing progress in great detail.
* A follow up page on the wiki, containing progress in great detail.
* Online demos of the current status
* Online demos of the current status
* Maintain a ToDo file in the github repository
* Maintain a ToDo file in the github repository
* Post (frequently) in the mailing list, asking for feedback.
* Post (frequently) in the mailing list, asking for feedback.
[[Category:2016 GSoC applications]]