41
edits
Changes
Summer of Code/2016/Sugarizer Server Dashboard (view source)
Revision as of 09:49, 25 March 2016
, 09:49, 25 March 2016no edit summary
the Application running via the Sugarizer Server, the users who have been registered on the server, journals and will also provide editing options
the Application running via the Sugarizer Server, the users who have been registered on the server, journals and will also provide editing options
to the user to modify the various aspects.
to the user to modify the various aspects.
=='''About Me'''==
===Personal Information===
<table class="wikitable">
<tr>
<td>'''Name''':</td> <td>Saurabh Badhwar</td>
</tr>
<tr>
<td>'''Current Program''':</td> <td>Bachelor in Technology, Computer Science Engineering</td>
</tr>
<tr>
<td>'''Year of study''':</td> <td>Pre-final year</td>
</tr>
<tr>
<td>'''College/University''':</td> <td>Guru Gobind Singh Indraprastha University, Delhi, India</td>
</tr>
<tr>
<td>'''E-Mail Address''':</td> <td>contact@saurabhbadhwar.xyz</td>
</tr>
<tr>
<td>'''Contact Number''':</td> <td>+91-9650-823-204</td>
</tr>
<tr>
<td>'''SugarLabs Wiki Username''':</td> <td>h4xr</td>
</tr>
<tr>
<td>'''IRC Nickname''':</td> <td>Saurabh_Badhwar</td>
</tr>
<tr>
<td>'''First language''':</td> <td>Hindi, Also proficient in English</td>
</tr>
<tr>
<td>'''Current Location''':</td> <td>Delhi, India</td>
</tr>
<tr>
<td>'''Work hours''':</td> <td>I would like to work between 13:00 to 18:00 (UTC +5:30) [Adjustable]</td>
</tr>
<tr>
<td>'''Website''':</td> <td>[http://saurabhbadhwar.xyz Saurabh Badhwar's Website]</td>
</tr>
<tr>
<td>'''Twitter''':</td> <td>[http://twitter.com/mynet55 Saurabh Badhwar on Twitter]</td>
</tr>
<tr>
<td>'''GitHub Profile''':</td> <td>[https://github.com/h4xr Saurabh Badhwar on GitHub]</td>
</tr>
</table>
===Technical Skills===
I have worked on various technologies during the course of time in various projects. My skillset includes:
*'''Frontend''': HTML5,CSS3,Javascript,Bootstrap and jQuery
*'''Backend''': PHP,Python,Node.js and frameworks like Flask,Express.js
*'''Database''': MySQL,Mongodb,Neo4j
===Previous Work Experience===
* Active contributor to Mozilla Delhi Community Website (Mozpacers) - [https://github.com/h4xr/Mozpacers.github.io Mozilla Delhi]
* Webmaster at [http://www.ieeeniec.com IEEE NIEC]
* Developed an Indian Railway reservation status checking application based on node.js and mongodb [https://github.com/h4xr/pnr PNR Check]
* Developed a custom CMS for a NGO website [https://github.com/h4xr/Sevasetu Sevasetu]
* Worked on backend development of [http://www.ieeeniec.com IEEE NIEC]
* Developed Image sharing website Camjam
=='''Overview'''==
=='''Overview'''==
Sugar Labs aims at creating tools that learners use to explore, discover, create, and reflect with the mission to support the Sugar community of users and developers and establish regional, autonomous "Sugar Labs" around the world to help learners "learn how to learn" by tailoring Sugar to local languages and curricula.
Sugar Labs aims at creating tools that learners use to explore, discover, create, and reflect with the mission to support the Sugar community of users and developers and establish regional, autonomous "Sugar Labs" around the world to help learners "learn how to learn" by tailoring Sugar to local languages and curricula.
The use of frameworks like bootstrap will help to build a responsive frontend which will help improve the user experience. The backend being powered by node.js and mongodb will help in better utilization of resources since most of the work will be IO based and the non-blocking IO of node.js will help improve the performance. This will also help in reducing the number of language dependencies the Sugarizer project is based on.
The use of frameworks like bootstrap will help to build a responsive frontend which will help improve the user experience. The backend being powered by node.js and mongodb will help in better utilization of resources since most of the work will be IO based and the non-blocking IO of node.js will help improve the performance. This will also help in reducing the number of language dependencies the Sugarizer project is based on.
==='''Mock Designs'''===
[[File:Login_page.png|thumb|left|Login page for dashboard]]
[[File:Dashboard_page.png|thumb|center|Dashboard for the server]]
These designs are the initial mockups and will be refined as per the requirements in the future.
=='''Milestones'''==
=='''Milestones'''==
<table class="wikitable">
<tr>
<th>Timeline</th>
<th>Task</th>
</tr>
<tr>
<td>
===22 April-23 May===
===22 April-23 May===
</td>
<td>
*Bonding with the community
*Bonding with the community
*Gathering the requirements for the project
*Gathering the requirements for the project
*Feedback from the mentor
*Feedback from the mentor
</td>
</tr>
<tr>
<td>
===23 May - 10 June===
===23 May - 10 June===
</td>
<td>
*Semester exams
*Semester exams
During the exam period the time being devoted to the development will be reduced. To compensate for the same, more tasks will be achieved during the pre and post examination period.
During the exam period the time being devoted to the development will be reduced. To compensate for the same, more tasks will be achieved during the pre and post examination period.
</td>
</tr>
<tr>
<td>
===11 June - 17 June===
===11 June - 17 June===
</td>
<td>
*First prototype
*First prototype
*Feedback and improvisation
*Feedback and improvisation
</td>
</tr>
<tr>
<td>
===18 June - 24 June===
===18 June - 24 June===
</td>
<td>
*Second prototype
*Second prototype
*Feedback and improvisation
*Feedback and improvisation
*Submission for mid term evaluation
*Submission for mid term evaluation
</td>
</tr>
<tr>
<td>
===25 June - 1 July===
===25 June - 1 July===
</td>
<td>
*Feedback and improvisation
*Feedback and improvisation
</td>
</tr>
<tr>
<td>
===2 July - 14 July===
===2 July - 14 July===
</td>
<td>
*Documentation for the dashboard
*Documentation for the dashboard
*Writing test cases
*Writing test cases
</td>
</tr>
<tr>
<td>
===15 July - 31 July===
===15 July - 31 July===
</td>
<td>
*First Beta
*First Beta
*Feedback and bug fixing
*Feedback and bug fixing
</td>
</tr>
<tr>
<td>
===1 August - 7 August===
===1 August - 7 August===
</td>
<td>
*Second Beta
*Second Beta
*Feedback and bug fixes
*Feedback and bug fixes
</td>
</tr>
<tr>
<td>
===8 August - 15 August===
===8 August - 15 August===
</td>
<td>
*Release candidate
*Release candidate
*Preparation for final submission
*Preparation for final submission
</td>
</tr>
<tr>
<td>
===16 August - 23 August===
===16 August - 23 August===
</td>
<td>
*Final Submission
*Final Submission
*Deliverable: A dashboard for Sugarizer server
*Deliverable: A dashboard for Sugarizer server
</td>
</tr>
</table>
== '''Miscellaneous''' ==
=='''About Me'''==
=== Sugarizer Server Install ===
[[File:Sugarizer Activity.png|left|thumb]]
[[File:Sugarizer Activity2.png|thumb]]
[[File:Sugarizer Home.png|centre|thumb]]
'''SugarLabs Wiki Username''': h4xr
=== A learning experience ===
As a child I was always fascinated by how the operating systems worked and how the applications runs over them. Fascinated by these as a child I always wanted to build my own Operating System. This was the time I began my journey into the world of Computer Science by starting with learning how to program in C. As my understanding grew about the field, it was a realization that building an OS wasn't as easy as it seemed but it proved to be a great entry point into the field of computer science for me. The dream of building an OS lead me to learn about different algorithms and data structures. There were many problems faced during this journey as a child but it proved to be a great morale booster for me.
[[Category:2016 GSoC applications]]
=== Bonding with the community ===
I believe in Team work and would love to be in close touch with the community during the development period and after that. During the development period I will try to be as fast as possible to answer any questions that are asked to me. I will be available on the IRC channel of the community as well as on the mailing lists.
In case of any doubt I will try to reach the mentor of the task and if due to some reason the mentor is unavailable to reply, I will try to find the answer of my queries by searching through the organisation wiki or asking other contributors. Incase the doubt still persists, instead of stopping the work and waiting for the mentor to reply, I will work on some other module so as to efficiently use the time and to deliver the work according to the mentioned deadlines.
In my personal opinion, being available for the community is the best way to contribute to it and keeping this in mind I will try to devote as much time as I can to the community to move its mission forward and will try to contribute in the best possible way.