Showing posts from December, 2016

Google Code-in 2016 Day 8

… Continuing from last post.
Task 9 “Website: Identify and Fix Issues our PSLab site on Github Pages”. But the problem was PSLab Site was way too simple and was using Clean Blog template so it was hard to find issues in it. So, I went ahead to check Site and what I found was that the site was broken or its not rendering properly. So, I reported the Issue#10 and someone fixed it by using CDN links insteas. Open Source :P. But, then I found out that developers.html, the second file was not fixed. So, I went ahead and fixed it and then I reported the Issue#14 and immediately created PR#15. Also in the meanwhile I found out that site was not having a Favicon(image placed on Tab, which generally is Logo or part of Logo). So, I created one more Issue#13 and this time I mentioned that I’m working on it. Then I created a Logo for PSLab, also I though about using FOSSASIA “F” logo as used in other sites of FOSSASIA to use as Favicon. Also, I googled and found out Font Awesome’s Flask Icon. I …

Google Code-in 2016 Day 7

… Continuing from last post.
Where’s Day 4, 5, 6? Well, I was working on FOSSASIA GCI 16 Site New look so didn’t got time to write’em.
Task 8 I was and still am enjoying working on GCI Site, and so I picked this task named “Website: Add a feature or fix an issue for the GCI website from the github issue tracker”. I found this Issue#400 and I planned to work on it. When I went through index.html and main.css, it was inconsistent at places and few sections were differently configured than rest. So, I mainly focused on Blog Section and fixed both the files. What I didn’t realised is that someone was working on blog section as well and has already committed his code. At the time of merging it created a merge conflict. Maintainers merge it by resolving the conflicts and it created a mess. So, I asked them that my version is fine and so we can use that to fix things and so I created PR#445 .

I was kinda off due to this ( I don’t know why) and so I decided to give the whole site a new look.…

Google Code-in 2016 Day 3

… Continuing from last post.
Task 6 So, after Task 5 I was like Why not try a task which is completely new to me and hence, Task 6 “ loklak search: Deploy the website of loklak search on your own GitHub account”. A completely new and exciting thing to me. But very less information was there in both task and loklak search So, that means I have to do all the research. But I call it a day. I woke up and all I was thinking was about loklak search. I asked in Slack and after some googling I got to a result, I was about deploying angularjs apps on Github which involve use of Bower components. I did everything and I got an empty site. Guess what?? It was wrong so I asked again in Slack and this time a loklak search project contributor was present he pointed me out to Angular-cli README. I read it and did all the things and I was still getting an empty site. I asked again and he helped me overcome a small issue and BOOM!!, I deployed my version of search engine. Unbelievable, isn’…

Google Code-in 2016 Day 2

… I’ll continue from where I left in last post. Late night my Parental Consent was approved and that marked the ending of Task#1.
Task 2 The first task was deploy FOSSASIA’s webapp, but wait, I’m not even part of the community right? So, I claimed task “Join the FOSSASIA channels and become a community member”. Yeah, that’s right it was a task and not a beginner one. So, in order to finish this one I generated an auto-invite and added myself in FOSSASIA Slack Team, subscribed myself to FOSSASIA Newsletter and Mailing List. Then I filled a form powered by Google Forms to get into Github GCI Team of FOSSASIA. Then I forked interesting repositories that I’d like to contribute to and starred others that I find interesting. I shared about this on Twitter, Facebook and Google+ and Done! Submitted for review. When I woke up it was approved.
Task 3 Till this time I’m actively participating in Slack channel and met lots of new people including Mentors and Fellow students. I looked for new tas…

Google Code-in 2016 Day 1

Google Code-in Google Code-in is a contest sponsored by Google to encourage pre-university students to know about open-source Projects and helps them contribute actively in such Projects.

This year, the contest started on 28 November 2016, and will go on till 16 January 2017. Preparation of this world-wide contest started much sooner. Around 10 October it was announced, and from 24 October, preparation started.
Task 1 Well, my bad I forgot to register and it was only today, that I registered. This is my first time in GCI. But, I have checked previous year archives. Today, when the registration process ended, I rushed towards task list and there FOSSASIA and KDE were the only two organisations that I recognise. So, I claimed the task from FOSSASIA, it was about deploying Event Webapp on Heroku. I’ve already used Heroku once and so I’ve already registered on Heroku. So, went ahead and forked the FOSSASIA Event Webapp repository on Github and I cloned it on my laptop. The deployment was…