Summer of Code/2016/Redesign and recreate Sugar Labs webappearance
About Me
| Name: | Kanika Murarka |
| Program: | Bachelor of Technology |
| Major: | Computer Science and Engineering (Pre-Final Year) |
| College/University: | GGSIPU, New Delhi, India |
| Email: | Contact[at]KanikaMurarka[dot]xyz |
| Phone: | +91-9868-179-156, +91-8800-184-063 |
| First language: | Hindi, Also proficient in English |
| IRC: | Kanikaa in freenode #sugar |
| SugarLabs Wiki Username: | Beastie |
| Timezone: | I can work from 16:00 to 21:00 IST (UTC +5:30) but it's adjustable |
| Current Location: | Delhi, India, |
| Open Source Projects: | I have contributed in Mozilla Delhi Community |
| Twitter: | Kanika on Twitter |
| Github: | Kanika on GitHub |
| Blog: | Kanika’s Blog |
About My project
Name of Project
Redesign and Recreate Sugar Labs Web Appearance
Abstract
This project is to revamp the existing templates in diversified sites of Sugar Labs and unify a theme across each one of them. The obsolete pages would be re-designed and a minimal number of technologies would be applied to develop the web appearance.
Overview
The existing sites are very diversified in nature. The goal is to make a unified theme and apply it across all the sites (main page, planet, wiki etc.). This would ensure consistency and ease of use across all Sugar Labs sites. The obsolete pages would be dropped/re-designed according to the needs and minimal design would be applied.
Using less no. of technologies would make code maintenance easier and would also facilitate in dropping off unnecessary tools. This would mean unification in technology across all sites.
Goals
- Designing modern and innovative template for all Sugar Labs Site:
- Unify the technologies used across all sites:
Approach
An incremental enhancement approach would be followed.
- Discuss with mentor(s) about specifications
- Implementing stuff
- Getting feedback and re-iterating
This would help in revealing any bugs/mis-conception early in development phase itself and also give more time on enhancing the application as desired.
Specifications
Milestones
| Week | Task |
|---|---|
22 April - 23 May |
|
23 May - 3 June (Tentative) |
|
4 June - 11 June |
|
12 June - 19 June |
|
20 June - 27 June |
|
28 June - 5 July |
|
6 July - 13 July |
|
20 July - 26 July |
|
27 July - 3 August |
|
4 August - 10 August |
|
10 August - 15 August |
|
15 August - 23 August |
|
Why should I be chosen for the project?
- I have a strong experience in HTML, CSS and JavaScript and a lot of interest in designing.
- I am an active IEEE member and Webteam head at IEEE-NIEC(sub-chapter of IEEE of my college).We(team) are recently working on the chapters website GitHub:IEEENIEC.
- I have interned at some organizations and well aware with working with deadlines and delivering the allotted tasks without compromising with the quality. My resume can be found on here.
- I am an open source enthusiast and contributed to the Mozilla Delhi Community GitHub:Mozpacers.
- I have recently worked for an NGO- SevaSetu, and worked for their website design LinkThe site is still under development.GitHub:SevaSetu
- Graphic Designer and Marketing head at NGO Tathastu
The community and me
If the task completes successfully..
I will be happy to have contributed in one more open source community and I will look forward to contribute more in the organization, even in projects out of my comfort zone.
If I get stuck and mentor is not around..
Since mentors are there only to guide us and help us with best of their knowledge, its me who have to complete the project. I will look up on internet to find the solution of the problem I am stuck with, if I dont get the solution, I will keep the task aside and carry on with another module, so that time do not get wasted. And when mentor is available, I can discuss my doubts is a better way.
Ways to keep the community informed of my progress
I will be posting it on IRC and also on mailing list.Also, I also planning to maintain a weakly task record on GitHub.