GSoC Posts

Community Bonding post Hey guys, I am back with one more post on how I spent my GSoC community Bonding period with coala. If you have read my previous post, you know that I was tensed about how will I get used to GitMate in such short time. Let's see what happened. First week: Firstly, I have set up GitMate environment and I wanted to work on some issue to get familiar with code base. So, I chose a small issue and started working on it. My work was to sync issues labels every time someone pushed a commit and updated their PR. So, I got all the PR labels in list called ignored list and each time you update a pull request(PR), GitMate gets all the labels of the issues, which the PR closes and if those labels aren't present in the PR, then add it to the PR, and remove all other labels on the PR, which isn't on the issue, also don't remove the PR related labels like "process/WIP", "process/pending review", size labels, etc. What I learned by f...

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 ...