GSoC Posts

What is GSoC? Google Summer of Code (GSoC) is an online, international program designed to encourage university student participation in open source software development. Students work for an open source software organization, and earn a stipend for successfully completing the project. If you want to know more about GSoC, click  here . How it all started? I joined a student club called  FOSS@AMRITA  in Amrita University , where a group of students work on various open source projects helping each other. I got to know about GSoC from the club itself, most of the previous year GSoC students from our college were members of the club. I was motivated by seeing them and started learning coding, staying in the lab after my college hours. Why I was attracted to GSoC is for real world experience, to prove myself that I can do something and for swag, stipend too. Why coala? Choosing an organization from previous year GSoC orgs was a hard one. Initi...

Coding Phase 2 Coding phase 2 has come to an end, I worked almost everyday in this phase, I finished lots of work including the one which was left over in phase 1. Though I tried to complete all the tasks as planned, there were a couple of issues left over which would take some extra time. Week 3 : I worked on "Adding Team class" in IGitt, which was a little tricky one because GitLab doesn't have teams. So, assuming GitLab groups(which actually represent organization) as teams was a workaround for the problem. Then I added a feature "Auto assign issues based on commit mention in PR". When any user opens a PR(pull request) and mentions issues, which are being closed or fixed, in commit message, GitMate automatically assigns PR author to the mentioned unassigned issues and if anyone else is assigned to mentioned issues, GitMate will inform the user to work on other issues. You can check out my merged MR here . Week 4 : I made a PR on adding `mergea...

Coding Phase 1 Week 4 Fixes vs Closes : I started working on adding a new feature in existing pull request(PR) auto review plugin, called "Fixes vs Closes checking". In coala, for every PR we make, we have to mention which issues we are trying solve, in commit message. We should use `Fixes issue_link`, if we are fixing a issue which has a `type/bug` label and use `Closes issue_link` if we are closing a issue which doesn't have a `type/bug` label. So, I have written code to do this automatically by GitMate, if commit message doesn't follow the guideline, then GitMate will remove the PR from review queue by removing `pending review' label, adding `work in progress` label to the PR and configurable comment will be added on the PR explaining what was done wrong. I have also made   IGitt enhancement to know which keywords(Fixes, Closes) referenced which issues.  PR Rejector : I mentioned in the previous blog post about having some issues with testing m...

Coding Phase 1 Hey guys, it's been a long time since my last GSoC post, I will be sharing what have I done in GSoC Coding Phase 1 in this post. As I said in my last post, I had exams during this period and I had lot of work to do. First week I couldn't work first three days due to exams.  As soon as I got a couple of preparation holidays, I started working on writing a new plugin called PR(pull request) rejector, which closes PR's opened on certain list of branches, and leave a configurable comment stating to open PR on another source branch. This plugin will be helpful to automatically review the source branch of the PR and save the time of developers. Though I started working on it, I could not complete it yet, due to some migrations error, so I decided to work on another issue and come back to this later. Second week There were some exams in the beginning of the week, but I was free in the weekend, so I started working on a IGitt enhancement, to add me...

My journey in coala: I joined coala organisation in January 2017, expecting to apply for GSoC 2017. Due to age restrictions I couldn't apply in 2017. But, I stayed and learned a lot from coala and it's community. I would say coala is really good for newcomers, it provides great documentation and help from community. Initially, I worked on coala core repositories, but I was interested in developing coala bot(corobo predecessor), a chat bot which helps members of coala to ease their workflow. So, I started fixing some bugs and started adding new features to it. These things led to my promotion to developer and I was Google Code In 2017 mentor. Selecting project and Writing Proposal: Recently, after GCI 2017, corobo was shutdown due to misuse of bot by some mischievous forces. And it increased a lot manual work and everyone was missing corobo badly. So, I started working on a GSoC proposal to fix corobo security and add some enhancements to it. After finishing up my draft ...