The End.

Kilari Teja
@ksdme, coala and gsoc
3 min readAug 15, 2018

14ᵗʰ August 2018

So, the official coding period of Google Summer of Code 2018 ends tonight, I have been working as a student for coala, a code linting and fixing tool chain building tools to make it available from within the editor. The journey so far has been jam packed with all kinds of action. Before I delve deeper into my experiences with GSoC’18 and the coala community, I would like to take a minute to give you my week on week development updates. So, here it goes

Developments

  • TagSectionFilters are now SectionTagsFilters: The implementation for SectionTagsFilter is complete and has been merged into cola core. Filtering can now be used at runtime and filtering of sections can be done using tags. Here is a sample invocation using tags
coala --filter-by section_tags save cance
  • FileProxies: coala now has partial support for analysis of in-memory files using FileProxies. coalib.coala_main.run_coala() can accept a multiplexed cache and use it to get a file dict. It is stable for now but the recent introduction of FileFactories is a matter of concern as currently ProxyMapFileCache returns pure dicts and the vanilla FileDictFileCache returns extended dict.
  • cEP: The cEP has now been merged and all the changes it suggests can be considered final and accepted. The cEP was in review for long but thanks to quick suggestions by John Mark Vandenberg it got merged in time.
  • coala-ls integration: Support for SectionTagsFilters and FileProxies have been implemented within coala-ls. You can now select which sections to run during certain kind of events using tags. Just mark sections which need to run on save with a save tag etc.
  • coala-vs-code: Finally, coala-vs-code has been merged!
  • Work Doc: I now have a work document at http://projects.coala.io/GSoC/2018/StatusReport/ksdme.
  • And much more…

Some of the stuff I promised in the proposal is pending, but we have agreed to consider it Post GSoC work because of some tight schedules. Checkout the work doc to learn more. So, now that we have our weekly ritual done, let me talk about GSoC’18 itself and me.

I feel the right way to convey what I mean is in my own voice, so, here is an excerpt of an interview of mine that I had with me:

Q) How do you feel?

Well, the past few days have been tiring, I have had to work a bit harder than I am used to hit the deadline. I did hit it though, thank god, thank my mentors and the almighty John Mark Vandenberg. I certainly feel a bit more relaxed.

Q) Are you nervous about the result?

Of course, I have worked hard for the past few weeks, I would hate to see my efforts go to vain (although the ‘work’ itself would never be wasted, cause Open Source…).

Q) What did you learn?

Are you kidding me, GSoC’18 taught me quite a few things, of them all the most important being touch typing 😀. Sounds silly, but yes, I learned to type because I had to do it fast enough. I also got introduced to the awesome world of CI/CD systems, the joy you get reviewing others code and what not. I finally have found my niche group of people I can talk Python to. I would definitely recommend participating if you can.

Q) Would you do it again?

Unfortunately, I will graduate college this year, so I won’t be eligible any more. I am glad I got to do this.

Q) Planning to stay with the community?

Obviously, I still plan to keep helping the community in every way possible. I would like to learn from all the cool people I met during my journey. I will begin with making coala-ls installable via pip.

Ok, that was it, but on a serious note, I would like to thank 高策 and John Mark Vandenberg and the entire coala community for helping me through the entire time and putting up with both flaws in my code and me, without their help this surely wouldn’t have been possible. I am glad I took the opportunity and put in the effort.

This is not the end of this series though, I will write one more post after the results are announced.

--

--