1

The Google Summer of Code

When one interprets the term ‘open source’, they are likely to associate it with the word ‘free’. However, when a web-developer does the same, it elicits an entirely different connotation.

 An immense benefit that open source technology boasts about is the sheer number of contributors that it attracts. Anybody can contribute as well as modify the original source code. Thus, the end product is polished and agile, something that many propriety software fail to be. The advantages of open source technology are well-documented and popular. Therefore, it’s no surprise that some of the biggest tech companies on the planet do their part in promoting open source technology. An apt example would be Google’s GSoC or Google Summer of Code. Every year, student-developers from around the globe work on free-and-open-source coding projects during the summer. In return they obtain a significant stipend and the invaluable experience of working with some of the finest minds of the tech community. In an essence, the platform is a coder’s paradise where the summer break gets long and taxing.

In order to attain better clarity on the Google Summer of Code program and the reason behind its prestige among aspiring developers, we caught up with Mehul Gupta, a second year student from the ECE department, who was accepted into the GSoC program on his very first attempt.

Just like any of us, Mehul, who is not overly fond of attending classes, loves to sleep and code. The latter of which he’s been doing for the past six years.

Q1) How did you come across GSoC?
A senior friend of mine introduced me to the idea of GSoC while I was still in school. The idea, though, only sunk in when I got into college. My senior, Siddharth Bhat, who had also been involved with GSoC before, urged me to apply for it.

Q2) How do you go about the entire process?
It’s best to start preparing as early as possible. One must first go through the list of organizations and choose the one they want to work with. In fact, you must look at it from a strategic standpoint. Every organization is not selected every year. So, if an organization has been selected for a few consecutive years, chances are that they might not get chosen the next year. If that is the case, you’d be stuck with an organization you know little about, making your project tougher due to the incomprehensibility of their codebase, and the time frame of the project could be as tight as twenty-three days. It is a task in itself to first make a provisional list of organizations you want to work with and then narrow it down to just one and further on choose one project.

Q3) How did you select your projects?
 I took the first fifteen days to select the company with whom I wanted to work, found out more about them and thought about what I wanted to do. In fact, there was a lot of thought process involved here-we had to write down our proposals and our approach, contact our mentors to clarify any doubts. It was after this that work really got serious. Since companies review your work and judge you accordingly, there’s no room for slack.

Q5) We’re assuming there was a selection process involved. Could you tell us more about that?
Absolutely. The set of tasks assigned to me were varying in nature. One of them was to finish what was called the GSoC ladder which was in fact the preliminary task. The ladder consisted of setting up the environment, solving issues, and writing test cases. It was very challenging. The tasks became more demanding and at a point I stopped going to college for a few days. I had to stay up many nights in order to get the work done.

Q6) Now that you got through, how was the entire experience?

Well, GSoC is an extremely time intensive program. I remember last summer when I used to bunk full days and sit in my room to work on this from seven in the morning till five in the evening. You do need a certain level of dedication towards this. Apart from that, one of the most annoying things about the program was the need for complete documentation of your work. This depends majorly on your organization but most of them require you to document your entire work every week or once in two weeks.

Q7) What is your area of expertise?
PHP. I’ve been using PHP for the past six years now. That’s one factor that has helped me with these projects. Despite being very challenging, they weren’t half as hard as they would be for a beginner.

Q8) What are the incentives you gain out of GSoC?
We do receive an online certificate from our organization as well as Google. The stipend is one of the best parts about the program. We initially receive 500$ for getting accepted into the organization. Subsequently we have a mid-term evaluation where we receive 2250$ and a final evaluation where we receive 2750$. So, totally about 5500$.

Q9) Apart from the obvious technical requirement, are there any other tips and tricks a candidate might need to get accepted into GSoC?
Well, it is extremely important to keep contributing to your organization even after submitting your proposal. They obviously want to check how interested you are and there’s nothing better than constantly contributing to their organization. Keep in touch with your mentor throughout the summer and more importantly never give up or lose hope throughout the process. Also, a GitHub profile is a must.

Q10) Any advice to budding aspirants?
GSoC is not very hard. It just requires a lot of dedication and patience and if you’re serious about applying for the next GSoC, I suggest you start right now.

-Akhil Vaidyanathan and Meghana Dharmapuri




Prometheus’ 16: Did the bugs eat your code?

919663604904-1457292683

One of most challenging events of IE-CSE’s tech-weekend, Prometheus-V was Pandora’s Bugs. It was an event purely revolving around coding and as the name suggests, debugging faulty codes. A two round event, it was conducted over a span of two days. The turn-out for this was overwhelming – almost 35 teams of two showed up for the first round, of which only nine with the best scores were allowed to move to the second round.

The first round was comparatively easy, requiring absolutely no prerequisite of debugging. It consisted a total of ten questions with two sub-parts each. The first part was a simple set of programming questions the correct answers to which would unlock the second complimentary part of that question. Hence, one could not just do the second part of the question unless they’d cracked the first. Basically, whether or not a team qualified for the next round got decided by the number of questions attempted, as against the points system the creators had put in place. The only downside being that most of the participants were barely able to attempt even 3 sub-parts out of the twenty.

The final round was held on the last day of the three days of Prometheus. This round too, followed a similar pattern. There were two sets of questions – the first one on debugging which carried a massive thirty points while the other part was plain coding which was further divided into easy and moderate questions. On solving every coding problem, the participants could ask for hints. Taking these hints wasn’t essential as most participants debugged at least one such code without asking for any hints. One thing observed in all these questions was that each of them had the names of at least one of the organizers or event heads of Pandora’s Bugs. This just went to show how thoroughly involved they were with the event and how much they enjoyed it.

IMG_20160403_134823

A very well planned event, Pandora’s Bugs proceeded almost on time. It was technically challenging which made sure that only the one with true mettle and caliber to live up to the tagline of Prometheus V – “Be a God”- would excel.




Prometheus ’16: Artem

The latest additon to the list of competitions under IE CSE’s flagship event ‘Prometheus’, Artem received participation from plenty of aspiring designers. Designers of all grades were seen testing their designing skills. The two-round competition was held on the second and third day of Prometheus in NLH 203.

“This is IECSE’s first ever design competition” explained Siddharth Ahuja, the Design Head of IE CSE. The first round of Artem was fairly simple and required the contestants to replicate an image that was presented to them and then use their creativity to modify their replicated image in accordance with the given theme-Candyland. The competition was tough and most of the contestants did a flawless job of replicating the image of the castle they were shown. Their creativity in modifying the castle is what seemed to have been the criterion for qualifying into the final round. A bonus theme, Batman, was also introduced in the contest, to allow the participants to gain extra points for finishing the first two images quickly. Photoshop, Illustrator, and Inkscape were some of the softwares that the contestants used for this round.

12963513_1012708178818703_9104500395189793824_n

Image Courtesy: IE CSE

In the final round of Artem, all the participants were only allowed to use either Photoshop or Illustrator. In this round, each participant was randomly given two fictional characters to combine. To add to the challenge, the participants were given a fixed currency with which they would have to buy the editing tools that they required for the job. “I enjoyed that one could add as much detail as he/she wanted to their design” opined Zoheb Shuja, whose amalgamation of Mojojojo and Deadpool won the competition for him.